Meeting Details

Date	30 Mar 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-03-23 ERM Weekly Delivery Update
References	JIRA Issue Board

Goals

ERM Sprint 136

Participants

Jag Goraya

Apologies

Discussion items

Time

Item

Notes

<5 mins

Introductions

Attendees / Apologies
Upcoming Availability

Call Priorities

WIP

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-1986
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-1989
- Progress / Impediments: NA
- TODO
  - Refactoring, eg, variable names
  - Styling
  - Tests
- New unknowns: NA
- Help or input needed: NA
- ETA for review: COP Wednesday
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2045
- Progress / Impediments
  - Migrations done and working
- TODO:
  - Test via Curl
  - Add value for lifecycleStatus
  - Add array for packagDescriptionUrls
  - Add for new view for domain class
- New unknowns: NA
- Help or input needed
- ETA for review: ~~Thu am~~ Mon pm
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-1319
- Progress / Impediments
  - continue to get errors using examples from CoverageField / CoverageFieldArray
- TODO
  - any examples for existing patterns (Monireh / Claudia)
  - if not, check in #stripes or #stripes-testing for expected practice
- New unknowns
- Help or input needed
  - how to test document category select field
    - not passing as is dropdown, not checkbox/option
    - no known existing patter
  - how to test document field array field (repeatng cards container)
    - DOM error
    - attempting to mock non-existing fields (that are within document cards, not field array)
    - just need to test that cards (document fields) are rendered
  - how to test drag and drop file upload
    - don't need to test drag and drop
    - mock document to test appearance in DOM
- ETA for review
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2058
- Progress / Impediments
  - view done
  - some local environment issues
  - some translation issues: rely on localize but not a folio component
  - broke every tests in agreements (okapi/RTL):
    - stripes-erm-components fix applied to enable RTL query
    - already merged
- TODO
  - filters work near completion
  - Steve looking at localize options
  - dependency bump release
  - apply to licenses (potentially it's captured
- New unknowns: NONE
- Help or input needed
  - opening up PR for Claudia to review
- ETA for review:
  - end of Mon 28
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2044
/
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-778
- Progress / Impediments
  - all code written in stripes-kint-components
  - requires ERM-2058
- TODO:
- New unknowns
- Help or input needed
- ETA for review

Pending

Blocked

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

Needs Elaboration

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?

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 Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-1066
/
2067
- Blocking conditions
- Action needed
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-20162062
- Blocking conditions
- Action needed

Needs Elaboration

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2046
- Who / When:
  - to discuss with Martina on 30 Mar
- ETA Ready for Dev:
- Who / When: NA
- ETA Ready for Dev: Sprint 137
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-20482059
- Who / When: NA
- ETA Ready for Dev: Sprint 137

Sprint Backlog - Next Up

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

Sprint Backlog - Next Up

2048
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2068
Claudia:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-1313
- Pair on licenses for ERM-2048, ERM-778, ERM-2044
Ethan:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-1850
  ?
Monireh:
Peter:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2059
  - OAI to package schema to package ingest
  - will need adding to package schema
  - then grab from pacjage ingest

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

RTL

Sprint Backlog - At Risk

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

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

QA / UAT

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2063
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2065
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-1979778
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-
2043
- 2016
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2017
/
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2018

Bugfix Cycle

NA

Release Candidates

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

Accepted

NA

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

Closed: Lotus Hotfix 1

NA

Closed: Morning Glory R2022.2

Features

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

RTL / Other Tests

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

<10 mins

AOB

New Issues

Added to sprint

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2062
- In Triage - not seen on snapshot
- blocked by ERM-2067
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2066
- fix in stripes-connect is disproportionate to refactor with react query
- to be reviewed after others
- would want to replace separately for agreement (line)s initially to make sure it worked
  - requires untangling from existing setup
- maybe half a sprint to do properly
- medium priority for Morning Glory
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2067
- highest priority of incoming bugs
- blocked by STCOM-931
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2063
- Needs some triage
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2065

Not added to sprint

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

Other

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-1958
- changes made to PR
- pending acceptance by Orgs team

Versions Compared

Old Version 1

New Version 2

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

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

Closed: Lotus Hotfix 1

Closed: Morning Glory R2022.2

Features

RTL / Other Tests

New Issues

Added to sprint

Not added to sprint

Other

Page Comparison

Versions Compared

Old Version 1

New Version 2

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

Jira LegacyserverSystem JiraserverId01505d01-b853-3c2e-90f1-ee9b165564fckeyERM-1979 Jira LegacyserverSystem JiraserverId01505d01-b853-3c2e-90f1-ee9b165564fckeyERM-2043

Closed: Lotus Hotfix 1

Closed: Morning Glory R2022.2

Features

RTL / Other Tests

New Issues

Added to sprint

Not added to sprint

Other

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