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


 from 14:00-15:00 UTC

Location: (Meeting ID: 502 527 3040).

Beta 3 Sprint : June 15-26


  • (BEFORE MEETING IN #dev-sprint) 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
    • (15 mins) Revisit our draft Beta 3 Project Board
      • Updates from Heather Greer Klein and Tim Donohue on questions from last week
        • Any way to sync JIRA tickets and GitHub Issues? (would be necessary if we wanted to continue to use both tools for time being)
          • No way to do this easily (without paying for an expensive plugin/tool)
        • Any way to embed GitHub issue information into Confluence Wiki (in same manner as JIRA tickets)?  For example, this feature in JIRA helps auto-create our Changes in 6.x in documentation.
      • Board structure/workflow
      • Questions for the team:
        • How is this Board working for you so far?  Likes/dislikes?
        • Should we bring this to the DSpace Committers to vote on moving all DSpace 7 tickets from JIRA to GitHub Issues?
    • (15 mins) Status check on 7.0 beta 3 release by end of June or early July
      • Release possible by week of June 29?
      • Or do we need to look at week of July 6? (NOTE: Tim is on vacation July 6-10)
  • (30 mins) Planning for next week


7.0 Release Goals

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

Current 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

Project Board

DSpace 7.0 Beta 3 Project Board:

To quickly find PRs assigned to you for review, click these links

Delayed / Needs Discussion

  1. Finalize / approve the initial list of all authorization features which we should implement for the /api/authz/features REST endpoint.  This list of features should be limited to only features which are required to enable/disable User Interface functionality. (In other words, we can always add more features in the future.  We just need to approve the list necessary for 7.0)
  2. Proposal from Art Lowel (Atmire)on enhancing object cache in Angular UI.
  3. Initial Performance Testing from Chris.  Needs revisiting / retesting prior to 7.0. 
    2. These performance tests were run prior to the work on "projections" (to limit the data returned by the REST API).  Therefore, it is likely performance is much improved, but needs verification testing.
  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.