Sprint Goal / Focus
- Sprint: 88
- Release: Goldenrod
- Quarter: 2020 Q2
- Start Monday 20 Apr, 2pm UK
- Finish Friday 1 May, 12pm UK
- Sprint Goal / Focus
- Sprint Capacity
- Review sprint candidates
- Agree technical approach / define key implementation tasks
- Finalise estimates / costings
- Confirm sprint scope
- Confirm first actions
- not in sprint
or @ - in sprint
|Feature ID||Issue ID||Sprint Backlog?|
Notes / Estimates / Actions
|Ready to merge. Should be available for QA.|
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.
Not working as expected.
GOkb rather than packageIngest adaptor.
Plenty of data available to
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.
827 Agreements in Code Review.
805 to follow, then circle back to 828 Licenses.
Everything else works, so good to progress past QA.
A potential change noted, to be reviewed with PO.
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.
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.
No patch / transaction handling required. Could be done ...
Would fix the existing extend functionality to cope with shrinking coverage statements, and cascade to related instances.
|Won't Do. No longer required, as confirmed by ERM Subgroup.|