Versions Compared

Old Version 20

changes.mady.by.user Andrea Bollini (4Science)

Saved on

compared with

New Version 21

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • (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. (Topic #1) Short mention from Andrea Bollini (4Science)about the strategy to adopt to manage relations (entities) in the submission. The expectation is to enhance/update the workspaceitem endpoint as required but to don't use directly the item endpoint (i.e. /api/core/items/:uuid/relations). As soon a design document/PR/idea is ready Andrea Bollini (4Science)will be happy to provide feedback, please just ping
    2. (Topic #2) (Used time for a deeper discussion of outstanding PR)
    3. Improved Estimation Strategy for Beta release. (Estimates should include time for discussion / code reviews, also should be done by multiple developers)
      1. Development Planning Spreadsheet needs to be updated, so that we can determine what (outstanding) tasks need estimation.
      2. Will be using Wideband Delphi estimation technique
  • (15 mins) Planning for next week

...

Blocked

  1. (Blocked PRs go here)

Delayed / Needs Discussion

  1. Initial Performance Testing from Chris. Needs detailed discussion in a future meeting
  2. (REST Contract) Edit Homepage News: https://github.com/DSpace/Rest7Contract/pull/45
    1. Delayed until after Preview release. 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.
  3. (REST) Scripts & Processes endpoint: https://github.com/DSpace/Rest7Contract/pull/17
  4. 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: https://github.com/DSpace/Rest7Contract#etags--conditional-headers
    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.

Priorities for Preview Release

As discussed in previous DSpace 7 meetings, our DSpace 7 Preview release is aimed for early May, followed by a Preview #2 in May (before OR2019).  The top priorities for the Preview Release are (in this order):

  1. Submission & Workflow UI / backend 
  2. Configurable Entities (from DSpace 7 Entities Working Group)
  3. Upgrading Solr Server for DSpace (not required for Preview, as there's no user facing features. However, the earlier we feel comfortable merging this effort the better)

Priorities for OR2019 revolve around features or needs that we want to show off in Workshops/Presentations. These include

  1. Finalizing theming/branding strategy for new UI
  2. DSpace Backend as One Webapp
  3. Finalizing (as much as reasonable) the upgrade process (including Solr, Handle Server, etc)

Notes

...

  1. Not discussed much, but could there be opportunities to use Travis CI + Docker Compose for testing of Angular??

Notes