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://duraspace.zoom.us/my/dspace (Meeting ID: 502 527 3040).
- More connection options available at DSpace Meeting Room
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.
- (30 mins) General Discussion Topics
- OR2019 Planning
- Which features to complete before OR2019?
- Theming/Branding strategy, One Webapp refactor, Solr upgrade process??
- Which features to complete before OR2019?
- Improved Estimation Strategy for Beta release. (Estimates should include time for discussion / code reviews, also should be done by multiple developers)
- Development Planning Spreadsheet needs to be updated, so that we can determine what (outstanding) tasks need estimation.
- Will be using Wideband Delphi estimation technique
- OR2019 Planning
- (15 mins) Planning for next week
- Assigning PRs for Review
- Next tasks from Development Planning Spreadsheet
Attendees
Tim Donohue - ON HOLIDAY MAY 24-29
- Mark H. Wood
- Giuseppe Digilio (4Science)
- Ben Bosman
- Pascal-Nicolas Becker
- Chris Wilper
- Terrence W Brady
- Pablo Prieto
- Paulo Graça
Current Work
= Highest Priority tasks (please prioritize these reviews/tasks over others). Currently this lists tasks/features that need to be completed for Preview Release.
= Priority for OR2019 (Preview #2 Release).
= review done (this week), changes were requested.
= review done, approved.
= review done, merge conflict or other minor changes requests
Tickets / PRs In Progress
- (Angular) Adding Accessibility via Travis CI https://github.com/DSpace/dspace-angular/pull/356 (work in progress) (Lower priority)
- https://github.com/DSpace/dspace-angular/issues/368 ( Art Lowel (Atmire) ) (Angular Bug)
- (REST Contract) Edit Homepage news: https://github.com/DSpace/Rest7Contract/pull/45 (Ben Bosman - has outstanding questions/comments) (Lower priority)
- (REST) Item Mapper functionality: https://github.com/DSpace/DSpace/pull/2282 (Kevin Van de Velde (Atmire) - changes requested. Implementation doesn't align with contract) (Timeline: Should be ready a week after the entities are merged)
- (REST) DS-4043: Revisit the security layer of the submission (work in progress) Andrea Bollini (4Science)
- https://github.com/DSpace/Rest7Contract/pull/41 (Waiting on updates fromBen Bosman ) (REST Contract) Group and eperson management:
- https://github.com/DSpace/DSpace/pull/2406 (Waiting on updates from Andrea Bollini (4Science) ) (REST) Pagination issues on Items findAll -
- (Backend) DS-4257: Renaming "dspace-spring-rest" to "dspace-server" (Tim Donohue). (Timeline: Not likely to be completed until after OR2019)
PRs Needing Review
- (REST) Refactor PatchBadRequestException to DSpaceBadRequestException and fix improper 500 response errors: https://github.com/DSpace/DSpace/pull/2403 (Needs RE-REVIEW Andrea Bollini (4Science) )
(REST) DS-4210 Deposit on collection without workflow seems to fail (405 but succeed) (work in progress - Needs support on identify failure on the test env will be appreciated): https://github.com/DSpace/DSpace/pull/2429
- (REST) Updating Owning Collections: https://github.com/DSpace/DSpace/pull/2283 (NEWLY UPDATED PR)
(Angular) Transfer to .po message format - Initial PR: https://github.com/DSpace/dspace-angular/pull/366 (Paulo Graça, Tim Donohue , Art Lowel (Atmire) UPDATED. NEEDS RE-REVIEW → Preview 2)
- https://github.com/DSpace/dspace-angular/pull/401 (NEW PR) (Angular) Group entity types together:
- https://github.com/DSpace/dspace-angular/pull/402 (NEW PR) (Angular) Deleting relationships:
(Backend) Upgrading to Handle Server v9: https://github.com/DSpace/DSpace/pull/2394 (Mark H. Wood)
(Backend) Our extensive EHCache configuration is ignored: https://github.com/DSpace/DSpace/pull/2397 (Terrence W Brady )
- (Backend) Make hard-coded list of metadata registry files configurable: https://github.com/DSpace/DSpace/pull/2116 (
Tim Donohue , NEEDS SECOND REVIEWER)
- (Backend) Minor dependency updates to "master": https://github.com/DSpace/DSpace/pull/2425 (
Mark H. Wood , NEEDS SECOND REVIEWER)
PRs Merged this week!
- (Angular) Misc Preview fixes Part 2 https://github.com/DSpace/dspace-angular/pull/398 (Paulo Graça , Tim Donohue )
- (Angular) Misc Preview fixes Part 2 Themed version https://github.com/DSpace/dspace-angular/pull/399 (Paulo Graça , Tim Donohue )
- One Webapp Backend - Initial PR: https://github.com/DSpace/DSpace/pull/2265 (Backend)
BLOCKED
- (Angular) Move Item Component: https://github.com/DSpace/dspace-angular/pull/335
- Blocked by DSpace PR#2283
- (Angular) Item-Collection Mapper: https://github.com/DSpace/dspace-angular/pull/348
- Blocked by DSpace PR#2282
Delayed
- (REST Contract) Edit Homepage News: https://github.com/DSpace/Rest7Contract/pull/45
- Delayed until after Preview release. 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.
- (REST) Scripts & Processes endpoint: https://github.com/DSpace/Rest7Contract/pull/17
- Concurrency in DSpace 7 (or 8). What do we want to do when multiple editors are editing the same object? Needs further analysis regarding implementation details
- We've decided (in meeting on March 7, 2019) to use ETags to implement concurrency. REST Contract notes on ETags: https://github.com/DSpace/Rest7Contract#etags--conditional-headers
- ETags only update of the two fields match. If someone edits first, your edit would fail and you would get a fail response (422?)
- ETags seems to have broader support in other REST APIs. Recommended also by both Art and Andrea.
Priorities for Preview Release
As discussed in previous DSpace 7 meetings, our DSpace 7 Preview release is aimed for early May, followed by a Preview #2 in May (before OR2019). The top priorities for the Preview Release are (in this order):
- Submission & Workflow UI / backend
- Configurable Entities (from DSpace 7 Entities Working Group)
- Upgrading Solr Server for DSpace (not required for Preview, as there's no user facing features. However, the earlier we feel comfortable merging this effort the better)
Priorities for OR2019 revolve around features or needs that we want to show off in Workshops/Presentations. These include
- Finalizing theming/branding strategy for new UI
- DSpace Backend as One Webapp
- Finalizing (as much as reasonable) the upgrade process (including Solr, Handle Server, etc)
Notes
Travis CI + Docker Compose for testing of Angular
- Docs: https://docs.travis-ci.com/user/docker/#using-docker-compose
- Blogpost on how to do it: http://elliot.land/post/using-docker-compose-on-travis-ci
- An example travis.yml file: https://github.com/Ortus-Solutions/docker-buildfiles/blob/master/.travis.example.yml