• Article Type: General
• Product: Aleph
• Product Version: 20
• Relevant for Installation Type: Dedicated-Direct; Direct; Local; Total Care

We wanted to prohibit the addition of certain 8xx fields to our Bib records. Becasue of the size of the consortium we support, we don't want to maintain individual versions of permission.dat tables, so I relied on check_doc features.

Refer to the attached screen capture and explanation, which describes various levels of control and messaging. This illustrates various checks:

1) The 856 is allowed as a tag; but has a URL error
2) The 866 is not in check_doc_line; furthermore, it is a mandatory error
3) The 852 is defined in check_doc_line; but it is a mandatory error on a bib record
4) The 950 field is not in check_doc_line, but results in a trigger only

Tables involved:
Defining valid tags: check_doc_line
General errors: check_doc (in the a-tree)
Triggers and mandatory checks: check_doc_mandatory

To isolate individual fields which can not be used (or must be used):
check_doc_doc …. Example as illustrated above:
D XX 6200 LDR## Y 852## N
D XX 6200 LDR## Y 866## N

Create error message for 6200:
check_doc.eng …. Example as illustrated above:
6200 L Do not use MARC Holdings fields on a Bibliographic Record.
[this error message should then be placed in check_doc_mandatory as a mandatory condition]

[SUNY OLIS, 2/13/08]

Resolution:
See attachment