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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »


 from 14:00-15:00 UTC

Location: (Meeting ID: 502 527 3040).


  • (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. "Scripts & Processes" endpoint proposal / proof-of-concept (Continuation)
      1. Original REST Contract PR:
      2. Atmire implementation proposal (to refactor ~6 scripts initially for DSpace v7):
  • (15 mins) Planning for next week


Current Work

Legend for status icons

(blue star) = Highest Priority tasks (please prioritize these reviews/tasks over others). Currently this lists tasks/features that need to be completed for Preview Release.

(star) = Priority for OR2019 (Preview #2 Release).

(error) = review done (this week), changes were requested.

(tick) = review done, approved.

(warning) = review done, merge conflict or other minor changes requests

Tickets / PRs In Progress

  1. (Angular) Adding Accessibility via Travis CI (work in progress) (Lower priority)
  2. (warning) (Angular Bug) ( Art Lowel (Atmire) )
  3. (REST Contract) Edit Homepage news: (Ben Bosman  - has outstanding questions/comments) (Lower priority)
  4. (REST) DS-4043: Revisit the security layer of the submission  (work in progress) Andrea Bollini (4Science)
  5. (warning) (REST Contract) Group and eperson management: (Waiting on updates fromBen Bosman )
  6. (REST) Pagination bug with withdrawn items: (Dimitris Pierrakos , Ben Bosman - Feedback provided)

PRs Needing Review

  1. (REST Contract) Scripts & Processes endpoint: Updated based on feedback during the meeting
  2. (REST) Issue when community has multiple dc.title values ((tick) Tim Donohue , Andrea Bollini (4Science) - feedback provided)
  3. (REST) Oai harvesting setup (Tim Donohue - (warning) Minor improvements requested, Andrea Bollini (4Science))
  4. (REST) Spring security for createAndReturn with parent id (Tim Donohue - (warning) Minor improvements requested, NEEDS SECOND REVIEWER
  5. (NEW)(REST) Endpoints to collect statistics (Ben Bosman , Mark H. Wood )
  6. (Angular) Item-Collection Mapper: ( Tim Donohue - (warning) noted errors in testing, Art Lowel (Atmire))
  7. (Angular) Shibboleth integration support:  (Julius running into an error with 'yarn start' only) (Giuseppe Digilio (4Science) reviewed again and provided feedback will help with debugging, Fernando FCT/FCCN, Paulo Graça)
  8. (Angular) Submission Miscellaneous fixes: ((tick)Art Lowel (Atmire), Tim Donohue -  (warning)Noted performance issues)
  9. (Angular) Redirecting user to same page after login ((tick)Art Lowel (Atmire)Giuseppe Digilio (4Science)- REREVIEW)
  10. (Angular) forceBypassCache should be removed from the RequestService: (Art Lowel (Atmire) - feedback provided, Giuseppe Digilio (4Science))
  11. (Angular) Collection pages WIP: (Art Lowel (Atmire) - feedback provided, Tim Donohue)

PRs Merged this week!

  1. (seleção)(Backend) Upgrade to Solr 7:  support sharded statistics
  2. (tick) (Backend) Solr 7 fixes for upgrading to DSpace 7 
  3. (seleção)(Angular) Convert i18n files to JSON5 format 
  4. (tick) (Angular) Move Item Component:


  1. (Blocked PRs go here)

Delayed / Needs Discussion

  1. (REST) Scripts & Processes endpoint
    1. How do we move this forward? In our Jan 24 meeting, Tim noted a risk of "scope creep" with this feature suggestion. This idea has been tabled since then.
    2. In July 25 meeting, Atmire said they'd come back with notes on the proposed backend implementation.
  2. Managing Authorization info in Angular UIHow to pass Authorization rights (i.e. logged in user's access rights) from REST API to Angular?  See for example:
    1. Can this be achieved via passed HAL "_links" (e.g. the existence of an "edit" link in REST response means you must have Edit rights)?
    2. 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
      1. Also likely to need to store/cache a user's Groups in UI layer, as some areas (e.g. Administrative) require knowledge of user group membership
  3. REST API Projections:  DS-3533 - Getting issue details... STATUS
    1. Early work begun at  Discussed in more detail in our Aug 22 meeting.  Overall, this approach seems like a good direction, need volunteers to move it forward.
      1. (discussion resumed by Andrea Bollini (4Science) could be relevant for the projection)
  4. Initial Performance Testing from Chris.
  5. (REST Contract) Edit Homepage News:
    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.
  6. 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.
  7. Improve/Re-enable End To End (e2e) Testing. Could there be opportunities to use Travis CI + Docker Compose for testing of Angular??


Scripts & processes endpoint discussion:

  • Change the name of the script to the identifier
  • Add message when a task is scheduled:
  • Should we use the long or short format for the parameters? Keep the short format for now
  • What is the added value of a curation task vs performing scripts from REST:
    • Both can be executed from REST in DSpace 7
    • Curation tasks can also be scheduled during the workflow
    • Migrating current command line script to curation tasks wouldn't make much sense
    • Is there sufficient added value to keep curation tasks?
    • Continue this discussion next week when Tim is present
  • No labels