Release Candidates

Code Review: 

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

  • Returned to development 
  • Problems with types not being as expected
  • Ethan and Claudia to timebox pairing session to debug and progress

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

  • Pending review

QA / UAT 

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

Items at Risk / Spillover

In Progress

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

  • smooth progress being made
  • Notes section should expand notes by default regardless of whether populated

Sprint Backlog

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

  • Conclusion: 
    • closures are not an option
    • cannot guarantee security requirements with current technical circumstances
  • Alternatively:
    • groovy templating engine with java handlebars, through which security is built-in 
    • explicit helper registration is needed
    • at first pass - could do pre-defined (given) proxies, but not offer user-extensible (custom) methods
      • use cases that can be built or delivered in the first instance are
        • direct replace (match all or first, full or partial)
        • insert characters
        • remove characters
      • TODO: add pseudo-templates to given use cases
    • going forward, still need to address security around user extensible urls if customisation is needed
  • Default behaviour where proxy has been defined for a platform is to use the proxy, rather than require explicit per-instance user confirmation
    • firing this at PTI level should work, as this has access to the necessary platform fields
    • this will allow the proxy map to be built

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

  • expected to be ready for code review today

Blocked

• NA

Needs Elaboration

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

• Hotfix cannot be released because Goldenrod uses Agreements 2.x rather than 3 which the change needs to be made with
• Issue will be closed as Won't Fix, with recommendation to users to not duplicate agreements with supplementary documents
• Potential interim workaround that could be developed is to prevent access to the functionality - this is not a priority development option. 
• Fix will be introduced to Honeysuckle, but institutions will need to upgrade.