Agreements
(UXPROD-573)
|
|
| 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: | agreements, erm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Epic Link: | Agreements | ||||||||||||||||||||
| Development Team: | Bienenvolk | ||||||||||||||||||||
| PO Rank: | 53 | ||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R2 | ||||||||||||||||||||
| 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): | R2 | ||||||||||||||||||||
| Rank: hbz (TBD): | R2 | ||||||||||||||||||||
| 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): | R4 | ||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||
| Description |
|
Support for agreements which are subject to patron driven or evidenced based acquisiton - that is where a general set of resources are accessible during the lifetime of the agreement, but some resources within that can be "purchased" at which point they become part of the libraries permanent collection. Workflow yet to be fully defined but may include:
There maybe the need for touchpoint with Inventory and Orders for this workflow to be fully realised |
| Comments |
| Comment by Anya [ 16/Oct/19 ] |
|
FC : Question: is there something similar for Eholdings? |
| Comment by Khalilah Gambrell [ 31/Oct/19 ] |
|
Anya, Chalmers is currently using tags to manage DDA/EBA titles. And in the future the plan is to implement acquisition/access status types to support whether a title is DDA/EBA. |
| Comment by Owen Stephens [ 05/Nov/19 ] |
|
Further improvements for managing PDA/EBA maybe delivered in future, but the functionality as scoped for this feature is now delivered |