Meeting Details

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

Goals

ERM Sprint 129

Participants

Apologies

Gill

Discussion items

Time

Item

Notes

<5 mins

Introductions

Attendees / Apologies
Upcoming Availability

Call Priorities

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1850
- no PCI or PTI entries in database (expecting ~40k)
- no errors in Local KB harvest/jobs
  - previously has taken hours longer than standard Gokb ingest
- no vagrant config changes
- looks like title ingest is succeeding (though stalled in process, so package ingest is failing)
- TODO:
  - rebuild vagrant
  - try small recordset for development: stop title ingest partially (restarting mod-agreements) and then package ingest will start automatically
- Ethan has shared stable pinned vagrant box details with Peter
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1953
- volume of lines is unknown, so not got clear data to optimise
- should follow pattern used by orders, which is to fetch up to 1000
- TODO:
  - add new fetch
  - filter new fetch based on id
  - provision fallback (show UUID) in case of fetch fail
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1938
- Jira
  server FOLIO Issue Tracker
  serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
  key ERM-1939
- Jira
  server FOLIO Issue Tracker
  serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
  key ERM-1940
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1931
- retrieval line without resource should be at the bottom of the list (because sorting by resource.name -> ref > UUID)
- could be that null is ignored, rather than treated as a sortable value
- issue is that how the sorting behaviour is unclear

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
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1940
- functionality is done
- cannot get JEST environment set up for the library -
  - not in a workspace, so not transpiling in the same way as before
  - reaching out to stripes and Steve for any pointers
- cut-off end of Friday to release code if not resolved (and to create debt task)
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1850
- assuming no further issues with recordset, aiming for code review on Thursday
- see above
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1949
/
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1950
- - changing handleResetCursor value in ExternalDataSourcesView seems to work but feels too easy
  - instead, should
    - PUT this in Route (because of stripes-connect)
    - add an onSubmit and pass to onSave
  - onSave is new to this implementation, so not used elsewhere
- Queries on issue: https://issues.folio.org/browse/ERM-1950?focusedCommentId=118462&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-118462
  - on first run (iff !lastCheck), do not permit syncStatus
  - no translations available
  - disable menu relevant options if syncStatus == idle or cursor is not set
- TODO:
  - try https://folio-project.slack.com/archives/CAYCU07SN/p1638974564161900
    - not working
  - raise draft PR for review / triage

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

NA

Needs Elaboration

NA

Sprint Backlog - Next Up

Claudia:
- TBD
Ethan:
- Jira
  server FOLIO Issue Tracker
  serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
  key ERM-1923
  /
  Jira
  server FOLIO Issue Tracker
  serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
  key ERM-1920
Monireh:
- Jira
  server FOLIO Issue Tracker
  serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
  key ERM-1953
Peter:
- Jira
  server FOLIO Issue Tracker
  serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
  key ERM-1799

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

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
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1483
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1484
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1485
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1486
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1922

QA / UAT

Aim to clear sprint without anything to carry over the holiday period

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1926
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1927
- TODO: Raise related stripes issue
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1931
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1932
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1900
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1882
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1883
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1884
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1912
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1921
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1948

Bugfix Cycle

NA

Release Candidates

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

Accepted

New

NA

Closed: Lotus R1 2022

Features

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1937

RTL / Other Tests

NA

<10 mins

AOB

New Issues

Added to sprint

NA

Not added to sprint

NA

Other

NAAim to clear sprint without anything to carry over the holiday period

Space shortcuts

Child pages

Versions Compared

Old Version 5

New Version Current

Key

Meeting Details

Goals

Participants

Apologies

Discussion items

In Progress

Blocked

Needs Elaboration

Sprint Backlog - Next Up

Sprint Backlog - to follow

Sprint Backlog - At Risk

Code Review:

QA / UAT

Bugfix Cycle

Accepted

Closed: Lotus R1 2022

Features

RTL / Other Tests

New Issues

Added to sprint

Not added to sprint

Other

Space shortcuts

Child pages

Page History

Versions Compared

Old Version 5

New Version Current

Key

Meeting Details

Goals

Participants

Apologies

Discussion items

In Progress

Blocked

Needs Elaboration

Sprint Backlog - Next Up

Sprint Backlog - to follow

Sprint Backlog - At Risk

Code Review:

QA / UAT

Bugfix Cycle

Accepted

Closed: Lotus R1 2022

Features

RTL / Other Tests

New Issues

Added to sprint

Not added to sprint

Other