Page tree
Skip to end of metadata
Go to start of metadata


 from 15:00-16:00 UTC

Location: (Meeting ID: 502 527 3040).


  • (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
    1. DS-4425 - Getting issue details... STATUS
    2. (Please add a topic)
  • (15 mins) Planning for next week
    • Assigning PRs for Review


7.0 Release Goals (tentative)

The final list of tasks to complete are listed in our DSpace 7 Release Plan spreadsheet.  This spreadsheet also lists which features are scheduled for each Beta release.

Below are the very rough 7.x Release Goals. Keep in mind, these timelines may shift (backwards or forwards) based on our available developer resources and/or community volunteers.

  • 7.0 Beta 1 (goal: Feb 2020) : Security, Performance and Browse updates
  • 7.0 Beta 2 (goal: Mar 2020): Authentication / Authorization enhancements/fixes. Administrative Editing. Item Versioning.
  • 7.0 Beta 3 (goal: Apr 2020): Account Profiles, Submission/Workflow enhancements, Administrative tools
  • 7.0 Beta 4 (goal: May 2020): SEO enhancements, Theming enhancements, Batch processing, Solr-based Statistics, GDPR
  • 7.0 Beta 5 (goal: June 2020, if necessary): May be optional, pending results of prior Betas. This beta is an opportunity for general bug fixing & cleanup before the final release. Might include finishing up any unfinished features (e.g. Configurable Entities or OpenAIREv4). Might also include resolving outstanding major bugs, documentation, etc. Scope to be determined in or around April.
  • 7.0 Final release: Will be released as soon as all Betas have been completed & any outstanding bugs have been resolved.  Perhaps 1-2 months after last Beta.
  • 7.1 Release (timeline TBD): Will include all features flagged as "7.1final" in Release Plan spreadsheet which were not completed in time for 7.0
  • 7.2 Release (timeline TBD): Will include all features flagged as "7.2final" in Release Plan spreadsheet which were not completed in time for 7.1 

Current Work

Legend for status icons

(blue star) = Highest Priority tasks (please prioritize these reviews/tasks over others).

(error) = review done, changes were requested or bugs found.

(tick) = review done, approved.

(warning) = 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

PRs Needing Review

  1. (REST Contract) Group and eperson management: (Tim Donohue - feedback provided,  Andrea Bollini (4Science) - (warning) feedback provided)
  2. (REST Contract) Versioning (Andrea Bollini (4Science)Tim Donohue - REREVIEW)
  3. (NEW) (REST Contract) Support for a trail by retrieving parent objects 1 APPROVAL((tick)Tim Donohue, NEEDS SECOND REVIEWER?)
  4. (REST) DS-4389 improving patch system framework Part 1 (Andrea Bollini (4Science)Tim Donohue - REREVIEW, Michael Spalti - NEEDS FEEDBACK)
    1. Michael's version
  5. (REST) Initial Implementation of Resource Policies endpoint: (Ben Bosman - Bugs found, Tim Donohue - Bugs found,  (tick) Andrea Bollini (4Science))
  6.  (blue star) (REST) Projections continued: (Ben BosmanTim Donohue) NEEDS UPDATES
  7. (REST) Workflow step definitions - Waiting on REBASE (Ben BosmanTim Donohue Andrea Bollini (4Science) )
  8. (REST) Default webui.submit.upload.required 1 APPROVAL (Tim Donohue - REVIEW & MERGE)
  9. (REST) Scripts & processes: importing and exporting csv's (Andrea Bollini (4Science)Tim Donohue)
  10. (REST) Shibboleth authentication (Paulo Graça, Ben Bosman )
  11. (NEW) (REST) Collection item template updates NEEDS UPDATES
  12.  (blue star) (Angular) Projections continued (merge with REST PR #2625): 1 APPROVAL (Art Lowel (Atmire)Tim Donohue)
  13. (Angular) Shibboleth authentication (merge with REST PR #2651) (Paulo GraçaBen Bosman)
  14. (Angular) Verify whether file uploads are mandatory 1 APPROVAL (Giuseppe Digilio (4Science)(warning) reviewed and changes requested , Tim Donohue)
    1. Related to REST PR#2650 (above)
  15. (Angular) Generic uri metadata 1 APPROVAL (Tim Donohue - feedback added, waiting on refactor)
  16. (Backend) dspace.bat file: 1 APPROVAL (Tim Donohue - (tick) Verified on Windows. One minor change needed,  Mark H. Wood  , Alexander Sulfrian, Chris Wilper , Andrea Bollini (4Science) - (tick) verified on linux) 
  17. (NEW) (blue star) (Backend) Java 11 upgrade and Replace JMockit with Mockito: Wilper, NEEDS SECOND REVIEWER)
  18. (NEW) (Backend) URL configuration refactor (new "dspace.server.url" and "dspace.ui.url") (Paulo GraçaNEEDS SECOND REVIEWER)

PRs Merged this week!

  1. (tick) (Angular) Edit collection - content source tab
  2. (tick) (Backend) Remove support for multiple ServiceManagers:
  3. (tick) (Backend) Remove GeoIP download Ant target, reconfigure for external provision: 1 APPROVAL
  4. (tick) (Backend) [DS-4239] Migrate the workflow.xml to spring


  1. (Blocked PRs go here)

Delayed / Needs Discussion

  1. Managing Authorization info in Angular UIHow to pass Authorization rights (i.e. logged in user's access rights) from REST API to Angular?  See for example:
    1. 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
    2. Work is ongoing, but has been started in these areas:
      1. Summary of ideas: REST Authorization 
      2. Contract for Authorization Endpoints:
      3. Contract for ResourcePolicies:
  2. REST API Projections:  DS-3533 - Getting issue details... STATUS
    1. Work begun in (by Chris Wilper)
      1. Based on detail discussions in our Oct 17 meeting
    2. (Outdated) Early work begun at  Discussed in more detail in our Aug 22 meeting.  Overall, this approach seems like a good direction, need volunteers to move it forward.
    3. (discussion resumed by Andrea Bollini (4Science) could be relevant for the projection)
  3. Initial Performance Testing from Chris.
  4. (REST Contract) Edit Homepage News:
    1. 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.  
    2. 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
    3. Timeline for this is uncertain.  Possibly in 7 or 8. May depend on how/whether it can be scoped.
  5. (warning) (Angular Bug) ( Art Lowel (Atmire) )
  6. 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
    1. We've decided (in meeting on March 7, 2019) to use ETags to implement concurrency. REST Contract notes on ETags:
    2. ETags only update of the two fields match. If someone edits first, your edit would fail and you would get a fail response (422?)
    3. ETags seems to have broader support in other REST APIs.  Recommended also by both Art and Andrea.