/
Gap list UM SIG

Gap list UM SIG

red = Has not been discussed or further discussion is needed.

yellow = Scheduled for discussion.

blue = Has been discussed, pending next steps

AppFunctionalityJIRAStatus and next stepsNotesUse cases+ 1 (Name/Institution)
UsersMore Granular User View Permissions

Discussed in SIG meeting 8/7/2024

To be revisited to better define requirements


Need to have more granular view/edit permissions for various parts of user records to enhance privacy. Not all staff should have permission to view user addresses and other sensitive personal information
UsersCustom Field Accordion Customization

Main Feature:

UXPROD-2491 - Getting issue details... STATUS

Related UI Cleanup:  UXPROD-4735 - Getting issue details... STATUS


Feature stories complete.

Revisit once development begins.

Scheduled for TrilliumCollected Use Cases: +1 Amelia Sutton, Five Colleges
Check OutDisplay Users Custom Fields at Check out.  UXPROD-4712 - Getting issue details... STATUS

Feature stories complete.

Revisit once development begins.


Collected Use Cases:

+1 Amelia Sutton, Five Colleges
UsersImplement OpenSearch in Users UXPROD-4915 - Getting issue details... STATUS

Draft feature completed. 

Needs to be discussed in SIG meeting, then pass to developers for cost analysis 


Need accurate result counts when searching. 
Correcting Slow Search in Users:

MODUSERS-457 - Getting issue details... STATUS

+1 Amelia Sutton, Five Colleges
UsersAllow override of failed renewal due to expired user UIU-1816 - Getting issue details... STATUS

To be discussed in a future meeting


Maybe this should be on the RA SIG gap list instead?


When a user record is inactive it is not possible to renew that user's open loans through override. Instead staff must either temporarily reactivate the user or manually adjust the due date on the loans.  

Workarounds discussed in SIG meeting on 2024-08-07 Meeting Notes


UsersShow links to Requests on user records for users with the "Requests: view" permission

Originally reported as a bug:  UIU-3190 - Getting issue details... STATUS  

Could be addressed by:  UIU-1343 - Getting issue details... STATUS

To be discussed in a future meeting

UIU-1343 was originally part of an old draft feature  UXPROD-2136 - Getting issue details... STATUS  which might be worth picking up again in the future.Users who should not be able to edit Requests still need to be able to link from a user record to that user's requestsJenny Bodenhamer (Oklahoma State University)
UsersMake it more clear which fields are being search in a User search UIU-1027 - Getting issue details... STATUS

Discussed on in the UM SIG

This is an extremely simple feature. Need to decide how we want the information presented to a user.

UsersAbility to create a user in a single shot MODUSERBL-68 - Getting issue details... STATUS Discussed on in the UM SIG

It would simplify the process for creating staff user records via the APIs


UsersAbility to Protect Fields from Being Overwritten by User Import UXPROD-242 - Getting issue details... STATUS Discussed on in the UM SIG

When an institution's external patron data is incorrect, but bulk user imports are taking place daily we need to protect a specified user from having their record updated through user import.


UsersUsers Version history / Change tracker UXPROD-5171 - Getting issue details... STATUS

Discussed on in the UM SIG


Helpful for troubleshooting issues with user loading


Related content