Forbidden error for "d" in LDR byte 5

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

Description:
Is it possible to configure check_doc tables so that entering d (for deleted record) in LDR/05 generates a forbidden error?

We don't want any other invalid values in the leader (or other fixed fields) to generate forbidden errors, we just want to prevent BIB records with 'd' in byte 5 of the leader from being saved to the server.

Resolution:
Check messages (forbidden or otherwise) for the leader are produced based on entries in the check_doc_field_ldr table. The site already had this entry in check_doc_field_ldr:

XX 005 1 acnp

Since d isn't in the list of valid values, a cataloger that enters d in that position of the LDR field will get an error message. The error message generated is type T (as defined in check_doc_mandatory), which does not prevent the cataloger from saving the record to the server with d in LDR/05. While it might be possible to change the type of message assigned to invalid LDR values to an M type error, such a change would cause all invalid values in LDR to become forbidden errors. In fact, all fixed field value errors get the same error value. And it is not clear you could even make it so only LDR fields would cause the "forbidden" error; it looks like the best you could do would be to make all "check_doc_line" errors forbidden or none of them. There is no way to get to the level of granularity that you are requesting.

• Article last edited: 10/8/2013