View Source

Date

20 Jul 2017

Angular updates

Attendees

Notes

Waffle Board: https://waffle.io/DSpace/dspace-angular
Highest priority is still getting the Angular 4 upgrade completed
- PR: https://github.com/DSpace/dspace-angular/pull/123
- Art notes that William created a separate ticket for ngrx upgrade issues: https://github.com/DSpace/dspace-angular/issues/126
- However, Art suggests that we should be looking to move from ngrx to ngrx-platform, see: https://github.com/DSpace/dspace-angular/issues/86
- It seems like the PR does not yet migrate from ngrx to ngrx-platform
- However, we don't want to hold up this PR any longer, as the Angular 4 upgrade is a blocker for other PRs
  - Recommend merging as-is (Art will give one last test and merge it)
  - Create new tickets (as needed) to describe any outstanding work. Those tickets can be claimed by whoever wants them
Planning for coming weeks
- Art wants to re-review code added just before OR2017. Some of that work was rushed and may need refactoring
- Some classes need enhanced tests (most of these still have tickets open in the "in progress" column in Waffle board)
  - Suggestion is to close those tickets that have been implemented
  - Open up a new ticket to implement the missing tests & put that ticket in "Ready" column
  - Art and others can then claim those tickets and add in missing tests little by little
- Art also wants to look at some of the old dependency tickets (e.g. https://github.com/DSpace/dspace-angular/issues/59), as some may be resolved after the Angular 4 upgrade
- Overall Goal: Finish up Browse endpoints over the next week if possible
- Search Endpoints will be next up
  - Tom Desair (Atmire) will be helping on the REST API side. He plans to propose updates to the REST Contract for next week's meeting (for all to review)
  - After approved, Tom will work to implement REST API side
  - General goal is to try and get Search implemented in time for Georgetown User Group meeting (Aug 22-23).
Andrea updated wiki with 4Science + Hasselt plans for building out deposit process and myDSpace screens:
- Submission/Workflow functionalities
- Looking for feedback on the proposed implementations
- Question: Will this include Authorization/Authentication work? Or is it hoped that someone else will tackle AuthN/Z in advance or in parallel? Obviously deposit / workflow is very dependent on AuthN/Z.
We have some new attendees. Both ask for resources on how to get more involved
Angular Resources:
- How to get involved in Angular UI work: DSpace 7 - Angular UI Development
- Overview of the technologies / links to resources: DSpace 7 UI Technology Stack
  - Also see Workshop materials from OR2017 : OR2017 DSpace Angular Workshop
- Waffle board (to claim tickets): https://waffle.io/DSpace/dspace-angular
- Please ask questions on Slack, as it helps us to enhance these materials for other new developers!

REST updates

Attendees

Terrence W Brady joined as well

Notes

Andrea was unable to attend, but sent his updates via Slack (copied in below)
- Hi all, I will miss the today meeting. The rest demo site is now aligned with the code on the master. This has been achieved merging the PR https://github.com/DSpace/DSpace/pull/1783 (there are some useful comments here about the proof of the useful of the HAL format for backward compatibility)
- The other updates are all related to the documentation, the REST contract has been updated and should now reflect what as been done and what we are working on
Art notes the discussion about how Tom Desair plans to claim work on Search REST API endpoints (see notes above in Angular discussion)
Tim notes that we need to update permissions in JIRA so that we can assign tasks to non-Committers. He'll look into opening up our permissions to allow any developer to be assigned to a ticket.
Terry notes he hopes to get involved again in coming week(s) on REST API work
For the new folks, REST API contributions work similar to Angular UI contributions
- However, REST API tickets are all in JIRA (tagged as "REST API v7"): https://jira.duraspace.org/issues/?filter=13920
We closed up the meeting early, as there were no other discussion topics / questions or comments
- Next meeting will be via Slack on Thurs, July 27 at 15:00 UTC