Table of Contents |
---|
Problem(s):
It is difficult to identify orders that are collaborative purchases with other institutions
Use Cases & Requirements:
Requirement | Status | Use cases | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
|
| ||||||||
| Joint purchasing: This could take more than one form
| |||||||||
| Joint purchase: Consortia is acting as a fiscal agent and may collect reimbursements from individual libraries | |||||||||
| Vendors will setup joint accounts for consortia. All members have agreed to participate in some capacity and is allotted and amount of value to make purchases on that account. In this case the vendor is actually managing the amount and is paid in advance. Member institutions may create Funds to track their progress, this means they may also create invoices and order records to commit and expend these amounts through the year. |
Proposed workflow: (TBD)
- Flag the order as a joint purchase with a data point at the PO level
- ...
Questions for Users:
Question | Status | Conclusion | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Does this detail overlap with Acquisitions method or Payment method? |
| ||||||||||
Are there still any joint purchases for Physical items? |
| ||||||||||
How much of these purchases are DDA versus other methods of acquisition? |
Questions for Vendors:
Question | Status | Conclusion | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
Questions for Developers:
Question | Status | Conclusion | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
Work Breakdown Structure:
Features:
UI Stories
MOD Stories