Agreements (UXPROD-573)

[UXPROD-1932] Manage resources joining/leaving an Agreement Created: 05/Aug/19  Updated: 16/Sep/20  Resolved: 27/Nov/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2019
Parent: Agreements

Type: New Feature Priority: P3
Reporter: Owen Stephens Assignee: Khalilah Gambrell
Resolution: Done Votes: 0
Labels: agreements, erm, po-mvp, team-mvp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by ERM-456 Manage Agreement line Active dates Closed
is defined by ERM-457 Use Agreement Line active from/active... Closed
Relates
relates to UXPROD-585 Track changes to eresources Closed
Epic Link: Agreements
Development Team: Bienenvolk
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R1
Rank: 5Colleges (ERM Jun 2020): R1
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

Over the lifetime of an agreement, resources may be added to or leave an agreement (e.g. if a title transfers to a new publisher).

This feature is to enable the management of these changes at an Agreement line level based on the dates that resources join or leave an agreement.

NB changes happening within a package which has been added to an agreement as an agreement line are managed at the package level not the agreement line level - so dates for a resource joining/leaving a package are managed separately via the appropriate knowledgebase. This feature is only about managing the changes at an agreement line level



 Comments   
Comment by Khalilah Gambrell [ 11/Feb/20 ]

Anya and Owen Stephens, this feature is not available to EBSCO KB customers at this time. I will need to create a user story/feature to support.

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