Jun 24, 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

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

  • changes have been approved

  • CI has failed, so not mergeable

  • Claudia will need the credentials to read on the build ... details are in the PR / CI Jenkins merge notes on jenkins-aws.indexdata.com. 

  • Once complete, can be merged. 

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

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

  • will be released to bugfix environment at 10am EST

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

  • New API has been released, so no longer blocked

  • Revisit this after the in-train comparison 

  • Expect to not begin until next week.

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

  • local dev environment problem is fixed

  • to investigate the GSON file. 

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

  • basic functionality broadly working

  • secondary calls nearly working

  • some known issues to iron out before ready for code review / QA

  • Some future use cases to consider in terms of component structure

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

  • icons to be dealt with in the future

  • other than that, this is probably 

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

  • keeping open, as needs to be revisited to allow for explaining data overlap 

  • Some tweaks rather than substantial reworking to improve contextual information for report users

  • Possibly adjustment to existing columns / additional columns 

  • Grouping / merged row presentation notes

    • Sorting would be inappropriate

    • Filtering is viable

    • Vertical centre alignment is not possible (eg, Platform) with the merged rows

    • Columns that don't vary should not be put in between columns that do vary (nested group issue)

    • targeted css is being used in split cells, so could be elaborated for colour coding 

  • Overlap information may change the shape

    • overlap field values from

      • Full - share a PCI

      • Partial - ...

      • None - don't share a title instance

    • needed because  and  may mean different things in different contexts

    • question about where and when the Overlap value is calculated - in backend seems preferable

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

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

15 mins

New Issues

• https://folio-org.atlassian.net/browse/ERM-960 / https://folio-org.atlassian.net/browse/ERM-961 /https://folio-org.atlassian.net/browse/ERM-963 

  • straightforward to replicate

  • not so straightforward to solve

  • points to undefined array element 

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

•  - cannot reproduce

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

10 mins

Next Sprint

• Continue with Comparison work

• URL customisation 

• Some UX improvements

<10 mins

AOB

Persisted accordian behaviour

• is doable

• similar approach to panes could be taken 

Last regular ERM call with @md331 (Deactivated)

• much appreciation all round for his support, contribution and commitment on the team.