Page History

...

1. (REST) Scripts & Processes endpoint: https://github.com/DSpace/Rest7Contract/pull/17
   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 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
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.

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

   • Docs: https://docs.travis-ci.com/user/docker/#using-docker-compose
   • Blogpost on how to do it: http://elliot.land/post/using-docker-compose-on-travis-ci
   • An example travis.yml file: https://github.com/Ortus-Solutions/docker-buildfiles/blob/master/.travis.example.yml

Notes

• Discussion of Community page mockups led by Laura Henze& Kate from NYU
  • Feedback still welcome on "Proposed design objectives".  These are useful in determining whether a design is successful and meets the goals
  • Mockups
    • v1 is the initial mockup.  Good feedback provided in comments
    • v2 is the initial mockup with separation of SubCommunities and Collections (as that was feedback on v1)
    • v3 is an enhanced proposal from Jose Carvalho, including more stats & download info
      • Some feedback is that the info is nice, but makes the page even larger.  Do we want to have this on a separate page or after  the subcommunity/collection listing (as much of this may be more interesting to community admins)
  • Discussion point: Do we like the sidebar here?
    • Yes, seems reasonable, but need a plan for how it collapses on smaller screens (e.g. phones)
    • Maybe we could collapse similar to Search Filters/Setting sidebar? e.g. Menu Mockups
      • Yes, possibly, though this sidebar is on the right instead of the left.  So, may need new component?
  • Discussion point: Search box for Community.  Should it be in the sidebar?
    • Art notes the initial plan was for the search icon (in site header) should eventually be clickable...and it'll expand into a search box.  We could just make that searchbox filterable to the community or collection. 
    • May want to think on whether the searchbox should be in the sidebar, or if we enhance the header search to support this option
  • Discussion point: Breadcrumbs. Currently don't exist
    • Art notes that the plan is these will exist.  Implementation ran into some initial performance issues that need resolution, but needs to exist in 7.0
  • Discussion point: New features like "Featured" sidebar listing, "Most downloads" sidebar listing, and the type-specific labels.
    • All these need more discussion and scoping.  Tim notes that we need to be careful not to expand our scope for any of these – may need to determine which are reasonable for 7.0 and which may need rescheduling
    • Type-specific labels (blue labels on Community/Collection):  Need to determine if these are based on Entity types or maybe on "dc.type".  May also be a topic of interest to DSpace 7 Entities Working Group (2018-19) eventually
    • "Featured" sidebar listing:  Nice idea, but currently doesn't exist on backend.  Not sure how to implement yet.  Noted by Laura & Kate that this might be the lowest priority of all new features
    • "Most downloads" sidebar listing: Nice idea as well, currently not in DSpace v6.  But, might be an opportunity to look at this as we implement more of statistics UI... might not be that hard to implement (needs analysis though)
  • Next steps
    • First three points are lower hanging fruit.  Can look more at how to collapse sidebar (Laura & Art had interest).  Also can reintroduce breadcrumbs discussion and searchbox ideas in upcoming meetings perhaps?
    • Other new features may need more analysis in terms of implementation strategy.  Not sure which can fit into v7 and which become v8 features
• Did not discuss Bundles in REST API.  That will move to Slack discussion, and also top of list next week
• No major updates on estimation process.  Tim looking into, but has not had much time in recent weeks.