Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Sprint Goal / Focus

  •  

Sprint Schedule

  • Sprint: 88
  • Release: Goldenrod
  • Quarter: 2020 Q2
  • Start Monday 20 Apr, 2pm UK
  • Finish Friday 1 May, 12pm UK


Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

Lead Roles:

  • Front End Code Review: 
  • Back End Code Review:  
  • QA: @

QA Environment: folio-testing

Navigation

Table of Contents

Expand
titleSprint Planning Agenda
  1. Sprint Goal / Focus
  2. Sprint Capacity
  3. Review sprint candidates 
  4. Agree technical approach / define key implementation tasks
  5. Finalise estimates / costings
  6. Confirm sprint scope
  7. Confirm first actions



Sprint Planning  

(error) - not in sprint

(tick) or @ - in sprint 

 

Sprint Focus

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2124

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-793
 / 
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-794
 / 
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-795

Ready to merge. Should be available for QA.

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2344

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-805

Pending tests. 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2344

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-807

Ready for QA.

Would benefit from 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-839
 being fixed. 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-547

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-839

Preferable to resolve this before fixing 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-547

There should be a package status from Gokb.

  • In packageIngest (line 114), default flag should be set to true.
    • use OR with exact equal 
  • So, default to 'progress with import' if not explicitly set. 
  • add case insensitivity

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1669

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-836
 / 
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-834

Ethan Freestone

No tangible progress or gotchas. 

Both issues need to be considered together. 

Whatever is truncated in 834 needs to be available in 836 in full. 

Truncation needs to be done on each name before concatenation. 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2124

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-547

Not working as expected.

GOkb rather than packageIngest adaptor. 

Plenty of data available to 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2346
 / 
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2345

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-748
 / 
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-777

Licenses pretty much done, via controller, to protect API.

Has to check tenant config that OKAPI supports the appropriate ERM functionality.

This allows pre-checks for presence and version of an interface in a tenant.

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2267
 / 
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2335

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-827
 / 
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-828

Claudia Malzer

827 Agreements in Code Review. 

805 to follow, then circle back to 828 Licenses.

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2347

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-814

For Release

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-841
 file attachments are not being copied. 

Everything else works, so good to progress past QA. 

A potential change noted, to be reviewed with PO. 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2124

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-788

(error)(error)

TODO: 

  • Identify what needs to be patched
  • Apply the patch
  • Save changes across patch influence


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2124

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-842
 

(error)(error)

This is an example of an errata (or patch) format, as described for ERM-788.

842: coordinated changes (may be fixed by ERM-788)

If we only get print identifiers for a resource and separately electronic resources that may not have an identifier, these are created as siblings. However, may end up with a future unlinked title instance if there is no known identifier. 

This functionality would create and clean up resources in a single transaction. 

Would benefit from the JSON patch process. 

Future: UI to accommodate this.

Out of FOLIO scope: share presentation to external systems.


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2124

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-843

FE: Aditya matukumalliWireframes: Gill Osguthorpe

Backend: 


843: simple changes with potential internal data updates, not necessarily requiring patch JSON.

Example: replacing coverage statement without extending it, and then potentially amending/synchronising it from PCI to PTI.

  • react to onSave changes to covering statements and alter related titles
    • could use an event to react to save (these now work for multi-tenant)
    • extend should preserve existing coverage behaviour (whether that does or doesn't account for gaps)
    • Change to PCIs (could be multiple CS) → PTIs (single CS) → TIs (single CS)
    • do not expose to OKAPI
  • define UI and related workflow
    • attach to separate permission to editing agreements
Would fix the existing extend functionality to cope with shrinking coverage statements, and cascade to related instances.
    • access functionality via
      • 'eResources' → 'options for acquiring'
      • agreement line record
    • new Edit PCI screen
      • select coverage statement
      • amend start and/or end date
    • new View PCI screen
    • no view of PCIs that have coverage statement errors

No patch / transaction handling required. Could be done ...

  • via the UI (tick)(tick) 
  • via file upload (error)(error)
  • via API (question)(question) 

Would fix the existing extend functionality to cope with shrinking coverage statements, and cascade to related instances.

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2352

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-829

(error)Won't Do. No longer required, as confirmed by ERM Subgroup.