Details
-
Story
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
None
-
ERM Sprint 125, ERM Sprint 126, ERM Sprint 127, ERM Sprint 128, ERM Sprint 129
-
Bienenvolk
-
Lotus R1 2022
Description
Purpose:
In the entitlement log, if there is custom coverage available for an entry based on the Entitlement (Agreement Line), this should be used in the EntitlementLog entry coverage instead of the default PCI coverage
User story statement(s):
As a consumer of the EntitlementLog,
I want to have the correct coverage information
so that I can use it appropriately (e.g. in a union catalogue)
Scenarios:
- Scenario:
- Given an agreement line for a PCI with a custom coverage
- When I view the EntitlementLog entry which has been created because of that custom coverage
- Then the coverage statement will reflect the custom coverage OR be present alongside the default coverage with enough information for the consumer to differentiate and use the correct coverage
Dev task breakdown
This file currently creates the coverage summary manually, but perhaps can be tweaked to work a little more like:
https://github.com/folio-org/mod-agreements/blob/6febed3bee4aec20f1c2b97857ef51cabbbf710a/service/grails-app/views/entitlement/_entitlement.gson#L24-L36
- If entitlement.coverage exists, use that.
- Else do what it was doing before
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-2817 ERM Agreements Title addition and removal feed
-
- Closed
-
- is cloned by
-
ERM-1883 Change to coverage should lead to updated entry in EntitlementLog
-
- Closed
-
-
ERM-1884 Populate "suppress" field in EntitlementLog
-
- Closed
-
- relates to
-
ERM-1459 Support a log of resources that have been added/removed from a library collection
-
- Closed
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...