Some libraries may want to restrict rights for editing records according to who “owns” the records. For example, a multi-branch library may want to restrict rights so staff at one branch cannot make changes to records belonging to another branch. Or a library may limit access to bib records by collection to restrict cataloging privileges to the individuals responsible for the development of those collections.
Restricting access in this way is referred to as “record ownership.” The basic concept is this: You assign owners to records—rights for accessing or editing a record are then restricted to users who have rights for the owner assigned to the record. Users are granted rights by ownership according to the role/owner pairs assigned to groups. (For more information, see Groups.)
An ownership lets you restrict a user’s rights to a certain subset of records (or, to use database terminology, to specific rows in a table). (For example, you can restrict a user’s rights for bib records to bibs that belong to your library’s juvenile collection.) Ownerships are currently used with bibs, authorities, workforms, and user, role, and group records; they may be used with other record types in future Horizon releases.
The definition of an owner is anything you want it to be, according to the groups of records whose access you want to restrict. (For example, an owner might be a library, a branch, an individual, a group of people, a department, an item type, a collection, or group of collections.) The software does not restrict you in any way.
Record ownership is optional; however, if you choose not to use record ownership, you still need to use the default owner of “Unowned” for records that require an owner. (For information about using the Unowned ownership, see Planning Ownerships.)
© 1998-2017 Sirsi Corporation