Mar 10, 2021    

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

Video Call in

• FOLIO Slack: #erm-developers

• Backup (Meet): https://meet.google.com/oei-okoc-eys

2021-03-03 ERM Weekly Delivery Update

JIRA Issue Board

<5 mins

Introductions

• Attendees / Apologies

• Upcoming Availability

Previous Actions

WIP Update 

Release Candidates

Code Review: 

• NA

QA / UAT 

• NA

For Release

• NA

Items at Risk / Spillover

In Progress

• https://folio-org.atlassian.net/browse/ERM-1544

  • Ready for code review

• https://folio-org.atlassian.net/browse/ERM-1564

  • Backend integration tests in progress

    • Should take around 30-40 minutes

  • Otherwise development done

  • Update

• https://folio-org.atlassian.net/browse/ERM-1547

  • 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 

• https://folio-org.atlassian.net/browse/ERM-1580

  • 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

• https://folio-org.atlassian.net/browse/ERM-1581

  • returned from code review to implement as a function

  • see 1537

Sprint Backlog

• NA

Needs Elaboration

• https://folio-org.atlassian.net/browse/ERM-1540 / https://folio-org.atlassian.net/browse/ERM-1541 / https://folio-org.atlassian.net/browse/ERM-1542 / https://folio-org.atlassian.net/browse/ERM-1543

  • No technical architect input ... Ethan to chase

  • Q: Should vendor / primary institution be migrated?

    • Yes

  • Needs test data for migration handling

Closed

• https://folio-org.atlassian.net/browse/ERM-1579

<10 mins

AOB

New Issues

Added to sprint

• https://folio-org.atlassian.net/browse/ERM-1537

  • reopened to resolve in comparable way to ERM-1581

Not added to sprint

• NA 

Organisation Roles

Issues: https://folio-org.atlassian.net/browse/ERM-1540 / https://folio-org.atlassian.net/browse/ERM-1541 / https://folio-org.atlassian.net/browse/ERM-1542 / https://folio-org.atlassian.net/browse/ERM-1543

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