As a Repository Manager, I want the ability to transfer ownership of sets between users so that institutional workflows, integrations, and operational processes can continue uninterrupted when staff responsibilities change.

In Alma, all users can create logical and itemized sets, but Repository Managers are responsible for overseeing and maintaining the broader set ecosystem across the institution. Repository Managers can already view all sets and delete sets created by other users, but they currently cannot reassign ownership of sets between users.

This creates operational challenges when staff leave the institution, responsibilities shift between departments, or integrations and scheduled workflows depend on sets owned by inactive users. Institutions increasingly rely on sets as shared operational infrastructure rather than personal user assets, making long-term ownership management difficult under the current model.

Current workarounds typically involve manually recreating sets, duplicating workflows, relying on shared/service accounts, or maintaining orphaned sets tied to inactive users.

Requested Functionality:
Allow Repository Managers to transfer ownership of logical and itemized sets to another user through both the Alma UI and APIs while preserving existing sharing permissions, scheduling, and configuration metadata. Support for bulk ownership reassignment during staff transitions or organizational changes would also be valuable.

Suggested API Enhancement:
Modify the existing PUT set API call to allow updating the created_by field.

Expected Benefits:
This enhancement would improve continuity for integrations and scheduled processes, reduce administrative overhead, strengthen governance of institutional assets, and reduce the number of duplicate or orphaned sets in enterprise Alma environments.