Sep 25, 2019 

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

Video Call in FOLIO Slack: #erm-developers

<5 mins

Introductions

• Attendees / Apologies

• Upcoming Availability

5 mins

Previous Actions

• Draft Jira issue for the JSON documentation outputs

30 mins

WIP Updates

• Pending Review

• In Progress: what's left to do?

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

    • conversations with dev and PO realising how complex the queries are

    • @Owen Stephens defining priority test cases to help with development

    • most complex case is agreement resources, and that's nearly done

    • expected ahead of Claudia starting work on related issues (Thu)

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

    • does not require a local frontend

• Pending: 

  • what's dependent?

    • ERM-466 backend is predecessor for ERM-467 and ERM-468

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

      • Reason for Closure is select dropdown rather than modal

      • Refdata needs migration work also

  • what's clear to proceed?

    • https://folio-org.atlassian.net/browse/ERM-462 should be ready for QA

10 mins

New Issues

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

  • resolved as part of 3.2 bugfix

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

  • pending elaboration

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

  • @Aditya matukumalli to pickup this sprint

<10 mins

AOB

• Memory / Timeout Issues on snapshot-stable

  • Test environment is 30s vs 1s locally for retrieving endpoints for entitlement  and entitlement-options  (front and back end)

  • Impact: 

    • testing failure results are ambiguous

    • cannot investigate current process for feature elaboration

    • No way to add an agreement, except by Create an environment

    • backend resource drain / distraction

  • Ian Hardy at IndexData is looking at this with Steve

  • Related Jira issue may have been closed 

  • gbv-intern and gbv-demo are both out-of-date - can be updated?

• Sprint Planning Calls & Mid-Sprint Planning Calls

• MCL Column Resizing issue has been raised and pushed back to ERM. STCOM-586.https://folio-org.atlassian.net/browse/STCOM-586

Memory / Timeout Issues

• Prioritise: endpoint development work ahead of timeout resolution

MCL Colum Resizing