Skip to:

Skip to Jira Navigation
Skip to Side Navigation
Skip to Main Content

CRUD affiliations and related permissions of a given user

Description

Current situation or problem: Users are not able to have multiple affiliations with unique permissions for different libraries in a consortia

In scope

Allow user with the appropriate permissions to view user records and identify their affiliation(s)

Allow user with the appropriate permissions to Add/edit the affiliation(s) and associated permissions of a given user record

Display all permissions for each affiliation the user has

Out of scope

Update permissions for more that one affiliation with a single action

Update permissions for a single affiliation for more than one user with a single action

Use case(s)

see linked document for more details

Links to additional info

see linked document for more details

Questions

Priority

P1

Labels

Fix versions

Poppy (R2 2023)

Development Team

Thunderjet

Assignee

Dennis Bridges

Solution Architect

None

Parent

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

Parent Field Value

None

Parent Status

None

Linked work items

clones

Context switching for staff user with multiple affiliations

is defined by

Cover Consortia User Tenant associations with karate tests

View affiliation associated permissions

Assign/unassign a users affiliations

Add/Edit a users permissions for associated affiliation(s)

View a users affiliations accordion in the details pane

Success and Error toasts - Assign/unassign a users affiliations

Implement sending USER_CREATED event using transactional outbox pattern

Implement sending USER_DELETED event using transactional outbox pattern

Define DB schema for storing user and affiliation associations and create table

Implement endpoint to retrieve list of registered affiliations for a user

Implement endpoint to remove user association from a tenant

Implement endpoint to add user affiliation and shadow user

Process kafka event from mod-users to delete primary user affiliation

Process kafka event from mod-users to create primary user affiliation

Spike: Investigate an approach how to configure tenants and deploy consortia functionality

Create Primary Affiliations When Adding New Tenant to Consortium

Exception handling for Assign/unassign a users affiliations

Change unique index to use userId and tenantId

Store central tenant id for each institutional tenant in mod-consortia

Delete shadow users when real user was deleted

Populate default user permissions when creating real/shadow users

Populate admin user with predefined permissions set during adding tenant to Consortia

Create system user to support all actions during Consortia tenant setup

Setup Thunderjet rancher environment for Poppy UAT testing

Checklist

hide

TestRail: Results

Activity

Show:

Dennis Bridges October 4, 2023 at 5:09 PM

All related stories completed for code freeze

(OLD ACCOUNT) Erin Nettifee February 16, 2023 at 8:37 PM

If a library is not in a FOLIO-based consortia, they won't want to have the UX change - but the idea of seeing permissions assigned to a user is appealing. Is there a way to enable the permissions assigned to a user for libraries without adding extra stuff to the UX that they don't want? Has the Users SIG had a chance to talk about any of this yet?

Done

Details
Reporter
Dennis Bridges
PO Rank
0
Front End Estimate
Large < 10 days
Front-End Confidence factor
50%
Back End Estimate
Small < 3 days
Back-End Confidence factor
50%
Release
Poppy (R2 2023)
Rank: Cornell (Full Sum 2021)
R5
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs

Created February 9, 2023 at 6:31 PM

Updated April 25, 2024 at 4:34 PM

Resolved October 4, 2023 at 5:09 PM

TestRail: Cases

TestRail: Runs