/
2022-09-07 ERM Weekly Delivery Update

2022-09-07 ERM Weekly Delivery Update

Sep 07, 2022

Meeting Details

Date

Sep 7, 2022 

Time

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

Location

Video Call in

Previously

2022-08-31 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya 

  • @Peter Böhm 

  • @Claudia Malzer 

  • @Ethan Freestone 

  • @Gill Osguthorpe 

  • @Owen Stephens 

Apologies

  • Monireh Rasouli

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions



Call Priorities





WIP 

  • ISSUE: 

    • Progress / Impediments: 

    • TODO: 

    • New unknowns: 

    • Help or input needed: 

    • ETA for review: 

  • 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-2288

    • Progress / Impediments: 

      • See Slack input from Steve

        • handling `pkg.save(failOnError:true)` doesn't work on its own

      • Exception happening now for contentTypes, and doesn't reach alternateResourceNames (previously only alternateResourceNames)

    • TODO: 

      • try adding `Pkg.get`

      • Restructure method into multiple methods

      • Refactor scope: only the bits for this issue

    • New unknowns: 

    • Help or input needed: continue on thread

    • ETA for review:  ?

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

    • Progress / Impediments: 

      • using subValue property

      • however, keyValue subValue text is italicised in component styling

    • TODO: add list class

    • New unknowns: NA

    • Help or input needed: NA

    • ETA for review: today

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

    • Progress / Impediments: 

      • added multiSelect control (copied from Tags)

      • multiple selection not working though

        • typo onClearFilter: resolved

    • TODO: extend tests

    • New unknowns: none

    • Help or input needed: none

    • ETA for review: today

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

    • Progress / Impediments: 

      • begun

      • needed some refactoring to enable development on it

    • TODO: all

    • New unknowns: NA

    • Help or input needed: NA

    • ETA for review: next Wed



Pending

  • ISSUE

    • Blocking conditions

    • Action needed

  • Are the blocking conditions still relevant? 

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



  • ISSUE: 

    • Who / When: 

    • ETA Ready for Dev: 

  • 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?





  • Who is picking up what next?

  • When is next issue expected to start / complete?

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

Blocked

Needs Elaboration

  • NA

Sprint Backlog - Next Up





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

Sprint Backlog -  At Risk



In Review

  • Any impediments to review or QA?

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



Code Review:

  • NA 

QA / UAT 

Bugfix Cycle 

  • NA





Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

Accepted

Closed: Nolana R2022.3

Stories / Bugs

  • NA

RTL / Tasks

  • NA

Previously

Closed (No ERM Release)

  • <10 mins

AOB



New Issues

Added to sprint

  • NA

Not added to sprint

  • NA

Other

SIG discussion: 

  • some changes expected to agreement search checkboxes that limit fields (ERM-2289)

  • Some rework expected to fall out

  • more to discuss on agreement lines next week, but for now:

    • an labels in header on agreement lines on results MCL change depending on whether hideInternalKb is set (first column is not applicable if not used)

    • does our search support searching refNo from eholdings without false positives? Owen to check, but we don't have any left anchoring support of substrings.