...
See Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4137
Use Cases
Case 1
- Identifier must (or should) be globally unique - requires validation against all tenants
- All tenants share "ownership" of this identifier
- Requires error handling and/or manual tenant assignment in the event of duplicates
Case 2
- Identifier must be accessible and usable by all tenants, but with localization allowed
- All tenants use this identifier, but this identifier can be tailored per tenant
- Uniqueness can be achieved via prefix. suffix or other internal handling
Case 3
- Identifier must be visible to all or specific tenants, but editable only by the owning tenant
- Uniqueness can be achieved via prefix, suffix or other internal handling
| Rec Type | ID | Editable? | Global/Local | Why unique? | Explicit or augmented? | System-generated or manual? | Responsible Team | JIRA Link | Use Case | Notes | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Item | Barcode | Y | G | Resource sharing | Augmented | M | Folijet Spitfire | Nearly impossible to eliminate barcode duplication across a large consortium, but need to differentiate ownership. | |||||||||||||||
| Item | Item | N | Folijet Spitfire | Even if not unique, do we need some sort of indicator of which tenant the Item HRID belongs to? | |||||||||||||||||||
| Instance | Instance HRID | N | Folijet Spitfire | Even if not unique, do we need some sort of indicator of which tenant the Instance HRID belongs to? | |||||||||||||||||||
| Holdings | Holdings HRID | N | Folijet Spitfire | Even if not unique, do we need some sort of indicator of which tenant the Holdings HRID belongs to? | |||||||||||||||||||
| Organization | Code | L | Thunderjet | 2 | |||||||||||||||||||
| Organization | Name | L | Thunderjet | 2 | |||||||||||||||||||
| Orders | PO Number | Thunderjet |
| 3 | |||||||||||||||||||
| Orders | PO Line | Thunderjet | 3 | I can't identify any scenarios where Tenant A would need to see a unique POL for Tenant B | |||||||||||||||||||
| Invoices | Invoice # | L | Thunderjet | 3 | |||||||||||||||||||
| Acquisition Unit | Name | G | Shared order across multiple tenants | Augmented | M | Thunderjet | 1 | Possible use case: central tenant acquires on behalf of other tenants. | |||||||||||||||
| Fiscal Year | Name | L | Thunderjet | 3 | |||||||||||||||||||
| Fiscal Year | Code | L | Thunderjet | 3 | Presumptive. Need confirmation from consortia. | ||||||||||||||||||
| Ledger | Code | L | Thunderjet | 3 | |||||||||||||||||||
| Group | Code | L | Thunderjet | 3 | |||||||||||||||||||
| Fund | Code | L | Thunderjet | 3 | |||||||||||||||||||
| Voucher | Number | L | Thunderjet | 3 | |||||||||||||||||||
| User | Username | Y | G | Users can have multiple affiliations; need to avoid conflict. | Explicit | M | Thunderjet | 1 | 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. | ||||||||||||||
| User | Barcode | Y | G | ||||||||||||||||||||
| Service point |
...