Release Candidates

Code Review: 

QA / UAT:

NA

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

Items at Risk / Spillover

Blocked: 

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

In Progress

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

   

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

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

  • working on this at the moment
  • expecting to go to code review Thu/Fri

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

  • functionality is done on Create
  • Edit functionality 
  • styling to be done

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

   
  • some minor snags, but nothing blocking or unexpected
  • local development versions for TK and Grails OKAPI seem fine
  • verifying against agreements
  • will use ui-agreements test to confirm them as well
  • not deployable until docker image is done
  • aim is to keep it within gradle, and just use a different image target
  • docker image will be shared by both licenses and agreements
  • aim to get agreements done by end of week, possibly both

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

     

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

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

  • experiencing orphan problems when changing identifiers (eg, ISSN)
  • current behaviour is expected, because of way identifiers behave
  • when id is changed, package is being updated, but title is replaced, old PTI links are severed, and original resources do still exist
  • unlikely testing scenario
  • issue to be pushed to code review

Sprint Backlog

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

  • entitlements is the endpoints for agreement lines
  • need to access al agreement lines for a single agreement rather than all agreements
  • would need to use /erm/resource/ID/entitlements or /erm/resource/ID/sas 
  • Steve to add comment in Jira

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

  • not started yet

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

   / 

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

   = to be completed by Adi along with ERM-1000

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

   = pending Owen's return

Needs Elaboration: 

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

   = should be open

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

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

Raised

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

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

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

   = added to Ready to Progress

Additional:

NA