Child pages
  • 2020-06-24 ERM Weekly Delivery Update
Skip to end of metadata
Go to start of metadata

Meeting Details


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

LocationVideo Call in FOLIO Slack: #erm-developers


Discussion items

Previously: 2020-05-20 ERM Weekly Delivery Update




Action Items

<5 minsIntroductions

20 minsSprint Cutoff

Release Candidates

Code Review: 

  • ERM-948 - Getting issue details... STATUS
    • 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 
    • Once complete, can be merged. 
  • ERM-958 - Getting issue details... STATUS



  • ERM-841 - Getting issue details... STATUS
    • will be released to bugfix environment at 10am EST

Items at Risk / Spillover


  • ERM-888 - Getting issue details... STATUS
    • New API has been released, so no longer blocked
    • Revisit this after the in-train comparison 
    • Expect to not begin until next week.

In Progress

  • ERM-510 - Getting issue details... STATUS
    • local dev environment problem is fixed
    • to investigate the GSON file. 
  • ERM-950 - Getting issue details... STATUS
    • 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
  • ERM-954 - Getting issue details... STATUS
    • icons to be dealt with in the future
    • other than that, this is probably 
  • ERM-953 - Getting issue details... STATUS
    • 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 (error) and (tick) may mean different things in different contexts
      • question about where and when the Overlap value is calculated - in backend seems preferable

Sprint Backlog

  • ERM-951 - Getting issue details... STATUS
  • ERM-952 - Getting issue details... STATUS

Needs Elaboration: NA

15 mins

New Issues


  • ERM-960 - Getting issue details... STATUS  /  ERM-961 - Getting issue details... STATUS  / ERM-963 - Getting issue details... STATUS  
    • straightforward to replicate
    • not so straightforward to solve
    • points to undefined array element 
  • ERM-962 - Getting issue details... STATUS
  •  - cannot reproduce
  • ERM-964 - Getting issue details... STATUS


10 mins

Next Sprint
  • Continue with Comparison work
  • URL customisation 
  • Some UX improvements

<10 minsAOB

Persisted accordian behaviour

  • is doable
  • similar approach to panes could be taken 

Last regular ERM call with Mark Deutsch

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