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


 from 15:00-16:00 UTC

Location: (Meeting ID: 502 527 3040).

Beta 1 & 2 Sprint : Feb 3-14

  • Work towards finalizing the Beta1 tasks in DSpace 7 Release Plan spreadsheet.  Goal is to have Beta1 released in mid-to-late Feb.
  • Beginning work on Beta2 tasks (especially those with many dependencies)


  • (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
    1. Revisiting Scripts & Processes endpoint PR#2648: Tim has concerns about usage of Bitstreams for temporary files (like uploaded CSVs, SAF Zips, AIPs, etc)
      1. See also last week's discussion notes
    2. (Please add a topic)
  • (20 mins) Planning for next week


7.0 Release Goals

These resources define the prioritization and general schedule we are working towards

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: ( (tick) Tim Donohue ,  Andrea Bollini (4Science) - REREVIEW BY FEB 13)
  2. MERGE (REST) DS-4389 improving patch system framework Part 1 (Andrea Bollini (4Science) - REVIEW (if possible) BY FEB 13, (tick) Tim Donohue, (tick) Michael Spalti )
    1. Michael's version
  3.  (blue star) MERGE FIRST (REST) Projections continued: ( (tick) Ben Bosman , (tick) Tim Donohue )
  4. (NEW) (REST) Select specific embeds (depends on PR#2625): (Tim DonohueBen Bosman)
  5. (REST) Workflow step definitions  (Ben Bosman - REREVIEW, Tim Donohue - REREVIEW, Andrea Bollini (4Science) - REREVIEW)
  6. (REST) Scripts & processes: importing and exporting csv's (Andrea Bollini (4Science) - REVIEW BY FEB 20Tim Donohue - REVIEW Comments, Mark H. Wood  )
  7. (REST) Shibboleth authentication (Paulo Graça, Ben Bosman )
  8. MERGE (REST) Collection item template updates 1 APPROVAL ((tick)Tim Donohue)
  9. (NEW) (REST) Edit Item - Manage Bitstreams 1 APPROVAL (Tim Donohue)
  10. (Angular) Shibboleth authentication (merge with REST PR #2651) (Paulo GraçaBen Bosman)
  11. (NEW) (Angular) (beta 2) Edit Item Bitstreams Tab (depends on #578) (Tim DonohueGiuseppe Digilio (4Science))
  12.  (blue star) (NEW) (Angular) (beta 1) Only resolve links when needed (Performance improvement work) (Tim DonohueGiuseppe Digilio (4Science))
  13.  (blue star) (NEW) (Angular) (beta 1) Angular 8 Upgrade (Tim DonohueGiuseppe Digilio (4Science))
  14.  (blue star) (Backend) Java 11 upgrade and Replace JMockit with Mockito (MERGE on/around Feb 13): ((tick)Chris Wilper, NEEDS SECOND REVIEWER)
    1. Corresponding Angular PR (must be merged after PR#2654 and below PR#2657):
  15. (Backend) URL configuration refactor (new "dspace.server.url" and "dspace.ui.url") (MERGE on/around Feb 13 (Paulo Graça - (tick)Mark H. Wood - (tick) )
  16. (NEW) (Backend) Fix errorprone test warnings after Java 11 upgrade (depends on PR#2654): 1 APPROVAL (Mark H. Wood)
  17. (NEW) DS-4428 missing parameter exception 1 APPROVAL (Tim Donohue)
  18. (NEW) DS-4418 remove uuid from resource policy rest (Tim Donohue) (Possibly one approval)

PRs Merged this week!

  1. (tick) (REST Contract) Clarify anonymous access to resourcepolicies endpoints 1 APPROVAL
  2. (tick) (REST Contract) Versioning
  3. (tick) (REST) Initial Implementation of Resource Policies endpoint: 
  4. (tick) (Angular) Generic uri metadata 1 APPROVAL


  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.