Page History

...

1. Submission integration (creating Entities & relations using the Item submission process) - Mockups already created by Paulo previously. - In implementation
2. Which metadata fields should be used for each Entity type. (DS-4223).  - In implementation
3. Additional data for relations (essentially "metadata" or labels on relations) - Related to many other features / use cases.   - In implementation
4. Author name variants  - In implementation
   1. Can estimate
5. 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
6. 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)
7. 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
   1. Relates to GDPR
8. AIP Backup & Restore (of Entities)*
9. 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)
10. SWORD integration (submission of Entities via SWORD) - Uses same format as AIP. Once AIP is implemented, SWORD should be easy.
11. OpenAIRE v4 implementation using Entities* - Brought up in Steering.  Possibly just an OAI-PMH configuration which maps Entity metadata fields to OpenAIRE v4
12. ORCID integration with Entities (for Person Entities). (Related to #15)
    1. Importing from external sources (can estimate)
13. Best Practices around Entities in Collections.  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 these Collections which only serve to store Entity Type.
14. 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)

15. (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

Notes

• Quick intros (welcome to Helen)
• Discussion of  https://github.com/DSpace/Rest7Contract/pull/74
  • Ben has removed any creation of Authority control values. This PR will be limited to Entities only
    • We also discussed that any changes to Authority Control values should be brought to / proposed to the DSpace 7 Working Group, as that is outside the scope of the Entities WG.  We should remain concentrated on Entities alone...though if we have broader ideas/proposals we can present them to the DSpace 7 WG
  • Discussion of whether the POST to create Entities should be on the /items endpoint or /workspaceitems
    • If on /items, this would be Admin only.  Only Admins would be able to create Entities from ORCID or similar external systems. This endpoint also skips workflow approval (which is why it's Admin only)
    • If on /workspaceitems, then more people could create Entities. However, Entities pulled from ORCID would also need to go through workflow approval (if enabled on the Collection)
    • After much discussion, we've realized this is very similar to DSpace 6.x Live import feature: 2016 Framework for live import from external sources
      • This is not yet built into 7.x, but is still in our Planning spreadsheet.
    • Live import seems like the same use case, as its purpose is to lookup information from an external source and then create an Item based on that external source metadata
    • We agree that there seems like a dependency here on that Live Import feature first being better defined
  • Later discussion that we need to keep in mind that this contract is currently assuming that we can generalize different external sources under a single endpoint.  While we hope this to be true, Andrea B's comment is correct. If we begin to find that during implementation, generalization is extremely difficult or impossible, we may need to revisit this contract and consider separate endpoints per external service (ORCID, PubMed, etc).