https://ac.bslw.com/community/wiki/api.php?action=feedcontributions&user=WikiSysop&feedformat=atomAC Wiki - User contributions [en]2024-03-29T12:46:36ZUser contributionsMediaWiki 1.23.14https://ac.bslw.com/community/wiki/index.php/Step_3.20Step 3.202022-05-31T20:16:20Z<p>WikiSysop: /* links */</p>
<hr />
<div>==JACKPHY Vernacular==<br />
The information in this section does not pertain directly to the profile steps, but it is important to your understanding of MARS 2.0 authority control processing.<br />
<br />
MARS 2.0 provides special processing for JACKPHY bibliographic records:<br />
'''J'''apanese, '''A'''rabic, '''C'''hinese, '''K'''orean, '''P'''ersian, '''H'''ebrew, '''Y'''iddish.<br />
<br />
The MARS 2.0 process is designed to preserve all characters in bibliographic records that are designated for use in MARC records, including non-Roman sets.<br />
<br />
===JACKPHY Vernacular and 880 fields===<br />
The heading text of non-Roman headings is not converted during MARS 2.0 authority control due to the lack of a standard vernacular JACKPHY authority file.<br />
<br />
The links between the vernacular headings (880) and romanized heading fields are maintained during MARS 2.0 processing.<br />
<br />
If romanized heading fields are deleted or added (e.g., due to a split) the occurrence number in the '''$6 linkage''' is modified appropriately. Similarly, the linking tag portion of the $6 linkage is modified to reflect any tag conversions in the romanized heading fields.<br />
<br />
An '''Associated Linked Field in $6 Not Found''' report (see Step 5.2, R18) is generated. This report lists all 880 fields which do not link to a romanized heading field due to incorrect data in the $6 linkage. All other 880 field data is untouched during processing.<br />
<br />
MARS 2.0 processing does not convert the romanized portions of 880 headings due to the lack of integrity of the resulting headings.<br />
<br />
However, a '''Linked Field in $6 Changed Heading''' (see Step 5.2, R86) report is available, which reports all tags that are linked to a vernacular tag with its linked romanized version of the tag changed in the MARS 2.0 process.<br />
<br />
<font size="3"><br />
'''original bib headings''':<br />
100 1 $6 880-1 $a Atiman, Adriano, <font color="red">$d ca. 1864-1956</font>.<br />
880 1 $6 100-1 $a <chinese characters for Atiman, Adriano>, $d ca. 1864-1956.<br />
<br />
'''The bibliographic heading in field 100 would match the See From tracing in the following LC''' <font color="red">n 82027709</font>:<br />
100 1 $a Atiman, Adriano, $d 1864 (ca.)-1956<br />
400 1 $a Atiman, Adriano, <font color="red">$d ca. 1864-1956</font></font><br />
<br />
MARS 2.0 converts the roman heading to the current form. The vernacular (880) heading would not be changed.<br />
<br />
<font size="3"><br />
'''The updated bibliographic record would contain the following headings and an entry would be added to report R86''':<br />
100 1 $6 880-1 $a Atiman, Adriano, <font color="red">$d 1864 (ca.)-1956</font>.<br />
880 1 $6 100-1 $a <chinese characters for Atiman, Adriano>, <font color="red">$d ca. 1864-1956</font>.</font><br />
<br />
===Diacritics in JACKPHY===<br />
For JACKPHY personal names, MARS 2.0 includes certain diacritics to enhance the matching capability.<br />
<br />
Often the only difference between two JACKPHY personal name headings is the presence or absence of a diacritic. A special JACKPHY normalization routine is used for JACKPHY bibliographic records.<br />
<br />
MARS 2.0 assumes a bibliographic record may contain JACKPHY romanized headings if at least 1 out of the following 3 criteria is present:<br />
*Specific values in an 066 '''character set presence''' field that indicate use of a JACKPHY graphic character set: '''$1''' in '''$a''' or '''$)1''' in '''$b''':<br />
**066 $a $1<br />
**066 $b $)1<br />
*'''880 alternate graphic represent''' field exists<br />
*Non-roman language codes in field 008[35-37]<br />
<br />
===Diacritics retained===<br />
When a bibliographic record is identified as a probable JACKPHY record, the following diacritics (normally disregarded due to the normalization routine) are retained in the normalized headings:<br />
*Alif<br />
*Ayn<br />
*Breve<br />
*Circumflex<br />
*Hyphen<br />
*Macron<br />
*Umlaut<br />
<br />
The preservation of these diacritics prevents matching a normalized JACKPHY personal name heading to the incorrect LC authority record.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.19Step 3.192022-05-31T20:16:07Z<p>WikiSysop: /* links */</p>
<hr />
<div>==LCSH to FAST Conversion==<br />
MARS 2.0 now has the capability of converting Library of Congress 6XX fields to FAST, where an equivalent occurs. Original LC 6XX fields will be retained and the new FAST 6XX fields will contain the proper $w source as well as the $0 URI.<br />
<br />
FAST Authority Records will be available for export should you need them.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.18Step 3.182022-05-31T20:15:55Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Deblinding XRefs==<br />
The information in this section does not pertain directly to the profile steps, but it is important to your understanding of MARS 2.0 authority control processing.<br />
<br />
LC authority records are constructed so that they are naturally '''self deblinding''':<br />
<br />
<font size="3"><br />
'''established heading''':<br />
150 $a Fishing<br />
<br />
'''see from heading''':<br />
450 $a Sport fishing<br />
<br />
'''see from also heading''':<br />
550 $a Wildlife-related recreation</font><br />
<br />
===See from xrefs===<br />
Most ILS generate a heading based on the 150 and 450 fields in the authority above:<br />
<br />
<font size="3"><br />
'''Sport fishing'''<br />
''See'' <font color="red">Fishing</font></font><br />
<br />
The See heading informs a patron searching for records using the entry term '''Sport fishing''' that '''works related to that topic''' can be found under the '''preferred term Fishing'''.<br />
<br />
This record is '''self deblinding''' since the display '''Sport fishing, See Fishing''' is not generated unless you have works cataloged under that term.<br />
<br />
If you have works cataloged under the term '''Fishing''', MARS 2.0 will include the authority record above in your authority file.<br />
<br />
If you have no works in your catalog under the topical subject heading Fishing, MARS 2.0 '''does not distribute''' the '''Fishing''' authority record to you.<br />
<br />
===See from also xrefs===<br />
In addition to the See cross-reference, most local systems will also generate a See Also display based on fields 150 and 550 in an authority record:<br />
<br />
<font size="3"><br />
'''Wildlife-related recreation'''<br />
''See also'' <font color="red">Fishing</font></font><br />
<br />
The See Also heading informs a patron searching for works related to '''Wildlife-related recreation''' that a search for the more general term '''Fishing''' should be considered.<br />
<br />
The See Also display helps patrons find works in your collection that may be related to the concept they are seeking. Whether your collection contains any works on the specific heading '''Wildlife-related recreation''', the provision of the additional entry term is beneficial to the patron.<br />
<br />
Deblinding See Also xrefs would prevent the above See Also display from being generated, usually by either deleting the 5XX xrefs from the authority records or changing the 5XX tag to a 4XX if your collection contains no works cataloged under that specific heading.<br />
<br />
MARS 2.0 staff does not recommend the removal of 5XX fields from authority records, or converting a 5XX tag.<br />
<br />
The available See Also xref in your ILS will direct the patron to the related term of Fishing found in your catalog.<br />
<br />
Then if you were to later acquire works cataloged under '''Wildlife-related recreation''', the necessary See Also display would not appear, as the underlying 550 field had been removed from the authority record. Or a See xref would be generated incorrectly indicating your catalog possessed no works on the primary heading.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.17Step 3.172022-05-31T20:15:45Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Pseudonyms==<br />
The information in this section does not pertain directly to the profile steps, but it is important to your understanding of MARS 2.0 authority control processing.<br />
<br />
Prior to the adoption of AACR2, each work was to be cataloged under the actual name of the author.<br />
<br />
All works written under the pseudonym, '''Mark Twain''', were to be cataloged under the author's actual name, '''Samuel Langhorne Clemens'''. LC authority records were constructed in such a way that all '''Mark Twain''' headings would be flipped to '''Samuel Langhorne Clemens''' during authority control processing.<br />
<br />
With the adoption of AACR2 in 1988 and its concept of bibliographic entities, works could be cataloged under the name the author chose to use.<br />
<br />
Prior to that time, works written under the pseudonym Mark Twain could not be cataloged under that name. Now, Mark Twain is an authorized heading and books penned by Mark Twain are cataloged under that name.<br />
<br />
LC has steadily added new authority records for bibliographic entities (or pseudonyms), and changed the 4XX See From xref under the author's actual name to 5XX See From Also xrefs.<br />
<br />
This effort has been essentially completed and there remain few, if any, LC name authority records that contain a pseudonym as a See From field.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.16Step 3.162022-05-31T20:15:36Z<p>WikiSysop: /* links */</p>
<hr />
<div>==JACKPHY Vernacular==<br />
The information in this section does not pertain directly to the profile steps, but it is important to your understanding of MARS 2.0 authority control processing.<br />
<br />
MARS 2.0 provides special processing for JACKPHY bibliographic records:<br />
'''J'''apanese, '''A'''rabic, '''C'''hinese, '''K'''orean, '''P'''ersian, '''H'''ebrew, '''Y'''iddish.<br />
<br />
The MARS 2.0 process is designed to preserve all characters in bibliographic records that are designated for use in MARC records, including non-Roman sets.<br />
<br />
===JACKPHY Vernacular and 880 fields===<br />
The heading text of non-Roman headings is not converted during MARS 2.0 authority control due to the lack of a standard vernacular JACKPHY authority file.<br />
<br />
The links between the vernacular headings (880) and romanized heading fields are maintained during MARS 2.0 processing.<br />
<br />
If romanized heading fields are deleted or added (e.g., due to a split) the occurrence number in the '''$6 linkage''' is modified appropriately. Similarly, the linking tag portion of the $6 linkage is modified to reflect any tag conversions in the romanized heading fields.<br />
<br />
An '''Associated Linked Field in $6 Not Found''' report (see Step 5.2, R18) is generated. This report lists all 880 fields which do not link to a romanized heading field due to incorrect data in the $6 linkage. All other 880 field data is untouched during processing.<br />
<br />
MARS 2.0 processing does not convert the romanized portions of 880 headings due to the lack of integrity of the resulting headings.<br />
<br />
However, a '''Linked Field in $6 Changed Heading''' (see Step 5.2, R86) report is available, which reports all tags that are linked to a vernacular tag with its linked romanized version of the tag changed in the MARS 2.0 process.<br />
<br />
<font size="3"><br />
'''original bib headings''':<br />
100 1 $6 880-1 $a Atiman, Adriano, <font color="red">$d ca. 1864-1956</font>.<br />
880 1 $6 100-1 $a <chinese characters for Atiman, Adriano>, $d ca. 1864-1956.<br />
<br />
'''The bibliographic heading in field 100 would match the See From tracing in the following LC''' <font color="red">n 82027709</font>:<br />
100 1 $a Atiman, Adriano, $d 1864 (ca.)-1956<br />
400 1 $a Atiman, Adriano, <font color="red">$d ca. 1864-1956</font></font><br />
<br />
MARS 2.0 converts the roman heading to the current form. The vernacular (880) heading would not be changed.<br />
<br />
<font size="3"><br />
'''The updated bibliographic record would contain the following headings and an entry would be added to report R86''':<br />
100 1 $6 880-1 $a Atiman, Adriano, <font color="red">$d 1864 (ca.)-1956</font>.<br />
880 1 $6 100-1 $a <chinese characters for Atiman, Adriano>, <font color="red">$d ca. 1864-1956</font>.</font><br />
<br />
===Diacritics in JACKPHY===<br />
For JACKPHY personal names, MARS 2.0 includes certain diacritics to enhance the matching capability.<br />
<br />
Often the only difference between two JACKPHY personal name headings is the presence or absence of a diacritic. A special JACKPHY normalization routine is used for JACKPHY bibliographic records.<br />
<br />
MARS 2.0 assumes a bibliographic record may contain JACKPHY romanized headings if at least 1 out of the following 3 criteria is present:<br />
*Specific values in an 066 '''character set presence''' field that indicate use of a JACKPHY graphic character set: '''$1''' in '''$a''' or '''$)1''' in '''$b''':<br />
**066 $a $1<br />
**066 $b $)1<br />
*'''880 alternate graphic represent''' field exists<br />
*Non-roman language codes in field 008[35-37]<br />
<br />
===Diacritics retained===<br />
When a bibliographic record is identified as a probable JACKPHY record, the following diacritics (normally disregarded due to the normalization routine) are retained in the normalized headings:<br />
*Alif<br />
*Ayn<br />
*Breve<br />
*Circumflex<br />
*Hyphen<br />
*Macron<br />
*Umlaut<br />
<br />
The preservation of these diacritics prevents matching a normalized JACKPHY personal name heading to the incorrect LC authority record.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.15Step 3.152022-05-31T20:15:24Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.15: Local Authority Master==<br />
[[Image:a3-13.png]]<br><br><br />
Sometimes a library has local authority records with local rules governing their relationship to the bibliographic record. MARS 2.0 can recognize your library’s local authority file and govern its matching criteria according to what your library needs.<br />
<br />
===Matched before national file===<br />
An example of a library using a form of a heading that is in conflict with the form chosen by LC. This occurs most often for series titles:<br />
<br />
<font size="3"><br />
'''If your library decided to use the following heading in a set of bib records''':<br />
440 0 $a West Group's tax practice series<br />
<br />
'''This is in conflict with the authorized form in the LC authority for this title''':<br />
010 $a n 00090467<br />
<font color="red">130 0 $a Tax practice series (St. Paul, Minn.)</font><br />
430 0 $a West Group's tax practice series</font><br />
<br />
A heading that matches a 4XX '''See From''' tracing in an LC authority record would convert to the authorized form in the 1XX field.<br />
<br />
To prevent this heading flip, you must provide a file of locally generated authority records against which your headings are matched '''first'''.<br />
<br />
If a heading first matches a local authority record, it will not convert based on the LC authority. No further matching occurs when a bibliographic heading matches a heading in a local authority record. The heading form established '''according to local practice''' is '''retained'''.<br />
<br />
===Matched after national file===<br />
Matching after a National file is useful for situations where the heading is special to the library and, while it may not be authorized yet by the National file, the library does not want to see the particular heading showing up in the '''Unmatched Primary Headings''' report (see Step 5.2, R07).<br />
<br />
This is especially helpful when the not-yet-authorized heading appears in multiple bibliographic records.<br />
<br />
===Local heading matching===<br />
If your library has an established MARC authority file that you want to incorporate into your MARS 2.0 master authority file, you will need to send us a MARC file of these records before we can process your bibliographic files.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.11Step 3.112022-05-31T20:14:47Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.11: Genre Form Matching==<br />
[[Image:a3-11b.png]]<br><br><br />
MARS 2.0 can match bibliographic genre form headings (655) against a variety of authority files. MARC 655 fields are available for libraries to record the genre, form, and/or physical characteristics of the materials being described.<br />
<br />
Standard published lists are used as sources for the genre and form terms. The source of each heading is designated by an abbreviation entered into '''$2 source of term'''.<br />
<br />
==Library of Congress Genre Form Terms==<br />
All LCGFT headings will have 2nd indicator '''7''', though there are still some LC genre headings with 2nd indicator '''0''' that have not yet been moved over into LCGFT. MARS 2.0 recognizes LCGFT identified by either method, and will update the identification used by the cataloged record:<br />
<br />
<font size="3"><br />
'''use of $2 in heading''':<br />
<font color="red">655 7</font> $a Fiction films $2 <font color="red">lcsh</font><br />
<br />
'''updated to lcgft 655 tag''':<br />
<font color="red">655</font> 7 $a Fiction films $2 <font color="red">lcgft</font></font><br />
<br />
LC has also added the subdivision '''Globes''' to the '''Map''' genre changes:<br />
<br />
<font size="3"><br />
651 0 $a Washington (D.C.) $v <font color="red">Pictorial maps</font>.<br />
'''changes to''':<br />
651 0 $a Washington (D.C.) $v <font color="red">Maps</font>.<br />
<font color="red">655</font> 7 $a Pictorial maps. $2 lcgft<br />
<br />
651 0 $a Ganymede (Satellite) $v <font color="red">Globes</font>.<br />
'''changes to''':<br />
651 0 $a Ganymede (Satellite) $v <font color="red">Maps</font>.<br />
<font color="red">655</font> 7 $a Globes. $2 lcgft</font><br />
<br />
===Genre form terms in topical 650 headings===<br />
Terms in '''topical subject headings''' (650) are always updated in accordance with the practice of the heading system indicated by the 2nd indicator of the field.<br />
<br />
Topical subject headings are not affected in any way by the options selected for genre form headings.<br />
<br />
Terms in '''genre form headings''' (655) are always updated in accordance with the practice of the heading system indicated by the rules governing that genre.<br />
<br />
In the example below, the 655 field has been updated based on a crossreference in an LC authority record, while the term in the 655 field has been updated based on a cross-reference in the related GSAFD authority record:<br />
<br />
<font size="3"><br />
'''Matching against''' <font color="red">LCGFT</font>:<br />
<font color="red">obsolete</font> '''655 heading''':<br />
655 0 $a <font color="red">Sitcoms (Television programs)</font><br />
<br />
<font color="red">updated</font> '''655 heading''':<br />
655 <font color="red">7</font> $a <font color="red">Situation comedies (Television programs)</font> $2 <font color="red">lcgft</font><br />
<br />
'''Matching against''' <font color="red">GSAFD</font>:<br />
<font color="red">obsolete</font>''' 655 heading''':<br />
655 7 $a <font color="red">Sitcoms</font>. $2 gsafd<br />
<br />
<font color="red">updated</font>''' 655 heading''':<br />
655 7 $a <font color="red">Comedy television programs</font>. $2 gsafd</font><br />
<br />
===Genre form update reports===<br />
Updates for genre form headings are included in '''Updated Headings''' report (see Step 5.2, R30).<br />
<br />
==AAT Authority Records==<br />
MARS 2.0 also provides authority control for genre form terms authorized for use in the '''Getty Art & Architecture Thesaurus''' (hereafter referred to as '''AAT'''):<br />
<br />
<font size="3"><br />
<font color="red">obsolete</font>''' 655 heading''':<br />
655 7 $a <font color="red">catalogs, on-line</font>. $2 aat<br />
<br />
<font color="red">updated</font>''' 655 heading''':<br />
655 7 $a <font color="red">online catalogs</font>. $2 aat</font><br />
<br />
'''Note''': ''AAT authorities also contain many extraneous subfields immediately following $a, which may present challenges to your ILS when trying to index or load the records. MARS 2.0 can strip these (uppercase alphabetic) subfields, leaving only the lowercase subfields in place.<br />
<br />
==GSAFD Authority Records==<br />
The following example shows an update for a genre term extracted from '''Guidelines on Subject Access to Individual Works of Fiction, Drama, etc''' (hereafter referred to as '''GSAFD'''):<br />
<br />
<font size="3"><br />
<font color="red">obsolete</font>''' 655 heading''':<br />
655 7 $a <font color="red">Utopias</font>. $2 gsafd<br />
<br />
<font color="red">updated</font>''' 655 heading''':<br />
655 7 $a <font color="red">Utopian fiction</font>. $2 gsafd</font><br />
<br />
==MeSH Genre Authority Records==<br />
MARS 2.0 also provides authority control for the list of genre terms authorized by the '''National Library of Medicine''' for use in 655 fields:<br />
<br />
<font size="3"><br />
<font color="red">obsolete</font>''' 655 heading''':<br />
655 7 $a <font color="red">Meeting Reports</font>. $2 mesh<br />
<br />
<font color="red">updated</font>''' 655 heading''':<br />
655 7 $a <font color="red">Congresses</font>. $2 mesh</font><br />
<br />
In 2002, a change to the MARC21 standards was authorized that allows identification of Medical genre terms either by using 2nd indicator '''7''' plus '''$2''', or by use of 2nd indicator '''2''' without '''$2'''. MARS 2.0 recognizes Medical genre terms identified by either method, and will retain the method of identification used by the cataloged record:<br />
<br />
<font size="3"><br />
'''use of $2 in 655''':<br />
655 <font color="red">7</font> $a Almanacs. $2 <font color="red">mesh</font><br />
<br />
'''updated 2nd indicator''' <font color="red">2</font>:<br />
655 <font color="red">2</font> $a Almanacs.</font><br />
<br />
==Rare Books Manuscripts Section Vocabularies==<br />
MARS 2.0 can now match against the '''Rare Books and Manuscript Section''' genre authority files (hereafter referred to as '''RBMS'''). RBMS is a set of eight different thesauri provided with the generous assistance of the '''Association of College and Research Libraries''', as well as '''Folger Shakespeare Library'''.<br />
<br />
These vocabularies provided a standardized means for retrieving special collections materials by genre, form, or by various physical characteristics that are typically of interest to researchers and special collections librarians.<br />
<br />
These thesauri are for relating materials to individuals or corporate bodies:<br />
{| border="0" cellspacing="0" cellpadding="5" style="border-collapse:collapse;"<br />
|- align="left"<br />
| rbbin || binding terms || !- align="right" | 307 records<br />
|- align="left"<br />
| rbgenr || genre terms || !- align="right" | 501 records<br />
|- align="left"<br />
| rbpap || paper terms || !- align="right" | 290 records<br />
|- align="left"<br />
| pri || printing evidence || !- align="right" | 152 records<br />
|- align="left"<br />
| rbprov || provenance evidence || !- align="right" | 82 records<br />
|- align="left"<br />
| rbpub || publishing evidence || !- align="right" | 39 records<br />
|- align="left"<br />
| rbrel || relator terms || !- align="right" | 71 records<br />
|- align="left"<br />
| rbtyp || type evidence || !- align="right" | 130 records<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==Thesaurus for Graphic Materials==<br />
The Thesaurus for Graphic Materials is a tool for indexing visual materials by subject and genre format. The thesaurus includes subject terms to index topic shown or reflected in pictures, and genre form terms to index types of photographs, prints, design drawings, ephemera, and other categories:<br />
{| border="0" cellspacing="0" cellpadding="5" style="border-collapse:collapse;"<br />
|- align="left"<br />
| gmgpc || genre terms || !- align="right" | 670 records<br />
|- align="left"<br />
| lctgm || subject terms || !- align="right" | 7,142 records<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==Faceted Access for Subject Terminology==<br />
OCLC has created an authority database for FAST headings and made this available for matching against. MARS 2.0 can process your FAST headings via our processing upon your request. The 655 fields would need to have 2nd indicator value of '''7''' and '''$2 fast''' in order for our system to process these genre headings.<br />
<br />
The FAST authority database comprises over 1.7 million authorities.<br />
<br />
FAST authorities allow for a faceted approach to listing subject headings within bibliographic records:<br />
<br />
<font size="3"><br />
<u>LCSH</u><br />
650 #0 $a American loyalists $z England.<br />
651 #0 $a United States $x History $y Revolution, 1775-1783 $v Biography.<br />
650 #0 $a Secret service $z Great Britain.<br />
650 #0 $a Painters $z United States.<br />
<br />
<u>FAST</u><br />
648 #7 $a 1775-1783. $2 fast<br />
650 #7 $a American loyalists. $2 fast<br />
611 27 $a American Revolution (1775-1783) $2 fast<br />
650 #7 $a Secret service. $2 fast<br />
650 #7 $a Painters. $2 fast<br />
651 #7 $a England. $2 fast<br />
651 #7 $a United States. $2 fast<br />
651 #7 $a Great Britain. $2 fast<br />
655 #7 $a Biography. $2 fast<br />
655 #7 $a History. $2 fast<br />
</font><br />
<br />
So each term within the original LC subject headings are broken out into a faceted network of headings. This could potentially enable discovery systems to make better links to subjects for patrons. Rather than searching for '''American loyalists in England''' patrons could search for '''American loyalists''' and then decide whether to pursue that to '''England''' or explore other countries with that term.<br />
<br />
<div style=clear:both></div><br><br />
<br />
==Cartographic Update==<br />
Backstage can update certain '''cartographic materials''' terms that exist in 650 or 651 $v subfields, as well as break out the terms into their own respective 655 field:<br />
<br />
<font size="3"><br />
<u>Original fields</u><br />
651 #0 $a Scotland <font color="red">$v Bathymetric maps</font>.<br />
651 #0 $a Scotland <font color="red">$v Globes.</font><br />
651 #0 $a Scotland <font color="red">$v Maps, Outline.</font><br />
<br />
<u>Updated fields</u><br />
651 #0 $a Scotland <font color="blue">$v Maps.</font><br />
<font color="blue">655 #7 $a Bathymetric maps $2 lcgft.</font><br />
<font color="blue">655 #7 $a Globes $2 lcgft.</font><br />
<font color="blue">655 #7 $a Outline maps $2 lcgft.</font><br />
</font><br />
<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.10Step 3.102022-05-31T20:14:36Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.10: Local Bib Subject Matching==<br />
[[Image:a3-10.png]]<br><br><br />
MARS 2.0 matches specified local subject fields against designated national subject authority headings. Many libraries create local subject fields in the 6XX field range with a 2nd indicator of '''4''', or in local 69X tags.<br />
<br />
MARS 2.0 can attempt to match the designated subject heading against a representative national heading. If it does not find a match it will then attempt to find matches in other tags represented in the subject authority file.<br />
<br />
===Search 6xx x4 against LC===<br />
[[Image:a3-10a.png]]<br><br><br />
In this option, MARS 2.0 matches the Local subject headings against LC Authority File as if the headings had a 2nd indicator of '''0''' instead of '''4'''.<br />
<br />
For those headings that match a heading in the LC Authority File, the 2nd indicator is changed from '''4''' to '''0'''. Headings that match a cross-reference in LC are flipped to the established LC form of the heading and the 2nd indicator is again changed from '''4''' to '''0''':<br />
<br />
<font size="3"><br />
'''original local bib heading''':<br />
650 <font color="red">4</font> $a <font color="red">American</font> Civil War, 1861-1865.<br />
<br />
'''updated local bib headings''':<br />
650 <font color="red">0 $a United States $x History</font> $x Civil War, 1861-1865.</font><br />
<br />
After the matching is completed, all remaining Local subject headings (i.e., those that did not match a heading in LC) are '''removed''' from the records.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.9Step 3.92022-05-31T20:14:27Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.9: Canadian Matching==<br />
[[Image:a3-9.png]]<br><br><br />
MARS 2.0 can match bibliographic headings against headings in the '''Library and Archives Canada Authority Files''' (hereafter referred to as '''Canadian'''). Canadian contains both Canadian Name and Subject authority records.<br />
<br />
The nearly '''660,000''' Canadian subject, personal, and corporate name authority records contain name headings that appear on publications catalogued for the Canadian National Bibliography and for names contributed by the National Archives of Canada and the Canadian Institute for Historical Microreproductions (CIHM). Some of the records have been authenticated by the NLC for use by the Library of Congress. <br />
<br />
===Fields matched===<br />
The following fields are matched against Canadian:<br><br />
[[Image:a3-9b.png]]<br><br />
'''Note:''' ''Only those with a 2nd indicator of 5 are Canadian Headings''<br />
<br />
===Ignore or remove without processing===<br />
Some libraries have catalogs that do not contain subject headings coded as Canadian headings. Other libraries have bibliographic records in their catalog that contain Canadian headings, but their local system is profiled to exclude them from the OPAC indexes.<br />
<br />
Most libraries in which the Canadian headings are not used and are not causing any problems for patrons choose to '''ignore''' these headings.<br />
<br />
Alternatively, you can choose to '''remove without processing''' any Canadian heading that MARS 2.0 encounters during processing.<br />
<br />
==Databases and Search Order==<br />
If you choose to have your Canadian headings processed, you also have the choice of which database to search against as well as in which order the databases should be searched. The two databases available to search are:<br />
*Canadian Authority Files<br />
*LC Authority File<br />
<br />
===Search Canadian authority file only===<br />
[[Image:a3-9b.png]]<br><br><br />
In this option, MARS 2.0 matches the Canadian headings against the Canadian Authority File. For those headings that match a heading in Canadian, the indicator remains as '''5'''.<br />
<br />
Headings that match a cross-reference in Canadian are flipped to the established form of the heading and the 2nd indicator is again retained as a '''5'''.<br />
<br />
After the matching is completed, all remaining Canadian headings (i.e., those that did not match a heading in an Canadian authority record) are '''retained''' in the records.<br />
<br />
===Search Canadian authority file against LC adult only===<br />
In the catalogs at some libraries, the presence of Canadian headings in their bibliographic records creates duplicate and sometimes confusing index entries for patrons. These libraries may wish to consider choosing this option:<br><br><br />
[[Image:a3-9c.png]]<br><br><br />
In this option, MARS 2.0 first matches the Canadian headings against the LC Authority File as if the headings had a 2nd indicator of '''0''' instead of '''5'''.<br />
<br />
For those headings that match a heading in the LC Authority File, the 2nd indicator is changed from '''5''' to '''0'''.<br />
<br />
Headings that match a cross-reference in LC are flipped to the established form of the heading and the 2nd indicator is again changed from '''5''' to '''0'''.<br />
<br />
After the matching is completed, all remaining Canadian headings (i.e., those that did not match a heading in an LC authority record) are '''retained''' in the records with the original 2nd indicator value of '''5'''.<br />
<br />
Or, you could choose that any Canadian headings that fail to match an LC authority record are '''removed''' from the bibliographic record.<br />
<br />
===Search Canadian 1st, LC 2nd===<br />
Some libraries prefer to search their Canadian authorities against the Canadian Authority File first. Any matches found will update the heading, but the 2nd indicator value will remain as '''5'''.<br />
<br />
However, unmatched Canadian authorities could then be searched against LC. Any matches found during this procedure would change the value of the 2nd indicator from '''5''' to '''0''':<br><br><br />
[[Image:a3-9d.png]]<br><br><br />
In this option, MARS 2.0 processes would retain unmatched Canadian headings, with a 2nd indicator value of 5, to be searched at a later date by the library.<br />
<br />
Matched headings for this option could either have a 2nd indicator value of '''5''' for matches found within Canadian or a 2nd indicator value of '''0''' for matches found within LC.<br />
<br />
This option is particularly useful for libraries interested in updating and retaining their Canadian headings if possible, with the option to upgrade them to LC headings if there is no match during the first pass against Canadian, as the following examples on the next page show:<br />
<br />
<font size="3"><br />
'''LC''' <font color="red">n 79102766</font>''':'''<br />
100 1 $a Atwood, Margaret Eleanor, $d 1939-<br />
400 1 $a Atwood, Margaret, $d 1939-<br />
<br />
'''canadian authority''' <font color="red">0100H2190</font>''':'''<br />
100 1 $a Atwood, Margaret, $d 1939-<br />
400 1 $a Atwood, Margaret<br />
400 1 $a Atwood, Margaret Eleanor<br />
400 1 $a Atwood, Margaret Eleanor, $d 1939-<br />
<br />
'''original canadian bib headings in sample records:'''<br />
(1) 100 1 $a Atwood, Margaret, $d 1939-<br />
(2) 700 1 $a Atwood, Margaret Eleanor, $d 1939-<br />
(3) 100 1 $a Atwood, Margaret<br />
(4) 700 1 $a Atwood, Margaret Eleanor<br />
<br />
'''The headings above would be converted as follows, based on authority match option selected.'''<br />
'''LC 1st, Canadian 2nd (LC preferred):'''<br />
(1) 100 1 $a Atwood, Margaret <font color="red">Eleanor</font>, $d 1939- LC updated heading<br />
(2) 700 1 $a Atwood, Margaret Eleanor, $d 1939- LC matched heading<br />
(3) 100 1 $a Atwood, Margaret, <font color="red">$d 1939-</font> CAN updated heading<br />
(4) 700 1 $a Atwood, Margaret, <font color="red">$d 1939-</font> CAN updated heading<br />
<br />
'''Canadian 1st, LC 2nd (Canadian preferred):'''<br />
(1) 100 1 $a Atwood, Margaret, $d 1939- CAN matched heading<br />
(2) 700 1 $a Atwood, Margaret, $d 1939- CAN updated heading<br />
(1) 100 1 $a Atwood, Margaret, <font color="red">$d 1939-</font> CAN updated heading<br />
(2) 700 1 $a Atwood, Margaret, <font color="red">$d 1939-</font> CAN updated heading</font><br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.8Step 3.82022-05-31T20:14:15Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.8: MeSH Matching==<br />
[[Image:a3-8.png]]<br><br><br />
MARS 2.0 can match bibliographic headings against headings in the '''National Library of Medicine Medical Subjects Authority File''' (hereafter referred to as '''MESH'''). The current Medical authority file contains just over '''615,000''' authority records for descriptors, qualifiers, and descriptor/qualifier combinations.<br />
<br />
===Fields matched===<br />
The following fields are matched against MESH:<br><br />
[[Image:3-9b.png]]<br><br />
'''Note:''' ''Only those with a 2nd indicator of 2 are MESH''<br />
<br />
===Ignore or remove without processing===<br />
Some libraries have catalogs that do not contain subject headings coded as MESH. Other libraries have bibliographic records in their catalog that contain MESH, but their local system is profiled to exclude them from the OPAC indexes.<br />
<br />
Most libraries in which the MESH are not used and are not causing any problems for patrons choose to '''ignore''' these headings.<br />
<br />
Alternatively, you can choose to '''remove without processing''' any MESH that MARS 2.0 encounters during processing.<br />
<br />
==Databases and Search Order==<br />
If you choose to have your MESH processed, you also have the choice of which database to search against as well as in which order the databases should be searched. The two databases available to search are:<br />
*MESH Authority File<br />
*LC Authority File<br />
<br />
===Search MeSH authority file only===<br />
[[Image:a3-8b.png]]<br><br><br />
In this option, MARS 2.0 matches MESH against MESH only. For those headings that match a heading in MESH, the indicator remains as '''2'''.<br />
<br />
Headings that match a cross-reference in MESH are flipped to the established form of the heading and the 2nd indicator is again retained as a '''2'''.<br />
<br />
After the matching is completed, all remaining MESH (i.e., those that did not match a heading in MESH) are '''retained''' in the records.<br />
<br />
===Search MeSH against LC only===<br />
In the catalogs at some libraries, the presence of MESH in their bibliographic records creates duplicate and sometimes confusing index entries for patrons. These libraries may wish to consider choosing this option:<br><br><br />
[[Image:a3-8c.png]]<br><br><br />
In this option, MARS 2.0 first matches the MESH against the LC Authority File as if the headings had a 2nd indicator of '''0''' instead of '''2'''.<br />
<br />
For those headings that match a heading in LC, the indicator is changed from '''2''' to '''0'''. Headings that match a cross-reference in LC are flipped to the established form of the heading and the 2nd indicator is again changed from '''2''' to '''0'''.<br />
<br />
After the matching is completed, all remaining MESH (i.e., those that did not match a heading in an LC authority record) are '''removed''' from the records.<br />
<br />
Or, you could choose that any MESH that fail to match an LC authority record are '''retained''' in the bibliographic record with the original 2nd indicator value of '''2'''.<br />
<br />
<font size="3"><br />
'''original bib medical heading''':<br />
650 <font color="red">2</font> $a Neoplasms.<br />
<br />
'''MARS 2.0 compares the heading against the LC Subjects file.'''<br />
'''The heading would match a cross-reference (4XX) in LC''' <font color="red">sh 850138553</font>''':'''<br />
150 $a Tumors<br />
450 $a <font color="red">Neoplasms</font><br />
<br />
'''updated bib medical heading''':<br />
650 <font color="red">0</font> $a <font color="red">Tumors</font>.</font><br />
<br />
When subject headings are converted from MESH to LC, MESH subdivisions that are not part of the matching LC authority are retained in their original form. For example, the heading below does not have an LC record for the full MESH:<br />
<br />
<font size="3"><br />
650 <font color="red">2</font> $a Neoplasms <font color="red">$x diagnosis</font>.</font><br />
<br />
The main part of the heading $a would match on the same LC authority listed above. A higher-level conversion would occur in which the $a is converted to LC, while $x is '''retained''' in its original form:<br />
<br />
<font size="3"><br />
650 <font color="red">0</font> $a Tumors <font color="red">$x diagnosis</font>.</font><br />
<br />
===Search MeSH 1st, LC 2nd===<br />
Some libraries prefer to search their MESH against the MESH Authority File first. Any matches found will update the heading, but the 2nd indicator value will remain as '''2'''.<br />
<br />
However, unmatched MESH could then be searched against LC. Any matches found during this procedure would change the value of the 2nd indicator from '''2''' to '''0''':<br><br><br />
[[Image:a3-8d.png]]<br><br><br />
In this option, MARS 2.0 processes would retain unmatched MESH, with a 2nd indicator value of '''2''', to be searched at a later date by the library (of course, '''remove unmatched''' could instead be chosen above if the library preferred that option).<br />
<br />
Matched headings for this option could '''either''' have a 2nd indicator value of '''2''' for matches found within MESH or a 2nd indicator value of '''0''' for matches found within LC.<br />
<br />
Changing the '''search order''' (LC=1, MESH=2) '''reverses the order''' in which headings are matched:<br />
<br />
<font size="3"><br />
'''original bib medical heading''':<br />
610 2<font color="red">2</font> $a Johns Hopkins University. <font color="red">$b School of Medicine</font>. $b Division of Medical Genetics.<br />
<br />
'''matches LC''' <font color="red">n 85363832</font>''':'''<br />
110 2 <font color="red">$a Johns Hopkins University. $b Division of Medical Genetics.</font><br />
410 2 $a Johns Hopkins University. $b School of Medicine. $b Division of Medical Genetics.<br />
<br />
'''updated bib MESH''':<br />
610 2<font color="red">0</font> $a Johns Hopkins University. $b Division of Medical Genetics.</font><br />
<br />
==Retain or Split Medical Subdivision Forms==<br />
[[Image:a3-8e.png]]<br><br><br />
MARS 2.0 offers you the option of retaining your MESH subdivision forms as they exist within the heading, or to split them out into a separate field: '''topical''' (650), '''geographic''' (651), or '''form''' (655):<br />
<br />
<font size="3"><br />
'''original MESH bib heading''':<br />
650 <font color="red">2</font> $a Ethics, Medical <font color="red">$x legislation</font><br />
<br />
'''updated MESH bib headings''':<br />
650 <font color="red">0</font> $a Ethics, Medical<br />
<font color="red">655 7</font> $a Legislation <font color="red">$2 mesh</font></font><br />
<br />
Currently the National Library of Medicine uses this faceted approach in LocatorPlus but combines all headings and subheadings into one string in their bibliographic utilities.<br />
<br />
===Faceted medical subdivision forms===<br />
{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse;"<br />
|- align="left"<br />
| academic dissertations || eulogies || patient information handout<br />
|- align="left"<br />
| account books || festschrift || pharmacopoeias<br />
|- align="left"<br />
| addresses || fictional works || posters<br />
|- align="left"<br />
| advertisements || funeral sermons || practice guideline<br />
|- align="left"<br />
| almanacs || guideline || price lists<br />
|- align="left"<br />
| animation || herbals || programs<br />
|- align="left"<br />
| architectural drawings || instruction || prospectuses<br />
|- align="left"<br />
| book illustrations || lecture notes || retracted publication<br />
|- align="left"<br />
| bookplates || lectures || review literature<br />
|- align="left"<br />
| broadslides || legislation || review of reported cases<br />
|- align="left"<br />
| caricatures || letter || scientific integrity review<br />
|- align="left"<br />
| consensus development conference || meta*hy analysis || sermons<br />
|- align="left"<br />
| consensus development conference, nij || newspaper article || statistics<br />
|- align="left"<br />
| database || patient information handout || technical report<br />
|- align="left"<br />
| documentaries and factual films || ephemera || unedited footage<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==MeSH Authority Control Numbers==<br />
MESH authority records carry the control number in field 001. However, some systems use the 010 field as the only control number, or include the 010 field in a system control number index:<br />
<br />
<font size="3"><br />
'''MESH control number in 001 field only''':<br />
001 D0206980D0009<br />
150 $a Duodenoscopes $x adverse effects<br />
<br />
'''MESH control number in 001 and 010 fields''':<br />
001 D0206980D0009<br />
<font color="red">010 $a D0206980D0009</font><br />
150 $a Duodenoscopes $x adverse effects</font><br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.7Step 3.72022-05-31T20:14:04Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.7: Childrens Matching==<br />
[[Image:a3-7.png]]<br><br><br />
MARS 2.0 processing can match bibliographic headings against the headings in the '''Annotated Card Program Subjects Authority File''' (hereafter referred to as '''Childrens'''). Childrens contains just over '''960''' authority records.<br />
<br />
===Fields matched===<br />
The following fields are matched against the Childrens:<br><br />
[[Image:3-8b.png]]<br><br />
'''Note:''' ''Only those with a 2nd indicator of '''1''' are Childrens Subjects''<br />
<br />
===Ignore or remove without processing===<br />
Some libraries have catalogs that do not contain subject headings coded as Childrens. Other libraries have bibliographic records in their catalog that contain Childrens headings, but their local system is profiled to exclude them from the OPAC indexes.<br />
<br />
Most libraries in which the Childrens headings are not used and are not causing any problems for patrons select '''ignore''', where MARS 2.0 ignores the Childrens headings during authority control processing.<br />
<br />
Alternatively, you may wish all Childrens subject headings with a 2nd indicator of '''1''' are removed from the bibliographic records.<br />
<br />
==Databases and Search Order==<br />
If you choose to have your Childrens headings processed, you also have the choice of which database to search against as well as in which order the databases should be searched. The two databases available to search are:<br />
*Childrens Subjects<br />
*LC [Adult] Authority File<br />
<br />
===Search Childrens authority file only===<br />
[[Image:a3-7b.png]]<br><br><br />
In this option, MARS 2.0 matches Childrens headings against Childrens only. For those headings that match a heading in Childrens, the indicator remains as '''1'''.<br />
<br />
Headings that match a cross-reference in Childrens are flipped to the established form of the heading and the 2nd indicator is again retained as a '''1'''.<br />
<br />
After the matching is completed, all remaining Childrens (i.e., those that did not match a heading in Childrens) are '''retained''' in the records.<br />
<br />
===Search Childrens against LC adult only===<br />
In the catalogs at some libraries, the presence of Childrens headings in their bibliographic records creates duplicate and sometimes confusing index entries for patrons. These libraries may wish to consider choosing this option:<br><br><br />
[[Image:a3-7c.png]]<br><br><br />
In this option, MARS 2.0 first matches Childrens headings against LC Adult as if the headings had a 2nd indicator of '''0''' instead of '''1'''.<br />
<br />
For those headings that match a heading in LC Adult, the indicator is changed from '''1''' to '''0'''.<br />
<br />
Headings that match a cross-reference in LC Adult are flipped to the established (adult) form of the heading and the 2nd indicator is again changed from '''1''' to '''0'''.<br />
<br />
After the matching is completed, all remaining Childrens headings (i.e., those that did not match a heading in LC Adult) are '''removed''' from the records.<br />
<br />
Or, you could choose that any Children’s headings that fail to match LC Adult are '''retained''' in the bibliographic record with the original 2nd indicator value of '''1'''.<br />
<br />
===Search Childrens 1st, LC adult 2nd===<br />
Some libraries prefer to search their Childrens headings against Childrens first. Any matches found will update the heading, but the 2nd indicator value will remain as '''1'''.<br />
<br />
However, unmatched Childrens headings could then be searched against LC Adult. Any matches found during this procedure would change the value of the 2nd indicator from '''1''' to '''0''':<br><br><br />
[[Image:a3-7d.png]]<br><br><br />
In this option, MARS 2.0 retains '''unmatched''' Childrens headings, with a 2nd indicator value of '''1''', to be searched at a later date by the library (of course, '''remove unmatched''' could instead be chosen above if the library preferred that option).<br />
<br />
Matched headings for this option could '''either''' have a 2nd indicator value of '''1''' for matches found within Childrens or a 2nd indicator value of '''0''' for matches found within LC Adult.<br />
<br />
This option is particularly useful for libraries interested in updating and retaining their Childrens headings if possible, with the option to upgrade them to LC Adult headings if there is no match during the first pass against the Childrens.<br />
<br />
Changing the '''search order''' (Adult 1st, Child 2nd) '''reverses the order''' in which headings are matched.<br />
<br />
==Add Juvenile Form Subdivisions to Matched Headings==<br />
[[Image:a3-7e.png]]<br><br><br />
Adding '''juvenile form subdivisions''' to '''matched headings''' will update the LC Adult matched headings with '''$v Juvenile literature''' (or whatever is specified by the library) to the heading:<br />
<br />
<font size="3"><br />
'''childrens heading''':<br />
650 <font color="red">1</font> $a Rain forests.<br />
650 <font color="red">1</font> $a Collies $v Fiction.<br />
<br />
'''matched LC Adult with''' <font color="red">juvenile form subdivisions</font>''' applied:'''<br />
650 <font color="red">0</font> $a Rain forests <font color="red">$v Juvenile literature</font>.<br />
650 <font color="red">0</font> $a Collies <font color="red">$v Juvenile fiction</font>.</font><br />
<br />
If your requirements either fall outside of these options or you have questions about Step 3.7, please contact your MARS 2.0 project manager.<br />
<br />
If there is an existing $v that contains '''juvenile''' anywhere in the subfield, then nothing is added. If there is an existing $v and it does not contain '''juvenile''', the program will lowercase the first letter of the '''last''' $v, then insert '''Juvenile''' at the beginning of that subfield.<br />
<br />
===Juvenile rules===<br />
If there is no $v in the tag, the program adds $v according to certain criteria within the Leader (LDR) fixed field. If the record is a book (LDR[06] = '''a''' or '''t'''), then the 008[33] is checked to determine what kind of '''$v Juvenile ...''' is added:<br />
*008[33] = '''1''' : add '''$v Juvenile fiction'''<br />
*008[33] = '''d''' : add '''$v Juvenile drama'''<br />
*008[33] = '''h''' : add '''$v Juvenile humor'''<br />
*008[33] = '''p''' : add '''$v Juvenile poetry'''<br />
<br />
Similarly, for software, films, music, and sound recordings each will have its own $v added according to the values in the LDR or 007 fields.<br />
<br />
For maps (LDR[06] = '''e''' or '''f'''), the program adds '''$v Maps for children''' on the end of the heading. All other formats will have '''$v Juvenile literature''' added to the heading.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.6Step 3.62022-05-31T20:13:54Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.6: Subdivision Updates==<br />
[[Image:a3-6.png]]<br><br><br />
The use of '''$v''' for form subdivisions (periodical, bibliography, etc.) was authorized in the MARC Bibliographic Format in 1995. Introduced first by NLM in MeSH headings, LC began distributing both bibliographic and authority records containing '''$v''' in February 1999.<br />
<br />
==LC Standard Form==<br />
An increasing number of authority records include subdivisions coded as subfield $v. When a heading in a bibliographic record matches an authority record heading, MARS 2.0 modifies the subfield codes to conform to those in the authority record as part of the matching process:<br />
<br />
<font size="3"><br />
'''original form''':<br />
650 0 $a English literature $x History and criticism <font color="red">$x</font> Periodicals.<br />
<br />
'''new form''':<br />
650 0 $a English literature $x History and criticism <font color="red">$v</font> Periodicals.</font><br />
<br />
<br />
===Preservation===<br />
Many libraries have begun coding form subdivisions as $v in their new catalog records. MARS 2.0 can preserve your $v codes in subject headings regardless of the existence of an LC authority record for the heading:<br />
<br />
<font size="3"><br />
'''original heading''':<br />
650 0 $a Stocks $x Prices <font color="red">$v</font> Databases.<br />
<br />
'''authority record''' <font color="red">sh 87003018</font>''':'''<br />
650 0 $a Stocks $x Prices <font color="red">$x</font> Databases.</font><br />
<br />
<br />
If you '''preserve existing $v''', the original $v will be retained even though the LC authority record codes '''databases''' as $x. The heading on the bibliographic record would be your original heading:<br />
<br />
<font size="3"><br />
650 0 $a Stocks $x Prices <font color="red">$v</font> Databases.</font><br />
<br />
<br />
===Update headings===<br />
You can also elect to have all form subdivisions coded as $v:<br />
<br />
<font size="3"><br />
'''original heading''':<br />
650 0 $a Stocks $x Prices '''$x''' Databases.<br />
<br />
'''authority record''' <font color="red">sh 87003018</font>''':'''<br />
650 0 $a Stocks $x Prices '''$x''' Databases.<br />
<br />
'''In this example, you have chosen''' <font color="red">update $x subdivisions to $v</font> '''regardless:'''<br />
650 0 $a Stocks $x Prices <font color="red">$v</font> Databases.</font><br />
<br />
<br />
MARS 2.0 would convert your bibliographic heading to the new $v form '''whether or not''' an authority record contained that form. MARS 2.0 programs only modify a subfield code if the subdivision meets a number of specific conditions, set by LC and MARC 21. To be eligible for updating to $v, the subdivision must be:<br />
*Part of a subject (6XX) heading<br />
*The last subfield, or last pair of subfields, in a heading<br />
<br />
Exceptions:<br />
*Eligible subfields can be followed by geographic $z<br />
*Eligible subfields can be followed by $x containing a language<br />
<br />
Other exceptions are also supported by the MARS 2.0 $v system and are found in our programming set of rules. The MARS 2.0 staff has made many additional changes to other MARS 2.0 tables so that obsolete subdivisions will be updated to the correct $v form. If you have a question about a particular $v conversion, please contact your MARS 2.0 project manager.<br />
<br />
MARS 2.0 programs apply an extensive table of over a thousand form subdivisions consisting of both single and multiple subdivisions to $v processing. This table was developed based on LC and MARC 21 form subdivision documents, plus analysis of library headings by the MARS 2.0 Authority Control team. Subdivisions that can be correctly coded by either a $x or $v are always converted to a $v if this option is selected.<br />
<br />
A '''Subfield Code Changed from $x to $v''' report is generated for all headings containing ambiguous headings that have been flipped to $v (see Step 5.2, R39).<br />
<br />
Two subdivisions that appear at the end of a heading are not converted to $v unless the pair has been included as an acceptable combination in the form subdivision table.<br />
<br />
In this example, both '''gazetteers''' and '''bibliography''' can be form subdivisions:<br />
<br />
<font size="3"><br />
'''original heading''':<br />
651 0 $a France <font color="red">$x</font> Gazetteers <font color="red">$x</font> Bibliography.</font><br />
<br />
<br />
The combination of these two $x subdivisions, however, is not an authorized form subdivision, so only the final subdivision would be recoded as $v:<br />
<br />
<font size="3"><br />
651 0 $a France $x Gazetteers <font color="red">$v</font> Bibliography.</font><br />
<br />
====Special Exception====<br />
Please note that even if you choose not to '''Update $x subdivisions to $v''', there is still a chance that an authority match against LC will make that update for your heading. Consider the following example:<br />
<br />
<font size="3"><br />
'''original heading''':<br />
650 0 $a English language <font color="red">$x</font> Dictionaries.</font><br />
<br />
In this case, your original heading has '''$x''' and you have indicated in the profile to ''not'' update $x to $v (by leaving the option unchecked). However, there exists this LCSH authority:<br />
<br />
<font size="3"><br />
'''LC subject authority''':<br />
001 sh 85043513<br />
150 $a English language <font color="red">$v</font> Dictionaries</font><br />
<br />
Due to our NACO normalization routines, both of these headings would normalize to this:<br />
<br />
<font size="3"><br />
ENGLISH LANGUAGE $ DICTIONARIES</font><br />
<br />
Now both headings match and your original heading is updated to this:<br />
<br />
<font size="3"><br />
'''updated heading''':<br />
650 0 $a English language <font color="red">$v</font> Dictionaries.</font><br />
<br />
When you leave '''Update $x subdivisions to $v''' unchecked in the profile, this possibility of being flipped based on an authority match still exists.<br />
<br />
<br />
'''NEW for 2019''' If you desire to leave '''Update $x subdivisions to $v''' unchecked in the profile, you now have the option to PROTECT your $x from flipping based on the authority record. Until we are able to update the Online Profile, please make this request in the free-text section 3-14.<br />
<br />
<br />
==Authority Records==<br />
MARS 2.0 processes described previously in this section are applied to bibliographic headings only. Many LC authority records contain potential form subdivisions coded as $x.<br />
<br />
Both preserving $v codes you enter and having MARS 2.0 update form subdivisions to the $v code will result in bibliographic headings coded differently than the established headings in LC authority records.<br />
<br />
The following examples show some headings from bibliographic records with differing subfield coding and the form of the heading in the LC authority records, which would be distributed to the library:<br />
<br />
<font size="3"><br />
'''bib heading (cartographic material is''' <font color="red">secondary</font>'''):'''<br />
651 0 $a United States $x Maps $x Early works to 1800.<br />
<br />
'''bib heading (work''' <font color="red">containing</font>''' actual maps or reproductions):'''<br />
651 0 $a United States $v Maps $v Early works to 1800.<br />
<br />
'''authority''' <font color="red">sh 86006684</font>''' (valid for''' <font color="red">both forms</font>''' listed above):'''<br />
151 $a United States $x Maps $x Early works to 1800<br />
<br />
'''bib heading''' (work <font color="red">about</font>''' various collections of manuscripts):'''<br />
650 0 $a Manuscripts $x Collections.<br />
<br />
'''bib heading (work''' <font color="red">containing</font>''' a collection of manuscripts):'''<br />
650 0 $a Manuscripts $v Collections.<br />
<br />
'''authority''' <font color="red">sh 85080674</font>''' (valid for both forms listed above):'''<br />
150 $a Manuscripts $v Collections</font><br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.5Step 3.52022-05-31T20:13:44Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.5: Series Processing==<br />
[[Image:a3-5.png]]<br><br><br />
MARS 2.0 provides a variety of different processing options for series headings. Local library cataloging practices and local system indexing of series headings are central factors in determining which MARS 2.0 series processing option would be most effective for any particular catalog.<br />
<br />
===Traced vs untraced===<br />
A series added entry '''8XX''' is made on the record for each work in a series if it is judged to be a useful access point. When an added entry for a series is made, we say that the series is '''traced'''. The traced record can be found by performing a search for the series as a title search in the OPAC.<br />
<br />
If a series is '''untraced''' there is no added entry made for the title of the series on the records of works in that series. Those records cannot be found by performing a search for the series as a title search in the OPAC.<br />
<br />
If custom series processing is required, describe the processing and outcome for each of the 4 types of series heading fields: '''400/410/411''', '''440''', '''490/8XX''', and '''490-0'''.<br />
<br />
Series are treated as '''traced''' if:<br />
*LC authority record has field 645 $a '''t'''<br />
**'''OR'''<br />
*008[12] = '''a''' or '''b''' or '''z'''<br />
<br />
Series are treated as '''untraced''' if:<br />
*LC authority match does not have field 645 $a '''t'''<br />
**'''AND'''<br />
*008[12] = '''c'''<br />
<br />
===Current Library of Congress policy===<br />
MARS 2.0 follows current Library of Congress policy, which treats '''unmatched''' series headings in the same manner as '''untraced''' series headings. So, in the case where a series heading has no authority match, the series will be handled as if it was '''untraced''':<br />
<br />
<font size="3"><br />
'''bib series headings''':<br />
490 <font color="red">1</font> $a Press release<br />
810 0 $a Press release (United States. Mission to the United Nations) ;$v no. 4353.<br />
<br />
'''no authority match is available''':<br />
490 <font color="red">0</font> $a Press release<br />
810 0 <font color="red">removed from record</font><br />
<br />
'''or, available authority match is untraced''':<br />
490 <font color="red">0</font> $a Press release<br />
810 0 <font color="red">removed from record</font></font><br />
<br />
MARS 2.0 programs can also '''retain unmatched 8XX''' fields if desired.<br />
<br />
===Current standard series processing: post July 2008===<br />
MARS 2.0 adheres to the June 2008 MARBI announcment regarding series processing:<br />
<br />
<blockquote>June 6th 2008, MARC Proposal No. 2008-07 presented by MARBI Committee will make field 440 obsolete and will redefine the first indicator value 1 of the 490 field to mean '''series traced in 8XX field'''.</blockquote><br />
<br />
Thus, standard MARS 2.0 series processing is to convert all '''4XX/8XX''' pairs to either '''traced''' 490-1/8XX or '''untraced''' 490-0.<br />
<br />
MARS 2.0 processing also allows many varied forms of series processing. As long as you can describe what you would expect to see returned for your series headings, our MARS 2.0 staff will work with you to make that happen. <br />
<br />
===400/410/411 series statements===<br />
The pre-AACR2 400/410/411 fields serve as both '''descriptive notes''' (Series Statements) and '''access points''' (Series Added Entries). Each 400/410/411 heading is converted to the '''AACR2''' form of a separate Series Statement '''490-1 Series traced differently''' and '''8XX Series Added Entry'''.<br />
<br />
MARS 2.0 generates a parallel 800/810/811 for each 400/410/411 heading. The tag of the 4XX series statement is changed to 490 with 1st indicator value '''1''' (series traced differently).<br />
<br />
Data from the original series note is retained in field 490, while the heading in the 8XX series added entry is changed to the established form of the heading:<br />
<br />
<font size="3"><br />
'''original headings''':<br />
100 1 $a Strong, Anna Louise, $d 1885-1970.<br />
<font color="red">400</font> 11 $a Her. $t Letters from China, $v v. 2<br />
<br />
'''updated headings''':<br />
100 1 $a Strong, Anna Louise, $d 1885-1970.<br />
<font color="red">490</font> 1 $a Letters from China, $v v. 2<br />
<font color="red">800</font> 1 $a Strong, Anna Louise, $d 1885-1970 $t Letters from China ;$v v. 2.<br />
<br />
'''original headings''':<br />
490 <font color="red">1</font> $a Emma Lord mystery<br />
<font color="red">800 1 $a Daheim, Mary. $t Emma Lord mystery.</font><br />
<br />
'''updated heading''':<br />
490 <font color="red">0</font> $a Emma Lord mystery</font><br />
<br />
Since the authority record for the above example is '''untraced''' (lacks 645 $a '''t'''), the 800 field is removed and the 490-1 is changed to 490-0. MARS 2.0 series processing can '''retain untraced 8XX''' fields if desired.<br />
<br />
==Main Entry Represented by Pronoun==<br />
Special pronoun processing routines are used whenever field 8XX is generated. There are two phases of the MARS 2.0 series note processing.<br />
<br />
===4XX series note processing===<br />
If a 400/410/411 field contains a 2nd indicator with a value of '''1''' (main entry represented by pronoun), the 4XX $a data is replaced by the 1XX main entry in fields 800/810/811. The pronoun remains in resulting field 490:<br />
<br />
<font size="3"><br />
'''original headings''':<br />
110 11 $a Wisconsin. $b Legislature. $b Legislative Reference Bureau.<br />
<font color="red">410</font> 11 $a Its. <font color="red">$t</font> Research bulletin, $v 78-RB-3<br />
<br />
'''updated headings''':<br />
110 11 $a Wisconsin. $b Legislature. $b Legislative Reference Bureau.<br />
<font color="red">490</font> 1 $a Its Research bulletin, $v 78-RB-3<br />
<font color="red">810 1 $a Wisconsin. $b Legislature. $b Legislative Reference Bureau. $t Research bulletin ;$v 78-RB-3.</font></font><br />
<br />
===Pronoun series processing===<br />
In fields 400/410/411 with a 2nd indicator of '''0''' (main entry not represented by a pronoun), MARS 2.0 checks the first '''6''' characters for any of the following words: '''Its''', '''His''', '''Her''', or '''Their'''.<br />
<br />
If one of those words is found, it is replaced by the 1XX main entry in the 800/810/811 field. The pronoun remains in the resulting 490 field. Pronoun processing is not appropriate for 440 fields, as some established series titles begin with a pronoun (e.g., '''His master's voice''').<br />
<br />
==Collapsed 490/830 to 440 series statements: pre July 2008==<br />
The 440 field served the dual purposes of a '''series statement''' and a '''series added entry'''. MARS 2.0 did not change field 440 if a related series authority record was not found (i.e., the heading was '''unmatched''').<br />
<br />
Field 440 was also not changed if the series heading was not changed during the authority control process (i.e., the heading matched the established heading form as recorded in field 1XX of an authority record and the punctuation in the heading remained unchanged).<br />
<br />
If the LC authority record indicated the established form of a series heading was different than the form recorded in field 440:<br />
*The field was retagged as '''490 series statement''' with 1st indicator '''1 series traced''' differently<br />
*Field '''8XX series added entry''' was added containing the '''established form''' of the heading<br />
<br />
<font size="3"><br />
'''original heading''':<br />
440 4 $a Department of the Army pamphlet ;$v 27-50<br />
<br />
'''updated headings''':<br />
490 1 $a Department of the Army pamphlet ;$v 27-50<br />
830 0 $a <font color="red">DA pam</font> ;$v 27-50</font><br />
<br />
===Initial article series note processing: pre July 2008===<br />
The established form of series headings in LC authority records contains initial articles. To accommodate this practice, MARS 2.0 ignores initial articles '''A''' and '''An''' when matching a 440 series heading, regardless of the value in the filing indicator.<br />
<br />
If the 440 field, for example, contains the heading '''A Barna report''', the matching software automatically checks for an authority record matching the form '''Barna report'''. Additional initial articles are ignored if the filing indicator is set.<br />
<br />
In the following example, the system ignores '''The''' during matching based on the filing indicator. MARS 2.0 checks the following languages during this step: '''English''', '''French''', '''German''', '''Italian''', '''Spanish'''.<br />
<br />
<font size="3"><br />
'''original heading''':<br />
440 4 $a <font color="red">The</font> Rare book tapes. $n Series 1 ;$v 5<br />
<br />
'''updated headings''':<br />
490 1 $a The Rare book tapes. Series 1 ;$v 5<br />
830 0 $a Rare book tapes. $n Series 1 ;$v 5.<br />
<br />
'''original headings''':<br />
490 1 $a Bulletin/Maine Agricultural Experiment Station : 1975-1977<br />
810 2 $a Life Sciences and Agricultural Experiment Station. $t <font color="red">Bulletin</font>.<br />
<br />
'''authority record''':<br />
130 0 $a <font color="red">Bulletin (Life Sciences and Agriculture Experiment)</font><br />
410 2 $a Life Sciences and Agricultural Experiment Station. $t Bulletin.<br />
<br />
'''updated headings''':<br />
490 1 $a Bulletin/Maine Agricultural Experiment Station : 1975-1977<br />
810 0 $a <font color="red">Bulletin (Life Sciences and Agriculture Experiment)</font></font><br />
<br />
==Summary of 490/830 fields not reverted: post July 2008==<br />
#Expand '''440''' to '''490-1/830''' pairs<br />
#Match '''830''' during authority control<br />
#If the 830 '''matches an untraced authority''' record (645 $a '''n'''), the '''490-1/830''' pair converts to a '''490-0'''<br />
#If the 830 '''does not match''' an authority record, the '''490-1/830 remains''' in the record<br />
#If a '''match is found''', the '''490-1/830''' pair '''remains''' in the record<br />
<br />
==Summary of 490/830 fields reverted to 440: pre July 2008==<br />
#Expand '''440''' to '''490-1/830''' pairs<br />
#Match '''830''' during authority control<br />
#If the 830 '''does not match''' or if it '''matches untraced authority''' record (645 $a '''n'''), the '''490-1/830''' pair '''reverts''' to a '''490-0'''<br />
#After '''matching''', if the '''490-1''' and '''830''' are '''identical''', they are '''reverted''' back to a '''440'''<br />
#If they '''differ''', the '''490-1/830 pair remains'''<br />
<br />
==490-0 Series Statements (Series Not Traced)==<br />
Series statements for '''untraced''' series ('''490''' fields with 1st indicator '''0''') function as descriptive statements only and are not normally subject to Authority Control. Series tracing practice, however, has changed significantly over the years. LC had previously traced few series, so many series titles were recorded in a '''490 series statement''' and coded as '''series not traced''' (1st indicator '''0'''). Current practice is to trace most series. Standard MARS 2.0 series processing brings many bibliographic series statements in line with current practice.<br />
<br />
In standard MARS 2.0 series processing, a '''490-0 series not traced''' field is not changed if a related series authority record could not be found (i.e., the heading is '''unmatched''').<br />
<br />
Field 490-0 also remains unchanged if the heading matches the established heading in field 1XX of an authority record, and the authority record indicates the series should not be traced (645 $a '''n'''):<br />
<br />
<font size="3"><br />
'''original heading''':<br />
490 0 $a American Paper Institute instrumentation program report<br />
<br />
'''authority record''':<br />
130 0 $a American Paper Institute instrumentation program report<br />
645 $a <font color="red">n</font><br />
<br />
'''updated heading (<font color="red">no change</font>'''):'''<br />
490 0 $a American Paper Institute instrumentation program report</font><br />
<br />
Field 490-0 is changed to field 490/8XX if the heading matches a heading in an authority record that indicates the series should be traced (645 $a '''t'''):<br />
<br />
<font size="3"><br />
'''original heading''':<br />
490 <font color="red">0</font> $a Campbell County history and genealogy<br />
<br />
'''authority record''':<br />
100 1 <font color="red">$a Hartman, Margaret Stregel. $t Campbell County history & genealogy</font><br />
430 0 $a Campbell County history and genealogy<br />
645 $a <font color="red">t</font><br />
<br />
'''updated headings''':<br />
490 <font color="red">1</font> $a Campbell County history and genealogy<br />
800 1 <font color="red">$a Hartman, Margaret Stregel. $t Campbell County history & genealogy.</font></font><br />
<br />
==Copy All Series Processing==<br />
A special MARS 2.0 series processing option is provided for libraries that need to have all series headings recorded in 8XX fields, often due to local system indexing requirements. In the MARS 2.0 '''Copy All''' series processing option:<br />
*Field 800/810/811 '''series added entry''' is created for each pre-AACR2 field 400/410/411 '''series statement/added entry'''<br />
*Field 830 '''series added entry''' is created for each field 440 '''series statement/added entry'''<br />
*Field 830 '''series added entry''' is created for each field 490-0 '''series statement, series not traced'''<br />
*Field 830 '''series added entry''' is created for each field 490-1 '''series statement, series traced differently''' when the bibliographic record does not contain field 8XX series added entry<br />
<br />
After field 8XX '''series added entry''' has been created for each series heading, the 8XX fields are subjected to normal MARS 2.0 Authority Control. Since the goal of MARS 2.0 Copy All series processing is to provide an indexable 8XX field for every series heading, an 8XX '''series added entry''' is created for every series heading regardless of the tracing practice or match status of the headings. The 4XX field is not altered in any way.<br />
<br />
'''Note''': ''Please check with your local system vendor before selecting the Copy All option.''<br />
<br />
==Custom Series Processing==<br />
MARS 2.0 Authority Control supports additional options for processing series headings. If the series processing options described do not meet your requirements, please discuss your requirements with your MARS project manager.<br />
<br />
==Series-like phrases==<br />
There are occasions when an authority record for a "series" states that the statement that currently exists in our 490/8XX is actually a "series like phrase" and should be entered as a 500 note. MARS 2.0 has the ability to follow the authority record for these instances. <br />
<br />
You may opt to turn on the "series-like phrase" option which will default to the following:<br />
The 1XX of the authority record will be added as a quoted 500 note.<br />
The 490/8XX will be removed<br />
The authority record will be added to your authmaster<br />
<br />
We can retain the 490/8XX if desired as well as NOT add the authority record to the authmaster if that is preferred. <br />
<br />
'''To select the "series-like phrase" option, please make mention in section 3-14 of the online Authority Control profile.'''<br />
<br />
==Volume information==<br />
Backstage's default practice is to copy the $v from the 490 field into the paired 8XX field. However, you may opt to OMIT the $v from the paired 8XX whenever the authority record does not contain a 642 field.<br />
<br />
'''To select the this option, please make mention in section 3-14 of the online Authority Control profile.'''<br />
<br />
==Publisher verification==<br />
Sometimes there are identical series headings for very different series and multiple authority records may present. In order to ensure we're selecting the best possible Authority Record, MARS 2.0 Series processing will attempt to verify the publisher within the Bib record against the publisher within the authority record. If no verification can be made, the heading will be left as-is and no authority record will be selected. The heading will appear on the '''R10 Heading Matches Multiple Authority Records report'''.<br />
<br />
Most of the time, however, your series titles will only match a single authority record. Default processing will accept any single authority record that matches. However, as a NEW option, you may choose to limit the matches to only those where the publisher matches. '''To select the this option, please make mention in section 3-14 of the online Authority Control profile.'''<br />
<br />
To make this improved matching work as best we can we’ve taken a few things into consideration. First, sometimes publishers don’t use their full names and use only a single word; we’ve included a protocol to catch some of these. Second, many publishers vary with whether they are using words such as “Inc”, Pub”, “Books”, “Press”; we are removing these terms from the matching parameters. Third, we normalize “&” and “Dept” to catch forms of publisher that may use “and” or “Department”.<br />
<br />
It must be said, however, that sometimes the publishers vary too much in the way that they’re transcribed that we cannot determine from an automatic algorithm if the publisher is indeed the same. So, if you choose to only accept authority records where publisher must match, there may be some that are considered non-matches but with manual review could be identified as matches. They will appear on the R07 Unmatched Primary Headings Report and may also appear on the R00 Near Match Headings report depending on how close they are to matching.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.4Step 3.42022-05-31T20:13:32Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.4: Split Headings==<br />
[[Image:a3-4.png]]<br><br><br />
When a heading splits and becomes 2 or more headings, MARS 2.0 either replaces the obsolete heading in the bibliographic record with all of the new headings, or leaves the old heading in the record:<br />
<font size="3"><br />
'''bib subject heading''':<br />
650 0 $a <font color="red">Nurses and nursing</font> $x Effect of managed care on.<br />
<br />
'''replaced by two split headings''':<br />
650 0 $a <font color="red">Nurses</font> $x Effect of managed care on.<br />
650 0 $a <font color="red">Nursing</font> $x Effect of managed care on.</font><br />
<br />
Subfield '''$a''' matches obsolete forms of the heading (4XX fields) in 2 authority records, '''sh 85093349''' <font color="red">Nurses</font> and '''sh 85093362''' <font color="red">Nursing</font>. If a library elected to have split headings replaced by all new headings the bibliographic heading would be replaced by the 2 headings above.<br />
<br />
<br />
Additional examples:<br />
<font size="3"><br />
'''bib subject heading''':<br />
650 0 $a <font color="red">New communities</font> $z Massachusetts $z Boston Region.<br />
<br />
'''replaced by two split headings''':<br />
650 0 $a <font color="red">New towns</font> $z Massachusetts $z Boston Region.<br />
650 0 $a <font color="red">Planned communities</font> $z Massachusetts $z Boston Region.</font><br />
<br />
<font size="3"><br />
'''bib subject heading''':<br />
610 20 $a <font color="red">Vsesoi︠u︡znai︠a︡ kommunisticheskai︠a︡ partii︠a︡ (bolʹshevikov)</font> $x Purges.<br />
<br />
'''replaced by two split headings''':<br />
610 20 $a <font color="red">Vsesoi︠u︡znai︠a︡ kommunisticheskai︠a︡ partii︠a︡ (bolʹshevikov) (1991- )</font> $x Purges.<br />
610 20 $a <font color="red">Vsesoi︠u︡znai︠a︡ kommunisticheskai︠a︡ partii︠a︡ (bolʹshevikov) (1925-1952)</font> $x Purges</font><br />
<br />
Subfield '''$a''' matches variant forms of the heading (4XX fields) in multiple authority records. These variant forms are added to the MARC record.<br />
<br />
Many libraries find that patrons have difficulty distinguishing between the new variants of a split heading and often search for the concept under the incorrect term.<br />
<br />
Therefore, most libraries choose to have all split headings inserted in the bibliographic record. <br />
<br />
<br />
'''NOTE: You may opt to limit the fields affected by this heading split. For instance, if you want only 650 fields to be split, please make note in section 3-14 of the Online Profile'''<br />
<br />
<br />
===Split heading reports available===<br />
For libraries choosing to insert split headings into the bibliographic record, a '''Split Headings''' report is generated (see Step 5.2, R31).<br />
<br />
If obsolete headings should be retained, a '''Split Headings - Headings Left Unchanged''' report is generated instead (see Step 5.2, R17).<br />
<br />
===Duplicate headings===<br />
When MARS 2.0 Authority Control is completed, a small number of bibliographic records may contain duplicate headings. This can occur when a heading has been updated to a form already in the bibliographic record, or when two different headings update to the same form.<br />
<br />
MARS 2.0 resolves this by '''deduping''' all authority controlled headings to ensure that headings in your bibliographic records will be unique. MARS 2.0 deduping compares heading text character by character.<br />
<br />
For example, a 650 field with a 2nd indicator of '''0''' (LC subject heading) and a 650 field with a 2nd indicator of '''2''' (Medical subject heading) are not considered duplicates.<br />
<br />
===Unmatched headings===<br />
If the normalized bibliographic heading does not match a normalized established heading in an authority record, the heading is '''unmatched'''. An '''Unmatched Primary Headings''' report is then generated (see Step 5.2, R07). You can use the report to make additional corrections to bibliographic headings in your local system.<br />
<br />
MARS 2.0 also creates a brief authority record out of the unmatched heading and tries to match against the national authority database during '''Notification''' services (see Step 6 of the Planning Guide). If a match is then found a new authority record is delivered to the library (see '''Ongoing Services''' in Step 6 for more details).<br />
<br />
Alternatively, the MARS 2.0 staff can manually review bibliographic headings which do not match an authority record. For more details about this service, please contact your MARS 2.0 project manager.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.3Step 3.32022-05-31T20:13:21Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.3: Partial Matches==<br />
[[Image:a3-3.png]]<br><br />
===Flip 2nd indicators===<br />
During the MARS 2.0 authority matching process, partial matches are found for subject headings in which not all of the subject heading has been authorized.<br />
<br />
Frequently, enough of the subject heading has been '''validated''' to warrant changing the 2nd indicator to reflect the match found. Even though the rest of the subject heading may not match (likely due to LC not creating authority records for every possible subdivision on a subject heading), libraries can still have the 2nd indicators flipped:<br />
<br />
<font size="3"><br />
'''bib subject heading''':<br />
650 <font color="red">4</font> $a English language $x Foreign elements $x Greek $v Textbooks.<br />
<br />
'''closest match''' <font color="red">sh 85043541</font>''':'''<br />
150 $a English language $x Foreign elements<br />
<br />
'''2nd indicator changed to''' <font color="red">0</font>''' for partial match:'''<br />
650 <font color="red">0 $a English language $x Foreign elements</font> $x Greek $v Textbooks.</font><br />
<br />
'''Note''': ''Only subject headings (6XX) are candidates for having their 2nd indicator flipped when a partial match is found. Headings will also be updated when partially matched.<br />
<br />
===Example Table===<br />
Assuming you have chosen to match a certain thesaurus against another and flip 2nd indicator to match results, this table will show how that matching will work. Common examples of this include matching Juvenile or Local headings against Library of Congress headings and updating.<br />
<br />
{|border="2" cellspacing="0" cellpadding="4" width="100%"<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|&nbsp;<br />
|align = "center" bgcolor = "#A6A6A6" width="12%" colspan = "2"|'''Change Indicator on Match Rules'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%" colspan = "2"|'''Partial Subject Flip Rules'''<br />
|-<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''Match Result'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''Flip 2nd ind on match'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''No Flip 2nd ind on match'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''Allow Partial Subject Flips'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''Do not allow partial flips'''<br />
<br />
|-<br />
|'''Full Match'''<br />
|Will Flip<br />
|Will Not Flip<br />
|Will Flip<br />
|Will Flip<br />
<br />
|-<br />
|'''Partial Match'''<br />
|Depends on Partial Flip rule<br />
|Will Not Flip<br />
|Will Flip<br />
|Will Not Flip<br />
<br />
|-<br />
|'''Non Match'''<br />
|Will Not Flip<br />
|Will Not Flip<br />
|Will Not Flip<br />
|Will Not Flip<br />
<br />
|}<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.2Step 3.22022-05-31T20:13:06Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.2: Tag Flipping==<br />
[[File:ac-3-2.png]]<br><br><br />
MARS 2.0 can flip certain fields between each other during the authority matching process. Sometimes bibliographic records have been generated with information appearing in the wrong field. With '''Tag Flipping''' turned on, these fields can be set to match against different tags regardless of the information within the original field:<br />
<br />
<font size="3"><br />
'''bib headings''':<br />
650 0 $a Italy (Rome)<br />
650 0 $a European Union.<br />
<br />
'''match as tag (flip)''':<br />
<font color="red">651</font> 0 $a Italy (Rome)<br />
<font color="red">610</font> 20 $a European Union.*<br />
<br />
''*the <font color="red">European Union flip</font> will only happen if the optional 650-flip is added''</font><br />
<br />
If the authority record causes the tag flip (difference in usage between 1XX and 4XX), then tags will always be flipped regardless of any other rule. Tag flipping rules '''includes X50 to X00 flipping'''. ''Old processing rules disallowed the X50 to X00 flipping, however, with the changing rules for fictitious and legendary characters, the need to allow X50 to flip to X00 was vital.''<br />
<br />
The rule that only subjects can flip to/from X50 and X51 also applies here. The MARS 2.0 Auxilliary File will '''not''' be included in this rule.<br />
<br />
===Tag flipping rules===<br />
If Tag Flipping is marked, then the following rules apply:<br />
#If 100, 110, 111, 700, 710, 711 matches X51 (authority) and the bib tag 1st indicator is '''1''', and the field only contains '''$a''', then the tag is '''forced to X10'''<br />
#If '''$a''' contains a '''single word''' or '''initials''', no flip is allowed between X00 and X10<br />
#Only '''subjects''' can flip to '''X50''' or '''X51''' based on an authority match:<br />
##If the bib tag is 600 or 611, flip to a 610<br />
##If the bib tag is 610 and is only $a or is $a and the second subfield is $v, $x, $y, $z then the bib heading can be flipped<br />
##If the bib tag is 610 and it contains other subfields than above, it will not be allowed to flip<br />
#Tags X50 and X51 '''can''' flip between each other<br />
#Tags can '''never*''' flip from X51, '''except''' X50<br />
#Tags can '''never*''' flip to or from 655<br />
#Tags can '''never*''' flip to or from X30 '''unless''' the authority record causes the tag flip<br />
#Tags will '''never*''' flip from matches to 18X subdivision authority records<br />
#Any flips not explicitly included above are allowed: X00, X10, X11 can flip between themselves<br />
<br />
'''Note''': ''A '''Possible Invalid Tags''' report (see Step 5.2, R09) includes headings in which MARS 2.0 was programmed '''not''' to flip the tag, even though the tags in the bibliographic and authority records did match.''<br />
<br />
''For example, a 130 tag is never flipped to a 100; similarly, a 710 is never allowed to flip to a 651. The '''Tags Flipped''' report (see Step 5.2, R32) includes tags that were changed during automated processing.''<br />
<br />
''*Never say never in these rules, as we can also create a custom match rule that would allow these particular flips, upon request.''<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.1Step 3.12022-05-31T20:12:54Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.1: Generic Name Headings==<br />
[[Image:a3-1.png]]<br><br><br />
<br />
===Matching===<br />
Currently if you have a generic name heading (no date or full form of name) in your bib record and a match is found on a See reference 400 of an LC Personal Name authority record, MARS 2.0 will automatically flip the authority heading to reflect the new authority:<br />
<br />
<font size="3"><br />
'''generic bib heading''':<br />
100 10 $a Campbell, John<br />
<br />
'''finds match to authority below''':<br />
001 n2001026796<br />
100 10 $a Campbell, John, $d 1826-1910<br />
<font color="red">400 10 $a Campbell, John</font><br />
<br />
'''generic bib heading changes to''':<br />
100 10 $a Campbell, John, <font color="red">$d 1826-1910</font></font><br />
<br />
Choosing to flip on '''generic name headings''' will give you a greater match rate, but it can cause '''mismatched headings'''. MARS 2.0 allows for the flip of all name authority headings including the '''generic name heading''' if there is a match to a See reference 400 in the LC authority record.<br />
<br />
'''Please note:''' if you choose to NOT flip generic headings, this just means it will not match against a 400 in an LC authority record in order to change to authorized form in the 100. The heading WILL still attempt to match another generic name in the 100 of an authority record. The matching authority record could potentially be an '''undifferentiated''' authority record. Undifferentiated authority records will usually have an 008/32 = b or a 667 "This 1XX field cannot be used under RDA until this undifferentiated record ...". The vast majority of our clients still prefer to match against and receive these "undifferentiated" authority records, but, if you would prefer to avoid these please let us know as we have a parameter we can put into place.<br />
<br />
===Normalization and matching===<br />
Normalization of the name headings is different. All information in the personal name heading is considered when determining matches. Only '''$a''' of the name heading is removed (i.e., the delimiter and subfield, not the data within $a).<br />
<br />
Name headings are defined as bib fields 100 (along with 240/243), 600, 700, and 800. Death date and other information in the bib heading date will always be considered. A bib heading with a death date will not match against an authority heading without one.<br />
<br />
Normalization of a name heading is as follows:<br><br />
<font size="3"><br />
'''original heading''':<br />
700 $a Pinsent, John, $d 1922-<br />
<br />
'''authority record''':<br />
100 $a Pinsent, John, $d 1922-1995<br />
400 $a <font color="red">Pinsent, John,</font> $d <font color="red">1922</font><br />
<br />
'''normalized original''':<br />
700 $ PINSENT, JOHN $ 1922<br />
<br />
'''normalized authority''':<br />
100 $ PINSENT, JOHN $ 1922 1995<br />
400 $ PINSENT, JOHN $ 1922<br />
<br />
'''updated heading''':<br />
700 $a Pinsent, John, $d 1922-<font color="red">1995</font>.</font><br />
<br />
In this case, the original heading contained a birth date yet lacked a death date. However, when a valid cross-reference exists (e.g., the older form used in this example) the match can then be updated with the death date.<br />
<br />
When multiple matches occur on personal name headings, the bib heading will not be replaced with any of the matches. In the case with multiple potential authority matches, the program cannot know which one to take over the others and so the bib heading remains unchanged. The multiple potential authority matches will be reported to the user in '''Heading Matches Multiple Authority Records''' (see Step 5.2, R10).<br />
<br />
During the final phase of Authority Control, the incorrect form of the heading in the bibliographic record is replaced by the established form of the authority record. The corrected heading contains missing or changed diacritics.<br />
<br />
===Bibliographic text replaced===<br />
When a heading matches a 1XX authorized heading or a 4XX unauthorized heading in an authority record, MARS 2.0 processing:<br />
*Replaces the bibliographic heading text with the text from the 1XX field of the authority record<br />
*Replaces the second and third characters of the bibliographic tag with the second and third characters of the 1XX authority heading tag, as appropriate (see “6XX Tag Flipping” in Step 3.2 of the Planning Guide)<br />
<br />
This replacement process corrects errors in capitalization, punctuation, spacing, subfield coding and some tagging errors. MARS 2.0 ensures that the appropriate ending punctuation is supplied in the bibliographic heading.<br />
<br />
==See From Tracings==<br />
MARS 2.0 Authority Matching software looks at both the authorized (or established) form of a heading in the authority record’s 1XX field and the unauthorized form in the 4XX fields (''See From'' tracings):<br />
<br />
<font size="3"><br />
'''original bib headings''':<br />
650 0 $a Philippine American War, Philippines, 1899-1902.<br />
651 0 $a Philippines $x History $y Insurrection, 1899-1901.<br />
651 0 $a United States $x History $y Philippine Insurrection, 1899-1902.</font><br />
<br />
The normalized headings from the bibliographic records are compared to the normalized authorized 1XX and the unauthorized 4XX authority record headings.<br />
<br />
<font size="3"><br />
The headings above match headings contained in <font color="red">sh 85100792</font> - LC subject authority record:<br />
001 sh 85100792<br />
151 0 $a Philippines $x History $y Philippine American War, 1899-1902<br />
450 0 $a Filipino American War, Philippines, 1899-1902<br />
<font color="red">450 0 $a Philippine American War, Philippines, 1899-1902</font><br />
450 0 $a Philippine Insurrection, Philippines, 1899-1902<br />
<font color="red">451 0 $a Philippines $x History $y Insurrection, 1899-1901<br />
451 0 $a United States $x History $y Philippine Insurrection, 1899-1902</font><br />
<br />
The three unauthorized headings in the bibliographic record would all be replaced by the established form of the heading:<br />
<font color="red">151 0 $a Philippines $x History $y Philippine American War, 1899-1902</font><br />
<br />
MARS 2.0 then merges or deduplicates the three identical authority headings to form one heading:<br />
651 0 $a Philippines $x History $y Philippine American War, 1899-1902</font><br />
<br />
==Hierarchy==<br />
Unauthorized headings (''See From'' tracings) are often included only in the authority record for the highest level of a heading. The authority record for '''Apples''', for instance, contains the older form of the heading, '''Apple'''. The authority record for the fuller heading, '''Apples — Marketing''', however, does not contain a tracing for '''Apple — Marketing'''.<br />
<br />
Using all hierarchy levels during Authority Matching, i.e., the highest level '''Apples''' plus all fuller forms such as '''Apples — Marketing''' and '''Apples — Washington (State) — Marketing''', allows a greater number of heading updates.<br />
<br />
Normalized headings are constructed for each level of hierarchy in the heading:<br />
<font size="3"><br />
'''original bib heading''':<br />
650 0 $a <font color="red">Electronic digital computers $x Programming</font> $v Congresses.<br />
<br />
'''levels of hierarchy for this heading''':<br />
650 0 $a Electronic digital computers<br />
650 0 $a Electronic digital computers $x Programming<br />
650 0 $a Electronic digital computers $x Programming $v Congresses<br />
<br />
'''partial match to 4XX heading in LC subject''' <font color="red">sh 85107310</font>:<br />
150 0 $a Computer programming<br />
450 0 $a <font color="red">Electronic digital computers $x Programming</font><br />
<br />
'''corrected form of heading in bib record (a partial match)''':<br />
650 0 $a <font color="red">Computer programming</font> $v Congresses.</font><br />
<br />
===Constructing multiple levels of hierarchy===<br />
When constructing multiple levels of hierarchy for a heading, the shortest form of the heading that is matched against the authority file is referred to as the '''highest level''' of the heading:<br />
<br />
<font size="3"><br />
'''full heading''':<br />
700 12 $a Freud, Sigmund, $d 1856-1939. $t Selections. $f 1990<br />
<br />
'''highest level heading''':<br />
700 12 <font color="red">$a Freud, Sigmund, $d 1856-1939</font></font><br />
<br />
===Hierarchy record delivered to marc file===<br />
When a hierarchy match is found not only is the authority heading replaced with the appropriate authority record, but the hierarchal version of the authority record is delivered to your MARC authority file allowing appropriate cross references to be connected to your new heading.<br />
<br />
===Subfields representing highest level heading===<br />
MARS 2.0 drops the right-most subfield(s) in generating a higher-level heading and it stops (it has reached the highest level heading) when it encounters any subfield code in the following table:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Subfield Codes Indicating Highest Level Heading<br />
|-<br />
| 100, 400, 600, 700, 800 || a b c d q<br />
|-<br />
| 110, 410, 610, 710, 810 || a b<br />
|-<br />
| 111, 411, 611, 711, 811 || a b<br />
|-<br />
| 130, 430, 630, 730, 830 || a d<br />
|-<br />
| 440 || a<br />
|-<br />
| 650 || a c d<br />
|-<br />
| 651 || a<br />
|-<br />
| 655 || a<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==Name/Title Headings==<br />
Name/title headings, which are often coded as a $a / $t combination in either a 7XX or 6XX field, present a unique challenge. LC authority records containing the full name/title headings have been established and would be matched during normal MARS 2.0 authority matching:<br />
<br />
<font size="3"><br />
'''name/title combined headings''':<br />
600 10 <font color="red">$a Twain, Mark</font>, $d 1835-1910. <font color="red">$t Innocents abroad.</font><br />
710 1 <font color="red">$a Canada. $t Treaties, etc.</font> $d 1992 Oct. 7.</font><br />
<br />
===Name/title split and temporary headings===<br />
At other times, however, the name/title heading is split between two fields, a 1XX Main Entry and a 240 Uniform Title. In order to correctly process 1XX/240 name/title headings, temporary headings are built whenever a record contains both a 1XX and 240 field:<br />
<br />
<font size="3"><br />
'''bib headings''':<br />
100 0 <font color="red">$a Aristotle</font>.<br />
240 10 $a <font color="red">Works</font>. $l English. $f 1984<br />
<br />
'''changes to''':<br />
100 0 $a Aristotle. <font color="red">$t</font> Works</font><br />
<br />
Using normal matching, the 100 field above would match the authority record for Aristotle. There is no authority record, however, for the uniform title found in the 240 field. The two fields (100/240) are combined during the matching process only.<br />
<br />
<font size="3"><br />
The temporary MARS 2.0 autohrity heading would then match the correct LC authority record <font color="red">n 8242241</font>:<br />
100 0 <font color="red">$a Aristotle. $t Works</font>. $l English. $f 1984<br />
400 0 $a Aristotle. $t Complete works of Aristotle. $f 1984</font><br />
<br />
===Name/title tracing===<br />
Inclusion of LC authority records in a library’s record distribution is an important MARS 2.0 service. Most local systems use the 400 ''See From'' tracing in the above authority record to guide patrons from the unauthorized to the authorized heading using a display similar to the following:<br />
<font size="3"><br />
Aristotle - Complete works of Aristotle - 1984<br />
''See'' <font color="red">Aristotle - Works - English - 1984</font></font><br />
<br />
===Name/title hierarchy===<br />
Use of all levels of hierarchy also affects matching using MARS 2.0 authority name/title headings. If there is no authority record containing the complete name/title heading, any authority records for the higher levels of the heading will be matched and provided.<br />
<br />
==Usage Codes==<br />
The matching process checks the authority record heading use codes from the authority record (008 bytes 14-16 and the type of series code 008 byte 12) to ensure that the bibliographic heading has been used appropriately:<br />
<font size="3"><br />
008 [12] – Type of series<br />
008 [14] – Main or added entry<br />
008 [15] – Subject added entry<br />
008 [16] – Series added entry</font><br />
<br />
A report of the matches in which the bibliographic usage and the authority record authorized usage codes conflict is available (see [[internal link|Step 5, R11]]).<br />
<br />
==Reference Records==<br />
LC has created '''reference''' authority records, which are not authorized for use in bibliographic records. These records are identified by a value '''b''' or '''c''' in byte '''9''' of the '''008''' field. MARS 2.0 does not match bibliographic headings against an LC reference record. No heading is converted from reference authority records.<br />
<br />
==MARS 2.0 Auxiliary File==<br />
MARS 2.0 also matches bibliographic headings against authority headings in the MARS 2.0 Auxiliary File. The auxiliary file contains records with additional validated headings and additional cross-references not present in national authority files. The additional cross-references convert incorrect or obsolete forms to the authorized form of the headings. Authority records from this file are used during authority matching only and are not distributed to libraries.<br />
<br />
For example, '''concentration camps''' were previously tagged as 651 headings, with the authority records in the LC SAF. When the tagging was changed to X10 and the authority records moved to the LC NAF, no 4XX See From tracings were added to the LC authority records for the obsolete form of the heading. The MARS 2.0 staff created records in the MARS 2.0 Auxiliary File that make the following conversion:<br />
<br />
<font size="3"><br />
'''bib heading''':<br />
<font color="red">651</font> 0 $a Husum-Schwesing (<font color="red">Germany</font> : Concentration camp)<br />
<br />
'''changes to''':<br />
<font color="red">610</font> 20 $a Husum-Schwesing (Concentration camp)</font><br />
<br />
==VIAF Name/Title matching==<br />
The incorporation of the VIAF name/title matching is now part of our '''DEFAULT''' matching process for Generic Names. You may opt to turn off the VIAF matching by making your request known in the free-form text area of section 3-14 of the Authority Control profile. <br />
<br />
Our process will take your generic 100 and 700 fields that contain a $a only and will search VIAF for that form of the name. If our form of the name is found, we then compare the title within the 245$a of your Bib record against the associated "Works" for that name in VIAF. We'll then select the United States form of that name to pass formally through our Authority Matching process; the LC Authority records will be returned to you as expected and your Bibliographic Heading will be updated with the authorized form.<br />
<br />
The process for the 600 field is similar but due to the 245$a not being present as a "work" in VIAF for these name subjects, we are only searching 600 fields that have a $t present. We felt we could not accurately attempt to match a 600 without a $t in VIAF to confirm the correct form of heading.<br />
<br />
Of course, the success of this matching will only be as good as the data represented in VIAF. Through testing we've discovered that a work's title may differ slightly in different contributors' VIAF records so some names may be updated while others aren't. <br />
<br />
Any headings that do not have a match in VIAF will still go through our Authority Matching process as outlined within your profile settings (for example, checking or unchecking the "Flip generic name headings" option as discussed above).<br />
<br />
If desired, optional report '''R24 - Generic Names Flipped''' can be returned to help you review these updated headings.<br />
<br />
<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.14Step 3.142022-05-31T20:08:13Z<p>WikiSysop: WikiSysop moved page Step 3.12 to Step 3.14 without leaving a redirect</p>
<hr />
<div>==Step 3.14: Local Fields in Authority Records==<br />
[[Image:a3-12.png]]<br><br><br />
Sometimes catalogers insert fields into their local system’s authority records. Ordinarily during authority control processing, these local fields would be ignored as the authorized version would replace the authorities in the ILS.<br />
<br />
MARS 2.0 can retain your local authority fields within matching updated authorities, which are then delivered to you to overlay at your end.<br />
<br />
A $5 with a special code (e.g., a cataloger's initials, etc) is a typical stamp within the authority record that offsets field(s) inserted locally by catalogers. When MARS 2.0 finds these $5 fields, it will retain that particular field and insert it into the matched authority record:<br />
<br />
<font size="3"><br />
'''original authority from library''':<br />
001 n 50006324<br />
100 1 $a Morse, John Torrey, $d 1840-1937<br />
670 $a From his works on Thomas Jefferson, with special notes <font color="red">$5 BLW</font><br />
<br />
'''LC match with''' <font color="red">$5 local note retained</font>:<br />
001 n 50006324<br />
040 $a DLC $c DLC $d DLC<br />
100 1 $a Morse, John Torrey, $d 1840-1937<br />
400 1 $a Morse, John T. $q (John Torrey), $d 1840-1937<br />
670 $a From his works on Thomas Jefferson, with special notes <font color="red">$5 BLW</font></font><br />
<br />
After the fields have been inserted into the updated authority records, the records are returned to your institution. Next, you would overlay those authority records into your system, overwriting the copies you have with those furnished by our MARS 2.0 system.<br />
<br />
The '''local notes''' within your original authority files would be '''retained''' in the updates that are delivered by Backstage.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.14Step 3.142022-05-31T20:08:01Z<p>WikiSysop: /* Step 3.12: Local Fields in Authority Records */</p>
<hr />
<div>==Step 3.14: Local Fields in Authority Records==<br />
[[Image:a3-12.png]]<br><br><br />
Sometimes catalogers insert fields into their local system’s authority records. Ordinarily during authority control processing, these local fields would be ignored as the authorized version would replace the authorities in the ILS.<br />
<br />
MARS 2.0 can retain your local authority fields within matching updated authorities, which are then delivered to you to overlay at your end.<br />
<br />
A $5 with a special code (e.g., a cataloger's initials, etc) is a typical stamp within the authority record that offsets field(s) inserted locally by catalogers. When MARS 2.0 finds these $5 fields, it will retain that particular field and insert it into the matched authority record:<br />
<br />
<font size="3"><br />
'''original authority from library''':<br />
001 n 50006324<br />
100 1 $a Morse, John Torrey, $d 1840-1937<br />
670 $a From his works on Thomas Jefferson, with special notes <font color="red">$5 BLW</font><br />
<br />
'''LC match with''' <font color="red">$5 local note retained</font>:<br />
001 n 50006324<br />
040 $a DLC $c DLC $d DLC<br />
100 1 $a Morse, John Torrey, $d 1840-1937<br />
400 1 $a Morse, John T. $q (John Torrey), $d 1840-1937<br />
670 $a From his works on Thomas Jefferson, with special notes <font color="red">$5 BLW</font></font><br />
<br />
After the fields have been inserted into the updated authority records, the records are returned to your institution. Next, you would overlay those authority records into your system, overwriting the copies you have with those furnished by our MARS 2.0 system.<br />
<br />
The '''local notes''' within your original authority files would be '''retained''' in the updates that are delivered by Backstage.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.14Step 3.142022-05-31T20:07:47Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.12: Local Fields in Authority Records==<br />
[[Image:a3-12.png]]<br><br><br />
Sometimes catalogers insert fields into their local system’s authority records. Ordinarily during authority control processing, these local fields would be ignored as the authorized version would replace the authorities in the ILS.<br />
<br />
MARS 2.0 can retain your local authority fields within matching updated authorities, which are then delivered to you to overlay at your end.<br />
<br />
A $5 with a special code (e.g., a cataloger's initials, etc) is a typical stamp within the authority record that offsets field(s) inserted locally by catalogers. When MARS 2.0 finds these $5 fields, it will retain that particular field and insert it into the matched authority record:<br />
<br />
<font size="3"><br />
'''original authority from library''':<br />
001 n 50006324<br />
100 1 $a Morse, John Torrey, $d 1840-1937<br />
670 $a From his works on Thomas Jefferson, with special notes <font color="red">$5 BLW</font><br />
<br />
'''LC match with''' <font color="red">$5 local note retained</font>:<br />
001 n 50006324<br />
040 $a DLC $c DLC $d DLC<br />
100 1 $a Morse, John Torrey, $d 1840-1937<br />
400 1 $a Morse, John T. $q (John Torrey), $d 1840-1937<br />
670 $a From his works on Thomas Jefferson, with special notes <font color="red">$5 BLW</font></font><br />
<br />
After the fields have been inserted into the updated authority records, the records are returned to your institution. Next, you would overlay those authority records into your system, overwriting the copies you have with those furnished by our MARS 2.0 system.<br />
<br />
The '''local notes''' within your original authority files would be '''retained''' in the updates that are delivered by Backstage.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]] - [[Step 3.20|3.20]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.20Step 3.202022-05-31T20:06:56Z<p>WikiSysop: WikiSysop moved page Step 3.14 to Step 3.20 without leaving a redirect</p>
<hr />
<div>==JACKPHY Vernacular==<br />
The information in this section does not pertain directly to the profile steps, but it is important to your understanding of MARS 2.0 authority control processing.<br />
<br />
MARS 2.0 provides special processing for JACKPHY bibliographic records:<br />
'''J'''apanese, '''A'''rabic, '''C'''hinese, '''K'''orean, '''P'''ersian, '''H'''ebrew, '''Y'''iddish.<br />
<br />
The MARS 2.0 process is designed to preserve all characters in bibliographic records that are designated for use in MARC records, including non-Roman sets.<br />
<br />
===JACKPHY Vernacular and 880 fields===<br />
The heading text of non-Roman headings is not converted during MARS 2.0 authority control due to the lack of a standard vernacular JACKPHY authority file.<br />
<br />
The links between the vernacular headings (880) and romanized heading fields are maintained during MARS 2.0 processing.<br />
<br />
If romanized heading fields are deleted or added (e.g., due to a split) the occurrence number in the '''$6 linkage''' is modified appropriately. Similarly, the linking tag portion of the $6 linkage is modified to reflect any tag conversions in the romanized heading fields.<br />
<br />
An '''Associated Linked Field in $6 Not Found''' report (see Step 5.2, R18) is generated. This report lists all 880 fields which do not link to a romanized heading field due to incorrect data in the $6 linkage. All other 880 field data is untouched during processing.<br />
<br />
MARS 2.0 processing does not convert the romanized portions of 880 headings due to the lack of integrity of the resulting headings.<br />
<br />
However, a '''Linked Field in $6 Changed Heading''' (see Step 5.2, R86) report is available, which reports all tags that are linked to a vernacular tag with its linked romanized version of the tag changed in the MARS 2.0 process.<br />
<br />
<font size="3"><br />
'''original bib headings''':<br />
100 1 $6 880-1 $a Atiman, Adriano, <font color="red">$d ca. 1864-1956</font>.<br />
880 1 $6 100-1 $a <chinese characters for Atiman, Adriano>, $d ca. 1864-1956.<br />
<br />
'''The bibliographic heading in field 100 would match the See From tracing in the following LC''' <font color="red">n 82027709</font>:<br />
100 1 $a Atiman, Adriano, $d 1864 (ca.)-1956<br />
400 1 $a Atiman, Adriano, <font color="red">$d ca. 1864-1956</font></font><br />
<br />
MARS 2.0 converts the roman heading to the current form. The vernacular (880) heading would not be changed.<br />
<br />
<font size="3"><br />
'''The updated bibliographic record would contain the following headings and an entry would be added to report R86''':<br />
100 1 $6 880-1 $a Atiman, Adriano, <font color="red">$d 1864 (ca.)-1956</font>.<br />
880 1 $6 100-1 $a <chinese characters for Atiman, Adriano>, <font color="red">$d ca. 1864-1956</font>.</font><br />
<br />
===Diacritics in JACKPHY===<br />
For JACKPHY personal names, MARS 2.0 includes certain diacritics to enhance the matching capability.<br />
<br />
Often the only difference between two JACKPHY personal name headings is the presence or absence of a diacritic. A special JACKPHY normalization routine is used for JACKPHY bibliographic records.<br />
<br />
MARS 2.0 assumes a bibliographic record may contain JACKPHY romanized headings if at least 1 out of the following 3 criteria is present:<br />
*Specific values in an 066 '''character set presence''' field that indicate use of a JACKPHY graphic character set: '''$1''' in '''$a''' or '''$)1''' in '''$b''':<br />
**066 $a $1<br />
**066 $b $)1<br />
*'''880 alternate graphic represent''' field exists<br />
*Non-roman language codes in field 008[35-37]<br />
<br />
===Diacritics retained===<br />
When a bibliographic record is identified as a probable JACKPHY record, the following diacritics (normally disregarded due to the normalization routine) are retained in the normalized headings:<br />
*Alif<br />
*Ayn<br />
*Breve<br />
*Circumflex<br />
*Hyphen<br />
*Macron<br />
*Umlaut<br />
<br />
The preservation of these diacritics prevents matching a normalized JACKPHY personal name heading to the incorrect LC authority record.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.15Step 3.152022-05-31T20:06:00Z<p>WikiSysop: WikiSysop moved page Step 3.13 to Step 3.15 without leaving a redirect</p>
<hr />
<div>==Step 3.15: Local Authority Master==<br />
[[Image:a3-13.png]]<br><br><br />
Sometimes a library has local authority records with local rules governing their relationship to the bibliographic record. MARS 2.0 can recognize your library’s local authority file and govern its matching criteria according to what your library needs.<br />
<br />
===Matched before national file===<br />
An example of a library using a form of a heading that is in conflict with the form chosen by LC. This occurs most often for series titles:<br />
<br />
<font size="3"><br />
'''If your library decided to use the following heading in a set of bib records''':<br />
440 0 $a West Group's tax practice series<br />
<br />
'''This is in conflict with the authorized form in the LC authority for this title''':<br />
010 $a n 00090467<br />
<font color="red">130 0 $a Tax practice series (St. Paul, Minn.)</font><br />
430 0 $a West Group's tax practice series</font><br />
<br />
A heading that matches a 4XX '''See From''' tracing in an LC authority record would convert to the authorized form in the 1XX field.<br />
<br />
To prevent this heading flip, you must provide a file of locally generated authority records against which your headings are matched '''first'''.<br />
<br />
If a heading first matches a local authority record, it will not convert based on the LC authority. No further matching occurs when a bibliographic heading matches a heading in a local authority record. The heading form established '''according to local practice''' is '''retained'''.<br />
<br />
===Matched after national file===<br />
Matching after a National file is useful for situations where the heading is special to the library and, while it may not be authorized yet by the National file, the library does not want to see the particular heading showing up in the '''Unmatched Primary Headings''' report (see Step 5.2, R07).<br />
<br />
This is especially helpful when the not-yet-authorized heading appears in multiple bibliographic records.<br />
<br />
===Local heading matching===<br />
If your library has an established MARC authority file that you want to incorporate into your MARS 2.0 master authority file, you will need to send us a MARC file of these records before we can process your bibliographic files.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.15Step 3.152022-05-31T20:05:41Z<p>WikiSysop: /* Step 3.13: Local Authority Master */</p>
<hr />
<div>==Step 3.15: Local Authority Master==<br />
[[Image:a3-13.png]]<br><br><br />
Sometimes a library has local authority records with local rules governing their relationship to the bibliographic record. MARS 2.0 can recognize your library’s local authority file and govern its matching criteria according to what your library needs.<br />
<br />
===Matched before national file===<br />
An example of a library using a form of a heading that is in conflict with the form chosen by LC. This occurs most often for series titles:<br />
<br />
<font size="3"><br />
'''If your library decided to use the following heading in a set of bib records''':<br />
440 0 $a West Group's tax practice series<br />
<br />
'''This is in conflict with the authorized form in the LC authority for this title''':<br />
010 $a n 00090467<br />
<font color="red">130 0 $a Tax practice series (St. Paul, Minn.)</font><br />
430 0 $a West Group's tax practice series</font><br />
<br />
A heading that matches a 4XX '''See From''' tracing in an LC authority record would convert to the authorized form in the 1XX field.<br />
<br />
To prevent this heading flip, you must provide a file of locally generated authority records against which your headings are matched '''first'''.<br />
<br />
If a heading first matches a local authority record, it will not convert based on the LC authority. No further matching occurs when a bibliographic heading matches a heading in a local authority record. The heading form established '''according to local practice''' is '''retained'''.<br />
<br />
===Matched after national file===<br />
Matching after a National file is useful for situations where the heading is special to the library and, while it may not be authorized yet by the National file, the library does not want to see the particular heading showing up in the '''Unmatched Primary Headings''' report (see Step 5.2, R07).<br />
<br />
This is especially helpful when the not-yet-authorized heading appears in multiple bibliographic records.<br />
<br />
===Local heading matching===<br />
If your library has an established MARC authority file that you want to incorporate into your MARS 2.0 master authority file, you will need to send us a MARC file of these records before we can process your bibliographic files.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.15Step 3.152022-05-31T20:04:51Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.13: Local Authority Master==<br />
[[Image:a3-13.png]]<br><br><br />
Sometimes a library has local authority records with local rules governing their relationship to the bibliographic record. MARS 2.0 can recognize your library’s local authority file and govern its matching criteria according to what your library needs.<br />
<br />
===Matched before national file===<br />
An example of a library using a form of a heading that is in conflict with the form chosen by LC. This occurs most often for series titles:<br />
<br />
<font size="3"><br />
'''If your library decided to use the following heading in a set of bib records''':<br />
440 0 $a West Group's tax practice series<br />
<br />
'''This is in conflict with the authorized form in the LC authority for this title''':<br />
010 $a n 00090467<br />
<font color="red">130 0 $a Tax practice series (St. Paul, Minn.)</font><br />
430 0 $a West Group's tax practice series</font><br />
<br />
A heading that matches a 4XX '''See From''' tracing in an LC authority record would convert to the authorized form in the 1XX field.<br />
<br />
To prevent this heading flip, you must provide a file of locally generated authority records against which your headings are matched '''first'''.<br />
<br />
If a heading first matches a local authority record, it will not convert based on the LC authority. No further matching occurs when a bibliographic heading matches a heading in a local authority record. The heading form established '''according to local practice''' is '''retained'''.<br />
<br />
===Matched after national file===<br />
Matching after a National file is useful for situations where the heading is special to the library and, while it may not be authorized yet by the National file, the library does not want to see the particular heading showing up in the '''Unmatched Primary Headings''' report (see Step 5.2, R07).<br />
<br />
This is especially helpful when the not-yet-authorized heading appears in multiple bibliographic records.<br />
<br />
===Local heading matching===<br />
If your library has an established MARC authority file that you want to incorporate into your MARS 2.0 master authority file, you will need to send us a MARC file of these records before we can process your bibliographic files.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.15Step 3.152022-05-31T20:04:17Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 3.13: Local Authority Master==<br />
[[Image:a3-13.png]]<br><br><br />
Sometimes a library has local authority records with local rules governing their relationship to the bibliographic record. MARS 2.0 can recognize your library’s local authority file and govern its matching criteria according to what your library needs.<br />
<br />
===Matched before national file===<br />
An example of a library using a form of a heading that is in conflict with the form chosen by LC. This occurs most often for series titles:<br />
<br />
<font size="3"><br />
'''If your library decided to use the following heading in a set of bib records''':<br />
440 0 $a West Group's tax practice series<br />
<br />
'''This is in conflict with the authorized form in the LC authority for this title''':<br />
010 $a n 00090467<br />
<font color="red">130 0 $a Tax practice series (St. Paul, Minn.)</font><br />
430 0 $a West Group's tax practice series</font><br />
<br />
A heading that matches a 4XX '''See From''' tracing in an LC authority record would convert to the authorized form in the 1XX field.<br />
<br />
To prevent this heading flip, you must provide a file of locally generated authority records against which your headings are matched '''first'''.<br />
<br />
If a heading first matches a local authority record, it will not convert based on the LC authority. No further matching occurs when a bibliographic heading matches a heading in a local authority record. The heading form established '''according to local practice''' is '''retained'''.<br />
<br />
===Matched after national file===<br />
Matching after a National file is useful for situations where the heading is special to the library and, while it may not be authorized yet by the National file, the library does not want to see the particular heading showing up in the '''Unmatched Primary Headings''' report (see Step 5.2, R07).<br />
<br />
This is especially helpful when the not-yet-authorized heading appears in multiple bibliographic records.<br />
<br />
===Local heading matching===<br />
If your library has an established MARC authority file that you want to incorporate into your MARS 2.0 master authority file, you will need to send us a MARC file of these records before we can process your bibliographic files.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.19Step 3.192022-05-31T20:03:13Z<p>WikiSysop: WikiSysop moved page Step 3.15 to Step 3.19 without leaving a redirect</p>
<hr />
<div>==LCSH to FAST Conversion==<br />
MARS 2.0 now has the capability of converting Library of Congress 6XX fields to FAST, where an equivalent occurs. Original LC 6XX fields will be retained and the new FAST 6XX fields will contain the proper $w source as well as the $0 URI.<br />
<br />
FAST Authority Records will be available for export should you need them.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_3.19Step 3.192022-05-31T20:02:04Z<p>WikiSysop: </p>
<hr />
<div>==LCSH to FAST Conversion==<br />
MARS 2.0 now has the capability of converting Library of Congress 6XX fields to FAST, where an equivalent occurs. Original LC 6XX fields will be retained and the new FAST 6XX fields will contain the proper $w source as well as the $0 URI.<br />
<br />
FAST Authority Records will be available for export should you need them.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]] - [[Step 3.17|3.17]] - [[Step 3.18|3.18]] - [[Step 3.19|3.19]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/File:A3-11b.pngFile:A3-11b.png2022-05-31T19:40:07Z<p>WikiSysop: WikiSysop uploaded a new version of &quot;File:A3-11b.png&quot;</p>
<hr />
<div></div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/File:A3-6.pngFile:A3-6.png2022-05-31T19:34:52Z<p>WikiSysop: WikiSysop uploaded a new version of &quot;File:A3-6.png&quot;</p>
<hr />
<div></div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/File:A3-1.pngFile:A3-1.png2022-05-31T19:24:14Z<p>WikiSysop: WikiSysop uploaded a new version of &quot;File:A3-1.png&quot;</p>
<hr />
<div></div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/File:A3-1.pngFile:A3-1.png2022-05-31T19:21:35Z<p>WikiSysop: WikiSysop uploaded a new version of &quot;File:A3-1.png&quot;</p>
<hr />
<div></div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/File:A3-1.pngFile:A3-1.png2022-05-31T19:15:13Z<p>WikiSysop: WikiSysop uploaded a new version of &quot;File:A3-1.png&quot;</p>
<hr />
<div></div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122022-05-31T19:03:08Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 2.12: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([http://stackoverflow.com/questions/176264/what-is-the-difference-between-a-uri-a-url-and-a-urn link]) within your records.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> http://id.loc.gov/authorities/names/nr99034050<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> http://id.loc.gov/authorities/subjects/sh85004836<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> http://id.nlm.nih.gov/mesh/D000716<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the full URI in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
<br />
At the end of 2019 we updated the URI processing to better reflect the "best practices" for Name/Title matches when that Name/Title appear in a 1XX & 240 field. New best practices are to include a URI for just the name in the 1XX field and a URI for the Name/Title in the 240 field.<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Alderman, Naomi, $e author.<br />
240 10 $a Power. $l Spanish<br />
<br />
'''updated record''':<br />
100 1# $a Alderman, Naomi, $e author. $0 http://id.loc.gov/authorities/names/n2006034931<br />
240 10 $a Power. $l Spanish $0 http://id.loc.gov/authorities/names/no2018156991<br />
</font><br />
<br />
We have two alternative options to this new standard for the 1XX/240. Please notify us if you would prefer either of these alternates.<br />
1. Add name-only URI in the 1XX field; no URI to the 240<br />
2. Add name/title URI to the 240 only; no URI to the 1XX<br />
<br />
===Add $4 to Access Points===<br />
In days past, the $4 in access points was defined for use for the relator "code" and was often used in place of the $e relator term. The $4 has now been redefined to ALSO include the URI for the relator. Our process will check the $e relator term and/or the $4 relator code against id.loc.gov/vocabulary/relators to identify the appropriate URI for the relator.<br />
<br />
Examples:<br />
100 1_ $a Delaplanche, Chantal, $e author. $4 http://id.loc.gov/vocabulary/relators/aut<br />
700 1_ $a Kirby, Luke. $4 act $4 http://id.loc.gov/vocabulary/relators/act<br />
<br />
<br />
===Add $0 to non-Access Points===<br />
With the continued conversations of moving beyond MARC to a linked data environment, the greater library community is continuing to explore other <br />
MARC fields that could potentially have URIs added. The MARS 2.0 service can currently add URIs to the following MARC fields: 043, 050, 33X, 34X.<br />
Examples:<br />
043 ## $a n-us--- $0 http://id.loc.gov/vocabulary/geographicAreas/n-us<br />
050 14 $a KF27 $b .E5525 2010b $0 http://id.loc.gov/authorities/classification/K<br />
336 ## $a text $2 rdacontent $0 http://rdaregistry.info/termList/RDAContentType/1020<br />
337 ## $a unmediated $2 rdamedia $0 http://rdaregistry.info/termList/RDAMediaType/1007<br />
338 ## $a volume $2 rdacarrier $0 http://rdaregistry.info/termList/RDACarrierType/1049<br />
<br />
340 ## $a plastic $2 rdamat $0 http://rdaregistry.info/termList/RDAMaterial/1029<br />
340 ## $g polychrome $2 rdacc $0 http://rdaregistry.info/termList/RDAColourContent/1003<br />
340 ## $a metal $2 rdamat $0 http://rdaregistry.info/termList/RDAMaterial/1022<br />
344 ## $a digital $2 rdatr $0 http://rdaregistry.info/termList/typeRec/1002<br />
344 ## $b optical $2 rdarm $0 http://rdaregistry.info/termList/recMedium/1001<br />
344 ## $c 1.4 m/s<br />
347 ## $b Blu-ray $d 1920 x 1080p $2 rda<br />
347 ## $a video file $2 rdaft $0 http://rdaregistry.info/termList/fileType/1006<br />
<br />
NOTE: Any incoming 34X will attempt to be split based on the RDA Registry vocabularies. If terms do not match a vocabulary, they will remain as they were in the incoming field.<br />
<br />
===Add $1 URIs to Access Points===<br />
In addition to having a $0 with the URI for the authority added, you may also opt to have a $1 for a Real World Object (RWO) added. Current sources available are the Virtual International Authority File (VIAF) and the International Standard Name Identifier (ISNI).<br />
Example:<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator. $1 http://viaf.org/viaf/64206515 $1 http://isni.org/isni/0000000122809802<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html link]) and ISNI ([http://www.isni.org/ link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another client decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other client also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a http://id.loc.gov/authorities/names/no2001000753<br />
921 ## $a http://viaf.org/viaf/23238834<br />
922 ## $a http://isni.org/isni/0000000116075005<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.11Step 2.112022-05-31T19:02:54Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 2.11: Accelerated Reader & Lexile Measures==<br />
[[Image:a2-10.png]]<br><br><br />
MARS 2.0 offers two types of enrichment options for your collection of juvenile records: accelerated reader & lexile measures.<br />
<br />
===Accelerated Reader===<br />
For more information about Accelerated Reader, quiz points and reading levels, please visit http://www.renaissance.com/:<br/><br />
Accelerated Reader (AR) is a computer program that helps teachers and librarians manage and monitor children’s independent reading practice. Your child picks<br />
a book at his own level and reads it at his own pace. When finished, your child takes a short quiz on the computer. (Passing the quiz is an<br />
indication that your child understood what was read.) AR gives children, teachers, and librarians feedback based on the quiz results, which<br />
the teacher then uses to help your child set goals and direct ongoing reading practice.<br />
<br />
Children using AR choose their own books to read, rather than having one<br />
assigned to them. This makes reading a much more enjoyable experience<br />
as they can choose books that are interesting to them.<br />
<br />
Teachers and librarians help your child choose books at an appropriate<br />
readability level that are challenging without being frustrating, ensuring<br />
that your child can pass the quiz and experience success. <br />
<br />
There are currently over '''870,000 ISBNs''' represented in the Accelerated Reader database.<br />
<br />
Here is an example of a before/after record with the AR enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">526 ## $a Accelerated Reader $b UG $c 5.1 $d 17 $z 166237</font></font><br />
<br />
===Lexile Measures===<br />
For more information about Lexile Measures, please visit '''www.lexile.com''':<br/><br />
The Lexile framework is a scientific way to match readers with text using the same scale. Recognized as the standard for matching readers with texts, Lexile&#174; measures connect learners of all ages with resources at the right level of challenge. Lexile measures provide a clear way to monitor progress toward college and career readiness. There are currently over '''500,000 ISBNs''' represented within the Lexile database.<br />
<br />
Here is an example of a before/after record with the Lexile enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">521 8# $a HL720L $b Lexile</font></font><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.8Step 2.82022-05-31T19:02:33Z<p>WikiSysop: /* links */</p>
<hr />
<div>[[Image:Ac-2-8.png ]]<br><br><br />
MARS 2.0 updates obsolete General Material Designations (GMDs) to the current authorized form, and corrects most incorrectly spelled GMD variants.<br />
<br />
Please indicate which GMD table you would like to use and your preferred bracket practice by filling out both parts of Step 2.8.<br />
<br />
===GMD location===<br />
MARS 2.0 assumes it has reached the end of the 245 $h when it encounters one of the following characters: subfield delimiter, end-of-field delimiter, forward slash, back slash, colon, semicolon, equals sign, or period.<br />
<br />
The 245 $h will be moved:<br />
*Before $b or after $n or $p in headings with a $b<br />
*Before a $c in headings without a $b, $n, or $p<br />
<br />
<font size="3"> 245 10 $a Royal gazette /$c New Brunswick <font color="red">$h microform</font><br />
245 00 $a Daily report. <font color="red">$h kit</font> $p People's Republic of China.<br />
<br />
'''changes to''':<br />
245 10 $a Royal gazette <font color="red">$h [microform]</font> /$c New Brunswick.<br />
245 00 $a Daily report. $p People's Republic of China <font color="red">$h [kit]</font>.</font><br />
<br />
=== AACR2 standard terms (level 1) ===<br />
In the AACR2 Standard Terms option (GMD Level 1), MARS 2.0 processing will convert as many GMDs as possible to the terms authorized in the current edition of AACR2.<br />
<br />
For example, both '''$h [computer file]''' and '''$h [computer fillle]''' would be modified to '''$h [electronic resource]'''.<br />
<br />
=== Common practice terms (level 2) ===<br />
In some local catalogs, there may exist GMDs which are not included in the AACR2 list of authorized GMDs (AACR2 paragraph 1.1C). The MARS 2.0 Level 2 GMD list contains '''common''' terms used in many libraries.<br />
<br />
For example, using the Level 2 Common Practice Terms table, the GMD '''$h [audicassette]''' would be corrected to '''$h [audiocassette]''', while in the AACR2 Standard Terms option (Level 1) '''$h [audicassette]''' would be corrected to the standard AACR2 GMD '''$h [sound recording]'''.<br />
<br />
Obsolete terms (i.e., terms that were once authorized by AACR2 and have been replaced by a different term) are normally updated to the replacement term even in Level 2. For example, '''$h [computer file]''' is replaced by the newer term '''$h [electronic resource]'''.<br />
<br />
=== Custom terms ===<br />
You can easily modify either of the GMD term options available in MARS 2.0. For example, if you would like to standardize all your GMDs to the AACR2 Standard Terms, but retain the non-standard terms “microfiche” and “microfilm”, simply notate it in Step 2.9 under Additional Information.<br />
<br />
=== Unrecognized terms===<br />
If the MARS 2.0 GMD tables do not contain a particular GMD variant, that GMD will be included in the '''Unrecognized GMD Report''' (see Step 5.2, R51).<br />
<br />
==Brackets==<br />
MARS 2.0 can also add square brackets around the GMD if not present. Similarly, if the GMD is enclosed in parentheses, angle brackets, etc. MARS 2.0 changes them to square brackets. MARS 2.0 can also remove brackets from GMDs to support systems in which the brackets cause display problems.<br />
<br />
<font size="3"> 245 14 $a The royal gazette <font color="red">$h microform</font> /$c New Brunswick.<br />
245 10 $a Pride and prejudice <font color="red">$h (vidrecording)</font> /$c Metro-Goldwyn-Mayer.<br />
<br />
'''changes to''': <br />
245 14 $a The royal gazette <font color="red">$h [microform]</font> /$c New Brunswick.<br />
245 10 $a Pride and prejudice <font color="red">$h [videorecording]</font> /$c Metro-Goldwyn-Mayer.</font><br />
<br />
The MARS 2.0 staff recommends adding square brackets to the 245 $h. Even if your present local system generates the necessary square brackets, it is likely a future system will require them in the record.<br />
<br />
'''Note''': ''Brackets around GMDs can only be added or removed if GMDs are being standardized. If GMDs are not being standardized, no changes will occur in the 245 $h.''<br />
<br />
==GMD Table Summary==<br />
The table below shows the results of selecting the various GMD Standardization options in Step 2.8:<br />
<br />
Original Form of GMD in Bibliographic Record: '''$h audiocasste'''<br><br><br />
[[Image:29a.png]]<br><br><br />
===AACR2 standard terms===<br />
(spelling variants not shown)<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Level 1<br />
! style="background:silver" align="center" | Level 1<br />
! style="background:silver" align="center" | Level 1<br />
|- align="left"<br />
| activity card || flash card || object<br />
|- align="left"<br />
| art original || game || picture<br />
|- align="left"<br />
| art reproduction || kit || realia<br />
|- align="left"<br />
| braille || manuscript || slide<br />
|- align="left"<br />
| cartographic material || microform || sound recording<br />
|- align="left"<br />
| cartographic material (tactile) || microscope slide || technical drawing<br />
|- align="left"<br />
| chart || model || text<br />
|- align="left"<br />
| chart (large print) || motion picture || text (large print)<br />
|- align="left"<br />
| diorama || multimedia || toy<br />
|- align="left"<br />
| electronic resource || music || transparency<br />
|- align="left"<br />
| filmstrip || music (braille) || videorecording<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Common terms===<br />
(spelling variants not shown)<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Level 2<br />
! style="background:silver" align="center" | Level 2<br />
! style="background:silver" align="center" | Level 2<br />
|- align="left"<br />
| activity card || globe || record<br />
|- align="left"<br />
| art original || government document || serial<br />
|- align="left"<br />
| art reproduction || graphic || slide set<br />
|- align="left"<br />
| atlas || kit || sound recording<br />
|- align="left"<br />
| audiocassette || large print || sound recording (cassette)<br />
|- align="left"<br />
| braille || laser disc || sound recording (compact disc)<br />
|- align="left"<br />
| cartographic chart || LP || sound recording (CD)<br />
|- align="left"<br />
| cartographic material || manuscript || sound recording (LP)<br />
|- align="left"<br />
| cartographic material (tactile) || map || study print<br />
|- align="left"<br />
| CD recording || map (tactile) || technical drawing<br />
|- align="left"<br />
| CD-ROM || microfiche || text<br />
|- align="left"<br />
| CDV || microfilm || text (large print)<br />
|- align="left"<br />
| chart || microform || toy<br />
|- align="left"<br />
| chart (large print) || microopaque || transparency<br />
|- align="left"<br />
| compact disc || microprint || US document<br />
|- align="left"<br />
| diorama || microscope slide || VHS<br />
|- align="left"<br />
| DVD || model || video CD<br />
|- align="left"<br />
| DVD-ROM || motion picture || video single disc<br />
|- align="left"<br />
| electronic resource || music || videocassette<br />
|- align="left"<br />
| electronic resource (CD-ROM) || music (braille) || videodisc<br />
|- align="left"<br />
| federal document || newspaper || videodisc (DVD)<br />
|- align="left"<br />
| filmstrip || periodical || videorecording<br />
|- align="left"<br />
| flash card || photograph || videorecording (DVD)<br />
|- align="left"<br />
| floppy || picture || videorecording (VHS)<br />
|- align="left"<br />
| game || realia || VSD<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.7Step 2.72022-05-31T19:02:14Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 2.7: Initial Articles & Indicators==<br />
[[Image:rda2-1.png]]<br><br><br />
MARS 2.0 supports the standard practice of omitting most initial articles even if a nonfiling character indicator has been defined for the field.<br />
<br />
Initial articles are retained, and the filing indicator correctly set, for the 245 Title Statement and 440 Series Statement/Title Added Entry fields.<br />
<br />
The MARS 2.0 Initial Article Table is an important part of the initial article processing routines. A copy is included at the end of this section. It is based on the Initial Definite and Indefinite Articles table that starts on page 40.<br />
<br />
===Corporate heading initial article check===<br />
You can choose to have corporate heading fields checked for initial articles. This MARS 2.0 option examines $t in these fields: '''110''', '''410''', '''610''', '''710''' and '''810'''.<br />
<br />
If $t begins with '''The''', the initial article is deleted and the first letter of the subsequent word is capitalized. Additionally, if the first word is '''A''' or '''An''', MARS 2.0 includes it in the Possible Leading Articles Report (see [http://ac.bslw.com/community/wiki/index.php5/Profile_Guide_Chapter_5#MARS_2.0_Bib_Reports_List Step 5.2, R14]).<br />
<br />
===245 & 440 fields===<br />
MARS 2.0 checks $a for any initial article in the language of the item (as coded in fixed field 008, bytes 35-37). If an initial article is found in field 245 or 440, the 2nd indicator (Nonfiling Characters) is set to the value in the MARS 2.0 Initial Article Table.<br />
<br />
If the field does not begin with an article in the language of the item, and the Nonfiling Characters indicator contains a number, no processing is done. This prevents setting an incorrect indicator value when a heading has been correctly coded for an initial article in a language other than that of the item as a whole.<br />
<br />
If the 2nd indicator contains a blank (or any other character except a number), MARS 2.0 looks for the presence of an initial A, An, or The. If the heading begins with one of these three text strings, the heading is included in the Possible Leading Articles report (see Step 5.2, R14).<br />
<br />
If no other condition is satisfied, a blank Nonfiling Characters indicator is set to zero.<br />
<br />
MARS 2.0 initial article processing is fully compliant with the February 20, 2003 Library of Congress change in counting non-filing characters.<br />
<br />
Diacritics associated with the initial letter of the following word are no longer included in the filing indicator:<br />
<br />
<font size="3"> 245 0<font color="red">5</font> $a <font color="red">Der ö</font>ffentliche Dienst …<br />
440 <font color="red">5</font> $a <font color="red">Los ú</font>ltimos alazapas ;$v 2<br />
<br />
'''changes to''':<br />
245 0<font color="red">4</font> $a <font color="red">Der ö</font>ffentliche Dienst …<br />
440 <font color="red">4</font> $a <font color="red">Los ú</font>ltimos alazapas ;$v 2</font><br />
<br />
Diacritics associated with the initial article and special characters other than diacritics, however, continue to be included in the filing indicator as shown in the examples below:<br />
<br />
<font size="3"> 245 0<font color="red">5</font> $a <font color="red">[The P</font>art of Pennsylvania that … townships].<br />
245 1<font color="red">5</font> $a <font color="red">The “o</font>ther” person …</font><br />
<br />
MARS 2.0 does '''not''' examine $p.<br />
<br />
==Other Fields==<br />
MARS 2.0 examines the beginning of each instance of these fields and subfields for initial articles:<br><br />
===Subfield $a===<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- align="center"<br />
| 130 || 630 || 730 || 740 || 830<br />
|- align="center"<br />
| 210 || 211 || 212 || 214 || 222<br />
|- align="center"<br />
| 240 || 242 || 243 || 246 || 247<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Subfield $t===<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- align="center"<br />
| 100 || 110 || 111<br />
|- align="center"<br />
| 400 || 410 || 411<br />
|- align="center"<br />
| 600 || 610 || 611<br />
|- align="center"<br />
| 700 || 710 || 711<br />
|- align="center"<br />
| 800 || 810 || 811<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
For fields that have a Nonfiling Characters indicator defined, the initial word is extracted based on the filing indicator and is compared with all articles in the MARS 2.0 Initial Article Table.<br />
<br />
If the initial word is an article:<br />
*The word is deleted<br />
*The first letter of the subsequent word is capitalized<br />
*The filing indicator is reset to zero<br />
<br />
If the article is not found, MARS 2.0 includes the field in the '''Suspicious Filing Indicators Report''' for local review (see Step 5.2, R13).<br />
<br />
MARS 2.0 uses a different process if:<br />
*The filing indicator is a zero or a blank<br />
*No filing indicator has been defined for the field<br />
*The subfield being examined is $t<br />
*If the subfield begins with '''The''':<br />
*The initial article is deleted<br />
*The first letter of the subsequent word is capitalized<br />
*The filing indicator (if defined) is reset to zero<br />
<br />
Additionally, if the first word is '''A''' or '''An''', it is included in the '''Possible Leading Articles Report''' (see Step 5.2, R14).<br />
<br />
==Counting Non-Filing Characters==<br />
With the advent of MARC21, the method of counting non-filing characters was clarified. On February 20, 2003 the Library of Congress implemented a change in practice for counting non-filing characters to reflect the MARC21 clarification.<br />
<br />
This change applies when definite or indefinite articles are present and the first filing word following the article begins with a character modified by a diacritic. When an initial article is present, the rule for counting non-filing characters is as follows:<br />
<blockquote>Count the article, diacritics associated with the article, any blank space, an alif, an ayn, or any mark of punctuation preceding the first filing character. Do '''not''' count a diacritic associated with the first filing character (the alif and ayn are not diacritics, they are special spacing characters not considered for filing).</blockquote><br />
<br />
This practice is best illustrated by the following examples.<br />
<br />
<font size="3"> '''Old practice''':<br />
245 1<font color="red">3</font> $a <font color="red">L’é</font>té …<br />
245 1<font color="red">5</font> $a <font color="red">Los ú</font>ltimos …<br />
245 0<font color="red">5</font> $a <font color="red">Der ö</font>ffentliche Dienst …<br />
245 1<font color="red">5</font> $a <font color="red">al-‘A</font>lam …<br />
<br />
'''New practice''':<br />
245 1<font color="red">2</font> $a <font color="red">L’</font>été …<br />
245 1<font color="red">4</font> $a <font color="red">Los </font>últimos …<br />
245 0<font color="red">4</font> $a <font color="red">Der </font>öffentliche Dienst …<br />
245 1<font color="red">4</font> $a <font color="red">al-‘</font>Alam …</font><br />
<br />
Other helpful examples with and without initial articles (these do '''not''' reflect a change in practice):<br />
<br />
<font size="3"> 245 0<font color="red">4</font> $a <font color="red">al-‘</font>Arabiyah …<br />
245 1<font color="red">4</font> $a <font color="red">He </font>Mone …<br />
245 1<font color="red">2</font> $a <font color="red">L’</font>enfant criminal.<br />
245 0<font color="red">5</font> $a <font color="red">[The P</font>art of Pennsylvania that … townships].<br />
245 1<font color="red">5</font> $a <font color="red">The “</font>other” person …<br />
245 1<font color="red">0</font> $a <font color="red">[</font>Diary] …<br />
245 1<font color="red">0</font> $a <font color="red">”</font>Full steam ahead!” …</font><br />
<br />
'''Note''': ''The following characters can be considered candidates as “the first filing character”:''<br />
*Latin letters<br />
*Arabic numbers<br />
*Super or subscript numbers<br />
*Æ – AE digraph<br />
*Œ – OE digraph<br />
*Ð – Crossed d<br />
*ð – Eth<br />
*i – Turkish i<br />
*L – Polish l<br />
*l – Script l<br />
*O – Hooked o<br />
*U – Hooked u<br />
*Ø – Slashed o<br />
*Þ – Icelandic thorn<br />
*Hatch mark (#)<br />
*& – Ampersand<br />
*+ – Plus sign<br />
<br />
==MARS 2.0 Initial Article Table==<br />
The table shown lists each initial article, and the associated filing indicator, by language.<br />
<br />
This table is not intended as a comprehensive list, but rather a tool that is used within a specific automated process. Generally, initial articles that cannot be correctly converted in all headings without manual review are not included in the table.<br />
<br />
'''MARS 2.0 Initial Article Table'''<br><br />
[[Image:28a.png]]<br><br><br />
<br />
'''MARS 2.0 Initial Article Table'''<br><br />
[[Image:28b.png]]<br><br><br />
<br />
'''MARS 2.0 Initial Article Table'''<br><br />
[[Image:28c.png]]<br><br><br />
<br />
'''MARS 2.0 Initial Article Table'''<br><br />
[[Image:28d.png]]<br><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.6Step 2.62022-05-31T19:01:52Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 2.6: Special Conversions & Additions==<br />
[[Image:rda2-1.png]]<br><br><br />
A number of MARC update conversions are more complex than simply changing a field tag or subfield code to the current value. Some fields, such as the 007, often need to be added to a record. The special MARC field conversion and additions currently provided are:<br />
*Add missing format data<br />
**007<br />
**245 $h (for AACR2 records, not RDA unless by request)<br />
*Add missing subfield data<br />
**017 $b<br />
**032 $b<br />
*Complex field conversions<br />
**1XX Main-Entry-Is-Subject<br />
**260 $d to 028 $a<br />
**262 to 260<br />
**300<br />
**301 to 300<br />
**305 to 300<br />
**705 to 700<br />
**715 to 710<br />
**X11<br />
<br />
Describe modifications to processing listed above. Provide a different default for the 007 field by listing specific values for each position.<br />
<br />
If any of the MARS 2.0 update special field conversions adds a field identical to a pre-existing field, the identical fields will be deduplicated.<br />
<br />
==Specific Fields==<br />
===007 field===<br />
MARS 2.0 can add an 007 Physical Description Fixed Field when missing. MARS 2.0 takes into account various fields within the Bib record, such as the 300/33X/34X fields, in order to populate the 007 field as accurately as possible. There may be some instances in which an 007 cannot be populated. MARS 2.0 attempts to add a missing 007 for the following record types: maps, sound recordings, video recordings, and microform.<br />
<br />
===1xx main-entry-is-subject===<br />
In the past, a value of '''1''' in the 2nd indicator meant the 1XX heading represented both the '''main entry''' and a '''topical subject''' access point. A MARC update in 1990 made use of the 1XX 2nd indicator for this purpose obsolete.<br />
<br />
MARS 2.0 generates a 6XX Subject Added Entry field when the 1XX Main Entry field has 2nd indicator value 1 (main entry is subject). The 2nd indicator of the 1XX Main Entry field is changed to a '''blank'''—the only value currently authorized for a 1XX 2nd indicator. The 1st indicator of the new 6XX field will match the 1XX field and the 2nd indicator will be ‘0’.<br />
<br />
===245 $h added (medium-aacr2)===<br />
MARS 2.0 processing can check for the absence of a $h (Medium) in the 245 Title Statement and add a missing General Material Designation (GMD) in some cases:<br />
<font size="3"> 245 10 $a Olympia town square /$c by Fred Smith.<br />
<br />
'''changes to''':<br />
245 10 $a Olympia town square <font color="red">$h [cartographic material]</font> /$c by Fred Smith.</font><br />
The following 245 $h GMDs are added based on the values indicated:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | 245 $h<br />
! style="background:silver" align="center" | LDR Byte 06 Value<br />
! style="background:silver" align="center" | 008 contains<br />
|- align="center"<br />
| [cartographic material] || e ''or'' f || <br />
|- align="center"<br />
| [electronic resource] || m || <br />
|- align="center"<br />
| [filmstrip] || g || byte 33 = f<br />
|- align="center"<br />
| [kit] || o || <br />
|- align="center"<br />
| [microform] || a ''or'' t || byte 23 = a, b ''or'' c<br />
|- align="center"<br />
| [motion picture] || g || byte 33 = m<br />
|- align="center"<br />
| [slide] || g || byte 33 = s<br />
|- align="center"<br />
| [sound recording] || i ''or'' j || <br />
|- align="center"<br />
| [transparency] || g || byte 33 = t<br />
|- align="center"<br />
| [vidoerecording] || g || byte 33 = v<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
To modify any values in this tables, please indicate any changes in Step 2-7.<br />
<br />
MARS 2.0 can also standardize GMDs already present in the 245 $h subfield. MARS 2.0 GMD Standardization is described in [http://ac.bslw.com/community/wiki/index.php5?title=Profile_Guide_Step_2.9&action=edit Step 2-9].<br />
<br />
'''Note''': $h (Medium) in other title fields and subfields are normally deleted in keeping with current cataloging practice (see the [http://ac.bslw.com/community/wiki/index.php5/Profile_Guide_Step_2.5#Subfield_Deletes_Table Subfield Deletes table] in [http://ac.bslw.com/community/wiki/index.php5/Profile_Guide_Step_2.5 Step 2-5]).<br />
<br />
===017 field===<br />
MARS 2.0 adds $b (Source) if not present in field 017 Copyright Registration Number. The $b in field 017 carries the name of the agency assigning the copyright registration number. Because the $b is now required, and records input before 1980 do not contain it, MARS 2.0 can add the appropriate $b code and data “U.S. Copyright Office” to field 017.<br />
<br />
===028 field===<br />
If the subfield order in an 028 field is $b $a, MARS 2.0 reorders the subfields so they follow the current standard order of $a $b.<br />
<br />
===032 field===<br />
MARS 2.0 adds $b (Source) if not present in field 032 Postal Registration Number. The $b in the 032 field carries the name of the agency assigning the postal registration number.<br />
<br />
Because $b is now required and records input before the subfield was defined do not contain it, MARS 2.0 can add the appropriate $b code and data “USPS” to field 032.<br />
<br />
===260 field===<br />
MARS 2.0 can convert field 260 $d to field 028 $a. Field 260 $d was defined as “Plate or publisher number,” but was made obsolete when field 028 Publisher Number for Music was defined. If a 260 $d exists in a bibliographic record and the value in Leader byte 06 is '''c''', '''d''', '''i''', or '''j''':<br />
*'''028''' field with indicator values '''02''' is '''generated'''<br />
*'''260 $d''' is moved to '''028 $a'''<br />
*'''260 $b''' is copied to '''028 $b'''<br />
*Punctuation in the 260 field is corrected, if necessary<br />
<br />
The 260 field conversion option includes special routines that update the punctuation in all 260 fields in the bibliographic records being processed.<br />
<br />
These punctuation routines update much of the punctuation in 260 fields to the current standards, including:<br />
*<space> + <colon> before $b<br />
*<comma> before $c<br />
*Final field punctuation, as necessary<br />
<br />
===262 field===<br />
Field 262 is restricted to pre-AACR2 records for sound recordings. Field 260 is valid for use with all music materials including sound recordings for the data contained in the 262 $a $b $c. Field 028 was defined for the data in the 262 $k $l (lowercase 'L').<br />
<br />
If field 262 exists in a bibliographic record:<br />
*262 is '''changed''' to 260<br />
*Changes both indicators of new 260 to blank<br />
*Retains these subfield codes: $a $b $c<br />
<br />
For each 262 $k present:<br />
*028 field with indicator values 02 is '''generated'''<br />
*262 $k is '''moved''' to 028 $a subfield<br />
*262 $b is '''copied''' to 028 $b<br />
<br />
For each 262 $l (lowercase 'L') present:<br />
*028 field with indicator values 12 '''generated'''<br />
*262 $l is '''moved''' to 028 $a<br />
*262 $b is '''copied''' to 028 $b<br />
<br />
If the 262 field does not contain a $k or $l (lowecase 'L'), MARS 2.0 does the following additional conversions:<br />
*262 $c is '''moved''' to 028 $a with indicator values 02<br />
*262 $e is '''moved''' to 028 $b with indicator values 12<br />
*262 $b is '''copied''' to 028 $b<br />
*262 $d '''changed''' to $c code<br />
<br />
After all conversions have been completed, the punctuation in the 028 fields and 260 field is updated.<br />
<br />
===300 field===<br />
Field 300 Physical Description of the described item includes validation and cleanup for language materials only (Leader byte 06 = a). Each option described below can be customized according to your preference.<br />
<br />
The following changes are made to the 300 $a:<br />
*unp. or n.p. is '''changed''' to 1 v. (unpaged)<br />
*Comma is added to page numbers if missing (e.g., 1264 p. becomes 1,264 p.)<br />
*l. is '''changed''' to leaves<br />
*approx. is '''changed''' to ca.<br />
*p.l. is '''removed''' (e.g., 4 p.l., xv, 20 p. becomes xv, 20 p.)<br />
*unnumbered is '''removed''' and brackets '''added''' (e.g., 48 unnumbered leaves becomes [48] leaves)<br />
*[various pagings] is '''changed''' to (various pagings)<br />
<br />
The following changes are made to the 300 $b:<br />
*Illustrative matter is '''rearranged''' to be in correct order<br />
*Obsolete illustrative matter is '''replaced''' with ill. (e.g., tables or fronts. becomes ill.)<br />
*ill. is '''removed''' if followed by parenthetical illustrative matter (e.g., ill. (ports.) becomes ports.)<br />
*illus. is '''changed''' to ill.<br />
<br />
The following general changes are made to the 300:<br />
*Various punctuation and spacing issues '''updated'''<br />
*Adds ''';$c cm.''' if missing<br />
*Adds '''300 $a p. ;$c cm.''' if record is monograph and 300 does not exist<br />
*Numbered plate data in $b is '''moved''' to $a; if plate designation is not numbered, it is '''removed'''<br />
<br />
<font size="3"> 300 $a 22 <font color="red">l.</font> :$b <font color="red">graphs</font>.<br />
300 $a <font color="red">unp.</font> $b ill<font color="red">us</font>. $c 30 cm.<br />
<br />
'''changes to:'''<br />
300 $a 22 <font color="red">leaves</font> :$b <font color="red">ill.</font> ;$c cm.<br />
300 $a <font color="red">1 v. (unpaged)</font> :$b ill. ;$c 30 cm.</font><br />
<br />
===301 field===<br />
In 1983, field 301 was made obsolete for visual materials. Physical description data is now carried in field 300 Physical Description, with the formerly separate color ($c), sound ($b) and videorecording speed ($f) data recorded in field 300 $b.<br />
<br />
If field 301 exists in a bibliographic record, MARS 2.0:<br />
*301 is '''changed''' to 300, with indicator values <blank><blank><br />
*Retains '''$a''' and '''$e''', with data<br />
*$d is '''changed''' to $c<br />
*$b $c $f data is '''combined''' into single $b<br />
<br />
===305 field===<br />
Field 305 Physical Description for Sound Recordings is a pre-AACR2 field made obsolete by format integration. Field 305 was functionally replaced by field 300 Physical Description.<br />
<br />
If field 305 exists in a bibliographic record:<br />
*305 is '''changed''' to 300, with indicator values <blank><blank><br />
*Retains '''$a''' and '''$c''', with data<br />
*$b $d $e $f data is '''combined''' into single $b<br />
*Updates the punctuation<br />
<br />
For each $m present in the 305 field:<br />
*305 $m is '''moved''' to 028 $a with indicator values 02<br />
*260 $b is '''copied''' to 028 $b<br />
<br />
<font size="3"> 260 $a New York, N.Y. <font color="red">$b Columbia</font>,$c 1959.<br />
305 $a 1 sound disc (20 min.) :$b analog, 33 1/3 rpm, stereo. ;$c 12 in. <font color="red">$m STMA 8007</font><br />
<br />
'''changes to''':<br />
<font color="red">028</font> 02 $a STMA 8007 $b Columbia<br />
260 $a New York, N.Y. :$b Columbia, $c 1959.<br />
300 $a 1 sound disc (20 min.) :$b analog, 33 1/3 rpm, stereo. ;$c 12 in.</font><br />
<br />
For each $n present in the 305 field:<br />
*305 $n is '''moved''' to 028 $a with indicator values 11<br />
*260 $b is '''copied''' to 028 $b<br />
<br />
<font size="3"> 305 $a 1 sound disc (18 min.) $c 10 in. $b 74 rpm $d standard <font color="red">$e</font> monaural <font color="red">$m STMA $n L27410X</font><br />
<br />
'''changes to''':<br />
<font color="red">028</font> 02 $a STMA 3059<br />
<font color="red">028</font> 11 $a L27410X<br />
300 $a 1 sound disc (18 min.) :$b 74 rpm, standard<font color="red">,</font> monaural ;$c 10 in.</font><br />
<br />
===705 & 715 field conversion===<br />
MARS 2.0 converts 705 tags to the equivalent 700 tag and 715 tags to 710, while also adding a Relator Code $4. The default content of the added $4 is '''prf''', the code for '''performer'''.<br />
<br />
'''Note''': ''Indicate in Step 2.6 if you would like a value different from '''prf''' in the new $4. The 705 Added Entry-Personal Name (Performer) and 715 Added Entry-Corporate Name (Performing Group) fields were made obsolete in 1980.''<br />
<br />
===X11 conference name headings===<br />
MARS 2.0 updates Conference Name fields '''111''', '''611''', '''711''', '''811''' to conform to AACR2 and current MARC21 standards. To change the obsolete $b code to $n, MARS 2.0 rearranges the subfields in AACR2 order and corrects the punctuation.<br />
<br />
<font size="3"> '''Pre-AACR2'''<br />
711 01 $a International Conference on the Chemistry and Uses of Molybdenum, <font color="red">$b</font> 1st, <font color="red">$c</font> University of Reading, <font color="red">$d</font> 1973<br />
<br />
'''changes to AACR2 form''':<br />
711 0 $a International Conference on the Chemistry and Uses of Molybdenum <font color="red">$n</font> (1st :<font color="red">$d</font> 1973 :<font color="red">$c</font> University of Reading)</font><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.5Step 2.52022-05-31T19:01:37Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 2.5: Indicator Updates==<br />
[[Image:rda2-1.png]]<br><br><br />
The following tables show the standard updates to 1st and 2nd indicators.<br />
<br />
===1st indicator updates table===<br />
MARS 2.0 makes these changes to the 1st indicator:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! align="center" |<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 017 || any || # || ! style="background:lightgray" | || 505 || # || 0<br />
|- align="center"<br />
| 048 || 012 || # || ! style="background:lightgray" | || 511 || #23 || 0<br />
|- align="center"<br />
| 082 || # || 0 || ! style="background:lightgray" | || 534 || 01 || #<br />
|- align="center"<br />
| 082 || 2 || 1 || ! style="background:lightgray" | || 535 || 03 || 1<br />
|- align="center"<br />
| 100 || #2 || 1 || ! style="background:lightgray" | || 550 || any || #<br />
|- align="center"<br />
| 110, 111 || # || 2 || ! style="background:lightgray" | || 600 || #2 || 1<br />
|- align="center"<br />
| 130 || # || 0 || ! style="background:lightgray" | || 610, 611 || # || 2<br />
|- align="center"<br />
| 210 || # || 1 || ! style="background:lightgray" | || 630 || # || 0<br />
|- align="center"<br />
| 222 || any || # || ! style="background:lightgray" | || 700 || #2 || 1<br />
|- align="center"<br />
| 240, 243 || 2 || 0 || ! style="background:lightgray" | || 710, 711 || # || 2<br />
|- align="center"<br />
| 240, 243 || 3 || 1 || ! style="background:lightgray" | || 730 || # || 0<br />
|- align="center"<br />
| 260 || 01456789 || # || ! style="background:lightgray" | || 800 || #2 || 1<br />
|- align="center"<br />
| 400 || #2 || 1 || ! style="background:lightgray" | || 810 || # || 2<br />
|- align="center"<br />
| 410, 411 || # || 2 || ! style="background:lightgray" | || 811 || # || 2<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===2nd indicator updates table===<br />
MARS 2.0 makes these changes to the 2nd indicator:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! align="center" |<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 050 || #123 || 0 || ! style="background:lightgray" | || 210 || 123456789 || #<br />
|- align="center"<br />
| 051 || 0123 || # || ! style="background:lightgray" | || 260 || any || #<br />
|- align="center"<br />
| 060 || #123 || 0 || ! style="background:lightgray" | || 440 || # || 0<br />
|- align="center"<br />
| 061 || 0123 || # || ! style="background:lightgray" | || 490 || any || #<br />
|- align="center"<br />
| 070, 071 || 0123 || # || ! style="background:lightgray" | || 600, 610, 611, 630 || # || 0<br />
|- align="center"<br />
| 072 || # || 0 || ! style="background:lightgray" | || 650, 651 || # || 0<br />
|- align="center"<br />
| 100, 110, 111, 130 || any || # || ! style="background:lightgray" | || 700, 710, 711, 730, 740 || 013 || #<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.4Step 2.42022-05-31T19:01:13Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 2.4: Subfield Updates & Deletes ==<br />
[[Image:rda2-1.png]]<br><br><br />
<br />
== Subfield Code Updates Table ==<br />
MARS 2.0 converts these subfield codes:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 024 || $b || $d<br />
|- align="center"<br />
| 050 || $d || $a<br />
|- align="center"<br />
| 111 || $b || $n<br />
|- align="center"<br />
| 242, 245, 246, 247 || $d || $n<br />
|- align="center"<br />
| 242, 245, 246, 247 || $e || $p<br />
|- align="center"<br />
| 411, 611, 711, 811 || $b || $n<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
== Subfield Deletes Table==<br />
MARS 2.0 deletes these subfields:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | Subfield<br />
|- align="right"<br />
| 052 || $c<br />
|- align="right"<br />
| 100, 110, 111, 130, 240 || $h<br />
|- align="right"<br />
| 100, 110, 111, 130, 240, 247 || $w<br />
|- align="right"<br />
| 400, 410, 411 || $w<br />
|- align="right"<br />
| 500 || $l, $x, $z<br />
|- align="right"<br />
| 600, 610, 611, 630 || $h<br />
|- align="right"<br />
| 600, 610, 611, 630, 650, 651 || $w<br />
|- align="right"<br />
| 700, 710, 711, 730 || $h<br />
|- align="right"<br />
| 700, 710, 711, 730 || $w<br />
|- align="right"<br />
| 760, 762, 765, 767, 770 || $q<br />
|- align="right"<br />
| 772, 773, 774, 775, 776 || $q<br />
|- align="right"<br />
| 776, 777, 780, 785, 786, 787 || $q<br />
|- align="right"<br />
| 800, 810, 811, 830 || $w<br />
|- align="right"<br />
| 830 || $h, $x<br />
|- align="right"<br />
| 850 || $b<br />
|- align="right"<br />
| 850 || $d<br />
|- align="right"<br />
| 850 || $e<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
== Relator $e Deletions==<br />
Current cataloging practice restricts the use of Relator Term $e subfields in 100 Main Entry and 700 Added Entry-Personal Name fields. A common exception is the continued use of the relator term '''ill.''' for '''illustrators'''. Since there are many variants of '''ill.''' our MARS 2.0 software will look for these as well.<br />
<br />
===Relator terms table===<br />
MARS 2.0 deletes $e and its data in fields 100 and 700 if it contains one of these Relator Terms. If not found in this list, the information remains unchanged:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- align="left"<br />
| arr. || ed. || joint ed.<br />
|- align="left"<br />
| author || editor & translator || joint editor<br />
|- align="left"<br />
| comp. & arr. || editor and translator || joint tr.<br />
|- align="left"<br />
| comp. & tr. || editor || jt. auth.<br />
|- align="left"<br />
| comp. and arr. || joint auth. || jt. author<br />
|- align="left"<br />
| comp. and tr. || joint author || jt. ed.<br />
|- align="left"<br />
| comp. || joint authors || tr. & ed.<br />
|- align="left"<br />
| compiler || joint comp. || tr. and ed.<br />
|- align="left"<br />
| ed. & arr. || joint compiler || tr.<br />
|- align="left"<br />
| ed. & tr. || joint ed. & tr. || trans.<br />
|- align="left"<br />
| ed. and arr. || joint ed. and tr. || translator<br />
|- align="left"<br />
| ed. and tr.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Terms table for “ill.” changes===<br />
MARS 2.0 also changes the following variations to '''ill.''' in $e in fields 100 and 700:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- align="left"<br />
| comp. & illus. || ed. and illus. || jt. illus<br />
|- align="left"<br />
| comp. & ill. || ed. and ill. || jt. ill.<br />
|- align="left"<br />
| comp. and illus. || ill || tr. & illus.<br />
|- align="left"<br />
| comp. and ill. || illus || tr. & ill.<br />
|- align="left"<br />
| ed. & illus. || illustrator || tr. and illus<br />
|- align="left"<br />
| ed. & ill. || joint illus || tr. and ill.<br />
|}<br />
<div style=clear:both></div><br><br />
'''Note''': ''These are AACR2 tables. Some or all entries within RDA tables may be different. RDA processing options can be found in our separate MARS 2.0 guide.''<br />
<br />
== 043 Subfield validation==<br />
MARS2.0 processing will validate the coding within the 043$a. Any coding that is obsolete and has a designated replacement, will be updated. Any coding that is obsolete but does not have a replacement code will be left as is. Coding is kept up to date through the use of the [https://www.loc.gov/marc/geoareas/gacs_code.html |MARC Code List for Geographic Areas]<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.3Step 2.32022-05-31T19:00:29Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 2.3: Field Updates & Deletes==<br />
[[Image:rda2-1.png]]<br><br><br />
<br />
Changes to the MARC21 communications format have made many fields obsolete. If one field has been replaced by another, the change is shown in the Tag Updates table in this section.<br />
<br />
If the field has been made obsolete without being replaced, the field is simply deleted from the bibliographic record. Fields that are deleted as part of MARS 2.0 are listed in the Field Deletes List in this section.<br />
<br />
==Field Updates Table==<br />
Fields and subfields converted by MARS 2.0.<br><br />
(‘x’ represents any 2nd indicator value, ‘#’ represents a blank 2nd indicator value):<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! align="center" ! style="background:lightgray" |<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 023 || 024 [8#] || ! style="background:lightgray" | || 315 || 310<br />
|- align="center"<br />
| 211 [0x] || 246 [2#] || ! style="background:lightgray" | || 350$a $b || 037$c (CF,CR)<br />
|- align="center"<br />
| 211 [1x] || 246 [3#] || ! style="background:lightgray" | || 350$a || 020$c or 037$c* (BK,VM,MU)<br />
|- align="center"<br />
| 212 [0x] || 246 [2#] || ! style="background:lightgray" | || 503 || 500<br />
|- align="center"<br />
| 212 [1x] || 246 [3#] || ! style="background:lightgray" | || 507 || 255 (MP)<br />
|- align="center"<br />
| 212 [2x] || 246 [3#] || ! style="background:lightgray" | || 512 || 500<br />
|- align="center"<br />
| 212 [3x] || 246 [3#] || ! style="background:lightgray" | || 523 || 500<br />
|- align="center"<br />
| 214 [0x] || 246 [2#] || ! style="background:lightgray" | || 527 || 500<br />
|- align="center"<br />
| 214 [1x] || 246 [3#] || ! style="background:lightgray" | || 537 || 500<br />
|- align="center"<br />
| 265 $a || 037 $b || ! style="background:lightgray" | || 543 || 583<br />
|- align="center"<br />
| 308 $a & b || 300 $a || ! style="background:lightgray" | || 570 || 500<br />
|- align="center"<br />
| 308 $c, $d & f || 300 $b || ! style="background:lightgray" | || 755 || 655<br />
|- align="center"<br />
| 308 $e || 300 $c || ! style="background:lightgray" | || 840 || 830<br />
|}<br />
<div style=clear:both></div><br><br />
*MARS Processing will first attempt to convert 350$a to 020$c, but if unable to do so based on multiple or no ISBN, or multiple 350$a then it will fall back to 037$c.<br />
<br />
==Field Deletes List==<br />
MARS 2.0 removes the following fields:<br />
<br />
{| border="1" cellspacing="0" cellpadding="8" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | 0XX<br />
! style="background:silver" align="center" | 2XX<br />
! style="background:silver" align="center" | 3XX<br />
! style="background:silver" align="center" | 5XX<br />
! style="background:silver" align="center" | 6XX<br />
! style="background:silver" align="center" | 8XX<br />
|- align="center"<br />
| 009 || 241 || 302 || 517 || 652 || 851<br />
|- align="center"<br />
| 011 || ! style="background:lightgray" | || 303 || 582 || 680 || ! style="background:lightgray" | <br />
|- align="center"<br />
| 087 || ! style="background:lightgray" | || 304 || ! style="background:lightgray" | || 681 || ! style="background:lightgray" | <br />
|- align="center"<br />
| 091 || ! style="background:lightgray" | || 359 || ! style="background:lightgray" | || 683 || ! style="background:lightgray" | <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.2Step 2.22022-05-31T18:59:58Z<p>WikiSysop: /* links */</p>
<hr />
<div>== Step 2.2 : Leader & Fixed Field Updates ==<br />
[[Image:rda2-1.png]]<br><br><br />
MARS 2.0 provides a variety of updates and corrections to values in the Leader and fixed fields (006, 007, 008).<br />
<br />
Step 2.2 can be customized according to your preference. If there is other information you wish to convey to us on this step, fill in '''With these modifications''' with more details.<br />
<br />
===Fixed field updates===<br />
Changes to MARC21 replaced many fixed field values or made them obsolete. In the leader, for example, the value '''p''' designating a “Record in partial ISBD form” in byte 18, Descriptive Cataloging Form, was made obsolete in 1987 and is now coded using value '''I''' (ISBD). MARS 2.0 Update converts an '''h''' value in Leader byte 18 to '''i'''.<br />
<br />
Bytes 18 (Frequency) and 19 (Regularity) in the 008 fixed field for Computer files/Electronic resources format materials were made obsolete in 1995. Additionally, 008 bytes 18-19 are undefined (should not be used) for Mixed materials format. MARS 2.0, therefore, converts any values in 008 bytes 18-19 to blanks for Computer files/Electronic resources and Mixed materials records.<br />
<br />
==MARS 2.0 Leader & Fixed Field Updates Table==<br />
In the following table, byte position is counted with the first byte being “00” (zero) to be consistent with MARC21 Bibliographic Format documentation. The table uses the following symbols:<br />
<font size="3"> # = blank space<br />
| = fill character</font><br />
<br />
Format codes are as follows (see [[Record_Format|Record Format]] for more details):<br />
<font size="3"> BK = Books<br />
CF = Computer files/Electronic resources<br />
MP = Maps<br />
MU = Music<br />
CR = Continuing resources (serials, etc.)<br />
VM = Visual materials<br />
MX = Mixed materials (includes obsolete Archival and Manuscripts control)</font><br />
<br />
'''Note''': ''‘x’ denotes record types affected''<br />
<br><br><br />
'''Leader'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 06 || h b n || a || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || p || i || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || r || i || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''006 Field'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| All || hex ‘00’ || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 06 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 07 || any || # || || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 08 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 09 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 10 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''007 Field'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| All || hex ‘00’ || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 02 || any || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos. 06-22'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| All || hex ‘00’ || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 06 || c || t || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 06 || d || e || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 19 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 19 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 20 || any || # || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 20 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 20 || any || # || || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 21 || a || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 21 || any || # || || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 21 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 22 || any || # || || || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 22 || ghixz || # || || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 22 || uv || # || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || || || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos.23-25'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 23 || any (except oq) || # || || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 23 || ghiz || # || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 23 || jpt || # || || || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 23 || x || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 24 || any || # || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 24 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 24 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 24 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 24 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 24 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 24 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 25 || any || # || || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 25 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 25 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 25 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 25 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 25 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 25 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos.26-27'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 26 || any || # || || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 26 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 26 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 26 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 26 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 26 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 26 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 27 || any || # || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 27 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 27 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 27 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 27 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 27 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 27 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos.28-34'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 28 || any || # || || || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 28 || n || o || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 28 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 28 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 29 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 29 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 29 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 30 || any || # || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 31 || any || # || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 32 || any || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 33 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 33 || abcdfghmq || z || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 33 || e || v || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 33 || # || 0 || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 34 || any || # || || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 34 || abcdfghmq || z || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 34 || dmt || # || || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 34 || # || n || || || || || || ! style="background:lightgray" | x || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==MARS 2.0 Country Code & Language Code corrections==<br />
As of April 2019 we are updating obsolete Country Codes (pos. 15-17) and Language Codes (35-37) in the 008 Fixed Field as found in https://www.loc.gov/marc/countries/ and https://www.loc.gov/marc/languages/<br />
<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.1Step 2.12022-05-31T18:59:27Z<p>WikiSysop: /* links */</p>
<hr />
<div>== Step 2.1: Validation ==<br />
[[Image:rda2-1.png]]<br><br />
<br />
== Numeric Field Validation ==<br />
MARC fields that are incorrectly formatted often cause user searches to fail and prevent items in the collection from being included in the system indexes. MARS 2.0 software can validate the structure of numeric data in the following fields:<ul><li>010: Library of Congress Control Number (LCCN)<li>020: International Standard Book Number (ISBN)<li>022: International Standard Serial Number (ISSN)<li>034: Coded Cartographic Mathematic Data (CCMD)</ul><br />
<br />
=== Historical fact ===<br />
LC changed the structure of the LCCN beginning on Jan. 1, 2001 in order to accommodate a four-digit year. The length of the control number remains 12 characters as it was prior to the change. However, in the old LCCN structure (A), suffixes were occasionally used. Under the new LCCN structure (B), the location of elements is slightly altered to accommodate a four-digit year. Under both structures, the prefix, year and serial number are the basic elements required to make a LCCN unique.<br />
<br />
Please indicate on Step 2.1 what kind of validation you would like performed on your 010, 020, 022, or 034 fields. Choosing '''Yes, With these modifications''' means that you would like the MARS 2.0 software to perform a modified validation (e.g., validate fields 020 and 022, but not fields 010 or 034).<br />
<br />
== Pre-2001 LCCN ==<br />
LCCN Structure A (2000 and earlier) numbers are formatted according to the following 6 divisions (separated by hyphens):<br><br />
<font size="3"> 1 2 3 4 5 6<br />
nb#-71-005810-#-/AC-/r86</font><br />
<br />
#3-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''<br />
#2 digits, usually the last 2 digits of the '''year'''<br />
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits<br />
#Blank '''space'''<br />
#Optional variable length '''suffix''' and/or alphabetic identifier<br />
#Optional '''revision date'''<br />
<br />
Examples of LCCN Structure A (the character # represents a single space):<br><br />
<font size="3"> ###95156543# Displayed as: 95-156543<br />
###94014580#/AC/r95 Displayed as: 94-14580/AC/r95<br />
###79310919#//r86 Displayed as: 79-310919//r86<br />
nb#71005810# Displayed as: nb71-5810</font><br />
<br />
== Post-2000 LCCN ==<br />
LCCN Structure B (2001 and later) numbers are formatted according the following 3 divisions (separated by hyphens):<br><br />
<font size="3"> 1 2 3<br />
##-2005-256543</font><br />
<br />
#2-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''<br />
#4-digit '''year'''<br />
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits<br />
<br />
Examples of LCCN Structure B (the character # represents a single space):<br><br />
<font size="3"> ##2005256543 Displayed as: 2005-256543<br />
##2010014580 Displayed as: 2010-14580<br />
nb2005005810 Displayed as: nb2005-5810</font><br />
<br />
According to the Library of Congress, Structure A LCCNs will not be changed to Structure B. This minimizes the impact of the LCCN change for local systems. Since LCCN structures A and B will continue to exist in authority and bibliographic records, MARS 2.0 programs provide for validation of both old and new LCCN formats. No provision is necessary, therefore, for the conversion of Structure A to the new Structure B formats, or vice versa.<br />
<br />
=== LCCN structure A corrections ===<br />
If the LCCN in the 010 $a is identified as a Structure A LCCN and does '''not''' have a valid structure, MARS 2.0 programs make the following format corrections (all changes are subsequently checked for validity):<br />
*If the first character of the LCCN is a number (no prefix is present), the programs insert 3 blanks (###) before the number:<br />
<font size="3"> Original: 95-156543 Corrected to: ###95156543#</font><br />
<br />
*If the first character of the LCCN is an alphabetic character and the second character is a number, MARS 2.0 programs insert 2 blanks (##) between the alphabetic character and the number to make a valid 3-character prefix:<br />
<font size="3"> Original: n95-156543 Corrected to: n##95156543#</font><br />
<br />
*If the first 2 characters of the LCCN are alphabetic and the third character is a number, MARS 2.0 programs insert 1 blank (#) between the alphabetic characters and the number to make a valid 3-character prefix:<br />
<font size="3"> Original: nb95-156543 Corrected to: nb#95156543#</font><br />
<br />
*If a hyphen appears in the 010 $a, MARS 2.0 programs count the number of digits before the hyphen. If one digit is before the hyphen, a 0 (zero) is inserted before the first digit in the LCCN (following the prefix). If 2 digits are before the hyphen, no zeroes are inserted at the beginning of the LCCN:<br />
<font size="3"> Original: nb#9-156543 Corrected to: nb#09156543#<br />
Original: nb#95-156543 Corrected to: nb#95156543#</font><br />
<br />
*MARS 2.0 programs also count the number of digits following the hyphen. If there are fewer than 6 digits, zeroes are added following the first 2 digits (##-) of the LCCN to make 6 digits (for a total of 8 digits). The hyphen is deleted from the LCCN:<br />
<font size="3"> Original: nb#95-6543 Corrected to: nb#95006543#<br />
Original: nb#95-56543 Corrected to: nb#95056543#</font><br />
<br />
*If the LCCN contains a suffix, the suffix is removed in accordance with the revised LC standard for Structure A LCCNs:<br />
<font size="3"> Original: nb#95-516543//r86 Corrected to: nb#95156543#</font><br />
<br />
*If the LCCN does not end with a blank, MARS 2.0 programs insert a blank following the last digit:<br />
<font size="3"> Original: nb#95-516543 Corrected to: nb#95156543#</font><br />
<br />
*If the 010 field data has been modified, the 010 field length is recalculated and the 010 directory entry is updated. The record length is recalculated and updated in the record leader.<br />
<br />
*If MARS 2.0 programs cannot correct the format of the LCCN in the 010 $a (e.g., there are 4 characters in the prefix or there are 9 digits), the 010 $a code is changed to $z and a report can be generated. See report R50 in step 5 for more information about this report.<br />
<br />
*The following invalid LCCN prefixes are corrected to the valid format (# = blank):<br />
<font size="3"> #a# -> a##<br />
##a -> a##<br />
#bc -> bc#<br />
# -> ###<br />
## -> ###</font><br />
<br />
=== LCCN structure B corrections ===<br />
If the LCCN in the 010 $a is identified as a Structure B LCCN and does not have a valid structure, MARS 2.0 programs attempt to correct it by making these conversions (all changes are subsequently checked for validity):<br />
*If the first character of the LCCN is a number (no prefix is present), the programs insert 2 blanks before the number:<br />
<font size="3"> Original: 2005-256543 Corrected to: ##2005256543</font><br />
<br />
*If the first character of the LCCN is an alphabetic character and the second character is a number, MARS 2.0 programs insert 1 blank (#) between the alphabetic character and the number to make a valid 2-character prefix:<br />
<font size="3"> Original: n2005-256543 Corrected to: n#2005256543<br />
Original: nb2005-256543 Corrected to: nb2005256543</font><br />
<br />
*If a hyphen or blank space appears in the 010 $a, MARS 2.0 programs count the number of digits following the hypen. If there are fewer than 6 digits, zeroes are added following the first 4 digits (####-) of the LCCN to make 6 digits (for a total of 10 digits). The hyphen is deleted from the LCCN:<br />
<font size="3"> Original: nb2005-6543 Corrected to: nb2005006543</font><br />
<br />
*If the 010 field data has been modified, the 010 field length is recalculated and the 010 directory entry is updated. The record length is recalculated and updated in the record leader.<br />
<br />
*If MARS 2.0 programs cannot correct the format of the LCCN in the 010 $a (e.g., there are 3 characters in the prefix or there are 11 digits), the 010 $a code is changed to $z and a report can be generated. See report R50 in Step 5 for more information about this report.<br />
<br />
*The following invalid LCCN prefixes are corrected to the valid format (# = blank):<br />
<font size="3"> #a -> a#<br />
#bc -> bc<br />
# -> ##</font><br />
<br />
== 020 Field ==<br />
Some automated systems do not index an ISBN if the format is invalid. An ISBN in field 020 $a should be 10 digits or 13 digits. If the ISBN in 020 $a does not have the valid structure, MARS 2.0 programs attempt to correct the ISBN structure by performing the following conversions:<br />
*If there are 9 digits in the ISBN, a 0 (zero) is inserted before the first digit in the ISBN:<br />
<font size="3"> Original: 873671008 Corrected to: 0873671008</font><br />
<br />
*All hyphens are deleted:<br />
<font size="3"> Original: 1-873671-008 Corrected to: 1873671008</font><br />
<br />
*A lowercase x is converted to uppercase:<br />
<font size="3"> Original: 187367100x Corrected to: 187367100X</font><br />
<br />
*If ISBN is 13 digits, MARS 2.0 programs will verify that the first 3 digits are '''978'''.<br />
<br />
*As an optional service, MARS 2.0 programs will correct the order of the ISBN (i.e. pairs of 13/10 and 13/10)<br />
<br />
*As an optional service, MARS 2.0 programs will convert ISBN-10 to ISBN-13 (includes check-sum value for both 10 and 13 length ISBNs):<br />
<font size="3"> Original: 1873671008 Corrected to: 9781873671000</font><br />
<br />
*If MARS 2.0 programs cannot correct the format of the ISBN in the 020 $a (e.g., there are 11 digits), the 020 $a code is changed to $z and a report is generated. See report R50 in Step 5 for more information about this report.<br />
<br />
=== Historical fact ===<br />
The structure of the ISBN has changed over the past thirty years. Prior to 1977, the 020 field was not repeatable and multiple ISBNs and related information were placed in repeated subfields. Older bibliographic records may still have multiple ISBNs in a single 020 field rather than in multiple 020 fields. January 1, 2007 marked the final date for fully adopting ISBN-13. Between 2005 and 2008, publishers were encouraged to supply both an ISBN-10 and an ISBN-13 for the same manifestation, based on guidelines issued by the International ISBN Agency (IIA). The Library of Congress began accommodating ISBN-13 on October 1, 2004. At the beginning of 2007 is when publishers were expected to supply only ISBN-13.<br />
<br />
=== Ordering 020 fields ===<br />
LC will accept both an ISBN-13 and an ISBN-10 for the same manifestation. These numbers are shown by publishers according to guidelines issued by the IIA, which call for grouping the pairs of ISBNs by manifestation. In printed products the ISBN-13 appears first, and each number is preceded by a print constant as in the following example:<br><br />
<font size="3"> ISBN-13: 978-1-873671-00-0<br />
ISBN-10: 1-873671-008</font><br />
<br />
=== Repeating 020 subfields ===<br />
MARS 2.0 Update processing validates an 020 field for correct subfield repeatability. If the 020 field contains multiple $a, each $a is placed in a separate 020 field:<br><br />
<font size="3"> 020 $a 11111111 $a 22222222<br />
Corrected to:<br />
020 $a 11111111<br />
020 $a 22222222</font><br />
<br />
=== Binding information in 020 fields ===<br />
Prior to 1978, binding information was placed in a $b. Older bibliographic records may have binding information in a $b rather than as a parenthetical qualifier in the $a.<br />
<br />
If the 020 field contains a $b and an 020 $a exists:<br />
*$b delimiter and subfield code are deleted<br />
*020 $b data is enclosed in parentheses<br />
*A blank is inserted at the end of the immediately preceding 020 $a data<br />
*020 $b data, enclosed in parentheses, is moved after the blank at the end of the 020 $a data<br />
<font size="3"> Original: 020 $a 1873671008 $b pbk. Corrected to: 020 $a 1873671008 (pbk.)</font><br />
<br />
=== 020 with missing $a ===<br />
If the 020 field contains a $b and no 020 $a exists, the $b code will be changed to $c:<br><br />
<font size="3"> 020 $b pbk.<br />
Corrected to:<br />
020 $c pbk.</font><br />
<br />
=== 020 with multiple $c ===<br />
If the 020 field contains multiple $c, each $c is placed in a separate 020 field:<br><br />
<font size="3"> 020 $c 4.95 (lib. bdg.) $c 3.60 (pbk.)<br />
Corrected to:<br />
020 $c 4.95 (lib. bdg.)<br />
020 $c 3.60 (pbk.)</font><br />
Please note that if 020 $c follows an existing $q in the '''same field''', the 020 $c will '''not''' be moved to a separate 020 field.<br />
<br />
=== 020 with multiple $a and $c ===<br />
MARS 2.0 programs correctly handle 020 fields with multiple $a and $c:<br><br />
<font size="3"> 020 $a 11111111 $c 4.95 $a 22222222 $c 3.60 $c 8.97 $b pbk.<br />
Corrected to:<br />
020 $a 11111111 $c 4.95<br />
020 $a 22222222 $c 3.60<br />
020 $c 8.97 (pbk.)</font><br />
<br />
== 022 Field ==<br />
MARS 2.0 Update processing can validated the format of the ISSN in field 022 $a. Some automated systems do not index an ISSN if the format is invalid. A valid ISSN in field 022 $a has the following structure: 4 digits, hyphen, 4 digits (or digits and an X):<br><br />
<font size="3"> 1234-1234<br />
1234-123X</font><br />
<br />
If the ISSN in field 022 $a does not have the valid structure, MARS 2.0 programs attempt to correct it by making these conversions:<br />
*If the ISSN has no hyphen, adds a hyphen between the fourth and fifth digits:<br />
<font size="3"> Original: 123<u>4</u>5678 Corrected to: 123<u>4-5</u>678</font><br />
<br />
*Converts a lowercase '''x''' to uppercase:<br />
<font size="3"> Original: 1234-567<u>x</u> Corrected to: 1234-567<u>X</u></font><br />
<br />
*If MARS 2.0 programs cannot correct the format of the ISSN in the 022 $a (e.g., there are 9 digits), the 022 $a code is changed to $y and a report is generated. See report R50 in Step 5 for more information about this report.<br />
<br />
== 034 Field ==<br />
MARS 2.0 Update processing can validate field 034 CMD (Coded Mathematical Data) for correct format. If the 034 field first indicator has value 2 and the 034 field contains multiple $a, MARS 2.0 Update processing:<br />
*Places each $a in a separate 034 field<br />
*Changes each 034 field first indicator to value 1<br />
<font size="3"> 034 2_$a a $b 100000 $a a $b 120000<br />
Corrected to:<br />
034 1_$a a $b 100000<br />
034 1_$a a $b 120000</font><br />
<br />
=== Historical fact ===<br />
First indicator value '''2''' became obsolete when field 034 was made repeatable in 1982. Older bibliographic records may still have first indicator value 2.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.9Step 2.92022-05-31T18:58:28Z<p>WikiSysop: WikiSysop moved page Step 2.13 to Step 2.9 without leaving a redirect</p>
<hr />
<div>==Step 2.9: Punctuation Removal==<br />
MARS 2.0 now offers an option to omit '''terminal''' punctuation in ''descriptive fields'' within the Bibliographic Record. This option was born out of the [https://www.loc.gov/aba/pcc/documents/test-records-punctuation.html PCC's options] of omitting punctuation when desired.<br />
<br />
For a number of years, the PCC has been working on investigating the use of "minimal punctuation" within MARC records. In 2019 Backstage began developing a process to remove terminal punctuation from descriptive fields. This process was built based on an Excel spreadsheet provided by the PCC for which descriptive fields within a MARC record were allowed to have terminal punctuation removed. At the time, access points were NOT to have terminal punctuation removed.<br />
<br />
January 2020 saw the implementation of options to have both terminal punctuation removed from ALL fields within the MARC record but also options for removing medial punctuation within the MARC fields.<br />
<br />
At this time, MARS 2.0 only incorporates the removal of terminal punctuation from the previously prescribed descriptive fields. Updates will be made to add options to removing terminal punctuation from access points as well as medial punctuation.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.9Step 2.92022-05-31T18:58:08Z<p>WikiSysop: </p>
<hr />
<div>==Step 2.9: Punctuation Removal==<br />
MARS 2.0 now offers an option to omit '''terminal''' punctuation in ''descriptive fields'' within the Bibliographic Record. This option was born out of the [https://www.loc.gov/aba/pcc/documents/test-records-punctuation.html PCC's options] of omitting punctuation when desired.<br />
<br />
For a number of years, the PCC has been working on investigating the use of "minimal punctuation" within MARC records. In 2019 Backstage began developing a process to remove terminal punctuation from descriptive fields. This process was built based on an Excel spreadsheet provided by the PCC for which descriptive fields within a MARC record were allowed to have terminal punctuation removed. At the time, access points were NOT to have terminal punctuation removed.<br />
<br />
January 2020 saw the implementation of options to have both terminal punctuation removed from ALL fields within the MARC record but also options for removing medial punctuation within the MARC fields.<br />
<br />
At this time, MARS 2.0 only incorporates the removal of terminal punctuation from the previously prescribed descriptive fields. Updates will be made to add options to removing terminal punctuation from access points as well as medial punctuation.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.9|2.9]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.1Step 2.12022-05-31T18:55:28Z<p>WikiSysop: /* links */</p>
<hr />
<div>== Step 2.1: Validation ==<br />
[[Image:rda2-1.png]]<br><br />
<br />
== Numeric Field Validation ==<br />
MARC fields that are incorrectly formatted often cause user searches to fail and prevent items in the collection from being included in the system indexes. MARS 2.0 software can validate the structure of numeric data in the following fields:<ul><li>010: Library of Congress Control Number (LCCN)<li>020: International Standard Book Number (ISBN)<li>022: International Standard Serial Number (ISSN)<li>034: Coded Cartographic Mathematic Data (CCMD)</ul><br />
<br />
=== Historical fact ===<br />
LC changed the structure of the LCCN beginning on Jan. 1, 2001 in order to accommodate a four-digit year. The length of the control number remains 12 characters as it was prior to the change. However, in the old LCCN structure (A), suffixes were occasionally used. Under the new LCCN structure (B), the location of elements is slightly altered to accommodate a four-digit year. Under both structures, the prefix, year and serial number are the basic elements required to make a LCCN unique.<br />
<br />
Please indicate on Step 2.1 what kind of validation you would like performed on your 010, 020, 022, or 034 fields. Choosing '''Yes, With these modifications''' means that you would like the MARS 2.0 software to perform a modified validation (e.g., validate fields 020 and 022, but not fields 010 or 034).<br />
<br />
== Pre-2001 LCCN ==<br />
LCCN Structure A (2000 and earlier) numbers are formatted according to the following 6 divisions (separated by hyphens):<br><br />
<font size="3"> 1 2 3 4 5 6<br />
nb#-71-005810-#-/AC-/r86</font><br />
<br />
#3-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''<br />
#2 digits, usually the last 2 digits of the '''year'''<br />
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits<br />
#Blank '''space'''<br />
#Optional variable length '''suffix''' and/or alphabetic identifier<br />
#Optional '''revision date'''<br />
<br />
Examples of LCCN Structure A (the character # represents a single space):<br><br />
<font size="3"> ###95156543# Displayed as: 95-156543<br />
###94014580#/AC/r95 Displayed as: 94-14580/AC/r95<br />
###79310919#//r86 Displayed as: 79-310919//r86<br />
nb#71005810# Displayed as: nb71-5810</font><br />
<br />
== Post-2000 LCCN ==<br />
LCCN Structure B (2001 and later) numbers are formatted according the following 3 divisions (separated by hyphens):<br><br />
<font size="3"> 1 2 3<br />
##-2005-256543</font><br />
<br />
#2-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''<br />
#4-digit '''year'''<br />
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits<br />
<br />
Examples of LCCN Structure B (the character # represents a single space):<br><br />
<font size="3"> ##2005256543 Displayed as: 2005-256543<br />
##2010014580 Displayed as: 2010-14580<br />
nb2005005810 Displayed as: nb2005-5810</font><br />
<br />
According to the Library of Congress, Structure A LCCNs will not be changed to Structure B. This minimizes the impact of the LCCN change for local systems. Since LCCN structures A and B will continue to exist in authority and bibliographic records, MARS 2.0 programs provide for validation of both old and new LCCN formats. No provision is necessary, therefore, for the conversion of Structure A to the new Structure B formats, or vice versa.<br />
<br />
=== LCCN structure A corrections ===<br />
If the LCCN in the 010 $a is identified as a Structure A LCCN and does '''not''' have a valid structure, MARS 2.0 programs make the following format corrections (all changes are subsequently checked for validity):<br />
*If the first character of the LCCN is a number (no prefix is present), the programs insert 3 blanks (###) before the number:<br />
<font size="3"> Original: 95-156543 Corrected to: ###95156543#</font><br />
<br />
*If the first character of the LCCN is an alphabetic character and the second character is a number, MARS 2.0 programs insert 2 blanks (##) between the alphabetic character and the number to make a valid 3-character prefix:<br />
<font size="3"> Original: n95-156543 Corrected to: n##95156543#</font><br />
<br />
*If the first 2 characters of the LCCN are alphabetic and the third character is a number, MARS 2.0 programs insert 1 blank (#) between the alphabetic characters and the number to make a valid 3-character prefix:<br />
<font size="3"> Original: nb95-156543 Corrected to: nb#95156543#</font><br />
<br />
*If a hyphen appears in the 010 $a, MARS 2.0 programs count the number of digits before the hyphen. If one digit is before the hyphen, a 0 (zero) is inserted before the first digit in the LCCN (following the prefix). If 2 digits are before the hyphen, no zeroes are inserted at the beginning of the LCCN:<br />
<font size="3"> Original: nb#9-156543 Corrected to: nb#09156543#<br />
Original: nb#95-156543 Corrected to: nb#95156543#</font><br />
<br />
*MARS 2.0 programs also count the number of digits following the hyphen. If there are fewer than 6 digits, zeroes are added following the first 2 digits (##-) of the LCCN to make 6 digits (for a total of 8 digits). The hyphen is deleted from the LCCN:<br />
<font size="3"> Original: nb#95-6543 Corrected to: nb#95006543#<br />
Original: nb#95-56543 Corrected to: nb#95056543#</font><br />
<br />
*If the LCCN contains a suffix, the suffix is removed in accordance with the revised LC standard for Structure A LCCNs:<br />
<font size="3"> Original: nb#95-516543//r86 Corrected to: nb#95156543#</font><br />
<br />
*If the LCCN does not end with a blank, MARS 2.0 programs insert a blank following the last digit:<br />
<font size="3"> Original: nb#95-516543 Corrected to: nb#95156543#</font><br />
<br />
*If the 010 field data has been modified, the 010 field length is recalculated and the 010 directory entry is updated. The record length is recalculated and updated in the record leader.<br />
<br />
*If MARS 2.0 programs cannot correct the format of the LCCN in the 010 $a (e.g., there are 4 characters in the prefix or there are 9 digits), the 010 $a code is changed to $z and a report can be generated. See report R50 in step 5 for more information about this report.<br />
<br />
*The following invalid LCCN prefixes are corrected to the valid format (# = blank):<br />
<font size="3"> #a# -> a##<br />
##a -> a##<br />
#bc -> bc#<br />
# -> ###<br />
## -> ###</font><br />
<br />
=== LCCN structure B corrections ===<br />
If the LCCN in the 010 $a is identified as a Structure B LCCN and does not have a valid structure, MARS 2.0 programs attempt to correct it by making these conversions (all changes are subsequently checked for validity):<br />
*If the first character of the LCCN is a number (no prefix is present), the programs insert 2 blanks before the number:<br />
<font size="3"> Original: 2005-256543 Corrected to: ##2005256543</font><br />
<br />
*If the first character of the LCCN is an alphabetic character and the second character is a number, MARS 2.0 programs insert 1 blank (#) between the alphabetic character and the number to make a valid 2-character prefix:<br />
<font size="3"> Original: n2005-256543 Corrected to: n#2005256543<br />
Original: nb2005-256543 Corrected to: nb2005256543</font><br />
<br />
*If a hyphen or blank space appears in the 010 $a, MARS 2.0 programs count the number of digits following the hypen. If there are fewer than 6 digits, zeroes are added following the first 4 digits (####-) of the LCCN to make 6 digits (for a total of 10 digits). The hyphen is deleted from the LCCN:<br />
<font size="3"> Original: nb2005-6543 Corrected to: nb2005006543</font><br />
<br />
*If the 010 field data has been modified, the 010 field length is recalculated and the 010 directory entry is updated. The record length is recalculated and updated in the record leader.<br />
<br />
*If MARS 2.0 programs cannot correct the format of the LCCN in the 010 $a (e.g., there are 3 characters in the prefix or there are 11 digits), the 010 $a code is changed to $z and a report can be generated. See report R50 in Step 5 for more information about this report.<br />
<br />
*The following invalid LCCN prefixes are corrected to the valid format (# = blank):<br />
<font size="3"> #a -> a#<br />
#bc -> bc<br />
# -> ##</font><br />
<br />
== 020 Field ==<br />
Some automated systems do not index an ISBN if the format is invalid. An ISBN in field 020 $a should be 10 digits or 13 digits. If the ISBN in 020 $a does not have the valid structure, MARS 2.0 programs attempt to correct the ISBN structure by performing the following conversions:<br />
*If there are 9 digits in the ISBN, a 0 (zero) is inserted before the first digit in the ISBN:<br />
<font size="3"> Original: 873671008 Corrected to: 0873671008</font><br />
<br />
*All hyphens are deleted:<br />
<font size="3"> Original: 1-873671-008 Corrected to: 1873671008</font><br />
<br />
*A lowercase x is converted to uppercase:<br />
<font size="3"> Original: 187367100x Corrected to: 187367100X</font><br />
<br />
*If ISBN is 13 digits, MARS 2.0 programs will verify that the first 3 digits are '''978'''.<br />
<br />
*As an optional service, MARS 2.0 programs will correct the order of the ISBN (i.e. pairs of 13/10 and 13/10)<br />
<br />
*As an optional service, MARS 2.0 programs will convert ISBN-10 to ISBN-13 (includes check-sum value for both 10 and 13 length ISBNs):<br />
<font size="3"> Original: 1873671008 Corrected to: 9781873671000</font><br />
<br />
*If MARS 2.0 programs cannot correct the format of the ISBN in the 020 $a (e.g., there are 11 digits), the 020 $a code is changed to $z and a report is generated. See report R50 in Step 5 for more information about this report.<br />
<br />
=== Historical fact ===<br />
The structure of the ISBN has changed over the past thirty years. Prior to 1977, the 020 field was not repeatable and multiple ISBNs and related information were placed in repeated subfields. Older bibliographic records may still have multiple ISBNs in a single 020 field rather than in multiple 020 fields. January 1, 2007 marked the final date for fully adopting ISBN-13. Between 2005 and 2008, publishers were encouraged to supply both an ISBN-10 and an ISBN-13 for the same manifestation, based on guidelines issued by the International ISBN Agency (IIA). The Library of Congress began accommodating ISBN-13 on October 1, 2004. At the beginning of 2007 is when publishers were expected to supply only ISBN-13.<br />
<br />
=== Ordering 020 fields ===<br />
LC will accept both an ISBN-13 and an ISBN-10 for the same manifestation. These numbers are shown by publishers according to guidelines issued by the IIA, which call for grouping the pairs of ISBNs by manifestation. In printed products the ISBN-13 appears first, and each number is preceded by a print constant as in the following example:<br><br />
<font size="3"> ISBN-13: 978-1-873671-00-0<br />
ISBN-10: 1-873671-008</font><br />
<br />
=== Repeating 020 subfields ===<br />
MARS 2.0 Update processing validates an 020 field for correct subfield repeatability. If the 020 field contains multiple $a, each $a is placed in a separate 020 field:<br><br />
<font size="3"> 020 $a 11111111 $a 22222222<br />
Corrected to:<br />
020 $a 11111111<br />
020 $a 22222222</font><br />
<br />
=== Binding information in 020 fields ===<br />
Prior to 1978, binding information was placed in a $b. Older bibliographic records may have binding information in a $b rather than as a parenthetical qualifier in the $a.<br />
<br />
If the 020 field contains a $b and an 020 $a exists:<br />
*$b delimiter and subfield code are deleted<br />
*020 $b data is enclosed in parentheses<br />
*A blank is inserted at the end of the immediately preceding 020 $a data<br />
*020 $b data, enclosed in parentheses, is moved after the blank at the end of the 020 $a data<br />
<font size="3"> Original: 020 $a 1873671008 $b pbk. Corrected to: 020 $a 1873671008 (pbk.)</font><br />
<br />
=== 020 with missing $a ===<br />
If the 020 field contains a $b and no 020 $a exists, the $b code will be changed to $c:<br><br />
<font size="3"> 020 $b pbk.<br />
Corrected to:<br />
020 $c pbk.</font><br />
<br />
=== 020 with multiple $c ===<br />
If the 020 field contains multiple $c, each $c is placed in a separate 020 field:<br><br />
<font size="3"> 020 $c 4.95 (lib. bdg.) $c 3.60 (pbk.)<br />
Corrected to:<br />
020 $c 4.95 (lib. bdg.)<br />
020 $c 3.60 (pbk.)</font><br />
Please note that if 020 $c follows an existing $q in the '''same field''', the 020 $c will '''not''' be moved to a separate 020 field.<br />
<br />
=== 020 with multiple $a and $c ===<br />
MARS 2.0 programs correctly handle 020 fields with multiple $a and $c:<br><br />
<font size="3"> 020 $a 11111111 $c 4.95 $a 22222222 $c 3.60 $c 8.97 $b pbk.<br />
Corrected to:<br />
020 $a 11111111 $c 4.95<br />
020 $a 22222222 $c 3.60<br />
020 $c 8.97 (pbk.)</font><br />
<br />
== 022 Field ==<br />
MARS 2.0 Update processing can validated the format of the ISSN in field 022 $a. Some automated systems do not index an ISSN if the format is invalid. A valid ISSN in field 022 $a has the following structure: 4 digits, hyphen, 4 digits (or digits and an X):<br><br />
<font size="3"> 1234-1234<br />
1234-123X</font><br />
<br />
If the ISSN in field 022 $a does not have the valid structure, MARS 2.0 programs attempt to correct it by making these conversions:<br />
*If the ISSN has no hyphen, adds a hyphen between the fourth and fifth digits:<br />
<font size="3"> Original: 123<u>4</u>5678 Corrected to: 123<u>4-5</u>678</font><br />
<br />
*Converts a lowercase '''x''' to uppercase:<br />
<font size="3"> Original: 1234-567<u>x</u> Corrected to: 1234-567<u>X</u></font><br />
<br />
*If MARS 2.0 programs cannot correct the format of the ISSN in the 022 $a (e.g., there are 9 digits), the 022 $a code is changed to $y and a report is generated. See report R50 in Step 5 for more information about this report.<br />
<br />
== 034 Field ==<br />
MARS 2.0 Update processing can validate field 034 CMD (Coded Mathematical Data) for correct format. If the 034 field first indicator has value 2 and the 034 field contains multiple $a, MARS 2.0 Update processing:<br />
*Places each $a in a separate 034 field<br />
*Changes each 034 field first indicator to value 1<br />
<font size="3"> 034 2_$a a $b 100000 $a a $b 120000<br />
Corrected to:<br />
034 1_$a a $b 100000<br />
034 1_$a a $b 120000</font><br />
<br />
=== Historical fact ===<br />
First indicator value '''2''' became obsolete when field 034 was made repeatable in 1982. Older bibliographic records may still have first indicator value 2.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]] - [[Step 2.13|2.13]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.2Step 2.22022-05-31T18:55:15Z<p>WikiSysop: /* links */</p>
<hr />
<div>== Step 2.2 : Leader & Fixed Field Updates ==<br />
[[Image:rda2-1.png]]<br><br><br />
MARS 2.0 provides a variety of updates and corrections to values in the Leader and fixed fields (006, 007, 008).<br />
<br />
Step 2.2 can be customized according to your preference. If there is other information you wish to convey to us on this step, fill in '''With these modifications''' with more details.<br />
<br />
===Fixed field updates===<br />
Changes to MARC21 replaced many fixed field values or made them obsolete. In the leader, for example, the value '''p''' designating a “Record in partial ISBD form” in byte 18, Descriptive Cataloging Form, was made obsolete in 1987 and is now coded using value '''I''' (ISBD). MARS 2.0 Update converts an '''h''' value in Leader byte 18 to '''i'''.<br />
<br />
Bytes 18 (Frequency) and 19 (Regularity) in the 008 fixed field for Computer files/Electronic resources format materials were made obsolete in 1995. Additionally, 008 bytes 18-19 are undefined (should not be used) for Mixed materials format. MARS 2.0, therefore, converts any values in 008 bytes 18-19 to blanks for Computer files/Electronic resources and Mixed materials records.<br />
<br />
==MARS 2.0 Leader & Fixed Field Updates Table==<br />
In the following table, byte position is counted with the first byte being “00” (zero) to be consistent with MARC21 Bibliographic Format documentation. The table uses the following symbols:<br />
<font size="3"> # = blank space<br />
| = fill character</font><br />
<br />
Format codes are as follows (see [[Record_Format|Record Format]] for more details):<br />
<font size="3"> BK = Books<br />
CF = Computer files/Electronic resources<br />
MP = Maps<br />
MU = Music<br />
CR = Continuing resources (serials, etc.)<br />
VM = Visual materials<br />
MX = Mixed materials (includes obsolete Archival and Manuscripts control)</font><br />
<br />
'''Note''': ''‘x’ denotes record types affected''<br />
<br><br><br />
'''Leader'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 06 || h b n || a || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || p || i || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || r || i || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''006 Field'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| All || hex ‘00’ || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 06 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 07 || any || # || || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 08 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 09 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 10 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''007 Field'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| All || hex ‘00’ || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 02 || any || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos. 06-22'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| All || hex ‘00’ || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 06 || c || t || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 06 || d || e || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 19 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 19 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 20 || any || # || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 20 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 20 || any || # || || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 21 || a || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 21 || any || # || || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 21 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 22 || any || # || || || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 22 || ghixz || # || || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 22 || uv || # || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || || || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos.23-25'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 23 || any (except oq) || # || || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 23 || ghiz || # || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 23 || jpt || # || || || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 23 || x || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 24 || any || # || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 24 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 24 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 24 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 24 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 24 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 24 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 25 || any || # || || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 25 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 25 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 25 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 25 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 25 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 25 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos.26-27'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 26 || any || # || || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 26 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 26 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 26 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 26 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 26 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 26 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 27 || any || # || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 27 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 27 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 27 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 27 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 27 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 27 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos.28-34'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 28 || any || # || || || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 28 || n || o || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 28 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 28 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 29 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 29 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 29 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 30 || any || # || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 31 || any || # || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 32 || any || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 33 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 33 || abcdfghmq || z || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 33 || e || v || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 33 || # || 0 || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 34 || any || # || || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 34 || abcdfghmq || z || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 34 || dmt || # || || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 34 || # || n || || || || || || ! style="background:lightgray" | x || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==MARS 2.0 Country Code & Language Code corrections==<br />
As of April 2019 we are updating obsolete Country Codes (pos. 15-17) and Language Codes (35-37) in the 008 Fixed Field as found in https://www.loc.gov/marc/countries/ and https://www.loc.gov/marc/languages/<br />
<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]] - [[Step 2.13|2.13]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.3Step 2.32022-05-31T18:55:02Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 2.3: Field Updates & Deletes==<br />
[[Image:rda2-1.png]]<br><br><br />
<br />
Changes to the MARC21 communications format have made many fields obsolete. If one field has been replaced by another, the change is shown in the Tag Updates table in this section.<br />
<br />
If the field has been made obsolete without being replaced, the field is simply deleted from the bibliographic record. Fields that are deleted as part of MARS 2.0 are listed in the Field Deletes List in this section.<br />
<br />
==Field Updates Table==<br />
Fields and subfields converted by MARS 2.0.<br><br />
(‘x’ represents any 2nd indicator value, ‘#’ represents a blank 2nd indicator value):<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! align="center" ! style="background:lightgray" |<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 023 || 024 [8#] || ! style="background:lightgray" | || 315 || 310<br />
|- align="center"<br />
| 211 [0x] || 246 [2#] || ! style="background:lightgray" | || 350$a $b || 037$c (CF,CR)<br />
|- align="center"<br />
| 211 [1x] || 246 [3#] || ! style="background:lightgray" | || 350$a || 020$c or 037$c* (BK,VM,MU)<br />
|- align="center"<br />
| 212 [0x] || 246 [2#] || ! style="background:lightgray" | || 503 || 500<br />
|- align="center"<br />
| 212 [1x] || 246 [3#] || ! style="background:lightgray" | || 507 || 255 (MP)<br />
|- align="center"<br />
| 212 [2x] || 246 [3#] || ! style="background:lightgray" | || 512 || 500<br />
|- align="center"<br />
| 212 [3x] || 246 [3#] || ! style="background:lightgray" | || 523 || 500<br />
|- align="center"<br />
| 214 [0x] || 246 [2#] || ! style="background:lightgray" | || 527 || 500<br />
|- align="center"<br />
| 214 [1x] || 246 [3#] || ! style="background:lightgray" | || 537 || 500<br />
|- align="center"<br />
| 265 $a || 037 $b || ! style="background:lightgray" | || 543 || 583<br />
|- align="center"<br />
| 308 $a & b || 300 $a || ! style="background:lightgray" | || 570 || 500<br />
|- align="center"<br />
| 308 $c, $d & f || 300 $b || ! style="background:lightgray" | || 755 || 655<br />
|- align="center"<br />
| 308 $e || 300 $c || ! style="background:lightgray" | || 840 || 830<br />
|}<br />
<div style=clear:both></div><br><br />
*MARS Processing will first attempt to convert 350$a to 020$c, but if unable to do so based on multiple or no ISBN, or multiple 350$a then it will fall back to 037$c.<br />
<br />
==Field Deletes List==<br />
MARS 2.0 removes the following fields:<br />
<br />
{| border="1" cellspacing="0" cellpadding="8" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | 0XX<br />
! style="background:silver" align="center" | 2XX<br />
! style="background:silver" align="center" | 3XX<br />
! style="background:silver" align="center" | 5XX<br />
! style="background:silver" align="center" | 6XX<br />
! style="background:silver" align="center" | 8XX<br />
|- align="center"<br />
| 009 || 241 || 302 || 517 || 652 || 851<br />
|- align="center"<br />
| 011 || ! style="background:lightgray" | || 303 || 582 || 680 || ! style="background:lightgray" | <br />
|- align="center"<br />
| 087 || ! style="background:lightgray" | || 304 || ! style="background:lightgray" | || 681 || ! style="background:lightgray" | <br />
|- align="center"<br />
| 091 || ! style="background:lightgray" | || 359 || ! style="background:lightgray" | || 683 || ! style="background:lightgray" | <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]] - [[Step 2.13|2.13]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.4Step 2.42022-05-31T18:54:39Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 2.4: Subfield Updates & Deletes ==<br />
[[Image:rda2-1.png]]<br><br><br />
<br />
== Subfield Code Updates Table ==<br />
MARS 2.0 converts these subfield codes:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 024 || $b || $d<br />
|- align="center"<br />
| 050 || $d || $a<br />
|- align="center"<br />
| 111 || $b || $n<br />
|- align="center"<br />
| 242, 245, 246, 247 || $d || $n<br />
|- align="center"<br />
| 242, 245, 246, 247 || $e || $p<br />
|- align="center"<br />
| 411, 611, 711, 811 || $b || $n<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
== Subfield Deletes Table==<br />
MARS 2.0 deletes these subfields:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | Subfield<br />
|- align="right"<br />
| 052 || $c<br />
|- align="right"<br />
| 100, 110, 111, 130, 240 || $h<br />
|- align="right"<br />
| 100, 110, 111, 130, 240, 247 || $w<br />
|- align="right"<br />
| 400, 410, 411 || $w<br />
|- align="right"<br />
| 500 || $l, $x, $z<br />
|- align="right"<br />
| 600, 610, 611, 630 || $h<br />
|- align="right"<br />
| 600, 610, 611, 630, 650, 651 || $w<br />
|- align="right"<br />
| 700, 710, 711, 730 || $h<br />
|- align="right"<br />
| 700, 710, 711, 730 || $w<br />
|- align="right"<br />
| 760, 762, 765, 767, 770 || $q<br />
|- align="right"<br />
| 772, 773, 774, 775, 776 || $q<br />
|- align="right"<br />
| 776, 777, 780, 785, 786, 787 || $q<br />
|- align="right"<br />
| 800, 810, 811, 830 || $w<br />
|- align="right"<br />
| 830 || $h, $x<br />
|- align="right"<br />
| 850 || $b<br />
|- align="right"<br />
| 850 || $d<br />
|- align="right"<br />
| 850 || $e<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
== Relator $e Deletions==<br />
Current cataloging practice restricts the use of Relator Term $e subfields in 100 Main Entry and 700 Added Entry-Personal Name fields. A common exception is the continued use of the relator term '''ill.''' for '''illustrators'''. Since there are many variants of '''ill.''' our MARS 2.0 software will look for these as well.<br />
<br />
===Relator terms table===<br />
MARS 2.0 deletes $e and its data in fields 100 and 700 if it contains one of these Relator Terms. If not found in this list, the information remains unchanged:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- align="left"<br />
| arr. || ed. || joint ed.<br />
|- align="left"<br />
| author || editor & translator || joint editor<br />
|- align="left"<br />
| comp. & arr. || editor and translator || joint tr.<br />
|- align="left"<br />
| comp. & tr. || editor || jt. auth.<br />
|- align="left"<br />
| comp. and arr. || joint auth. || jt. author<br />
|- align="left"<br />
| comp. and tr. || joint author || jt. ed.<br />
|- align="left"<br />
| comp. || joint authors || tr. & ed.<br />
|- align="left"<br />
| compiler || joint comp. || tr. and ed.<br />
|- align="left"<br />
| ed. & arr. || joint compiler || tr.<br />
|- align="left"<br />
| ed. & tr. || joint ed. & tr. || trans.<br />
|- align="left"<br />
| ed. and arr. || joint ed. and tr. || translator<br />
|- align="left"<br />
| ed. and tr.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Terms table for “ill.” changes===<br />
MARS 2.0 also changes the following variations to '''ill.''' in $e in fields 100 and 700:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- align="left"<br />
| comp. & illus. || ed. and illus. || jt. illus<br />
|- align="left"<br />
| comp. & ill. || ed. and ill. || jt. ill.<br />
|- align="left"<br />
| comp. and illus. || ill || tr. & illus.<br />
|- align="left"<br />
| comp. and ill. || illus || tr. & ill.<br />
|- align="left"<br />
| ed. & illus. || illustrator || tr. and illus<br />
|- align="left"<br />
| ed. & ill. || joint illus || tr. and ill.<br />
|}<br />
<div style=clear:both></div><br><br />
'''Note''': ''These are AACR2 tables. Some or all entries within RDA tables may be different. RDA processing options can be found in our separate MARS 2.0 guide.''<br />
<br />
== 043 Subfield validation==<br />
MARS2.0 processing will validate the coding within the 043$a. Any coding that is obsolete and has a designated replacement, will be updated. Any coding that is obsolete but does not have a replacement code will be left as is. Coding is kept up to date through the use of the [https://www.loc.gov/marc/geoareas/gacs_code.html |MARC Code List for Geographic Areas]<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]] - [[Step 2.13|2.13]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.5Step 2.52022-05-31T18:54:24Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 2.5: Indicator Updates==<br />
[[Image:rda2-1.png]]<br><br><br />
The following tables show the standard updates to 1st and 2nd indicators.<br />
<br />
===1st indicator updates table===<br />
MARS 2.0 makes these changes to the 1st indicator:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! align="center" |<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 017 || any || # || ! style="background:lightgray" | || 505 || # || 0<br />
|- align="center"<br />
| 048 || 012 || # || ! style="background:lightgray" | || 511 || #23 || 0<br />
|- align="center"<br />
| 082 || # || 0 || ! style="background:lightgray" | || 534 || 01 || #<br />
|- align="center"<br />
| 082 || 2 || 1 || ! style="background:lightgray" | || 535 || 03 || 1<br />
|- align="center"<br />
| 100 || #2 || 1 || ! style="background:lightgray" | || 550 || any || #<br />
|- align="center"<br />
| 110, 111 || # || 2 || ! style="background:lightgray" | || 600 || #2 || 1<br />
|- align="center"<br />
| 130 || # || 0 || ! style="background:lightgray" | || 610, 611 || # || 2<br />
|- align="center"<br />
| 210 || # || 1 || ! style="background:lightgray" | || 630 || # || 0<br />
|- align="center"<br />
| 222 || any || # || ! style="background:lightgray" | || 700 || #2 || 1<br />
|- align="center"<br />
| 240, 243 || 2 || 0 || ! style="background:lightgray" | || 710, 711 || # || 2<br />
|- align="center"<br />
| 240, 243 || 3 || 1 || ! style="background:lightgray" | || 730 || # || 0<br />
|- align="center"<br />
| 260 || 01456789 || # || ! style="background:lightgray" | || 800 || #2 || 1<br />
|- align="center"<br />
| 400 || #2 || 1 || ! style="background:lightgray" | || 810 || # || 2<br />
|- align="center"<br />
| 410, 411 || # || 2 || ! style="background:lightgray" | || 811 || # || 2<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===2nd indicator updates table===<br />
MARS 2.0 makes these changes to the 2nd indicator:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! align="center" |<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 050 || #123 || 0 || ! style="background:lightgray" | || 210 || 123456789 || #<br />
|- align="center"<br />
| 051 || 0123 || # || ! style="background:lightgray" | || 260 || any || #<br />
|- align="center"<br />
| 060 || #123 || 0 || ! style="background:lightgray" | || 440 || # || 0<br />
|- align="center"<br />
| 061 || 0123 || # || ! style="background:lightgray" | || 490 || any || #<br />
|- align="center"<br />
| 070, 071 || 0123 || # || ! style="background:lightgray" | || 600, 610, 611, 630 || # || 0<br />
|- align="center"<br />
| 072 || # || 0 || ! style="background:lightgray" | || 650, 651 || # || 0<br />
|- align="center"<br />
| 100, 110, 111, 130 || any || # || ! style="background:lightgray" | || 700, 710, 711, 730, 740 || 013 || #<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]] - [[Step 2.13|2.13]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysophttps://ac.bslw.com/community/wiki/index.php/Step_2.6Step 2.62022-05-31T18:54:10Z<p>WikiSysop: /* links */</p>
<hr />
<div>==Step 2.6: Special Conversions & Additions==<br />
[[Image:rda2-1.png]]<br><br><br />
A number of MARC update conversions are more complex than simply changing a field tag or subfield code to the current value. Some fields, such as the 007, often need to be added to a record. The special MARC field conversion and additions currently provided are:<br />
*Add missing format data<br />
**007<br />
**245 $h (for AACR2 records, not RDA unless by request)<br />
*Add missing subfield data<br />
**017 $b<br />
**032 $b<br />
*Complex field conversions<br />
**1XX Main-Entry-Is-Subject<br />
**260 $d to 028 $a<br />
**262 to 260<br />
**300<br />
**301 to 300<br />
**305 to 300<br />
**705 to 700<br />
**715 to 710<br />
**X11<br />
<br />
Describe modifications to processing listed above. Provide a different default for the 007 field by listing specific values for each position.<br />
<br />
If any of the MARS 2.0 update special field conversions adds a field identical to a pre-existing field, the identical fields will be deduplicated.<br />
<br />
==Specific Fields==<br />
===007 field===<br />
MARS 2.0 can add an 007 Physical Description Fixed Field when missing. MARS 2.0 takes into account various fields within the Bib record, such as the 300/33X/34X fields, in order to populate the 007 field as accurately as possible. There may be some instances in which an 007 cannot be populated. MARS 2.0 attempts to add a missing 007 for the following record types: maps, sound recordings, video recordings, and microform.<br />
<br />
===1xx main-entry-is-subject===<br />
In the past, a value of '''1''' in the 2nd indicator meant the 1XX heading represented both the '''main entry''' and a '''topical subject''' access point. A MARC update in 1990 made use of the 1XX 2nd indicator for this purpose obsolete.<br />
<br />
MARS 2.0 generates a 6XX Subject Added Entry field when the 1XX Main Entry field has 2nd indicator value 1 (main entry is subject). The 2nd indicator of the 1XX Main Entry field is changed to a '''blank'''—the only value currently authorized for a 1XX 2nd indicator. The 1st indicator of the new 6XX field will match the 1XX field and the 2nd indicator will be ‘0’.<br />
<br />
===245 $h added (medium-aacr2)===<br />
MARS 2.0 processing can check for the absence of a $h (Medium) in the 245 Title Statement and add a missing General Material Designation (GMD) in some cases:<br />
<font size="3"> 245 10 $a Olympia town square /$c by Fred Smith.<br />
<br />
'''changes to''':<br />
245 10 $a Olympia town square <font color="red">$h [cartographic material]</font> /$c by Fred Smith.</font><br />
The following 245 $h GMDs are added based on the values indicated:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | 245 $h<br />
! style="background:silver" align="center" | LDR Byte 06 Value<br />
! style="background:silver" align="center" | 008 contains<br />
|- align="center"<br />
| [cartographic material] || e ''or'' f || <br />
|- align="center"<br />
| [electronic resource] || m || <br />
|- align="center"<br />
| [filmstrip] || g || byte 33 = f<br />
|- align="center"<br />
| [kit] || o || <br />
|- align="center"<br />
| [microform] || a ''or'' t || byte 23 = a, b ''or'' c<br />
|- align="center"<br />
| [motion picture] || g || byte 33 = m<br />
|- align="center"<br />
| [slide] || g || byte 33 = s<br />
|- align="center"<br />
| [sound recording] || i ''or'' j || <br />
|- align="center"<br />
| [transparency] || g || byte 33 = t<br />
|- align="center"<br />
| [vidoerecording] || g || byte 33 = v<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
To modify any values in this tables, please indicate any changes in Step 2-7.<br />
<br />
MARS 2.0 can also standardize GMDs already present in the 245 $h subfield. MARS 2.0 GMD Standardization is described in [http://ac.bslw.com/community/wiki/index.php5?title=Profile_Guide_Step_2.9&action=edit Step 2-9].<br />
<br />
'''Note''': $h (Medium) in other title fields and subfields are normally deleted in keeping with current cataloging practice (see the [http://ac.bslw.com/community/wiki/index.php5/Profile_Guide_Step_2.5#Subfield_Deletes_Table Subfield Deletes table] in [http://ac.bslw.com/community/wiki/index.php5/Profile_Guide_Step_2.5 Step 2-5]).<br />
<br />
===017 field===<br />
MARS 2.0 adds $b (Source) if not present in field 017 Copyright Registration Number. The $b in field 017 carries the name of the agency assigning the copyright registration number. Because the $b is now required, and records input before 1980 do not contain it, MARS 2.0 can add the appropriate $b code and data “U.S. Copyright Office” to field 017.<br />
<br />
===028 field===<br />
If the subfield order in an 028 field is $b $a, MARS 2.0 reorders the subfields so they follow the current standard order of $a $b.<br />
<br />
===032 field===<br />
MARS 2.0 adds $b (Source) if not present in field 032 Postal Registration Number. The $b in the 032 field carries the name of the agency assigning the postal registration number.<br />
<br />
Because $b is now required and records input before the subfield was defined do not contain it, MARS 2.0 can add the appropriate $b code and data “USPS” to field 032.<br />
<br />
===260 field===<br />
MARS 2.0 can convert field 260 $d to field 028 $a. Field 260 $d was defined as “Plate or publisher number,” but was made obsolete when field 028 Publisher Number for Music was defined. If a 260 $d exists in a bibliographic record and the value in Leader byte 06 is '''c''', '''d''', '''i''', or '''j''':<br />
*'''028''' field with indicator values '''02''' is '''generated'''<br />
*'''260 $d''' is moved to '''028 $a'''<br />
*'''260 $b''' is copied to '''028 $b'''<br />
*Punctuation in the 260 field is corrected, if necessary<br />
<br />
The 260 field conversion option includes special routines that update the punctuation in all 260 fields in the bibliographic records being processed.<br />
<br />
These punctuation routines update much of the punctuation in 260 fields to the current standards, including:<br />
*<space> + <colon> before $b<br />
*<comma> before $c<br />
*Final field punctuation, as necessary<br />
<br />
===262 field===<br />
Field 262 is restricted to pre-AACR2 records for sound recordings. Field 260 is valid for use with all music materials including sound recordings for the data contained in the 262 $a $b $c. Field 028 was defined for the data in the 262 $k $l (lowercase 'L').<br />
<br />
If field 262 exists in a bibliographic record:<br />
*262 is '''changed''' to 260<br />
*Changes both indicators of new 260 to blank<br />
*Retains these subfield codes: $a $b $c<br />
<br />
For each 262 $k present:<br />
*028 field with indicator values 02 is '''generated'''<br />
*262 $k is '''moved''' to 028 $a subfield<br />
*262 $b is '''copied''' to 028 $b<br />
<br />
For each 262 $l (lowercase 'L') present:<br />
*028 field with indicator values 12 '''generated'''<br />
*262 $l is '''moved''' to 028 $a<br />
*262 $b is '''copied''' to 028 $b<br />
<br />
If the 262 field does not contain a $k or $l (lowecase 'L'), MARS 2.0 does the following additional conversions:<br />
*262 $c is '''moved''' to 028 $a with indicator values 02<br />
*262 $e is '''moved''' to 028 $b with indicator values 12<br />
*262 $b is '''copied''' to 028 $b<br />
*262 $d '''changed''' to $c code<br />
<br />
After all conversions have been completed, the punctuation in the 028 fields and 260 field is updated.<br />
<br />
===300 field===<br />
Field 300 Physical Description of the described item includes validation and cleanup for language materials only (Leader byte 06 = a). Each option described below can be customized according to your preference.<br />
<br />
The following changes are made to the 300 $a:<br />
*unp. or n.p. is '''changed''' to 1 v. (unpaged)<br />
*Comma is added to page numbers if missing (e.g., 1264 p. becomes 1,264 p.)<br />
*l. is '''changed''' to leaves<br />
*approx. is '''changed''' to ca.<br />
*p.l. is '''removed''' (e.g., 4 p.l., xv, 20 p. becomes xv, 20 p.)<br />
*unnumbered is '''removed''' and brackets '''added''' (e.g., 48 unnumbered leaves becomes [48] leaves)<br />
*[various pagings] is '''changed''' to (various pagings)<br />
<br />
The following changes are made to the 300 $b:<br />
*Illustrative matter is '''rearranged''' to be in correct order<br />
*Obsolete illustrative matter is '''replaced''' with ill. (e.g., tables or fronts. becomes ill.)<br />
*ill. is '''removed''' if followed by parenthetical illustrative matter (e.g., ill. (ports.) becomes ports.)<br />
*illus. is '''changed''' to ill.<br />
<br />
The following general changes are made to the 300:<br />
*Various punctuation and spacing issues '''updated'''<br />
*Adds ''';$c cm.''' if missing<br />
*Adds '''300 $a p. ;$c cm.''' if record is monograph and 300 does not exist<br />
*Numbered plate data in $b is '''moved''' to $a; if plate designation is not numbered, it is '''removed'''<br />
<br />
<font size="3"> 300 $a 22 <font color="red">l.</font> :$b <font color="red">graphs</font>.<br />
300 $a <font color="red">unp.</font> $b ill<font color="red">us</font>. $c 30 cm.<br />
<br />
'''changes to:'''<br />
300 $a 22 <font color="red">leaves</font> :$b <font color="red">ill.</font> ;$c cm.<br />
300 $a <font color="red">1 v. (unpaged)</font> :$b ill. ;$c 30 cm.</font><br />
<br />
===301 field===<br />
In 1983, field 301 was made obsolete for visual materials. Physical description data is now carried in field 300 Physical Description, with the formerly separate color ($c), sound ($b) and videorecording speed ($f) data recorded in field 300 $b.<br />
<br />
If field 301 exists in a bibliographic record, MARS 2.0:<br />
*301 is '''changed''' to 300, with indicator values <blank><blank><br />
*Retains '''$a''' and '''$e''', with data<br />
*$d is '''changed''' to $c<br />
*$b $c $f data is '''combined''' into single $b<br />
<br />
===305 field===<br />
Field 305 Physical Description for Sound Recordings is a pre-AACR2 field made obsolete by format integration. Field 305 was functionally replaced by field 300 Physical Description.<br />
<br />
If field 305 exists in a bibliographic record:<br />
*305 is '''changed''' to 300, with indicator values <blank><blank><br />
*Retains '''$a''' and '''$c''', with data<br />
*$b $d $e $f data is '''combined''' into single $b<br />
*Updates the punctuation<br />
<br />
For each $m present in the 305 field:<br />
*305 $m is '''moved''' to 028 $a with indicator values 02<br />
*260 $b is '''copied''' to 028 $b<br />
<br />
<font size="3"> 260 $a New York, N.Y. <font color="red">$b Columbia</font>,$c 1959.<br />
305 $a 1 sound disc (20 min.) :$b analog, 33 1/3 rpm, stereo. ;$c 12 in. <font color="red">$m STMA 8007</font><br />
<br />
'''changes to''':<br />
<font color="red">028</font> 02 $a STMA 8007 $b Columbia<br />
260 $a New York, N.Y. :$b Columbia, $c 1959.<br />
300 $a 1 sound disc (20 min.) :$b analog, 33 1/3 rpm, stereo. ;$c 12 in.</font><br />
<br />
For each $n present in the 305 field:<br />
*305 $n is '''moved''' to 028 $a with indicator values 11<br />
*260 $b is '''copied''' to 028 $b<br />
<br />
<font size="3"> 305 $a 1 sound disc (18 min.) $c 10 in. $b 74 rpm $d standard <font color="red">$e</font> monaural <font color="red">$m STMA $n L27410X</font><br />
<br />
'''changes to''':<br />
<font color="red">028</font> 02 $a STMA 3059<br />
<font color="red">028</font> 11 $a L27410X<br />
300 $a 1 sound disc (18 min.) :$b 74 rpm, standard<font color="red">,</font> monaural ;$c 10 in.</font><br />
<br />
===705 & 715 field conversion===<br />
MARS 2.0 converts 705 tags to the equivalent 700 tag and 715 tags to 710, while also adding a Relator Code $4. The default content of the added $4 is '''prf''', the code for '''performer'''.<br />
<br />
'''Note''': ''Indicate in Step 2.6 if you would like a value different from '''prf''' in the new $4. The 705 Added Entry-Personal Name (Performer) and 715 Added Entry-Corporate Name (Performing Group) fields were made obsolete in 1980.''<br />
<br />
===X11 conference name headings===<br />
MARS 2.0 updates Conference Name fields '''111''', '''611''', '''711''', '''811''' to conform to AACR2 and current MARC21 standards. To change the obsolete $b code to $n, MARS 2.0 rearranges the subfields in AACR2 order and corrects the punctuation.<br />
<br />
<font size="3"> '''Pre-AACR2'''<br />
711 01 $a International Conference on the Chemistry and Uses of Molybdenum, <font color="red">$b</font> 1st, <font color="red">$c</font> University of Reading, <font color="red">$d</font> 1973<br />
<br />
'''changes to AACR2 form''':<br />
711 0 $a International Conference on the Chemistry and Uses of Molybdenum <font color="red">$n</font> (1st :<font color="red">$d</font> 1973 :<font color="red">$c</font> University of Reading)</font><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]] - [[Step 2.12|2.12]] - [[Step 2.13|2.13]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>WikiSysop