Page History
...
Metadata schemas for Entity types (DS-4223). 
(Minor refactor) Decide which metadata field should be used to store Entity Type (DS-4184). Currently, it is stored in "relationship.type".- 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/Rest7Contract/blob/master/relationships.md#deleting-a-relationship , REST: https://github.com/DSpace/DSpace/pull/2332 , Angular: https://github.com/DSpace/dspace-angular/pull/402
- Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.c62y8iqnvlur
- Copy virtual metadata from deleted entity to related entity
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/78
- In implementation (REST API and Angular)
- Dynamic display of Relations
- Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.pm34t6u1djdf
- May require usability improvements (NEEDS DISCUSSION)
- Submission Integration Tasks
- Creating new Entities using Submission Forms
- Creating relations between two Entities during Submission process
- Contract: https://github.com/DSpace/Rest7Contract/pull/64 , REST: https://github.com/DSpace/DSpace/pull/2472
- In Implementation (Angular)
- Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.9aixusqzgcnp
- Search External Sources (includes ORCID integration with Entities)
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/74 (in review)
- REST: https://github.com/DSpace/DSpace/pull/2560 (in review)
- In Implementation (REST API and Angular)
- Convert External Sources to an Entity
- If an Admin: Contract under review: https://github.com/DSpace/Rest7Contract/pull/82
- If a Submitter: Contract under review: https://github.com/DSpace/Rest7Contract/pull/83
- Name Variants
- Create name variants in submission
- In Implementation (REST API and Angular)
- Display name variants on Item pages (Angular)
- OpenAIRE v4 implementation (using Entities)
- TO BE DISCUSSED ON OCT 29.
- Early PR expected in the next week or so. This initial work will be configuration only (no new code).
- Possible need for a follow-up PR to implement improvements to OAI-PMH to support OpenAIRE v4.
- How to display related items on an Item page if that related item is still in workflow approval
- TODO: Needs proposal. Early idea is to simply display the related item as plain text metadata (until approved).
- Edit Item page integration
- TODO: Needs proposal. How to display relationships on "edit metadata" tab. How to add relationships on "relationships" tab
- 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
Old Task List (kept here for reference while editing the above list)
- Submission integration (creating Entities & relations using the Item submission process) - Mockups already created by Paulo previously. - In implementation
- Not started yet: Adding name variants, importing from external sources
- Which metadata fields should be used for each Entity type. (DS-4223). - In implementation
- Not done yet: A field to store the entity type. This is currently set to relationship.type
- Additional data for relations (essentially "metadata" or labels on relations) - Related to many other features / use cases. - In implementation
- Not fully complete.
- Author name variants - In implementation
- Not fully complete. Can estimate.
- Configuration of batch import (via CSV) for Entities - Already a CSV import available, but can only link entities in CSV to existing entities (in the system). Need to decide how to represent relations in CSV. - In implementation
- Needs analysis of what is outstanding.
- Permissions on Relations (who has permissions to add/modify/delete relations) - Currently, if you have Edit permissions on the Entity, then you can edit/delete any relationships to/from that Entity. (NEEDS DISCUSSION)
- Deleting objects with Relations (How or should deletion propagate between closely related objects, e.g. delete entire Journal) - Currently, deleting a relation just decouples the two Entities. E.g. If you delete a Person entity, that Person may no longer be listed on any Publications it is linked to (may want to copy info over after deletion). - Discussed on Aug 6
- Relates to GDPR
- AIP Backup & Restore (of Entities)*
- Dynamic display of Relations - determine automatically how a list of entities displayed on an Item page (list vs search). Currently hardcoded based on entity type (in item page template). Want to make it configurable/dynamic. (NEEDS DISCUSSION)
- SWORD integration (submission of Entities via SWORD) - Uses same format as AIP. Once AIP is implemented, SWORD should be easy.
- OpenAIRE v4 implementation using Entities* - Brought up in Steering. Possibly just an OAI-PMH configuration which maps Entity metadata fields to OpenAIRE v4
- ORCID integration with Entities (for Person Entities). (Related to #15)
- Importing from external sources (can estimate)
- Best Practices around Entities in Collections. 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. Can we hide
- Should we eventually consider hiding these Collections which only serve to store Entity
- The ability of pick the proper affiliation of a Person for a specific context. DSpace should address this use case to allow the user to describe something like in this document http://repositorium.sdum.uminho.pt/bitstream/1822/46268/1/1-s2.0-S1877050917302788.pdf regarding the authors and affiliations. You have different persons, each can belong to an institution at the time of that publication. The affiliation shouldn't be changed afterwards. And the user should be able to pick the proper one if an Author has more than one. (PER discussion on July 16, this is lower priority and may be more likely to be implemented in DSpace 8)
(REQUIRED) Deeper dive discussion into how Entities will work with Authority Control, and how ORCID integration will work (as ORCID integrates with Authority Control). Some useful resources: Discussed in meetings on Aug 27 and Sept 17 - In implementation
- Authority Control of Metadata Values ORCID Integration#Importingexistingauthors&keepingtheindexuptodate
- Types?
Notes
Overview
Content Tools