Page History

...

1. (REST Contract) Group and eperson management: https://github.com/DSpace/Rest7Contract/pull/41 (Tim Donohue - feedback provided,  Andrea Bollini (4Science) -  feedback provided)
2. (REST) Scripts and processes endpoint https://github.com/DSpace/DSpace/pull/2529 FEEDBACK HAS BEEN PROCESSED (Tim Donohue -  concerns about creating a lot of new Controllers, Dimitris Pierrakos) - Was reviewed by Ben Bosman internally.
3. (REST) Ds 4317 bundles in rest https://github.com/DSpace/DSpace/pull/2548 ( Ben Bosman, Tim Donohue -  concerns about creating a lot of new Controllers, Chris Wilper )
   1. Also requires an Angular branch (WIP)
4. (REST) REST Projections "proof of concept": https://github.com/DSpace/DSpace/pull/2547 (Early Reviews welcome from all.)
5. (REST) Ds 4358 tests in modules https://github.com/DSpace/DSpace/pull/2553 

   Status
   colour Blue title 1 approval

   (Tim Donohue -  dependencies need cleanup, NEEDS SECOND REVIEWER)
6. (NEW) (REST) CRUD on Collection & Community logo https://github.com/DSpace/DSpace/pull/2562 (Chris Wilper, Tim Donohue)
7. (Angular) Shibboleth integration support: https://github.com/DSpace/dspace-angular/pull/429  (Giuseppe Digilio (4Science) reviewed again fixed error with yarn start, Fernando FCT/FCCN, Paulo Graça - feedback provided)
8. (Angular) forceBypassCache should be removed from the RequestService: https://github.com/DSpace/dspace-angular/pull/468 (Art Lowel (Atmire) - approved again,  Giuseppe Digilio (4Science) )
9. (Angular) Routing by handle and uuid: https://github.com/DSpace/dspace-angular/pull/490 (Art Lowel (Atmire) - provided feedback, Giuseppe Digilio (4Science), Tim Donohue , Andrea Bollini (4Science) - might be able to help with pid endpoint)
10. (Angular) Tracking stats from the UI https://github.com/DSpace/dspace-angular/pull/495 (Tim Donohue , NEEDS SECOND REVIEWER)
11. (Angular) Refactor object lists https://github.com/DSpace/dspace-angular/pull/497 (Giuseppe Digilio (4Science), Tim Donohue)
12. (NEW) (Angular) Add community & collection tree https://github.com/DSpace/dspace-angular/pull/505 (NEEDS REVIEWERS)
13. (NEW) (Angular) i18n sync script https://github.com/DSpace/dspace-angular/pull/504 (NEEDS REVIEWERS)
14. (NEW) (Angular) Edit collection - content source tab https://github.com/DSpace/dspace-angular/pull/506 (NEEDS REVIEWERS)
15. (Backend) dspace.bat file: https://github.com/DSpace/DSpace/pull/2544 

    Status
    colour Blue title 1 approval

     (Tim Donohue, Alexander Sulfrian, Chris Wilper ) 

...

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

Andrea Bollini (4Science) has investigated on that and created the following resources/proposals: 

• REST Authorization

• https://github.com/DSpace/Rest7Contract/pull/87 

• https://github.com/4Science/Rest7Contract/pull/1

2. REST API Projections: 

1. 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.
   1. https://github.com/DSpace/Rest7Contract/issues/2 (discussion resumed by Andrea Bollini (4Science) could be relevant for the projection)

1. Initial Performance Testing from Chris.
   1. https://cwilper.github.io/dspace-perftest/
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. 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.

...