Release Candidates

Code Review: 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-834

   / 

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-826

   /

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-547836

   / 

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-826837

  • Merged, just not transitioned
  • Ready to QA

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-836547

  • still has open PR

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-837828

  • pulled back for code review to test for duplication when there are alternate names 
  • if duplicating, may need to handle consistency in another way

QA / UAT: 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-793

   / 

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-794

   / 

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-795

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-748

   / 

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-777

Items at Risk / Spillover

In Progress

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-843

   / 

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-847

   / 

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-849

  • View and Edit screens largely functioning
  • Still TODO
    
    • Related Titles: requires ERM-776
    • Agreements MCL 
      • unsure how this links to the sibling issues, to expand title instance data 
  • ERM-776 need to provide sibling identifiers
    • needs some backend analysis from Steve Osguthorpe
  • additional info need for TI, to expand TI into PCI?
    • see Slack messages from here

    • Jira
      server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-856

    • can derive from PCI (single call)
    • bolt on siblingdata (related identifiers) to TI

Open / Sprint Backlog

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-788

Needs Elaboration

• NA

Raised

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-855

   / 

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-854

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-853

   / 

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-852

  • 500 can be handled more gracefully
    • backend error message needs to be revised (ERM-857)
    • also needs a front end fix 
  • 404 pertains to re-fetching deleted item;
    • frontend fix only
  • Difference in behaviours
    • in Licenses, the tags are re-fetched
    • in Agreements still need to re-fetch ALs
• Peter Böhm to investigate via 

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-857

Additional