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
Planning Sprint #2 / begin beta3 : May 11-15
- Finish up planning / discussions
- Begin more development on beta 3
- Review DSpace 7 Release Plan spreadsheet for beta3 and beta4 task
May 21st is a public holiday in Belgium, so the Atmire team cannot make next week's meeting. Do we consider rescheduling for Weds, May 20th? Or simply do quick updates via Slack?
Agenda
(15 mins) 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
- (10 mins) Restricted endpoints are sometimes the only HAL link path to public endpoints
- Prior the the meeting, please review/comment on the ticket:
- Some endpoints don't allow you to GET them, but do have publicly accessible child endpoints (e.g. registrations, resourcepolicies, …). To get to those child endpoints the UI can't discover them because the parent endpoint returns a 4xx status code. We should consider a way to prevent a regular response but allow retrieving the HAL links
- (15 mins) How to address the "Collection dropdown in submission" issues
- Prior to the meeting, please review/comment on the updated proposal from 4Science: Collection dropdown in submission
- somehow related to this discussion Creation of DSpace Entities
- Tabled Topics (will not be discussed unless time allows)
- 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
- (Waiting on proposal for addressing side effects from Andrea Bollini (4Science) ) Controlled Vocabularies and Authority Control in DSpace 7
- How to move forward on Controlled Vocabulary feature: https://github.com/DSpace/DSpace/pull/2743
- 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)
- (10 mins) Restricted endpoints are sometimes the only HAL link path to public endpoints
- (20 mins) Planning for next week
- Claim tasks for next week from DSpace 7 Release Plan spreadsheet
- Assigning PRs for Review
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.0beta2 milestone (highest priority)
- Open issues in 7.0beta3 milestone (second 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.0beta2 (highest priority)
- Unassigned tickets scheduled for 7.0beta3 (second 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 4) Stats reports https://github.com/DSpace/Rest7Contract/pull/125 (NEEDS REVIEWERS)
- (REST) (low priority) (beta4) Scripts & processes: importing and exporting csv's https://github.com/DSpace/DSpace/pull/2648 (Andrea Bollini (4Science) - REREVIEW, Tim Donohue - REREVIEW )
- (REST) Configurable whitelist for "Access-Control-Allow-Origin" header: https://github.com/DSpace/DSpace/pull/2735 (Ben Bosman - REREVIEW , Giuseppe Digilio (4Science) - REVIEW)
- (NEW) (REST) (beta3) DS-4042: Fix implementation and add IT for wrong PATCH request in submission: https://github.com/DSpace/DSpace/pull/2760 (NEEDS REVIEWERS)
- (NEW) (REST) (beta3) DS-4499: Fix cleanup of test environment in earlier ITs (and performance increase in ITs): https://github.com/DSpace/DSpace/pull/2759 (Tim Donohue - minor feedback added, NEEDS SECOND REVIEWER)
- (Angular) (beta 3) Edit resource policies https://github.com/DSpace/dspace-angular/pull/645 (Tim Donohue, Art Lowel (Atmire) - Feedback added, Julian Timal (eScire) )
- (Angular) (beta 3) Administer Workflow https://github.com/DSpace/dspace-angular/pull/650 ( Tim Donohue , Julian Timal (eScire) )
- (Angular) Alternative links https://github.com/DSpace/dspace-angular/pull/652 (Giuseppe Digilio (4Science) feedback added, Tim Donohue - feedback added)
- (Angular) Login as EPerson https://github.com/DSpace/dspace-angular/issues/653 (Tim Donohue -feedback added / bugs reported, Giuseppe Digilio (4Science) - REVIEW BY MAY 14 ,Julian Timal (eScire))
- (Backend) (low priority) DS-626 : Exchange usage data with IRUS https://github.com/DSpace/DSpace/pull/2664 (Craig Rosenbeck, Tim Donohue - Added feedback)
- (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) [DS-4149] porting XOAI additional indexer https://github.com/DSpace/DSpace/pull/2756 (Paulo Graça, Andrea Bollini (4Science) )
PRs Needing Updates / On Hold
- (REST Contract) (low priority) related to the scripts & processes PR above (related to PR 2648 below) https://github.com/DSpace/Rest7Contract/pull/99 (NEEDS UPDATES FROM Kevin Van de Velde (Atmire) ) (Andrea Bollini (4Science) - REVIEWED, Tim Donohue )
- (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) (beta 3) Subresources should obey access restrictions https://github.com/DSpace/DSpace/pull/2726 (NEEDS UPDATES FROM Ben Bosman ) (Tim Donohue - Added suggestions for moving forward, Andrea Bollini (4Science), Craig Rosenbeck -)
- (REST) (WAITING ON DISCUSSION, SEE Controlled Vocabularies and Authority Control in DSpace 7) (beta 3) Controlled vocabularyMykhaylo Boychuk https://github.com/DSpace/DSpace/pull/2743 (REST Contract #120) (Tim Donohue, Kevin Van de Velde (Atmire) )
- (Angular) (low priority) (beta4) Scripts & Processes Admin UI https://github.com/DSpace/dspace-angular/pull/636 ( NEEDS UPDATES FROM Art Lowel (Atmire) ) (Tim Donohue, Giuseppe Digilio (4Science), Craig Rosenbeck)
- Depends on REST PR #2648 (see above)
PRs Coming Soon
- (beta 3) REST Language Support on the backend Mykhaylo Boychuk ETA 17 or 20 April
- (PR from Kevin coming?) Support Community or Collection Admins adding/managing Community/Collection Groups. See brainstorm REST Contract PR and this early
PRs Merged this week!
- (Angular) Switch to Angular CLI https://github.com/DSpace/dspace-angular/pull/625
- (REST) (beta 3) Account profile management https://github.com/DSpace/DSpace/pull/2747
- (REST) Assume login feature https://github.com/DSpace/DSpace/pull/2740
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.