Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

Date & Location

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


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.

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.  

Agenda

#TimeItemInformationWho
15mins

Agenda

Any additional topics to today's agenda?

All
215minWorking to finalize task list for DSpace 7 Estimation Process
  • Review our updated Task List (to be drafted by Lieven Droogmans)
    • Filter out tasks that are "out of scope" for DSpace 7 (likely in DSpace 8 or beyond)
    • Define/scope/subdivide tasks that we want to estimate for DSpace 7.0 inclusion
  • Looking for additional volunteers to help with estimation of tasks!
  • Tim to report back on whether he can be the secondary estimator on all tasks.
All
35minsMeeting time after daylight savings`

Does 15UTC still work for everyone (this will be one hour earlier after daylight saving time ends), or should we shift to 16UTC?

Tim
510minsWrap-up and Assigning tasks
  • Assign tasks / PRs to review (as needed)
  • Next meeting is Tues, Oct 29

Current Work

Tickets to Resolve

PRs Needing Review

  1. (REST Contract) Entities: Creating an archived item from an external source https://github.com/DSpace/Rest7Contract/pull/82 (Paulo Graça - feedback provided, Tim Donohue)
  2. (REST Contract) Metadata suggestions in the live import https://github.com/DSpace/Rest7Contract/pull/83 (Paulo Graça - suggests to split in 2, Tim Donohue)
  3. (REST) Ds 4224 paginated methods for relationships https://github.com/DSpace/DSpace/pull/2535 (Chris Wilper - feedback provided, Alexander Sulfrian (tick)) (CAN BE MERGED)
  4. (REST) Entities bug-fixes in place management https://github.com/DSpace/DSpace/pull/2551 (Chris Wilper, Tim Donohue, Paulo Graça) May just need one approval
  5. (NEW) (REST) Feature: external sources https://github.com/DSpace/DSpace/pull/2560 (Paulo Graça, Tim Donohue )
  6. (Angular) Item page entities changes/refactoring https://github.com/DSpace/dspace-angular/pull/475 (Paulo Graça (error) , Tim Donohue)
  7. (Angular) Name variants on item pages https://github.com/DSpace/dspace-angular/pull/496 1 APPROVAL  (Paulo Graça, Tim Donohue)

PRs Merged this week!

  1. (tick) (REST Contract) Entities support for external authority sources https://github.com/DSpace/Rest7Contract/pull/74
  2. (tick) (REST) Discovery indexing: Ensuring discovery configuration is used during indexing https://github.com/DSpace/DSpace/pull/2527

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. Submission integration (creating Entities & relations using the Item submission process) - Mockups already created by Paulo previously. - In implementation
    1. Not started yet: Adding name variants, importing from external sources
  2. Which metadata fields should be used for each Entity type. (DS-4223).  - In implementation
    1. Not done yet: A field to store the entity type. This is currently set to relationship.type
  3. Additional data for relations (essentially "metadata" or labels on relations) - Related to many other features / use cases.   - In implementation
    1. Not fully complete.
  4. Author name variants  - In implementation
    1. Not fully complete. Can estimate.
  5. 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. - In implementation
    1. Needs analysis of what is outstanding.
  6. 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. (NEEDS DISCUSSION)
  7. 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).  - Discussed on Aug 6
    1. Relates to GDPR
  8. 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. (NEEDS DISCUSSION)
  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). (Related to #15)
    1. Importing from external sources (can estimate)
  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 http://repositorium.sdum.uminho.pt/bitstream/1822/46268/1/1-s2.0-S1877050917302788.pdf 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)

  15. (REQUIRED) Deeper dive discussion into how Entities will work with Authority Control, and how ORCID integration will work (as ORCID integrates with Authority Control). Some useful resources:  Discussed in meetings on Aug 27 and Sept 17 - In implementation

Notes

  • Meeting time after daylight savings ends.  As of next week (Oct 29), we will switch this meeting to 16:00UTC.
  • Revisiting our task list. Lieven Droogmans wrote up a summary doc of what is left to do, which he walked us through
    • See entities-task-list.pdf
    • ACTION: Tim will take these notes and update the Wiki Task List
    • Additional notes on OpenAIRE v4
      • Jose & Paulo should have work to share by next week's meeting.  (Tim will add to agenda)
      • The initial PR will only  provide configuration (metadata fields, entities, etc) related to OpenAIRE v4.  They are striving to use all other Entities features as-is.
      • Goal in DSpace 7 is to provide "basic compliance" with guidelines
      • Some followup PRs may be needed to ensure OAI-PMH interface shares everything properly
  • Next week's main topic is OpenAIRE v4.  We'll also look at the updated Task List to see if there's other areas to enhance.
  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.