Apr 15, 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-547

  • Steve to review

• https://folio-org.atlassian.net/browse/ERM-793 / https://folio-org.atlassian.net/browse/ERM-794 / https://folio-org.atlassian.net/browse/ERM-795

  • Steve to review backend before Mark can review 

  • backend review is a big job

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

  • Adi reviewing

QA / UAT: 

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

  • Ready for Release

• https://folio-org.atlassian.net/browse/ERM-807 / https://folio-org.atlassian.net/browse/ERM-800 / https://folio-org.atlassian.net/browse/ERM-814 / https://folio-org.atlassian.net/browse/ERM-835

  • all pending QA

Items at Risk / Spillover

In Progress

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

  • done, but wrapped in with  ERM-779

  • will push for review with ERM-779

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

  • using override method rather than events

  • less reusable, but best option

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

  • FE mostly done barring final checks

  • can test migrations if put within a changeset, rather than dropping table.

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

  • under consideration: what to display when no alternative names are presented

  • solution as applied by Claudia to stand (ie, show nothing)

Open / Sprint Backlog

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

  • lower priority than other sprint work

  • not as simple as previously considered

  • to do with ERM-836

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

  • needs some dedicated time on Thursday to ready for next sprint

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

  • very quick to implement when licenses model is done (ERM-827)

Needs Elaboration

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

  • Question is around opening up custom properties as a generic solution

  • Progress discussion with subgroup over last two weeks

  • Not sure that we don't need custom properties

  • But there are some more specific requirements emerging (as well as if not instead of re-applying custom properties)

  • Reviewing feedback and the many various touchpoints to work out what to do next

  • Notes may not be a good solution either

  • Challenge is that any first solution here may be wrongfully re-purposed for workarounds, which will have downstream data quality issues

  • Not going to to progress custom properties in next sprint

  • Need to avoid putting things on the 'source of truth' kb record

15 mins

New Issues

Raised

• https://folio-org.atlassian.net/browse/ERM-835 - see above

• https://folio-org.atlassian.net/browse/ERM-836 - Peter to pick up with ERM-834

Additional

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

  • could it be basket overflowing from the render area triggering a size re-calculation?

  • Owen seems to be able to reproduce on Catalina at 100%

10 mins

Next Sprint

Should not combine errata and custom properties

<10 mins

AOB

Ready to Progress reviewed/triaged

• API change for LAS:eR - Ethan to progress, along with ERM-831 and ERM-832