https://folio-org.atlassian.net/browse/UXPROD-2124

https://folio-org.atlassian.net/browse/ERM-793 / https://folio-org.atlassian.net/browse/ERM-794 / https://folio-org.atlassian.net/browse/ERM-795

@md331 (Deactivated) / 

@Owen Stephens

Ready to merge. Should be available for QA.

https://folio-org.atlassian.net/browse/UXPROD-2344

https://folio-org.atlassian.net/browse/ERM-805

@Claudia Malzer

Pending tests. 

https://folio-org.atlassian.net/browse/UXPROD-2344

https://folio-org.atlassian.net/browse/ERM-807

@Owen Stephens

Ready for QA.

Would benefit from https://folio-org.atlassian.net/browse/ERM-839 being fixed. 

https://folio-org.atlassian.net/browse/ERM-547

https://folio-org.atlassian.net/browse/ERM-839

@Ethan Freestone

Preferable to resolve this before fixing https://folio-org.atlassian.net/browse/ERM-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

https://folio-org.atlassian.net/browse/UXPROD-1669

https://folio-org.atlassian.net/browse/ERM-836 / https://folio-org.atlassian.net/browse/ERM-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. 

https://folio-org.atlassian.net/browse/UXPROD-2124

https://folio-org.atlassian.net/browse/ERM-547

@Peter Böhm

Not working as expected.

GOkb rather than packageIngest adaptor. 

Plenty of data available to 

https://folio-org.atlassian.net/browse/UXPROD-2346 / https://folio-org.atlassian.net/browse/UXPROD-2345

https://folio-org.atlassian.net/browse/ERM-748 / https://folio-org.atlassian.net/browse/ERM-777

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

https://folio-org.atlassian.net/browse/UXPROD-2267 / https://folio-org.atlassian.net/browse/UXPROD-2335

https://folio-org.atlassian.net/browse/ERM-827 / https://folio-org.atlassian.net/browse/ERM-828

@Claudia Malzer

827 Agreements in Code Review. 

805 to follow, then circle back to 828 Licenses.

https://folio-org.atlassian.net/browse/UXPROD-2347

https://folio-org.atlassian.net/browse/ERM-814

For Release

https://folio-org.atlassian.net/browse/ERM-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. 

https://folio-org.atlassian.net/browse/UXPROD-2124

https://folio-org.atlassian.net/browse/ERM-788

TODO: 

• Identify what needs to be patched

• Apply the patch

• Save changes across patch influence

https://folio-org.atlassian.net/browse/UXPROD-2124

https://folio-org.atlassian.net/browse/ERM-842 

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.

https://folio-org.atlassian.net/browse/UXPROD-2124

https://folio-org.atlassian.net/browse/ERM-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

  • 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  

• via file upload 

• via API  

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

https://folio-org.atlassian.net/browse/UXPROD-2352

https://folio-org.atlassian.net/browse/ERM-829

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