Child pages
  • 2020-07-29 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




Action Items

<5 minsIntroductions

30 minsWIP Updates

Code Review: 

  • ERM-943 - Getting issue details... STATUS
    • Subtasks In Progress
    • Clear to merge
    • Frontend work to be done
      • better not to use the term type  for names!
  • ERM-1012 - Getting issue details... STATUS
    • just moved to code review

In Progress 

  • ERM-1018 - Getting issue details... STATUS  /  ERM-1022 - Getting issue details... STATUS
    • nearly done,
    • running tests
    • so close for code review
    • one PR to deal with both
  • ERM-1032 - Getting issue details... STATUS  /  ERM-1023 - Getting issue details... STATUS
    • need to manually add styles to the loading components or create a new component within stripes-erm-components

Sprint Backlog

  • ERM-944 - Getting issue details... STATUS  / 
    • some questions raised in Slack
  • ERM-945 - Getting issue details... STATUS
    • some help needed for ERM-945 
    • should ERM-945 be in settings
      • does this use similar behaviour to picklists?
      • technical architecture doesn't exist yet to support settings
      • would have to be hardcoded in each adaptor
      • preferable to not add more import functionality to mod-agreements?
      • theoretically could use a known model like LASER? 
        • not really
    • ERM-945 is not possible at this stage. Removing from sprint. 
    • Owen Stephens to create Mapping Feature
    • could be worthwhile to align the backend with JDK11 upgrade
    • Ian Ibbotson to set up new task "adding preferred term relationships" linked to new feature
  • ERM-1010 - Getting issue details... STATUS
    • seems clear
    • will get into detail tomorrow
  • Pending dev review 
  • ERM-1032 - Getting issue details... STATUS
    • large reports > 1000 resources are not performant
      • due to MCL rendering rather than server response
    • pagination (like with eresources) is an improvement, but still poor user experience
      • problem here is different from eresources, but performance effect would be the same
      • nonetheless, pagination is still useful in this scenario
    • alternatively, rendering progressively is also not performant
    • no explicit requirement to make a report searchable ... however, when not paginated can use browser find
    • using a Load All button will complete, but still takes a long time
      • puts the option in the user's hands
      • some changes needed to the STCOM compoennt 
        • request for changes raised
        • being reviewed by John
    • Summary: use a combination of 
      • ERM-1038 - Getting issue details... STATUS
      • Pagination (100 first  + Load More + Load All)
        • Load More trumps Load All if only one button can be presented in MCL
      • ERM-1023 - Getting issue details... STATUS  
  • ERM-904 - Getting issue details... STATUS

Needs Elaboration

  • ERM-999 - Getting issue details... STATUS
    • waiting or ERM-1010 feedback

QA / UAT: 


10 mins

New Issues

Raised / to bring into sprint: NA


<15 minsAOB
  • Friday: Mid Sprint Review
  • Allocations vs Capacity