Cataloging/Authorities Implementation Group
3 January 2002
The group discussed the relationships between Operator IDs, Cataloging Profiles, and Cataloging Happening Locations.
The cataloging profiles are based on current job descriptions for various level staff. The profiles are currently set up to be applied system-wide. Therefore, if we have at least one catalog librarian in any cataloging happening location, that location must have a cataloging profile for "catalog librarian". If we have a catalog librarian in all 24 locations, all 24 locations would need to have that cataloging profile. If only one location has a catalog librarian, then only that one catalog happening location will have a “catalog librarian” profile.
Problem: When we have a cataloging profile with many locations, the staff person must scroll down to the correct cataloging happening location to select that location.
Question: Is there another way of assigning locations so only one appears? If not, then we might consider another way of handling cataloging profiles.
Two Ideas were discussed:
First idea: Although
more labor-intensive up front, if we created cataloging profiles for each
location, and assigned the appropriate location to that profile, the staff in
that location would only see one cataloging happening location.
Example: We could create "[Location] Catalog Librarian"s, each with the same "profile values" as our current "catalog librarian". Then each [Location] Catalog Librarian profile would be assigned only the catalog happening location from which he/she works. That way, when logging into the Voyager Cataloging module, staff would only see one location.
Although more labor-intensive up front, we could create cataloging profiles for each location. We could create "[Location] Catalog Librarian" profiles, each with the same "profile values" as our current "catalog librarian". Then each [Location] Catalog Librarian profile would be assigned only the catalog happening location from which he/she works. That way, when logging into the Voyager Cataloging module, the system would automatically log a staff person into the assigned cataloging location. The staff would not have to wade through a long list of twenty-some-odd happening locations to find their own. We would be sure to use all the profiles needed by that location. For example if a location had staff for C&T copy cataloging”, “View only” and “Catalog librarian”, we could create special profiles named for that location, using our “boiler plate” profiles, and assign the appropriate location to that profile (Cornell wishes they had gone this route).
Second idea: Do we really need 24 Cataloging Happening Locations or can we get by with fewer than five, or even one? What is the real purpose of Cataloging Happening Locations? Are they used primarily for statistics? Or are they tied to NUC codes?
[Patricia has since learned that we use our NUC suffixes primarily for billing purposes, not for statistical reasons. We currently use cataloger initials in the copy holdings statement to trace the record back to the cataloger. In Voyager the Operator ID will appear in the History Tab, along with the type of change, date and time of change. We do not necessarily need the cataloging happening location for tracing record creation]
Patricia will e-mail other Voyager locations asking how they use the information from their Cataloging Happening Locations.
Having fewer than five cataloging happening locations would streamline the login process for catalogers and reduce the setup time needed in SysAdmin.