Versions Compared

Old Version 38

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 39

changes.mady.by.user Tim Donohue

Saved on

Key

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

...

  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: https://github.com/DSpace/dspace-angular/issues/393
    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
      2. Andrea Bollini (4Science) has investigated on that and created the following resources/proposals: 
      3. REST Authorization
      4. https://github.com/DSpace/Rest7Contract/pull/87 
      5. https://github.com/4Science/Rest7Contract/pull/1
  2. REST API Projections: 
    Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyDS-3533
    1. Work begun in https://github.com/DSpace/DSpace/pull/2547 (by Chris Wilper)
      1. Based on detail discussions in our Oct 17 meeting. 
    2. (Outdated) Early work begun at https://github.com/DSpace/DSpace/pull/1847.  Discussed in more detail in our Aug 22 meeting.  Overall, this approach seems like a good direction, need volunteers to move it forward.
    3. https://github.com/DSpace/Rest7Contract/issues/2 (discussion resumed by Andrea Bollini (4Science) could be relevant for the projection)
  3. Initial Performance Testing from Chris.
    1. https://cwilper.github.io/dspace-perftest/
  4. (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.
  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: 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.

Notes

  • Discussion of  7.0 Release Schedule from Leadership & Steering
    • As of last Weds (Nov 27), Leadership approved a tentative release schedule.  However, it's based on the assumption of 4FTE developers, and Leadership is now looking to secure funding to ensure we can guarantee development at that effort for the next 6months (roughly speaking that's when 7.0 may be out, but only if we have 4FTEs starting on Jan 1)
      • Leadership & Steering will be looking to align paid development resources to help with these Beta sprints (to help ensure we have consistent development resources).  That said, volunteer-based development will continue to be welcome, as it will help us move even faster.  More info will be coming.
    • Working to ramp down DSpace 7 Entities Working Group by Jan 1.  Seems likely that most of the Entities / OpenAIRE work (if not all) will be completed or "in code review" by end of December anyhow.
      • Andrea Bollini (4Science) noted that this don't seem inline with the direction of a managed schedule of dspace 7 where Entities eventually are in lowest priority for DSpace 7.  He notes that speedup this work in December mean subtract time to other task in higher priority and require other to review work not in the immediate todo list or give up to other. He point out to a coming PR that seems too large to be reviewed properly: https://github.com/DSpace/dspace-angular/pull/531
      • Tim noted that this one PR (#531) is not representative of the normal development process of the Entities WG. Agrees it's a large PR that will take more effort to review.  All other PRs out of Entities WG are much smaller (generally in 1-2K range, as we've previously strived for)
      • Tim noted that this ramp down idea was also mentioned in Leadership Group meeting on Weds.  There were no questions or concerns expressed, so Tim is moving this forward
      • As of Jan 1, the Entities Group will shut down regardless of whether work is completed.  If it's completed, great.  If not, then any still open PRs will need to be addressed at a later time (depending on available volunteers, as all paid developers will be concentrating on higher priority tasks as of Jan 1)
      • Tim also notes that obviously he cannot control exactly where volunteers choose to put their effort. That is why Leadership & Steering is looking for paid developer resources – those developers we can require to work on specific tasks (in order to get paid).  However, there will always be the ability for volunteers to choose other tasks to work on – even if those tasks are lower on the priority list...but, that said, low priority PRs will also be low priority to code review/merge.
    • As of Jan 1, we'll be one working group (this one).  Working Group will start to work more in a "sprint-like" fashion.
    • Goal is to work together to release a new updated "beta" per month (starting in Feb).  These Betas will be layering on new features each month, until we hit 7.0 Final.  Releases will be simple (like was done for "7.0 Preview") – just cut a tag, and push release via Docker. (I.e. this will NOT be a full Maven release process, as these Betas are simply for early community testing & feedback.)
      • Tim will post more info on each "Beta" soon (by next week).  First Beta though will concentrate more on updating our dependencies – getting REST API on latest Java & Spring Boot, getting UI on latest Angular.