Page tree
Skip to end of metadata
Go to start of metadata

Date & Location

 at 15:00 UTC (11:00am EST)


Join from PC, Mac, Linux, iOS or Android:  (Meeting ID: 502 527 3040)


Actual attendee list will be updated after meeting.




Any additional topics to today's agenda


OpenAIRE v4

Updates from the OpenAIREv4 sub-team on recent discussions / work.

320minsName variants / Relationships in SubmissionUpdates / Proposals for how to potentially implement name variants & Relationships in Submission UI.Atmire
410minsDiscussion of Task #7

Dig a bit deeper on this task. What is possible for DSpace 7?

  • #7 : Deleting objects with Relations (How or should deletion propagate between closely related objects, e.g. delete entire Journal)
55minsWrap-up and Assigning tasks
  • Assign tasks / PRs to review (as needed)
  • Next Meeting is Tues, July 23.

Current Work

Tickets to Resolve

PRs Needing Review

  1. (NEW) (Rest Contract) (Entities) Rename properties and support for name variants: (Tim Donohue, Paulo Graça)
  2. (Angular) (Entities) Deleting relationships: (Paulo Graça , Tim Donohue )
  3. (Angular) (Entities) One-sided relationship filtering and refactoring ((tick)Ben Bosman,(tick) Paulo Graça )
  4. (Angular) (Entities) Grid templates for entity types (Paulo Graça, Alexander Sulfrian )
  5. (NEW) (Angular) (Entities) Search Performance optimizations

PRs Merged this week!

  1. (tick) (REST Contract) (Entities) Support for defining relationship lookups in the submission forms

Task List

This list was roughly prioritized 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. NOTE: Keep in mind, just because an item 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.

  1. (Lieven, Ben, Tim, Fernando, Jose, Mark, Oliver, Paulo) Submission integration (creating Entities & relations using the Item submission process) - Mockups already created by Paulo previously.
  2. (Lieven, Ben, Tim, Jose, Oliver, Paulo) Which metadata fields should be used for each Entity type. (DS-4223).
  3. (Lieven, Ben, Tim, Mark) Additional data for relations (essentially "metadata" or labels on relations) - Related to many other features / use cases. 
  4. (Oliver, Paulo) Author name variants - Not currently implemented
  5. (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.
  6. (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.
  7. (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).
    1. Relates to GDPR
  8. (Alexander) 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.
  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).
  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 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)


  • OpenAIRE v4 subteam updates (slides from Jose)
    • Slides: 
    • Main DSpace areas of impact of OpenAIREv4 guidelines
      • Input (input-forms, sword, batch edit/import, APIs, etc)
      • Management (CRUD, new metadata schemas)
      • Output (OAI-PMH mainly, but also metadata export, APIs, etc.
    • Entities for OpenAIREv4
      • Publication
      • Person (Author)
      • Project (Funding)
      • Organization
      • Publisher? (optional, may not be out-of-box)
    • Showed off implementation on DSpace 5, which is based more on authority control system.
      • Person from ORCID
      • Publisher via Sherpa Romeo
      • Custom OAI-PMH schema with metadataPrefix=oai_openaire
    • DSpace 7 development
      • change the way funding info is presented & shared (to be developed by Dimitris)
      • Using OpenAIRE API to pull in Project (Funding) entities. (Seems similar to pulling in People via ORCID)
    • Proposal Doc for DSpace 7:
    • TODO: For next week's discussion. Read doc concentrating on R1 and R2
  • Name variants & Relationships in Submission UI.
    • Lieven demoed early screenshots (Relations in submission forms and author name variants)
    • Lots of discussion of how this would work with existing Authority Control & ORCID integration → Tabled for next week
    • How would permissions on name variants work?  May depend on where name variants are stored....are they metadata on a Person?  Are they labels on Relationships pointing at a Person?

Action Items

Any assigned actions will appear here, along with details of who they are assigned to.

  • No labels