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

Roadmap Priorities

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1755
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-585
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1472


Apologies


Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions
  •   
20 minsSprint Cutoff
  • Items at Risk / Spillover

    • Open / Sprint Backlog

      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-356
         - to pick up after ERM-394
    • In Progress

      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-428
         - to merge along with ERM-429
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-429
         - controlling license done, which can be 
        • TODO: tests need updating as rendering has changed
        • aim for ready for QA on Friday.
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-410
         - all subtasks are `In QA` - anything left to develop, or can the parent issue be sent for QA? (tick)(tick)
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-270
         - working solution in a PR needs refactoring, aim to complete today
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-394
         - expecting today
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-371
         - TODO: tests are breaking, need updating
  • Release Candidates

    • Code Review: none

    • QA / UAT

      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-444
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-419
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-168
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-430
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-395
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-392
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-393
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-260

15 mins

New Issues
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-447
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-448
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-449
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-450
     

    • may be related to a separate Docker memory handling issue.

    • Steve has been in touch with Ian Hardy. Appears that container can be assigned to more memory than it is possible to use.

    • no ERM application error. 
    • workaround is to restart container.

5 mins

Next Sprint
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1467
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1469
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1932
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-396

Leverage and surface into UI the existing active_from and active_to fields.

Copy and link existing agreements to new agreements (link of different type, eg, supercede or replace). Should support post-cancellation-access links going forward. 


<10 minsAOB
  • Documentation starter: 
    • can we start to use the kind of JSON outputs 

ERM/Licenses/Re:Share Tool Selection Rationale  

  • Translation / refdata: Owen to document base list
  •  Mark Deutsch draft Jira issue for the JSON documentation outputs.