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 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.
- Tim Donohue - LYRASIS
- Alexander Sulfrian - Freie Universität Berlin
- Lieven Droogmans - Atmire
- Ben Bosman - Atmire
- Paulo Lopes - FCT|FCCN
- Mark H. Wood - IUPUI
- Paulo Graça- FCT|FCCN
- Jose Carvalho - University of Minho
- Dimitris Pierrakos - ARC/OpenAIRE
- Oliver Goldschmidt - Hamburg University of Technology (TUHH) (unavailable in Dec)
- Helen Baer - Colorado State University
Agenda
# | Time | Item | Information | Who |
---|---|---|---|---|
1 | 5mins | Agenda | Any additional topics to today's agenda? | All |
2 | 25mins | Updates on OpenAIREv4 | Any updates to discuss this week? Work based on:
| All |
3 | 15mins | Wrap-up and Assigning tasks |
|
Current Work
= Highest Priority tasks (please prioritize these reviews/tasks over others). These are tasks with lots of dependencies
= review done, changes were requested or bugs found.
= review done, approved.
= 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
- All JIRA tickets tagged with "Configurable Entities": https://jira.duraspace.org/issues/?jql=project%20%3D%20DS%20AND%20component%20%3D%20%22Configurable%20Entities%22
- Critical Tickets: https://jira.duraspace.org/issues?jql=project%20%3D%20DS%20AND%20priority%20%3D%20Critical%20AND%20component%20%3D%20%22Configurable%20Entities%22
- Major Tickets: https://jira.duraspace.org/issues?jql=project%20%3D%20DS%20AND%20priority%20%3D%20Major%20AND%20component%20%3D%20%22Configurable%20Entities%22
- (HIGH PRIORITY) Bug with performance of Angular (especially with regards to Entities, e.g. in PR#402): https://github.com/DSpace/dspace-angular/issues/458
(REST Contract) There could be more than one Entity reference for external sources https://github.com/DSpace/Rest7Contract/issues/90
PRs Needing Review
- (NEW) (REST Contract) Entity type small changes https://github.com/DSpace/Rest7Contract/pull/95
- (NEW) (REST) Creating a workspace item from an external source https://github.com/DSpace/DSpace/pull/2614
- (NEW) (REST) Get entity type performance improvement https://github.com/DSpace/DSpace/pull/2615 (Tim Donohue , NEEDS SECOND REVIEWER)
- (NEW) (REST) DS-4401 Enforce relational place ordering when place direction is known https://github.com/DSpace/DSpace/pull/2617#pullrequestreview-329680282 (Ben Bosman, NEEDS SECOND REVIEWER)
- (Angular) Keep virtual metadata on relationship delete https://github.com/DSpace/dspace-angular/pull/530 (Paulo Graça - feedback added, Tim Donohue - feedback added)
- (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 - early review, one bug reported)
- (Angular) Item page entities improvements https://github.com/DSpace/dspace-angular/pull/532 (Paulo Graça, Tim Donohue)
- sample screenshots: pr-532.pdf
- (Angular) Virtual metadata on item delete https://github.com/DSpace/dspace-angular/pull/533 ( Paulo Graça , Tim Donohue )
- sample screenshots: pr-533.pdf
- Dependent on #530 (see above)
- (Angular) Reordering related entities in the submission https://github.com/DSpace/dspace-angular/pull/534 (Paulo Graça, Tim Donohue)
- Dependent on #531 (see above)
- (NEW) (Angular) Lookup relations - Search external sources https://github.com/DSpace/dspace-angular/pull/539
- Dependent on #531 (see above)
- (OpenAIRE4) OpenAIRE 4 submission forms and virtual metadata https://github.com/DSpace/DSpace/pull/2608 (Dimitris Pierrakos, Ben Bosman, Tim Donohue - feedback added)
- (OpenAIRE4) OpenAIRE4 oai_openaire metadata format support [WIP] https://github.com/DSpace/DSpace/pull/2592 (Dimitris Pierrakos, Tim Donohue, Ben Bosman)
PRs Merged this week!
- (REST Contract) Metadata suggestions in the live import https://github.com/DSpace/Rest7Contract/pull/83
- (OpenAIRE4) OpenAIRE 4 required metadata fields https://github.com/DSpace/DSpace/pull/2576
- (REST bugfix) bug update relationships https://github.com/DSpace/DSpace/pull/2610
- (REST) Creating an archived item from an external source https://github.com/DSpace/DSpace/pull/2590
- (REST) Avoid setting the virtual metadata language to ANY (*) https://github.com/DSpace/DSpace/pull/2613
- (REST) Delete item with relationships: configure defaults https://github.com/DSpace/DSpace/pull/2599
- (Angular) Tabbed display of relations: https://github.com/DSpace/dspace-angular/pull/517
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.
= task considered "completed" (unless bugs or issues are later found)
= task is incomplete or has further work to be done.
= task that may be delayed or postponed for after 7.0.
- Metadata schemas for Entity types (DS-4223).
- (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?)
- Creating Relations (between Entities) with CSV Batch Import
- Permissions on Relations (between Entities)
- Discussed on Aug 6
- Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.y6qarjnylexl
- Deleting Entities that have existing relations
- Deletion action itself:
- 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
- Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.c62y8iqnvlur
- Copy virtual metadata from deleted entity to related entity
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/78
- REST impl: https://github.com/DSpace/DSpace/pull/2577
- Angular Impl (in progress / under review): https://github.com/DSpace/dspace-angular/pull/530 and https://github.com/DSpace/dspace-angular/pull/533
- Deletion action itself:
- Dynamic display of Relations
- Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.pm34t6u1djdf
- Completed, but may require usability improvements (NEEDS DISCUSSION - may be delayed for v7.1)
- Submission Integration Tasks
- Creating new Entities using Submission Forms
- Creating relations between two Entities during Submission process
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/64 ,
- REST Impl: https://github.com/DSpace/DSpace/pull/2472
- Angular Impl (in progress / under review): https://github.com/DSpace/dspace-angular/pull/531 and https://github.com/DSpace/dspace-angular/pull/534
- Early Docs / Notes: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.9aixusqzgcnp
- Search External Sources (includes ORCID integration with Entities)
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/74
- REST Impl: https://github.com/DSpace/DSpace/pull/2560
- Angular is in implementation (no PR yet)
- Convert External Sources to an Entity
- If an Admin:
- REST Contract: https://github.com/DSpace/Rest7Contract/pull/82
- REST Impl: https://github.com/DSpace/DSpace/pull/2590
- If a Submitter (Feature is NOT specific to Entities, as this is simply porting the "Live Import" framework of DSpace 6.x)
- REST Contract under review: https://github.com/DSpace/Rest7Contract/pull/83
- If an Admin:
- Name Variants
- Create name variants in submission
- REST Impl: https://github.com/DSpace/DSpace/pull/2561
- Angular Impl (in progress / under review) - this is included as part of https://github.com/DSpace/dspace-angular/pull/531
- Display name variants on Item pages (Angular)
- Create name variants in submission
- OpenAIRE v4 support (using Entities)
- Configuration of Entities needed for OpenAIRE v4: https://github.com/DSpace/DSpace/pull/2575
- Configuration of Metadata fields/schemas needed for OpenAIRE v4: https://github.com/DSpace/DSpace/pull/2576
- Configuration of Submission Input Forms for OpenAIRE v4 (under review): https://github.com/DSpace/DSpace/pull/2608
- Configuration of OAI-PMH for OpenAIRE v4 (under review): https://github.com/DSpace/DSpace/pull/2592
- How to display related items on an Item page if that related item is still in workflow approval
- Early idea is to simply display the related item as plain text metadata (until workflow approval completes).
- Edit Item page integration
- Relations in AIP Backup & Restore
- Creating Relations in SAF Import (might be postponed for a future release)
- Requires AIP Backup & Restore
- Proposal: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.n8ktliibe7kj
- SWORD integration (might be postponed for a future release)
- Requires AIP Backup & Restore, as SWORD uses the same crosswalks / format as AIP.
- Proposal: https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.xufwyy1ep8h2
- 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.
- Should we eventually consider hiding these Collections which only serve to store Entity Types?