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

Date & Location

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


Location:

Join from PC, Mac, Linux, iOS or Android:  https://lyrasis.zoom.us/my/dspace  (Meeting ID: 502 527 3040)

Attendees

Actual attendee list will be updated after meeting.

Agenda

#TimeItemInformationWho
15mins

Agenda

Any additional topics to today's agenda?

All
225minsUpdates on OpenAIREv4

Any updates to discuss this week?

Question from last week (Nov 26):  How do we handle "relatedIdentifiers" vs "alternateIdentifiers" in our DSpace metadata?

  1. The new Schema.org identifier fields in PR#2576 seem to correspond to "alternateIdentifiers" (e.g. person.identifier.gsid is an alternative Google Scholar identifier for the Person Entity). 
    1. These fields represent (externally created) Identifiers that correspond to the Entity in DSpace. For example, if a publisher has its own DOI, then the publisher's DOI would be stored in these fields....while the DSpace-generated DOI would be stored in "dc.identifier.uri" as normal.
  2. "relatedIdentifiers" concept could be represented as new "oaire.relatedIdentifier.*" fields perhaps?  (Jose Carvalhoand Paulo Graçawill discuss and get back to us)

Discussion about entities on XOAI layer (https://github.com/DSpace/DSpace/pull/2592) The way XOAI uses Solr, we foresee that Solr will get some weight and also the "/dspace/bin/dspace oai import" method will be a little bit slower using this approach (this was negligible with our experience with DS5, but we just processed Publications, now we may also process Persons). At the moment the only possible solution that occurs is to have a configuration (perhaps on oai.cfg) to enable/disable entities. Other suggestions includes filtering by the relationship label, like: isAuthorOfPublication.

Work based on:

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

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 https://github.com/DSpace/Rest7Contract/pull/83 (Paulo Graça (tick) - I'm ok with the current status of this PR, Tim Donohue -  provided feedback)
  2. (REST) Delete item with relationships: configure defaults https://github.com/DSpace/DSpace/pull/2599 (Paulo Graça - feedback added, Alexander SulfrianTim Donohue)
  3. (REST) Creating an archived item from an external source https://github.com/DSpace/DSpace/pull/2590 (Paulo Graça  (tick) - It's Ok, but should we rely solely on the relationship.type from collection item template?, Tim Donohue)
  4. (NEW) (REST bugfix) bug update relationships https://github.com/DSpace/DSpace/pull/2610 (Paulo Graça (tick) , Tim Donohue (tick))
  5. (Angular) Keep virtual metadata on relationship delete https://github.com/DSpace/dspace-angular/pull/530 (Paulo GraçaTim Donohue)
  6. (Angular) Create relationships during the submission https://github.com/DSpace/dspace-angular/pull/531 (Paulo Graça - it's Ok, but still is WIP, Tim Donohue)
  7. (NEW) (Angular) Tabbed display of relations: https://github.com/DSpace/dspace-angular/pull/517 (Paulo Graça (tick) - shouldn't it be also available at main search?, Tim Donohue (tick)) (MERGE CONFLICTS)
  8. (NEW) (Angular) Item page entities improvements https://github.com/DSpace/dspace-angular/pull/532 (Paulo GraçaTim Donohue)
    1. sample screenshots: pr-532.pdf
  9. (NEW) (Angular) Virtual metadata on item delete https://github.com/DSpace/dspace-angular/pull/533 ( Paulo Graça , Tim Donohue )
    1. sample screenshots:  pr-533.pdf
  10. (NEW) (Angular) Reordering related entities in the submission https://github.com/DSpace/dspace-angular/pull/534 (Paulo GraçaTim Donohue)
  11. (OpenAIRE4) OpenAIRE 4 required metadata fields https://github.com/DSpace/DSpace/pull/2576 ((tick)Dimitris PierrakosBen Bosman - provided feedback, (tick) Tim Donohue)
  12. (NEW) (OpenAIRE4) OpenAIRE 4 submission forms and virtual metadata [WIP] https://github.com/DSpace/DSpace/pull/2608 (Dimitris PierrakosBen BosmanTim Donohue)
  13. (NEW) (OpenAIRE4) OpenAIRE4 oai_openaire metadata format support [WIP] https://github.com/DSpace/DSpace/pull/2592 (Dimitris PierrakosTim DonohueBen Bosman)

PRs Merged this week!

  1. (tick) (REST) Feature: external sources https://github.com/DSpace/DSpace/pull/2560
  2. (tick) (REST) Entities: Projects discovery configuration https://github.com/DSpace/DSpace/pull/2598
  3. (tick) (REST) Delete item with relationships https://github.com/DSpace/DSpace/pull/2577
  4. (tick) (OpenAIRE4) OpenAIRE 4 Entities and Relationships https://github.com/DSpace/DSpace/pull/2575

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: https://github.com/DSpace/DSpace/pull/2443 , Angular: https://github.com/DSpace/dspace-angular/pull/420
    2. Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.wjaqg235p53r
  2. (warning) (Minor refactor) Decide which metadata field should be used to store Entity Type (DS-4184).  Currently, it is stored in "relationship.type". (DEEMED LOWER PRIORITY, but "nice to have" for 7.0 if possible?)
  3. (tick) Creating Relations (between Entities) with CSV Batch Import 
    1. REST: https://github.com/DSpace/DSpace/pull/2269 and https://github.com/DSpace/DSpace/pull/2471 and https://github.com/DSpace/DSpace/pull/2522
    2. Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.df1z7jh9mcc
  4. (tick) Permissions on Relations (between Entities)
    1. Discussed on Aug 6 
    2. Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.y6qarjnylexl
  5. Deleting Entities that have existing relations
    1. (tick) Deletion action itself:
      1. REST Contract: https://github.com/DSpace/Rest7Contract/blob/master/relationships.md#deleting-a-relationship , REST: https://github.com/DSpace/DSpace/pull/2332 , Angular: https://github.com/DSpace/dspace-angular/pull/402
      2. Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.c62y8iqnvlur
    2. (warning) Copy virtual metadata from deleted entity to related entity
      1. (tick) REST Contract: https://github.com/DSpace/Rest7Contract/pull/78
      2. (tick) REST impl: https://github.com/DSpace/DSpace/pull/2577
      3. (warning) Angular Impl (in progress / under review): https://github.com/DSpace/dspace-angular/pull/530
  6. (tick) Dynamic display of Relations
    1. Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.pm34t6u1djdf
    2. (warning) Completed, but may require usability improvements (NEEDS DISCUSSION - may be delayed for v7.1)
  7. Submission Integration Tasks
    1. (tick) Creating new Entities using Submission Forms
      1. REST: https://github.com/DSpace/DSpace/pull/2443
      2. Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.9aixusqzgcnp
    2. (warning) Creating relations between two Entities during Submission process
      1. (tick) REST Contract: https://github.com/DSpace/Rest7Contract/pull/64 ,
      2. (tick) REST Impl: https://github.com/DSpace/DSpace/pull/2472
      3. (warning) Angular Impl (in progress / under review): https://github.com/DSpace/dspace-angular/pull/531
      4. Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.9aixusqzgcnp
    3. (warning) Search External Sources (includes ORCID integration with Entities)
      1. (tick) REST Contract: https://github.com/DSpace/Rest7Contract/pull/74 
      2. (tick) REST Impl: https://github.com/DSpace/DSpace/pull/2560
      3. Angular is in implementation (no PR yet)
    4. (warning) Convert External Sources to an Entity
      1. If an Admin:
        1. (tick) REST Contract: https://github.com/DSpace/Rest7Contract/pull/82
        2. (warning) REST Impl (under review): https://github.com/DSpace/DSpace/pull/2590
      2. If a Submitter (Feature is NOT specific to Entities, as this is simply porting the "Live Import" framework of DSpace 6.x)
        1. (warning) REST Contract under review: https://github.com/DSpace/Rest7Contract/pull/83
  8. Name Variants
    1. (warning) Create name variants in submission
      1. (tick) REST Impl: https://github.com/DSpace/DSpace/pull/2561
      2. (warning) Angular Impl (in progress / under review) - this is included as part of https://github.com/DSpace/dspace-angular/pull/531
    2. (tick) Display name variants on Item pages (Angular)
  9. (warning) OpenAIRE v4 support (using Entities)
    1. (tick) Configuration of Entities needed for OpenAIRE v4: https://github.com/DSpace/DSpace/pull/2575
    2. (warning) Configuration of Metadata fields/schemas needed for OpenAIRE v4 (under review): https://github.com/DSpace/DSpace/pull/2576
    3. (warning) Configuration of Submission Input Forms for OpenAIRE v4 (in implementation, no PR yet)
    4. (warning) Configuration of OAI-PMH for OpenAIRE v4 (in implementation, no PR yet)
  10. (warning) How to display related items on an Item page if that related item is still in workflow approval
    1. Early idea is to simply display the related item as plain text metadata (until workflow approval completes).
  11. (warning) Edit Item page integration
    1. How to display relationships on "edit metadata" tab in UI.  How to add relationships on "relationships" tab in UI.
    2. Angular UI Mockups discussed/approved on Nov 5 and Nov 12.
  12. (question) Relations in AIP Backup & Restore
    1. Discussed on Oct 15
    2. Proposal: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.qi8bp6kog7yi
  13. (question) Creating Relations in SAF Import (might be postponed for a future release)
    1. Requires AIP Backup & Restore
    2. Proposal: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.n8ktliibe7kj
  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: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.xufwyy1ep8h2
  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?

Notes

  • Question from last week (Nov 26):  How do we handle "relatedIdentifiers" vs "alternateIdentifiers" in our DSpace metadata?

    • The new Schema.org identifier fields in PR#2576 seem to correspond to "alternateIdentifiers" (e.g. person.identifier.gsid is an alternative Google Scholar identifier for the Person Entity). 
      • These fields represent (externally created) Identifiers that correspond to the Entity in DSpace. For example, if a publisher has its own DOI, then the publisher's DOI would be stored in these fields....while the DSpace-generated DOI would be stored in "dc.identifier.uri" as normal.
    • "relatedIdentifiers" concept could be represented as new "oaire.relatedIdentifier.*" fields perhaps?  (Jose Carvalhoand Paulo Graçawill discuss and get back to us)
    • DECISION: was to remove the identifier fields from publication and rely on `dc.identifier.*` for that entity type (for now).  Some identifiers were added to other Entities however.  See PR#2576 for updates
  • Discussion about entities on XOAI layer (https://github.com/DSpace/DSpace/pull/2592) The way XOAI uses Solr, we foresee that Solr will get some weight and also the "/dspace/bin/dspace oai import" method will be a little bit slower using this approach (this was negligible with our experience with DS5, but we just processed Publications, now we may also process Persons). At the moment the only possible solution that occurs is to have a configuration (perhaps on oai.cfg) to enable/disable entities. Other suggestions includes filtering by the relationship label, like: isAuthorOfPublication.
    • Some possible OAI-PMH performance issues noted, if we are loading large numbers of objects (e.g. all related Entities) in order to fill out the response of one Entity.
    • Possible solution: Do not  load up all related Entities...instead, just load the info available on the relationship object (i.e. a Label and the Entity ID).  This may speed up OAI-PMH requests as we'll be loading less objects.  However, it may not be exactly what the OAI harvesters expect (uncertain).
    • Could also consider precaching these responses for speed, but that may add a lot of complexity to DSpace itself.  The primary limitation here is within OAI-PMH, and this isn't a DSpace-specific issue.
  • No labels