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

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

      • Reviewed, pending ERM-644 to merge ahead of QA.

      • However, held up in Jenkins. Needs to be re-run by Claudia ({{git commit amend}}).  Currently being  rejected. 

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

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

      • Back with Steve for final review hopefully

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

  • QA / UAT

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

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

      • Pending Owen

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

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

• Items at Risk / Spillover

  • Open / Sprint Backlog

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

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

      • Needs web-toolkit access

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

  • In Progress

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

      • Confirmed as clear to go (no technical or user dependencies)

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

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

      • Front end done

      • Fields added to domain model

      • Import code is wizardry - need Steve's input

      • JSON schema provided for the domain model.

      • Still need clarity on business rules and data validation rules

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

      • Advance notice of breaking changes fro Acquisitions team

      • Orders interfaces are changing. 

      • New support for packages on POL record. 

      • Cannot merge ahead of time because of snapshot process

      • Changes ready to go, but need to be held until Acquisitions are ready to merge later on 22 Jan

      • Backend boxes need to be updated locally as of builds on 23 Jan for Orders 9.0

      • Not currently planning to do a formal ui-agreements version release. 

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

15 mins

New Issues

Raised

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

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

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

Brought into sprint: 

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

10 mins

Next Sprint

TBC.  

<10 mins

AOB

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

  • developer preference is to follow the recipe for making complex queries that is ERM-specific, rather than a generic solution

  • so, no reusable component, but the ux pattern should be reusable

  • SAS filters are up for review / re-design

  • may need to be run against the ERM usergroup, which could delay 

  • potentially use popup filters, though this has accessibility issues 

  • need a PO requirements review, then a UI feasibility review

• Lazy loading readiness

  • @Aditya matukumalli looking at applying this to ui-agreements, based on ui-users work shared by Victor

  • Initially looking at agreement view/edit, but potential application (eventually) for areas such as eresources in agreement

  • Net benefit is faster loading / performance