- Article Type: General
- Product: Aleph
- Product Version: 16.02
I've been receiving complaints that sites can not update cataloging records because a higher level cataloger touched the record. When I check the record, I see that BATCH-UPD has a high cataloger level.
I suspect one of two things -- BATCH-UPD has a cataloging level being set somewhere, but where? (could you point me to the right table)
BATCH-UPD takes it's cataloging level from the person who is running the cataloging process. If this is true, can you tell me how I may instruct folks to run batch processing so that someone with a 90 level does not cut off someone from a 50 level from doing catalog maintenance on the batch-updated record?
[Note: "BATCH-UPD" is either ue_01 (indexing daemon) or p_manage_21 (global change).]
In version 16.02-up, the Cataloger level of a BATCH-UPD CAT record is coming from the Cataloger level of the last preceding *actual* cataloger -- which is as it should be: these processes should not and do not change the Cataloger level.
- Article last edited: 10/8/2013