Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-396
      • 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. 
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-500
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-465
      • 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?
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-459
      • Tests to write after 
      • Backend work needed before can write tests: continue next sprint
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-457
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-392
      • need to find out how to upload a package from the backend (ie, without 
      • alternatively can let harvested jobs sync from startup
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-394
      • returned to Steve to complete 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-407
        , as endpoints not working as expected
  • Pending: 
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-498
      • front end basically done
      • backend due today
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-460
      • requires backend to progress frontend
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-393
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-497
       
    • what's dependent?
    • what's clear to proceed?
  •   Steve Osguthorpe to create Jira issue for backend tests for 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-396

10 mins

New Issues
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-500



<10 minsAOB
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-499
     
    • not an ERM decision
    • still TBD whether/what ERM work is required