Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 2) (UXPROD-4485)

[UXPROD-4207] Globally unique identifiers in consortia acquisitions Created: 17/Apr/23  Updated: 30/Nov/23  Resolved: 22/Nov/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 2)

Type: New Feature Priority: P2
Reporter: Joseph Reimers Assignee: Joseph Reimers
Resolution: Won't Do Votes: 0
Labels: LC1, ecs, unique-identifiers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-4137 Managing unique identifiers in acquis... Closed
is defined by MODCON-35 Spike: Prevent deleting real user whe... Open
is defined by MODCON-26 [BE] Add tenant code to tenant profile Closed
is defined by STCOR-721 Add auth errors handler on Login screen Closed
is defined by UICONSET-6 Add tenant code to tenant profile Closed
is defined by UICONSET-61 Consortia - account for duplicate use... Closed
is defined by UIAC-66 Add tenant code to acquisition unit Draft
is defined by UIAC-65 Consortia - enforce unique acquisitio... In Refinement
is defined by UICONSET-5 Settings: Enforce unique username In Refinement
is defined by UIU-2848 Prevent creation of duplicate usernam... In Refinement
Release: Ramsons (R2 2024)
Epic Link: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 2)
Front End Estimate: Medium < 5 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 30%
Back End Estimate: Large < 10 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 30%
Development Team: Thunderjet
PO Rank: 0

 Description   

Current situation or problem: In a consortium environment, certain human-readable identifiers must be unique across all tenants. The system must provide checks against creation of duplicate records, and in the event of a duplicate record, must provide an appropriate resolution.

In scope

  • User - Username
  • Acquisition Unit - Name

Out of scope

Records and/or identifiers that do not need to be unique across the consortium

Use case(s)

  1. Duplicate usernames should not exist across multiple tenants because a single user may have membership in more than one tenant. In the event a duplicate user exists, that user must be associated with its primary tenant for that session only.
  2. Duplicate acquisition unit names should not exist across multiple tenants because of the high level of risk associated with a large number of duplicate acquisition unit names when ordering is carried out by the central tenant. A duplicate acquisition unit name should never exist.

Proposed solution/stories

  1. Usernames
    1. Provide a mechanism for checking for duplicate usernames across all tenants at the point of user creation
    2. Provide a mechanism for associating duplicate usernames with specific tenants on a per-session basis at the point of user login
    3. Provide a mechanism for de-duplicating duplicate usernames
  2. Acquisition units
    1. Assign a non-editable tenant-specific prefix to all acquisition units
    2. Ensure that the prefix+acquisition unit name works with third-party integrations where appropriate

Links to additional info

Questions

  • Is there any reason NOT to use the Institution code from the Tenants setting as the prefix for acquisitions units?
  • Is there any reason we would want to disable enforced acquisitions unit uniqueness in a consortium environment? Not every consortium will need it but making it optional may add significantly to development complexity while not impacting usability.


 Comments   
Comment by Erin Nettifee [ 17/Apr/23 ]

Joseph Reimers you will also need to check for duplication when a user account is edited, as usernames can be changed after an account is created.

Comment by Joseph Reimers [ 22/Nov/23 ]

We believe existing functionality addresses the unique identifiers requirements. If any issues arise, we will create targeted features to address those use cases.

Generated at Fri Feb 09 00:38:06 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.