Differences
This shows you the differences between two versions of the page.
help:validationcols [2024/02/09 18:55] Rick [Validation table column definitions and examples] |
help:validationcols [2024/02/09 20:35] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Validation table column definitions and examples ====== | ||
- | |||
- | The files used to make the validation tables for MARC Report are now generally available under \\ | ||
- | a [[https:// | ||
- | the suggested attribution statement is: | ||
- | MARC Report Validation Table (c)1999-2024 | ||
- | by Richard Fritz and Deborah Fritz is licensed under CC BY-NC-SA 4.0 | ||
- | |||
- | Links to the primary tables follow. These tables are current with version 261 of the program. | ||
- | |||
- | NB. If opening these files in Excel, it will attempt to remove leading zeroes. \\ | ||
- | There should be a pop-up advising of this behavior--**Be sure to respond " | ||
- | |||
- | * [[https:// | ||
- | * [[https:// | ||
- | * [[https:// | ||
- | |||
- | ===== Overview ===== | ||
- | |||
- | The validation table format is: one row for each content designator (the latter being any tag, fixed field value, tag indicator value, or subfield value). | ||
- | |||
- | |||
- | There are 15 columns in each row, labelled as follows: | ||
- | - TAG | ||
- | - POS | ||
- | - LEN | ||
- | - TYPE | ||
- | - CODE | ||
- | - IND1 | ||
- | - IND2 | ||
- | - SUBF | ||
- | - DESC1 | ||
- | - DESC2 | ||
- | - DESC3 | ||
- | - REP | ||
- | - CAT | ||
- | - MSG | ||
- | - EXP | ||
- | |||
- | These columns are documented in detail below. | ||
- | ===== General notes ===== | ||
- | |||
- | * The first row for each MARC Tag section in the validation table is dubbed the '//Tag Row//' | ||
- | |||
- | * In the instructions below, the term " | ||
- | |||
- | * The sort order of the rows in each Tag block is important. The order is alphabetic, with the following exceptions: | ||
- | * Numbers follow letters (i.e. ' | ||
- | * The fill character |, and the blank space #, precede the letters (i.e. ' | ||
- | |||
- | * This page follows the MARC21 specifications for the leader and fixed fields. Users familiar only with the OCLC display mash-up of these fields may find the following page helpful: [[https:// | ||
- | |||
- | * When adding a row for a fixed field element, columns **IND1**, **IND2**, **SUBF**, and **REP** must be empty. | ||
- | |||
- | * When adding a row for a variable field value: | ||
- | * if defining an Indicator 1 value, columns **IND2**, **SUBF**, and **REP** are empty | ||
- | * if defining an Indicator 2 value, columns **IND1**, **SUBF**, and **REP** are empty | ||
- | * if defining a Subfield value, columns **IND1** and **IND2** are empty | ||
- | |||
- | * Do __not__ enter any Unicode into the table. | ||
- | |||
- | __About the fixed fields__ | ||
- | |||
- | You will probably notice that there are a great many rows at the beginning of the table for the fixed fields. The reason for this is that many of the referenced content designators have a definiton that is dependent on the type of material being described. | ||
- | |||
- | For example, if an 007/01 is coded ' | ||
- | |||
- | To deal with this variability, | ||
- | |||
- | ---- | ||
- | \\ | ||
- | For general instructions on how to activate custom validation in MARC Report, [[help: | ||
- | |||
- | ===== Validation table Columns ===== | ||
- | |||
- | There are 15 columns for each row in a MARC Report Validation table. | ||
- | |||
- | ** 1. TAG ** | ||
- | |||
- | TAG contains the three-digit MARC TAG. For example, enter " | ||
- | |||
- | ** 2. POS ** | ||
- | |||
- | POS contains the starting offset/ | ||
- | |||
- | If not applicable (which will be the default for a variable field) enter " | ||
- | | ||
- | ** 3. LEN ** | ||
- | |||
- | LEN contains the specified length of a fixed-field element. This must be a two-digit number. For example, enter " | ||
- | |||
- | If not applicable (which will be the default for a variable field) enter " | ||
- | |||
- | | ||
- | ** 4. TYPE ** | ||
- | |||
- | TYPE contains a two-character mnemonic code in a fixed field row. | ||
- | |||
- | If not applicable (which will be the default for a variable field), TYPE is empty (but note exceptions below). | ||
- | | ||
- | For tags 000, 006, 008, TYPE must be one of the following two-letter codes: | ||
- | BK (i.e. Books) | ||
- | CF (i.e. Computer Files) | ||
- | MP (i.e. Maps) | ||
- | MU (i.e. Music) | ||
- | SE (i.e. Continuing Resources*) | ||
- | MX (i.e. Mixed Materials) | ||
- | VM (i.e. Visual Materials) | ||
- | |||
- | *For compatibility reasons, MARC Report requires the TYPE code " | ||
- | |||
- | For tag 007, TYPE must be one of the following two-letter codes: | ||
- | MP (i.e. Map) | ||
- | CF (i.e. Electronic resource) | ||
- | GL (i.e. Globe) | ||
- | TM (i.e. Tactile material) | ||
- | PR (i.e. Projected graphic) | ||
- | MC (i.e. Microform) | ||
- | NP (i.e. Nonprojected graphic) | ||
- | MO (i.e. Motion picture) | ||
- | KT (i.e. Kit) | ||
- | NM (i.e. Notated music) | ||
- | RS (i.e. Remote-sensing image) | ||
- | SR (i.e. Sound recording) | ||
- | TX (i.e. Text) | ||
- | VR (i.e. Videorecording) | ||
- | UN (i.e. Unspecified) | ||
- | | ||
- | __Exceptions: | ||
- | * In the Authorities validation table, TYPE is coded " | ||
- | * In the Holdings format validation table, TYPE is coded " | ||
- | * In the Bibliographic validation table, rows for old/ | ||
- | | ||
- | ** 5. CODE ** | ||
- | |||
- | CODE contains the defined value for a fixed field element. CODE is case-sensitive and thus far has always been entered in lowercase. The number of characters in CODE must equal the value in the corresponding LEN column. | ||
- | |||
- | CODE is typically empty for variable fields, but note the following exception. | ||
- | | ||
- | __Exceptions: | ||
- | |||
- | CODE values beginning with " | ||
- | | ||
- | ** 6. IND1 ** | ||
- | |||
- | IND1 contains a defined value for Indicator 1. Valid values are "#" | ||
- | |||
- | IND1 must be empty for a fixed field or control field. | ||
- | | ||
- | ** 7. IND2 ** | ||
- | |||
- | IND2 contains a defined value for Indicator 2. Valid values are "#" | ||
- | |||
- | IND2 must be empty for a fixed field or control field. | ||
- | | ||
- | ** 8. SUBF ** | ||
- | |||
- | SUBF contains a defined subfield code. Valid values are a-z (letters must be lowercase), and 0-9. Must be entered in alphabetical order, with numeric subfields (in numeric order) __following__ alphabetic subfields. | ||
- | |||
- | SUBF must be empty for a fixed field or control field. | ||
- | | ||
- | ** 9. DESC1 ** | ||
- | |||
- | DESC1 contains the name of the field, as given by LC in the MARC documentation (https:// | ||
- | |||
- | In MARC Report, DESC1 has always been entered in uppercase ((the reason for this may be seen when using the program' | ||
- | |||
- | For example, for each row in the bib table with TAG 504, DESC1 contains: | ||
- | BIBLIOGRAPHY, | ||
- | | ||
- | ** 10. DESC2 ** | ||
- | |||
- | The function of the DESC2 varies according to the type of content designator, but again, the string entered here is always taken from the MARC documentation site cited above. This string is entered in sentence case. | ||
- | |||
- | For the Leader and Fixed Fields, DESC2 contains the label assigned to each character position; DESC2 is repeated for each value defined for a character position. | ||
- | |||
- | For example, in the rows that enumerate the values defined for Leader position 06, DESC2 contains: | ||
- | Type of record | ||
- | |||
- | For Indicators, DESC2 contains the name of the indicator (" | ||
- | |||
- | For example, in rows that enumerate the values defined for Indicator 1 in personal name tags, DESC2 contains: | ||
- | First indicator: Type of personal name entry element | ||
- | |||
- | For Subfields, DESC2 contains the label assigned to the subfield code (without the subfield code itself). | ||
- | |||
- | For example, in the row for Tag 100, subfield $a, DESC2 contains: | ||
- | | ||
- | |||
- | DESC2 is empty in only one case: 'Tag Rows' (i.e., the first row in any Tag's sequence of rows). | ||
- | | ||
- | ** 11. DESC3 ** | ||
- | |||
- | The function of the DESC3 varies according to the type of content designator, but again, the string entered here is always taken from the MARC documentation site cited above. This string is entered in sentence case. | ||
- | |||
- | For the Leader and Fixed Fields, DESC3 contains the label assigned to each CODE defined for a position. | ||
- | |||
- | For example, the CODE and DESC3 columns for Cataloging Source (008/39) contain: | ||
- | |||
- | CODE DESC3 | ||
- | | No attempt to code | ||
- | # National bibliographic agency | ||
- | c Cooperative cataloging program | ||
- | d Other | ||
- | u Unknown | ||
- | |||
- | For Indicators, DESC3 contains the label assigned to each value defined for an Indicator. | ||
- | |||
- | For example, in rows that enumerate the values defined for Indicator 1 in personal name tags, IND1 and DESC3 contain: | ||
- | |||
- | IND1 DESC3 | ||
- | 0 | ||
- | 1 | ||
- | 2 | ||
- | |||
- | A common occurrence in variable fields is the following (example for Tag 500, columns DESC1, DESC2, and DESC3): | ||
- | |||
- | DESC1 | ||
- | GENERAL NOTE First indicator Undefined; contains a blank (#) | ||
- | GENERAL NOTE Second indicator Undefined; contains a blank (#) | ||
- | |||
- | DESC3 is always empty for subfields. | ||
- | | ||
- | ** 12. REP ** | ||
- | |||
- | For TAG and Subfield rows, the REP column contains " | ||
- | |||
- | REP is empty in all other cases. | ||
- | | ||
- | ** 13. CAT ** | ||
- | |||
- | CAT contains a one-character ' | ||
- | |||
- | CAT is empty in all other cases. | ||
- | | ||
- | ** 14. MSG ** | ||
- | |||
- | MSG contains a note which MARC Report wiil display in the ' | ||
- | | ||
- | ** 15. EXP ** | ||
- | |||
- | EXP is not implemented by MARC Report. You may enter a short note here, or leave it blank. | ||
- | | ||
- | |||
- | ---- | ||
- | \\ | ||
- | |||
- | In addition to the documentation above, another good way to learn about the validation table format used by MARC Report is to open a validation table and study it. There are many thousands of rows in the bib table, for example, and they have all been entered in a consistent order and manner. | ||
- | |||
- | ===== Examples ===== | ||
- | |||
- | Note: The examples that follow below are provided to demonstrate how to change a validation table, but they do __not__ reflect currrent MARC21 standards. | ||
- | |||
- | __Steps to add a new Tag to the table__ | ||
- | |||
- | //To add a new tag, a minimum of new four rows will be needed: one for the "//Tag row//", | ||
- | |||
- | For example, let's add a new repeatable Tag 328, named " | ||
- | |||
- | __Tag row__ | ||
- | * Scroll down to the first row with a **TAG** value greater than " | ||
- | * Enter " | ||
- | * The **TYPE**, **CODE**, **IND1**, **IND2**, and **SUBF** columns must remain empty | ||
- | * Enter the name of the Tag in uppercase--" | ||
- | * The **DESC2** and **DESC3** columns must remain empty. | ||
- | * Enter " | ||
- | __Indicator rows__ | ||
- | * Insert two new rows (beneath the 328 Tag row added above) | ||
- | * Again, enter " | ||
- | * In the first new row, enter '#' | ||
- | * In the second new row, enter '#' | ||
- | * The **TYPE**, **CODE**, **SUBF**, and **REP** ((Repeatability does not apply to indicator rows)) columns must remain empty for each indicator row | ||
- | __Subfield rows__ | ||
- | * Insert a new row beneath the 328 Second Indicator row added above | ||
- | * Again, enter " | ||
- | * Enter " | ||
- | * The **TYPE**, **CODE**, **IND1**, **IND2**, and **DESC3** columns must remain empty for a subfield row. | ||
- | |||
- | When this example is complete, the table rows for the new tag " | ||
- | |||
- | {{: | ||
- | |||
- | <!-- | ||
- | __Steps to add a new Indicator 1 value to a variable field; example: Tag 521, Indicator 1 = " | ||
- | |||
- | * Insert a new row at the appropriate position: locate the Tag " | ||
- | * Enter " | ||
- | * Enter " | ||
- | * Enter " | ||
- | * The Type, Code, Ind2, and Subf columns must remain empty | ||
- | * Repeat the name of the Tag in the Desc1 column | ||
- | * Repeat the description of Indicator 1 in the Desc2 column (Eg. "First indicator: | ||
- | * Add the description for Indicator 1 = " | ||
- | * The Rep column must remain empty. | ||
- | * Optionally enter a note or definition in the Exp column (this column is not used by MARC Report at present) | ||
- | |||
- | __Steps to add a new Indicator 2 value to a variable field; example: Tag 650, Indicator 2 = " | ||
- | |||
- | * Insert a new row at the appropriate position: locate the Tag " | ||
- | * Enter " | ||
- | * Enter " | ||
- | * Enter " | ||
- | * The Type, Code, Ind1, and Subf columns must remain empty | ||
- | * Repeat the name of the Tag in the Desc1 column | ||
- | * Repeat the description of Indicator 2 in the Desc2 column (Eg. " | ||
- | * Add the description for Indicator 2 = " | ||
- | * The Rep column must remain empty. | ||
- | * Optionally enter a note or definition in the Exp column (this column is not used by MARC Report at present) | ||
- | |||
- | __Steps to add a new Subfield value to a variable field; example: Tag 882, Subfield " | ||
- | |||
- | * Insert a new row at the appropriate position: locate the Tag " | ||
- | * Enter " | ||
- | * Enter " | ||
- | * The Type, Code, Ind1, and Ind2 columns must remain empty | ||
- | * Repeat the name of the Tag in the Desc1 column | ||
- | * Add the description for Subfield " | ||
- | * The Desc3 column should remain empty. | ||
- | * Enter " | ||
- | * Optionally enter a note or definition in the Exp column (this column is not used by MARC Report at present) | ||
- | | ||
- | To illustrate a table update, let's assume the following case. A Marc Update has just been published that includes the following changes: | ||
- | | ||
- | Rename Field 348 to: | ||
- | 348 โ Notated Music Characteristics (R) | ||
- | | ||
- | Add new subfields $c and $d to field 348 as follows: | ||
- | $c โ Form of musical notation term | ||
- | | ||
- | $d โ Form of musical notation code | ||
- | | ||
- | Follow these steps to make these changes: | ||
- | | ||
- | | ||
- | * Scroll down until you reach " | ||
- | | ||
- | * To rename the field, change " | ||
- | |||
- | --> | ||
- | |||
- | ===== Exceptions ===== | ||
- | | ||
- | There are a few cases not described above, the most notable being the use of strings beginning with " | ||
- | |||
- | For example, in the 008, the bib table contains the code **$LANG** in position 35 for each bib type. These " | ||
- | |||
- | These special function designators are not customizable by the end-user. | ||
- | |||
- | If there is need to validate a MARC data element against a user-defined list of values, the following wiki page may be useful: | ||
- | [[help: | ||
- | |||
- | | ||