Next Steps to Prioritize (unordered, but numbered for easy reference)
(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).
Is this list complete?
All
3
25 min
Discuss TODOs for OR2019
In order to make a big splash at OR2019, it'd be good to have some direction on the following
Metadata schemas for Entity Type field (relationship.type) and each Entity Type (e.g. People, Journal). See DS-4223
Three months since last meeting of this group. Congrats to the team who worked so hard on entities and getting the preview release out the door! There is plenty of work still let to do, the submission process for entities is not yet there. Many other phase 2 features to discuss, but getting the preview out was no small feat, and all that hard work is much appreciated.
Tim notes that one thing that will change going forward, in the past work was in a separate branch and that was very useful for the first cut of entities, everything going forward should be against the master branch. More direct work with the DS 7 working gorup. Hope that the PRs will go in more rapidly, be smaller, and have a bigger pool of testers.
The hope is that moving against master will reduce conversations being repeated in the Entities and the DS 7 working group. Goal to bring all reviews into one place and all feedback is visible.
Prioritization of features: setting an order for discussion and making sure everything is on the list
See list above in order based on attendee discussion
To-dos for OR2019
3rd party metadata schema: Schema.org, mostly flat, could be a good starting place.
Need to have some sort of CRIS data model included and need to work on mapping these metadata schema to represent entities. One implemented by openAIRE 4 is one we could easily comply with.
Schema.org will be a starting point, will make a small selection of fields, and look at mapping to Serif and openAIRE schema. Then can easily extend as needed
Next meeting 18th June at 15:00 UTC
Action Items
Any assigned actions will appear here, along with details of who they are assigned to.