Feb 2, 2022 

9:05am ET, 2:05pm UK, 3:05pm Germany

Video Call in

• FOLIO Slack: #erm-developers

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

2022-01-26 ERM Weekly Delivery Update

JIRA Issue Board

<5 mins

Introductions

• Attendees / Apologies

• Upcoming Availability

Call Priorities

WIP 

• What progress or impediment on previously stated actions?

• What's left to do?

• Any new unknowns?

• What help or input is needed?

• When expected to be ready for review?

In Progress

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

  • Resolved and merged

  • Ready for QA

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

  • missing new dashboard option

  • rebuilding vagrant 

  • will need to manually assign permissions

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

  • Just started

Pending

Blocked

• Are the blocking conditions still relevant? 

• What action is needed to unblock, and by whom?

Needs Elaboration

• Who needs to be involved in the elaboration process? 

• What is the timeframe for getting input?

• When is the issue expected to be ready for development?

Sprint Backlog

• Who is picking up what next?

• When is next issue expected to start / complete?

• Anything needed to start next issue (dependencies or clarifications)?

Blocked

• NA

Needs Elaboration

• NA

Sprint Backlog - Next Up

• Claudia:

• Ethan:

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

    • further requirement analysis needed by Owen

      • will need to be revisited once 1799 changes are made

    • needs ERM-1799 and backend for 1986 to be complete before 

• Monireh: 

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

• Peter:  TBD

At Risk

• What is now at risk of not being started this sprint?

• Do any of these take priority over other sprint backlog items?

Sprint Backlog - to follow

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

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

  • needs input from @Ian Ibbotson (Use this one) 

  • issue table delivered, but description effect not happening 

Sprint Backlog -  At Risk

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

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

  • comment to be added

  • looks like start and end date are double handled causing technically bad json

  • should be starightforward, but some complexity as transient

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

  • options: either strip out the code or exception handle 

  • decision: closing and dealing with by exception

In Review

• Any impediments to review or QA?

• Any useful context, implementation choices or limitations for the reviewer/tester to know ?

Code Review: 

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

  • need to still add CODEOWNERS

  • reassigned to Monireh to comment out tests and resubmit PR

QA / UAT 

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

  • now has a job to fire to backfill assign match keys

    • not intending to be used more than once

    • restricted to admin

  • likely to need more work

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

  • backend amends needed for 

  • frontend designs complete, to implement after 1800

Bugfix Cycle 

• NA

Release Candidates

• What has passed QA since last dev call?

• What has been closed since last dev call?

Accepted

New

• NA

Closed: Lotus R1 2022

Features

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

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

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

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

RTL / Other Tests

• NA

<10 mins

AOB

New Issues

Added to sprint

• NA

Not added to sprint

• NA

Other

•  NA