/
2019-04-10 ERM Delivery Weekly Update

2019-04-10 ERM Delivery Weekly Update

Apr 11, 2019

Meeting Details

Date

Apr 10, 2019 

 

Time

09:30am ET, 2:30pm UK, 3:30pm Germany

Location

Video Call in FOLIO Slack: #erm-developers

Participants

  • @Jag Goraya

  • @Kurt Nordstrom

  • @md331 (Deactivated)

  • @Owen Stephens

Apologies

  • @Benjamin Ahlborn

  • @Claudia Malzer

  • @Felix Hemme

  • @Gill Osguthorpe

  • @Ian Ibbotson (Use this one)

  • @John Fereira

  • @Martina Schildt

  • @Martina Tumulla

  • @Peter Böhm

  • @steve.osguthorpe

Discussion items

Time

Item

Notes

Action Items

Time

Item

Notes

Action Items

<5 mins

Introductions

 

30 mins

ERM Sprint 60 Retrospective

  • Sprint cycle is practically curtailed, but creates opportunity for 'between sprint' time

  • Improvements to ERM (rather than FOLIO) onboarding

 

20 mins

Sprint 61 Engineering Design Notes

 

 

5+ mins

AOB

  • None

 

Engineering Design Notes / Queries

Feature

Issue

Notes

Feature

Issue

Notes

 

https://folio-org.atlassian.net/browse/ERM-79

  • Some final integration tests to commit

  • Sort order to be implemented

 

https://folio-org.atlassian.net/browse/ERM-49

Progressing dialogue with Wayne to determine implementation options.

 

https://folio-org.atlassian.net/browse/ERM-92

Questions around approach to creating domain objects outside of web app context for integration testing, which Kurt will raise on the ticket.

 

https://folio-org.atlassian.net/browse/ERM-139

TBD whether to share data or fetch each time. FOLIO preference is emerging to be fetch each time (as eHoldings does). This should be resolved in the UX call on Thursday

This approach will result in more fetches, but this should be mitigated through caching.

No caching has yet been implemented, but this is something we need to plan for and schedule into upcoming sprint work.

Determine / confirm caching strategy (@Ian Ibbotson (Use this one))

Note: deferring the refactor until the routing question is resolved need not delay work on Amendments, but if that is progressed using SearchAndSort (rather than SearchAndSortQuery), it will need re-work later. Decision is to expedite the routing best practice question through UX team, complete the refactor and use the next couple of weeks to get a sense of the impact of additional fetches that caching needs to mitigate.

 

https://folio-org.atlassian.net/browse/ERM-173 / https://folio-org.atlassian.net/browse/ERM-174

smart-components has been amended to make Tags handling more flexible, which allows for the option to create a new withTags component in stripes-erm-components.

 

https://folio-org.atlassian.net/browse/ERM-162 / https://folio-org.atlassian.net/browse/ERM-163