Feb 12, 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: all in good place to test 

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

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

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

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

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

Code Review

• https://folio-org.atlassian.net/browse/ERM-644 - good to move to QA

In Progress 

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

  • backend PR submitted

  • frontend / UI begun this morning 

  • query about selection tool that allows for type-ahead filter on Edit

    • free text is used for Provider

    • update existing package expected to autofill - that's the long-term goal

  • PO happy to go with single form with just free text

  • given this, should be ready for code review today

  • there may be some attention needed for dynamic array handling in the future (as with Organizations)

    • should this be done at a (smart) component level?

    • maybe ... not a concern for it now, or any clear value for typedown at the moment

Sprint Backlog

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

  • issue updated to show database location of fields

  • 4 of the fields are coming off the title instance (so should be good to update existing KBART export service)

  • date_monograph_published_print  and date_monograph_published_online may be slightly more tricky

  • if trying to populate both, we would have to look for sibling title references. That would be a useful general ERM utility, so is perhaps best built elsewhere first to be reusable, rather than burying in an export lookup. 

    • ermResources/electronic

• https://folio-org.atlassian.net/browse/ERM-711 - to pick up after Steve returns from holiday

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

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

  • validation is in code, but not being actioned

  • needs further investigation

  • lower priority than LASER

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

  • ready to pickup by Adi

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

Needs Elaboration

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

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

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

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

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

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

  • selection via SaS

  • leaning towards

    • export rather than on-screen report in first instance

    • multiple licenses in tabular format

  • still to determine how to  handle selection across results pages

  • further conversation about output needs in next ERM subgroup (19 Feb)

  • doesn't rule out supplementing with a basket mechanism

    • could work nicely to build up results across multiple queries without having to deal with complex queries

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

10 mins

New Issues

Raised / brought into sprint: 

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

  • Adi to have a look

  • Not yet been tested on Supplementary Properties - Gill/Owen to verify

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

  • looks like URL structure has changed in mod/ui-organizations-storage

  • This is a breaking change done as part of an in-progress/unversioned tech debt refactor

  • Cannot easily be done outside of major release versions, where explicit dependencies are defined

  • No heads-up / warning that this - some project communication issues to be addressed

  • Awaiting clarification from Dennis/Craig as to whether this i a permanent change

  • There would likely be peer dependency failures if ERM built to the new (unversioned) specification

<15 mins

AOB