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

Daylight Saving Time began on March 8 for parts of USA

Daylight Saving Time (DST) starts in parts of the USA on March 8, but starts in Europe on March 29.  Because DST begins on different days in different parts of the world, this meeting time will change (temporarily) for anyone who experiences DST earlier. 

The meeting will remain at 15:00-16:00 UTC through March, but this will now be one hour later for anywhere under DST.

As of April 2, once everyone is in DST, the meeting time will switch to 14:00-15:00 UTC (one hour earlier), in order to move it back into the normal timeslot for everyone.


 from 15:00-16:00 UTC

Location: (Meeting ID: 502 527 3040).

Beta 2 & 3 Sprint : March 16-27

  • Concentrated work on Beta2 tasks, and beginning 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. REMINDER: Meeting time next week will be at 14:00UTC.  This will be the same (local) time for Europeans, but one hour earlier for anyone already in daylight saving time.
    3. Language support on the REST API: is it missing in our spreedsheet? our idea is to support it via the Accept-Language Header. It is needed to provide support for any language dependent information managed on the REST side such as the submission-form, controlled-vocabulary, authorities
  • (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. (REST Contract) CC License (Andrea Bollini (4Science) - REVIEWED (error)Tim Donohue)
  3. (NEW) (REST Contract) (beta 3) New User Registration & Forgot password (Andrea Bollini (4Science)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. (blue star) (REST) Shibboleth authentication (Paulo Graça - (tick), Ben Bosman - REREVIEW)
  6. (blue star) (REST) DS-4122 Create Integration Tests to prove access restricted Communities/Collections cannot be accessed anonymously ((tick) Tim Donohue , Ben Bosman )
  7. (blue star) (REST) DS-4411 Create Integration Tests to prove newly created users have no special rights; 1 APPROVAL((tick) Tim Donohue, MERGE AFTER MEETING)
  8. (REST) (tentative 7.1) [DS-4281]: Metadata suggestions in the live import (Tim Donohue - REVIEW, Andrea Bollini (4Science) - REVIEW BY April 9 if possible)
  9. (blue star) (NEW) (REST) (beta 2) REST API should respect "metadata.hide" configurations (Tim Donohue, Andrea Bollini (4Science))
  10. (blue star) (NEW) (REST) (beta 2) Edit Community/Collection - Assign Roles/Groups (Needs help figuring out Travis error) (Tim DonohueAndrea Bollini (4Science), Ben Bosman )
  11. (blue star) (NEW) (REST) (beta 2) Group/EPerson management: Delete, retrieve parent object & patch support (Tim DonohueAndrea Bollini (4Science))
  12. (blue star) (Angular) Shibboleth authentication (merge with REST PR #2651) (Paulo Graça (tick)Ben Bosman (warning) minor comments/suggestions)
  13. (blue star) (Angular) (beta 2) Edit Item Bitstreams Tab Donohue - (warning) Minor usability issues, but mostly works great, Giuseppe Digilio (4Science) - REVIEW, Ben Bosman)
  14. (blue star) (Angular) (beta 2) Ensure workflow members can only perform actions assigned (code conflicts will be solved combined with review feedback) (Giuseppe Digilio (4Science)Tim DonohueArt Lowel (Atmire))
  15. (blue star) (Angular) (beta2) Manage Groups (Tim Donohue - (warning) Some bugs reported, but mostly works, NEEDS SECOND REVIEWER)
  16. (Angular) (beta3) Switch to Angular CLI (Tim DonohueGiuseppe Digilio (4Science))
  17. (Backend) DS-626 : Exchange usage data with IRUS (NEEDS REVIEWERS)
  18. (Backend) (tentative 7.2) DS-4440 GDPR - Anonymize Statistics Feature: (Andrea Bollini (4Science)Ben BosmanTim Donohue)
  19. (Backend / Security) Upgrade Spring Boot, Spring & Spring HATEOAS: (Andrea Bollini (4Science),  Craig Rosenbeck)
  20. (Backend) GitHub Pull Request Template:  1 APPROVAL((tick)Andrea Bollini (4Science))

PRs Coming Soon

PRs Merged this week!

  1. (tick)(REST Contract) [] Changing submitter availability
  2. (tick) (NEW) (REST Contract) [Scripts & processes] Adding "nameLong" & "mandatory" attributes
  3. (tick) (NEW) (REST Contract) [] Adding 422 for group deletes
  4. (tick) (REST Contract) Login-as using WWW-Authenticate
  5. (tick) (blue star) (REST) Read only versioning endpoints  1 APPROVAL
  6. (tick) (blue star) (REST) Initial implementation of the authorizations endpoints 
  7. (tick) (REST) [Scripts & processes] Adding mandatory / longname options to rest output 1 APPROVAL
  8. (tick) (blue star) (Angular) (beta 2) List versions - 1 APPROVAL
  9. (tick) (blue star) (Angular) (beta 2) Notice regarding the availability of new version on item pages: 1 APPROVAL


  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.