Details
-
New Feature
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
XXL < 30 days
-
XXL < 30 days
-
Bienenvolk
-
-
82
-
-
R4
-
R4
-
R4
-
R4
-
R4
-
R4
-
R1
-
R1
-
R1
-
R4
-
R1
-
R4
-
R3
-
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:
ERM-395Populate access start and access end datesERM-397Reporting change to the coverage dates on a resource (need to decide when this gets reported)ERM-392Reporting change in title count in a package (maybe percentage)ERM-394Viewing current content of package in UIERM-393Reporting change to the date a resource joined/date left package (access_from, access_to dates on resource)ERM-396Viewing 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
TestRail: Results
Attachments
Issue Links
- is defined by
-
ERM-392 Reporting change in title count in a package
-
- Closed
-
-
ERM-393 Reporting change to the date a resource joined/date left package
-
- Closed
-
-
ERM-394 Viewing only current content of package in UI
-
- Closed
-
-
ERM-395 Populate access start and access end dates
-
- Closed
-
-
ERM-396 Viewing upcoming joiners/leavers for a package
-
- Closed
-
-
ERM-397 Reporting change to coverage dates on a resource
-
- Closed
-
- relates to
-
UXPROD-1932 Manage resources joining/leaving an Agreement
-
- Closed
-