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:  (Meeting ID: 502 527 3040)


Actual attendee list will be updated after meeting.




Any additional topics to today's agenda?

215minsUpdates on OpenAIREv4

Any updates to discuss this week? Work based on:

Task 1

Topic #2

Topic #3

515minsWrap-up and Assigning tasks
  • Assign tasks / PRs to review (as needed)
  • Next meeting is Tues, Dec 3

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. (REST Contract) Metadata suggestions in the live import (Paulo Graça (tick) - I'm ok with the current status of this PR, Tim Donohue -  provided feedback)
  2. (REST) Delete item with relationships (Paulo Graça (tick)Alexander Sulfrian(tick) Tim Donohue )
  3. (REST) Delete item with relationships: configure defaults (Paulo GraçaAlexander SulfrianTim Donohue)
  4. (REST) Feature: external sources (Paulo Graça (tick), Tim Donohue - HIGH PRIORITY )
  5. (REST) Creating an archived item from an external source (Paulo GraçaTim Donohue)
  6. (NEW) (REST) Entities: Projects discovery configuration ((tick) Tim Donohue, MERGE IT)
  7. (NEW) (Angular) Keep virtual metadata on relationship delete (Paulo GraçaTim Donohue)
  8. (NEW) (Angular) Create relationships during the submission (Paulo GraçaTim Donohue)
  9. (OpenAIRE4) OpenAIRE 4 Entities and Relationships (Dimitris PierrakosBen Bosman (tick)Tim Donohue)
  10. (OpenAIRE4) OpenAIRE 4 required fields (Dimitris PierrakosBen Bosman - provided feedback, Tim Donohue)

PRs Merged this week!

  1. (tick) (REST) Entities: Search relationships total fix
  2. (tick) (REST) Entities bug-fixes in place management
  3. (tick) (REST Contract) Adding entry HAL Link at entryValues level

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