Jan 15, 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

QA / UAT

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

In Progress 

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

  • Moved to code review, and merged

  • "there's amendments.js but this wasn't working before my changes"

    • no issue is logged for that

    • tests are there but not working

    • tests don't run as part of PR process, need to be run locally

  • also, functionality to add documents not working

    • fixed locally

  • TODO: open new branches and Jira issues for both

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

  • merged, awaiting backend

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

  • about to enter code review

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

• https://folio-org.atlassian.net/browse/UXPROD-2081

  • Backend: fields added

  • UI

    • front end designs: to be defined / written

    • also to combine coverage data

  • Rules

    • expecting to make progress today

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

  • package contents element complete

  • moving on to lkb info/error logs

Needs Elaboration

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

  • increasingly will need a separate UI to build more complex queries

  • possible precedent pattern from Data Import rules

  • similar discussion within Metadata group(?)

  • aim to look at UI approaches next week

  • ERM-591 should now enable this from backend

Sprint Backlog

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

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

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

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

15 mins

New Issues

Raised / brought into sprint: 

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

Also:

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

  • cannot consistently reproduce across browsers (possible that Charlotte's original issue has been resolved, though that may just be Mac's disappearing scrollbar)

  • appears to be Win10 only, possibly Chrome only

  • May be related to the scrollbar work done by John Coburn

  • @md331 (Deactivated)  to transfer issue to STCOM

<10 mins

AOB

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

  • outside of FOLIO scope

  • no capacity to have explored so far

  • meaningful log interrogation is still likely a priority

  • this doesn't need to be the solution and streaming then being a dependency

  • streaming is likely the easiest option to implement

  • logs is the most likely use case to test a streaming implementation (as well as eresource entitlement)

  • OS to consider priority for scheduling investigation of this: ERM-633 still takes precedence.

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

  • Q: how to identify a record?

  • See notes on ERM Sprints 79-80. Owen to followup with Steve.

WolfCon aims: 

1. understand how people use the functionality in actual practice (concrete use cases) - existing and gaps

2. have cross-app integration conversations, including how to practically take those forward for delivery

Wolfcon schedule: https://wolfcon2020a.sched.com/