Release Candidates

Code Review: NA

QA / UAT: 

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-844

  • not seeing complete set of eHoldings data 
  • Owen to provide test examples
  • FE uses underscore and ref objects differently
  • Can add missing data (eg, identifiers) to backend 

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-843

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-877

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-889

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-894

   / 

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-895

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-896

   / 

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-897

Items at Risk / Spillover

In Progress

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-681

  • to tie into existing harvest as new service
  • single thread functioning is fine
  • to work out: multithreaded behaviour
    • easiest resolution is to run two tenants
  • GOKb will need to `/packages` handling being enforced

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-510

  • still not sure how to access MDC - cannot map to existing code structure
  • potentially need to raise the log message at a different level
  • Steve to examine what could be done with the MDC part, and whether need to take alternative routes

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-788

   / 

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-791

  • currently writing tests for errata statements to support this
  • should be good to move to QA in next sprint

Sprint Backlog

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-842

   
  • contingent on 

    Jira Legacy
    server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-788

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-893

  • Component
    • reached out to Data Import team - their component is not reusable - tightly coupled to DI
    • JC needs to add accessibility info to component before it can be standardised
    • Adi to draft component components to build on
  • ERM use-case / implementation
    • queuing updates should not be done
    • tags will be sent with all required fields as part of a single endpoint
    • 'suppress from discovery' added as a flag, rather than a tag - as per user request
    • UI variation:
      • add note to UI to confirm that changes are persisted immediately
      • change 'save & close' button to 'close'
      • remove 'cancel'

Needs Elaboration

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-869

  • wireframes done - pending review

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-868

  • to `create` a TI isn't patching anymore ... cannot do this currently, can be added to errata schema later
  • sequence needs consideration
  • patch tests will help with this

•  re ERM-844 Owen Stephens to create new stories to elaborate for gaps and kludges at front and back end

Raised

Additional

Accessibility / Definition of Done

• Primer: https://github.com/folio-org/stripes-components/blob/master/docs/AccessibilityDevPrimer.md
• Definition of Done:
  • Done: developer responsibility
  • Verified by Lead Dev in code review