Won't Do
Details
Reporter
Dennis BridgesDennis BridgesPO Rank
0Front End Estimate
Large < 10 daysFront End Estimator
Khalilah GambrellKhalilah GambrellFront-End Confidence factor
30%Back End Estimate
XXL < 30 daysBack End Estimator
Khalilah GambrellKhalilah GambrellBack-End Confidence factor
30%Release
Not For ReleaseTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Reporter
Dennis Bridges
Dennis BridgesPO Rank
0
Front End Estimate
Large < 10 days
Front End Estimator
Khalilah Gambrell
Khalilah GambrellFront-End Confidence factor
30%
Back End Estimate
XXL < 30 days
Back End Estimator
Khalilah Gambrell
Khalilah GambrellBack-End Confidence factor
30%
Release
Not For Release
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 17, 2023 at 8:41 PM
Updated May 2, 2024 at 7:24 PM
Resolved November 22, 2023 at 3:51 PM
Current situation or problem: Acquisitions records contain a number of human readable IDs that are expected to be unique within a given library. Some of these identifiers may also need to be unique across consortia. FOLIO needs to identify what identifiers in the Instance, Holding and Item should be unique within a member vs what should be unique across members.
In scope
Apply the method for managing unique IDs across consortia members to the unique IDs enumerated below
Out of scope
LCAP-related requirements - existing functionality meets their criteria.
Use case(s)
Identifier must be globally unique
-User - Username- Moved to UXPROD-4308
Acquisition Unit - Name
Note: Go-live requirement
Identifier must be accessible and usable by all tenants but with tenant-specific localization
Organization - Name
Organization - Code
Note: LOW PRIORITY
Identifier must be visible to all or specific tenants but only one tenant has write/delete ability.
Orders - PO Number
Orders - PO Line
Invoices - Invoice Number
Fiscal Year - Name
Fiscal Year - Code
Fund - Code
Group - Code
Ledger - Code
Note: Not required for go-live
Proposed solution/stories
Case 1:
Newly created identifiers should have uniqueness verified across all tenants
If an identifier turns out to be non-unique, provide a mechanism for users to associate that identifier with a specific tenant whenever that identifier is accessed (i.e. association per use, not forced permanent association.)
Case 2:
Allow (or force) the record associated with the identifier to be replicated across all tenants (e.g. basic Organization info such as address and phone number)
Allow other tenants to manage some or all information associated with the record for that specific tenant
e.g. Contact persons, Integrations
Allow a tenant to define a record associated with the identifier as non-shareable
Case 3:
Allow other tenants to view the identifier and information associated with that identifier
Allow tenants to define a record associated with a given identifier as non-shareable
e.g. suppress a specific Order or POL from consortium view
Allow tenants to define all records associated with a given identifier as non-shareable
e.g. designate all Funds as non-shareable
Links to additional info
Unique identifier analysis: https://folio-org.atlassian.net/wiki/x/KBNU
Questions