Agreements (UXPROD-573)

[UXPROD-585] Track changes to eresources Created: 17/May/18  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: Owen Stephens
Resolution: Done Votes: 0
Labels: crossrmapps, erm, po-mvp, resourcemanagement, team-mvp
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original estimate: Not Specified

Issue links:
Defines
is defined by ERM-396 Viewing upcoming joiners/leavers for ... Closed
is defined by ERM-392 Reporting change in title count in a ... Closed
is defined by ERM-393 Reporting change to the date a resour... Closed
is defined by ERM-394 Viewing only current content of packa... Closed
is defined by ERM-395 Populate access start and access end ... Closed
is defined by ERM-397 Reporting change to coverage dates on... Closed
Relates
relates to UXPROD-1932 Manage resources joining/leaving an A... Closed
Sub-tasks:
Key
Summary
Type
Status
Assignee
UXPROD-1936 Support viewing resources that will b... Sub-task Closed  
UXPROD-1975 Check behaviour of Coverage data chan... Sub-task Closed Owen Stephens  
Epic Link: Agreements
Front End Estimate: XXL < 30 days
Back End Estimate: XXL < 30 days
Development Team: Bienenvolk
PO Rank: 82
PO Ranking Note: This feature relates to UXPROD-1791. Once it is possible for users to import and update e-resource data describing packages into the internal KB, there needs to be some level of change management and reporting alongside this to enable institutions to manage their lists of e-resources effectively.

This feature will also ensure that data updates coming from GOKb are handled correctly and users can easily see what changes have happened
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R1
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R4
Rank: TAMU (MVP Jan 2021): R3
Rank: U of AL (MVP Oct 2020): R4

 Description   

This feature was significantly updated on 5th August 2019 to focus on the 'tracking' aspects. A new, related, feature has been created to manage changes on Agreement lines

Where information about the content/coverage of a eresource is tracked by an external knowledgebase, use this information to update data about resources in Folio and provide information and functionality to those managing the resource on behalf of the library.

Will include:

  • Tracking broad changes to a package as the result of a job (e.g. number of titles updated/added/removed)
  • Ability to see dates resources joined/will join and left/will leave packages
  • Ensure the current list of resources in a package/agreement is accurate based on the current date
  • Offer the ability for a user to see upcoming joining/leaving titles

Discussion Jag/Owen 22nd July 2019:
First steps

  • Rules for populating package join/leave dates
  • Rules for changes to coverage (does it extend or replace existing coverage?)
  • Ensure data model handles these
  • Ensure we have adequate logging on package import that user can see what has changed
  • Ensure UI is updated so it:
    • displays relevant information about dates resources joined/left a package
    • allows user to easily see current package content and upcoming joiners/leavers
    • only current resources in package are shown when user views "E-resources covered by this Agreement"

Deliverable scenarios:

  1. ERM-395 Closed Populate access start and access end dates
  2. ERM-397 Closed Reporting change to the coverage dates on a resource (need to decide when this gets reported)
  3. ERM-392 Closed Reporting change in title count in a package (maybe percentage)
  4. ERM-394 Closed Viewing current content of package in UI
  5. ERM-393 Closed Reporting change to the date a resource joined/date left package (access_from, access_to dates on resource)
  6. ERM-396 Closed Viewing upcoming joiners/leavers for a package in UI

NB any reporting required is about the job logging that it is making a change, not a subsequent diff between before and after states of a resource/package


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