Alma needs ti have the ability to identify bib, holdings, and item records created by individual staff operators.
The MDE shows the operator of various versions of a bib record. When a bib record is imported via an import profile that creates inventory, however, the staff operator that ran the import is not identified as the creator of the bib, holding, and/or item record. We often did Access queries in Voyager to identify bibs, holdings, or item records created or modified by particular staff members or student assistants. I can see that we could do such a report from Alma on bib record operators of versions after the initial import and I can also see in the Item history tab the operator who made changes to the item record. But I cannot find in the documentation the ability to identify the operator who ran the import, or the identity of the operator that modified the holding record. In fact, the documentation shows that the creation of a bib record via import only shows the creator as "Import" (our instance of Alma says a record we imported today via an import profile was created by ExLibris, which is equally unhelpful). Because we have multiple staff doing multiple imports every day, searching through the list under Resources/Monitor and View Imports for individual bib records to find who imported them is unrealistically time consuming. And since we change the holdings location to Withdrawn in order to distinguish such materials from deleted records that we don't want to count, we need to be able to identify holdings records modified by our student workers on particular days in order to check their work.
Marilou Hinchcliff
shared this idea
-
Marilou Hinchcliff
commented
This is similiar to idea https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/35181883-please-provide-the-way-of-knowing-the-real-pol-cre We need to be able to see who on our staff has created or modified any record in Alma even when records are created via import profiles or a job. The staff have to log in to use these functions, so it should be possible to link that log in to the operations they do in order to identify who created or modified a record via any mechanism, singly or in bulk.