Jul 1, 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

Code Review: 

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

  • works locally now, displaying JSON info as expected

  • progressed to Code Review

  • Owen to create separate story to add the info into UI

In Progress 

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

  • App is done

  • Tests begun

  • Weird issue re filters: 

    • not showing up in URL

    • Tests seem to block test writing

  • Standalone works

  • Running without ui-agreements runs fine, introducing it causes the filters to not display

  • Two filters with different names = shouldn't be an issue

  • Filters call the plugins, which each call mod-agreements

    • potentially caching some ui-agreements

  • Set up as with other 

  • datakey is being passed in, though needs to be unique

    • may be the same that's being passed in on both filters. 

  • needs a separate endpoint which will be used by ERM-951

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

  • depends on backend of ERM-950 being merged

  • however there is a PR build failrure because of 

  • JSON structure is not confirmed to be being returned

  • has some dummy data being passed to MCL resembling ERM-953 wireframes

  • frontend work required: 

    • need callback properties in MCL 

    • awaiting shape from ERM-959: added sample during call

  • assume it is data.endpoint

  • will need a STCOM PR 

    • probably ready today

  • will continue to work off Ethan's branch locally

Sprint Backlog

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

• https://folio-org.atlassian.net/browse/ERM-943 / https://folio-org.atlassian.net/browse/ERM-944 / https://folio-org.atlassian.net/browse/ERM-945

  • Steve has reviewed Ian's preferred approach (extend refdata to include subtype detail), and there is a track-stopping challenge

  • Second property field will be ugly but probably the better approach for now than refdata extension

  • Semantically correct way will surpass sprint boundaries; 

  • Decision on way forward confirmed during call:

    • add second property

  • Allocated to @Claudia Malzer

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

• ERM-952

  • https://folio-org.atlassian.net/browse/ERM-957 - done and committed

  • https://folio-org.atlassian.net/browse/ERM-959 - Ethan to add shape for 

Needs Elaboration

• NA

QA / UAT: 

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

  • Passed straight through to QA

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

  • Permission changed from organization-storage to organization

  • causes a breaking interface dependency change

  • Will need to trigger a bugfix release

10 mins

New Issues

Raised / to bring into sprint: NA

Raised: 

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

  • raised as mitigation for ERM-974 and ERM-975

  • brings into line with similar user feedback behaviour introduced for PO lines

  • not required for Goldenrod

  • should be available for Ready to Progress 

<15 mins

AOB

NA