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 EDT)


Location:

Join from PC, Mac, Linux, iOS or Android: https://duraspace.zoom.us/j/9963190968

Or iPhone one-tap :
US: +16468769923,,9963190968# or +16699006833,,9963190968# 
Or Telephone:
Dial(for higher quality, dial a number based on your current location): 
US: +1 646 876 9923 or +1 669 900 6833 
Meeting ID: 996 319 0968
International numbers available: https://zoom.us/u/h6HCh

Attendees

Actual attendee list will be updated after meeting.

Agenda

#TimeItemInformationWho
130minsDiscussion of survey comments and results

Questions: https://goo.gl/forms/uNmrSo7hKvtqpdFq1

Results: https://docs.google.com/spreadsheets/d/1Oo0B8qBrpFAFAi90dqbFYpG70uLfaXn0qi4dPgjXd7k/edit?usp=sharing

All
225mins

Moving towards a decision on an Entities implementation

Do we have enough information to make a decision? Is there any further information you wish to see / hear regarding either proposal?

Based on timelines, should we limit our initial use cases for DSpace 7 (as suggested by Tim via Slack)?

Resources:

  1. Comparison of the Proposals: https://docs.google.com/document/d/1I_nsgdVWwx0AdyfT8-nHNu7kUWxJh7v8EBVYkWkr6g8/edit#
    1. Proposal #1: Item Entities with bidirectional (two-way) relationships stored in a new database table: https://docs.google.com/document/d/1wEmHirFzrY3qgGtRr2YBQwGOvH1IuTVGmxDIdnqvwxM/edit?ts=5b8fe9ab#
    2. Proposal #2: Item Entities with unidirectional (one-way) relationships stored in metadata (via existing authority control framework): https://docs.google.com/document/d/16JuEL0TSq9cfxjiB77h3LQUr83N05Qd4iva7-BmYf9I/edit#heading=h.12kr45bl409y


Tim
35minsWrap-up and Next Meeting Reminder

Our Working Group will meet every other week, on Tuesday at 15:00 UTC

  • Next Meeting: Tues, Oct 23 at 15:00 UTC
Tim

Notes

All meetings will be recorded. Recordings and brief/summary notes will appear here after the meeting

  • Next steps (as decided in our meeting)
    • We will be moving forward with Proposal #1, attempting to thoroughly review/test/improve upon it, to ensure that it will meet our initial DSpace 7 Use Cases.
      • If at any time we hit a wall, or something that is not deemed acceptable, we still have time to "pivot" to a different solution (e.g. Proposal #2).  However, at this point, all discussion will move towards improving/understanding Proposal #1.
    • The codebase behind Proposal #1 will be made publicly available/accessible.  It will be moved to a (collaborative) branch under the DSpace/DSpace github repository.
      • Once it has been thoroughly reviewed and is found to meet our minimal use cases, a Pull Request from that branch will be created, so that it can be migrated into `master`
      • Tim will notify all once this move has happened.
    • The following additional organizations / individuals have promised to help chip in on improving Proposal #1 on this collaborative branch.  Others are also welcome to chip in.
    • EVERYONE: Help to fill out our use cases / user stories in: https://docs.google.com/document/d/1CJ8AkBtrY49rqn-WhYlP3kkZRVhCXGVgAIZHutJ-fas/edit
      • Any questions/concerns about the implementation should ideally be expressed as a part of one of these user stories, as it will clarify the real need/use case behind the question.

Action Items

Any assigned actions will appear here, along with details of who they are assigned to.


  • No labels

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