Admin control of Staff-created showcases and saved searches
When staff create showcases and then are no longer with the library, there is no way the Admin can "take over" the showcase to maintain it. The only option is to delete the showcase and re-create it. Same with saved searches. If a reference librarian has created a saved search but leaves the library, search would have to be re-created.

-
Jacinta commented
Having the ability to retain, and continue to add to, content created by staff who have left the organisation would be very beneficial. It maintains diverse viewpoints whilst saving the of time duplicating something which has already been in place.
-
Martin Boyce commented
This idea appears to be related to another one:
Ability to copy showcases and parent list/search from one staff patron to another -
Martin Boyce commented
I agree this would be very useful. We have showcases created by staff in particular roles. When staff move around, and new people take that role it would be good to be able to transfer the 'ownership' of that showcase to a different user account. We also have examples where we would like more than one staff member (i.e. user account) to be able to add and remove titles from a particular showcase, e.g. job-sharing arrangements.
I realize it is possible to have multiple staff members login to a single Vega admin account, but it's nice to be able to maintain individual Vega admin accounts so we still know who is authorized to access and edit showcases. Maybe there's a need for an additional role for Showcase editors that can add and remove titles from any user's lists? Or perhaps a tweak to the permissions for the Showcase Admin role that enables this?
-
Kathryn Brew commented
This would also be very helpful when giving all our staff the new "vega/staff user" accounts instead of "patron user" accounts. We have created a lot of showcases attached to our personal library cards, and with the new vega-specific admin accounts, it will be a pain to recreate all those showcases.
Transferring ownership or even creating a system where showcases can be shared rather than credited to an individual would be nice. In a consortium, we would need to be able to group users by library, and then they could have shared control over showcases created within their group, or something like that.