Managing unique identifiers in acquisitions records

Description

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)

  1. Identifier must be globally unique

    • -User - Username- Moved to UXPROD-4308

    • Acquisition Unit - Name

    • Note: Go-live requirement

  2. Identifier must be accessible and usable by all tenants but with tenant-specific localization

    • Organization - Name

    • Organization - Code

    • Note: LOW PRIORITY

  3. 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

Priority

Fix versions

None

Development Team

Thunderjet

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Activity

Show:

Joseph ReimersNovember 22, 2023 at 3:51 PM

This was a parent analysis feature and we've done what we know we needed to do. If additional use cases emerge, we will create appropriate features specific to those use cases.

Joseph ReimersJuly 21, 2023 at 6:51 PM

I'm disassociating this feature from the LCAP project because it was originally created for ECS and is distinct from LCAP's unique identifier requirements.

Won't Do

Details

Reporter

PO Rank

0

Front End Estimate

Large < 10 days

Front End Estimator

Front-End Confidence factor

30%

Back End Estimate

XXL < 30 days

Back End Estimator

Back-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
TestRail: Cases
TestRail: Runs