Page History
...
- (REST Contract) Metadata suggestions in the live import https://github.com/DSpace/Rest7Contract/pull/83 (Paulo Graça - I'm ok with the current status of this PR, Tim Donohue - provided feedback)
- (REST) Delete item with relationships: configure defaults https://github.com/DSpace/DSpace/pull/2599 (Paulo Graça - feedback added, Alexander Sulfrian, Tim Donohue)
- (REST) Creating an archived item from an external source https://github.com/DSpace/DSpace/pull/2590 (Paulo Graça - It's Ok, but should we rely solely on the relationship.type from collection item template?, Tim Donohue)
- (NEW) (REST bugfix) bug update relationships https://github.com/DSpace/DSpace/pull/2610 (Paulo Graça , Tim Donohue )
- (Angular) Keep virtual metadata on relationship delete https://github.com/DSpace/dspace-angular/pull/530 (Paulo Graça, Tim Donohue)
- (Angular) Create relationships during the submission https://github.com/DSpace/dspace-angular/pull/531 (Paulo Graça - it's Ok, but still is WIP, Tim Donohue)
- (NEW) (Angular) Tabbed display of relations: https://github.com/DSpace/dspace-angular/pull/517 (Paulo Graça ) - shouldn't it be also available at main search?, Tim Donohue ) (MERGE CONFLICTS)
- (NEW) (Angular) Item page entities improvements (OpenAIRE4) OpenAIRE 4 required metadata fields https://github.com/DSpace/DSpacedspace-angular/pull/2576532 (Dimitris Pierrakos, Ben Bosman - provided feedbackPaulo Graça, Tim Donohue)
PRs Merged this week!
- sample screenshots: pr-532.pdf
- (NEW) (Angular) Virtual metadata on item delete (REST) Feature: external sources https://github.com/DSpace/DSpacedspace-angular/pull/2560533 (REST) Entities: Projects discovery configuration https://github.com/DSpace/DSpace/pull/2598 Paulo Graça , Tim Donohue )
- sample screenshots: pr-533.pdf
- (NEW) (Angular) Reordering related entities in the submission (REST) Delete item with relationships https://github.com/DSpace/DSpacedspace-angular/pull/2577534 (Paulo Graça, Tim Donohue)
- (OpenAIRE4) OpenAIRE 4 Entities and Relationships OpenAIRE 4 required metadata fields https://github.com/DSpace/DSpace/pull/2575
Task List
This task list has been updated as of our meeting on Oct 22, 2019. The tasks are numbered for easy reference, but are not necessarily listed in priority order. During this meeting we worked to re-summarize current work status so that we can align this task list with the DSpace 7 Estimation Process (and as such, estimate any we feel should be considered for 7.0 release). NOTE: Keep in mind, just because a task is listed here does NOT guarantee it will be completed for DSpace 7. Some of these tasks may need to be delayed for a future release.
Panel | ||
---|---|---|
| ||
= task considered "completed" (unless bugs or issues are later found) = task is incomplete or has further work to be done. = task that may be delayed or postponed for after 7.0. |
- 2576 (Dimitris Pierrakos, Ben Bosman - provided feedback, Tim Donohue)
- (NEW) (OpenAIRE4) OpenAIRE 4 submission forms and virtual metadata [WIP] https://github.com/DSpace/DSpace/pull/2608 (Dimitris Pierrakos, Ben Bosman, Tim Donohue)
- (NEW) (OpenAIRE4) OpenAIRE4 oai_openaire metadata format support [WIP] https://github.com/DSpace/DSpace/pull/2592 (Dimitris Pierrakos, Tim Donohue, Ben Bosman)
PRs Merged this week!
- (REST) Feature: external sources Metadata schemas for Entity types (DS-4223). REST: https://github.com/DSpace/DSpace/pull/24432560
- (REST) Entities: Projects discovery configuration , Angular: https://github.com/DSpace/dspace-angularDSpace/pull/4202598
- (REST) Delete item with relationships Early Docs / Notes: https://docs.googlegithub.com/documentDSpace/dDSpace/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.wjaqg235p53rpull/2577
- (OpenAIRE4) OpenAIRE 4 Entities and Relationships https://github.com/DSpace/DSpace/pull/2575
Task List
This task list has been updated as of our meeting on Oct 22, 2019. The tasks are numbered for easy reference, but are not necessarily listed in priority order. During this meeting we worked to re-summarize current work status so that we can align this task list with the DSpace 7 Estimation Process (and as such, estimate any we feel should be considered for 7.0 release). NOTE: Keep in mind, just because a task is listed here does NOT guarantee it will be completed for DSpace 7. Some of these tasks may need to be delayed for a future release.
Panel | ||
---|---|---|
| ||
= task considered "completed" (unless bugs or issues are later found) = task is incomplete or has further work to be done. = task that may be delayed or postponed for after 7.0. |
- Metadata schemas for Entity types (DS-4223).
- REST: https://github.com/DSpace/DSpace/pull/2443 , Angular
- (Minor refactor) Decide which metadata field should be used to store Entity Type (DS-4184). Currently, it is stored in "relationship.type". (DEEMED LOWER PRIORITY, but "nice to have" for 7.0 if possible?)
- Creating Relations (between Entities) with CSV Batch Import
- Permissions on Relations (between Entities)
- Discussed on Aug 6
- Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.y6qarjnylexl
- Deleting Entities that have existing relations
- Deletion action itself:REST Contract: https://github.com/DSpace/Rest7Contractdspace-angular/blob/master/relationships.md#deleting-a-relationship , RESTpull/420
- Early Docs / Notes: https://githubdocs.google.com/DSpacedocument/DSpace/pull/2332 , Angular: https://github.com/DSpace/dspace-angular/pull/402Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.c62y8iqnvlurwjaqg235p53r
- (Minor refactor) Decide which metadata field should be used to store Entity Type (DS-4184). Currently, it is stored in "relationship.type". (DEEMED LOWER PRIORITY, but "nice to have" for 7.0 if possible?)
- Creating Relations (between Entities) with CSV Batch Import
- REST: Copy virtual metadata from deleted entity to related entity
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/78 REST impl: https://github.com/DSpace/DSpace/pull/2577 Angular Impl (in progress / under review): 2269 and https://github.com/DSpace/dspace-angularDSpace/pull/530
- 2471 and https://github.com/DSpace/DSpace/pull/2522
- Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.pm34t6u1djdf
- Completed, but may require usability improvements (NEEDS DISCUSSION - may be delayed for v7.1)
- Discussed on Aug 6
- Early Docs /
- Creating new Entities using Submission Forms
- REST: https://github.com/DSpace/DSpace/pull/2443 Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.9aixusqzgcnpy6qarjnylexl
- Deletion action itself:
- REST Contract:
- REST Contract: https://github.com/DSpace/Rest7Contract/blob/pull/64 , REST Impl: master/relationships.md#deleting-a-relationship , REST: https://github.com/DSpace/DSpace/pull/2472 Angular Impl (in progress / under review)2332 , Angular: https://github.com/DSpace/dspace-angular/pull/531402
- Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.9aixusqzgcnpc62y8iqnvlur
- Copy virtual metadata from deleted entity to related entity Search External Sources (includes ORCID integration with Entities)
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/74 78
- REST Implimpl: https://github.com/DSpace/DSpace/pull/2560
- Angular is in implementation (no PR yet)
- 2577
- Angular Impl (in progress /
- If an Admin:
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/82 REST Impl ( under review): https://github.com/DSpace/DSpacedspace-angular/pull/2590If a Submitter (Feature is NOT specific to Entities, as this is simply porting the "Live Import" framework of DSpace 6.x) REST Contract under review530
- Early Docs / Notes: https://githubdocs.google.com/DSpacedocument/Rest7Contractd/pull/83
- 1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.pm34t6u1djdf
- Completed, but may require usability improvements (NEEDS DISCUSSION - may be delayed for v7.1)
- Creating new Entities using Submission Forms
- REST:
- Create name variants in submission
- REST Impl: https://github.com/DSpace/DSpace/pull/2561 Angular Impl (in progress / under review) - this is included as part of 2443
- Early Docs / Notes: https://githubdocs.google.com/DSpacedocument/dspace-angular/pull/531
- Display name variants on Item pages (Angular)
- Creating relations between two Entities during Submission process
- Configuration of Entities needed for OpenAIRE v4:
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/64 ,
- REST Impl:
- Angular Impl (in progress / under review): https://github.com/DSpace/
- Configuration of Submission Input Forms for OpenAIRE v4 (in implementation, no PR yet)
- Search External Sources (includes ORCID integration with Entities)
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/74
- REST Impl: https://github.com/DSpace/DSpace/pull/2560
- Angular is in implementation (
- no PR yet)
- Early idea is to simply display the related item as plain text metadata (until workflow approval completes).
- Requires AIP Backup & Restore
- Proposal: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.n8ktliibe7kj
- Requires AIP Backup & Restore, as SWORD uses the same crosswalks / format as AIP.
- Proposal: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.xufwyy1ep8h2
- Should we eventually consider hiding these Collections which only serve to store Entity Types?
...
- Convert External Sources to an Entity
- If an Admin:
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/82
- REST Impl (under review): https://github.com/DSpace/DSpace/pull/2590
- If a Submitter (Feature is NOT specific to Entities, as this is simply porting the "Live Import" framework of DSpace 6.x)
- REST Contract under review: https://github.com/DSpace/Rest7Contract/pull/83
- If an Admin:
- Convert External Sources to an Entity
- Name Variants
- Create name variants in submission
- REST Impl: https://github.com/DSpace/DSpace/pull/2561
- Angular Impl (in progress / under review) - this is included as part of https://github.com/DSpace/dspace-angular/pull/531
- Display name variants on Item pages (Angular)
- Create name variants in submission
- OpenAIRE v4 support (using Entities)
- Configuration of Entities needed for OpenAIRE v4: https://github.com/DSpace/DSpace/pull/2575
- Configuration of Metadata fields/schemas needed for OpenAIRE v4 (under review): https://github.com/DSpace/DSpace/pull/2576
- Configuration of Submission Input Forms for OpenAIRE v4 (in implementation, no PR yet)
- Configuration of OAI-PMH for OpenAIRE v4 (in implementation, no PR yet)
- How to display related items on an Item page if that related item is still in workflow approval
- Early idea is to simply display the related item as plain text metadata (until workflow approval completes).
- Edit Item page integration
- Relations in AIP Backup & Restore
- Creating Relations in SAF Import (might be postponed for a future release)
- Requires AIP Backup & Restore
- Proposal: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.n8ktliibe7kj
- SWORD integration (might be postponed for a future release)
- Requires AIP Backup & Restore, as SWORD uses the same crosswalks / format as AIP.
- Proposal: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.xufwyy1ep8h2
- Best Practices around Entities in Collections (NOT: this may just be early documentation). We've suggested in the Preview Release to structure Collections based on Entity Type (Person Collection, Projects Collection, etc). We should better document and formalize these best practices.
- Should we eventually consider hiding these Collections which only serve to store Entity Types?
Notes
Question from last week (Nov 26): How do we handle "relatedIdentifiers" vs "alternateIdentifiers" in our DSpace metadata?
- The new Schema.org identifier fields in PR#2576 seem to correspond to "alternateIdentifiers" (e.g. person.identifier.gsid is an alternative Google Scholar identifier for the Person Entity).
- These fields represent (externally created) Identifiers that correspond to the Entity in DSpace. For example, if a publisher has its own DOI, then the publisher's DOI would be stored in these fields....while the DSpace-generated DOI would be stored in "dc.identifier.uri" as normal.
- "relatedIdentifiers" concept could be represented as new "oaire.relatedIdentifier.*" fields perhaps? (Jose Carvalhoand Paulo Graçawill discuss and get back to us)
- DECISION: was to remove the identifier fields from publication and rely on `dc.identifier.*` for that entity type (for now). Some identifiers were added to other Entities however. See PR#2576 for updates
- The new Schema.org identifier fields in PR#2576 seem to correspond to "alternateIdentifiers" (e.g. person.identifier.gsid is an alternative Google Scholar identifier for the Person Entity).
- Discussion about entities on XOAI layer (https://github.com/DSpace/DSpace/pull/2592) The way XOAI uses Solr, we foresee that Solr will get some weight and also the "/dspace/bin/dspace oai import" method will be a little bit slower using this approach (this was negligible with our experience with DS5, but we just processed Publications, now we may also process Persons). At the moment the only possible solution that occurs is to have a configuration (perhaps on oai.cfg) to enable/disable entities. Other suggestions includes filtering by the relationship label, like: isAuthorOfPublication.
- Some possible OAI-PMH performance issues noted, if we are loading large numbers of objects (e.g. all related Entities) in order to fill out the response of one Entity.
- Possible solution: Do not load up all related Entities...instead, just load the info available on the relationship object (i.e. a Label and the Entity ID). This may speed up OAI-PMH requests as we'll be loading less objects. However, it may not be exactly what the OAI harvesters expect (uncertain).
- Could also consider precaching these responses for speed, but that may add a lot of complexity to DSpace itself. The primary limitation here is within OAI-PMH, and this isn't a DSpace-specific issue.