...
Rec Type | ID | Editable? | Global/Local | Why unique? | Explicit or augmented? | System-generated or manual? | Notes |
---|---|---|---|---|---|---|---|
Item | Barcode | Y | G | Resource sharing | Augmented | M | Nearly impossible to eliminate barcode duplication across a large consortium, but need to differentiate ownership. |
Item | HRID | ||||||
Instance | Instance HRID | ||||||
Holdings | Holdings HRID | ||||||
Organization | Code | L | |||||
Organization | Name | L | |||||
Orders | PO Number | ||||||
Orders | PO Line | I can't identify any scenarios where Tenant A would need to see a unique POL for Tenant B | |||||
Invoices | Invoice # | L | |||||
Acquisition Unit | Name | G | Shared order across multiple tenants | Augmented | M | Possible use case: central tenant acquires on behalf of other tenants. | |
Fiscal Year | Name | L | |||||
Fiscal Year | Code | L | Presumptive. Need confirmation from consortia. | ||||
Ledger | Code | L | |||||
Group | Code | L | |||||
Fund | Code | L | |||||
Voucher | Number | L | |||||
User | Username | Y | G | Users can have multiple affiliations; need to avoid conflict. | Explicit | M | Use case: Central office has a John Doe with limited permissions across multiple tenants. One of those tenants has a staff member Jane Doe. Folio cannot support 2 "jdoe" logins within the same instance. |
Processes Potentially Affected
...