May 27, 2020 

09:30am ET, 2:30pm UK, 3:30pm Germany

Video Call in FOLIO Slack: #erm-developers

<5 mins

Introductions

• Attendees / Apologies

• Upcoming Availability

20 mins

Sprint Cutoff

Release Candidates

Code Review: NA

QA / UAT: 

• https://folio-org.atlassian.net/browse/ERM-844

  • not seeing complete set of eHoldings data 

  • Owen to provide test examples

  • FE uses underscore and ref objects differently

  • Can add missing data (eg, identifiers) to backend 

• https://folio-org.atlassian.net/browse/ERM-843

• https://folio-org.atlassian.net/browse/ERM-877

• https://folio-org.atlassian.net/browse/ERM-889

• https://folio-org.atlassian.net/browse/ERM-894 / https://folio-org.atlassian.net/browse/ERM-895

• https://folio-org.atlassian.net/browse/ERM-896 / https://folio-org.atlassian.net/browse/ERM-897

Items at Risk / Spillover

In Progress

• https://folio-org.atlassian.net/browse/ERM-681

  • to tie into existing harvest as new service

  • single thread functioning is fine

  • to work out: multithreaded behaviour

    • easiest resolution is to run two tenants

  • GOKb will need to `/packages` handling being enforced

• https://folio-org.atlassian.net/browse/ERM-510

  • still not sure how to access MDC - cannot map to existing code structure

  • potentially need to raise the log message at a different level

  • Steve to examine what could be done with the MDC part, and whether need to take alternative routes

• https://folio-org.atlassian.net/browse/ERM-788 / https://folio-org.atlassian.net/browse/ERM-791

  • currently writing tests for errata statements to support this

  • should be good to move to QA in next sprint

Sprint Backlog

• https://folio-org.atlassian.net/browse/ERM-842 

  • contingent on https://folio-org.atlassian.net/browse/ERM-788

• https://folio-org.atlassian.net/browse/ERM-893

  • Component

    • reached out to Data Import team - their component is not reusable - tightly coupled to DI

    • JC needs to add accessibility info to component before it can be standardised

    • Adi to draft components to build on

  • ERM use-case / implementation

    • queuing updates should not be done

    • tags will be sent with all required fields as part of a single endpoint

    • 'suppress from discovery' added as a flag, rather than a tag - as per user request

    • UI variation:

      • add note to UI to confirm that changes are persisted immediately

      • change 'save & close' button to 'close'

      • remove 'cancel'

Needs Elaboration

• https://folio-org.atlassian.net/browse/ERM-869

  • wireframes done - pending review

• https://folio-org.atlassian.net/browse/ERM-868

  • to `create` a TI isn't patching anymore ... cannot do this currently, can be added to errata schema later

  • sequence needs consideration

  • patch tests will help with this

15 mins

New Issues

Raised

Additional

• ERM-774 to ERM-776: Claudia to progress sibling issues

10 mins

Next Sprint

Final sprint in Goldenrod

<10 mins

AOB

Accessibility / Definition of Done

• Primer: https://github.com/folio-org/stripes-components/blob/master/docs/AccessibilityDevPrimer.md

• Definition of Done:

  • Done: developer responsibility

  • Verified by Lead Dev in code review