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
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
- Revisiting Community Homepage mockups from Laura Henze. See: Community page mockups
- (Topic #2)
- 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
- (15 mins) Planning for next week
- Assigning PRs for Review
- Next tasks from Development Planning Spreadsheet
Attendees
Andrea Bollini (4Science) - On holiday, will return on Aug 8 meeting.
- Mark H. Wood
- Giuseppe Digilio (4Science)
- Ben Bosman
- Pascal-Nicolas Becker
- Chris Wilper
- Terrence W Brady
- Paulo Graça (sorry I but won't be available)
- Dimitris Pierrakos - Out of the office until Aug 19
- Julius Gruber
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) 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 for confirmation of proposed approach by Andrea Bollini (4Science) from Kevin Van de Velde (Atmire) and any other interested/available ) (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)
- (Angular) Transfer to .po message format - Initial PR: https://github.com/DSpace/dspace-angular/pull/366 (Paulo Graça , Tim Donohue , Art Lowel (Atmire) )
PRs Needing Review
- (REST Contract) Collecting statistics - https://github.com/DSpace/Rest7Contract/pull/63 (Dimitris Pierrakos, Andrea Bollini (4Science) -
changes requested, Ben Bosman )
- (REST Contract) OAI Harvesting configuration - https://github.com/DSpace/Rest7Contract/pull/66 (Paulo Graça, Tim Donohue - feedback provided)
- (REST) Item Mapper functionality: https://github.com/DSpace/DSpace/pull/2282 ( Tim Donohue - feedback provided, Ben Bosman )
- (REST) Pagination bug with withdrawn items: https://github.com/DSpace/DSpace/pull/2406 (Dimitris Pierrakos , Ben Bosman - Feedback provided)
- (Angular) (Entities) Deleting relationships: https://github.com/DSpace/dspace-angular/pull/402 (Paulo Graça - will test again, Tim Donohue )
- (Angular) Move Item Component: https://github.com/DSpace/dspace-angular/pull/335 (Giuseppe Digilio (4Science) reviewed and provided feedback, Tim Donohue )
- (Angular) Item-Collection Mapper: https://github.com/DSpace/dspace-angular/pull/348 (NEEDS REVIEWERS)
- Dependent on PR#2282 (above)
- (Angular) Shibboleth integration support (WORK IN PROGRESS): https://github.com/DSpace/dspace-angular/pull/429 (Julius has updated the PR. Ready for RE-REVIEW) (Giuseppe Digilio (4Science), Fernando FCT/FCCN, Paulo Graça )
- 4Science will enable Shibboleth on public demo.
- (Angular) Submission Miscellaneous fixes: https://github.com/DSpace/dspace-angular/pull/432 (Art Lowel (Atmire) feedback provided, Julius Gruber )
- (Angular) Replace model factories https://github.com/DSpace/dspace-angular/pull/434 (
Tim Donohue, Giuseppe Digilio (4Science))
PRs Merged this week!
(Backend) One Webapp Phase 2: Rename "dspace-spring-rest" to "dspace-server-webapp": https://github.com/DSpace/DSpace/pull/2459
(Backend) Upgrading to Handle Server v9: https://github.com/DSpace/DSpace/pull/2394
Blocked
- (Blocked PRs go here)
Delayed / Needs Discussion
- (REST) Scripts & Processes endpoint: https://github.com/DSpace/Rest7Contract/pull/17
- How do we move this forward? In our Jan 24 meeting, Tim noted a risk of "scope creep" with this feature suggestion. This idea has been tabled since then.
- In July 25 meeting, Atmire said they'd come back with notes on the proposed backend implementation.
- Managing Authorization info in Angular UI: How to pass Authorization rights (i.e. logged in user's access rights) from REST API to Angular? See for example: https://github.com/DSpace/dspace-angular/issues/393
- Can this be achieved via passed HAL "_links" (e.g. the existence of an "edit" link in REST response means you must have Edit rights)?
- In July 25 meeting, we noted this probably cannot be resolved with just one simple solution. May need to look at different options for different scenarios
- Also likely to need to store/cache a user's Groups in UI layer, as some areas (e.g. Administrative) require knowledge of user group membership
- Initial Performance Testing from Chris.
- (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.
- 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.
Not discussed much, but could there be opportunities to use 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