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

Date

 from 14:00-15:00 UTC

Location: https://lyrasis.zoom.us/my/dspace (Meeting ID: 502 527 3040).

Beta 4 Sprint : Ongoing

Agenda

  • (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.
  • (20 mins) General Discussion Topics
    1. (20 mins) Follow-up to Submission form conceptual design. Review & Discuss Atmire plan
      1. On July 30, we agreed that Submission Process should ONLY touch WorkspaceItem and WorkflowItem (per it's initial design).  Therefore, we must fix/refactor any code in the Submission Process which bypasses those objects/endpoints to read from or update Item objects/endpoints. 
      2. Atmire plan (to address improper behavior of the code merged in PR#541): https://github.com/DSpace/dspace-angular/issues/818#issuecomment-669765211
      3. Other notes;
        1. Giuseppe provided a "quick fix" solution for his Controlled Vocab PR: https://github.com/DSpace/dspace-angular/pull/751
        2. The two bugs caused by PR#541 are being fixed:
          1. https://github.com/DSpace/dspace-angular/issues/816  → Fixed by Giuseppe's PR#751
          2. (tick) https://github.com/DSpace/dspace-angular/issues/817 → Fixed on main
  • (40 mins) Planning for next week

Attendees

7.0 Release Goals

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

Current Work

Project Board

DSpace 7.0 Beta 4 Project Board: https://github.com/orgs/DSpace/projects/3

To quickly find PRs assigned to you for review, visit https://github.com/pulls/review-requested  (This is also available in the GitHub header under "Pull Requests → Review Requests"

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. Initial Performance Testing from Chris.  Needs revisiting / retesting prior to 7.0. 
    1. https://cwilper.github.io/dspace-perftest/
    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.
  3. (REST Contract) Edit Homepage News: https://github.com/DSpace/Rest7Contract/pull/45
    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.

Notes

  • Follow-up to Submission form conceptual design. Review & Discuss Atmire plan
    • All generally agree with approach laid out in https://github.com/DSpace/dspace-angular/issues/818#issuecomment-669765211
    • Andrea notes that the PATCH request fields should match the response fields.  See https://github.com/DSpace/dspace-angular/issues/818#issuecomment-685994648
    • Tim adds very minor feedback.  Doesn't like the "type='plain-metadata-value'" as that's a rather long type name.  Is it possible to shorten to "type='metadatavalue'"?   Or is there a reason why we need to note this is "plain" metadata?
    • All agree this is lower priority for 7.0, as the features "work" (once Controlled Vocab PR is merged, and it's close).  So, this work is essentially a major refactor to make the relationships/entities code easier to maintain in the long run, and align it so that everything in the Submission Process goes through the WorkspaceItem and WorkflowItem.  The features will work in 7.0, but in 7.1 we'll refactor/clean them up.
    • NEXT STEPS