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


Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions


30 minsWIP Updates

QA / UAT: all in good place to test 

  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-685
     / 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-690

Code Review

  • NA

In Progress 

  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-689
    • code should work, but can't properly test extended export
    • query about easier way to get active package data
    • Ethan has a sample package json that should make that possible, if an agreement is created (which would need to done in the UI)
    • Peter to update (add or extend) dev script in mod-agreements to include package and agreement
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-700
     / 
  • json seems to be appending names with zero characters
  • otherwise going well
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-702
      • json seems to be appending names with zero characters
      • otherwise going well
      • question remains about where this is hosted
      • can be run outside of FOLIO (as an isolated GBV served script) for this iteration, but will need to be integrated with the platform
        • driver is displaying error messages in usage context
        • raises questions about cross-app logging
        • impacts licenses and subscriptionAgreements
        • to be raised with Tech Council members on Thu 27 Feb
        • agreements model is not currently expected to change to have an extensible identifier, but to use a reference instead (based on name, though this is brittle)
        • testing to be done by Felix and/or Annika
        • Ian Ibbotson (Use this one) to add acceptance criteria / statement
    • Modal: 
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-723
       
    • Callout: 
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-724
       / 
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-725
       / 
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-
    724
    • 727
      • functionality is now in stripes-core, so no need to take to the stripes team on Thursday
      • easy to pick up while waiting for laser work to 
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-668
       / 
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-684
      • starting still expecting to QA this sprint
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-713
       / 
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-712
      • PR just raised for frontend
      • backend not started yet
      • for backend: it is sufficient to output everything and leave it blank if no data (more efficient than only showing populated fields)
      • frontend need to know what errors might be sent back to report in UI
        • always return CSV whether or not empty
        • log backend errors in console

    Sprint Backlog

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-708
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-681
     
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-715
       
      • dependent on resolving 
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-747
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-740
       / 
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-742
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-705
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-655

    Needs Elaboration

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-726
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-730
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-735
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-701
       
    • For
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-702
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-737
         / 
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-738
         / 
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-739
    •   

    10 mins

    New Issues

    Raised / brought into sprint: 

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-747

    <15 minsAOB

    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-495