CRUD for Teams and addition of teams assignment to objects in various FOLIO apps (UXPROD-1147)

[UXPROD-3680] Ability to create Teams for the User app, and assign users, record type, organizations to them. Created: 27/May/22  Updated: 20/Jun/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: CRUD for Teams and addition of teams assignment to objects in various FOLIO apps

Type: New Feature Priority: P3
Reporter: Ann-Marie Breaux (Inactive) Assignee: Amelia Sutton
Resolution: Unresolved Votes: 0
Labels: crossrmapps, usermanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-1147 CRUD for Teams and addition of teams ... In Progress
Relates
relates to UXPROD-872 Consortia/Multiple Libraries (Single ... Draft
Epic Link: CRUD for Teams and addition of teams assignment to objects in various FOLIO apps
Rank: Cornell (Full Sum 2021): R5

 Description   

Purpose: FOLIO Administrators in multi-library environments need the ability to create User records that are the domain of a certain library within the tenant.

High-Level Requirements:

  • Create multiple teams
  • Ability to assign users to more than one User team
  • Ability to assign users to teams
  • Ability to assign more than one team to an User record
  • Ability to assign task regulated by individual permissions to teams, e.g. View-only, Create, Edit, Delete, Mark for deletion


 Comments   
Comment by Thomas Trutt [ 14/Jul/22 ]

Q: was the idea of this ticket to creating teams just for Tech Services areas or was this a larger idea that could be used for grouping circulation departments and staff? I could see from a RA perspective that this would be very useful for managing FTE and Student Employees.

Comment by Dennis Bridges [ 07/Dec/22 ]

Making note that we discussed use cases with the User management SIG today.

Summary notes:
Operator use case: User is working at a speific service point and may work part time at others. This user should have a limited ability to do the following depending on the service point they are working at.

  • - Create Edit user records
  • - Update prefered name
  • - Change department
  • - Add proxy or sponsor
  • - Edit custom fields
  • - Change expiration
  • - Create and edit recquests
  • - Cancel requests
  • - Move requests
  • - Change request type
  • - Re-order request que
  • - CRUD fines
  • - CRUD Loans
  • - CRUD checkin and chekout

User can make mistakes when at unfamiliar station

  • - User may override a fine that they aren’t permitted by policy to do so. As they are not aware of that this policy is different for the Business library.
  • - They might create patrons

There is a circulation desk in the library where you can not check anything out.

  • - Supervisory staff might be able to check things out there
  • - Regular staff would be able to work there but not check things out from there. They could check things out else where.
  • - Item policy would prevent in general but user are able to override. Only some should be able to override.

Users can participate in multiple areas of the system and should exhibit certain behavior in these contexts.

  • I would expect to have overlapping teams: 1 team for main counter staff in campus/library 1, 1 team for main counter staff in campus/library 2, 1 team for reading room staff in library 1, 1 team for heads of circulation in both libraries, 1 team for ill staff, etc. etc. Some users would belong to several teams. This could be used for assigning tasks.
Comment by Lloyd Chittenden [ 19/Dec/22 ]

Our use case is managing multiple libraries on a single tenant. Specifically the school district. The student privacy laws in this state are very strict. If we were running the school district's libraries on a single FOLIO server, we would need to be able to prevent a school librarian at one school from viewing the patron records for students at all the other schools. On the other hand the staff at the central district office would need to be able to see and work with everyone's library records.

We would also want to prevent them from editing each other's items and holdings while sharing instances, but that's less critical. The privacy thing is a show stopper for using FOLIO in this case.

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