View source for Profile Guide Chapter 5

MARS 2.0 offers a variety of reports designed to assist in your database maintenance tasks. You choose the reports that are appropriate for your project and circumstances.

These are the four basic types of reports that are available in this section:<ul><li>Statistical Summary<li>Bibliographic Reports<li>Authority Change Reports<li>Authority Delete Reports</ul><br>

== Report Formats ==
MARS 2.0 reports are provided in electronic format so they can be downloaded at the same time the MARC records are distributed. All MARS 2.0 reports are in HTML format. The reports can be viewed and printed using any standard browser. They can also be edited with HTML editors and some word processors, however, editing these reports in a word processor may result in the ALA diacritics to display incorrectly.
<br>
== Statistical Summary ==
A MARS 2.0 Statistical Summary is generated for every project that involves processing bibliographic records for authority control. The Statistical Summary includes both high-level and detailed statistical information about the records processed. It also includes the number of times selected actions were taken and the number of headings that met certain criteria.

The statistical information is divided into five sections:<ul><li>'''Section 1: Record Overview''' – A high-level view of the processed file(s). This section includes the number of bibliographic records by type (books, serials, etc.) and how many records were changed during MARS 2.0 processing.<li>'''Section 2: Field Distribution''' – A statistical analysis of the distribution of fields (by tag) within the bibliographic file. Included are how many records had none, one, or two instances of each field, and how many fields changed (by tag). Changes listed in this section correspond with MARC Update Processing (see Step 2 of the Planning Guide).<li>'''Section 3: Authority Control''' – Provides match-rate statistics for fields under authority control examined during MARS 2.0 Authority Control processing (see Step 3 of the Planning Guide).<li>'''Section 4: Authority Control Processing''' – Counts of specific changes made, and conditions found, during MARS 2.0 Authority Control processing (see Step 3 of the Planning Guide).<li>'''Section 5: MARC Update Processing''' – Counts of specific changes made, and conditions found, during MARC Update processing (see Step 2 of the Planning Guide).</ul>

Sections 4 and 5 also serve as a list of the reports available. Those reports marked with an asterisk (following the report number) are available for all MARS 2.0 authority control projects at no additional cost.
 
== Sample Statistical Summary ==
A sample MARS 2.0 Statistical Summary for West Bay College (fictitious) is shown on the next eight pages.
[[Image:5s1x.png]]<br>

=== Section 1:  Record Overview ===
[[Image:5s1x2.png]]<br>
 
=== Section 2:  Field Distrubtion ===

'''''Control Fields (0XX)'''''<br>
[[Image:5s2c.png]]<br>

'''''Descriptive Fields (2XX, 3XX)'''''<br>
[[Image:5s2d.png]]<br>
 
'''''Main and Added Entries (1XX, 4XX, 7XX, 8XX)'''''<br>
[[Image:5s2m.png]]<br>

'''''Subject Access Fields (6XX)'''''<br>
[[Image:5s2s.png]]<br>
 
'''''Notes and Local Fields (5XX,9XX)'''''<br>
[[Image:5s2n.png]]<br>

=== Section 3:  Authority Control ===

'''''Main and Added Entries'''''<br>
[[Image:5s3m.png]]<br>
 
'''''Subject Access Fields'''''<br>
[[Image:5s3sub.png]]<br>

'''''Series Fields'''''<br>
[[Image:5s3ser.png]]<br>

'''''Field Types'''''<br>
[[Image:5s3f.png]]<br>
 
=== Section 4:  Authority Control Processing ===

'''''Conditions Found'''''<br>
[[Image:5s4c1.png]]<br> 
[[Image:5s4c2.png]]<br> 
 
'''''Updates Made'''''<br>
[[Image:5s4u.png]]<br> 
 
=== Section 5:  MARC Update Processing ===

'''''Updates Made'''''<br>
[[Image:5s5.png]]<br> 
*Related information for items marked with an asterisk is included in MARS 2.0 no-fee standard reports. Optional MARS 2.0 reports are available for all other conditions and updates reported in this section for an additional fee. Please contact your Porject Manager for details.


=== Bib Reports ===
MARS 2.0 generates two distinct types of bib reports:<ol><li>Actions taken during processing<li>Specific conditions identified during processing</ol>

The first type provides information about actions taken during MARS 2.0 processing. Examples include headings changed, tags flipped, or subfield codes corrected. Each report shows both the headings before MARS 2.0 processing began and the final form of the heading after processing was completed. An example from the “Tags Flipped” report (R32) follows:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'''ocm57168571'''<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Old&nbsp;&nbsp;&nbsp;&nbsp;650&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;$aEuropean Union.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;New&nbsp;&nbsp;&nbsp;610&nbsp;&nbsp;20&nbsp;$aEuropean Union.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'''ocm52341653'''<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Old&nbsp;&nbsp;&nbsp;&nbsp;650&nbsp;&nbsp;&nbsp;&nbsp;1&nbsp;$aOuter space$xExploration$vFiction.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;New&nbsp;&nbsp;&nbsp;651&nbsp;&nbsp;&nbsp;&nbsp;1&nbsp;$aOuter space$xExploration$vFiction.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'''ocm56334103'''<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Old&nbsp;&nbsp;&nbsp;&nbsp;650&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;$aPennsylvania$vFiction.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;New&nbsp;&nbsp;&nbsp;651&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;$aPennsylvania$vFiction.

The second type of report contains information about specific conditions identified during MARS 2.0 processing that may be helpful in follow-up database or heading maintenance. Examples include unmatched headings or unrecognized $z subfields. These reports generally show only the final form of the heading after processing was completed but no match was found. An example from the “Unmatched Headings” report (R07) follows:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ocm60562678&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;700&nbsp;&nbsp;1&nbsp;&nbsp;&nbsp;$aAllan, Dede.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ocm60883370&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;700&nbsp;&nbsp;1&nbsp;&nbsp;&nbsp;$aAlonso, Ludmila.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ocm57496196&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;100&nbsp;&nbsp;1&nbsp;&nbsp;&nbsp;$aAmadeus.$tThe traveling dog.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ocm55083588&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;700&nbsp;&nbsp;1&nbsp;&nbsp;&nbsp;$aAmmeter, Cheryl.<br>

=== Standard Reports ===
MARS 2.0 provides many of the most commonly used Bibliographic Reports as a standard part of every authority control project. They are available for pickup and review (or not) at your discretion. Custom reports can be developed for conditions not covered by MARS 2.0 optional reports. Contact your sales representative for pricing on custom and non-standard reports.

Reports included as ‘standard’ reports are:<br>
{| border="1" cellspacing="0" cellpadding="5" align="left"
! style="background:silver" align="left" | Number 
! style="background:silver" | Report Title
|-
| R01 || Statistical Summary
|- 
| R07 || Unmatched Primary Headings
|- 
| R09 || Possible Invalid Tags - Tags Unchanged
|-
| R10 || Heading Matches Multiple Authority Records
|- 
| R11 || Heading Usage Not Authorized
|- 
| R13 || Suspicious Filing Indicators
|- 
| R14 || Possible Leading Articles
|- 
| R17* || Split Headings - Headings Left Unchanged
|-
| R25 || Unrecognized $z Geographic Subfields
|- 
| R31* || Split Headings
|- 
| R32 || Tag Flips
|}
<div style=clear:both></div>
*Depending on your selection for Step 3.5, you'll receive either R17 or R31, whichever is more relevant.
*Technically, R06 is the last "free" report, though it can quickly become unwieldy in size.

=== Bib Control Numbers ===
Many local system use a unique serial number, or bib control number, to track and retrieve each bibliographic record. Other systems use standard numbers such as OCLC or LC control numbers. A report which includes bibliographic control numbers allows your local staff to locate headings in a report using the record’s control number.

In many MARS 2.0 bib reports, inclusion of these control numbers is optional. Other bib reports may include control numbers as the information reported can be related to a specific, single bib record. 

== Step 5.1 Question ==
[[Image:5-1.jpg]]<br>

=== Report Format ===
If you choose expanded format, please provide the location of the bib control numbers in your records (e.g., 001 or 907a). MARS 2.0 can also obtain a control number for a secondary source field if the primary field is not present (e.g., Primary: 001, Secondary: 907a). If assistance is needed, the MARS 2.0 staff will gladly help you determine the location of the control numbers in your records.

If bib control numbers are not included in your MARS 2.0 Bibliographic Reports, a heading contained in ten bibliographic records will appear in the report only once. This type of report is in ''collapsed'' format. Collapsed-format reports are usually requested by libraries with a local system that offers robust global update tools.

When bib control numbers are included in a MARS 2.0 Authority Control report, a heading contained in ten bibliographic records would be included in your report ten times, each time with a different bibliographic control number. Reports that include bib control numbers are in ''expanded'' format. Expanded-format reports are especially useful when making updates in one record at a time. Please choose the ''expanded'' or ''collapsed'' option found in profile Step 5.1.

'''Example'''<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'''Expanded  (4 separate entries for same heading)'''<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ocm47933106&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;650&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;$aKeith, Millie (Fictitious character).<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ocm48085387&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;650&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;$aKeith, Millie (Fictitious character).<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ocm49033700&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;650&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;$aKeith, Millie (Fictitious character).<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ocm49033707&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;650&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;$aKeith, Millie (Fictitious character).<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'''Collapsed  (1 entry for all 4 headings)'''<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;650&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;$aKeith, Millie (Fictitious character).<br>

=== Bib Report Sorting ===
The information in each bib report is sorted in one of two ways, determined by the type of information in the report:<ol><li>Authority Control Sort<li>Tag Sort</ol>

=== Authority Control Sort ===
Reports dealing with authority controlled fields are arranged by type of heading (e.g., Names, Subjects, Series). Within each section, headings are arranged first by the second two digits of the field tag, then alphabetically by heading.

For example, in the Names section X00 personal name headings (100 and 700 fields) are listed before X10 corporate name headings (110 and 710 tags).

{| border="1" cellspacing="0" cellpadding="5" align="left"
! style="background:silver" align="left" | Section 
! style="background:silver" | Tags Included
|- 
| Names	 || 100, 110, 111, 130, 700, 710, 711, 730
|- 
| Subjects || 600, 610, 611, 630, 650, 651
|- 
| Series || 440, 800, 810, 811, 830 (also 400, 410, 411 if present)
|- 
| Form / Genre || 655
|}
<div style=clear:both></div>
<br>

If you have requested that LC Children’s headings be matched, there will be a separate report section for Subjects (Children). The same is true for MeSH and Local subject headings

== Step 5.2 Question ==
[[Image:5-2.jpg]]<br>

=== Optional Bib Reports ===
The primary factor in the number of optional or custom reports you request is the availability of the staff for additional heading or record maintenance. Each library needs to determine, based on their local circumstances, if any post-processing review will be done.

Many libraries that use the MARS 2.0 Authority Control service do not order optional reports. They find that most headings are updated or corrected by the MARS 2.0 Authority Control process and additional heading review is not warranted. Other libraries have determined that they are willing to invest in correcting one or more additional conditions that could not be fully resolved using automated processing alone. These libraries choose any number of optional reports.

Please list optional reports in Step 5.2 of the profile. If you choose no optional reports, Backstage Library Works will send you the standard reports [R01, R07, R09, R10, R11, R13, R14, R17, R25, R31, R32].

Sample pages from three bib reports are shown on the following three pages.

[[Image:5-3par1.png]]<br>

The fields in this report contain a primary heading which matched an established heading in an authority record, plus additional subfields that were not present in the related authority record. For example, the heading '''$aWashington Press Association'''''$vBy-laws'' contains a primary heading which matched an LC name authority record (subfield $a), plus a free-floating subdivision which was not present in an authority record for this body (subfield $v).

Most partially matched headings are valid, but an authority record has not been created for the entire heading. Some headings, however, will contain one or more subdivisions which are not valid, not authorized for use in that heading, incorrectly spelled, etc. In this report, the portion of the heading string that '''matched''' a valid authority record will appear in bold text.

'''''Subject Personal Names (600)'''''<br>
[[Image:5-3par2.png]]<br>

----

[[Image:5-3pos1.png]]<br>

This report shows authority controlled fields which matched an authority record with a different tag. For example, if a Topical Subject x50 heading matched a Uniform Title x30 authority record, the bibliographic heading would be included in this report. Headings are only included in this report when the tag was not changed due to restrictions within the BSLW 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 the Changed Headings and 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 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. 
'''Note''': ''Corporate x10 headings will appear in this report if the Type of Name indicator is incorrect''.

[[Image:5-3pos2.png]]<br>

----

[[Image:5-3fli1.png]]<br>

This report includes authority controlled headings in which the field tag was changed during BSLW Authority Control processing. In this report, the portion of the heading string that matched a valid authority record will appear in bold text.

[[Image:5-3fli2.png]]<br>

== Step 5.3 Question ==
[[Image:5-3.jpg]]<br>

=== Custom Reports ===
MARS 2.0 can generate custom reports that include information meeting many different conditions. A library could obtain a list of all the headings that contain a geographic subdivision ($z subfield) in their state or province, or all subject headings (6XX fields) that have a second indicator value of '''4''' (local headings), etc.

Like MARS 2.0 Bibliographic Reports, custom reports can be sorted by bibliographic record number, or the headings can be deduped and the headings then sorted alphabetically, etc.

=== Custom Requests ===
MARS 2.0 is an extremely flexible service. If the options presented in Step 5 do not adequately address your needs, please discuss your requirements with your MARS 2.0 Project Manager. Many different types of reports can be created using the characteristics described in this chapter (e.g., fields to include, format of the report, sort order). Reports that fall outside the scope of the options in Step 5 can be requested by attaching a description on a separate page.

To request a custom report, describe the information desired in Step 5.3. Please address the following parameters as appropriate:<ul><li>'''Records to Include'''. All or selected records from a particular library, records containing a certain field, records containing a particular text in a specified field, records of a particular format (for example, videos), or any combination of these or similar conditions.<li>'''Fields to Include'''. All fields in a record or selected fields.<li>'''Sort Order'''. The records can be sorted by almost any field, for example, the local system control number, the main entry, the main entry then title, a call number or hierarchy of call number fields.</ul>

=== Sample Custom Report ===
A sample page from a custom report:

[[Image:5-4cus1.png]]<br>

This report shows Bibliographic records that do not contain any subject headings (6XX).

[[Image:5-4cus2.png]]<br>

== MARS 2.0 Bib Reports List ==
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
<br>
<br>
'''<font color="red">R01	Statistical Summary</font>'''<br>
Includes both high-level and detailed statistical information about the files processed. It also includes the number of times selected actions were taken and the number of headings that contain specific conditions related to database and heading maintenance.
<br>
<br>
'''R02	Authority Add Report'''<br>
Authority records which were added either through Notification or Current Cataloging (see Step 6 for ongoing services). Each record within this report highlights the main entry (1XX) field of the authority record.
<br>
<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>
'''<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>
<br>
'''R05	Matched Headings'''<br>
Every heading that was matched during MARS 2.0 Authority Control is listed within this report.
<br>
<br>
'''<font color="red">R06	Partially Matched Headings</font>'''<br>
The fields in this report contain a primary heading which matched an established heading in an authority record, plus additional subfields that were not present in the related authority record. For example, the heading '''Washington Press Association—By-laws''' contains a primary heading which matched an LC name authority record, plus a free-floating subdivision which was not present in an authority record for this body. The partially matched portion of this heading in this report is bolded for ease of use.

Most partially matched headings are valid, but for which an authority record has not been created. Some headings, however, will contain one or more subdivisions which are not valid, not authorized for use in that heading, incorrectly spelled, etc.
<br>
<br>
'''<font color="red">R07	Unmatched Primary Headings</font>'''<br>
The fields in this report include a primary heading which did not match an established heading or cross reference in any authority record. The ''primary heading'' in a field includes different subfields depending on the heading type. For example, the primary heading in a Personal Name (X00) heading includes the $a subfield plus any $b, $c, $q or $d subfields present.

For subject (6XX) headings, only authority records in the related national authority file (and internal MARS 2.0 authority files) are checked for matching records. For example, a Topical Subject (650) heading with a second indicator zero is only matched against the LC Subject Authority File unless special processing is required. MeSH, Library and Archives Canada and LC Children’s unmatched headings will appear in this report if available.

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>
'''R08	Generic Names'''<br>
The fields in this report contain a primary name heading which is considered generic (i.e. names without qualifiers such as a date or fuller form of the name). Choosing to flip on generic name headings will give you a greater match rate, but it can cause mismatched headings. The MARS 2.0 software allows for the flip of all name authority headings including the generic heading if there is a match to a See reference (400) in the LC authority record.
<br>
<br>
'''<font color="red">R09	Possible Invalid Tags</font>'''<br>
This report shows authority controlled fields which matched an authority record with a different tag. For example, if a Topical Subject (X50) heading matched a Uniform Title (X30) authority record, the bibliographic heading would be included in this report.

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 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 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.

Partially matched headings are included only if the full heading did not match any heading in the authority file, but a portion of the heading (one of the higher levels) matched the established heading in more than one authority record. This partial match may occur when a free-floating subject subdivision or geographic subdivision has been used with a subject heading that appears in two LC authority records. The multiple authority records that matched are not delivered to the customer if the heading appears in this report.
<br>
<br>
'''<font color="red">R11	Heading Usage Not Authorized</font>'''<br>
Headings in this report matched a heading in the authority file, but the usage codes in the authority record indicate that the heading is not appropriate for the use to which it has been applied in the bibliographic record. An example would be when the authority record indicates that the heading is appropriate for use as a main or added entry, but the heading has been used as a series added entry.

Headings are included when the full headings did not match any heading in the authority file, but a portion of the heading (one of the higher levels) matched a heading in an authority record with authorized usage codes that does not match the usage in the bibliographic record.

Many of the headings in this report will either need to be changed to a different form, or have their tag changed.
<br>
<br>
'''<font color="red">R13	Suspicious Filing Indicators</font>'''<br>
The headings in this report meet either of the following conditions:<ul><li>Indicator value does not represent the length of the initial word<li>Indicator value may or may not be a leading article based on the initial word</ul>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'''Examples'''<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;740&nbsp;&nbsp;15&nbsp;$aThe cat in the hat.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;740&nbsp;&nbsp;1&nbsp;&nbsp;$aDe juramenti promissourii.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;740&nbsp;&nbsp;12&nbsp;$aDe obligatione conscientiae praetectiones decem.<br>

The initial word in these headings was retained in the field unchanged. Because the filing indicator affects retreival in many automated systems, you may wish to examine these headings to determine if the filing indicator requires correction in the bibliographic record on your local system.

'''Note''': ''BSLW tests the value of the filing indicator based on the presence of the initial word in a list of initial articles for each language. The language code in the 008 field (bytes 35-37) is used to determine the language of the record. If the 008 language code is missing, or different than the language of the heading, headings will be listed in this report even though the filing indicator is set correctly''.
<br>
<br>
'''<font color="red">R14	Possible Leading Articles</font>'''<br>
The headings in this report contain an initial word that may or may not be a leading article. For example, although an initial word "A" is normally a leading article in English language word titles, it is not an article in the title '''A is for apple'''. The initial word in these headings was retained in the field unchanged. 

Because the filing indicator affects retrieval in many automated systems, you may wish to examine these headings to determine if the filing indicator is correct or if it needs to be corrected in the bibliographic record on your local system.
<br>
<br>
'''R15	Article Appears to Be Only Data in Field'''<br>
Fields are included in this report when the entire heading consists of a leading article. For example, if an entire heading consists of the word The, this report would reflect each of these headings and its need to be reviewed and any necessary changes made in the bibliographic record on your local system.
<br>
<br>
'''R16	Series Leading Pronoun Present Without Matching 1XX Main Entry'''<br>
This report contains Series Traced Note (4XX) fields which contain a pronoun that takes the place of the 1XX main entry text (e.g., '''His Dialogues'''). To update this obsolete cataloging practice, MARS 2.0 normally replaces the initial pronoun with the heading in the 1XX main entry field. In these bibliographic records, however, there was no 1XX main entry available. Thus, the pronoun has been retained in the generated 8XX series added entry field. In each of these bibliographic records, you need to correct the 8XX series added entry field and add a 1XX main entry field (if appropriate).

'''Note''':	The field correction described above is an optional service of the MARS 2.0 service.
<br>
<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>
<br>
'''R18	Associated Linked Field in $6 Not Found'''<br>
The linked field represented in the Linkage subfield ($6) in the headings was not found in the bibliographic record. The bibliographic record needs to be examined, and the correct data added to the Linkage subfield.
<br>
<br>
'''R19	Invalid $e Found in 100/700 – Not Deleted / Changed'''<br>
If a Relator Term subfield ($e) contains text which appears on the list (see Step 2.5) to be deleted (for example '''joint author''') or corrected (for example '''illus.''' to '''ill.''') the subfield is deleted or fixed. If the Relator Term subfield contains text which does not appear on either list, the heading is included in the this report.

Reviewing the headings within this report allows you to correct those that are not in the standard form, and / or simply remove the Relator Term subfields not appropriate in your local catalog.
<br>
<br>
'''R20	Non-Standard or Missing Source Code in 655 $2'''<br>
Genre / Form Headings (655 fields) in this report contain a second indicator ‘7’ yet do not contain the required ''Source of Term'' subfield ($2).

Headings in this report should be examined to determine if the value in the Source of Term subfield needs to be added.
<br>
<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.
<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.
<br>
<br>
'''<font color="red">R25	Unrecognized $z Subfields</font>'''<br>
The headings in this report contain one or more geographic subdivisions that were not present in the list of established place names used by MARS 2.0. A heading containing two unrecognized $z subfields will appear twice in this report.

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 obviously not a place name.
<br>
<br>
'''R26	Title Found – Unable to Update'''<br>
A title of honor (for example '''Sir''') was found within the headings in this report, but MARS 2.0 was unable to generate the appropriate $c subfield.
<br>
<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 ''R35—Minor Heading Changes'' for updated headings that contained only a minor heading change.
<br>
<br>
'''<font color="red">R31	Split Headings</font>'''<br>
This report includes all authority controlled headings which were “split” during MARS 2.0 Authority Control processing. Headings can split into multiple headings based on a one-to-many change in a primary heading or a one-to-many change in an individual subfield. 

Examples include the change from '''Nurses and nursing''' to the headings '''Nurses''' and '''Nursing''', and the change from “'''–Dictionaries and encyclopedias'''” to the subdivisions “'''–Dictionaries'''” and “'''–Encyclopedias'''”.

In most cases, retaining all replacement headings will assist users in locating relevant resources. In some cases, however, one or more of the replacement headings is not appropriate for the work represented. In these cases, the library may wish to remove those replacement headings which are less relevant for the work represented.
<br>
<br>
'''<font color="red">R32	Tags Flipped</font>'''<br>
This report includes all authority controlled headings in which the field tag was changed during MARS 2.0 Authority Control processing.
<br>
<br>
'''R33	Subdivisions Flipped'''<br>
This report includes authority controlled headings in which MARS 2.0 changed an out-dated or incorrect subdivision to the correct form. This report does not include headings in which the only updates were made based on a match to a cross reference in an authority record. The headings in this report are also included in the larger report ''R30—Updated Headings''.
<br>
<br>
'''R35	Minor Heading Changes'''<br>
This report includes all authority controlled headings which contained only a “minor” heading change such as a change in form (punctuation, spacing, capitalization) or a subfield code change from $x to $v. See ''R30—Update Headings'' for headings that were changed in more signficant ways.
<br>
<br>
'''R36	Leading Article Deleted'''<br>
A leading (initial) article was found in the subfield $a or $t of the headings in this report. MARS 2.0 deleted the leading article, converted the resulting first character of the subfield to uppercase (if appropriate) and set the filing indicator to 0 (if appropriate).
<br>
<br>
'''R37	Filing Indicator Changed'''<br>
The Filiing Indicator in the headings in this report was corrected based on the correct value as shown in the LC authority files and / or ''MARC21 Format for Bibliographic Data'' (Initial Article and Filing Indicator Validation table—see Step 2.8).

'''Note''':	When MARC21 was issued in 1999 the method of counting non-filing characters was clarified. That clarification resulted in a change in practice that the Library of Congress implemented on February 20, 2003 (http://www.loc.gov/catadir/cpso/nonfil.pdf).

MARS 2.0 sets filing indicators based on this LC clarification.
<br>
<br>
'''R38	Changed O and l to 0 and 1 in Dates'''<br>
In the personal name headings in this report, an uppercase O was changed to a number 0 or a lower case L was changed to a number 1 in the date $d subfield.
<br>
<br>
'''R39	Subfield Code Changed from $x to $v'''<br>
Headings in this report include a subdivision in which a topical $x subdivision was recoded as a form $v subdivision.
<br>
<br>
'''R40	TOC Enrichment Changes'''<br>
Headings in this report represent changes that were made during the TOC Enrichment service (see Step 7 of the Planning Guide).
<br>
<br>
'''R41	Manual Review Changes'''<br>
Headings in this report represent changes that were made during the Manual Review process (see Step 7 of the Planning Guide).
<br>
<br>
'''R42	Invalid Subfields'''<br>
Each field in this report contained an invalid subfield within the bibliographic record based on current standard cataloging practices.
<br>
<br>
'''R50	Invalid Data Format in Standard Identifier Fields'''<br>
The format of the data in an 010 (LCCN), 020 (ISBN), or 022 (ISSN) field is invalid and could not be corrected through automated processing. A common cause is presence of too many characters. The subfield code has been changed to $z (invalid) and the data has been retained and unchanged. Remember to change the subfield code back to $a if you correct the format of the invalid field.
<br>
<br>
'''R51	Unrecognized GMDs'''<br>
MARS 2.0 Update processing examines GMDs in the first subfield $h (Medium) in each 245 Title Statement. This report shows the 245 $h terms which were not found in the GMD list you selected (either AACR2 terms only, or the expanded set of GMDs that contain other commonly used GMDs). These GMDs may either be invalid or incorrectly spelled GMDs, or they may be non-standard GMDs used within your local catalog. See Step 2.9.

'''Note''':	If headings in this report contain GMDs which you treat as authorized in your catalog, you can provide a list of those GMDs to the MARS 2.0 staff. These GMDs will then be treated as authorized for your library and will not appear in future Unrecognized GMD reports.
<br>
<br>
'''R52	Duplicate Fields Found – Duplicate(s) Removed'''<br>
Headings in this report were listed as duplicates within the bibliographic record before MARS 2.0 processing removed at least one instance of the duplicated heading.
<br>
<br>
'''R53	Duplicate Fields Found – Duplicate(s) Retained'''<br>
Headings in this report are listed as duplicates within the bibliographic record. Despite MARS 2.0 processing removing most duplicate fields, there are some headings that were retained as duplicates.
<br>
<br>
'''R54	Field Too Long to Validate'''<br>
MARS 2.0 does not process fields that exceeded 1000 characters in length. These fields are retained without modification in the bibliographic record. Formatted Contents Note (505) fields are excluded from this report. These long fields sometimes are in indication of a damaged bibliographic record in which multiple fields are being merged into a single field.
<br>
<br>
'''R55	Empty Subfield Deleted'''<br>
Subfields with no information within the bibliographic record are removed according to current standard cataloging practices.
<br>
<br>
'''R56	Data Conversion Error'''<br>
Errors where data conversion was not able to successfully translate information are listed in this report.
<br>
<br>
'''R57	69X Local Tag Flipped'''<br>
Libraries with local tags in 69X fields where matching is requested will have headings in this report that found matches and flipped to corresponding LC 6XX tags.
<br>
<br>
'''R58	XREF Match'''<br>
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>
'''R60	Obsolete Tags Flipped'''<br>
The tags are corrected based on MARS 2.0 Bibliographic Validation process which converts obsolete fields to the current equivalent. This report does not include fields in which the tag was corrected during MARS 2.0 Authority Control processing.
<br>
<br>
'''R61	Obsolete Subfield Codes Deleted'''<br>
Obsolete subfield codes in each of the headings below are corrected during MARS 2.0 Bibliographic Validation which converts obsolete subfields to the current equivalent. This report does not include subfield codes which were corrected during MARS 2.0 Authority Control processing.

'''Note''':	Subfield code updates are based on the tag of the field. An incorrect tag can, therefore, result in incorrect subfield code updates.
<br>
<br>
'''R62	Obsolete Fields Removed'''<br>
The obsolete fields shown in this report are removed from the bibliographic record(s) based on current standard cataloging practices. Descriptions of these obsolete fields can normally be found in the current or previous editions of the ''MARC21 Format for Bibliographic Data''.
<br>
<br>
'''R63	Obsolete Subfields Removed'''<br>
Each field in this report contained an obsolete subfield which was removed from the bibliographic record based on current standard cataloging practices. Descriptions of these obsolete subfields are found in ''MARC21 Format for Bibliographic Data''.
<br>
<br>
'''R64	Empty Field Deleted'''<br>
In each of the records indicated within this report, MARS 2.0 removed a field that contained no information other than delimiters, subfield codes, and spaces.
<br>
<br>
'''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>
'''R67	New 007 Field Added'''<br>
In each of the records listed in this report, MARS 2.0 added an 007 field containing the field data shown.
<br>
<br>
'''R68	008 Fixed Field Values Updated'''<br>
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 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>
'''R69	Data Moved to New Field'''<br>
This report includes fields in which a standard ID number was moved to a new field due to a change in MARC standards. Examples of fields affected include 020 fields (with multiple $a subfields), the obsolete 260 subfield $d (moved to an 028 field) and the obsolete 262 field.
<br>
<br>
'''R70	LCCN Format Corrected'''<br>
In the LCCN 010 fields shown in this report, the format of the Library of Congress Control Number in the $a subfield was incorrect and was changed to the correct format.

'''Note''':	If no change is apparent in this report, the change made was in the number of final blank spaces in the LCCN (blank spaces are not represented in this report format).
<br>
<br>
'''R71	ISBN Format Corrected'''<br>
In the ISBN 020 fields shown in this report, the format of the ISBN was changed to the correct format. The report includes ISBN 020 fields which contained an obsolete subfield $b. This data was moved to the end of the subfield $a, as recommended by the Library of Congress. If there was no subfield $a into which to move the data, the subfield $b code was changed to $c, as recommended by the Library of Congress.
<br>
<br>
'''R72	ISSN Format Corrected'''<br>
In the ISSN 022 fields shown in this report, the format of the ISSN was changed to the correct format.
<br>
<br>
'''R73	GMD Changed'''<br>
The GMD or punctuation in the 245 $h subfield was modified during GMD Standardization processing (see Step 2.9).
<br>
<br>
'''R74	GMD Added'''<br>
The GMD in each heading in this report was added during MARS 2.0 Update processing. None of the fields in this report contained a 245 $h subfield prior to MARS 2.0 Update processing.
<br>
<br>
'''R75	GMD Brackets Added'''<br>
Brackets were added to the GMD in the 245h $h subfield in each of the headings in this report (see Step 2.9). Also includes any correction to spaces found before or after a bracket even if a bracket was not actually added.
<br>
<br>
'''R76	GMD Moved to Different Location in Heading'''<br>
The 245 $h GMD subfield was moved to a different location within the field in accordance with placement rules in ''MARC21 Format for Bibliographic Data''.
<br>
<br>
'''R77	Added Required Subfield $b to Field 017'''<br>
The Copyright Number 017 fields in this report did not contain a subfield $b, which is now a required subfield per MARC21 Format for Bibliographic Data. MARS 2.0 added a subfield $b and default data to field 017, as recommended by the Library of Congress.
<br>
<br>
'''R78	Added Required Subfield $b to Field 032'''<br>
The Copyright Number 032 fields in this report did not contain a subfield $b, which is now a required subfield per MARC21 Format for Bibliographic Data. MARS 2.0 added a subfield $b and default data to field 032, as recommended by the Library of Congress. Default data is defined as the name or abbreviation of the agency assigning the number [http://www.loc.gov/marc/bibliographic/bd032.html].
<br>
<br>
'''R79	Removed Blank Space Following Subfield Code'''<br>
One or more blank spaces were found following a subfield code in the fields in this report. These blank spaces (e.g., “$x History”) were removed in MARS 2.0 Update prior to MARS 2.0 Authority Control processing.
<br>
<br>
'''R80	Number of Indicators Corrected'''<br>
The variable fields (010-999 tag) listed in this report did not contain two indicators. MARS 2.0 Update programs added one or two blank indicators, or removed extra indicators, as appropriate so the field meets the ''MARC21 Format for Bibliographic Data'' requirements.
<br>
<br>
'''R81	Undefined Indicators Changed to Blank'''<br>
The variable fields (010-999 tag) listed in this report contained a non-blank value in an indicator position that is undefined in ''MARC21 Format for Bibliographic Data'' requirements. Since a blank space is the only allowed value in an undefined indicator position, these non-standard values were changed to blank spaces.
<br>
<br>
'''R82	Type of Name Entry Element Indicator Changed'''<br>
The Type of Name Entry Element Indicator in the headings in this report was corrected based on the correct value as shown in the LC authority files and / or ''MARC21 Format for Bibliographic Data''.
<br>
<br>
'''R83	Thesaurus Indicator Changed'''<br>
The Thesaurus Indicator (6XX second indicator, or source indicator) in the headings in this report was corrected based on MARS 2.0 authority control matching.
<br>
<br>
'''R84	Misc. Indicators Changed'''<br>
The indicators in the headings in this report were corrected based on ''MARC21 Format for Bibliographic Data''. This report does not include changes to standard authority control-related indicators such as Filing, Thesaurus, or Name Type Indicators.
<br>
<br>
'''R85	Conference Subfields Rearranged in AACR2 Order'''<br>
The order of the subfields in the conference name headings in this report were changed from pre-AACR2 to AACR2 subdivision order.
<br>
<br>
'''R86	Linked Field in $6 Changed Heading'''<br>
The fields in this report include all tags that are linked to ($6880) vernacular tags. The linked fields listed within this report represent only changed Romanized linked fields. Their corresponding ($6880) vernacular tags have not been changed. The bibliographic records need to be examined, and the vernacular tags need to be updated to reflect the changed Romanized versions of the authority headings.
<br>
<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,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.

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
<br>
<br>
'''R88	Invalid $6 Link Format'''<br>
Headings where the $6 link format does not match acceptable ranges are listed in this report.
<br>
<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>
<br>
'''R96	Bibliographic 790 Field Changed'''<br>
Headings in this report represent unassigned 790 fields that were changed during authority control processing.
<br>
<br>
'''R99	Primary Heading Untraced'''<br>
Primary headings that were untraced are listed in this report.

[[category:Profile Guide]]