Agreements
(UXPROD-573)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q1 2019 | Parent: | Agreements |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Owen Stephens | Assignee: | Owen Stephens |
| Resolution: | Done | Votes: | 0 |
| Labels: | entitlements, erm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Epic Link: | Agreements | ||||||||||||||||
| Development Team: | Bienenvolk | ||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R2 | ||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||
| Description |
|
For a
For a title, this would indicate that the custom coverage should be used instead of the default/normal coverage for the title. Specifically changes to the coverage at agreement line level for Title Instances or Package Content Items should be reflected in the e-resource list within the agreement preview pane
Notes For visibility of future work, for supporting modifying Package Content Items where only the Package exists as an agreement line we intend to:
Potential future work:
Also note this is only needed for situations where ERM internal KB resources are added to an agreement. As eHoldings/Agreements integration moves forward, where eHoldings items are added to an agreement they should not support this function, as all custom coverage information will be set in eHoldings |
| Comments |
| Comment by Theodor Tolstoy (One-Group.se) [ 08/Feb/19 ] |
|
Chalmers would do this in eHoldings? Khalilah Gambrell |
| Comment by Khalilah Gambrell [ 08/Feb/19 ] |
|
Yes, Theodor Tolstoy (One-Group.se) handled in eholdings. |