...
See | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-4137 |
|---|
|
| Rec Type | ID | Global/Local | Notes |
|---|
| Item | Barcode | G |
|
| Item | HRID | G |
|
| Instance | Instance HRID | G |
|
| Holdings | Holdings HRID | G |
|
| Organization | Code | L |
|
| Organization | Name | L |
|
| Orders | PO Number | G | Erring on the side of caution here. Certain visibility into orders is necessary but deeper analysis of how much is shared is required |
| Orders | PO Line | G |
|
| Invoices | Invoice # | L |
|
| Acquisition Unit | Name | G |
|
| Fiscal Year | Code | L | Presumptive. Need confirmation from consortia. |
| Ledger | Code | L |
|
Proposed Workflow
Questions
| Question | Status | Conclusions | Comments |
|---|
| Are any record types or unique identifiers missing in the above list, which will need to be visible or partially visible to some or all consortia members? | |
|
|
| Are there any circumstances under which other order-specific information should be shared with the consortium? | |
|
|