2020-03-26 DSpace 7 Working Group Meeting

Date

26 Mar 2020 from 15:00-16:00 UTC

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

• More connection options available at DSpace Meeting Room

Agenda

• (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.
• (25 mins) General Discussion Topics
  1. REMINDER: Meeting time next week will be at 14:00UTC.  This will be the same (local) time for Europeans, but one hour earlier for anyone already in daylight saving time.
  2. https://github.com/DSpace/Rest7Contract/pull/110
  3. Language support on the REST API: is it missing in our spreedsheet? our idea is to support it via the Accept-Language Header. It is needed to provide support for any language dependent information managed on the REST side such as the submission-form, controlled-vocabulary, authorities
• (20 mins) Planning for next week
  
  • Claim tasks for next week from DSpace 7 Release Plan spreadsheet
  • Assigning PRs for Review

Attendees

• Art Lowel (Atmire) 

• Andrea Bollini (4Science)  

• Tim Donohue

• Lieven Droogmans 

• Mark H. Wood
• Giuseppe Digilio (4Science) 
• Ben Bosman
• Chris Wilper
• Paulo Graça 

7.0 Release Goals

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

• DSpace 7 Release Goals : overview of goals/timelines & beta release process
• DSpace 7 Release Plan spreadsheet:  our planning spreadsheet which details which features are scheduled for each Beta release.

Current Work

Claim a Ticket!

If you do not have access in JIRA or GitHub to officially claim the ticket you wish to work on, contact Tim Donohue

• Available Angular UI Tickets
  
  • Open issues in 7.0beta2 milestone (highest priority)
  • Open issues in 7.0beta3 milestone (second highest priority)
  • Open issues flagged as "Difficulty: low".  These may be a good starting point for newer developers.
• Available REST API Tickets
  
  • Unassigned tickets scheduled for 7.0beta2 (highest priority)
  • Unassigned tickets scheduled for 7.0beta3 (second highest priority)
  • General REST API tickets flagged as "low hanging fruit".  These may be a good starting point for newer developers.
  • General REST API unassigned bug tickets.  Again, might be a good starting point for newer developers.

PRs Needing Review

1. (REST Contract) related to the scripts & processes PR above (related to PR 2648 below) https://github.com/DSpace/Rest7Contract/pull/99 (NEEDS UPDATES FROM KEVIN) (Andrea Bollini (4Science) -  REVIEWED, Tim Donohue )
2. (REST Contract) CC License https://github.com/DSpace/Rest7Contract/pull/110 (Andrea Bollini (4Science) - REVIEWED , Tim Donohue)
3. (NEW) (REST Contract) (beta 3) New User Registration & Forgot password https://github.com/DSpace/Rest7Contract/pull/117 (Andrea Bollini (4Science), Tim Donohue)
4. (REST) (beta4) Scripts & processes: importing and exporting csv's https://github.com/DSpace/DSpace/pull/2648 (WAITING ON PR UPDATES FROM KEVIN) (Andrea Bollini (4Science) -  REVIEWED, Tim Donohue - added summary of way forward Mark H. Wood  )
5.  (REST) Shibboleth authentication https://github.com/DSpace/DSpace/pull/2651 (Paulo Graça - , Ben Bosman - REREVIEW)
6.  (REST) DS-4122 Create Integration Tests to prove access restricted Communities/Collections cannot be accessed anonymously https://github.com/DSpace/DSpace/pull/2707 ( Tim Donohue , Ben Bosman )
7.  (REST) DS-4411 Create Integration Tests to prove newly created users have no special rights; https://github.com/DSpace/DSpace/pull/2716 1 APPROVAL( Tim Donohue, MERGE AFTER MEETING)
8. (REST) (tentative 7.1) [DS-4281]: Metadata suggestions in the live import https://github.com/DSpace/DSpace/pull/2712 (Tim Donohue - REVIEW, Andrea Bollini (4Science) - REVIEW BY April 9 if possible)
9.  (NEW) (REST) (beta 2) REST API should respect "metadata.hide" configurations https://github.com/DSpace/DSpace/pull/2719 (Tim Donohue, Andrea Bollini (4Science))
10.  (NEW) (REST) (beta 2) Edit Community/Collection - Assign Roles/Groups https://github.com/DSpace/DSpace/pull/2722 (Needs help figuring out Travis error) (Tim Donohue, Andrea Bollini (4Science), Ben Bosman )
11.  (NEW) (REST) (beta 2) Group/EPerson management: Delete, retrieve parent object & patch support https://github.com/DSpace/DSpace/pull/2723 (Tim Donohue, Andrea Bollini (4Science))
12.  (Angular) Shibboleth authentication (merge with REST PR #2651) https://github.com/DSpace/dspace-angular/pull/568 (Paulo Graça , Ben Bosman  minor comments/suggestions)
13.  (Angular) (beta 2) Edit Item Bitstreams Tab  https://github.com/DSpace/dspace-angular/pull/577(Tim Donohue -  Minor usability issues, but mostly works great, Giuseppe Digilio (4Science) - REVIEW, Ben Bosman)
14.  (Angular) (beta 2) Ensure workflow members can only perform actions assigned  https://github.com/DSpace/dspace-angular/pull/608 (code conflicts will be solved combined with review feedback) (Giuseppe Digilio (4Science), Tim Donohue, Art Lowel (Atmire))
15.  (Angular) (beta2) Manage Groups https://github.com/DSpace/dspace-angular/pull/613 (Tim Donohue -  Some bugs reported, but mostly works, NEEDS SECOND REVIEWER)
16. (Angular) (beta3) Switch to Angular CLI https://github.com/DSpace/dspace-angular/pull/625 (Tim Donohue, Giuseppe Digilio (4Science))
17. (Backend) DS-626 : Exchange usage data with IRUS https://github.com/DSpace/DSpace/pull/2664 (NEEDS REVIEWERS)
    
18. (Backend) (tentative 7.2) DS-4440 GDPR - Anonymize Statistics Feature: https://github.com/DSpace/DSpace/pull/2692 (Andrea Bollini (4Science), Ben Bosman, Tim Donohue)
19. (Backend / Security) Upgrade Spring Boot, Spring & Spring HATEOAS: https://github.com/DSpace/DSpace/pull/2720 (Andrea Bollini (4Science),  Craig Rosenbeck)
20. (Backend) GitHub Pull Request Template: https://github.com/DSpace/DSpace/pull/2721  1 APPROVAL(Andrea Bollini (4Science))

PRs Coming Soon

PRs Merged this week!

1. (REST Contract) [version.md] Changing submitter availability https://github.com/DSpace/Rest7Contract/pull/112
2.  (NEW) (REST Contract) [Scripts & processes] Adding "nameLong" & "mandatory" attributes https://github.com/DSpace/Rest7Contract/pull/114
3.  (NEW) (REST Contract) [epersongroups.md] Adding 422 for group deletes https://github.com/DSpace/Rest7Contract/pull/115
4.  (REST Contract) Login-as using WWW-Authenticate https://github.com/DSpace/Rest7Contract/pull/109
5.   (REST) Read only versioning endpoints https://github.com/DSpace/DSpace/pull/2680  1 APPROVAL
6.   (REST) Initial implementation of the authorizations endpoints https://github.com/DSpace/DSpace/pull/2663 
7.  (REST) [Scripts & processes] Adding mandatory / longname options to rest output https://github.com/DSpace/DSpace/pull/2715 1 APPROVAL
8.   (Angular) (beta 2) List versions - https://github.com/DSpace/dspace-angular/pull/585 1 APPROVAL
9.   (Angular) (beta 2) Notice regarding the availability of new version on item pages: https://github.com/DSpace/dspace-angular/pull/595 1 APPROVAL

Blocked

1. (Blocked PRs go here)

Delayed / Needs Discussion

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. 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
   2. Work is ongoing, but has been started in these areas:
      1. Summary of ideas: REST Authorization 
      2. Contract for Authorization Endpoints: https://github.com/DSpace/Rest7Contract/pull/92
      3. Contract for ResourcePolicies: https://github.com/DSpace/Rest7Contract/pull/87
2. Initial Performance Testing from Chris.
   1. https://cwilper.github.io/dspace-perftest/
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.
4.  (Angular Bug) https://github.com/DSpace/dspace-angular/issues/368 ( Art Lowel (Atmire) )
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