Jan 29, 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: tets data now set up, so able to make good progress in testing

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

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

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

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

Code Review

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

  • migration development completed

  • query about how best to locally: details on Vagrant Setup for ERM 

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

  • final BigTest integration to complete 

  • currently going well

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

In Progress 

• https://folio-org.atlassian.net/browse/ERM-633 - de-scoped from active development

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

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

  • Using license properties approach because of the vertex(?) constraints on mod-customfields library

  • Owen to follow up with Leipzig that ERM are doing the front end changes

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

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

Sprint Backlog

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

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

  • Mapping and UI to follow current QA

    • expect to be dropdown to define type of import and additional fields to capture new details

    • makes sense to have new route, as going to new endpoint. 

  • Clear to proceed with TSV controller

Needs Elaboration

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

  • active discussion between FE/BE/PO/UX

  • backend constrains ideal - but within requirement parameters

15 mins

New Issues

Raised / brought into sprint: 

Also:

<10 mins

AOB

CHAL-208.  Entitlement endpoints are slow (~30s) in eHoldings, as single rows being added. Performance issues. This may be faced again by other EKB users (such as Cornell). 

• Stripes-connect re-fetches on offset (but fixing this wouldn't fix the issue: may reduce the performance, but would involve significant work. 

• ERM fetches per title. 

Some potential resolutions: 

• ERM imports the data (commercially unlikely)

• Attach order lines via eHoldings (rather than agreement resources): though can't do this if needing different order lines per resource.

• Use a batch endpoint.