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 3 Sprint : June 15-26
- Working on finalizing beta3 (Goal to release at end of June or very early July)
- Review DSpace 7 Release Plan spreadsheet for beta3 and beta4 tasks
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
- (Suggest a Topic by Tuesday)
- Tabled Topics (will not be discussed this week, but possible for next week)
- 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
- Proposal from Art Lowel (Atmire)on enhancing object cache in Angular UI.
- 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)
- (35 mins) Planning for next week
- Assigning PRs for Review
- (As necessary) claim tasks for next week from DSpace 7 Release Plan spreadsheet
Attendees
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
= Highest Priority tasks (please prioritize these reviews/tasks over others).
= 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.
Claim a Ticket!
If you do not have access in JIRA or GitHub to officially claim the ticket you wish to work on, contact Tim Donohue
- Available Angular UI Tickets
- Open issues in 7.0beta3 milestone (highest priority)
- Open issues flagged as "Difficulty: low". These may be a good starting point for newer developers.
- Available REST API Tickets
- Unassigned tickets scheduled for 7.0beta3 (highest priority)
- General REST API tickets flagged as "low hanging fruit". These may be a good starting point for newer developers.
- General REST API unassigned bug tickets. Again, might be a good starting point for newer developers.
PRs Needing Review
- (REST Contract) (beta 3) related to the scripts & processes PR above (related to PR 2648 below) https://github.com/DSpace/Rest7Contract/pull/99 ( Tim Donohue -minor request before merging) (Once contact is updated Tim Donohue will rereview and merge)
- (NEW) (REST Contract) (beta 3) Refactoring Authority support / value-pairs / controlled vocabularies: https://github.com/DSpace/Rest7Contract/pull/128 (Tim Donohue will rereview, Ben Bosman )
- (NEW) (REST) (beta3) Pre authorize annotations for subresources https://github.com/DSpace/DSpace/pull/2778 ( Craig Rosenbeck , Andrea Bollini (4Science) )
- (REST) (beta3) New user registration & forgot password https://github.com/DSpace/DSpace/pull/2763 (Tim Donohue - Noted a few minor issues remaining, Andrea Bollini (4Science) REREVIEW)
- (REST) (beta3) Scripts & processes: importing and exporting csv's https://github.com/DSpace/DSpace/pull/2648 ( Tim Donohue REREVIEW after contract and merge)
- (REST) (beta3) DS-4042: Fix implementation and add IT for wrong PATCH request in submission: https://github.com/DSpace/DSpace/pull/2760 (Tim Donohue , Ben Bosman REREVIEW)
- (REST) (beta 3) CC License support: https://github.com/DSpace/DSpace/pull/2764 (Tim Donohue - Added feedback for Kevin on design issues, Craig Rosenbeck )
- (REST) (beta 3) Performance issues with finding Collections a user can submit to https://github.com/DSpace/DSpace/pull/2771 (Kevin Van de Velde (Atmire - minor feedback Tim Donohue - minor feedback - look at 4122 and make sure it has Kevin's details)
- (REST) (beta 3) DS-4486 Add support/tests for Collection/Community role-based groups for Community/Collection Admins https://github.com/DSpace/DSpace/pull/2774 (Kevin Van de Velde (Atmire) REREVIEW, Tim Donohue )
- (Angular) (beta3) Scripts & Processes Admin UI https://github.com/DSpace/dspace-angular/pull/636 (Tim Donohue, Giuseppe Digilio (4Science), Craig Rosenbeck)
- Depends on REST PR #2648 (see above)
- (Angular) Add multi-field sorting https://github.com/DSpace/dspace-angular/pull/634 1 APPROVAL (Giuseppe Digilio (4Science) feedback added, Tim Donohue - questions on how to review/test. No specs in PR)
- (Angular) New User Registration https://github.com/DSpace/dspace-angular/pull/687 (Art Lowel (Atmire) with a few UX suggestions that can move to a ticket, Giuseppe Digilio (4Science) better to test once REST PR is merged)
- Depends on REST PR #2763 (see above)
- (Angular) (beta3) Refactor registry service https://github.com/DSpace/dspace-angular/pull/697 (Tim Donohue will give quick second review, Giuseppe Digilio (4Science) REREVIEW)
- (NEW) (Angular) (beta4) Fix context sensitive menus https://github.com/DSpace/dspace-angular/pull/700 (Giuseppe Digilio (4Science) , Tim Donohue will give second review)
- (NEW) (Angular) (beta3) Fix issues with edit collection and community pages https://github.com/DSpace/dspace-angular/issues/701 (1 APPROVAL after build fix, Giuseppe Digilio (4Science) )
- (NEW) (Angular) (beta3) CC License support https://github.com/DSpace/dspace-angular/pull/703 (Giuseppe Digilio (4Science) , Tim Donohue )
- depends on REST PR #2764
- (Backend) (low priority) DS-626 : Exchange usage data with IRUS https://github.com/DSpace/DSpace/pull/2664 (Craig Rosenbeck, Tim Donohue - REREVIEW, others can take a look)
- (Backend) (low priority) (tentative 7.2) DS-4440 GDPR - Anonymize Statistics Feature: https://github.com/DSpace/DSpace/pull/2692 (Andrea Bollini (4Science), Ben Bosman, Tim Donohue)
- (Backend) (low priority) [DS-4149] porting XOAI additional indexer https://github.com/DSpace/DSpace/pull/2756 (Paulo Graça feedback added, Andrea Bollini (4Science) )
- (Backend) [DS-3940] SHERPA v2 API (master port): https://github.com/DSpace/DSpace/pull/2773 (Andrea Bollini (4Science) feedback added, Kevin Van de Velde (Atmire) feedback added)
PRs Needing Updates / On Hold
- (REST Contract) Language support on the backend (possible new cookie for Angular?) https://github.com/DSpace/Rest7Contract/pull/122 ( NEEDS UPDATES FROM Andrea Bollini (4Science) ) (Tim Donohue, Ben Bosman, Art Lowel (Atmire) )
- (REST) (WAITING ON DISCUSSION, SEE 2020-05-18 DSpace 7 Transition BTE to Live Import Mtg) (tentative 7.1) [DS-4281]: Metadata suggestions in the live import https://github.com/DSpace/DSpace/pull/2712 (Tim Donohue , Andrea Bollini (4Science))
- (REST) (WAITING ON UPDATES AFTER FINALIZING https://github.com/DSpace/Rest7Contract/pull/128) (beta 3) Controlled vocabularyMykhaylo Boychuk https://github.com/DSpace/DSpace/pull/2743 (REST Contract #120) (Tim Donohue, Kevin Van de Velde (Atmire) )
- (Angular) (WAITING ON PROPOSAL FROM Art Lowel (Atmire) FOR RESOLVING CACHING MISBEHAVIOR IN SUBMISSION UI) Alternative links https://github.com/DSpace/dspace-angular/pull/652 (Giuseppe Digilio (4Science) feedback added, Tim Donohue - feedback added)
PRs Coming Soon
- (beta 3) REST Language Support on the backend Mykhaylo Boychuk (blocked internally, it is under review by Andrea Bollini (4Science))
PRs Merged this week!
- (REST Contract) Minor Logout changes to support Logout Page https://github.com/DSpace/Rest7Contract/pull/124
- (Angular) Fix authentication issue with protected page on CSR: https://github.com/DSpace/dspace-angular/pull/702 1 APPROVAL
Blocked
- (Blocked PRs go here)
Delayed / Needs Discussion
- 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.