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

Meeting time has changed to 14:00 UTC

Because of Daylight Saving Time (DST) throughout the world, we have changed the meeting time to 14:00-15:00 UTC (one hour earlier than last week).  For those just entering DST, this will be the same local time as last week.  For those who entered DST earlier in March, this means the meeting will be one hour earlier.


 from 14:00-15:00 UTC

Location: (Meeting ID: 502 527 3040).

Beta 2 Finish Sprint : March 30-April 10

  • Finish up Beta 2 tasks & release 7.0beta2
  • Additional work on Beta3 tasks


  • (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. (If needed) Discussion of Authorization for Downloads:
  • (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) related to the scripts & processes PR above (related to PR 2648 below) ((warning)NEEDS UPDATES FROM KEVIN) (Andrea Bollini (4Science) - (error) REVIEWEDTim Donohue )
  2. (NEW) (REST Contract) (beta 3) New User Registration & Forgot password (WORK STARTS NEXT WEEK) (Andrea Bollini (4Science), (tick) Tim Donohue)
  3. (NEW) (REST Contract) Remove unnecessary exception in license PATCH ((error) Andrea Bollini (4Science) NEEDS REVIEWERS, Tim Donohue)
  4. (REST) (beta4) Scripts & processes: importing and exporting csv's ((warning)WAITING ON PR UPDATES FROM KEVIN) (Andrea Bollini (4Science) - (error) REVIEWEDTim Donohue - added summary of way forward Mark H. Wood  )
  5. (REST) (tentative 7.1) [DS-4281]: Metadata suggestions in the live import (Tim Donohue - REVIEW BY April 9Andrea Bollini (4Science) - REVIEW BY April 9 if possible)
  6. (blue star) (NEW) (REST) (beta 2) REST API should respect "metadata.hide" configurations (Possibly one approval) (Tim Donohue - REREVIEW, Andrea Bollini (4Science))
  7. (blue star) (NEW) (REST) (beta 2) Edit Community/Collection - Assign Roles/Groups (Tim Donohue - REREVIEWAndrea Bollini (4Science), Ben Bosman )
  8. (blue star) (NEW) (REST) (beta 2) Group/EPerson management: Delete, retrieve parent object & patch support (NEEDS UPDATES) (Tim Donohue - early feedback added, Andrea Bollini (4Science))
  9. (blue star) (NEW) (REST) (beta 2) Subresources should obey access restrictions (Possibly one approval) (Tim Donohue  - REVIEWAndrea Bollini (4Science))
  10. (NEW) (REST) (beta 3) Administer Workflow (Abort WorkflowItem, Delete WorkflowItem) (Tim DonohueAndrea Bollini (4Science))
  11. (blue star) (Angular) (beta 2) Edit Item Bitstreams Tab (MERGE, BUT CREATE TICKET) ((tick) Tim Donohue , Giuseppe Digilio (4Science) - REVIEW, (tick) Ben Bosman)
  12. (blue star) (Angular) (beta 2) Ensure workflow members can only perform actions assigned (MERGE) (Giuseppe Digilio (4Science) - REVIEW, (tick) Tim Donohue, (tick) Art Lowel (Atmire) )
  13. (blue star) (Angular) (beta2) Manage Groups (Tim Donohue - (warning) Some bugs reported, but mostly works, Art Lowel (Atmire) , Craig Rosenbeck)
  14. (blue star) (NEW) (Angular) (beta2) Edit Community - Assign Roles/Groups (DEPENDS on PR#613 above) (Possibly one approval) (Tim DonohueArt Lowel (Atmire)
  15. (blue star) (NEW) (Angular) (beta2) Edit Collection - Assign Roles/Groups (DEPENDS on PR#613 above) (PR Coming Soon) (Tim Donohue , Art Lowel (Atmire) )
  16. (NEW) (Angular) (beta3) Scripts & Processes Admin UI (Tim DonohueGiuseppe Digilio (4Science), Craig Rosenbeck)
  17. (Angular) (EARLY beta3) Switch to Angular CLI (Tim DonohueGiuseppe Digilio (4Science))
  18. (Backend) DS-626 : Exchange usage data with IRUS (NEEDS REVIEWERS)
  19. (Backend) (tentative 7.2) DS-4440 GDPR - Anonymize Statistics Feature: (Andrea Bollini (4Science)Ben BosmanTim Donohue)
  20. (Backend / Security) (EARLY beta3) Upgrade Spring Boot, Spring & Spring HATEOAS: (Andrea Bollini (4Science),  Craig Rosenbeck)

PRs Coming Soon

  1. (blue star) (Angular) (beta2) Edit resource policies (ETA 3rd April) Giuseppe Digilio (4Science)
  2. (blue star) (REST) beta2 Authorization as someone with admin right IT (ETA 3rd April) Mykhaylo Boychuk

PRs Merged this week!

  1. (tick) (Backend) GitHub Pull Request Template:  1 APPROVAL
  2. (tick) (blue star) (REST) DS-4411 Create Integration Tests to prove newly created users have no special rights; 1 APPROVAL
  3. (tick) (REST Contract) CC License
  4. (tick) (blue star) (REST) Shibboleth authentication
  5. (tick) (blue star) (REST) DS-4122 Create Integration Tests to prove access restricted Communities/Collections cannot be accessed anonymously
  6. (tick) (REST) (bugfix) refactoring max file size
  7. (tick) (blue star) (Angular) Shibboleth authentication (merge with REST PR #2651)
  8. (tick) (blue star) (NEW) (Angular) (bugfix) Broken create community


  1. (Blocked PRs go here)

Delayed / Needs Discussion

  1. 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:
    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. Initial Performance Testing from Chris.
  3. (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.
  4. (warning) (Angular Bug) ( Art Lowel (Atmire) )
  5. 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.