Meeting Details

Date	22 Mar 2023
Time	11:30am UK, 12:30pm Germany
Location	Video Call in FOLIO Slack: #erm-developers Backup (Meet): https://meet.google.com/oei-okoc-eys
Previously	2023-03-15 ERM Weekly Delivery Update
References	JIRA Issue Board

Goals

ERM Sprint 161

Participants

Apologies

Discussion items

01505d01-b853-3c2e-90f1-ee9b165564fc

Time

Item

Notes

<5 mins

Introductions

Attendees / Apologies
Upcoming Availability

Call Priorities

SI-12

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-26302886
- Progress / Impediments:
  - Packages
- TODO:
  - extend and set validation for content item schema for titles
    - validating that nested content items cannot happen
    - can then throw exception if title not present
    - then move on to ingest
    - this unlocks manual testing and regression testing
  - Tweak schema that is being used to interpret from TIPP
  - Add switch so harvest and push are exclusive
  - Apply changes for logging
- New unknowns:
  - How to do QA on this piece?
    - Won't - wait until feature is ready (so, after ERM-2631)
  - Interpret from TIPP record what is needed, as we currently do
- Help or input needed:
  - Need input on logging requirements (from Owen)
  - Developer workflow / reset environments (from Ian)
- ETA for review: ?
- QA:
  - On completion: regression test harvest
  - Roll QA for this into ERM-2631
- - pattern was not matching
  - clarified with PO
- TODO: un-draft PR
- New unknowns / Help or input needed: NA
- ETA for review: ready to go
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key SI-12
- Progress / Impediments:
  - PR raised
- TODO:
  - resolve github actions warning
  - remove slash in line 75
- New unknowns / Help or input needed:
- ETA for review: today
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-20642630
- Progress / Impediments:

just starting

New unknowns /

- - Discussed logging with Owen
  - Will follow logging for old process (so can be applied to both)
  - logging work pushing back refactoring
  - switch to decide whether harvest or pushKb is now in place, operating at service level
  - delayed by cypress calls
  - Developer workflow / reset environments (from Ian)
- TODO:
- convert to functional components
- - - some questions to take to users
      - OS to discuss with GBV
      - Martina to set up call
      - To take forward separate (out of scope) to ERM-2630
    - align new logging with existing jobs
    - followed by title ingest refactoring
    - update ERM-2631 with summary from conversation notes
  - New unknowns: NA
  - Help or input needed:
- - - Developer workflow / reset environments (from Ian)
      - further discussion needed about how to implement
      - needed for ERM-2631

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

NA

Needs Elaboration / Triage

NA

Sprint Backlog - Next Up

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-20642883
- update route to be more specific: if `erm_id`, only redirect if rendering list (ie, nothing open in third pane)
- will change existing behaviour
- returned to Owen for elaboration
- moved out of sprint
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-1026
- coming from compare.gson being pulled from backend - different approach could be refdata or strings
  - ~~refdata:~~
    - could be harder
    - if so, erm-comparisons should have a picklist editor
  - strings
    - use as translation keys
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-1061
- "Load all" button outside of MCL is not feasible
- Jump to top and jump to bottom is doable
  - stripes button type text
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-1795

Allocations

Claudia: NA
Ethan: NA
Monireh
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-1026
Monireh:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-1061
Ethan: NA

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

Removed

NA

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

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2879
- needs environment to be re-built
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2064
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2612
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2633
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2624
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2625

Release Candidates

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

For Release / Pending Testrails

Jira Legacy

server

System Jira

serverId

key

ERM-2643

Jira Legacy

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

Closed: Poppy R2023.2

Stories / Bugs

NA

Maintenance / Tasks

NA

Release Tasks

Closed: Orchid R2023.1 Bugfix

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

Release Tasks

NA

Closed (No ERM Release)

<10 mins

AOB

New Issues

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

Added to sprint

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

Not added to sprint

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

Versions Compared

Old Version 1

New Version 2

Key

Meeting Details

Goals

Participants

Apologies

Discussion items

In Progress

Blocked

Needs Elaboration / Triage

Sprint Backlog - Next Up

Allocations

Sprint Backlog - to follow

Code Review:

QA / UAT

For Release / Pending Testrails

Closed: Poppy R2023.2

Stories / Bugs

Maintenance / Tasks

Release Tasks

Closed: Orchid R2023.1 Bugfix

Release Tasks

NA

Added to sprint

Not added to sprint

Other

Component Updates

Release Planning

Testing

Security

Page Comparison

Versions Compared

Old Version 1

New Version 2

Key

Meeting Details

Goals

Participants

Apologies

Discussion items

In Progress

Blocked

Needs Elaboration / Triage

Sprint Backlog - Next Up

Allocations

Sprint Backlog - to follow

Code Review:

QA / UAT

For Release / Pending Testrails

Closed: Poppy R2023.2

Stories / Bugs

Maintenance / Tasks

Release Tasks

Closed: Orchid R2023.1 Bugfix

Release Tasks

NA

Added to sprint

Not added to sprint

Other

Component Updates

Release Planning

Testing

Security