Moving as many Entities metadata concepts/fields as possible to schema.org fields
Or, only using schema.org fields when a concept/field doesn't exist in Dublin Core / DCTerms
Some questions from the PR:
Do Person Entity names belong in "dc.title"? Or is that not descriptive enough, and we should look to use schema.org's Thing schema ("thing.name" field)
Do Person Entity ORCIDs belong in "dc.identifier"? Or again, should we look towards schema.org and use "thing.identifier" or "thing.identifier.orcid"
Tim
2
20mins
Revisiting Priorities Listing (see full list below)
This list was voted on in the meeting on May 23, 2019 (just before OR2019). The prioritization below may change, but it gives a high level overview of what still needs to be done.
(Lieven, Ben, Tim, Fernando, Jose, Mark, Oliver, Paulo) Submission integration (creating Entities & relations using the Item submission process) - Mockups already created by Paulo previously.
(Lieven, Ben, Tim, Jose, Oliver, Paulo) Which metadata fields should be used for each Entity type. (DS-4223).
(Lieven, Ben, Tim, Mark) Additional data for relations (essentially "metadata" or labels on relations) - Related to many other features / use cases.
(Oliver, Paulo) Author name variants - Not currently implemented
(Jose) 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.
(Mark) 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.
(Fernando) 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).
Relates to GDPR
(Alexander) 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.
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).
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.
Tim will create a JIRA ticket to describe the two metadata options (rely more on DC, or move more towards schema.org). Will ask DCAT (and others) to review and provide feedback.
List pros/cons to each approach. Note adding schema.org support makes entities metadata easier, but may add complexities to Browse/Search/Submit configurations (we could properly configure out-of-box) and other features that relate to metadata (e.g. Batch metadata editing, OAI-PMH, etc)
Simple approach, extending relations to mostly support Author name variants
Complex approach, come up with a solution to also support temporal relationships (e.g. author with changing affiliations, Journals moving between publishers, Journals changing names...over time)
Atmire recommends simple approach, as it'll be much quicker to get to for 7.x. But, this means no support for Temporal relationships (other than possibly recommending versioning Entities that have changed relationships over time, e.g. version 1 of a Journal may have one name, while version 2 has a different name).
Agreement among team
Decision:
Version 7 will concentrate on Author variants (simple label on relations)
Temporal relations will be left for Version 8. More use cases may help us design this better.
May even want to consider whether these are better met by somehow storing relationships as triples (as RDF has solved some of these issues via usage of triples)
, 
but requested a missing javadoc, Paulo Graça