Agreements (UXPROD-573)

[UXPROD-1490] Set custom coverage for package entitlements Created: 24/Jan/19  Updated: 25/Oct/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Agreements

Type: New Feature Priority: P3
Reporter: Owen Stephens Assignee: Owen Stephens
Resolution: Unresolved 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-159 Manage custom coverage for Package ag... Closed
is defined by ERM-160 Manage custom coverage for Package ag... Closed
is defined by ERM-161 Manage custom coverage for Package ag... Closed
Relates
relates to ERM-122 Extend package model for coverage Closed
Potential Workaround: By supporting the import of custom package information (via UXPROD-1791 and related features), institutions will be able to create packages with custom coverage, which provides a work around for not being able to set custom package coverage in the UI
Epic Link: Agreements
Front End Estimate: Medium < 5 days
Front End Estimator: md331 (Inactive)
Back End Estimate: Large < 10 days
Back End Estimator: steve.osguthorpe
Estimation Notes and Assumptions: Around 5 days Back end, but this crosses the boundary of the "Medium" estimate. So it's the bottom end of Large
Development Team: Bienenvolk
Kiwi Planning Points (DO NOT CHANGE): 4
PO Rank: 19
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R2
Rank: Grand Valley (Full Sum 2021): R2
Rank: hbz (TBD): R4
Rank: Lehigh (MVP Summer 2020): R2
Rank: Leipzig (ERM Aut 2019): R2
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Libraries may buy e-resources in bundles (packages) defined by suppliers and described by suppliers and knowledgebases . These packages bring together multiple resources which are purchased as a group. When the package includes journals, the first (and if appropriate, last) available issue of the journal available as part of the package is described by start and end coverage statements.

In some cases it may be possible for a library to buy an e-resource package, but for some of the journal titles in the package to have different coverage statements than are stated by the supplier or knowledgebase. In these cases the library still wishes to use the description of the package as provided by the supplier/knowledgebase, but to make changes to the coverage statements for all, or for a subset of titles, or for specific, titles within the package.

To support this, for a package resource to be managed in an agreement context, eResource Managers should be able to set custom coverage dates for

  • all titles in a package
  • a subset of selected titles in a package
  • a single title in a package


 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) will be handled in eholdings.

Comment by Khalilah Gambrell [ 10/Apr/19 ]

patty.wanninger - this feature will not be applicable to any library using EBSCO KB.

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