Staff user accounts: add library/organization field
To manage staff accounts across a consortium, we need to be able to associate users with each other by library. It would be very useful to have a piece of metadata for staff accounts that identifies which library(ies) they work for.
This would:
1. Make it easier to filter users when looking at the long list of all users.
2. Let people have control over the showcases created by others in their organization but not the entire system - currently, we can't let librarians publish their own showcases because we don't want them to have consortia-level control to all showcases. Something in-between is needed.
3. Allow the library name to be used as an alternative for displaying showcase creator, instead of displaying the staff member's real name.
And maybe more...
Preferably, this data would be tied to the locations in the system and carry across different Vega products and allow for more fine tuning.
Kathryn Brew
shared this idea
-
Eileen Keller
commented
This would add a much needed level of management to the staff users. A library level grouping with additional permissions would allow the libraries more control over their settings. Moving some of the management from the full consortia to the individual libraries would be helpful.
If this meant that Site Admins could only delete users from their own library, that would be a huge additional feature.
-
Kathryn Brew
commented
Our member libraries would like to be able to edit the "library info" widget themselves. The widget isn't linked to sites, so they can’t. This is another case where associating logins to locations would be useful. If users/sites/features can be linked to the list of locations, people with permissions linked to a location could edit various things, including any sites associated with that location, the library info widget, other users and showcases within that location group, closed locations, etc.