Cooperative Collection Development notifications for cancellation and last copy
- Dennis Bridges
UXPROD-4825 - Getting issue details... STATUS
Problem(s):
Managing collections in a multi-tenant environment limits a users ability to view items on order for other institutions. Particularly when libraries are also using acquisitions units.
Use Cases & Requirements:
| Legend |
| Scope may require separate feature |
Requirement | Status | Use cases |
|---|---|---|
When member library A cancels a subscription member library B is notified. | PENDING | User at member library A cancels "only" subscription for a given material. Patrons at member library B might be relying on access to that material and will no longer be able to use it. User at library A is notified so they can make a decision whether they now must acquire that material to maintain access. |
When a libraries copy of something becomes the only one left the library needs to be notified | PENDING | When a libraries copy of something becomes the only one left in the consortium the demand for that item could become more difficult to manage very quickly. User at the library must determine whether to purchase additional copies. |
Proposed workflow:
Questions:
Question | Status | Conclusion | Comments |
|---|---|---|---|
OPEN | |||
OPEN |
Functionality Potentially Impacted by Changes:
Functional area | Records | Potential impact | Suggested Regression Testing |
|---|---|---|---|