Agreements (UXPROD-573)

[UXPROD-1489] Set custom coverage for title entitlements Created: 24/Jan/19  Updated: 16/Sep/20  Resolved: 25/Mar/19

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:
Cloners
clones UXPROD-1158 Enable setting of custom coverage for... Closed
Defines
is defined by ERM-65 Manage custom entitlement coverage fo... Closed
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

  • Title Instance
  • Package Content Item
    which has been added to an agreement as an agreement line support setting custom coverage dates.

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

  • Subscription Line item for Title Instances or Package Content Items only in this feature
  • Expectation is that the edit happens "in line" within agreement edit pane - wireframes to be provided
  • In custom coverage start/end dates should support date picker
  • End date cannot be before start date
  • End date can be empty
  • Start date is required

Notes
This feature is restricted to Agreement Lines that are either title instances or package content items. This is because a link between Agreement and a Package does not lead to a direct link between the Agreement and any Package Content Item within the Package. We do not currently anticipate changing this, but taking a different approach to situations where libraries want to set custom coverage for a package content item within a package where only the package exists as an agreement line

For visibility of future work, for supporting modifying Package Content Items where only the Package exists as an agreement line we intend to:

  • Allow amendments to the Package
  • add Package to the agreement
  • Then if they have an amendment to the Package, they would record that
    This is likely to be done via an addition to the current data model to support the concept of a "derived package"

Potential future work:

  • Support “derived package” - a version of an existing package with some variations in coverage etc.
  • Derived packages could either track a package or not (for updates etc.) - user choice
  • This work needs planning before we support customisation of either package coverage (at agreement line level) or custom coverage on specific Package Content Items within a Package in a subscription line

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.

Generated at Fri Feb 09 00:15:58 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.