Jun 17, 2020 

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

Video Call in FOLIO Slack: #erm-developers

<5 mins

Introductions

• Attendees / Apologies

• Upcoming Availability

30 mins

WIP Updates

Code Review: 

• NA

In Progress 

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

  • patch added by Steve and tested locally

  • not getting any exception or console errors anymore

  • but still not getting data tables (Steve is getting data)

  • Peter to recreate vagrant box 

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

  • stalled because of breaking change from LAS:eR

  • can be progressed blind, but no output could be verified

  • awaiting David Klobber's confirmation that the breaking changes are rectified - expecting to resume at tail end of this sprint

  • Expected ~1 day work left when resolved, assuming no further LAS:eR complication.

  • Slack thread

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

  • identifier structures have been modified unexpectedly

  • question about whether to roll changes back or use new structure

  • Decision:

    • accept the improved changes

    • apply changes to isbn/issn only

  • Slack thread

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

  • basic plugin (similar to eresources) is working

  • however, packages need to be presented

  • what are the relevant existing filters? 

    • isPackage (hidden)

    • dataPackage(?)

  • future call points?

    • possibly when adding an agreement from AL, which would need to check across all sources

    • potentially non-packages (the inverse of the current requirement, rather specific)

    • titleInstance

  • just tests remaining

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

  • similar UI to KB Local Admin (in terms of layout and filters)

  • additional filters for package and agreement

  • filters envisaged to be simple, single-select, AND filters 

  • why wouldn't the select package not be a multi-select?

  • need to go back to the drawing board and revisit how comparison points are selected. 

  • likely to be adding abstract, growable title list array which packages could use

Sprint Backlog

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

  • TODO:

    • create comparison selection form

    • integrate backend endpoints

    • testing

  • don't need Type of job

  • Steve to set up mock branch to create dummy JSON job

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

  • fix has caused creation of 2 IDs while cloning

  • hoping to resolve today

Needs Elaboration

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

  • TBC title instance presentation

  • TBC JSON terminology for items present / not present in comparison point (using yes and no for now)

  • rowspans are not possible currently in MCL; hack would be using fixed-height; Gill considering options with Filip

• https://folio-org.atlassian.net/browse/ERM-952 / https://folio-org.atlassian.net/browse/ERM-955 / https://folio-org.atlassian.net/browse/ERM-957

QA / UAT: 

• NA

10 mins

New Issues

Raised / to bring into sprint: NA

Raised: NA

<15 mins

AOB

?