• Article Type: General
• Product: Aleph
• Product Version: 20

Description:
On many occasions, when our catalogers save a record in Aleph, keeping it open in the Cataloging module editor, and then make an additional change, the record won't re-file with new edits. Instead, a message pops up in red letters with an exlamation point that so-and-so (cataloger's name or initials) already updated the record, along with time and date stamp, and message that it will saved on local drive only.

In order to work around this, we have to copy the record, close it, then superimpose the copied record onto the penultimate (server-based) version, which results in duplicated OWN field, one of which must then be deleted, and then re-filed.

Shouldn't we be able to make as many edits as we want while the record is open in the editor?

Resolution:
In the screenshot you sent, the 050 looks like this:

050 4 |bDK32.
|b.S88 2011

I assume that this is not what the cataloger entered in....

The situation is that described in KB 8192-8007 -- the difference being that the "Cataloger" is not "BATCH-UPD", but, rather, the username of the Cataloger doing the update. But the handling of the problem is the same as KB 8192-8007.

• Article last edited: 10/8/2013