2019-10-09 ERM Weekly Delivery Update

Meeting Details

Date
 
Time

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

LocationVideo Call in FOLIO Slack: #erm-developers

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions
  •  
5 minsPrevious Actions
  • NA

30 mins

WIP Updates
  • Pending Review
    • ERM-396 - Getting issue details... STATUS
      • integration tests not going to be possible as {{dropped}} is essentially unpredictable - don't know the url from the backend
      • can't also get this from Local KB Admin. Electron (doesn't support file upload testing).
      • not desirable to fragment test suite across Nightmare and BigTest.
      • Would need to be manually checked. 
    • ERM-500 - Getting issue details... STATUS
    • ERM-465 - Getting issue details... STATUS
      • backend has been merged
      • some frontend tidy-up to do, but basically done
      • good pattern for handling warnings done by Aditya matukumalli
  • In Progress: what's left to do?
    • ERM-459 - Getting issue details... STATUS
      • Tests to write after 
      • Backend work needed before can write tests: continue next sprint
    • ERM-457 - Getting issue details... STATUS
    • ERM-392 - Getting issue details... STATUS
      • need to find out how to upload a package from the backend (ie, without 
      • alternatively can let harvested jobs sync from startup
    • ERM-394 - Getting issue details... STATUS
      • returned to Steve to complete  ERM-407 - Getting issue details... STATUS , as endpoints not working as expected
  • Pending: 
    • ERM-498 - Getting issue details... STATUS
      • front end basically done
      • backend due today
    • ERM-460 - Getting issue details... STATUS
      • requires backend to progress frontend
    • ERM-393 - Getting issue details... STATUS
    • ERM-497 - Getting issue details... STATUS  
    • what's dependent?
    • what's clear to proceed?

10 mins

New Issues
  • ERM-500 - Getting issue details... STATUS



<10 minsAOB
  • ERM-499 - Getting issue details... STATUS  
    • not an ERM decision
    • still TBD whether/what ERM work is required