Profile Guide Chapter 5 - Revision history

Lee Ann: fixed typo

2018-11-28T18:24:43Z

fixed typo

Nate at 17:52, 9 May 2013

2013-05-09T17:52:22Z

Jeremy: /* MARS 2.0 Bib Reports List */

2011-11-17T17:09:00Z

‎MARS 2.0 Bib Reports List

Jeremy: /* MARS 2.0 Bib Reports List */

2011-11-11T22:16:12Z

‎MARS 2.0 Bib Reports List

Nate: /* MARS 2.0 Bib Reports List */

2011-05-06T14:15:31Z

‎MARS 2.0 Bib Reports List

Nate: /* MARS 2.0 Bib Reports List */

2011-05-06T14:14:47Z

‎MARS 2.0 Bib Reports List

Nate: /* MARS 2.0 Bib Reports List */

2011-05-06T14:14:30Z

‎MARS 2.0 Bib Reports List

Nate: /* MARS 2.0 Bib Reports List */

2011-05-06T14:13:33Z

‎MARS 2.0 Bib Reports List

Jeremy: /* MARS 2.0 Bib Reports List */

2010-12-09T18:15:41Z

‎MARS 2.0 Bib Reports List

Jeremy: /* MARS 2.0 Bib Reports List */

2010-12-09T18:11:31Z

‎MARS 2.0 Bib Reports List

@@ Line 350: / Line 350: @@
 <br>
 '''R21  Added "Juvenile" to Existing 6XX $v'''<br>
-For libraries that choose this option in Step 3.8, "Juvenile" will be inserted at the beginning of $v for any former LC Child heading (6xx 2nd indicator of '1') that was matched against LC Adult and had its 2nd indicator changed to '0'. As an example, this would result in '''$vFiction''' being changed to '''$vJuvenile fiction'''. This report lists all headings that received the ''$vJuvenile'' addition.
+For libraries that choose this option in Step 3.7, "Juvenile" will be inserted at the beginning of $v for any former LC Child heading (6xx 2nd indicator of '1') that was matched against LC Adult and had its 2nd indicator changed to '0'. As an example, this would result in '''$vFiction''' being changed to '''$vJuvenile fiction'''. This report lists all headings that received the ''$vJuvenile'' addition.
 <br>
 <br>
 '''R22  Added "$vJuvenile literature" to 6XX'''<br>
-For libraries that choose this option in Step 3.8, "$vJuvenile literature" is added at the end of any former LC Child heading (6xx 2nd indicator of '1') that was matched against LC Adult and had its 2nd indicator changed to '0'. As an example, '''$aFriendship''' would change to '''$aFriendship$vJuvenile literature'''. This report lists all headings that received the ''$vJuvenile literature'' addition.
+For libraries that choose this option in Step 3.7, "$vJuvenile literature" is added at the end of any former LC Child heading (6xx 2nd indicator of '1') that was matched against LC Adult and had its 2nd indicator changed to '0'. As an example, '''$aFriendship''' would change to '''$aFriendship$vJuvenile literature'''. This report lists all headings that received the ''$vJuvenile literature'' addition.
 <br>
 <br>

@@ Line 576: / Line 576: @@
 The fields in this report include all changed 240, 600-611 and 700-711 tags with a $t-subfield that have a ‘c,d, i or j’ in the Leader byte 06 field. This report shows changes made in Uniform Title authority headings for sound recordings or scores.
-The MARS 2.0 authority control software cannot differentiate $t-subfields that always, sometimes or never signify breaks in the logical unit. The Uniform Title headings need to be examined to determine if the $t-subfield is appropriate for the new Uniform Title heading.
+If a bib record has 100 $t, our system automatically moves the $t down to a 240 (breaking the logical unit). There are times, however, where the $t is valid on the 100 and shouldn’t be moved to 240, but our system cannot determine those instances, so we request that the library review the R87 report for these instances to see if the 240 should be moved back up to 100 $t.
 '''Note''':	Title portions of 1XX tags are split off into their own 240 fields. The MARS 2.0 authority control process temporarily builds a 1XX Name / 240 Title heading. When the two are put together to form a compound heading (MARS 2.0 authority control does in matching). The $a-subfield from the 240 becomes a $t-subfield in temporary headings to be used for matching. Once a match is found MARS 2.0 authority control splits the new Name / Title heading back to its original state as separate 1XX and 240 tags. The $t-subfield is converted back to a 240 $a-subfield. The 240 changes will also be included in this report

@@ Line 298: / Line 298: @@
 Many of the headings in this report will either need to be changed to a different form, or have their tag changed.
 <br>
 <br>
@@ Line 491: / Line 487: @@
 '''R65	Leader Fixed Field Values Updated'''<br>
 One or more values in the Leader fields are updated during MARS 2.0 Update processing. Leader values are updated only if specified in ''MARC21 Format for Bibliographic Data'' or if requested by the library.
 <br>
 <br>

@@ Line 366: / Line 366: @@
 If a heading does not contain any bolded text, the unrecognized geographic subdivision was corrected during later phases of MARS 2.0 processing.
-'''Note''':	Any $z subfield that is unrecognized will be included in this report, even if it contains a subdivision that is obviouisly not a place name.
+'''Note''':	Any $z subfield that is unrecognized will be included in this report, even if it contains a subdivision that is obviously not a place name.
 <br>
 <br>

@@ Line 235: / Line 235: @@
 == MARS 2.0 Bib Reports List ==
-Each of the available MARS 2.0 bib reports is described in this section. Reports with the '''<font color="red">red</font>''' background are '''<font color="red">Standard Reports</font>'''.
+Each of the available MARS 2.0 bib reports is described in this section. Reports highlighted in '''<font color="red">RED</font>''' are '''<font color="red">Standard Reports</font>'''.
 '''Note''':	Change and Delete reports associated with ongoing services are covered in more detail in Step 6, Ongoing Services. ''MARC21 Format for Bibliographic Data'' located here: http://www.loc.gov/marc/bibliographic/ecbdhome.html

@@ Line 252: / Line 252: @@
 <br>
 <br>
-''<font color="red">'R04	Authority Delete Report</font>'''<br>
+'''<font color="red">R04	Authority Delete Report</font>'''<br>
 Authority records which were deleted either through Notification or Current Cataloging (see Step 6 for ongoing services). The old version of the record (prior to the change) is located on the left side of the report with the changed or updated version on the right side of the report. Updated fields are highlighted within the report. Also of note: the old LCCN is moved to a $z subfield in the replacement records.
 <br>

@@ Line 248: / Line 248: @@
 <br>
 <br>
-'''R03	Authority Change Report'''<br>
+'''<font color="red">R03	Authority Change Report</font>'''<br>
 Authority records which were changed either through Notification or Current Cataloging (see Step 6 for ongoing services). The old version of the record (prior to the change) is located on the left side of the report with the changed or updated version on the right side of the report. Updated fields are highlighted within the report.
 <br>
 <br>
-'''R04	Authority Delete Report'''<br>
+''<font color="red">'R04	Authority Delete Report</font>'''<br>
 Authority records which were deleted either through Notification or Current Cataloging (see Step 6 for ongoing services). The old version of the record (prior to the change) is located on the left side of the report with the changed or updated version on the right side of the report. Updated fields are highlighted within the report. Also of note: the old LCCN is moved to a $z subfield in the replacement records.
 <br>

@@ Line 333: / Line 333: @@
 <br>
 <br>
-'''R17	Split Headings — Headings Left Unchanged''' <br>
+'''<font color="red">R17	Split Headings — Headings Left Unchanged</font>''' <br>
 The headings in this report matched ''See From'' cross-references (4XX fields) in multiple authority records. You may wish to review these potential split headings to determine which heading(s) is most appropriate for the bibliographic record, and make the appropriate changes in your local system.
 <br>

@@ Line 283: / Line 283: @@
 Headings are only included in this report when the tag was not changed due to restrictions within the MARS 2.0 software (e.g., never change an X30 tag to an X50 tag unless based on an authority record cross reference). Headings in which the tags were automatically corrected are listed in R30—Updated Headings and R32—Tags Flipped reports (all tag changes made to all authority controlled fields are included in both reports).
-Many of the headings in this report will be correct an no action is necessary. For example, the heading Arizona might be both a valid Geographic Name (X51) and a Uniform Title (X30) heading. A review of the headings in this report will allow the library to identify and fix incorrect tags that could not be safely corrected during automated authority control processing.
+Many of the headings in this report will be correct and no action is necessary. For example, the heading Arizona might be both a valid Geographic Name (X51) and a Uniform Title (X30) heading. A review of the headings in this report will allow the library to identify and fix incorrect tags that could not be safely corrected during automated authority control processing.
 <br>
 <br>
-'''<font color="red">R10	Heading Matches Established Headings in Multiple Authority Records</font>'''<br>
+'''<font color="red">R10	Heading Matches Multiple Authority Records</font>'''<br>
 Headings in this report matched the established heading (1XX) or cross-reference (4XX) in more than one authority record (for example, more than one LC authority record). Headings are included if either the full heading or just the primary heading matched multiple authority records. Other changes to the heading, not based on the authority matching process, can be made, such as an incorrectly spelled subdivision being flipped to the correct form.
@@ Line 374: / Line 374: @@
 <br>
 '''R30	Updated Headings'''<br>
-This report includes all authority controlled headings which were updated during MARS 2.0 Authority Control processing. Headings not included in this report include those fields not under authority control such as those with tags 0XX, 245, 3XX, 5XX, 9XX. Also not included in this report are headings that contain only a “minor” heading change such as a change in form (punctuation, spacing, capitalization) or a subfield code change from $x to $v. See the ''R30—Minor Heading Changes'' for updated headings that contained only a minor heading change.
+This report includes all authority controlled headings which were updated during MARS 2.0 Authority Control processing. Headings not included in this report include those fields not under authority control such as those with tags 0XX, 245, 3XX, 5XX, 9XX. Also not included in this report are headings that contain only a “minor” heading change such as a change in form (punctuation, spacing, capitalization) or a subfield code change from $x to $v. See the ''R35—Minor Heading Changes'' for updated headings that contained only a minor heading change.
 <br>
 <br>
@@ Line 464: / Line 464: @@
 <br>
 '''R58	XREF Match'''<br>
-Headings that found matches against an authority record’s 4XX See From tracings are listed in this report.
+During Pass One if a heading matches an LC Deleted authority, it follows the cross-reference (010 $z) and replaces the heading with that authority record.
 <br>
 <br>
@@ Line 504: / Line 504: @@
 During MARS 2.0 Update processing, obsolete values in 008 fixed fields are updated to the correct value as specificed in ''MARC21 Format for Bibliographic Data'' or as requested by the library.
-'''Note''':	Some of the fixed field udpates may result in blank data preceding non-blank data in the Accompanying Matter fixed field (008 bytes 23-27) in visual material format bibliographic records. This process shifts non-blank characters to the left in the Accompanying Matter fixed field element.
+'''Note''':	Some of the fixed field updates may result in blank data preceding non-blank data in the Accompanying Matter fixed field (008 bytes 23-27) in visual material format bibliographic records. This process shifts non-blank characters to the left in the Accompanying Matter fixed field element.
 <br>
 <br>
@@ Line 582: / Line 582: @@
 <br>
 '''R87	Music Uniform Title $t Match'''<br>
-The fields in this report include all changed 240, 600-611 and 700-711 tags with a $t-subfield that have a ‘c,di or j’ in the Leader byte 06 field. This report shows changes made in Uniform Title authority headings for sound recordings or scores.
+The fields in this report include all changed 240, 600-611 and 700-711 tags with a $t-subfield that have a ‘c,d, i or j’ in the Leader byte 06 field. This report shows changes made in Uniform Title authority headings for sound recordings or scores.
 The MARS 2.0 authority control software cannot differentiate $t-subfields that always, sometimes or never signify breaks in the logical unit. The Uniform Title headings need to be examined to determine if the $t-subfield is appropriate for the new Uniform Title heading.
@@ Line 593: / Line 593: @@
 <br>
 <br>
-'''R89	Subject Field Added by Backstage'''<br>
+'''R89	Subfield Added by Backstage'''<br>
 Subfield fields added by Backstage Library Works during authority control processing will be noted within this report.
 <br>

@@ Line 272: / Line 272: @@
 The majority of non-65X headings in this report will normally be headings which are valid, but have not yet been established, i.e., an authority record has not yet been added to the national authority file for that heading. Some of the headings, however, will be incorrect forms of established headings that could not be corrected during authority cleanup process.
 <br>
 <br>
@@ Line 282: / Line 286: @@
 <br>
 <br>
-'''R10	Heading Matches Established Headings in Multiple Authority Records'''<br>
+'''<font color="red">R10	Heading Matches Established Headings in Multiple Authority Records</font>'''<br>
 Headings in this report matched the established heading (1XX) or cross-reference (4XX) in more than one authority record (for example, more than one LC authority record). Headings are included if either the full heading or just the primary heading matched multiple authority records. Other changes to the heading, not based on the authority matching process, can be made, such as an incorrectly spelled subdivision being flipped to the correct form.