Meeting Details

Date	08 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-01 ERM Weekly Delivery Update
References	JIRA Issue Board

Goals

ERM Sprint 160

Participants

Apologies

Discussion items

Time

Item

Notes

<5 mins

Introductions

Attendees / Apologies
Upcoming Availability

Call Priorities

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2645
- Owen to test using Cypress
- Needs non-prod environment to run Cypress on against these tests
- Followup Followups:
  - https://folio-project.slack.com/archives/DF7D1AYSD/p1678266004170869
  - https://folio-project.slack.com/archives/C04SXV9D7BM/p1678278447924929

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 JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2630
- Progress / Impediments:
  - expecting some external service to use Gokb scrollAPI in chunks of 5000 packages (not content items), managing state and queue position
  - treating cursor/state as black box for now
  - should be able to use schemas/shapes mostly as-is
    - add package id to contentSchema
    - add comment t
  - will end up with 2 parallel ways to get data in
    - scheduled harvest for package ingest (current)
    - push service (this piece)
  - will need to refactor package ingest (harvest) service to separate out reusable ingest functionality
  - support either harvest or push (not both) for an ingest
  - external push service will use TIPPs to set up content items, linking them to known content rather than creating new ones
    - provides transactional redundancy
    - provides a restart point
    - reduce performance burden on agreements
  - so far:
    - 2 trivial endpoints set up under `erm/pushkb`
- TODO:
  - get endpoints accepting/logging out json input
    - started
    - not wired through okapi as shape uincertain
    - can hit locally, passsing list of packages and log them out to a package schema
    - therefore package schema is accepting this approach
    - split schema to interdependently (1) expect and (2) not expect ...
  - wire schema into ingest process
  - dig into ingest process to plan refactoring
- New unknowns:
- Help or input needed:
  - Input needed from Ian to understand legacy technical decisions around, eg, remote kb, source/ref push/pull
  - To follow up on Thursday with Ian re domain model and shape of future shape/behaviour of external service
- ETA for review:
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2612
- Progress / Impediments:
  - passed to code review
  - needs test data to be relocated to central file
- TODO:
  - Ethan to stub new Jira for multiselect and delete ERM-2612
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key ERM-2664
- New unknowns / Help or input needed: NA
- ETA for review: now

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

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2645
- OS to ask Khalilah and hosted-ref-environments

Needs Elaboration / Triage

NA

Sprint Backlog - Next Up

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

Allocations

Claudia:
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2643
Ethan:
- Release Tasks
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key ERM-2640
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key ERM-2648
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key ERM-2649
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2643
Monireh:
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2612

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:

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2633
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2612
- refdata for tests need to be removed from test resources and added to central test data file
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2624
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2625
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key SI-12
- found it requires opening in a new window
- pushed to QA

QA / UAT

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

Release Candidates

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

For Release / Pending Testrails

Closed: Poppy R2023.2

Stories / Bugs

NA

Maintenance / Tasks

NA

Release Tasks

NA

Closed: Orchid R2023.1

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

Closed: Orchid R2023.1 Bugfix

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

Closed (No ERM Release)

<10 mins

AOB

New Issues

New unexpected Proxy Settings behaviour
- If no proxy setting set, prompts for unsaved changes when navigating away
- handleCancel → onDelete → onDelete
  - needs logic to reset form if field length < 1
  - remove onDelete call from handleCancel
- However, better to rewrite away from Card to MCL
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key ERM-2793
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key ERM-2792

Added to sprint

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2647
/
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key SI-12
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-1795

Not added to sprint

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2644
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2792
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2793

Other

Owen and Gill to review potential UX consistency issues to bring into release cycle

Component Updates

NA

Release Planning

Orchid Bugfix tests to follow ERM-2643

Testing

describe permissions as part of test scenarios

Security

NA

Versions Compared

Old Version 3

New Version Current

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

NA

Closed: Orchid R2023.1

Closed: Orchid R2023.1 Bugfix

Added to sprint

Not added to sprint

Other

Component Updates

Release Planning

Testing

Security

Page Comparison

Versions Compared

Old Version 3

New Version Current

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

NA

Closed: Orchid R2023.1

Closed: Orchid R2023.1 Bugfix

Added to sprint

Not added to sprint

Other

Component Updates

Release Planning

Testing

Security