/
2022-06-01 ERM Weekly Delivery Update

2022-06-01 ERM Weekly Delivery Update

Jun 01, 2022

Meeting Details

Date

Jun 1, 2022 

Time

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

Location

Video Call in

Previously

2022-05-25 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya 

  • @Monireh Rasouli 

  • @Gill Osguthorpe 

  • @Peter Böhm 

  • @Claudia Malzer 

Apologies

  • Ethan Freestone

  • Owen Stephens

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

  • NA

 

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-2172

    • Progress / Impediments: 

      • alternateNames are being saved - attribute error is gone

    • TODO:  

      • if there is more than one alternate name, then they are joined into a single name

      • repeat for contentType

      • push branch 

    • New unknowns: 

      • concatenation issue makes no sense

        • not many examples for Groovy of xml and collect

        • could look for done in Java

    • Help or input needed: NA

    • ETA for review: 

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

    • Progress / Impediments: 

      • some issues with MultiProp in the backend work ... no test data 

      • tests written for view and edit

      • filters work begun

    • TODO:  

      • complete filters

      • continue tests

      • need to write more tests once backend is available for refData

    • New unknowns: NA

    • Help or input needed: 

      • Needs backend merging 

    • ETA for review: 

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

    • Progress / Impediments: 

      • had to make some minor changes in ui-agreements and ui-licenses because of label overrides and help popovers

        • might conflict with the work that Monireh is doing

      • Cannot move info popover to after required * 

        • GO to check screen reader behaviour 

    • TODO: 

      • view panes improvement

      • Make Type field inactive (maybe show as key value rather than option)

      • change the search box

      • Update context to category in settings

    • New unknowns: NA

    • Help or input needed:

      • will need agreements and licenses merged, as well as SKC for QA

      • Making "Type" and "Pick list" inactive rather than hiding

      • Naming conventions for category, context etc is confusing - needs some review

    • ETA for review: -

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

    • Developer on leave

 

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

  • See Next Up

Sprint Backlog -  At Risk

  • See Next Up

 

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

NA

Needs Elaboration

https://folio-org.atlassian.net/browse/ERM-2184

Sprint Backlog - Next Up

https://folio-org.atlassian.net/browse/ERM-2120

https://folio-org.atlassian.net/browse/ERM-2061

https://folio-org.atlassian.net/browse/ERM-2092

https://folio-org.atlassian.net/browse/ERM-2092

https://folio-org.atlassian.net/browse/ERM-2174

https://folio-org.atlassian.net/browse/ERM-2148

https://folio-org.atlassian.net/browse/ERM-2151

 

 

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 

Carried Over

Bugfix Cycle 

  • NA

 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

Accepted

  • NA

Carried Forward

Closed: Morning Glory R2022.2

Features

  • NA

RTL / Other Tests

  • NA

Closed (No ERM Release)

  • NA

  • <10 mins

AOB

 

New Issues

Added to sprint

  • NA

Not added to sprint

  • NA

Other

NA