[UXPROD-2817] ERM Agreements Title addition and removal feed Created: 12/Nov/20 Updated: 25/Feb/22 Resolved: 25/Feb/22 |
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Lotus (R1 2022) |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Owen Stephens | Assignee: | Owen Stephens |
| Resolution: | Done | Votes: | 0 |
| Labels: | agreements, erm, local_kb | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||
| Development Team: | Bienenvolk | ||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 39 | ||||||||||||||||||||||||||||||||||||||||
| PO Ranking Note: | This is a blocker for implementers in Germany who wish to use Agreements to feed the Union Catalogue | ||||||||||||||||||||||||||||||||||||||||
| Cap Plan Fix Version (DO NOT CHANGE): | R2 2021 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R5 | ||||||||||||||||||||||||||||||||||||||||
| Description |
|
N.B. Applies to the Agreements Internal KB only Current situation or problem: Because the definitions of what constitutes a "current" title rely heavily on dates that are stored in Agreements and the Agreements internal KB, the list of current titles can change from day to day without any changes to the underlying stored data. For example if an Agreement Line has an "active to" date, once that date is passed that agreement line is no longer "active" and all of the titles that form part of that agreement line cease to be part of the current title list. The implication of this is that to keep a discovery system up to date, a complete export of all current titles would be required daily - which would be very inefficient. This feature is to support support the ability to produce a log of additions and removals of resources to/from the library collection based on agreements, agreement lines, and package information (from the internal KB). It should be possible to query a list of changes since a specific date. If queried from "day 0" (i.e. all changes ever), the response can be used to reproduce the current state of available resources by 'replaying' the list of changes over the entire time period. In scope Out of scope Use case(s) |