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

Date & Location

 at 16:00 UTC (11:00am EDT)


Join from PC, Mac, Linux, iOS or Android:


Actual attendee list will be updated after meeting.




Any additional topics to today's agenda?

220minsUpdates on OpenAIREv4


New PRs:

Based on:

Mainly focus on Annex 6 and Annex 7

Future steps: demo submission form

Jose & Paulo
320minsEntities integration on edit item (Edit metadata tab)Mockups for "Edit Metadata" tab of the Edit Item page.  For Entities, this tab will need to display (read-only) virtual metadata, so that it can be seen (and reordered) alongside real metadata.Lieven
4if time allowsReplacing plain-text metadata with relationshipSolution for common use case problem: If you’d be submitting a new person entity, which already has 10 publications in the repository containing that person's name as plain text metadata in, duplicate metadata would be created (the old actual metadata and the new virtual metadata).Lieven
515minsWrap-up and Assigning tasks
  • Assign tasks / PRs to review (as needed)
  • Next meeting is Tues, Nov 19

Current Work

Legend for status icons

(blue star) = Highest Priority tasks (please prioritize these reviews/tasks over others). These are tasks with lots of dependencies

(error) = review done, changes were requested or bugs found.

(tick) = review done, approved.

(warning) = review done, merge conflict or other minor changes requests

1 APPROVAL = pull request only requires a single approval to merge.  This is generally reserved for PRs which are either smaller, obvious, and/or bug fixes with tests to prove they work.  

Tickets to Resolve

PRs Needing Review

  1. (NEW) (REST Contract) Adding entry HAL Link at entryValues level (Ben Bosman - provided feedback, Tim Donohue )
  2. (REST Contract) Metadata suggestions in the live import (Paulo Graça - REREVIEW. suggests to split in 2, Tim Donohue - REREVIEW)
  3. (NEW) (REST) Delete item with relationships (Paulo GraçaAlexander Sulfrian)
  4. (REST) Entities bug-fixes in place management UPDATED (Chris WilperTim DonohuePaulo Graça) May just need one approval
  5. (REST) Feature: external sources (Paulo Graça (tick), Tim Donohue )
  6. (REST) Entities: configuring whether name variants should be used UPDATED (Paulo Graça (tick)Tim Donohue) QUICK REVIEW & MERGE
  7. (NEW) OpenAIRE4: OpenAIRE 4 Entities and Relationships (Dimitris PierrakosBen BosmanTim Donohue)
  8. (NEW) OpenAIRE4: OpenAIRE 4 required fields (Dimitris PierrakosBen BosmanTim Donohue)
  9. (NEW) Fix for DS-4379 (listed above) (Paulo GraçaBen Bosman)

PRs Merged this week!

  1. (tick) (Angular) Item page entities changes/refactoring

Task List

This task list has been updated as of our meeting on Oct 22, 2019.  The tasks are numbered for easy reference, but are not necessarily listed in priority order.  During this meeting we worked to re-summarize current work status so that we can align this task list with the DSpace 7 Estimation Process (and as such, estimate any we feel should be considered for 7.0 release).  NOTE: Keep in mind, just because a task 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.

Legend for status icons

(tick) = task considered "completed" (unless bugs or issues are later found)

(warning) = task is incomplete or has further work to be done.

(question) = task that may be delayed or postponed for after 7.0.

  1. (tick) Metadata schemas for Entity types (DS-4223). 
    1. REST: , Angular:
    2. Early Docs / Notes:
  2. (warning) (Minor refactor) Decide which metadata field should be used to store Entity Type (DS-4184).  Currently, it is stored in "relationship.type".
  3. (tick) Creating Relations (between Entities) with CSV Batch Import 
    1. REST: and and
    2. Early Docs / Notes:
  4. (tick) Permissions on Relations (between Entities)
    1. Discussed on Aug 6 
    2. Early Docs / Notes:
  5. Deleting Entities that have existing relations
    1. (tick) Deletion action itself:
      1. REST Contract: , REST: , Angular:
      2. Early Docs / Notes:
    2. (warning) Copy virtual metadata from deleted entity to related entity
      1. REST Contract:
      2. In implementation (REST API and Angular)
  6. (tick) Dynamic display of Relations
    1. Early Docs / Notes:
    2. (warning) May require usability improvements (NEEDS DISCUSSION)
  7. Submission Integration Tasks
    1. (tick) Creating new Entities using Submission Forms
      1. REST:
      2. Early Docs / Notes:
    2. (warning) Creating relations between two Entities during Submission process
      1. Contract: , REST:
      2. In Implementation (Angular)
      3. Early Docs / Notes:
    3. (warning) Search External Sources (includes ORCID integration with Entities)
      1. REST Contract: (in review)
      2. REST: (in review)
      3. In Implementation (REST API and Angular)
    4. (warning) Convert External Sources to an Entity
      1. If an Admin: Contract under review:
      2. If a Submitter: Contract under review:
  8. Name Variants
    1. (warning) Create name variants in submission
      1. In Implementation (REST API and Angular)
    2. (tick) Display name variants on Item pages (Angular)
  9. (warning) OpenAIRE v4 implementation (using Entities)
    2. Early PR expected in the next week or so.  This initial work will be configuration only (no new code). 
    3. Possible need for a follow-up PR to implement improvements to OAI-PMH to support OpenAIRE v4.
  10. (warning) How to display related items on an Item page if that related item is still in workflow approval
    1. TODO: Needs proposal.  Early idea is to simply display the related item as plain text metadata (until approved).
  11. (warning) Edit Item page integration
    1. TODO: Needs proposal.  How to display relationships on "edit metadata" tab.  How to add relationships on "relationships" tab
  12. (question) Relations in AIP Backup & Restore
    1. Discussed on Oct 15
    2. Proposal:
  13. (question) Creating Relations in SAF Import (might be postponed for a future release)
    1. Requires AIP Backup & Restore
    2. Proposal:
  14. (question) SWORD integration (might be postponed for a future release)
    1. Requires AIP Backup & Restore, as SWORD uses the same crosswalks / format as AIP.
    2. Proposal:
  15. (question) 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. 
    1. Should we eventually consider hiding these Collections which only serve to store Entity Types?


  • No labels