Meeting Details

Date	24 Aug 2022
Time	9:05am ET, 2:05pm UK, 3:05pm Germany
Location	Video Call in FOLIO Slack: #erm-developers Backup (Meet): https://meet.google.com/oei-okoc-eys
Previously	2022-08-17 ERM Weekly Delivery Update
References	JIRA Issue Board

Goals

ERM Sprint 147

Participants

Apologies

Owen Stephens
Monireh Rasouli
Gill Osguthrope

Discussion items

Time

Item

Notes

<5 mins

Introductions

Attendees / Apologies
Upcoming Availability

Call Priorities

WIP

Expand

title	In Progress

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

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2328
- Progress / Impediments: NA
- TODO:
  - Not required
  - Closed
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2306
- Progress / Impediments:
  - domain class, migrations done
- TODO:
  - run tests
- New unknowns: NA
- Help or input needed: NA
- ETA for review: End of today
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2288
- Progress / Impediments:
  - Changes requested to reduce db churn
  - started working on iteration mechanism
- TODO:
  - iterate first over the current attributes to check if included in the first
  - if not, remove each separately
  - iterate over new list being ingested, and check for attribute presence, and remove if not
  - complete as a single transaction (should already be in place, as saving at the end)
  - potentially add a compare list routine to reuse code (not expected)
- New unknowns: NA
- Help or input needed:
  - work out how to do it in Groovy with different data types
- ETA for review: Thu/Mon

Pending

Expand

title	Blocked

ISSUE
- Blocking conditions
- Action needed

Are the blocking conditions still relevant?
What action is needed to unblock, and by whom?

Expand

title	Needs Elaboration

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?

Expand

title	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

Needs Elaboration

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2314
- Who / When:
- ETA Ready for Dev:

Sprint Backlog - Next Up

Claudia:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2315
  - extend getResourceIdentifier() with a returnAll boolean parameter (stripes-erm-components)
    - use this to determine whether to return a list or single identifier
    - set to true when using on this screen
  - tweak test for getResourceIdentifier
  - update ui-agreements to apply logic
  - add tests to eResourceIdentifier to check multiple cases
  - add unique key to array list entries for react to handle correctly
  - in eResourceIdentifier,
    - assume always true
    - render list using stripes-list component
Ethan:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2313
Monireh: NA
Peter:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2311

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

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2214
- relates to translations that are coming from kint-components
- therefore related to and being handled as part of migration of kint-components (
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2316
  )

Sprint Backlog - At Risk

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2310
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2307
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2308
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2309

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

Previously
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2234
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2093
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2220
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2278
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2279
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2289
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2290
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2304
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2312

Bugfix Cycle

NA

Release Candidates

What has passed QA since last dev call?
What has been closed since last dev call?

Accepted

NA

Closed: Nolana R2022.3

Stories / Bugs

NA

RTL / Tasks

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2329
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2133
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2320
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2321
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2323
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2324
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2325
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2326
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2318
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2319

Closed (No ERM Release)

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2328

<10 mins

AOB

New Issues

Added to sprint

NA

Not added to sprint

NA

Other

mod-service-interaction and ui-dashboard will need the breaking changes from ERM-2312 to work in development environments.
ui-agreements has breaking changes from ERM-2289
- new example of a single component with two separate url routes to access
- new changes check request origin to make sure that user is returned to the correct place afterwards
Vagrant box is deprecated
- no known retirement point at this time
- should be using testing-backend
- Version: 5.0.0-20220301.7571 does work
- Latest: https://app.vagrantup.com/folio/boxes/testing-backend

Versions Compared

Old Version 6

New Version 7

Key

Meeting Details

Goals

Participants

Apologies

Discussion items

In Progress

Blocked

Needs Elaboration

Sprint Backlog - Next Up

Sprint Backlog - to follow

Code Review:

QA / UAT

Bugfix Cycle

Accepted

Closed: Nolana R2022.3

Stories / Bugs

RTL / Tasks

Closed (No ERM Release)

New Issues

Not added to sprint

Other

Page Comparison

Versions Compared

Old Version 6

New Version 7

Key

Meeting Details

Goals

Participants

Apologies

Discussion items

In Progress

Blocked

Needs Elaboration

Sprint Backlog - Next Up

Sprint Backlog - to follow

Code Review:

QA / UAT

Bugfix Cycle

Accepted

Closed: Nolana R2022.3

Stories / Bugs

RTL / Tasks

Closed (No ERM Release)

New Issues

Not added to sprint

Other