ERM Sprint 88

Owned by Jag Goraya
Last updated: Apr 20, 2020

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 Availability: Schedule | Calendar

Notes / Exceptions:

Lead Roles:

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

QA Environment: folio-testing

Navigation

 Sprint 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

UXPROD-2124 - Getting issue details... STATUS

ERM-793 - Getting issue details... STATUS  /  ERM-794 - Getting issue details... STATUS  /  ERM-795 - Getting issue details... STATUS

md331 (Deactivated) / 

Owen Stephens

Ready to merge. Should be available for QA.

UXPROD-2344 - Getting issue details... STATUS

ERM-805 - Getting issue details... STATUS

Claudia Malzer

Pending tests. 

UXPROD-2344 - Getting issue details... STATUS

ERM-807 - Getting issue details... STATUS

Owen Stephens

Ready for QA.

Would benefit from  ERM-839 - Getting issue details... STATUS  being fixed. 

ERM-547 - Getting issue details... STATUS

ERM-839 - Getting issue details... STATUS

Ethan Freestone

Preferable to resolve this before fixing  ERM-547 - Getting issue details... STATUS . 

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

UXPROD-1669 - Getting issue details... STATUS

ERM-836 - Getting issue details... STATUS  /  ERM-834 - Getting issue details... STATUS

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. 

UXPROD-2124 - Getting issue details... STATUS

ERM-547 - Getting issue details... STATUS

Peter Böhm

Not working as expected.

GOkb rather than packageIngest adaptor. 

Plenty of data available to 

UXPROD-2346 - Getting issue details... STATUS  /  UXPROD-2345 - Getting issue details... STATUS

ERM-748 - Getting issue details... STATUS  /  ERM-777 - Getting issue details... STATUS

steve.osguthorpe

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.

UXPROD-2267 - Getting issue details... STATUS  /  UXPROD-2335 - Getting issue details... STATUS

ERM-827 - Getting issue details... STATUS  /  ERM-828 - Getting issue details... STATUS

Claudia Malzer

827 Agreements in Code Review. 

805 to follow, then circle back to 828 Licenses.

UXPROD-2347 - Getting issue details... STATUS

ERM-814 - Getting issue details... STATUS

For Release

ERM-841 - Getting issue details... STATUS  file attachments are not being copied. 

Everything else works, so good to progress past QA. 

A potential change noted, to be reviewed with PO. 

UXPROD-2124 - Getting issue details... STATUS

ERM-788 - Getting issue details... STATUS

(error)

TODO: 

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


UXPROD-2124 - Getting issue details... STATUS

ERM-842 - Getting issue details... STATUS  

(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.


UXPROD-2124 - Getting issue details... STATUS

ERM-843 - Getting issue details... STATUS

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
    • 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) 
  • via file upload (error)
  • via API (question) 

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

UXPROD-2352 - Getting issue details... STATUS

ERM-829 - Getting issue details... STATUS

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