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
from 14:00-15:00 UTC
Location: https://lyrasis.zoom.us/my/dspace (Meeting ID: 502 527 3040).
- More connection options available at DSpace Meeting Room
Beta 4 Sprint : Ongoing
- Beta 4 active development
- DSpace 7 Project Boards
- View PRs assigned to you for review/testing: https://github.com/pulls/review-requested
Agenda
(BEFORE MEETING IN #dev-sprint) Developer Stand Up - Developers give brief updates on their effort (or their team's effort).
- Update/see "Current Work" section below based on your status. Please feel free to update prior to meeting.
- Please highlight any new work (needing reviews/testing), any blockers (for you), and any discussion topics you may have.
- (25 mins) General Discussion Topics
- (15 mins) Follow-up to Submission form conceptual design:
- Last week we agreed that Submission Process should ONLY touch WorkspaceItem and WorkflowItem (per it's initial design). Therefore, we must fix/refactor any code in the Submission Process which bypasses those objects/endpoints to read from or update Item objects/endpoints.
- One known example of that improper behavior is the code merged in PR#541. One possible way to fix that behavior is documented in https://github.com/DSpace/dspace-angular/issues/818
- Questions for the team:
- Do we have (rough) estimates of the effort it would take to fix the code from PR#541 to align with the agreed upon behavior? Where should we schedule this?
- Are there any quick/small workarounds that could be applied immediately while that behavior is fixed?
- Giuseppe Digilio (4Science) provided a "quick fix" solution for his (previously blocked) Controlled Vocab PR: https://github.com/DSpace/dspace-angular/pull/751
- Do we have any timelines on fixing the other current bugs caused by PR#541?
- (10 mins) Scripts & Processes Output PR: https://github.com/DSpace/DSpace/pull/2905
- Tim has performance/scalability concerns about the Hibernate code/configuration added here to store Process output logs in the database.
- Should we rethink this approach? Or is there a way to implement with current Hibernate settings?
- (15 mins) Follow-up to Submission form conceptual design:
- (35 mins) Planning for next week
- Tim is on holiday from Aug 10-18. Do we want to cancel next week's meeting on Thursday, Aug 13? (i.e. just give updates via Slack)
- Review of our Beta 4 Project Board
Attendees
Andrea Bollini (4Science) - On holiday July 27-Aug 7
Tim Donohue - Upcoming holiday Aug 10-18
Lieven Droogmans - Upcoming holiday Aug 3 - Aug 7
- Giuseppe Digilio (4Science) - Upcoming holiday July 31-Aug 21
- Ben Bosman
- Paulo Graça - out between Aug 15-31
- Heather Greer Klein
7.0 Release Goals
These resources define the prioritization and general schedule we are working towards
- DSpace 7 Release Goals : overview of goals/timelines & beta release process
- DSpace 7 Release Plan spreadsheet: our planning spreadsheet which details which features are scheduled for each Beta release.
Current Work
Project Board
DSpace 7.0 Beta 4 Project Board: https://github.com/orgs/DSpace/projects/3
To quickly find PRs assigned to you for review, visit https://github.com/pulls/review-requested (This is also available in the GitHub header under "Pull Requests → Review Requests"
Delayed / Needs Discussion
- Finalize / approve the initial list of all authorization features which we should implement for the /api/authz/features REST endpoint. This list of features should be limited to only features which are required to enable/disable User Interface functionality. (In other words, we can always add more features in the future. We just need to approve the list necessary for 7.0)
- Review current spreadsheet (from Andrea Bollini (4Science) ) : https://docs.google.com/spreadsheets/d/1182LcD_WqIZRbUGWpLtBw0aOMR9jhbOVB7GZqtTpR9A/edit?usp=sharing
- Art Lowel (Atmire) : I don't see any immediate issues with the current set of features, but I would prefer a consistent naming scheme. I'd use canDoSomething for everything
- Tim Donohue added possible renames of these features based on Art's idea (see cell comments in spreadsheet). I like the "can[DoSomething]" naming scheme as well.
- Review current spreadsheet (from Andrea Bollini (4Science) ) : https://docs.google.com/spreadsheets/d/1182LcD_WqIZRbUGWpLtBw0aOMR9jhbOVB7GZqtTpR9A/edit?usp=sharing
- Initial Performance Testing from Chris. Needs revisiting / retesting prior to 7.0.
- https://cwilper.github.io/dspace-perftest/
- These performance tests were run prior to the work on "projections" (to limit the data returned by the REST API). Therefore, it is likely performance is much improved, but needs verification testing.
- (REST Contract) Edit Homepage News: https://github.com/DSpace/Rest7Contract/pull/45
- Delayed. General agreement (in meeting on March 21, 2019) that storing HTML in metadata fields is not really ideal behavior. Metadata (from a librarian standpoint) tends to be free of format-related markup (as that allows for easier sharing, understanding of metadata. Currently Community & Collection homepage information is HTML-based and is stored in metadata that is appropriate for a minor subset of information (like the title) but it is better to move large/rich text to bitstreams.
- Proposal here is to consider storing HTML-based markup (for Site, Community & Collection homepages) in Bitstream(s) associated with the object in question. May allow for more CMS-lite behavior in the future
- Timeline for this is uncertain. Possibly in 7 or 8. May depend on how/whether it can be scoped.