2021-03-10 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Mar 10, 2021
2 min read

Meeting Details

Date

    

Time

10:30am ET, 3:30pm UK, 4:30pm Germany

Location

Video Call in

Previously2021-03-03 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

  • Adi

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions



Previous Actions








WIP Update 

Release Candidates

Code Review: 

  • NA

QA / UAT 

  • NA

For Release

  • NA

Items at Risk / Spillover

In Progress

  • ERM-1544 - Getting issue details... STATUS
    • Ready for code review
  • ERM-1564 - Getting issue details... STATUS
    • Backend integration tests in progress
      • Should take around 30-40 minutes
    • Otherwise development done
    • Update
  • ERM-1547 - Getting issue details... STATUS
    • Need to refactor whole component to functional and then use relevant hook
    • Good examplar to model from - should only be a couple of days, but unlikely to be ready for review or QA this sprint.
    • Tricky bit may be componentDidMount - Ethan to point to alternative 
  • ERM-1580 - Getting issue details... STATUS
    • Need to abstract some of implementation to make it less massive
      • Won't be fully optimised in this iteration, but should be a good enough drag and drop model for future implementers
    • No good drag and drop test library currently available
      • Key press tests for accessibility do work
    • Aim is to develop a reusable component for any field array
    • End-to-end demo should be doable on Thursday
  • ERM-1581 - Getting issue details... STATUS
    • returned from code review to implement as a function
    • see 1537

Sprint Backlog

  • NA

Needs Elaboration

  • ERM-1540 - Getting issue details... STATUS / ERM-1541 - Getting issue details... STATUS / ERM-1542 - Getting issue details... STATUS / ERM-1543 - Getting issue details... STATUS
    • No technical architect input ... Ethan to chase
    • Q: Should vendor / primary institution be migrated?
      • Yes
    • Needs test data for migration handling

Closed


<10 minsAOB

New Issues

Added to sprint

  • ERM-1537 - Getting issue details... STATUS
    • reopened to resolve in comparable way to ERM-1581

Not added to sprint

  • NA 

Organisation Roles

Issues:  ERM-1540 - Getting issue details... STATUS / ERM-1541 - Getting issue details... STATUS / ERM-1542 - Getting issue details... STATUS / ERM-1543 - Getting issue details... STATUS

Previously

  • REQ: change current setup to support
    • multiple organisations with multiple roles for an agreement or license
    • one primary organisation per license or agreement (pattern as per contact address)
  • UNKNOWNS:
    • impact on filtering by org(s)/role(s)
    • migration
  • TASK TBC: new domain class on SubscriptionAgreement to support role-note pairs
  • Remove exclusive vendor restriction
  • PLAN:
    • Ethan: determine data model and class changes (solicit feedback from Ian/Steve)
    • Owen: add migration scenarios to issue
    • Claudia: review updated information and define work breakdown required 

Permissions

  • Some discussion about adding descriptions into package,json.
  • No technical reason not to add them. 
  • Therefore stories to follow