/
2022-08-17 ERM Weekly Delivery Update

2022-08-17 ERM Weekly Delivery Update

Aug 17, 2022

Meeting Details

Date

Aug 17, 2022 

Time

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

Location

Video Call in

Previously

2022-08-10 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya 

  • @Monireh Rasouli 

  • @Peter Böhm 

  • @Gill Osguthorpe 

  • @Claudia Malzer 

  • @Ethan Freestone 

Apologies

  • Owen Stephens

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

    • Progress / Impediments:

      • Issues with POLine filter

      • Getting errors with undefined tags

    • TODO: 

      • Fix POLine filter

    • New unknowns: NA

    • Help or input needed: 

      • Ethan to help with POLine filter

    • ETA for review: Fri/Mon

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

    • Progress / Impediments: 

      • json works

      • has test account for gokb

        • needed help from Mortiz to resolve setup issues

      • gokb package is imported, waiting for it to present to check that updates reflect in OAI feed (built-in delay)

    • TODO: 

      • Complete test for GOkb once appearing in feed

      • Review what attributes are testable for kbart

      • Test for kbart

    • New unknowns: NA

      • not sure whether test exists for kbart import?

        • no, it is called directly

    • Help or input needed: 

      • what endpoint to use for kbart? 

        • look at what the frontend consumes on snapshot, including package information

      • triggering gokb harvesting (see vagrant setup on wiki)

        1. change syncStatus to be refData idle

        2. reset cursor to 0

    • ETA for review:  Thu

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

    • Progress / Impediments: 

      • migration to new domain model should be done

      • some issues testing that (reviewing with Ian/Steve to support getting new test users)

      • outline of API 

      • update frontend to use new api

    • TODO: 

      • test functionality equivalence

      • confirm outline

      • write tests

      • major version bump

    • New unknowns: NA

    • Help or input needed: NA

    • ETA for review: 

      • 2d (Tue)

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

    • Progress / Impediments: just started

    • TODO: 

      • extend getResourceIdentifier() with a returnAll boolean parameter

      • update agreements to apply logic

      • tests

    • New unknowns: 

    • Help or input needed: 

      • how to see changes? 

        • grab all resources and count them

    • ETA for review: Thu

 

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

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

  • NA

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:

QA / UAT 

Bugfix Cycle 

  • NA

 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

Accepted

  • NA

Closed: Morning Glory R2022.2

Stories / Bugs

Closed: Morning Glory Big Fix R2022.2

Stories / Bugs

Releases

Closed: Nolana R2022.3

Stories / Bugs

  • NA

RTL / Tasks

  • NA

Closed (No ERM Release)

  • NA

  • <10 mins

AOB

 

New Issues

Added to sprint

  • NA

Not added to sprint

  • ERM–2318 to ERM-2328: stripes-erm-components should be a peer

    • will need to add as a dev-dep as well as a peer-dep

Other

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

  • Button grouping reviewed at SIG 10 Aug: https://folio-project.slack.com/archives/CAYCU07SN/p1660646280421719

    • Preference is collapsible tabs (~10d effort)

  • New issue to be raised

  • Options to do the non-collapsible alternative: routing v state

    • Routing: parameterising the tabs in the url (more effort)

      • would result in a breaking change for agreements and eresources

      • routing would need to change again if we ended up going collapsible again

    • State: or add a state, to determine which search the user is directed to.  (less effort)

      • rouing would stay flat but be presented hierarchically in the UI

      • would cause fewer problems, but is ickier

    • Overall effort 1d-2d