AC Wiki - User contributions [en]

Step 6.0

2026-02-04T22:44:45Z

Casey: /* Bibliographic Update service */

==Step 6.0: Ongoing Services==
===Notification service===
The MARS 2.0 Authority Notification Service keeps your authority files up to date by notifying you when authority records are updated, replaced, or deleted, and supplying the updated records to your library. This service is very flexible, with options that make it easy to customize in order to meet local requirements.

With the exception of new records that replaced deleted records and unmatched headings (briefs), you do not receive new authority records through this service. The Current Cataloging Service provides new authority records.

No downtime is required for your catalog while this service is running.

This service works great in conjunction with an ILS that can globally update Bib Headings based on the new/changed authority records that are provided. If your ILS cannot do this, please talk to us about the Bibliographic Update Service (see below).

===Current Cataloging service===
The focus of the Current Cataloging Service is to incorporate Authority Control for your '''new''' bibliographic records into your regular cataloging workflow. There are two components to this service:

*Delivery of bibliographic records upgraded by MARS 2.0 Authority Control processing. All the same settings that you put into place with your Basefile Profile(s) are transferred to this process. This helps keep your catalog consistent!
*Delivery of new authority records not previously distributed to you that match headings in the bibliographic records. Also included are changed authorities that were previously distributed but also appear again in the current batch of bib records you provided.

'''All Ongoing Service plans intend to include Current Cataloging plus EITHER Authority Notification OR Bibliographic Update. However, there are some institutions that receive updated authority records from another source so Current Cataloging alone may be appropriate.'''

===Bibliographic Update service===
Some ILS don't have the ability to update Bibliographic Headings when Updated Authority Records are issued as part of the Authority Notification Service. This is where the Bibliographic Update Service comes in (Comprehensive Notification in Marcive parlance).

As part of this service, we store all Bibliographic Records you have sent for processing in a Master Bibliographic Database. This includes all Bib records from your Basefile plus all records from your Current Cataloging (New Bib) service. On an agreed frequency we will "re-authorize" the Bib Headings within the Master Bib Database to identify 1) New or Updated Authorities and 2) Bib headings to update. We will deliver back to you all new/updated authorities in addition to the Bib records that had headings updated.

However, the you '''must''' submit any updated or deleted bibliographic records prior to the scheduled run. Why? Because we don't want to change headings in Bibs that you either don't have any longer OR that you have edited in some other way. It helps us keep things sync'd so we don't "undo" edits you've painstakingly made.

The Bib Update Service does also require downtime within your catalog so that you are not making changes to records that could potentially be overlaid, thus having those changes lost. However, we have fine-tuned our process so instead of being down up to a week, we can usually complete the process within a day or two.

So, let's just reiterate that workflow:
# Backstage creates a database of Bibs based on your Basefile + all subsequent Current Cataloging batches
# Right before you're scheduled to process, YOU will send us your Changed and Deleted bib records
# We will import and overlay the older versions of those Changed/Deleted Bibs
# We will re-authorize all headings within the latest Master Bib Database. In this process we track which headings have changed as well as which authorities have changed
# We deliver changed Bibs plus any new/changed/deleted authorities back to you
# You load all files back into your system

You may be asking, "How is this different than the Current Cataloging service that I'm also subscribed to?" Great question! The Current Cataloging process involved MUCH MORE work on the Bibs. You may remember that in your basefile you had various clean-up routines happening that include MARC validation, stripping fields, RDA Enrichment, etc. in addition to authority matching. These other routines happen in the Current Cataloging service and NOT the Bibliographic Update Service aside for some punctuation fixes in the headings that were updated. The Current Cataloging and the Bibliographic Update are complementary services and provide you with a well rounded Authority Maintenance service.

==MARS 2.0 Master Authority File==
MARS 2.0 maintains a Master Authority File for your institution that has been supported by any of the MARS 2.0 Authority Control services. Your MARS 2.0 Master Authority File can actually consist of a number of separate authority files, based on the profile options selected by you and your staff:
*National-level authority records (separate files for LC, MeSH, NLC, etc.)
*Locally generated records that conflict with LC practices, but are required for your catalog
*Locally generated records to be replaced by national-level records
*National-level authority records with local tags & subfields to be merged with updates in national records
*MARS 2.0 unmatched heading records for all bibliographic headings that did not fully match a national-level authority record during the MARS 2.0 Authority Control processing of your bibliographic records

===National-level authority files===
The first step in your '''Notification Service''' is to compare each authority record previously distributed to you with the current version of the appropriate national-level authority files.

This service is available on a '''weekly''', '''monthly''', '''quarterly''', '''semi-annual''' or '''annual''' basis.

An '''update''' has occurred when a national-level authority record’s '''005 date and time of latest transaction''' field is later than the date and time in the 005 field in the record previously distributed to your library.

===Deleted records===
If one of the authority records (based on its control number) no longer exists in the national-level file, a '''delete''' has occurred (i.e., the national library has removed the record from the master copy of their authority file).

If you choose to receive updated records electronically, the deleted authority records will have the Record Status (Leader byte 05) set to '''d'''.

===Replaced records===
For each deleted authority record, MARS 2.0 programs search the entire appropriate national-level authority file to see if the deleted record has been replaced.

If the record’s control number is found in the appropriate field in the nationallevel file (for example, 010 $z for LC authority records) the deleted record has been '''replaced''' by a different authority record.

MARS 2.0 includes replacement records as '''new''' records in authority update files, and/or displays them in Authority Delete Reports.

===MARS 2.0 unmatched heading records===
Your MARS 2.0 Master Authority File includes a '''brief record''' generated for each '''unmatched''' heading during the MARS 2.0 Authority Control processing of bibliographic records.

During every subsequent '''Notification Service''', MARS 2.0 programs search for a national-level authority record corresponding to these unmatched headings.

When searching the national files, MARS 2.0 programs always check both the Established Heading (1XX) and See From xrefs (4XX) for potential matches. If one is found, the new authority record will be included in the authority distribution files.

The new national-level authority record will replace the MARS 2.0 unmatched heading record in your Master Authority File.

===Authority record status===
MARS 2.0 automatically sets the Record Status (Leader byte 05):
*New ('''n''') - these authorities are '''new''' to your catalog
*Changed ('''c''') - these records '''already exist''' in your catalog and are '''changed'''
*Deleted ('''d''') - these authorities need to be '''removed''' from your catalog

'''Note''': ''Authority records issued by LC with a '''record status''' of '''a''' (increase in encoding level) are distributed by MARS 2.0 with a record status of '''c''' (changed), since it is a '''change''' to a record in your local authority file.

Similarly, authority records issued by LC with a record status of '''s''' or '''x''' are distributed by MARS 2.0 with a record status of '''d''', since they need to be '''deleted''' from your local authority file.''

===Upgrading damaged authority records===
If authority records have been modified during previous cleanup projects by other vendors, records could be missing a necessary field (e.g., 005) or have damaged or missing LC Authority Record Numbers. Let your MARS 2.0 project manager know if your authority file needs extra attention.

== Topics ==
===Notification===
* [[Step 6.1|Step 6.1]] - Authority Update Frequency
* [[Step 6.2|Step 6.2]] - New & Changed Authorities
* [[Step 6.3|Step 6.3]] - Deleted Authorities
* [[Step 6.4|Step 6.4]] - Older Forms of Headings
* [[Step 6.5|Step 6.5]] - Library Adds & Deletes

===Current Cataloging===
* [[Step 6.6|Step 6.6]] - New Bibliographic Update Frequency
* [[Step 6.7|Step 6.7]] - New & Changed Authorities

===Bibliographic Update===
* [[Step 6.9|Step 6.9]] - Authority Update Frequency
* [[Step 6.10|Step 6.10]] - New & Changed Authorities
* [[Step 6.11|Step 6.11]] - Deleted Authorities
* [[Step 6.12|Step 6.12]] - Older Forms of Headings
* [[Step 6.13|Step 6.13]] - Bibliographic Changes & Deletes

==links==
<center>[[Step 6.1|6.1]] - [[Step 6.2|6.2]] - [[Step 6.3|6.3]] - [[Step 6.4|6.4]] - [[Step 6.5|6.5]] - [[Step 6.6|6.6]] - [[Step 6.7|6.7]] - [[Step 6.9|6.9]] - [[Step 6.10|6.10]] - [[Step 6.11|6.11]] - [[Step 6.12|6.12]] - [[Step 6.13|6.13]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 6.0

2026-02-04T22:11:17Z

Casey: /* Current Cataloging service */

==Step 6.0: Ongoing Services==
===Notification service===
The MARS 2.0 Authority Notification Service keeps your authority files up to date by notifying you when authority records are updated, replaced, or deleted, and supplying the updated records to your library. This service is very flexible, with options that make it easy to customize in order to meet local requirements.

With the exception of new records that replaced deleted records and unmatched headings (briefs), you do not receive new authority records through this service. The Current Cataloging Service provides new authority records.

No downtime is required for your catalog while this service is running.

This service works great in conjunction with an ILS that can globally update Bib Headings based on the new/changed authority records that are provided. If your ILS cannot do this, please talk to us about the Bibliographic Update Service (see below).

===Current Cataloging service===
The focus of the Current Cataloging Service is to incorporate Authority Control for your '''new''' bibliographic records into your regular cataloging workflow. There are two components to this service:

*Delivery of bibliographic records upgraded by MARS 2.0 Authority Control processing. All the same settings that you put into place with your Basefile Profile(s) are transferred to this process. This helps keep your catalog consistent!
*Delivery of new authority records not previously distributed to you that match headings in the bibliographic records. Also included are changed authorities that were previously distributed but also appear again in the current batch of bib records you provided.

'''All Ongoing Service plans intend to include Current Cataloging plus EITHER Authority Notification OR Bibliographic Update. However, there are some institutions that receive updated authority records from another source so Current Cataloging alone may be appropriate.'''

===Bibliographic Update service===
Some ILS don't have the ability to update Bibliographic Headings when Updated Authority Records are issued as part of the Authority Notification Service. This is where the Bibliographic Update Service comes in (Comprehensive Notification in Marcive parlance).

As part of this service, we store all Bibliographic Records you have sent for processing in a Master Bibliographic Database. This includes all Bib records from your Basefile plus all records from your Current Cataloging (New Bib) service. On an agreed frequency we will "re-authorize" the Bib Headings within the Master Bib Database to identify 1) New or Updated Authorities and 2) Bib headings to update. We will deliver back to you all new/updated authorities in addition to the Bib records that had headings updated.

However, the you '''must''' submit any updated or deleted bibliographic records prior to the scheduled run. Why? Because we don't want to change headings in Bibs that you either don't have any longer OR that you have edited in some other way. It helps us keep things sync'd so we don't "undo" edits you've painstakingly made.

The Bib Update Service does also require downtime within your catalog so that you are not making changes to records that could potentially be overlaid, thus having those changes lost. However, we have fine-tuned our process so instead of being down up to a week, we can usually complete the process within a day or two.

So, let's just reiterate that workflow:
# Backstage creates a database of Bibs based on your Basefile + all subsequent Current Cataloging batches
# Right before you're scheduled to process, YOU will send us your Changed and Deleted bib records
# We will re-authorize all headings within the Bib File. In this process we track which headings have changed as well as which authorities have changed
# We deliver changed Bibs plus any new/changed/deleted authorities back to you
# You load all files back into your system

You may be asking, "How is this different than the Current Cataloging service that I'm also subscribed to?" Great question! The Current Cataloging process involved MUCH MORE work on the Bibs. You may remember that in your basefile you had various clean-up routines happening that include MARC validation, stripping fields, RDA Enrichment, etc. in addition to authority matching. These other routines happen in the Current Cataloging service and NOT the Bibliographic Update Service aside for some punctuation fixes in the headings that were updated. The Current Cataloging and the Bibliographic Update are complementary services and provide you with a well rounded Authority Maintenance service.

==MARS 2.0 Master Authority File==
MARS 2.0 maintains a Master Authority File for your institution that has been supported by any of the MARS 2.0 Authority Control services. Your MARS 2.0 Master Authority File can actually consist of a number of separate authority files, based on the profile options selected by you and your staff:
*National-level authority records (separate files for LC, MeSH, NLC, etc.)
*Locally generated records that conflict with LC practices, but are required for your catalog
*Locally generated records to be replaced by national-level records
*National-level authority records with local tags & subfields to be merged with updates in national records
*MARS 2.0 unmatched heading records for all bibliographic headings that did not fully match a national-level authority record during the MARS 2.0 Authority Control processing of your bibliographic records

===National-level authority files===
The first step in your '''Notification Service''' is to compare each authority record previously distributed to you with the current version of the appropriate national-level authority files.

This service is available on a '''weekly''', '''monthly''', '''quarterly''', '''semi-annual''' or '''annual''' basis.

An '''update''' has occurred when a national-level authority record’s '''005 date and time of latest transaction''' field is later than the date and time in the 005 field in the record previously distributed to your library.

===Deleted records===
If one of the authority records (based on its control number) no longer exists in the national-level file, a '''delete''' has occurred (i.e., the national library has removed the record from the master copy of their authority file).

If you choose to receive updated records electronically, the deleted authority records will have the Record Status (Leader byte 05) set to '''d'''.

===Replaced records===
For each deleted authority record, MARS 2.0 programs search the entire appropriate national-level authority file to see if the deleted record has been replaced.

If the record’s control number is found in the appropriate field in the nationallevel file (for example, 010 $z for LC authority records) the deleted record has been '''replaced''' by a different authority record.

MARS 2.0 includes replacement records as '''new''' records in authority update files, and/or displays them in Authority Delete Reports.

===MARS 2.0 unmatched heading records===
Your MARS 2.0 Master Authority File includes a '''brief record''' generated for each '''unmatched''' heading during the MARS 2.0 Authority Control processing of bibliographic records.

During every subsequent '''Notification Service''', MARS 2.0 programs search for a national-level authority record corresponding to these unmatched headings.

When searching the national files, MARS 2.0 programs always check both the Established Heading (1XX) and See From xrefs (4XX) for potential matches. If one is found, the new authority record will be included in the authority distribution files.

The new national-level authority record will replace the MARS 2.0 unmatched heading record in your Master Authority File.

===Authority record status===
MARS 2.0 automatically sets the Record Status (Leader byte 05):
*New ('''n''') - these authorities are '''new''' to your catalog
*Changed ('''c''') - these records '''already exist''' in your catalog and are '''changed'''
*Deleted ('''d''') - these authorities need to be '''removed''' from your catalog

'''Note''': ''Authority records issued by LC with a '''record status''' of '''a''' (increase in encoding level) are distributed by MARS 2.0 with a record status of '''c''' (changed), since it is a '''change''' to a record in your local authority file.

Similarly, authority records issued by LC with a record status of '''s''' or '''x''' are distributed by MARS 2.0 with a record status of '''d''', since they need to be '''deleted''' from your local authority file.''

===Upgrading damaged authority records===
If authority records have been modified during previous cleanup projects by other vendors, records could be missing a necessary field (e.g., 005) or have damaged or missing LC Authority Record Numbers. Let your MARS 2.0 project manager know if your authority file needs extra attention.

== Topics ==
===Notification===
* [[Step 6.1|Step 6.1]] - Authority Update Frequency
* [[Step 6.2|Step 6.2]] - New & Changed Authorities
* [[Step 6.3|Step 6.3]] - Deleted Authorities
* [[Step 6.4|Step 6.4]] - Older Forms of Headings
* [[Step 6.5|Step 6.5]] - Library Adds & Deletes

===Current Cataloging===
* [[Step 6.6|Step 6.6]] - New Bibliographic Update Frequency
* [[Step 6.7|Step 6.7]] - New & Changed Authorities

===Bibliographic Update===
* [[Step 6.9|Step 6.9]] - Authority Update Frequency
* [[Step 6.10|Step 6.10]] - New & Changed Authorities
* [[Step 6.11|Step 6.11]] - Deleted Authorities
* [[Step 6.12|Step 6.12]] - Older Forms of Headings
* [[Step 6.13|Step 6.13]] - Bibliographic Changes & Deletes

==links==
<center>[[Step 6.1|6.1]] - [[Step 6.2|6.2]] - [[Step 6.3|6.3]] - [[Step 6.4|6.4]] - [[Step 6.5|6.5]] - [[Step 6.6|6.6]] - [[Step 6.7|6.7]] - [[Step 6.9|6.9]] - [[Step 6.10|6.10]] - [[Step 6.11|6.11]] - [[Step 6.12|6.12]] - [[Step 6.13|6.13]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 6.0

2026-02-04T22:09:16Z

Casey: /* Notification service */

==Step 6.0: Ongoing Services==
===Notification service===
The MARS 2.0 Authority Notification Service keeps your authority files up to date by notifying you when authority records are updated, replaced, or deleted, and supplying the updated records to your library. This service is very flexible, with options that make it easy to customize in order to meet local requirements.

With the exception of new records that replaced deleted records and unmatched headings (briefs), you do not receive new authority records through this service. The Current Cataloging Service provides new authority records.

No downtime is required for your catalog while this service is running.

This service works great in conjunction with an ILS that can globally update Bib Headings based on the new/changed authority records that are provided. If your ILS cannot do this, please talk to us about the Bibliographic Update Service (see below).

===Current Cataloging service===
The focus of the Current Cataloging Service is to incorporate Authority Control for your '''new''' bibliographic records into your regular cataloging workflow. There are two components to this service:

*Delivery of bibliographic records upgraded by MARS 2.0 Authority Control processing. All the same settings that you put into place with your Basefile Profile(s) are transferred to this process. This helps keep your catalog consistent!
*Delivery of new authority records not previously distributed to you that match headings in the bibliographic records. Also included are changed authorities that were previously distributed but also appear again in the current batch of bib records you provided.

===Bibliographic Update service===
Some ILS don't have the ability to update Bibliographic Headings when Updated Authority Records are issued as part of the Authority Notification Service. This is where the Bibliographic Update Service comes in (Comprehensive Notification in Marcive parlance).

As part of this service, we store all Bibliographic Records you have sent for processing in a Master Bibliographic Database. This includes all Bib records from your Basefile plus all records from your Current Cataloging (New Bib) service. On an agreed frequency we will "re-authorize" the Bib Headings within the Master Bib Database to identify 1) New or Updated Authorities and 2) Bib headings to update. We will deliver back to you all new/updated authorities in addition to the Bib records that had headings updated.

However, the you '''must''' submit any updated or deleted bibliographic records prior to the scheduled run. Why? Because we don't want to change headings in Bibs that you either don't have any longer OR that you have edited in some other way. It helps us keep things sync'd so we don't "undo" edits you've painstakingly made.

The Bib Update Service does also require downtime within your catalog so that you are not making changes to records that could potentially be overlaid, thus having those changes lost. However, we have fine-tuned our process so instead of being down up to a week, we can usually complete the process within a day or two.

So, let's just reiterate that workflow:
# Backstage creates a database of Bibs based on your Basefile + all subsequent Current Cataloging batches
# Right before you're scheduled to process, YOU will send us your Changed and Deleted bib records
# We will re-authorize all headings within the Bib File. In this process we track which headings have changed as well as which authorities have changed
# We deliver changed Bibs plus any new/changed/deleted authorities back to you
# You load all files back into your system

You may be asking, "How is this different than the Current Cataloging service that I'm also subscribed to?" Great question! The Current Cataloging process involved MUCH MORE work on the Bibs. You may remember that in your basefile you had various clean-up routines happening that include MARC validation, stripping fields, RDA Enrichment, etc. in addition to authority matching. These other routines happen in the Current Cataloging service and NOT the Bibliographic Update Service aside for some punctuation fixes in the headings that were updated. The Current Cataloging and the Bibliographic Update are complementary services and provide you with a well rounded Authority Maintenance service.

==MARS 2.0 Master Authority File==
MARS 2.0 maintains a Master Authority File for your institution that has been supported by any of the MARS 2.0 Authority Control services. Your MARS 2.0 Master Authority File can actually consist of a number of separate authority files, based on the profile options selected by you and your staff:
*National-level authority records (separate files for LC, MeSH, NLC, etc.)
*Locally generated records that conflict with LC practices, but are required for your catalog
*Locally generated records to be replaced by national-level records
*National-level authority records with local tags & subfields to be merged with updates in national records
*MARS 2.0 unmatched heading records for all bibliographic headings that did not fully match a national-level authority record during the MARS 2.0 Authority Control processing of your bibliographic records

===National-level authority files===
The first step in your '''Notification Service''' is to compare each authority record previously distributed to you with the current version of the appropriate national-level authority files.

This service is available on a '''weekly''', '''monthly''', '''quarterly''', '''semi-annual''' or '''annual''' basis.

An '''update''' has occurred when a national-level authority record’s '''005 date and time of latest transaction''' field is later than the date and time in the 005 field in the record previously distributed to your library.

===Deleted records===
If one of the authority records (based on its control number) no longer exists in the national-level file, a '''delete''' has occurred (i.e., the national library has removed the record from the master copy of their authority file).

If you choose to receive updated records electronically, the deleted authority records will have the Record Status (Leader byte 05) set to '''d'''.

===Replaced records===
For each deleted authority record, MARS 2.0 programs search the entire appropriate national-level authority file to see if the deleted record has been replaced.

If the record’s control number is found in the appropriate field in the nationallevel file (for example, 010 $z for LC authority records) the deleted record has been '''replaced''' by a different authority record.

MARS 2.0 includes replacement records as '''new''' records in authority update files, and/or displays them in Authority Delete Reports.

===MARS 2.0 unmatched heading records===
Your MARS 2.0 Master Authority File includes a '''brief record''' generated for each '''unmatched''' heading during the MARS 2.0 Authority Control processing of bibliographic records.

During every subsequent '''Notification Service''', MARS 2.0 programs search for a national-level authority record corresponding to these unmatched headings.

When searching the national files, MARS 2.0 programs always check both the Established Heading (1XX) and See From xrefs (4XX) for potential matches. If one is found, the new authority record will be included in the authority distribution files.

The new national-level authority record will replace the MARS 2.0 unmatched heading record in your Master Authority File.

===Authority record status===
MARS 2.0 automatically sets the Record Status (Leader byte 05):
*New ('''n''') - these authorities are '''new''' to your catalog
*Changed ('''c''') - these records '''already exist''' in your catalog and are '''changed'''
*Deleted ('''d''') - these authorities need to be '''removed''' from your catalog

'''Note''': ''Authority records issued by LC with a '''record status''' of '''a''' (increase in encoding level) are distributed by MARS 2.0 with a record status of '''c''' (changed), since it is a '''change''' to a record in your local authority file.

Similarly, authority records issued by LC with a record status of '''s''' or '''x''' are distributed by MARS 2.0 with a record status of '''d''', since they need to be '''deleted''' from your local authority file.''

===Upgrading damaged authority records===
If authority records have been modified during previous cleanup projects by other vendors, records could be missing a necessary field (e.g., 005) or have damaged or missing LC Authority Record Numbers. Let your MARS 2.0 project manager know if your authority file needs extra attention.

== Topics ==
===Notification===
* [[Step 6.1|Step 6.1]] - Authority Update Frequency
* [[Step 6.2|Step 6.2]] - New & Changed Authorities
* [[Step 6.3|Step 6.3]] - Deleted Authorities
* [[Step 6.4|Step 6.4]] - Older Forms of Headings
* [[Step 6.5|Step 6.5]] - Library Adds & Deletes

===Current Cataloging===
* [[Step 6.6|Step 6.6]] - New Bibliographic Update Frequency
* [[Step 6.7|Step 6.7]] - New & Changed Authorities

===Bibliographic Update===
* [[Step 6.9|Step 6.9]] - Authority Update Frequency
* [[Step 6.10|Step 6.10]] - New & Changed Authorities
* [[Step 6.11|Step 6.11]] - Deleted Authorities
* [[Step 6.12|Step 6.12]] - Older Forms of Headings
* [[Step 6.13|Step 6.13]] - Bibliographic Changes & Deletes

==links==
<center>[[Step 6.1|6.1]] - [[Step 6.2|6.2]] - [[Step 6.3|6.3]] - [[Step 6.4|6.4]] - [[Step 6.5|6.5]] - [[Step 6.6|6.6]] - [[Step 6.7|6.7]] - [[Step 6.9|6.9]] - [[Step 6.10|6.10]] - [[Step 6.11|6.11]] - [[Step 6.12|6.12]] - [[Step 6.13|6.13]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 6.0

2026-02-04T22:07:30Z

Casey: /* Current Cataloging service */

==Step 6.0: Ongoing Services==
===Notification service===
The MARS 2.0 Authority Notification Service keeps your authority files up to date by notifying you when authority records are updated, replaced, or deleted, and supplying the updated records to your library. This service is very flexible, with options that make it easy to customize in order to meet local requirements.

With the exception of new records that replaced deleted records and unmatched headings (briefs), you do not receive new authority records through this service. The Current Cataloging Service provides new authority records.

No downtime is required for your catalog while this service is running.

===Current Cataloging service===
The focus of the Current Cataloging Service is to incorporate Authority Control for your '''new''' bibliographic records into your regular cataloging workflow. There are two components to this service:

*Delivery of bibliographic records upgraded by MARS 2.0 Authority Control processing. All the same settings that you put into place with your Basefile Profile(s) are transferred to this process. This helps keep your catalog consistent!
*Delivery of new authority records not previously distributed to you that match headings in the bibliographic records. Also included are changed authorities that were previously distributed but also appear again in the current batch of bib records you provided.

===Bibliographic Update service===
Some ILS don't have the ability to update Bibliographic Headings when Updated Authority Records are issued as part of the Authority Notification Service. This is where the Bibliographic Update Service comes in (Comprehensive Notification in Marcive parlance).

As part of this service, we store all Bibliographic Records you have sent for processing in a Master Bibliographic Database. This includes all Bib records from your Basefile plus all records from your Current Cataloging (New Bib) service. On an agreed frequency we will "re-authorize" the Bib Headings within the Master Bib Database to identify 1) New or Updated Authorities and 2) Bib headings to update. We will deliver back to you all new/updated authorities in addition to the Bib records that had headings updated.

However, the you '''must''' submit any updated or deleted bibliographic records prior to the scheduled run. Why? Because we don't want to change headings in Bibs that you either don't have any longer OR that you have edited in some other way. It helps us keep things sync'd so we don't "undo" edits you've painstakingly made.

The Bib Update Service does also require downtime within your catalog so that you are not making changes to records that could potentially be overlaid, thus having those changes lost. However, we have fine-tuned our process so instead of being down up to a week, we can usually complete the process within a day or two.

So, let's just reiterate that workflow:
# Backstage creates a database of Bibs based on your Basefile + all subsequent Current Cataloging batches
# Right before you're scheduled to process, YOU will send us your Changed and Deleted bib records
# We will re-authorize all headings within the Bib File. In this process we track which headings have changed as well as which authorities have changed
# We deliver changed Bibs plus any new/changed/deleted authorities back to you
# You load all files back into your system

You may be asking, "How is this different than the Current Cataloging service that I'm also subscribed to?" Great question! The Current Cataloging process involved MUCH MORE work on the Bibs. You may remember that in your basefile you had various clean-up routines happening that include MARC validation, stripping fields, RDA Enrichment, etc. in addition to authority matching. These other routines happen in the Current Cataloging service and NOT the Bibliographic Update Service aside for some punctuation fixes in the headings that were updated. The Current Cataloging and the Bibliographic Update are complementary services and provide you with a well rounded Authority Maintenance service.

==MARS 2.0 Master Authority File==
MARS 2.0 maintains a Master Authority File for your institution that has been supported by any of the MARS 2.0 Authority Control services. Your MARS 2.0 Master Authority File can actually consist of a number of separate authority files, based on the profile options selected by you and your staff:
*National-level authority records (separate files for LC, MeSH, NLC, etc.)
*Locally generated records that conflict with LC practices, but are required for your catalog
*Locally generated records to be replaced by national-level records
*National-level authority records with local tags & subfields to be merged with updates in national records
*MARS 2.0 unmatched heading records for all bibliographic headings that did not fully match a national-level authority record during the MARS 2.0 Authority Control processing of your bibliographic records

===National-level authority files===
The first step in your '''Notification Service''' is to compare each authority record previously distributed to you with the current version of the appropriate national-level authority files.

This service is available on a '''weekly''', '''monthly''', '''quarterly''', '''semi-annual''' or '''annual''' basis.

An '''update''' has occurred when a national-level authority record’s '''005 date and time of latest transaction''' field is later than the date and time in the 005 field in the record previously distributed to your library.

===Deleted records===
If one of the authority records (based on its control number) no longer exists in the national-level file, a '''delete''' has occurred (i.e., the national library has removed the record from the master copy of their authority file).

If you choose to receive updated records electronically, the deleted authority records will have the Record Status (Leader byte 05) set to '''d'''.

===Replaced records===
For each deleted authority record, MARS 2.0 programs search the entire appropriate national-level authority file to see if the deleted record has been replaced.

If the record’s control number is found in the appropriate field in the nationallevel file (for example, 010 $z for LC authority records) the deleted record has been '''replaced''' by a different authority record.

MARS 2.0 includes replacement records as '''new''' records in authority update files, and/or displays them in Authority Delete Reports.

===MARS 2.0 unmatched heading records===
Your MARS 2.0 Master Authority File includes a '''brief record''' generated for each '''unmatched''' heading during the MARS 2.0 Authority Control processing of bibliographic records.

During every subsequent '''Notification Service''', MARS 2.0 programs search for a national-level authority record corresponding to these unmatched headings.

When searching the national files, MARS 2.0 programs always check both the Established Heading (1XX) and See From xrefs (4XX) for potential matches. If one is found, the new authority record will be included in the authority distribution files.

The new national-level authority record will replace the MARS 2.0 unmatched heading record in your Master Authority File.

===Authority record status===
MARS 2.0 automatically sets the Record Status (Leader byte 05):
*New ('''n''') - these authorities are '''new''' to your catalog
*Changed ('''c''') - these records '''already exist''' in your catalog and are '''changed'''
*Deleted ('''d''') - these authorities need to be '''removed''' from your catalog

'''Note''': ''Authority records issued by LC with a '''record status''' of '''a''' (increase in encoding level) are distributed by MARS 2.0 with a record status of '''c''' (changed), since it is a '''change''' to a record in your local authority file.

Similarly, authority records issued by LC with a record status of '''s''' or '''x''' are distributed by MARS 2.0 with a record status of '''d''', since they need to be '''deleted''' from your local authority file.''

===Upgrading damaged authority records===
If authority records have been modified during previous cleanup projects by other vendors, records could be missing a necessary field (e.g., 005) or have damaged or missing LC Authority Record Numbers. Let your MARS 2.0 project manager know if your authority file needs extra attention.

== Topics ==
===Notification===
* [[Step 6.1|Step 6.1]] - Authority Update Frequency
* [[Step 6.2|Step 6.2]] - New & Changed Authorities
* [[Step 6.3|Step 6.3]] - Deleted Authorities
* [[Step 6.4|Step 6.4]] - Older Forms of Headings
* [[Step 6.5|Step 6.5]] - Library Adds & Deletes

===Current Cataloging===
* [[Step 6.6|Step 6.6]] - New Bibliographic Update Frequency
* [[Step 6.7|Step 6.7]] - New & Changed Authorities

===Bibliographic Update===
* [[Step 6.9|Step 6.9]] - Authority Update Frequency
* [[Step 6.10|Step 6.10]] - New & Changed Authorities
* [[Step 6.11|Step 6.11]] - Deleted Authorities
* [[Step 6.12|Step 6.12]] - Older Forms of Headings
* [[Step 6.13|Step 6.13]] - Bibliographic Changes & Deletes

==links==
<center>[[Step 6.1|6.1]] - [[Step 6.2|6.2]] - [[Step 6.3|6.3]] - [[Step 6.4|6.4]] - [[Step 6.5|6.5]] - [[Step 6.6|6.6]] - [[Step 6.7|6.7]] - [[Step 6.9|6.9]] - [[Step 6.10|6.10]] - [[Step 6.11|6.11]] - [[Step 6.12|6.12]] - [[Step 6.13|6.13]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 6.0

2026-02-04T22:03:22Z

Casey: /* Bibliographic Update service */ Fixed the description so it's more helpful

==Step 6.0: Ongoing Services==
===Notification service===
The MARS 2.0 Authority Notification Service keeps your authority files up to date by notifying you when authority records are updated, replaced, or deleted, and supplying the updated records to your library. This service is very flexible, with options that make it easy to customize in order to meet local requirements.

With the exception of new records that replaced deleted records and unmatched headings (briefs), you do not receive new authority records through this service. The Current Cataloging Service provides new authority records.

No downtime is required for your catalog while this service is running.

===Current Cataloging service===
The focus of the Current Cataloging Service is to incorporate Authority Control for your '''new''' bibliographic records into your regular cataloging workflow. There are two components to this service:

*Delivery of bibliographic records upgraded by MARS 2.0 Authority Control processing
*Delivery of new authority records not previously distributed to you that match headings in the bibliographic records

===Bibliographic Update service===
Some ILS don't have the ability to update Bibliographic Headings when Updated Authority Records are issued as part of the Authority Notification Service. This is where the Bibliographic Update Service comes in (Comprehensive Notification in Marcive parlance).

As part of this service, we store all Bibliographic Records you have sent for processing in a Master Bibliographic Database. This includes all Bib records from your Basefile plus all records from your Current Cataloging (New Bib) service. On an agreed frequency we will "re-authorize" the Bib Headings within the Master Bib Database to identify 1) New or Updated Authorities and 2) Bib headings to update. We will deliver back to you all new/updated authorities in addition to the Bib records that had headings updated.

However, the you '''must''' submit any updated or deleted bibliographic records prior to the scheduled run. Why? Because we don't want to change headings in Bibs that you either don't have any longer OR that you have edited in some other way. It helps us keep things sync'd so we don't "undo" edits you've painstakingly made.

The Bib Update Service does also require downtime within your catalog so that you are not making changes to records that could potentially be overlaid, thus having those changes lost. However, we have fine-tuned our process so instead of being down up to a week, we can usually complete the process within a day or two.

So, let's just reiterate that workflow:
# Backstage creates a database of Bibs based on your Basefile + all subsequent Current Cataloging batches
# Right before you're scheduled to process, YOU will send us your Changed and Deleted bib records
# We will re-authorize all headings within the Bib File. In this process we track which headings have changed as well as which authorities have changed
# We deliver changed Bibs plus any new/changed/deleted authorities back to you
# You load all files back into your system

You may be asking, "How is this different than the Current Cataloging service that I'm also subscribed to?" Great question! The Current Cataloging process involved MUCH MORE work on the Bibs. You may remember that in your basefile you had various clean-up routines happening that include MARC validation, stripping fields, RDA Enrichment, etc. in addition to authority matching. These other routines happen in the Current Cataloging service and NOT the Bibliographic Update Service aside for some punctuation fixes in the headings that were updated. The Current Cataloging and the Bibliographic Update are complementary services and provide you with a well rounded Authority Maintenance service.

==MARS 2.0 Master Authority File==
MARS 2.0 maintains a Master Authority File for your institution that has been supported by any of the MARS 2.0 Authority Control services. Your MARS 2.0 Master Authority File can actually consist of a number of separate authority files, based on the profile options selected by you and your staff:
*National-level authority records (separate files for LC, MeSH, NLC, etc.)
*Locally generated records that conflict with LC practices, but are required for your catalog
*Locally generated records to be replaced by national-level records
*National-level authority records with local tags & subfields to be merged with updates in national records
*MARS 2.0 unmatched heading records for all bibliographic headings that did not fully match a national-level authority record during the MARS 2.0 Authority Control processing of your bibliographic records

===National-level authority files===
The first step in your '''Notification Service''' is to compare each authority record previously distributed to you with the current version of the appropriate national-level authority files.

This service is available on a '''weekly''', '''monthly''', '''quarterly''', '''semi-annual''' or '''annual''' basis.

An '''update''' has occurred when a national-level authority record’s '''005 date and time of latest transaction''' field is later than the date and time in the 005 field in the record previously distributed to your library.

===Deleted records===
If one of the authority records (based on its control number) no longer exists in the national-level file, a '''delete''' has occurred (i.e., the national library has removed the record from the master copy of their authority file).

If you choose to receive updated records electronically, the deleted authority records will have the Record Status (Leader byte 05) set to '''d'''.

===Replaced records===
For each deleted authority record, MARS 2.0 programs search the entire appropriate national-level authority file to see if the deleted record has been replaced.

If the record’s control number is found in the appropriate field in the nationallevel file (for example, 010 $z for LC authority records) the deleted record has been '''replaced''' by a different authority record.

MARS 2.0 includes replacement records as '''new''' records in authority update files, and/or displays them in Authority Delete Reports.

===MARS 2.0 unmatched heading records===
Your MARS 2.0 Master Authority File includes a '''brief record''' generated for each '''unmatched''' heading during the MARS 2.0 Authority Control processing of bibliographic records.

During every subsequent '''Notification Service''', MARS 2.0 programs search for a national-level authority record corresponding to these unmatched headings.

When searching the national files, MARS 2.0 programs always check both the Established Heading (1XX) and See From xrefs (4XX) for potential matches. If one is found, the new authority record will be included in the authority distribution files.

The new national-level authority record will replace the MARS 2.0 unmatched heading record in your Master Authority File.

===Authority record status===
MARS 2.0 automatically sets the Record Status (Leader byte 05):
*New ('''n''') - these authorities are '''new''' to your catalog
*Changed ('''c''') - these records '''already exist''' in your catalog and are '''changed'''
*Deleted ('''d''') - these authorities need to be '''removed''' from your catalog

'''Note''': ''Authority records issued by LC with a '''record status''' of '''a''' (increase in encoding level) are distributed by MARS 2.0 with a record status of '''c''' (changed), since it is a '''change''' to a record in your local authority file.

Similarly, authority records issued by LC with a record status of '''s''' or '''x''' are distributed by MARS 2.0 with a record status of '''d''', since they need to be '''deleted''' from your local authority file.''

===Upgrading damaged authority records===
If authority records have been modified during previous cleanup projects by other vendors, records could be missing a necessary field (e.g., 005) or have damaged or missing LC Authority Record Numbers. Let your MARS 2.0 project manager know if your authority file needs extra attention.

== Topics ==
===Notification===
* [[Step 6.1|Step 6.1]] - Authority Update Frequency
* [[Step 6.2|Step 6.2]] - New & Changed Authorities
* [[Step 6.3|Step 6.3]] - Deleted Authorities
* [[Step 6.4|Step 6.4]] - Older Forms of Headings
* [[Step 6.5|Step 6.5]] - Library Adds & Deletes

===Current Cataloging===
* [[Step 6.6|Step 6.6]] - New Bibliographic Update Frequency
* [[Step 6.7|Step 6.7]] - New & Changed Authorities

===Bibliographic Update===
* [[Step 6.9|Step 6.9]] - Authority Update Frequency
* [[Step 6.10|Step 6.10]] - New & Changed Authorities
* [[Step 6.11|Step 6.11]] - Deleted Authorities
* [[Step 6.12|Step 6.12]] - Older Forms of Headings
* [[Step 6.13|Step 6.13]] - Bibliographic Changes & Deletes

==links==
<center>[[Step 6.1|6.1]] - [[Step 6.2|6.2]] - [[Step 6.3|6.3]] - [[Step 6.4|6.4]] - [[Step 6.5|6.5]] - [[Step 6.6|6.6]] - [[Step 6.7|6.7]] - [[Step 6.9|6.9]] - [[Step 6.10|6.10]] - [[Step 6.11|6.11]] - [[Step 6.12|6.12]] - [[Step 6.13|6.13]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.0

2026-01-21T20:47:07Z

Casey: /* National authority files */ UPdated NLC counts based on full downloads (I know we technically have more that we didn't know if/what to delete)

==Authority Cleanup Overview==
The first phase of MARS 2.0 Authority Control comprises a battery of routines that update and correct individual subfields and contiguous pairs of subfields, the purpose of which is to increase the likelihood of finding the appropriate authority match.

These corrections are based on a number of subfield update tables, maintained by MARS 2.0 authorities librarians.

MARS 2.0 subfield correction routines include:
* Updating obsolete forms of subdivisions to the current form
* Correcting common typographical errors
* Expanding abbreviations in subject subfields to their fuller form
* Converting common direct geographic subdivisions to their indirect form
* Deleting subject subdivisions which have been canceled or discontinued
* Correcting spacing, capitalization, and punctuation

===Update obsolete subdivisions===
MARS 2.0 uses a number of subfield correction tables to correct common errors in LC subfields


— Relations (General) with the United States

'''changes to''':
— Relations — United States

===Correct typographical errors===
MARS 2.0 also uses the subfield correction tables to correct common spelling errors in LC subdivisions:

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Histroy || History || LC 6XX $x
|-
| Untied States || United States || LC 650 $z and 651 $a
|}
<div style=clear:both></div>

===Expand abbreviations===
The subfield correction tables also support the expansion of outdated or invalid abbreviations in LC headings to the full form. Changes are made only when the outdated or invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Outdated / Invalid
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Hist. & crit. || History and criticism || LC 6XX $x
|-
| U.S. || United States || LC 651 $a, X10 $a, and 6XX $z
|-
| Econ. cond. || Economic conditions || LC 6XX $x
|}
<div style=clear:both></div>

===Direct-to-indirect geographic conversion===
MARS 2.0 uses a table to convert direct geographic subdivisions to the indirect form. Changes are made by the direct-to-indirect subfield conversion program only when the invalid form is the entire text of the $z '''and''' there is only one $z in the heading:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Direct Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $z Paris || $z France $z Paris || LC 6XX fields
|-
| $z Jefferson Co., Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|-
| $z Jefferson County, Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|}
<div style=clear:both></div>

===Chronological conversion===
MARS 2.0 uses a table to convert chronological headings '''$y''' to their correct form. Corrections are made to spelling and punctuation as well as to format:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $y Twentieth century || $y 20th century || LC 6XX fields
|-
| $z 20th century || $y 20th century || LC 6XX fields
|-
| $y 20th centry ||$y 20th century ||LC 6XX fields
|}
<div style=clear:both></div>

===Delete obsolete subdivisions===
MARS 2.0 uses a subfield deletion table to eliminate canceled subfields from LC bibliographic headings, deleting subfields only when the invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Deleted
! style="background:silver" | Field / Subfield
|-
| Addresses, essays, lectures || 6XX $x
|-
| Addresses, sermons, etc. || 6XX $x
|-
| Collected works || 6XX $x
|}
<div style=clear:both></div>

The subfield deletion table also includes common misspellings and typographical errors:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Field / Subfield
|-
| Adresses, essays, lectures || 6XX $x
|-
| Addressses, essays, lectures || 6XX $x
|-
| Collected work || 6XX $x
|}
<div style=clear:both></div>

===Retain selected subdivisions===
The subfield deletion table includes a section that prevents subfield conversions and deletions in headings meeting specific criteria.

— Yearbooks

'''changes to''':
— Periodicals
except when — Yearbooks ''is part of the subfield pair:''
— Students — Yearbooks

===Correct spacing, capitalization, and punctuation===
Most errors in spacing, capitalization and punctuation are corrected as an integral part of the authority cleanup and authority matching processes. Routines are also run to correct spacing and punctuation on the following fields:

1XX, 240, 243, 245, 260, 4XX, 6XX, 7XX, 8XX

These processes eliminate any excess spaces in each field, makes sure each field has the correct punctuation within and between each subfield, and makes sure each field has ending punctuation.


'''original headings''':
100 10 $a Black, Adam, $d 1974- .$t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001, $c Berlin, Germany)

'''updated headings''':
100 10 $a Black, Adam, $d 1974- $t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001 :$c Berlin, Germany)

==Authority Matching Overview==
While Authority Cleanup improves authority controlled headings using proprietary MARS 2.0 correcton tables, authority matching compares each authority controlled heading in your bibliographic records against authority record headings from any of a number of national and other authority files.

===National authority files===
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Abbrev.
! style="background:silver" | National Authority File
! style="background:silver" | Updates
! style="background:silver" | Size
|-
| ! align="center" | NAF || Library of Congress Names || ! align="center" | Weekly || ! align="center" | 12,042,590
|-
| ! align="center" | SAF || Library of Congress Subjects || ! align="center" | Weekly || ! align="center" | 466,121
|-
| ! align="center" | CHILD/CYAC || Library of Congress Children's and Young Adult Program || ! align="center" | Weekly || ! align="center" | 13,131
|-
| ! align="center" | LCGFT || Library of Congress Genre Form Terms || ! align="center" | Weekly || ! align="center" | 2,627
|-
| ! align="center" | LCMPT || Library of Congress Medium of Performance Terms || ! align="center" | TBD || ! align="center" | 876
|-
| ! align="center" | MESH || National Library of Medicine || ! align="center" | Annual || ! align="center" | 658,232
|-
| ! align="center" | NLC-N || Library Archives Canada Names || ! align="center" | Monthly || ! align="center" | 2,185,630
|-
| ! align="center" | NLC-S || Library Archives Canada Subjects || ! align="center" | Monthly || ! align="center" | 11,616
|-
| ! align="center" | AAT || Art & Architecture Thesaurus || ! align="center" | TBD || ! align="center" | 56,876
|-
| ! align="center" | RBMSCV || *Updated* Rare Books and Manuscripts Section Vocabularies || ! align="center" | TBD || ! align="center" | 1,401
|-
| ! align="center" | TGM || Thesaurus for Graphic Materials || ! align="center" | TBD|| ! align="center" | 8,590
|-
| ! align="center" | GSAFD || Guidelines on Subject Access to Individual Works of Fiction, Drama, etc || ! align="center" | Frozen || ! align="center" | 153
|-
| ! align="center" | FAST || Faceted Application of Subject Terminology || ! align="center" | Quarterly || ! align="center" | 1,855,837
|-
| ! align="center" | NASA || NASA Thesaurus || ! align="center" | TBD || ! align="center" | 18,336
|-
| ! align="center" | OLACVGGT || OLAC Video Game Genre Vocabulary || ! align="center" | Frozen || ! align="center" | 66
|-
| ! align="center" | EMBNE || National Library of Spain || ! align="center" | TBD|| ! align="center" | 4,512,763
|-
| ! align="center" | QLSP || Queens Library Spanish Language Subject Headings || ! align="center" | Frozen || ! align="center" | 11,745
|-
| ! align="center" | ERIC|| Education Resources Information Center (ERIC) Thesaurus || ! align="center" | TBD || ! align="center" | 4,552
|-
| ! align="center" | HOMOIT || Homosaurus || ! align="center" | Semi-annual || ! align="center" | 3,955
|-
| ! align="center" | ULAN || Union List of Artist Names || ! align="center" | TBD || ! align="center" | 402,765
|-
| ! align="center" | TGN || Thesaurus of Geographic Names || ! align="center" | TBD || ! align="center" | 2,991,045
|-
| ! align="center" | RVM || Répertoire de vedettes-matière || ! align="center" | Monthly || ! align="center" | 347,302
|}

<div style=clear:both></div>

NOTE: As of September 2018, the Canadiana Name Authorities product from Library and Archives Canada has been discontinued. Library and Archives Canada is joining NACO and authority records are expected to be distributed via LC. Subjects Authorities are still distributed via LAC.

NOTE: RBMSCV (formerly known as RBMS) was released early 2023; the vocabulary and authorities is fully live in the Backstage system.

NOTE: Vocabularies and counts updated 11/25/2025.

===Goals of authority matching===
Authority matching uses the headings in authority records to update or correct the bibliographic headings so they conform to current standards.

Authority matching is also the basis for providing full authority records for your local system. The goals of authority matching are to:
*Update '''invalid headings''' to '''valid forms''' based on cross-references found in authority records (convert to the established form of heading)
*Modify headings that have incorrect '''spacing''', '''punctuation''', '''indicators''', or '''subfield codes''' to the correct form based on matches found
*Update '''invalid higher levels''' of a heading to their '''valid forms''', based on cross-references found in authority records
*Distribute '''matched authority records''' to your institution
*Identify headings requiring '''more attention''' by your staff, through the use of MARS 2.0 reports

===Fields under authority control===
MARS 2.0 corrects and updates the full range of authority controlled headings. The following bibliographic headings / fields are included in MARS 2.0 authority control processing:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" | Name, Title, and Series Authority Controlled Headings
|-
|Personal Names||100, 700
|-
|Corporate Names||110, 710
|-
|Conference Names||111, 711
|-
|Uniform Titles||130, 240, 730
|-
|Uniform Titles in a $t||600, 610, 611, 700, 710, 711
|-
|Series||400, 410, 411, 440, 800, 810, 811, 830
|}
<div style=clear:both></div>

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" |Subject Authority Controlled Headings
|-
|Personal Names||600
|-
|Corporate Names||610
|-
|Conference Names||611
|-
|Uniform Titles||630
|-
|Topical||650
|-
|Geographic||651
|-
|Genre||655
|}
<div style=clear:both></div>

===Subfields disregarded===
A number of MARC subfields are disregarded during MARS 2.0 authority matching. In the following headings, the volume designations in fields 810 and 440 $v, the heading linkage information in field 130 $6, and the ISSN in field 440 $x, are all examples of subfield information which is not under authority control:


810 2 $a John Bartholomew and Son. $t Bartholomew world travel series ;$v 10.
130 0 $6 880-01 $a ”Hsuuan lai his kan” his lieh.
440 4 $a Romanica Gothoburgensia ;$v 12, 16 $x 0080-3863

===Subfields matched or ignored===
The table below shows the subfields that are included in the MARS 2.0 authority matching process:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | MARC Field !!style="background:silver" | Subfields Retained During Matching !! style="background:silver" | Subfields Ignored During Matching
|-
|100, 400, 700, 800 || a b c d f g h k l m n o p q r s t y z || e u v w x 2 3 4 5 6
|-
|110, 410, 710, 810 || a b c d f g h k l m n o p r s t y z || e u v w x 2 3 4 5 6
|-
|111, 411, 711, 811 || a b c d e f g h k l m n o p q r s t u y z || v w x 2 3 4 5 6
|-
|130, 830 || a d f g h k l m n o p r s t x y z || v w 2 3 5 6
|-
|730 || a d f g h k l m n o p r s t y z || v w x 2 3 5 6
|-
|440 || a n p || v w x 6
|-
|600 || a b c d f g h k l m n o p q r s t v x y z || e u w 2 3 4 5 6
|-
|610 || a b c d f g h k l m n o p r s t v x y z || e u w 2 3 4 5 6
|-
|611 || a b c d e f g h k l m n o p q r s t u v x y z || 2 3 4 5 6
|-
|630 || a d f g h k l m n o p r s t v x y z || w 2 3 5 6
|-
|650 || a b c d v x y z || e w 2 3 6
|-
|651 || a b v x y z || w 2 3 6
|-
|655 || a b c v x y z || e w 2 3 6
|}
<div style=clear:both></div>

===Normalization===
Headings from both your bibliographic records and the MARS 2.0 national authority files are normalized before they are compared for matching. MARS 2.0 uses the NACO normalization standard. During normalization:
*Alphabetic characters are converted to '''uppercase'''
*The '''first comma will be retained''' in $a for personal name headings
*All other punctuation is '''removed'''
*Certain '''diacritics''' and '''hyphens''' are left in for JACKPHY normalization
*All other diacritics are '''removed'''
*Special characters are replaced by an '''alphabetic equivalent'''
*Subfield codes are '''removed'''
*Subfield delimiters for '''all but first subfield''' will be left in

'''bib record heading''':
$a Architecture $z Brazil $x S'ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Notice the subfield codes and the diacritic in '''S'ao Paulo''' have been discarded when constructing the normalized form of the heading.

Because subfield codes are ignored during the authority matching process, invalid subfield codes do not affect the matching and may be corrected during the process.

For this example, the normalized form of the established heading '''1XX''' in the authority record is:

'''authority heading''':
$a Architecture $z Brazil $z S~ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Since the normalized forms of the bibliographic and authority headings are the same, the established form in the authority record replaces the form in the bibliographic record.

The bibliographic heading then contains the correct diacritic ~ instead of ' and the subfield code for '''S'ao Paulo''' has been corrected to '''$z'''.

== Topics ==
* [[Step 3.1|Step 3.1]] - Generic Name Headings
* [[Step 3.2|Step 3.2]] - Tag Flipping
* [[Step 3.3|Step 3.3]] - Partial Matches
* [[Step 3.4|Step 3.4]] - Split Headings
* [[Step 3.5|Step 3.5]] - Series Processing
* [[Step 3.6|Step 3.6]] - Subdivision Updates
* [[Step 3.7|Step 3.7]] - Childrens Matching
* [[Step 3.8|Step 3.8]] - MESH Matching
* [[Step 3.9|Step 3.9]] - Canadian Matching
* [[Step 3.10|Step 3.10]] - Local Bibliographic Subject Matching
* [[Step 3.11|Step 3.11]] - Genre Form Matching
* [[Step 3.12|Step 3.12]] - Subject Term Conversions
* [[Step 3.13|Step 3.13]] - Other Subject Vocabulary Matching
* [[Step 3.14|Step 3.14]] - Local Fields in Authority Records
* [[Step 3.15|Step 3.15]] - Local Authority Master
* [[Step 3.16|Step 3.16]] - JACKPHY Vernacular
* [[Step 3.17|Step 3.17]] - Pseudonyms
* [[Step 3.18|Step 3.18]] - Deblinding XRefs

The rest of the information contained in Step 3 details the matching options for your bibliographic and authority records. As with each step of this profile, these options are suggestions though each one can be customized according to your preference.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.0

2026-01-19T20:28:17Z

Casey: /* National authority files */

==Authority Cleanup Overview==
The first phase of MARS 2.0 Authority Control comprises a battery of routines that update and correct individual subfields and contiguous pairs of subfields, the purpose of which is to increase the likelihood of finding the appropriate authority match.

These corrections are based on a number of subfield update tables, maintained by MARS 2.0 authorities librarians.

MARS 2.0 subfield correction routines include:
* Updating obsolete forms of subdivisions to the current form
* Correcting common typographical errors
* Expanding abbreviations in subject subfields to their fuller form
* Converting common direct geographic subdivisions to their indirect form
* Deleting subject subdivisions which have been canceled or discontinued
* Correcting spacing, capitalization, and punctuation

===Update obsolete subdivisions===
MARS 2.0 uses a number of subfield correction tables to correct common errors in LC subfields


— Relations (General) with the United States

'''changes to''':
— Relations — United States

===Correct typographical errors===
MARS 2.0 also uses the subfield correction tables to correct common spelling errors in LC subdivisions:

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Histroy || History || LC 6XX $x
|-
| Untied States || United States || LC 650 $z and 651 $a
|}
<div style=clear:both></div>

===Expand abbreviations===
The subfield correction tables also support the expansion of outdated or invalid abbreviations in LC headings to the full form. Changes are made only when the outdated or invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Outdated / Invalid
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Hist. & crit. || History and criticism || LC 6XX $x
|-
| U.S. || United States || LC 651 $a, X10 $a, and 6XX $z
|-
| Econ. cond. || Economic conditions || LC 6XX $x
|}
<div style=clear:both></div>

===Direct-to-indirect geographic conversion===
MARS 2.0 uses a table to convert direct geographic subdivisions to the indirect form. Changes are made by the direct-to-indirect subfield conversion program only when the invalid form is the entire text of the $z '''and''' there is only one $z in the heading:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Direct Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $z Paris || $z France $z Paris || LC 6XX fields
|-
| $z Jefferson Co., Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|-
| $z Jefferson County, Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|}
<div style=clear:both></div>

===Chronological conversion===
MARS 2.0 uses a table to convert chronological headings '''$y''' to their correct form. Corrections are made to spelling and punctuation as well as to format:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $y Twentieth century || $y 20th century || LC 6XX fields
|-
| $z 20th century || $y 20th century || LC 6XX fields
|-
| $y 20th centry ||$y 20th century ||LC 6XX fields
|}
<div style=clear:both></div>

===Delete obsolete subdivisions===
MARS 2.0 uses a subfield deletion table to eliminate canceled subfields from LC bibliographic headings, deleting subfields only when the invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Deleted
! style="background:silver" | Field / Subfield
|-
| Addresses, essays, lectures || 6XX $x
|-
| Addresses, sermons, etc. || 6XX $x
|-
| Collected works || 6XX $x
|}
<div style=clear:both></div>

The subfield deletion table also includes common misspellings and typographical errors:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Field / Subfield
|-
| Adresses, essays, lectures || 6XX $x
|-
| Addressses, essays, lectures || 6XX $x
|-
| Collected work || 6XX $x
|}
<div style=clear:both></div>

===Retain selected subdivisions===
The subfield deletion table includes a section that prevents subfield conversions and deletions in headings meeting specific criteria.

— Yearbooks

'''changes to''':
— Periodicals
except when — Yearbooks ''is part of the subfield pair:''
— Students — Yearbooks

===Correct spacing, capitalization, and punctuation===
Most errors in spacing, capitalization and punctuation are corrected as an integral part of the authority cleanup and authority matching processes. Routines are also run to correct spacing and punctuation on the following fields:

1XX, 240, 243, 245, 260, 4XX, 6XX, 7XX, 8XX

These processes eliminate any excess spaces in each field, makes sure each field has the correct punctuation within and between each subfield, and makes sure each field has ending punctuation.


'''original headings''':
100 10 $a Black, Adam, $d 1974- .$t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001, $c Berlin, Germany)

'''updated headings''':
100 10 $a Black, Adam, $d 1974- $t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001 :$c Berlin, Germany)

==Authority Matching Overview==
While Authority Cleanup improves authority controlled headings using proprietary MARS 2.0 correcton tables, authority matching compares each authority controlled heading in your bibliographic records against authority record headings from any of a number of national and other authority files.

===National authority files===
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Abbrev.
! style="background:silver" | National Authority File
! style="background:silver" | Updates
! style="background:silver" | Size
|-
| ! align="center" | NAF || Library of Congress Names || ! align="center" | Weekly || ! align="center" | 12,042,590
|-
| ! align="center" | SAF || Library of Congress Subjects || ! align="center" | Weekly || ! align="center" | 466,121
|-
| ! align="center" | CHILD/CYAC || Library of Congress Children's and Young Adult Program || ! align="center" | Weekly || ! align="center" | 13,131
|-
| ! align="center" | LCGFT || Library of Congress Genre Form Terms || ! align="center" | Weekly || ! align="center" | 2,627
|-
| ! align="center" | LCMPT || Library of Congress Medium of Performance Terms || ! align="center" | TBD || ! align="center" | 876
|-
| ! align="center" | MESH || National Library of Medicine || ! align="center" | Annual || ! align="center" | 658,232
|-
| ! align="center" | NLC-N || Library Archives Canada Names || ! align="center" | Monthly || ! align="center" | 2,368,795
|-
| ! align="center" | NLC-S || Library Archives Canada Subjects || ! align="center" | Monthly || ! align="center" | 42,013
|-
| ! align="center" | AAT || Art & Architecture Thesaurus || ! align="center" | TBD || ! align="center" | 56,876
|-
| ! align="center" | RBMSCV || *Updated* Rare Books and Manuscripts Section Vocabularies || ! align="center" | TBD || ! align="center" | 1,401
|-
| ! align="center" | TGM || Thesaurus for Graphic Materials || ! align="center" | TBD|| ! align="center" | 8,590
|-
| ! align="center" | GSAFD || Guidelines on Subject Access to Individual Works of Fiction, Drama, etc || ! align="center" | Frozen || ! align="center" | 153
|-
| ! align="center" | FAST || Faceted Application of Subject Terminology || ! align="center" | Quarterly || ! align="center" | 1,855,837
|-
| ! align="center" | NASA || NASA Thesaurus || ! align="center" | TBD || ! align="center" | 18,336
|-
| ! align="center" | OLACVGGT || OLAC Video Game Genre Vocabulary || ! align="center" | Frozen || ! align="center" | 66
|-
| ! align="center" | EMBNE || National Library of Spain || ! align="center" | TBD|| ! align="center" | 4,512,763
|-
| ! align="center" | QLSP || Queens Library Spanish Language Subject Headings || ! align="center" | Frozen || ! align="center" | 11,745
|-
| ! align="center" | ERIC|| Education Resources Information Center (ERIC) Thesaurus || ! align="center" | TBD || ! align="center" | 4,552
|-
| ! align="center" | HOMOIT || Homosaurus || ! align="center" | Semi-annual || ! align="center" | 3,955
|-
| ! align="center" | ULAN || Union List of Artist Names || ! align="center" | TBD || ! align="center" | 402,765
|-
| ! align="center" | TGN || Thesaurus of Geographic Names || ! align="center" | TBD || ! align="center" | 2,991,045
|-
| ! align="center" | RVM || Répertoire de vedettes-matière || ! align="center" | Monthly || ! align="center" | 347,302
|}

<div style=clear:both></div>

NOTE: As of September 2018, the Canadiana Name Authorities product from Library and Archives Canada has been discontinued. Library and Archives Canada is joining NACO and authority records are expected to be distributed via LC. Subjects Authorities are still distributed via LAC.

NOTE: RBMSCV (formerly known as RBMS) was released early 2023; the vocabulary and authorities is fully live in the Backstage system.

NOTE: Vocabularies and counts updated 11/25/2025.

===Goals of authority matching===
Authority matching uses the headings in authority records to update or correct the bibliographic headings so they conform to current standards.

Authority matching is also the basis for providing full authority records for your local system. The goals of authority matching are to:
*Update '''invalid headings''' to '''valid forms''' based on cross-references found in authority records (convert to the established form of heading)
*Modify headings that have incorrect '''spacing''', '''punctuation''', '''indicators''', or '''subfield codes''' to the correct form based on matches found
*Update '''invalid higher levels''' of a heading to their '''valid forms''', based on cross-references found in authority records
*Distribute '''matched authority records''' to your institution
*Identify headings requiring '''more attention''' by your staff, through the use of MARS 2.0 reports

===Fields under authority control===
MARS 2.0 corrects and updates the full range of authority controlled headings. The following bibliographic headings / fields are included in MARS 2.0 authority control processing:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" | Name, Title, and Series Authority Controlled Headings
|-
|Personal Names||100, 700
|-
|Corporate Names||110, 710
|-
|Conference Names||111, 711
|-
|Uniform Titles||130, 240, 730
|-
|Uniform Titles in a $t||600, 610, 611, 700, 710, 711
|-
|Series||400, 410, 411, 440, 800, 810, 811, 830
|}
<div style=clear:both></div>

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" |Subject Authority Controlled Headings
|-
|Personal Names||600
|-
|Corporate Names||610
|-
|Conference Names||611
|-
|Uniform Titles||630
|-
|Topical||650
|-
|Geographic||651
|-
|Genre||655
|}
<div style=clear:both></div>

===Subfields disregarded===
A number of MARC subfields are disregarded during MARS 2.0 authority matching. In the following headings, the volume designations in fields 810 and 440 $v, the heading linkage information in field 130 $6, and the ISSN in field 440 $x, are all examples of subfield information which is not under authority control:


810 2 $a John Bartholomew and Son. $t Bartholomew world travel series ;$v 10.
130 0 $6 880-01 $a ”Hsuuan lai his kan” his lieh.
440 4 $a Romanica Gothoburgensia ;$v 12, 16 $x 0080-3863

===Subfields matched or ignored===
The table below shows the subfields that are included in the MARS 2.0 authority matching process:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | MARC Field !!style="background:silver" | Subfields Retained During Matching !! style="background:silver" | Subfields Ignored During Matching
|-
|100, 400, 700, 800 || a b c d f g h k l m n o p q r s t y z || e u v w x 2 3 4 5 6
|-
|110, 410, 710, 810 || a b c d f g h k l m n o p r s t y z || e u v w x 2 3 4 5 6
|-
|111, 411, 711, 811 || a b c d e f g h k l m n o p q r s t u y z || v w x 2 3 4 5 6
|-
|130, 830 || a d f g h k l m n o p r s t x y z || v w 2 3 5 6
|-
|730 || a d f g h k l m n o p r s t y z || v w x 2 3 5 6
|-
|440 || a n p || v w x 6
|-
|600 || a b c d f g h k l m n o p q r s t v x y z || e u w 2 3 4 5 6
|-
|610 || a b c d f g h k l m n o p r s t v x y z || e u w 2 3 4 5 6
|-
|611 || a b c d e f g h k l m n o p q r s t u v x y z || 2 3 4 5 6
|-
|630 || a d f g h k l m n o p r s t v x y z || w 2 3 5 6
|-
|650 || a b c d v x y z || e w 2 3 6
|-
|651 || a b v x y z || w 2 3 6
|-
|655 || a b c v x y z || e w 2 3 6
|}
<div style=clear:both></div>

===Normalization===
Headings from both your bibliographic records and the MARS 2.0 national authority files are normalized before they are compared for matching. MARS 2.0 uses the NACO normalization standard. During normalization:
*Alphabetic characters are converted to '''uppercase'''
*The '''first comma will be retained''' in $a for personal name headings
*All other punctuation is '''removed'''
*Certain '''diacritics''' and '''hyphens''' are left in for JACKPHY normalization
*All other diacritics are '''removed'''
*Special characters are replaced by an '''alphabetic equivalent'''
*Subfield codes are '''removed'''
*Subfield delimiters for '''all but first subfield''' will be left in

'''bib record heading''':
$a Architecture $z Brazil $x S'ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Notice the subfield codes and the diacritic in '''S'ao Paulo''' have been discarded when constructing the normalized form of the heading.

Because subfield codes are ignored during the authority matching process, invalid subfield codes do not affect the matching and may be corrected during the process.

For this example, the normalized form of the established heading '''1XX''' in the authority record is:

'''authority heading''':
$a Architecture $z Brazil $z S~ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Since the normalized forms of the bibliographic and authority headings are the same, the established form in the authority record replaces the form in the bibliographic record.

The bibliographic heading then contains the correct diacritic ~ instead of ' and the subfield code for '''S'ao Paulo''' has been corrected to '''$z'''.

== Topics ==
* [[Step 3.1|Step 3.1]] - Generic Name Headings
* [[Step 3.2|Step 3.2]] - Tag Flipping
* [[Step 3.3|Step 3.3]] - Partial Matches
* [[Step 3.4|Step 3.4]] - Split Headings
* [[Step 3.5|Step 3.5]] - Series Processing
* [[Step 3.6|Step 3.6]] - Subdivision Updates
* [[Step 3.7|Step 3.7]] - Childrens Matching
* [[Step 3.8|Step 3.8]] - MESH Matching
* [[Step 3.9|Step 3.9]] - Canadian Matching
* [[Step 3.10|Step 3.10]] - Local Bibliographic Subject Matching
* [[Step 3.11|Step 3.11]] - Genre Form Matching
* [[Step 3.12|Step 3.12]] - Subject Term Conversions
* [[Step 3.13|Step 3.13]] - Other Subject Vocabulary Matching
* [[Step 3.14|Step 3.14]] - Local Fields in Authority Records
* [[Step 3.15|Step 3.15]] - Local Authority Master
* [[Step 3.16|Step 3.16]] - JACKPHY Vernacular
* [[Step 3.17|Step 3.17]] - Pseudonyms
* [[Step 3.18|Step 3.18]] - Deblinding XRefs

The rest of the information contained in Step 3 details the matching options for your bibliographic and authority records. As with each step of this profile, these options are suggestions though each one can be customized according to your preference.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.0

2025-11-25T15:02:05Z

Casey: /* National authority files */ Updated DBs and counts

==Authority Cleanup Overview==
The first phase of MARS 2.0 Authority Control comprises a battery of routines that update and correct individual subfields and contiguous pairs of subfields, the purpose of which is to increase the likelihood of finding the appropriate authority match.

These corrections are based on a number of subfield update tables, maintained by MARS 2.0 authorities librarians.

MARS 2.0 subfield correction routines include:
* Updating obsolete forms of subdivisions to the current form
* Correcting common typographical errors
* Expanding abbreviations in subject subfields to their fuller form
* Converting common direct geographic subdivisions to their indirect form
* Deleting subject subdivisions which have been canceled or discontinued
* Correcting spacing, capitalization, and punctuation

===Update obsolete subdivisions===
MARS 2.0 uses a number of subfield correction tables to correct common errors in LC subfields


— Relations (General) with the United States

'''changes to''':
— Relations — United States

===Correct typographical errors===
MARS 2.0 also uses the subfield correction tables to correct common spelling errors in LC subdivisions:

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Histroy || History || LC 6XX $x
|-
| Untied States || United States || LC 650 $z and 651 $a
|}
<div style=clear:both></div>

===Expand abbreviations===
The subfield correction tables also support the expansion of outdated or invalid abbreviations in LC headings to the full form. Changes are made only when the outdated or invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Outdated / Invalid
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Hist. & crit. || History and criticism || LC 6XX $x
|-
| U.S. || United States || LC 651 $a, X10 $a, and 6XX $z
|-
| Econ. cond. || Economic conditions || LC 6XX $x
|}
<div style=clear:both></div>

===Direct-to-indirect geographic conversion===
MARS 2.0 uses a table to convert direct geographic subdivisions to the indirect form. Changes are made by the direct-to-indirect subfield conversion program only when the invalid form is the entire text of the $z '''and''' there is only one $z in the heading:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Direct Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $z Paris || $z France $z Paris || LC 6XX fields
|-
| $z Jefferson Co., Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|-
| $z Jefferson County, Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|}
<div style=clear:both></div>

===Chronological conversion===
MARS 2.0 uses a table to convert chronological headings '''$y''' to their correct form. Corrections are made to spelling and punctuation as well as to format:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $y Twentieth century || $y 20th century || LC 6XX fields
|-
| $z 20th century || $y 20th century || LC 6XX fields
|-
| $y 20th centry ||$y 20th century ||LC 6XX fields
|}
<div style=clear:both></div>

===Delete obsolete subdivisions===
MARS 2.0 uses a subfield deletion table to eliminate canceled subfields from LC bibliographic headings, deleting subfields only when the invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Deleted
! style="background:silver" | Field / Subfield
|-
| Addresses, essays, lectures || 6XX $x
|-
| Addresses, sermons, etc. || 6XX $x
|-
| Collected works || 6XX $x
|}
<div style=clear:both></div>

The subfield deletion table also includes common misspellings and typographical errors:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Field / Subfield
|-
| Adresses, essays, lectures || 6XX $x
|-
| Addressses, essays, lectures || 6XX $x
|-
| Collected work || 6XX $x
|}
<div style=clear:both></div>

===Retain selected subdivisions===
The subfield deletion table includes a section that prevents subfield conversions and deletions in headings meeting specific criteria.

— Yearbooks

'''changes to''':
— Periodicals
except when — Yearbooks ''is part of the subfield pair:''
— Students — Yearbooks

===Correct spacing, capitalization, and punctuation===
Most errors in spacing, capitalization and punctuation are corrected as an integral part of the authority cleanup and authority matching processes. Routines are also run to correct spacing and punctuation on the following fields:

1XX, 240, 243, 245, 260, 4XX, 6XX, 7XX, 8XX

These processes eliminate any excess spaces in each field, makes sure each field has the correct punctuation within and between each subfield, and makes sure each field has ending punctuation.


'''original headings''':
100 10 $a Black, Adam, $d 1974- .$t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001, $c Berlin, Germany)

'''updated headings''':
100 10 $a Black, Adam, $d 1974- $t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001 :$c Berlin, Germany)

==Authority Matching Overview==
While Authority Cleanup improves authority controlled headings using proprietary MARS 2.0 correcton tables, authority matching compares each authority controlled heading in your bibliographic records against authority record headings from any of a number of national and other authority files.

===National authority files===
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Abbrev.
! style="background:silver" | National Authority File
! style="background:silver" | Updates
! style="background:silver" | Size
|-
| ! align="center" | NAF || Library of Congress Names || ! align="center" | Weekly || ! align="center" | 12,042,590
|-
| ! align="center" | SAF || Library of Congress Subjects || ! align="center" | Weekly || ! align="center" | 466,121
|-
| ! align="center" | CHILD/CYAC || Library of Congress Children's and Young Adult Program || ! align="center" | Weekly || ! align="center" | 13,131
|-
| ! align="center" | LCGFT || Library of Congress Genre Form Terms || ! align="center" | Weekly || ! align="center" | 2,627
|-
| ! align="center" | LCMPT || Library of Congress Medium of Performance Terms || ! align="center" | TBD || ! align="center" | 876
|-
| ! align="center" | MESH || National Library of Medicine || ! align="center" | Annual || ! align="center" | 658,232
|-
| ! align="center" | NLC-N || Library Archives Canada Names || ! align="center" | Monthly || ! align="center" | 2,368,795
|-
| ! align="center" | NLC-S || Library Archives Canada Subjects || ! align="center" | Monthly || ! align="center" | 42,013
|-
| ! align="center" | AAT || Art & Architecture Thesaurus || ! align="center" | TBD || ! align="center" | 56,876
|-
| ! align="center" | RBMSCV || *Updated* Rare Books and Manuscripts Section Vocabularies || ! align="center" | TBD || ! align="center" | 1,401
|-
| ! align="center" | TGM || Thesaurus for Graphic Materials || ! align="center" | TBD|| ! align="center" | 8,590
|-
| ! align="center" | GSAFD || Guidelines on Subject Access to Individual Works of Fiction, Drama, etc || ! align="center" | Frozen || ! align="center" | 153
|-
| ! align="center" | FAST || Faceted Application of Subject Terminology || ! align="center" | Quarterly || ! align="center" | 1,855,837
|-
| ! align="center" | NASA || NASA Thesaurus || ! align="center" | TBD || ! align="center" | 18,336
|-
| ! align="center" | OLACVGGT || OLAC Video Game Genre Vocabulary || ! align="center" | Frozen || ! align="center" | 66
|-
| ! align="center" | EMBNE || National Library of Spain || ! align="center" | TBD|| ! align="center" | 4,512,763
|-
| ! align="center" | QLSP || Queens Library Spanish Language Subject Headings || ! align="center" | Frozen || ! align="center" | 11,745
|-
| ! align="center" | ERIC|| Education Resources Information Center (ERIC) Thesaurus || ! align="center" | TBD || ! align="center" | 4,552
|-
| ! align="center" | HOMOIT || Homosaurus || ! align="center" | Semi-annual || ! align="center" | 3,955
|-
| ! align="center" | ULAN || Union List of Artist Names || ! align="center" | TBD || ! align="center" | 402,765
|-
| ! align="center" | TGN || Thesaurus of Geographic Names || ! align="center" | TBD || ! align="center" | 2,991,045
|-
| ! align="center" | RVM || Répertoire de vedettes-matière || ! align="center" | TBD || ! align="center" | COMING SOON
|}

<div style=clear:both></div>

NOTE: As of September 2018, the Canadiana Authorities product from Library and Archives Canada has been discontinued. Library and Archives Canada is joining NACO and authority records are expected to be distributed via LC.

NOTE: RBMSCV (formerly known as RBMS) was released early 2023; the vocabulary and authorities is fully live in the Backstage system.

NOTE: Vocabularies and counts updated 11/25/2025.

===Goals of authority matching===
Authority matching uses the headings in authority records to update or correct the bibliographic headings so they conform to current standards.

Authority matching is also the basis for providing full authority records for your local system. The goals of authority matching are to:
*Update '''invalid headings''' to '''valid forms''' based on cross-references found in authority records (convert to the established form of heading)
*Modify headings that have incorrect '''spacing''', '''punctuation''', '''indicators''', or '''subfield codes''' to the correct form based on matches found
*Update '''invalid higher levels''' of a heading to their '''valid forms''', based on cross-references found in authority records
*Distribute '''matched authority records''' to your institution
*Identify headings requiring '''more attention''' by your staff, through the use of MARS 2.0 reports

===Fields under authority control===
MARS 2.0 corrects and updates the full range of authority controlled headings. The following bibliographic headings / fields are included in MARS 2.0 authority control processing:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" | Name, Title, and Series Authority Controlled Headings
|-
|Personal Names||100, 700
|-
|Corporate Names||110, 710
|-
|Conference Names||111, 711
|-
|Uniform Titles||130, 240, 730
|-
|Uniform Titles in a $t||600, 610, 611, 700, 710, 711
|-
|Series||400, 410, 411, 440, 800, 810, 811, 830
|}
<div style=clear:both></div>

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" |Subject Authority Controlled Headings
|-
|Personal Names||600
|-
|Corporate Names||610
|-
|Conference Names||611
|-
|Uniform Titles||630
|-
|Topical||650
|-
|Geographic||651
|-
|Genre||655
|}
<div style=clear:both></div>

===Subfields disregarded===
A number of MARC subfields are disregarded during MARS 2.0 authority matching. In the following headings, the volume designations in fields 810 and 440 $v, the heading linkage information in field 130 $6, and the ISSN in field 440 $x, are all examples of subfield information which is not under authority control:


810 2 $a John Bartholomew and Son. $t Bartholomew world travel series ;$v 10.
130 0 $6 880-01 $a ”Hsuuan lai his kan” his lieh.
440 4 $a Romanica Gothoburgensia ;$v 12, 16 $x 0080-3863

===Subfields matched or ignored===
The table below shows the subfields that are included in the MARS 2.0 authority matching process:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | MARC Field !!style="background:silver" | Subfields Retained During Matching !! style="background:silver" | Subfields Ignored During Matching
|-
|100, 400, 700, 800 || a b c d f g h k l m n o p q r s t y z || e u v w x 2 3 4 5 6
|-
|110, 410, 710, 810 || a b c d f g h k l m n o p r s t y z || e u v w x 2 3 4 5 6
|-
|111, 411, 711, 811 || a b c d e f g h k l m n o p q r s t u y z || v w x 2 3 4 5 6
|-
|130, 830 || a d f g h k l m n o p r s t x y z || v w 2 3 5 6
|-
|730 || a d f g h k l m n o p r s t y z || v w x 2 3 5 6
|-
|440 || a n p || v w x 6
|-
|600 || a b c d f g h k l m n o p q r s t v x y z || e u w 2 3 4 5 6
|-
|610 || a b c d f g h k l m n o p r s t v x y z || e u w 2 3 4 5 6
|-
|611 || a b c d e f g h k l m n o p q r s t u v x y z || 2 3 4 5 6
|-
|630 || a d f g h k l m n o p r s t v x y z || w 2 3 5 6
|-
|650 || a b c d v x y z || e w 2 3 6
|-
|651 || a b v x y z || w 2 3 6
|-
|655 || a b c v x y z || e w 2 3 6
|}
<div style=clear:both></div>

===Normalization===
Headings from both your bibliographic records and the MARS 2.0 national authority files are normalized before they are compared for matching. MARS 2.0 uses the NACO normalization standard. During normalization:
*Alphabetic characters are converted to '''uppercase'''
*The '''first comma will be retained''' in $a for personal name headings
*All other punctuation is '''removed'''
*Certain '''diacritics''' and '''hyphens''' are left in for JACKPHY normalization
*All other diacritics are '''removed'''
*Special characters are replaced by an '''alphabetic equivalent'''
*Subfield codes are '''removed'''
*Subfield delimiters for '''all but first subfield''' will be left in

'''bib record heading''':
$a Architecture $z Brazil $x S'ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Notice the subfield codes and the diacritic in '''S'ao Paulo''' have been discarded when constructing the normalized form of the heading.

Because subfield codes are ignored during the authority matching process, invalid subfield codes do not affect the matching and may be corrected during the process.

For this example, the normalized form of the established heading '''1XX''' in the authority record is:

'''authority heading''':
$a Architecture $z Brazil $z S~ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Since the normalized forms of the bibliographic and authority headings are the same, the established form in the authority record replaces the form in the bibliographic record.

The bibliographic heading then contains the correct diacritic ~ instead of ' and the subfield code for '''S'ao Paulo''' has been corrected to '''$z'''.

== Topics ==
* [[Step 3.1|Step 3.1]] - Generic Name Headings
* [[Step 3.2|Step 3.2]] - Tag Flipping
* [[Step 3.3|Step 3.3]] - Partial Matches
* [[Step 3.4|Step 3.4]] - Split Headings
* [[Step 3.5|Step 3.5]] - Series Processing
* [[Step 3.6|Step 3.6]] - Subdivision Updates
* [[Step 3.7|Step 3.7]] - Childrens Matching
* [[Step 3.8|Step 3.8]] - MESH Matching
* [[Step 3.9|Step 3.9]] - Canadian Matching
* [[Step 3.10|Step 3.10]] - Local Bibliographic Subject Matching
* [[Step 3.11|Step 3.11]] - Genre Form Matching
* [[Step 3.12|Step 3.12]] - Subject Term Conversions
* [[Step 3.13|Step 3.13]] - Other Subject Vocabulary Matching
* [[Step 3.14|Step 3.14]] - Local Fields in Authority Records
* [[Step 3.15|Step 3.15]] - Local Authority Master
* [[Step 3.16|Step 3.16]] - JACKPHY Vernacular
* [[Step 3.17|Step 3.17]] - Pseudonyms
* [[Step 3.18|Step 3.18]] - Deblinding XRefs

The rest of the information contained in Step 3 details the matching options for your bibliographic and authority records. As with each step of this profile, these options are suggestions though each one can be customized according to your preference.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.0

2025-03-26T15:54:31Z

Casey: /* National authority files */

==Authority Cleanup Overview==
The first phase of MARS 2.0 Authority Control comprises a battery of routines that update and correct individual subfields and contiguous pairs of subfields, the purpose of which is to increase the likelihood of finding the appropriate authority match.

These corrections are based on a number of subfield update tables, maintained by MARS 2.0 authorities librarians.

MARS 2.0 subfield correction routines include:
* Updating obsolete forms of subdivisions to the current form
* Correcting common typographical errors
* Expanding abbreviations in subject subfields to their fuller form
* Converting common direct geographic subdivisions to their indirect form
* Deleting subject subdivisions which have been canceled or discontinued
* Correcting spacing, capitalization, and punctuation

===Update obsolete subdivisions===
MARS 2.0 uses a number of subfield correction tables to correct common errors in LC subfields


— Relations (General) with the United States

'''changes to''':
— Relations — United States

===Correct typographical errors===
MARS 2.0 also uses the subfield correction tables to correct common spelling errors in LC subdivisions:

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Histroy || History || LC 6XX $x
|-
| Untied States || United States || LC 650 $z and 651 $a
|}
<div style=clear:both></div>

===Expand abbreviations===
The subfield correction tables also support the expansion of outdated or invalid abbreviations in LC headings to the full form. Changes are made only when the outdated or invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Outdated / Invalid
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Hist. & crit. || History and criticism || LC 6XX $x
|-
| U.S. || United States || LC 651 $a, X10 $a, and 6XX $z
|-
| Econ. cond. || Economic conditions || LC 6XX $x
|}
<div style=clear:both></div>

===Direct-to-indirect geographic conversion===
MARS 2.0 uses a table to convert direct geographic subdivisions to the indirect form. Changes are made by the direct-to-indirect subfield conversion program only when the invalid form is the entire text of the $z '''and''' there is only one $z in the heading:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Direct Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $z Paris || $z France $z Paris || LC 6XX fields
|-
| $z Jefferson Co., Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|-
| $z Jefferson County, Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|}
<div style=clear:both></div>

===Chronological conversion===
MARS 2.0 uses a table to convert chronological headings '''$y''' to their correct form. Corrections are made to spelling and punctuation as well as to format:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $y Twentieth century || $y 20th century || LC 6XX fields
|-
| $z 20th century || $y 20th century || LC 6XX fields
|-
| $y 20th centry ||$y 20th century ||LC 6XX fields
|}
<div style=clear:both></div>

===Delete obsolete subdivisions===
MARS 2.0 uses a subfield deletion table to eliminate canceled subfields from LC bibliographic headings, deleting subfields only when the invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Deleted
! style="background:silver" | Field / Subfield
|-
| Addresses, essays, lectures || 6XX $x
|-
| Addresses, sermons, etc. || 6XX $x
|-
| Collected works || 6XX $x
|}
<div style=clear:both></div>

The subfield deletion table also includes common misspellings and typographical errors:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Field / Subfield
|-
| Adresses, essays, lectures || 6XX $x
|-
| Addressses, essays, lectures || 6XX $x
|-
| Collected work || 6XX $x
|}
<div style=clear:both></div>

===Retain selected subdivisions===
The subfield deletion table includes a section that prevents subfield conversions and deletions in headings meeting specific criteria.

— Yearbooks

'''changes to''':
— Periodicals
except when — Yearbooks ''is part of the subfield pair:''
— Students — Yearbooks

===Correct spacing, capitalization, and punctuation===
Most errors in spacing, capitalization and punctuation are corrected as an integral part of the authority cleanup and authority matching processes. Routines are also run to correct spacing and punctuation on the following fields:

1XX, 240, 243, 245, 260, 4XX, 6XX, 7XX, 8XX

These processes eliminate any excess spaces in each field, makes sure each field has the correct punctuation within and between each subfield, and makes sure each field has ending punctuation.


'''original headings''':
100 10 $a Black, Adam, $d 1974- .$t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001, $c Berlin, Germany)

'''updated headings''':
100 10 $a Black, Adam, $d 1974- $t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001 :$c Berlin, Germany)

==Authority Matching Overview==
While Authority Cleanup improves authority controlled headings using proprietary MARS 2.0 correcton tables, authority matching compares each authority controlled heading in your bibliographic records against authority record headings from any of a number of national and other authority files.

===National authority files===
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Abbrev.
! style="background:silver" | National Authority File
! style="background:silver" | Updates
! style="background:silver" | Size
|-
| ! align="center" | NAF || Library of Congress Names || ! align="center" | Weekly || ! align="center" | 8,212,000
|-
| ! align="center" | SAF || Library of Congress Subjects || ! align="center" | Weekly || ! align="center" | 8,611,000
|-
| ! align="center" | CHILD/CYAC || Library of Congress Children's and Young Adult Program || ! align="center" | Weekly || ! align="center" | 12,633
|-
| ! align="center" | LCGFT || Library of Congress Genre Form Terms || ! align="center" | Weekly || ! align="center" | 2,000
|-
| ! align="center" | LCMPT || Library of Congress Medium of Performance Terms || ! align="center" | TBD || ! align="center" | 876
|-
| ! align="center" | MESH || National Library of Medicine || ! align="center" | Annual || ! align="center" | 616,000
|-
| ! align="center" | NLC-N || Library Archives Canada Names || ! align="center" | Frozen || ! align="center" | 653,000
|-
| ! align="center" | NLC-S || Library Archives Canada Subjects || ! align="center" | Frozen || ! align="center" | 659,000
|-
| ! align="center" | AAT || Art & Architecture Thesaurus || ! align="center" | TBD || ! align="center" | 56,876
|-
| ! align="center" | RBMSCV || *Updated* Rare Books and Manuscripts Section Vocabularies || ! align="center" | TBD || ! align="center" | 1,479
|-
| ! align="center" | TGM || Thesaurus for Graphic Materials || ! align="center" | TBD|| ! align="center" | 8,608
|-
| ! align="center" | GSAFD || Guidelines on Subject Access to Individual Works of Fiction, Drama, etc || ! align="center" | Frozen || ! align="center" | 153
|-
| ! align="center" | FAST || Faceted Application of Subject Terminology || ! align="center" | Quarterly || ! align="center" | 1,821,179
|-
| ! align="center" | NASA || NASA Thesaurus || ! align="center" | TBD || ! align="center" | 18,336
|-
| ! align="center" | OLACVGGT || OLAC Video Game Genre Vocabulary || ! align="center" | Frozen || ! align="center" | 66
|-
| ! align="center" | EMBNE || National Library of Spain || ! align="center" | TBD|| ! align="center" | 4,085,978
|-
| ! align="center" | QLSP || Queens Library Spanish Language Subject Headings || ! align="center" | Frozen || ! align="center" | 11,745
|-
| ! align="center" | ERIC|| Education Resources Information Center (ERIC) Thesaurus || ! align="center" | TBD || ! align="center" | 4,552
|-
| ! align="center" | HOMOIT || Homosaurus || ! align="center" | Semi-annual || ! align="center" | 3,734
|}

<div style=clear:both></div>

NOTE: As of September 2018, the Canadiana Authorities product from Library and Archives Canada has been discontinued. Library and Archives Canada is joining NACO and authority records are expected to be distributed via LC.

NOTE: RBMSCV (formerly known as RBMS) was released early 2023; the vocabulary and authorities is fully live in the Backstage system.

===Goals of authority matching===
Authority matching uses the headings in authority records to update or correct the bibliographic headings so they conform to current standards.

Authority matching is also the basis for providing full authority records for your local system. The goals of authority matching are to:
*Update '''invalid headings''' to '''valid forms''' based on cross-references found in authority records (convert to the established form of heading)
*Modify headings that have incorrect '''spacing''', '''punctuation''', '''indicators''', or '''subfield codes''' to the correct form based on matches found
*Update '''invalid higher levels''' of a heading to their '''valid forms''', based on cross-references found in authority records
*Distribute '''matched authority records''' to your institution
*Identify headings requiring '''more attention''' by your staff, through the use of MARS 2.0 reports

===Fields under authority control===
MARS 2.0 corrects and updates the full range of authority controlled headings. The following bibliographic headings / fields are included in MARS 2.0 authority control processing:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" | Name, Title, and Series Authority Controlled Headings
|-
|Personal Names||100, 700
|-
|Corporate Names||110, 710
|-
|Conference Names||111, 711
|-
|Uniform Titles||130, 240, 730
|-
|Uniform Titles in a $t||600, 610, 611, 700, 710, 711
|-
|Series||400, 410, 411, 440, 800, 810, 811, 830
|}
<div style=clear:both></div>

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" |Subject Authority Controlled Headings
|-
|Personal Names||600
|-
|Corporate Names||610
|-
|Conference Names||611
|-
|Uniform Titles||630
|-
|Topical||650
|-
|Geographic||651
|-
|Genre||655
|}
<div style=clear:both></div>

===Subfields disregarded===
A number of MARC subfields are disregarded during MARS 2.0 authority matching. In the following headings, the volume designations in fields 810 and 440 $v, the heading linkage information in field 130 $6, and the ISSN in field 440 $x, are all examples of subfield information which is not under authority control:


810 2 $a John Bartholomew and Son. $t Bartholomew world travel series ;$v 10.
130 0 $6 880-01 $a ”Hsuuan lai his kan” his lieh.
440 4 $a Romanica Gothoburgensia ;$v 12, 16 $x 0080-3863

===Subfields matched or ignored===
The table below shows the subfields that are included in the MARS 2.0 authority matching process:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | MARC Field !!style="background:silver" | Subfields Retained During Matching !! style="background:silver" | Subfields Ignored During Matching
|-
|100, 400, 700, 800 || a b c d f g h k l m n o p q r s t y z || e u v w x 2 3 4 5 6
|-
|110, 410, 710, 810 || a b c d f g h k l m n o p r s t y z || e u v w x 2 3 4 5 6
|-
|111, 411, 711, 811 || a b c d e f g h k l m n o p q r s t u y z || v w x 2 3 4 5 6
|-
|130, 830 || a d f g h k l m n o p r s t x y z || v w 2 3 5 6
|-
|730 || a d f g h k l m n o p r s t y z || v w x 2 3 5 6
|-
|440 || a n p || v w x 6
|-
|600 || a b c d f g h k l m n o p q r s t v x y z || e u w 2 3 4 5 6
|-
|610 || a b c d f g h k l m n o p r s t v x y z || e u w 2 3 4 5 6
|-
|611 || a b c d e f g h k l m n o p q r s t u v x y z || 2 3 4 5 6
|-
|630 || a d f g h k l m n o p r s t v x y z || w 2 3 5 6
|-
|650 || a b c d v x y z || e w 2 3 6
|-
|651 || a b v x y z || w 2 3 6
|-
|655 || a b c v x y z || e w 2 3 6
|}
<div style=clear:both></div>

===Normalization===
Headings from both your bibliographic records and the MARS 2.0 national authority files are normalized before they are compared for matching. MARS 2.0 uses the NACO normalization standard. During normalization:
*Alphabetic characters are converted to '''uppercase'''
*The '''first comma will be retained''' in $a for personal name headings
*All other punctuation is '''removed'''
*Certain '''diacritics''' and '''hyphens''' are left in for JACKPHY normalization
*All other diacritics are '''removed'''
*Special characters are replaced by an '''alphabetic equivalent'''
*Subfield codes are '''removed'''
*Subfield delimiters for '''all but first subfield''' will be left in

'''bib record heading''':
$a Architecture $z Brazil $x S'ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Notice the subfield codes and the diacritic in '''S'ao Paulo''' have been discarded when constructing the normalized form of the heading.

Because subfield codes are ignored during the authority matching process, invalid subfield codes do not affect the matching and may be corrected during the process.

For this example, the normalized form of the established heading '''1XX''' in the authority record is:

'''authority heading''':
$a Architecture $z Brazil $z S~ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Since the normalized forms of the bibliographic and authority headings are the same, the established form in the authority record replaces the form in the bibliographic record.

The bibliographic heading then contains the correct diacritic ~ instead of ' and the subfield code for '''S'ao Paulo''' has been corrected to '''$z'''.

== Topics ==
* [[Step 3.1|Step 3.1]] - Generic Name Headings
* [[Step 3.2|Step 3.2]] - Tag Flipping
* [[Step 3.3|Step 3.3]] - Partial Matches
* [[Step 3.4|Step 3.4]] - Split Headings
* [[Step 3.5|Step 3.5]] - Series Processing
* [[Step 3.6|Step 3.6]] - Subdivision Updates
* [[Step 3.7|Step 3.7]] - Childrens Matching
* [[Step 3.8|Step 3.8]] - MESH Matching
* [[Step 3.9|Step 3.9]] - Canadian Matching
* [[Step 3.10|Step 3.10]] - Local Bibliographic Subject Matching
* [[Step 3.11|Step 3.11]] - Genre Form Matching
* [[Step 3.12|Step 3.12]] - Subject Term Conversions
* [[Step 3.13|Step 3.13]] - Other Subject Vocabulary Matching
* [[Step 3.14|Step 3.14]] - Local Fields in Authority Records
* [[Step 3.15|Step 3.15]] - Local Authority Master
* [[Step 3.16|Step 3.16]] - JACKPHY Vernacular
* [[Step 3.17|Step 3.17]] - Pseudonyms
* [[Step 3.18|Step 3.18]] - Deblinding XRefs

The rest of the information contained in Step 3 details the matching options for your bibliographic and authority records. As with each step of this profile, these options are suggestions though each one can be customized according to your preference.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.0

2025-03-26T15:51:54Z

Casey: /* National authority files */

==Authority Cleanup Overview==
The first phase of MARS 2.0 Authority Control comprises a battery of routines that update and correct individual subfields and contiguous pairs of subfields, the purpose of which is to increase the likelihood of finding the appropriate authority match.

These corrections are based on a number of subfield update tables, maintained by MARS 2.0 authorities librarians.

MARS 2.0 subfield correction routines include:
* Updating obsolete forms of subdivisions to the current form
* Correcting common typographical errors
* Expanding abbreviations in subject subfields to their fuller form
* Converting common direct geographic subdivisions to their indirect form
* Deleting subject subdivisions which have been canceled or discontinued
* Correcting spacing, capitalization, and punctuation

===Update obsolete subdivisions===
MARS 2.0 uses a number of subfield correction tables to correct common errors in LC subfields


— Relations (General) with the United States

'''changes to''':
— Relations — United States

===Correct typographical errors===
MARS 2.0 also uses the subfield correction tables to correct common spelling errors in LC subdivisions:

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Histroy || History || LC 6XX $x
|-
| Untied States || United States || LC 650 $z and 651 $a
|}
<div style=clear:both></div>

===Expand abbreviations===
The subfield correction tables also support the expansion of outdated or invalid abbreviations in LC headings to the full form. Changes are made only when the outdated or invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Outdated / Invalid
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Hist. & crit. || History and criticism || LC 6XX $x
|-
| U.S. || United States || LC 651 $a, X10 $a, and 6XX $z
|-
| Econ. cond. || Economic conditions || LC 6XX $x
|}
<div style=clear:both></div>

===Direct-to-indirect geographic conversion===
MARS 2.0 uses a table to convert direct geographic subdivisions to the indirect form. Changes are made by the direct-to-indirect subfield conversion program only when the invalid form is the entire text of the $z '''and''' there is only one $z in the heading:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Direct Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $z Paris || $z France $z Paris || LC 6XX fields
|-
| $z Jefferson Co., Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|-
| $z Jefferson County, Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|}
<div style=clear:both></div>

===Chronological conversion===
MARS 2.0 uses a table to convert chronological headings '''$y''' to their correct form. Corrections are made to spelling and punctuation as well as to format:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $y Twentieth century || $y 20th century || LC 6XX fields
|-
| $z 20th century || $y 20th century || LC 6XX fields
|-
| $y 20th centry ||$y 20th century ||LC 6XX fields
|}
<div style=clear:both></div>

===Delete obsolete subdivisions===
MARS 2.0 uses a subfield deletion table to eliminate canceled subfields from LC bibliographic headings, deleting subfields only when the invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Deleted
! style="background:silver" | Field / Subfield
|-
| Addresses, essays, lectures || 6XX $x
|-
| Addresses, sermons, etc. || 6XX $x
|-
| Collected works || 6XX $x
|}
<div style=clear:both></div>

The subfield deletion table also includes common misspellings and typographical errors:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Field / Subfield
|-
| Adresses, essays, lectures || 6XX $x
|-
| Addressses, essays, lectures || 6XX $x
|-
| Collected work || 6XX $x
|}
<div style=clear:both></div>

===Retain selected subdivisions===
The subfield deletion table includes a section that prevents subfield conversions and deletions in headings meeting specific criteria.

— Yearbooks

'''changes to''':
— Periodicals
except when — Yearbooks ''is part of the subfield pair:''
— Students — Yearbooks

===Correct spacing, capitalization, and punctuation===
Most errors in spacing, capitalization and punctuation are corrected as an integral part of the authority cleanup and authority matching processes. Routines are also run to correct spacing and punctuation on the following fields:

1XX, 240, 243, 245, 260, 4XX, 6XX, 7XX, 8XX

These processes eliminate any excess spaces in each field, makes sure each field has the correct punctuation within and between each subfield, and makes sure each field has ending punctuation.


'''original headings''':
100 10 $a Black, Adam, $d 1974- .$t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001, $c Berlin, Germany)

'''updated headings''':
100 10 $a Black, Adam, $d 1974- $t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001 :$c Berlin, Germany)

==Authority Matching Overview==
While Authority Cleanup improves authority controlled headings using proprietary MARS 2.0 correcton tables, authority matching compares each authority controlled heading in your bibliographic records against authority record headings from any of a number of national and other authority files.

===National authority files===
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Abbrev.
! style="background:silver" | National Authority File
! style="background:silver" | Updates
! style="background:silver" | Size
|-
| ! align="center" | NAF || Library of Congress Names || ! align="center" | Weekly || ! align="center" | 8,212,000
|-
| ! align="center" | SAF || Library of Congress Subjects || ! align="center" | Weekly || ! align="center" | 8,611,000
|-
| ! align="center" | CHILD/CYAC || Library of Congress Children's and Young Adult Program || ! align="center" | Weekly || ! align="center" | 12,633
|-
| ! align="center" | LCGFT || Library of Congress Genre Form Terms || ! align="center" | Weekly || ! align="center" | 2,000
|-
| ! align="center" | LCMPT || Library of Congress Medium of Performance Terms || ! align="center" | TBD || ! align="center" | 876
|-
| ! align="center" | MESH || National Library of Medicine || ! align="center" | Annual || ! align="center" | 616,000
|-
| ! align="center" | NLC-N || Library Archives Canada Names || ! align="center" | Frozen || ! align="center" | 653,000
|-
| ! align="center" | NLC-S || Library Archives Canada Subjects || ! align="center" | Frozen || ! align="center" | 659,000
|-
| ! align="center" | AAT || Art & Architecture Thesaurus || ! align="center" | TBD || ! align="center" | 56,876
|-
| ! align="center" | RBMSCV || *Updated* Rare Books and Manuscripts Section Vocabularies || ! align="center" | TBD || ! align="center" | 1,479
|-
| ! align="center" | TGM || Thesaurus for Graphic Materials || ! align="center" | TBD|| ! align="center" | 8,608
|-
| ! align="center" | GSAFD || Guidelines on Subject Access to Individual Works of Fiction, Drama, etc || ! align="center" | Frozen || ! align="center" | 153
|-
| ! align="center" | FAST || Faceted Application of Subject Terminology || ! align="center" | Quarterly || ! align="center" | 1,821,179
|-
| ! align="center" | NASA || NASA Thesaurus || ! align="center" | TBD || ! align="center" | 18,336
|-
| ! align="center" | OLACVGGT || OLAC Video Game Genre Vocabulary || ! align="center" | Frozen || ! align="center" | 66
|-
| ! align="center" | EMBNE || National Library of Spain || ! align="center" | TBD|| ! align="center" | 4,085,978
|-
| ! align="center" | QLSP || Queens Library Spanish Language Subject Headings || ! align="center" | Frozen || ! align="center" | 11,745
|-
| ! align="center" | ERIC|| Education Resources Information Center (ERIC) Thesaurus || ! align="center" | TBD || ! align="center" | 4,552
|-
| ! align="center" | HOMOIT || Homosaurus || ! align="center" | Semi-annual || ! align="center" | 2,834
|}

<div style=clear:both></div>

NOTE: As of September 2018, the Canadiana Authorities product from Library and Archives Canada has been discontinued. Library and Archives Canada is joining NACO and authority records are expected to be distributed via LC.

NOTE: RBMSCV (formerly known as RBMS) was released early 2023; the vocabulary and authorities is fully live in the Backstage system.

===Goals of authority matching===
Authority matching uses the headings in authority records to update or correct the bibliographic headings so they conform to current standards.

Authority matching is also the basis for providing full authority records for your local system. The goals of authority matching are to:
*Update '''invalid headings''' to '''valid forms''' based on cross-references found in authority records (convert to the established form of heading)
*Modify headings that have incorrect '''spacing''', '''punctuation''', '''indicators''', or '''subfield codes''' to the correct form based on matches found
*Update '''invalid higher levels''' of a heading to their '''valid forms''', based on cross-references found in authority records
*Distribute '''matched authority records''' to your institution
*Identify headings requiring '''more attention''' by your staff, through the use of MARS 2.0 reports

===Fields under authority control===
MARS 2.0 corrects and updates the full range of authority controlled headings. The following bibliographic headings / fields are included in MARS 2.0 authority control processing:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" | Name, Title, and Series Authority Controlled Headings
|-
|Personal Names||100, 700
|-
|Corporate Names||110, 710
|-
|Conference Names||111, 711
|-
|Uniform Titles||130, 240, 730
|-
|Uniform Titles in a $t||600, 610, 611, 700, 710, 711
|-
|Series||400, 410, 411, 440, 800, 810, 811, 830
|}
<div style=clear:both></div>

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" |Subject Authority Controlled Headings
|-
|Personal Names||600
|-
|Corporate Names||610
|-
|Conference Names||611
|-
|Uniform Titles||630
|-
|Topical||650
|-
|Geographic||651
|-
|Genre||655
|}
<div style=clear:both></div>

===Subfields disregarded===
A number of MARC subfields are disregarded during MARS 2.0 authority matching. In the following headings, the volume designations in fields 810 and 440 $v, the heading linkage information in field 130 $6, and the ISSN in field 440 $x, are all examples of subfield information which is not under authority control:


810 2 $a John Bartholomew and Son. $t Bartholomew world travel series ;$v 10.
130 0 $6 880-01 $a ”Hsuuan lai his kan” his lieh.
440 4 $a Romanica Gothoburgensia ;$v 12, 16 $x 0080-3863

===Subfields matched or ignored===
The table below shows the subfields that are included in the MARS 2.0 authority matching process:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | MARC Field !!style="background:silver" | Subfields Retained During Matching !! style="background:silver" | Subfields Ignored During Matching
|-
|100, 400, 700, 800 || a b c d f g h k l m n o p q r s t y z || e u v w x 2 3 4 5 6
|-
|110, 410, 710, 810 || a b c d f g h k l m n o p r s t y z || e u v w x 2 3 4 5 6
|-
|111, 411, 711, 811 || a b c d e f g h k l m n o p q r s t u y z || v w x 2 3 4 5 6
|-
|130, 830 || a d f g h k l m n o p r s t x y z || v w 2 3 5 6
|-
|730 || a d f g h k l m n o p r s t y z || v w x 2 3 5 6
|-
|440 || a n p || v w x 6
|-
|600 || a b c d f g h k l m n o p q r s t v x y z || e u w 2 3 4 5 6
|-
|610 || a b c d f g h k l m n o p r s t v x y z || e u w 2 3 4 5 6
|-
|611 || a b c d e f g h k l m n o p q r s t u v x y z || 2 3 4 5 6
|-
|630 || a d f g h k l m n o p r s t v x y z || w 2 3 5 6
|-
|650 || a b c d v x y z || e w 2 3 6
|-
|651 || a b v x y z || w 2 3 6
|-
|655 || a b c v x y z || e w 2 3 6
|}
<div style=clear:both></div>

===Normalization===
Headings from both your bibliographic records and the MARS 2.0 national authority files are normalized before they are compared for matching. MARS 2.0 uses the NACO normalization standard. During normalization:
*Alphabetic characters are converted to '''uppercase'''
*The '''first comma will be retained''' in $a for personal name headings
*All other punctuation is '''removed'''
*Certain '''diacritics''' and '''hyphens''' are left in for JACKPHY normalization
*All other diacritics are '''removed'''
*Special characters are replaced by an '''alphabetic equivalent'''
*Subfield codes are '''removed'''
*Subfield delimiters for '''all but first subfield''' will be left in

'''bib record heading''':
$a Architecture $z Brazil $x S'ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Notice the subfield codes and the diacritic in '''S'ao Paulo''' have been discarded when constructing the normalized form of the heading.

Because subfield codes are ignored during the authority matching process, invalid subfield codes do not affect the matching and may be corrected during the process.

For this example, the normalized form of the established heading '''1XX''' in the authority record is:

'''authority heading''':
$a Architecture $z Brazil $z S~ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Since the normalized forms of the bibliographic and authority headings are the same, the established form in the authority record replaces the form in the bibliographic record.

The bibliographic heading then contains the correct diacritic ~ instead of ' and the subfield code for '''S'ao Paulo''' has been corrected to '''$z'''.

== Topics ==
* [[Step 3.1|Step 3.1]] - Generic Name Headings
* [[Step 3.2|Step 3.2]] - Tag Flipping
* [[Step 3.3|Step 3.3]] - Partial Matches
* [[Step 3.4|Step 3.4]] - Split Headings
* [[Step 3.5|Step 3.5]] - Series Processing
* [[Step 3.6|Step 3.6]] - Subdivision Updates
* [[Step 3.7|Step 3.7]] - Childrens Matching
* [[Step 3.8|Step 3.8]] - MESH Matching
* [[Step 3.9|Step 3.9]] - Canadian Matching
* [[Step 3.10|Step 3.10]] - Local Bibliographic Subject Matching
* [[Step 3.11|Step 3.11]] - Genre Form Matching
* [[Step 3.12|Step 3.12]] - Subject Term Conversions
* [[Step 3.13|Step 3.13]] - Other Subject Vocabulary Matching
* [[Step 3.14|Step 3.14]] - Local Fields in Authority Records
* [[Step 3.15|Step 3.15]] - Local Authority Master
* [[Step 3.16|Step 3.16]] - JACKPHY Vernacular
* [[Step 3.17|Step 3.17]] - Pseudonyms
* [[Step 3.18|Step 3.18]] - Deblinding XRefs

The rest of the information contained in Step 3 details the matching options for your bibliographic and authority records. As with each step of this profile, these options are suggestions though each one can be customized according to your preference.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.4

2024-11-21T16:21:45Z

Casey:

==Step 2.4: Subfield Updates & Deletes ==
[[Image:rda2-1.png]] 

'''PLEASE NOTE''' that if any RDA Enrichment is happening via the RDA Enrichment Profile, any AACR2-specific things (like removal of $e or keeping AACR2 abbreviation in 300 field) will NOT happen; RDA Enrichment supersedes anything that is AACR2-specific.

== Subfield Code Updates Table ==
MARS 2.0 converts these subfield codes:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | Tags
! style="background:silver" align="center" | From
! style="background:silver" align="center" | To
|- align="center"
| 024 || $b || $d
|- align="center"
| 050 || $d || $a
|- align="center"
| 111 || $b || $n
|- align="center"
| 242, 245, 246, 247 || $d || $n
|- align="center"
| 242, 245, 246, 247 || $e || $p
|- align="center"
| 411, 611, 711, 811 || $b || $n
|}
<div style=clear:both></div> 

== Subfield Deletes Table==
MARS 2.0 deletes these subfields:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | Tags
! style="background:silver" align="center" | Subfield
|- align="right"
| 052 || $c
|- align="right"
| 100, 110, 111, 130, 240 || $h
|- align="right"
| 100, 110, 111, 130, 240, 247 || $w
|- align="right"
| 400, 410, 411 || $w
|- align="right"
| 500 || $l, $x, $z
|- align="right"
| 600, 610, 611, 630 || $h
|- align="right"
| 600, 610, 611, 630, 650, 651 || $w
|- align="right"
| 700, 710, 711, 730 || $h
|- align="right"
| 700, 710, 711, 730 || $w
|- align="right"
| 760, 762, 765, 767, 770 || $q
|- align="right"
| 772, 773, 774, 775, 776 || $q
|- align="right"
| 776, 777, 780, 785, 786, 787 || $q
|- align="right"
| 800, 810, 811, 830 || $w
|- align="right"
| 830 || $h, $x
|- align="right"
| 850 || $b
|- align="right"
| 850 || $d
|- align="right"
| 850 || $e
|}
<div style=clear:both></div> 

== Relator $e Deletions==
AACR2 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.

===Relator terms table===
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:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="left"
| arr. || ed. || joint ed.
|- align="left"
| author || editor & translator || joint editor
|- align="left"
| comp. & arr. || editor and translator || joint tr.
|- align="left"
| comp. & tr. || editor || jt. auth.
|- align="left"
| comp. and arr. || joint auth. || jt. author
|- align="left"
| comp. and tr. || joint author || jt. ed.
|- align="left"
| comp. || joint authors || tr. & ed.
|- align="left"
| compiler || joint comp. || tr. and ed.
|- align="left"
| ed. & arr. || joint compiler || tr.
|- align="left"
| ed. & tr. || joint ed. & tr. || trans.
|- align="left"
| ed. and arr. || joint ed. and tr. || translator
|- align="left"
| ed. and tr.
|}
<div style=clear:both></div> 

===Terms table for “ill.” changes===
MARS 2.0 also changes the following variations to '''ill.''' in $e in fields 100 and 700:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="left"
| comp. & illus. || ed. and illus. || jt. illus
|- align="left"
| comp. & ill. || ed. and ill. || jt. ill.
|- align="left"
| comp. and illus. || ill || tr. & illus.
|- align="left"
| comp. and ill. || illus || tr. & ill.
|- align="left"
| ed. & illus. || illustrator || tr. and illus
|- align="left"
| ed. & ill. || joint illus || tr. and ill.
|}
<div style=clear:both></div> 
'''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.''

== 043 Subfield validation==
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]

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.6

2024-11-21T16:19:26Z

Casey: /* Step 2.6: Special Conversions & Additions */

==Step 2.6: Special Conversions & Additions==
[[Image:rda2-1.png]] 
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:
*Add missing format data
**007
**245 $h (for AACR2 records, not RDA unless by request)
*Add missing subfield data
**017 $b
**032 $b
*Complex field conversions
**1XX Main-Entry-Is-Subject
**260 $d to 028 $a
**262 to 260
**300
**301 to 300
**305 to 300
**705 to 700
**715 to 710
**X11

Describe modifications to processing listed above. Provide a different default for the 007 field by listing specific values for each position.

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.

'''PLEASE NOTE''' that if any RDA Enrichment is happening via the RDA Enrichment Profile, any AACR2-specific things (like keeping AACR2 abbreviations in the 300) will NOT happen; RDA Enrichment supersedes anything that is AACR2-specific.

==Specific Fields==
===007 field===
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.

===1xx main-entry-is-subject===
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.

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

===245 $h added (medium-aacr2)===
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:
 245 10 $a Olympia town square /$c by Fred Smith.

'''changes to''':
245 10 $a Olympia town square $h [cartographic material] /$c by Fred Smith.
The following 245 $h GMDs are added based on the values indicated:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | 245 $h
! style="background:silver" align="center" | LDR Byte 06 Value
! style="background:silver" align="center" | 008 contains
|- align="center"
| [cartographic material] || e ''or'' f ||
|- align="center"
| [electronic resource] || m ||
|- align="center"
| [filmstrip] || g || byte 33 = f
|- align="center"
| [kit] || o ||
|- align="center"
| [microform] || a ''or'' t || byte 23 = a, b ''or'' c
|- align="center"
| [motion picture] || g || byte 33 = m
|- align="center"
| [slide] || g || byte 33 = s
|- align="center"
| [sound recording] || i ''or'' j ||
|- align="center"
| [transparency] || g || byte 33 = t
|- align="center"
| [vidoerecording] || g || byte 33 = v
|}
<div style=clear:both></div> 

To modify any values in this table, please indicate any changes in Step 2-7.

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

'''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]).

===017 field===
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.

===028 field===
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.

===032 field===
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.

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.

===260 field===
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''':
*'''028''' field with indicator values '''02''' is '''generated'''
*'''260 $d''' is moved to '''028 $a'''
*'''260 $b''' is copied to '''028 $b'''
*Punctuation in the 260 field is corrected, if necessary

The 260 field conversion option includes special routines that update the punctuation in all 260 fields in the bibliographic records being processed.

These punctuation routines update much of the punctuation in 260 fields to the current standards, including:
*<space> + <colon> before $b
*<comma> before $c
*Final field punctuation, as necessary

===262 field===
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').

If field 262 exists in a bibliographic record:
*262 is '''changed''' to 260
*Changes both indicators of new 260 to blank
*Retains these subfield codes: $a $b $c

For each 262 $k present:
*028 field with indicator values 02 is '''generated'''
*262 $k is '''moved''' to 028 $a subfield
*262 $b is '''copied''' to 028 $b

For each 262 $l (lowercase 'L') present:
*028 field with indicator values 12 '''generated'''
*262 $l is '''moved''' to 028 $a
*262 $b is '''copied''' to 028 $b

If the 262 field does not contain a $k or $l (lowecase 'L'), MARS 2.0 does the following additional conversions:
*262 $c is '''moved''' to 028 $a with indicator values 02
*262 $e is '''moved''' to 028 $b with indicator values 12
*262 $b is '''copied''' to 028 $b
*262 $d '''changed''' to $c code

After all conversions have been completed, the punctuation in the 028 fields and 260 field is updated.

===300 field===
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.

The following changes are made to the 300 $a:
*unp. or n.p. is '''changed''' to 1 v. (unpaged)
*Comma is added to page numbers if missing (e.g., 1264 p. becomes 1,264 p.)
*l. is '''changed''' to leaves
*approx. is '''changed''' to ca.
*p.l. is '''removed''' (e.g., 4 p.l., xv, 20 p. becomes xv, 20 p.)
*unnumbered is '''removed''' and brackets '''added''' (e.g., 48 unnumbered leaves becomes [48] leaves)
*[various pagings] is '''changed''' to (various pagings)

The following changes are made to the 300 $b:
*Illustrative matter is '''rearranged''' to be in correct order
*Obsolete illustrative matter is '''replaced''' with ill. (e.g., tables or fronts. becomes ill.)
*ill. is '''removed''' if followed by parenthetical illustrative matter (e.g., ill. (ports.) becomes ports.)
*illus. is '''changed''' to ill.

The following general changes are made to the 300:
*Various punctuation and spacing issues '''updated'''
*Adds ''';$c cm.''' if missing
*Adds '''300 $a p. ;$c cm.''' if record is monograph and 300 does not exist
*Numbered plate data in $b is '''moved''' to $a; if plate designation is not numbered, it is '''removed'''

 300 $a 22 l. :$b graphs.
300 $a unp. $b illus. $c 30 cm.

'''changes to:'''
300 $a 22 leaves :$b ill. ;$c cm.
300 $a 1 v. (unpaged) :$b ill. ;$c 30 cm.

===301 field===
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.

If field 301 exists in a bibliographic record, MARS 2.0:
*301 is '''changed''' to 300, with indicator values <blank><blank>
*Retains '''$a''' and '''$e''', with data
*$d is '''changed''' to $c
*$b $c $f data is '''combined''' into single $b

===305 field===
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.

If field 305 exists in a bibliographic record:
*305 is '''changed''' to 300, with indicator values <blank><blank>
*Retains '''$a''' and '''$c''', with data
*$b $d $e $f data is '''combined''' into single $b
*Updates the punctuation

For each $m present in the 305 field:
*305 $m is '''moved''' to 028 $a with indicator values 02
*260 $b is '''copied''' to 028 $b

 260 $a New York, N.Y. $b Columbia,$c 1959.
305 $a 1 sound disc (20 min.) :$b analog, 33 1/3 rpm, stereo. ;$c 12 in. $m STMA 8007

'''changes to''':
028 02 $a STMA 8007 $b Columbia
260 $a New York, N.Y. :$b Columbia, $c 1959.
300 $a 1 sound disc (20 min.) :$b analog, 33 1/3 rpm, stereo. ;$c 12 in.

For each $n present in the 305 field:
*305 $n is '''moved''' to 028 $a with indicator values 11
*260 $b is '''copied''' to 028 $b

 305 $a 1 sound disc (18 min.) $c 10 in. $b 74 rpm $d standard $e monaural $m STMA $n L27410X

'''changes to''':
028 02 $a STMA 3059
028 11 $a L27410X
300 $a 1 sound disc (18 min.) :$b 74 rpm, standard, monaural ;$c 10 in.

===705 & 715 field conversion===
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'''.

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

===X11 conference name headings===
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.

 '''Pre-AACR2'''
711 01 $a International Conference on the Chemistry and Uses of Molybdenum, $b 1st, $c University of Reading, $d 1973

'''changes to AACR2 form''':
711 0 $a International Conference on the Chemistry and Uses of Molybdenum $n (1st :$d 1973 :$c University of Reading)

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.4

2024-11-21T16:17:50Z

Casey:

==Step 2.4: Subfield Updates & Deletes ==
[[Image:rda2-1.png]] 

'''PLEASE NOTE''' that if any RDA Enrichment is happening via the RDA Enrichment Profile, any AACR2-specific things (like removal of $e or keeping AACR2 abbreviation in 300 field) will NOT happen; RDA Enrichment supersedes anything that is AACR2-specific.

== Subfield Code Updates Table ==
MARS 2.0 converts these subfield codes:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | Tags
! style="background:silver" align="center" | From
! style="background:silver" align="center" | To
|- align="center"
| 024 || $b || $d
|- align="center"
| 050 || $d || $a
|- align="center"
| 111 || $b || $n
|- align="center"
| 242, 245, 246, 247 || $d || $n
|- align="center"
| 242, 245, 246, 247 || $e || $p
|- align="center"
| 411, 611, 711, 811 || $b || $n
|}
<div style=clear:both></div> 

== Subfield Deletes Table==
MARS 2.0 deletes these subfields:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | Tags
! style="background:silver" align="center" | Subfield
|- align="right"
| 052 || $c
|- align="right"
| 100, 110, 111, 130, 240 || $h
|- align="right"
| 100, 110, 111, 130, 240, 247 || $w
|- align="right"
| 400, 410, 411 || $w
|- align="right"
| 500 || $l, $x, $z
|- align="right"
| 600, 610, 611, 630 || $h
|- align="right"
| 600, 610, 611, 630, 650, 651 || $w
|- align="right"
| 700, 710, 711, 730 || $h
|- align="right"
| 700, 710, 711, 730 || $w
|- align="right"
| 760, 762, 765, 767, 770 || $q
|- align="right"
| 772, 773, 774, 775, 776 || $q
|- align="right"
| 776, 777, 780, 785, 786, 787 || $q
|- align="right"
| 800, 810, 811, 830 || $w
|- align="right"
| 830 || $h, $x
|- align="right"
| 850 || $b
|- align="right"
| 850 || $d
|- align="right"
| 850 || $e
|}
<div style=clear:both></div> 

== Relator $e Deletions==
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.

===Relator terms table===
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:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="left"
| arr. || ed. || joint ed.
|- align="left"
| author || editor & translator || joint editor
|- align="left"
| comp. & arr. || editor and translator || joint tr.
|- align="left"
| comp. & tr. || editor || jt. auth.
|- align="left"
| comp. and arr. || joint auth. || jt. author
|- align="left"
| comp. and tr. || joint author || jt. ed.
|- align="left"
| comp. || joint authors || tr. & ed.
|- align="left"
| compiler || joint comp. || tr. and ed.
|- align="left"
| ed. & arr. || joint compiler || tr.
|- align="left"
| ed. & tr. || joint ed. & tr. || trans.
|- align="left"
| ed. and arr. || joint ed. and tr. || translator
|- align="left"
| ed. and tr.
|}
<div style=clear:both></div> 

===Terms table for “ill.” changes===
MARS 2.0 also changes the following variations to '''ill.''' in $e in fields 100 and 700:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="left"
| comp. & illus. || ed. and illus. || jt. illus
|- align="left"
| comp. & ill. || ed. and ill. || jt. ill.
|- align="left"
| comp. and illus. || ill || tr. & illus.
|- align="left"
| comp. and ill. || illus || tr. & ill.
|- align="left"
| ed. & illus. || illustrator || tr. and illus
|- align="left"
| ed. & ill. || joint illus || tr. and ill.
|}
<div style=clear:both></div> 
'''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.''

== 043 Subfield validation==
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]

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.4

2024-11-21T16:17:37Z

Casey:

==Step 2.4: Subfield Updates & Deletes ==
[[Image:rda2-1.png]] 

'''PLEASE NOTE''' that if any RDA Enrichment is happening via the RDA Enrichment Profile, any AACR2-specific things (like removal of $e or keeping AACR2 abbreviation in 300 field) will NOT happen; RDA Enrichment supersedes anything that is AACR2-specific.

== Subfield Code Updates Table ==
MARS 2.0 converts these subfield codes:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | Tags
! style="background:silver" align="center" | From
! style="background:silver" align="center" | To
|- align="center"
| 024 || $b || $d
|- align="center"
| 050 || $d || $a
|- align="center"
| 111 || $b || $n
|- align="center"
| 242, 245, 246, 247 || $d || $n
|- align="center"
| 242, 245, 246, 247 || $e || $p
|- align="center"
| 411, 611, 711, 811 || $b || $n
|}
<div style=clear:both></div> 

== Subfield Deletes Table==
MARS 2.0 deletes these subfields:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | Tags
! style="background:silver" align="center" | Subfield
|- align="right"
| 052 || $c
|- align="right"
| 100, 110, 111, 130, 240 || $h
|- align="right"
| 100, 110, 111, 130, 240, 247 || $w
|- align="right"
| 400, 410, 411 || $w
|- align="right"
| 500 || $l, $x, $z
|- align="right"
| 600, 610, 611, 630 || $h
|- align="right"
| 600, 610, 611, 630, 650, 651 || $w
|- align="right"
| 700, 710, 711, 730 || $h
|- align="right"
| 700, 710, 711, 730 || $w
|- align="right"
| 760, 762, 765, 767, 770 || $q
|- align="right"
| 772, 773, 774, 775, 776 || $q
|- align="right"
| 776, 777, 780, 785, 786, 787 || $q
|- align="right"
| 800, 810, 811, 830 || $w
|- align="right"
| 830 || $h, $x
|- align="right"
| 850 || $b
|- align="right"
| 850 || $d
|- align="right"
| 850 || $e
|}
<div style=clear:both></div> 

== Relator $e Deletions==
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.

'''PLEASE NOTE''' that if any RDA Enrichment is happening via the RDA Enrichment Profile, any AACR2-specific things (like removal of $e) will NOT happen; RDA Enrichment supersedes anything that is AACR2-specific.

===Relator terms table===
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:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="left"
| arr. || ed. || joint ed.
|- align="left"
| author || editor & translator || joint editor
|- align="left"
| comp. & arr. || editor and translator || joint tr.
|- align="left"
| comp. & tr. || editor || jt. auth.
|- align="left"
| comp. and arr. || joint auth. || jt. author
|- align="left"
| comp. and tr. || joint author || jt. ed.
|- align="left"
| comp. || joint authors || tr. & ed.
|- align="left"
| compiler || joint comp. || tr. and ed.
|- align="left"
| ed. & arr. || joint compiler || tr.
|- align="left"
| ed. & tr. || joint ed. & tr. || trans.
|- align="left"
| ed. and arr. || joint ed. and tr. || translator
|- align="left"
| ed. and tr.
|}
<div style=clear:both></div> 

===Terms table for “ill.” changes===
MARS 2.0 also changes the following variations to '''ill.''' in $e in fields 100 and 700:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="left"
| comp. & illus. || ed. and illus. || jt. illus
|- align="left"
| comp. & ill. || ed. and ill. || jt. ill.
|- align="left"
| comp. and illus. || ill || tr. & illus.
|- align="left"
| comp. and ill. || illus || tr. & ill.
|- align="left"
| ed. & illus. || illustrator || tr. and illus
|- align="left"
| ed. & ill. || joint illus || tr. and ill.
|}
<div style=clear:both></div> 
'''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.''

== 043 Subfield validation==
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]

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.4

2024-11-21T16:16:48Z

Casey:

==Step 2.4: Subfield Updates & Deletes ==
[[Image:rda2-1.png]] 

== Subfield Code Updates Table ==
MARS 2.0 converts these subfield codes:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | Tags
! style="background:silver" align="center" | From
! style="background:silver" align="center" | To
|- align="center"
| 024 || $b || $d
|- align="center"
| 050 || $d || $a
|- align="center"
| 111 || $b || $n
|- align="center"
| 242, 245, 246, 247 || $d || $n
|- align="center"
| 242, 245, 246, 247 || $e || $p
|- align="center"
| 411, 611, 711, 811 || $b || $n
|}
<div style=clear:both></div> 

== Subfield Deletes Table==
MARS 2.0 deletes these subfields:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | Tags
! style="background:silver" align="center" | Subfield
|- align="right"
| 052 || $c
|- align="right"
| 100, 110, 111, 130, 240 || $h
|- align="right"
| 100, 110, 111, 130, 240, 247 || $w
|- align="right"
| 400, 410, 411 || $w
|- align="right"
| 500 || $l, $x, $z
|- align="right"
| 600, 610, 611, 630 || $h
|- align="right"
| 600, 610, 611, 630, 650, 651 || $w
|- align="right"
| 700, 710, 711, 730 || $h
|- align="right"
| 700, 710, 711, 730 || $w
|- align="right"
| 760, 762, 765, 767, 770 || $q
|- align="right"
| 772, 773, 774, 775, 776 || $q
|- align="right"
| 776, 777, 780, 785, 786, 787 || $q
|- align="right"
| 800, 810, 811, 830 || $w
|- align="right"
| 830 || $h, $x
|- align="right"
| 850 || $b
|- align="right"
| 850 || $d
|- align="right"
| 850 || $e
|}
<div style=clear:both></div> 

== Relator $e Deletions==
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.

'''PLEASE NOTE''' that if any RDA Enrichment is happening via the RDA Enrichment Profile, any AACR2-specific things (like removal of $e) will NOT happen; RDA Enrichment supersedes anything that is AACR2-specific.

===Relator terms table===
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:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="left"
| arr. || ed. || joint ed.
|- align="left"
| author || editor & translator || joint editor
|- align="left"
| comp. & arr. || editor and translator || joint tr.
|- align="left"
| comp. & tr. || editor || jt. auth.
|- align="left"
| comp. and arr. || joint auth. || jt. author
|- align="left"
| comp. and tr. || joint author || jt. ed.
|- align="left"
| comp. || joint authors || tr. & ed.
|- align="left"
| compiler || joint comp. || tr. and ed.
|- align="left"
| ed. & arr. || joint compiler || tr.
|- align="left"
| ed. & tr. || joint ed. & tr. || trans.
|- align="left"
| ed. and arr. || joint ed. and tr. || translator
|- align="left"
| ed. and tr.
|}
<div style=clear:both></div> 

===Terms table for “ill.” changes===
MARS 2.0 also changes the following variations to '''ill.''' in $e in fields 100 and 700:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="left"
| comp. & illus. || ed. and illus. || jt. illus
|- align="left"
| comp. & ill. || ed. and ill. || jt. ill.
|- align="left"
| comp. and illus. || ill || tr. & illus.
|- align="left"
| comp. and ill. || illus || tr. & ill.
|- align="left"
| ed. & illus. || illustrator || tr. and illus
|- align="left"
| ed. & ill. || joint illus || tr. and ill.
|}
<div style=clear:both></div> 
'''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.''

== 043 Subfield validation==
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]

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.0

2024-11-21T16:15:49Z

Casey:

==Bibliographic Validation & Cleanup==
MARS 2.0 makes changes in over 100 different MARC fields within your bibliographic record. Our ''Bibliographic Cleanup'' service updates many elements in MARC bibliographic records to conform with current MARC 21 standards, providing increased consistency within your bibliographic files.

The level of MARC update is entirely configurable by you and your staff. The update process is tailored to your expectations of what you’d like to see happen within your bibliographic records.

'''PLEASE NOTE''' that if any RDA Enrichment is happening via the RDA Enrichment Profile, any AACR2-specific things (like removal of $e) will NOT happen; RDA Enrichment supersedes anything that is AACR2-specific.

=== Standard MARC21 validation ===
As soon as we receive your files, they are prepared for processing. The MARS 2.0 programs check '''all''' files of MARC records submitted to ensure they conform to the basic structural requirements of the MARC21 communications format. Our validation programs ensure that all records meet the following criteria:<ul><li>Leader is present and correctly structured<li>Directory is present and correctly structured<li>No record exceeds 99,999 characters. Including bibliographic records larger than 99,999 byte maximum size prevents successful processing of the input files. Records cannot be segmented (broken apart into multiple physical records) to reach the maximum size limit. These records will be output as potentially corrupt for the library to review<li>No field exceeds 9,999 characters (MARC21 directory limitation)<li>If a record exceeds the character or field size it is not processed. If there is a large number of rejected records our programmers will contact the library project manager to determine a course of action<li>All records contain the following standard MARC delimiters:<ul><li>Record terminators (ASCII 1D16)<li>Field terminators (ASCII 1E16)<li>Subfield delimiters (ASCII 1F16)</ul><li>All records contain valid characters (either in MARC8 or UTF8)<li>Any null characters (hex 00) are changed to spaces when records are loaded<li>MARS 2.0 will also delete empty fields or subfields as records are loaded</ul>
'''Note''': ''MARS 2.0 programs can process MARC21 records that lack 001, 008 or other fields.''

== Topics ==
Section 2 is one of our most comprehensive documents, and as such is too large for a single page.
* [[Step 2.1|Step 2.1]] - Validate 010, 020, 022, 034 fields
* [[Step 2.2|Step 2.2]] - Leader & fixed field updates
* [[Step 2.3|Step 2.3]] - Field updates & deletes
* [[Step 2.4|Step 2.4]] - Subfield updates & deletes
* [[Step 2.5|Step 2.5]] - Indicator values
* [[Step 2.6|Step 2.6]] - Field conversions & additions
* [[Step 2.7|Step 2.7]] - Initial article & filing indicators
* [[Step 2.8|Step 2.8]] - GMD standardization
* [[Step 2.9|Step 2.9]] - Minimal Punctuation (Forthcoming)
* [[Step 2.11|Step 2.11]] - Reading Levels
* [[Step 2.12|Step 2.12]] - Identities Management/URI Enrichment

The rest of the information contained in Step 2 details the kinds of changes that are available to make within your bibliographic records. As with each step of this profile, these options are suggestions though each one can be customized according to your preference.

==links==
<center>[[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.13|2.13]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

RDA 5.4

2024-11-18T18:35:30Z

Casey: /* Music abbreviations */

==RDA 5.4: Uniform Title Updates (X00, X10, X30, 240)==
[[image:rda5-4.png]]
===Music abbreviations===
Certain abbreviations should no longer be used in the arranged statement for music (240 $o, 6XX $o, 7XX $o): acc., arr., unacc. [http://files.library.northwestern.edu/public/pccahitg/RDA_conversion.ArrAccUnacc.doc NAF Conversion documentation, Music abbreviations] (pdf) The following abbreviations will be spelled out in subfield $o in music headings. Additionally, these abbreviations will be spelled out when found in '''$m''', '''$o''', '''$p''', and '''$t''' of the 1XX, 6XX, 7XX, and 8XX fields.

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
|-
| acc. || accompaniment
|-
| arr. || arranged
|-
| unacc. || unaccompanied
|}
<div style=clear:both></div>


'''original fields''':
240 00 $a Wedding of Gloriana. $k Selections; $o arr.
630 00 $a Wedding of Gloriana. $k Selections; $o unacc.

'''updated fields''':
240 00 $a Wedding of Gloriana. $k Selections; $o arranged.
630 00 $a Wedding of Gloriana. $k Selections; $o unaccompanied.

===Uniform titles with 2 languages in $l > 700 fields===
When a uniform title $l contains two languages, this can be separated into two 700 fields with individual $l subfields. When the uniform title is the 240 field, the 240 field is removed during the process: [http://access.rdatoolkit.org/document.php?id=rdachp6&target=rda6-3526# RDA 6.11.1.4] (html)

<div style=clear:both></div>


'''original fields''':
100 0 $a Plato
240 10 $a Works. $l English & Greek. $f 1914

'''updated fields''':
700 0 $a Plato. $t Works. $l English. $f 1914.
700 0 $a Plato. $t Works. $l Greek. $f 1914.

Currently, not all Library of Congress authorities have been updated to reflect this type of change, so these new 700 fields may no longer match the LC authority file and you may see them on our Unmatched Headings Report. As these changes are made in LC, authorities for the unmatched headings will be delivered as part of ongoing processing.

Also, please note that when a 240 contains $l Polyglot an automated system cannot determine what the multiple languages are without the item in hand. These will be reported so you can add your own 700's, at will.

UPDATE: When we are adding a 7XX from the 240 fields, if one of the languages from the 240 $l appears in the 041 $h, that language will be omitted from the newly created 7XX

==Default==
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- style="background:#CCFFFF; font-size: 110%;"
| Make all changes & expand abbreviations for uniform titles in 240, X00, X10, X11, X30 fields.
|}
<div style=clear:both></div> 
==links==
<center>[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]]</center>
[[category:RDA Profile Guide]]

Step 2.1

2024-11-18T18:32:46Z

Casey: added "979" as ISBN possibilitey

== Step 2.1: Validation ==
[[Image:rda2-1.png]] 

== Numeric Field Validation ==
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>

=== Historical fact ===
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.

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

== Pre-2001 LCCN ==
LCCN Structure A (2000 and earlier) numbers are formatted according to the following 6 divisions (separated by hyphens): 
 1 2 3 4 5 6
nb#-71-005810-#-/AC-/r86

#3-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''
#2 digits, usually the last 2 digits of the '''year'''
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits
#Blank '''space'''
#Optional variable length '''suffix''' and/or alphabetic identifier
#Optional '''revision date'''

Examples of LCCN Structure A (the character # represents a single space): 
 ###95156543# Displayed as: 95-156543
###94014580#/AC/r95 Displayed as: 94-14580/AC/r95
###79310919#//r86 Displayed as: 79-310919//r86
nb#71005810# Displayed as: nb71-5810

== Post-2000 LCCN ==
LCCN Structure B (2001 and later) numbers are formatted according to the following 3 divisions (separated by hyphens): 
 1 2 3
##-2005-256543

#2-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''
#4-digit '''year'''
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits

Examples of LCCN Structure B (the character # represents a single space): 
 ##2005256543 Displayed as: 2005-256543
##2010014580 Displayed as: 2010-14580
nb2005005810 Displayed as: nb2005-5810

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.

=== LCCN structure A corrections ===
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):
*If the first character of the LCCN is a number (no prefix is present), the programs insert 3 blanks (###) before the number:
 Original: 95-156543 Corrected to: ###95156543#

*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:
 Original: n95-156543 Corrected to: n##95156543#

*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:
 Original: nb95-156543 Corrected to: nb#95156543#

*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:
 Original: nb#9-156543 Corrected to: nb#09156543#
Original: nb#95-156543 Corrected to: nb#95156543#

*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:
 Original: nb#95-6543 Corrected to: nb#95006543#
Original: nb#95-56543 Corrected to: nb#95056543#

*If the LCCN contains a suffix, the suffix is removed in accordance with the revised LC standard for Structure A LCCNs:
 Original: nb#95-516543//r86 Corrected to: nb#95156543#

*If the LCCN does not end with a blank, MARS 2.0 programs insert a blank following the last digit:
 Original: nb#95-516543 Corrected to: nb#95156543#

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

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

*The following invalid LCCN prefixes are corrected to the valid format (# = blank):
 #a# -> a##
##a -> a##
#bc -> bc#
# -> ###
## -> ###

=== LCCN structure B corrections ===
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):
*If the first character of the LCCN is a number (no prefix is present), the programs insert 2 blanks before the number:
 Original: 2005-256543 Corrected to: ##2005256543

*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:
 Original: n2005-256543 Corrected to: n#2005256543
Original: nb2005-256543 Corrected to: nb2005256543

*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:
 Original: nb2005-6543 Corrected to: nb2005006543

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

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

*The following invalid LCCN prefixes are corrected to the valid format (# = blank):
 #a -> a#
#bc -> bc
# -> ##

== 020 Field ==
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:
*If there are 9 digits in the ISBN, a 0 (zero) is inserted before the first digit in the ISBN:
 Original: 873671008 Corrected to: 0873671008

*All hyphens are deleted:
 Original: 1-873671-008 Corrected to: 1873671008

*A lowercase x is converted to uppercase:
 Original: 187367100x Corrected to: 187367100X

*If ISBN is 13 digits, MARS 2.0 programs will verify that the first 3 digits are '''978''' or '''979'''.

*As an optional service, MARS 2.0 programs will correct the order of the ISBN (i.e. pairs of 13/10 and 13/10)

*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):
 Original: 1873671008 Corrected to: 9781873671000

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

=== Historical fact ===
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.

=== Ordering 020 fields ===
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: 
 ISBN-13: 978-1-873671-00-0
ISBN-10: 1-873671-008

=== Repeating 020 subfields ===
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: 
 020 $a 11111111 $a 22222222
Corrected to:
020 $a 11111111
020 $a 22222222

=== Binding information in 020 fields ===
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.

If the 020 field contains a $b and an 020 $a exists:
*$b delimiter and subfield code are deleted
*020 $b data is enclosed in parentheses
*A blank is inserted at the end of the immediately preceding 020 $a data
*020 $b data, enclosed in parentheses, is moved after the blank at the end of the 020 $a data
 Original: 020 $a 1873671008 $b pbk. Corrected to: 020 $a 1873671008 (pbk.)

=== 020 with missing $a ===
If the 020 field contains a $b and no 020 $a exists, the $b code will be changed to $c: 
 020 $b pbk.
Corrected to:
020 $c pbk.

=== 020 with multiple $c ===
If the 020 field contains multiple $c, each $c is placed in a separate 020 field: 
 020 $c 4.95 (lib. bdg.) $c 3.60 (pbk.)
Corrected to:
020 $c 4.95 (lib. bdg.)
020 $c 3.60 (pbk.)
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.

=== 020 with multiple $a and $c ===
MARS 2.0 programs correctly handle 020 fields with multiple $a and $c: 
 020 $a 11111111 $c 4.95 $a 22222222 $c 3.60 $c 8.97 $b pbk.
Corrected to:
020 $a 11111111 $c 4.95
020 $a 22222222 $c 3.60
020 $c 8.97 (pbk.)

== 022 Field ==
MARS 2.0 Update processing can validate 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): 
 1234-1234
1234-123X

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:
*If the ISSN has no hyphen, adds a hyphen between the fourth and fifth digits:
 Original: 12345678 Corrected to: 1234-5678

*Converts a lowercase '''x''' to uppercase:
 Original: 1234-567x Corrected to: 1234-567X

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

== 034 Field ==
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:
*Places each $a in a separate 034 field
*Changes each 034 field first indicator to value 1
 034 2_$a a $b 100000 $a a $b 120000
Corrected to:
034 1_$a a $b 100000
034 1_$a a $b 120000

=== Historical fact ===
First indicator value '''2''' became obsolete when field 034 was made repeatable in 1982. Older bibliographic records may still have first indicator value 2.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.18

2024-10-17T15:58:47Z

Casey: /* links */

==Deblinding XRefs==
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.

LC authority records are constructed so that they are naturally '''self deblinding''':


'''established heading''':
150 $a Fishing

'''see from heading''':
450 $a Sport fishing

'''see from also heading''':
550 $a Wildlife-related recreation

===See from xrefs===
Most ILS generate a heading based on the 150 and 450 fields in the authority above:


'''Sport fishing'''
''See'' Fishing

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

This record is '''self deblinding''' since the display '''Sport fishing, See Fishing''' is not generated unless you have works cataloged under that term.

If you have works cataloged under the term '''Fishing''', MARS 2.0 will include the authority record above in your authority file.

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.

===See from also xrefs===
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:


'''Wildlife-related recreation'''
''See also'' Fishing

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.

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.

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.

MARS 2.0 staff does not recommend the removal of 5XX fields from authority records, or converting a 5XX tag.

The available See Also xref in your ILS will direct the patron to the related term of Fishing found in your catalog.

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.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.17

2024-10-17T15:58:37Z

Casey: /* links */

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

Prior to the adoption of AACR2, each work was to be cataloged under the actual name of the author.

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.

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.

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.

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.

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.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.16

2024-10-17T15:58:26Z

Casey: /* links */

==JACKPHY Vernacular==
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.

MARS 2.0 provides special processing for JACKPHY bibliographic records:
'''J'''apanese, '''A'''rabic, '''C'''hinese, '''K'''orean, '''P'''ersian, '''H'''ebrew, '''Y'''iddish.

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.

===JACKPHY Vernacular and 880 fields===
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.

The links between the vernacular headings (880) and romanized heading fields are maintained during MARS 2.0 processing.

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.

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.

MARS 2.0 processing does not convert the romanized portions of 880 headings due to the lack of integrity of the resulting headings.

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.


'''original bib headings''':
100 1 $6 880-1 $a Atiman, Adriano, $d ca. 1864-1956.
880 1 $6 100-1 $a <chinese characters for Atiman, Adriano>, $d ca. 1864-1956.

'''The bibliographic heading in field 100 would match the See From tracing in the following LC''' n 82027709:
100 1 $a Atiman, Adriano, $d 1864 (ca.)-1956
400 1 $a Atiman, Adriano, $d ca. 1864-1956

MARS 2.0 converts the roman heading to the current form. The vernacular (880) heading would not be changed.


'''The updated bibliographic record would contain the following headings and an entry would be added to report R86''':
100 1 $6 880-1 $a Atiman, Adriano, $d 1864 (ca.)-1956.
880 1 $6 100-1 $a <chinese characters for Atiman, Adriano>, $d ca. 1864-1956.

===Diacritics in JACKPHY===
For JACKPHY personal names, MARS 2.0 includes certain diacritics to enhance the matching capability.

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.

MARS 2.0 assumes a bibliographic record may contain JACKPHY romanized headings if at least 1 out of the following 3 criteria is present:
*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''':
**066 $a $1
**066 $b $)1
*'''880 alternate graphic represent''' field exists
*Non-roman language codes in field 008[35-37]

===Diacritics retained===
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:
*Alif
*Ayn
*Breve
*Circumflex
*Hyphen
*Macron
*Umlaut

The preservation of these diacritics prevents matching a normalized JACKPHY personal name heading to the incorrect LC authority record.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.15

2024-10-17T15:58:16Z

Casey: /* links */

==Step 3.15: Local Authority Master==
[[Image:a3-13.png]] 
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.

===Matched before national file===
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:


'''If your library decided to use the following heading in a set of bib records''':
440 0 $a West Group's tax practice series

'''This is in conflict with the authorized form in the LC authority for this title''':
010 $a n 00090467
130 0 $a Tax practice series (St. Paul, Minn.)
430 0 $a West Group's tax practice series

A heading that matches a 4XX '''See From''' tracing in an LC authority record would convert to the authorized form in the 1XX field.

To prevent this heading flip, you must provide a file of locally generated authority records against which your headings are matched '''first'''.

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

===Matched after national file===
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).

This is especially helpful when the not-yet-authorized heading appears in multiple bibliographic records.

===Local heading matching===
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.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.14

2024-10-17T15:58:06Z

Casey: /* links */

==Step 3.14: Local Fields in Authority Records==
[[Image:a3-12.png]] 
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.

MARS 2.0 can retain your local authority fields within matching updated authorities, which are then delivered to you to overlay at your end.

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:


'''original authority from library''':
001 n 50006324
100 1 $a Morse, John Torrey, $d 1840-1937
670 $a From his works on Thomas Jefferson, with special notes $5 BLW

'''LC match with''' $5 local note retained:
001 n 50006324
040 $a DLC $c DLC $d DLC
100 1 $a Morse, John Torrey, $d 1840-1937
400 1 $a Morse, John T. $q (John Torrey), $d 1840-1937
670 $a From his works on Thomas Jefferson, with special notes $5 BLW

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.

The '''local notes''' within your original authority files would be '''retained''' in the updates that are delivered by Backstage.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.11

2024-10-17T15:57:47Z

Casey: /* links */

==Step 3.11: Genre Form Matching==
[[Image:a3-11b.png]] 
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.

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

==Library of Congress Genre Form Terms==
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:


'''use of $2 in heading''':
655 7 $a Fiction films $2 lcsh

'''updated to lcgft 655 tag''':
655 7 $a Fiction films $2 lcgft

LC has also added the subdivision '''Globes''' to the '''Map''' genre changes:


651 0 $a Washington (D.C.) $v Pictorial maps.
'''changes to''':
651 0 $a Washington (D.C.) $v Maps.
655 7 $a Pictorial maps. $2 lcgft

651 0 $a Ganymede (Satellite) $v Globes.
'''changes to''':
651 0 $a Ganymede (Satellite) $v Maps.
655 7 $a Globes. $2 lcgft

===Genre form terms in topical 650 headings===
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.

Topical subject headings are not affected in any way by the options selected for genre form headings.

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.

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:


'''Matching against''' LCGFT:
obsolete '''655 heading''':
655 0 $a Sitcoms (Television programs)

updated '''655 heading''':
655 7 $a Situation comedies (Television programs) $2 lcgft

'''Matching against''' GSAFD:
obsolete''' 655 heading''':
655 7 $a Sitcoms. $2 gsafd

updated''' 655 heading''':
655 7 $a Comedy television programs. $2 gsafd

===Genre form update reports===
Updates for genre form headings are included in '''Updated Headings''' report (see Step 5.2, R30).

==AAT Authority Records==
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'''):


obsolete''' 655 heading''':
655 7 $a catalogs, on-line. $2 aat

updated''' 655 heading''':
655 7 $a online catalogs. $2 aat

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

==GSAFD Authority Records==
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'''):


obsolete''' 655 heading''':
655 7 $a Utopias. $2 gsafd

updated''' 655 heading''':
655 7 $a Utopian fiction. $2 gsafd

==MeSH Genre Authority Records==
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:


obsolete''' 655 heading''':
655 7 $a Meeting Reports. $2 mesh

updated''' 655 heading''':
655 7 $a Congresses. $2 mesh

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:


'''use of $2 in 655''':
655 7 $a Almanacs. $2 mesh

'''updated 2nd indicator''' 2:
655 2 $a Almanacs.

==Rare Books Manuscripts Section Vocabularies==
MARS 2.0 can match against the NEW '''Rare Books and Manuscript Section''' genre authority files (hereafter referred to as '''RBMSCV'''). The original RBMS vocabulary was once 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'''. In 2023 the vocabulary was re-published as a single thesaurus on [https://id.loc.gov/vocabulary/rbmscv.html id.loc.gov/]

Backstage's process will automatically search those genre terms with the old RBMS $2 (differing for each of the eight thesauri) against the new single thesaurus ($2 rbmscv) and will update the term and the $2. URIs are also available for those who desire them.


obsolete''' 655 heading''':
655 7 $a Fine paper printings (Publishing). $2 rbpub

updated''' 655 heading''':
655 7 $a Fine paper printings. $2 rbmscv

'''Each client can determine whether they'd like to retain the subdivisions from the original vocabulary or remove them to conform to current vocabulary practice. Additionally, each client can decide if they'd like to retain or delete those that do not have an RBMSCV equivalent.'''

Questions have arisen regarding the old subdivisions that were allowed in the previous edition of RBMS. The vast majority of our clients that have asked about this old subdivisions DO want to retain them in the new vocabulary even though they're not technically allowed. Because of this, '''this is our default process'''. However, we're more than happy to delete them if you prefer! Another option to consider would be to copy the original RBMS heading to a local 6XX to retain the subdivisions, then delete them from the new/updated 655 RBMSCV heading.

==Thesaurus for Graphic Materials==
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:
{| border="0" cellspacing="0" cellpadding="5" style="border-collapse:collapse;"
|- align="left"
| gmgpc || genre terms || !- align="right" | 670 records
|- align="left"
| lctgm || subject terms || !- align="right" | 7,142 records
|}
<div style=clear:both></div> 

==Faceted Access for Subject Terminology==
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.

The FAST authority database comprises over 1.7 million authorities.

FAST authorities allow for a faceted approach to listing subject headings within bibliographic records:


LCSH
650 #0 $a American loyalists $z England.
651 #0 $a United States $x History $y Revolution, 1775-1783 $v Biography.
650 #0 $a Secret service $z Great Britain.
650 #0 $a Painters $z United States.

FAST
648 #7 $a 1775-1783. $2 fast
650 #7 $a American loyalists. $2 fast
611 27 $a American Revolution (1775-1783) $2 fast
650 #7 $a Secret service. $2 fast
650 #7 $a Painters. $2 fast
651 #7 $a England. $2 fast
651 #7 $a United States. $2 fast
651 #7 $a Great Britain. $2 fast
655 #7 $a Biography. $2 fast
655 #7 $a History. $2 fast


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.

<div style=clear:both></div> 

==OLACVGGT==
The OLAC Video Game Genre Terms is a vocabulary that implemented in 2018 and is not intended to be updated any further.


'''Bib 655 heading''':
655 7 $a 2D video games. $2 olacvggt

==Cartographic Update==
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:


Original fields
651 #0 $a Scotland $v Bathymetric maps.
651 #0 $a Scotland $v Globes.
651 #0 $a Scotland $v Maps, Outline.

Updated fields
651 #0 $a Scotland $v Maps.
655 #7 $a Bathymetric maps $2 lcgft.
655 #7 $a Globes $2 lcgft.
655 #7 $a Outline maps $2 lcgft.


<div style=clear:both></div> 

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.10

2024-10-17T15:57:36Z

Casey: /* links */

==Step 3.10: Local Bib Subject Matching==
[[Image:a3-10.png]] 
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.

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.

===Search 6xx x4 against LC===
[[Image:a3-10a.png]] 
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'''.

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''':


'''original local bib heading''':
650 4 $a American Civil War, 1861-1865.

'''updated local bib headings''':
650 0 $a United States $x History $x Civil War, 1861-1865.

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.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.9

2024-10-17T15:57:23Z

Casey: /* links */

==Step 3.9: Canadian Matching==
[[Image:a3-9.png]] 
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.

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.

===Fields matched===
The following fields are matched against Canadian: 
[[Image:a3-9b.png]] 
'''Note:''' ''Only those with a 2nd indicator of 5 are Canadian Headings''

===Ignore or remove without processing===
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.

Most libraries in which the Canadian headings are not used and are not causing any problems for patrons choose to '''ignore''' these headings.

Alternatively, you can choose to '''remove without processing''' any Canadian heading that MARS 2.0 encounters during processing.

==Databases and Search Order==
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:
*Canadian Authority Files
*LC Authority File

===Search Canadian authority file only===
[[Image:a3-9b.png]] 
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'''.

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

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.

===Search Canadian authority file against LC adult only===
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: 
[[Image:a3-9c.png]] 
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'''.

For those headings that match a heading in the LC Authority File, the 2nd indicator is changed from '''5''' 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 '''5''' to '''0'''.

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

Or, you could choose that any Canadian headings that fail to match an LC authority record are '''removed''' from the bibliographic record.

===Search Canadian 1st, LC 2nd===
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'''.

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''': 
[[Image:a3-9d.png]] 
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.

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.

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:


'''LC''' n 79102766''':'''
100 1 $a Atwood, Margaret Eleanor, $d 1939-
400 1 $a Atwood, Margaret, $d 1939-

'''canadian authority''' 0100H2190''':'''
100 1 $a Atwood, Margaret, $d 1939-
400 1 $a Atwood, Margaret
400 1 $a Atwood, Margaret Eleanor
400 1 $a Atwood, Margaret Eleanor, $d 1939-

'''original canadian bib headings in sample records:'''
(1) 100 1 $a Atwood, Margaret, $d 1939-
(2) 700 1 $a Atwood, Margaret Eleanor, $d 1939-
(3) 100 1 $a Atwood, Margaret
(4) 700 1 $a Atwood, Margaret Eleanor

'''The headings above would be converted as follows, based on authority match option selected.'''
'''LC 1st, Canadian 2nd (LC preferred):'''
(1) 100 1 $a Atwood, Margaret Eleanor, $d 1939- LC updated heading
(2) 700 1 $a Atwood, Margaret Eleanor, $d 1939- LC matched heading
(3) 100 1 $a Atwood, Margaret, $d 1939- CAN updated heading
(4) 700 1 $a Atwood, Margaret, $d 1939- CAN updated heading

'''Canadian 1st, LC 2nd (Canadian preferred):'''
(1) 100 1 $a Atwood, Margaret, $d 1939- CAN matched heading
(2) 700 1 $a Atwood, Margaret, $d 1939- CAN updated heading
(1) 100 1 $a Atwood, Margaret, $d 1939- CAN updated heading
(2) 700 1 $a Atwood, Margaret, $d 1939- CAN updated heading

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.8

2024-10-17T15:57:11Z

Casey: /* links */

==Step 3.8: MeSH Matching==
[[Image:a3-8.png]] 
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.

===Fields matched===
The following fields are matched against MESH: 
[[Image:3-9b.png]] 
'''Note:''' ''Only those with a 2nd indicator of 2 are MESH''

===Ignore or remove without processing===
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.

Most libraries in which the MESH are not used and are not causing any problems for patrons choose to '''ignore''' these headings.

Alternatively, you can choose to '''remove without processing''' any MESH that MARS 2.0 encounters during processing.

==Databases and Search Order==
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:
*MESH Authority File
*LC Authority File

===Search MeSH authority file only===
[[Image:a3-8b.png]] 
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'''.

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

After the matching is completed, all remaining MESH (i.e., those that did not match a heading in MESH) are '''retained''' in the records.

===Search MeSH against LC only===
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: 
[[Image:a3-8c.png]] 
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'''.

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

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.

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


'''original bib medical heading''':
650 2 $a Neoplasms.

'''MARS 2.0 compares the heading against the LC Subjects file.'''
'''The heading would match a cross-reference (4XX) in LC''' sh 850138553''':'''
150 $a Tumors
450 $a Neoplasms

'''updated bib medical heading''':
650 0 $a Tumors.

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:


650 2 $a Neoplasms $x diagnosis.

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:


650 0 $a Tumors $x diagnosis.

===Search MeSH 1st, LC 2nd===
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'''.

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''': 
[[Image:a3-8d.png]] 
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).

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.

Changing the '''search order''' (LC=1, MESH=2) '''reverses the order''' in which headings are matched:


'''original bib medical heading''':
610 22 $a Johns Hopkins University. $b School of Medicine. $b Division of Medical Genetics.

'''matches LC''' n 85363832''':'''
110 2 $a Johns Hopkins University. $b Division of Medical Genetics.
410 2 $a Johns Hopkins University. $b School of Medicine. $b Division of Medical Genetics.

'''updated bib MESH''':
610 20 $a Johns Hopkins University. $b Division of Medical Genetics.

==Retain or Split Medical Subdivision Forms==
[[Image:a3-8e.png]] 
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):


'''original MESH bib heading''':
650 2 $a Ethics, Medical $x legislation

'''updated MESH bib headings''':
650 0 $a Ethics, Medical
655 7 $a Legislation $2 mesh

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.

===Faceted medical subdivision forms===
{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse;"
|- align="left"
| academic dissertations || eulogies || patient information handout
|- align="left"
| account books || festschrift || pharmacopoeias
|- align="left"
| addresses || fictional works || posters
|- align="left"
| advertisements || funeral sermons || practice guideline
|- align="left"
| almanacs || guideline || price lists
|- align="left"
| animation || herbals || programs
|- align="left"
| architectural drawings || instruction || prospectuses
|- align="left"
| book illustrations || lecture notes || retracted publication
|- align="left"
| bookplates || lectures || review literature
|- align="left"
| broadslides || legislation || review of reported cases
|- align="left"
| caricatures || letter || scientific integrity review
|- align="left"
| consensus development conference || meta*hy analysis || sermons
|- align="left"
| consensus development conference, nij || newspaper article || statistics
|- align="left"
| database || patient information handout || technical report
|- align="left"
| documentaries and factual films || ephemera || unedited footage
|}
<div style=clear:both></div> 

==MeSH Authority Control Numbers==
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:


'''MESH control number in 001 field only''':
001 D0206980D0009
150 $a Duodenoscopes $x adverse effects

'''MESH control number in 001 and 010 fields''':
001 D0206980D0009
010 $a D0206980D0009
150 $a Duodenoscopes $x adverse effects

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.7

2024-10-17T15:57:01Z

Casey: /* links */

==Step 3.7: Childrens Matching==
[[Image:a3-7.png]] 
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.

===Fields matched===
The following fields are matched against the Childrens: 
[[Image:3-8b.png]] 
'''Note:''' ''Only those with a 2nd indicator of '''1''' are Childrens Subjects''

===Ignore or remove without processing===
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.

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.

Alternatively, you may wish all Childrens subject headings with a 2nd indicator of '''1''' are removed from the bibliographic records.

==Databases and Search Order==
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:
*Childrens Subjects
*LC [Adult] Authority File

===Search Childrens authority file only===
[[Image:a3-7b.png]] 
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'''.

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

After the matching is completed, all remaining Childrens (i.e., those that did not match a heading in Childrens) are '''retained''' in the records.

===Search Childrens against LC adult only===
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: 
[[Image:a3-7c.png]] 
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'''.

For those headings that match a heading in LC Adult, the indicator is changed from '''1''' to '''0'''.

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

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.

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

===Search Childrens 1st, LC adult 2nd===
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'''.

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''': 
[[Image:a3-7d.png]] 
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).

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.

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.

Changing the '''search order''' (Adult 1st, Child 2nd) '''reverses the order''' in which headings are matched.

==Add Juvenile Form Subdivisions to Matched Headings==
[[Image:a3-7e.png]] 
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:


'''childrens heading''':
650 1 $a Rain forests.
650 1 $a Collies $v Fiction.

'''matched LC Adult with''' juvenile form subdivisions''' applied:'''
650 0 $a Rain forests $v Juvenile literature.
650 0 $a Collies $v Juvenile fiction.

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.

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.

===Juvenile rules===
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:
*008[33] = '''1''' : add '''$v Juvenile fiction'''
*008[33] = '''d''' : add '''$v Juvenile drama'''
*008[33] = '''h''' : add '''$v Juvenile humor'''
*008[33] = '''p''' : add '''$v Juvenile poetry'''

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.

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.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.6

2024-10-17T15:56:49Z

Casey: /* links */

==Step 3.6: Subdivision Updates==
[[Image:a3-6.png]] 
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.

==LC Standard Form==
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:


'''original form''':
650 0 $a English literature $x History and criticism $x Periodicals.

'''new form''':
650 0 $a English literature $x History and criticism $v Periodicals.

===Preservation===
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:


'''original heading''':
650 0 $a Slavs $v Folklore.

'''authority record''' sh2008111734''':'''
650 0 $a Slavs $x Folklore.

If you '''preserve existing $v''', the original $v will be retained even though the LC authority record codes '''Folklore''' as $x. The heading on the bibliographic record would be your original heading:


650 0 $a Slavs $v Folklore.

Similarly, if you '''preserve existing $x''', the original $x will be retained even though the LC authority record codes '''databases''' as $v. The heading on the bibliographic record would be your original heading:

'''original heading''':
650 0 $a Stocks $x Prices $x Databases.

'''authority record''' sh 87003018 ''':'''
650 0 $a Stocks $x Prices $v Databases.

===Update headings===
You can also elect to have all form subdivisions coded as $v:


'''original heading''':
650 0 $a Stocks $x Prices '''$x''' Databases.

'''authority record''' sh 87003018''':'''
650 0 $a Stocks $x Prices '''$x''' Databases.

'''In this example, you have chosen''' update $x subdivisions to $v '''regardless:'''
650 0 $a Stocks $x Prices $v Databases.

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:
*Part of a subject (6XX) heading
*The last subfield, or last pair of subfields, in a heading

Exceptions:
*Eligible subfields can be followed by geographic $z
*Eligible subfields can be followed by $x containing a language

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.

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.

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

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.

In this example, both '''gazetteers''' and '''bibliography''' can be form subdivisions:


'''original heading''':
651 0 $a France $x Gazetteers $x Bibliography.

The combination of these two $x subdivisions, however, is not an authorized form subdivision, so only the final subdivision would be recoded as $v:


651 0 $a France $x Gazetteers $v Bibliography.

====Special Exception====
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:


'''original heading''':
650 0 $a English language $x Dictionaries.

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:


'''LC subject authority''':
001 sh 85043513
150 $a English language $v Dictionaries

Due to our NACO normalization routines, both of these headings would normalize to this:


ENGLISH LANGUAGE $ DICTIONARIES

Now both headings match and your original heading is updated to this:


'''updated heading''':
650 0 $a English language $v Dictionaries.

When you leave '''Update $x subdivisions to $v''' unchecked in the profile, this possibility of being flipped based on an authority match still exists.

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

==Authority Records==
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.

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.

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:


'''bib heading (cartographic material is''' secondary'''):'''
651 0 $a United States $x Maps $x Early works to 1800.

'''bib heading (work''' containing''' actual maps or reproductions):'''
651 0 $a United States $v Maps $v Early works to 1800.

'''authority''' sh 86006684''' (valid for''' both forms''' listed above):'''
151 $a United States $x Maps $x Early works to 1800

'''bib heading''' (work about''' various collections of manuscripts):'''
650 0 $a Manuscripts $x Collections.

'''bib heading (work''' containing''' a collection of manuscripts):'''
650 0 $a Manuscripts $v Collections.

'''authority''' sh 85080674''' (valid for both forms listed above):'''
150 $a Manuscripts $v Collections

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.5

2024-10-17T15:56:38Z

Casey: /* links */

==Step 3.5: Series Processing==
[[Image:a3-5.png]] 
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.

===Traced vs untraced===
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.

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.

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

Series are treated as '''traced''' if:
*LC authority record has field 645 $a '''t'''
**'''OR'''
*008[12] = '''a''' or '''b''' or '''z'''

Series are treated as '''untraced''' if:
*LC authority match does not have field 645 $a '''t'''
**'''AND'''
*008[12] = '''c'''

===Current Library of Congress policy===
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''':


'''bib series headings''':
490 1 $a Press release
810 0 $a Press release (United States. Mission to the United Nations) ;$v no. 4353.

'''no authority match is available''':
490 0 $a Press release
810 0 removed from record

'''or, available authority match is untraced''':
490 0 $a Press release
810 0 removed from record

MARS 2.0 programs can also '''retain unmatched 8XX''' fields if desired.

===Current standard series processing: post July 2008===
MARS 2.0 adheres to the June 2008 MARBI announcment regarding series processing:

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

Thus, standard MARS 2.0 series processing is to convert all '''4XX/8XX''' pairs to either '''traced''' 490-1/8XX or '''untraced''' 490-0.

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.

===400/410/411 series statements===
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'''.

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

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:


'''original headings''':
100 1 $a Strong, Anna Louise, $d 1885-1970.
400 11 $a Her. $t Letters from China, $v v. 2

'''updated headings''':
100 1 $a Strong, Anna Louise, $d 1885-1970.
490 1 $a Letters from China, $v v. 2
800 1 $a Strong, Anna Louise, $d 1885-1970 $t Letters from China ;$v v. 2.

'''original headings''':
490 1 $a Emma Lord mystery
800 1 $a Daheim, Mary. $t Emma Lord mystery.

'''updated heading''':
490 0 $a Emma Lord mystery

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.

==Main Entry Represented by Pronoun==
Special pronoun processing routines are used whenever field 8XX is generated. There are two phases of the MARS 2.0 series note processing.

===4XX series note processing===
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:


'''original headings''':
110 11 $a Wisconsin. $b Legislature. $b Legislative Reference Bureau.
410 11 $a Its. $t Research bulletin, $v 78-RB-3

'''updated headings''':
110 11 $a Wisconsin. $b Legislature. $b Legislative Reference Bureau.
490 1 $a Its Research bulletin, $v 78-RB-3
810 1 $a Wisconsin. $b Legislature. $b Legislative Reference Bureau. $t Research bulletin ;$v 78-RB-3.

===Pronoun series processing===
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'''.

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

==Collapsed 490/830 to 440 series statements: pre July 2008==
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''').

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

If the LC authority record indicated the established form of a series heading was different than the form recorded in field 440:
*The field was retagged as '''490 series statement''' with 1st indicator '''1 series traced''' differently
*Field '''8XX series added entry''' was added containing the '''established form''' of the heading


'''original heading''':
440 4 $a Department of the Army pamphlet ;$v 27-50

'''updated headings''':
490 1 $a Department of the Army pamphlet ;$v 27-50
830 0 $a DA pam ;$v 27-50

===Initial article series note processing: pre July 2008===
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.

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.

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


'''original heading''':
440 4 $a The Rare book tapes. $n Series 1 ;$v 5

'''updated headings''':
490 1 $a The Rare book tapes. Series 1 ;$v 5
830 0 $a Rare book tapes. $n Series 1 ;$v 5.

'''original headings''':
490 1 $a Bulletin/Maine Agricultural Experiment Station : 1975-1977
810 2 $a Life Sciences and Agricultural Experiment Station. $t Bulletin.

'''authority record''':
130 0 $a Bulletin (Life Sciences and Agriculture Experiment)
410 2 $a Life Sciences and Agricultural Experiment Station. $t Bulletin.

'''updated headings''':
490 1 $a Bulletin/Maine Agricultural Experiment Station : 1975-1977
810 0 $a Bulletin (Life Sciences and Agriculture Experiment)

==Summary of 490/830 fields not reverted: post July 2008==
#Expand '''440''' to '''490-1/830''' pairs
#Match '''830''' during authority control
#If the 830 '''matches an untraced authority''' record (645 $a '''n'''), the '''490-1/830''' pair converts to a '''490-0'''
#If the 830 '''does not match''' an authority record, the '''490-1/830 remains''' in the record
#If a '''match is found''', the '''490-1/830''' pair '''remains''' in the record

==Summary of 490/830 fields reverted to 440: pre July 2008==
#Expand '''440''' to '''490-1/830''' pairs
#Match '''830''' during authority control
#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'''
#After '''matching''', if the '''490-1''' and '''830''' are '''identical''', they are '''reverted''' back to a '''440'''
#If they '''differ''', the '''490-1/830 pair remains'''

==490-0 Series Statements (Series Not Traced)==
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.

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

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'''):


'''original heading''':
490 0 $a American Paper Institute instrumentation program report

'''authority record''':
130 0 $a American Paper Institute instrumentation program report
645 $a n

'''updated heading (no change'''):'''
490 0 $a American Paper Institute instrumentation program report

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'''):


'''original heading''':
490 0 $a Campbell County history and genealogy

'''authority record''':
100 1 $a Hartman, Margaret Stregel. $t Campbell County history & genealogy
430 0 $a Campbell County history and genealogy
645 $a t

'''updated headings''':
490 1 $a Campbell County history and genealogy
800 1 $a Hartman, Margaret Stregel. $t Campbell County history & genealogy.

==Copy All Series Processing==
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:
*Field 800/810/811 '''series added entry''' is created for each pre-AACR2 field 400/410/411 '''series statement/added entry'''
*Field 830 '''series added entry''' is created for each field 440 '''series statement/added entry'''
*Field 830 '''series added entry''' is created for each field 490-0 '''series statement, series not traced'''
*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

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.

'''Note''': ''Please check with your local system vendor before selecting the Copy All option.''

==Custom Series Processing==
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.

==Series-like phrases==
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.

You may opt to turn on the "series-like phrase" option which will default to the following:
The 1XX of the authority record will be added as a quoted 500 note.
The 490/8XX will be removed
The authority record will be added to your authmaster

We can retain the 490/8XX if desired as well as NOT add the authority record to the authmaster if that is preferred.

'''To select the "series-like phrase" option, please make mention in section 3-14 of the online Authority Control profile.'''

==Volume information==
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.

'''To select the this option, please make mention in section 3-14 of the online Authority Control profile.'''

==Publisher verification==
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'''.

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

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

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.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.4

2024-10-17T15:56:25Z

Casey: /* links */

==Step 3.4: Split Headings==
[[Image:a3-4.png]] 
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:

'''bib subject heading''':
650 0 $a Nurses and nursing $x Effect of managed care on.

'''replaced by two split headings''':
650 0 $a Nurses $x Effect of managed care on.
650 0 $a Nursing $x Effect of managed care on.

Subfield '''$a''' matches obsolete forms of the heading (4XX fields) in 2 authority records, '''sh 85093349''' Nurses and '''sh 85093362''' Nursing. If a library elected to have split headings replaced by all new headings the bibliographic heading would be replaced by the 2 headings above.

Additional examples:

'''bib subject heading''':
650 0 $a New communities $z Massachusetts $z Boston Region.

'''replaced by two split headings''':
650 0 $a New towns $z Massachusetts $z Boston Region.
650 0 $a Planned communities $z Massachusetts $z Boston Region.


'''bib subject heading''':
610 20 $a Vsesoi︠u︡znai︠a︡ kommunisticheskai︠a︡ partii︠a︡ (bolʹshevikov) $x Purges.

'''replaced by two split headings''':
610 20 $a Vsesoi︠u︡znai︠a︡ kommunisticheskai︠a︡ partii︠a︡ (bolʹshevikov) (1991- ) $x Purges.
610 20 $a Vsesoi︠u︡znai︠a︡ kommunisticheskai︠a︡ partii︠a︡ (bolʹshevikov) (1925-1952) $x Purges

Subfield '''$a''' matches variant forms of the heading (4XX fields) in multiple authority records. These variant forms are added to the MARC record.

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.

Therefore, most libraries choose to have all split headings inserted in the bibliographic record.

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

===Split heading reports available===
For libraries choosing to insert split headings into the bibliographic record, a '''Split Headings''' report is generated (see Step 5.2, R31).

If obsolete headings should be retained, a '''Split Headings - Headings Left Unchanged''' report is generated instead (see Step 5.2, R17).

===Duplicate headings===
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.

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.

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.

===Unmatched headings===
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.

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

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.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.3

2024-10-17T15:56:13Z

Casey: /* links */

==Step 3.3: Partial Matches==
[[Image:a3-3.png]] 
===Flip 2nd indicators===
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.

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:


'''bib subject heading''':
650 4 $a English language $x Foreign elements $x Greek $v Textbooks.

'''closest match''' sh 85043541''':'''
150 $a English language $x Foreign elements

'''2nd indicator changed to''' 0''' for partial match:'''
650 0 $a English language $x Foreign elements $x Greek $v Textbooks.

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

===Example Table===
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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|align = "center" bgcolor = "#A6A6A6" width="12%"| 
|align = "center" bgcolor = "#A6A6A6" width="12%" colspan = "2"|'''Change Indicator on Match Rules'''
|align = "center" bgcolor = "#A6A6A6" width="12%" colspan = "2"|'''Partial Subject Flip Rules'''
|-
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''Match Result'''
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''Flip 2nd ind on match'''
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''No Flip 2nd ind on match'''
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''Allow Partial Subject Flips'''
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''Do not allow partial flips'''

|-
|'''Full Match'''
|Will Flip
|Will Not Flip
|Will Flip
|Will Flip

|-
|'''Partial Match'''
|Depends on Partial Flip rule
|Will Not Flip
|Will Flip
|Will Not Flip

|-
|'''Non Match'''
|Will Not Flip
|Will Not Flip
|Will Not Flip
|Will Not Flip

|}

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.2

2024-10-17T15:56:00Z

Casey: /* links */

==Step 3.2: Tag Flipping==
[[File:ac-3-2.png]] 
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:


'''bib headings''':
650 0 $a Italy (Rome)
650 0 $a European Union.

'''match as tag (flip)''':
651 0 $a Italy (Rome)
610 20 $a European Union.*

''*the European Union flip will only happen if the optional 650-flip is added''

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

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.

===Tag flipping rules===
If Tag Flipping is marked, then the following rules apply:
#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'''
#If '''$a''' contains a '''single word''' or '''initials''', no flip is allowed between X00 and X10
#Only '''subjects''' can flip to '''X50''' or '''X51''' based on an authority match:
##If the bib tag is 600 or 611, flip to a 610
##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
##If the bib tag is 610 and it contains other subfields than above, it will not be allowed to flip
#Tags X50 and X51 '''can''' flip between each other
#Tags can '''never*''' flip from X51, '''except''' X50
#Tags can '''never*''' flip to or from 655
#Tags can '''never*''' flip to or from X30 '''unless''' the authority record causes the tag flip
#Tags will '''never*''' flip from matches to 18X subdivision authority records
#Any flips not explicitly included above are allowed: X00, X10, X11 can flip between themselves

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

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

''*Never say never in these rules, as we can also create a custom match rule that would allow these particular flips, upon request.''

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.1

2024-10-17T15:55:45Z

Casey: /* links */

==Step 3.1: Generic Name Headings==
[[Image:a3-1.png]] 

===Matching===
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:


'''generic bib heading''':
100 10 $a Campbell, John

'''finds match to authority below''':
001 n2001026796
100 10 $a Campbell, John, $d 1826-1910
400 10 $a Campbell, John

'''generic bib heading changes to''':
100 10 $a Campbell, John, $d 1826-1910

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.

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

===Normalization and matching===
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).

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.

Normalization of a name heading is as follows: 

'''original heading''':
700 $a Pinsent, John, $d 1922-

'''authority record''':
100 $a Pinsent, John, $d 1922-1995
400 $a Pinsent, John, $d 1922

'''normalized original''':
700 $ PINSENT, JOHN $ 1922

'''normalized authority''':
100 $ PINSENT, JOHN $ 1922 1995
400 $ PINSENT, JOHN $ 1922

'''updated heading''':
700 $a Pinsent, John, $d 1922-1995.

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.

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

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.

===Bibliographic text replaced===
When a heading matches a 1XX authorized heading or a 4XX unauthorized heading in an authority record, MARS 2.0 processing:
*Replaces the bibliographic heading text with the text from the 1XX field of the authority record
*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)

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.

==See From Tracings==
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):


'''original bib headings''':
650 0 $a Philippine American War, Philippines, 1899-1902.
651 0 $a Philippines $x History $y Insurrection, 1899-1901.
651 0 $a United States $x History $y Philippine Insurrection, 1899-1902.

The normalized headings from the bibliographic records are compared to the normalized authorized 1XX and the unauthorized 4XX authority record headings.


The headings above match headings contained in sh 85100792 - LC subject authority record:
001 sh 85100792
151 0 $a Philippines $x History $y Philippine American War, 1899-1902
450 0 $a Filipino American War, Philippines, 1899-1902
450 0 $a Philippine American War, Philippines, 1899-1902
450 0 $a Philippine Insurrection, Philippines, 1899-1902
451 0 $a Philippines $x History $y Insurrection, 1899-1901
451 0 $a United States $x History $y Philippine Insurrection, 1899-1902

The three unauthorized headings in the bibliographic record would all be replaced by the established form of the heading:
151 0 $a Philippines $x History $y Philippine American War, 1899-1902

MARS 2.0 then merges or deduplicates the three identical authority headings to form one heading:
651 0 $a Philippines $x History $y Philippine American War, 1899-1902

==Hierarchy==
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'''.

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.

Normalized headings are constructed for each level of hierarchy in the heading:

'''original bib heading''':
650 0 $a Electronic digital computers $x Programming $v Congresses.

'''levels of hierarchy for this heading''':
650 0 $a Electronic digital computers
650 0 $a Electronic digital computers $x Programming
650 0 $a Electronic digital computers $x Programming $v Congresses

'''partial match to 4XX heading in LC subject''' sh 85107310:
150 0 $a Computer programming
450 0 $a Electronic digital computers $x Programming

'''corrected form of heading in bib record (a partial match)''':
650 0 $a Computer programming $v Congresses.

===Constructing multiple levels of hierarchy===
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:


'''full heading''':
700 12 $a Freud, Sigmund, $d 1856-1939. $t Selections. $f 1990

'''highest level heading''':
700 12 $a Freud, Sigmund, $d 1856-1939

===Hierarchy record delivered to marc file===
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.

===Subfields representing highest level heading===
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:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | Subfield Codes Indicating Highest Level Heading
|-
| 100, 400, 600, 700, 800 || a b c d q
|-
| 110, 410, 610, 710, 810 || a b
|-
| 111, 411, 611, 711, 811 || a b
|-
| 130, 430, 630, 730, 830 || a d
|-
| 440 || a
|-
| 650 || a c d
|-
| 651 || a
|-
| 655 || a
|}
<div style=clear:both></div> 

==Name/Title Headings==
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:


'''name/title combined headings''':
600 10 $a Twain, Mark, $d 1835-1910. $t Innocents abroad.
710 1 $a Canada. $t Treaties, etc. $d 1992 Oct. 7.

===Name/title split and temporary headings===
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:


'''bib headings''':
100 0 $a Aristotle.
240 10 $a Works. $l English. $f 1984

'''changes to''':
100 0 $a Aristotle. $t Works

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.


The temporary MARS 2.0 autohrity heading would then match the correct LC authority record n 8242241:
100 0 $a Aristotle. $t Works. $l English. $f 1984
400 0 $a Aristotle. $t Complete works of Aristotle. $f 1984

===Name/title tracing===
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:

Aristotle - Complete works of Aristotle - 1984
''See'' Aristotle - Works - English - 1984

===Name/title hierarchy===
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.

==Usage Codes==
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:

008 [12] – Type of series
008 [14] – Main or added entry
008 [15] – Subject added entry
008 [16] – Series added entry

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

==Reference Records==
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.

==MARS 2.0 Auxiliary File==
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.

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:


'''bib heading''':
651 0 $a Husum-Schwesing (Germany : Concentration camp)

'''changes to''':
610 20 $a Husum-Schwesing (Concentration camp)

==VIAF Name/Title matching==
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 deselecting the option in section 3-1.

'''NOTE May 2024: As of right now, we're aware there are issues with bad data in the VIAF database, we're working on some work-arounds. Until those are in place we temporarily NOT recommending searching against VIAF as there may be mismatches. Proceed with caution if you do opt for this.'''

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.

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.

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.

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

If desired, optional report '''R24 - Generic Names Flipped''' can be returned to help you review these updated headings.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.7

2024-10-14T16:11:28Z

Casey: fixed a couple characters

==Step 2.7: Initial Articles & Indicators==
[[Image:rda2-1.png]] 
MARS 2.0 supports the standard practice of omitting most initial articles even if a nonfiling character indicator has been defined for the field.

Initial articles are retained, and the filing indicator correctly set, for the 245 Title Statement and 440 Series Statement/Title Added Entry fields.

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.

===Corporate heading initial article check===
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'''.

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

===245 & 440 fields===
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.

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.

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

If no other condition is satisfied, a blank Nonfiling Characters indicator is set to zero.

MARS 2.0 initial article processing is fully compliant with the February 20, 2003 Library of Congress change in counting non-filing characters.

Diacritics associated with the initial letter of the following word are no longer included in the filing indicator:

 245 05 $a Der öffentliche Dienst …
440 5 $a Los últimos alazapas ;$v 2

'''changes to''':
245 04 $a Der öffentliche Dienst …
440 4 $a Los últimos alazapas ;$v 2

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:

 245 05 $a [The Part of Pennsylvania that … townships].
245 15 $a The “other” person …

MARS 2.0 does '''not''' examine $p.

==Other Fields==
MARS 2.0 examines the beginning of each instance of these fields and subfields for initial articles: 
===Subfield $a===
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="center"
| 130 || 630 || 730 || 740 || 830
|- align="center"
| 210 || 211 || 212 || 214 || 222
|- align="center"
| 240 || 242 || 243 || 246 || 247
|}
<div style=clear:both></div> 

===Subfield $t===
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="center"
| 100 || 110 || 111
|- align="center"
| 400 || 410 || 411
|- align="center"
| 600 || 610 || 611
|- align="center"
| 700 || 710 || 711
|- align="center"
| 800 || 810 || 811
|}
<div style=clear:both></div> 

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.

If the initial word is an article:
*The word is deleted
*The first letter of the subsequent word is capitalized
*The filing indicator is reset to zero

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

MARS 2.0 uses a different process if:
*The filing indicator is a zero or a blank
*No filing indicator has been defined for the field
*The subfield being examined is $t
*If the subfield begins with '''The''':
*The initial article is deleted
*The first letter of the subsequent word is capitalized
*The filing indicator (if defined) is reset to zero

Additionally, if the first word is '''A''' or '''An''', it is included in the '''Possible Leading Articles Report''' (see Step 5.2, R14).

==Counting Non-Filing Characters==
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.

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

This practice is best illustrated by the following examples.

 '''Old practice''':
245 13 $a L’été …
245 15 $a Los últimos …
245 05 $a Der öffentliche Dienst …
245 15 $a al-‘Alam …

'''New practice''':
245 12 $a L’été …
245 14 $a Los últimos …
245 04 $a Der öffentliche Dienst …
245 14 $a al-‘Alam …

Other helpful examples with and without initial articles (these do '''not''' reflect a change in practice):

 245 04 $a al-‘Arabiyah …
245 14 $a Hē Monē …
245 12 $a L’enfant criminal.
245 05 $a [The Part of Pennsylvania that … townships].
245 15 $a The “other” person …
245 10 $a [Diary] …
245 10 $a “Full steam ahead!” …

'''Note''': ''The following characters can be considered candidates as “the first filing character”:''
*Latin letters
*Arabic numbers
*Super or subscript numbers
*Æ – AE digraph
*Œ – OE digraph
*Ð – Crossed d
*ð – Eth
*i – Turkish i
*L – Polish l
*l – Script l
*O – Hooked o
*U – Hooked u
*Ø – Slashed o
*Þ – Icelandic thorn
*Hatch mark (#)
*& – Ampersand
*+ – Plus sign

==MARS 2.0 Initial Article Table==
The table shown lists each initial article, and the associated filing indicator, by language.

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.

'''MARS 2.0 Initial Article Table''' 
[[Image:28a.png]] 

'''MARS 2.0 Initial Article Table''' 
[[Image:28b.png]] 

'''MARS 2.0 Initial Article Table''' 
[[Image:28c.png]] 

'''MARS 2.0 Initial Article Table''' 
[[Image:28d.png]] 

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.6

2024-10-14T16:05:10Z

Casey: grammar fix

==Step 2.6: Special Conversions & Additions==
[[Image:rda2-1.png]] 
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:
*Add missing format data
**007
**245 $h (for AACR2 records, not RDA unless by request)
*Add missing subfield data
**017 $b
**032 $b
*Complex field conversions
**1XX Main-Entry-Is-Subject
**260 $d to 028 $a
**262 to 260
**300
**301 to 300
**305 to 300
**705 to 700
**715 to 710
**X11

Describe modifications to processing listed above. Provide a different default for the 007 field by listing specific values for each position.

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.

==Specific Fields==
===007 field===
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.

===1xx main-entry-is-subject===
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.

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

===245 $h added (medium-aacr2)===
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:
 245 10 $a Olympia town square /$c by Fred Smith.

'''changes to''':
245 10 $a Olympia town square $h [cartographic material] /$c by Fred Smith.
The following 245 $h GMDs are added based on the values indicated:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | 245 $h
! style="background:silver" align="center" | LDR Byte 06 Value
! style="background:silver" align="center" | 008 contains
|- align="center"
| [cartographic material] || e ''or'' f ||
|- align="center"
| [electronic resource] || m ||
|- align="center"
| [filmstrip] || g || byte 33 = f
|- align="center"
| [kit] || o ||
|- align="center"
| [microform] || a ''or'' t || byte 23 = a, b ''or'' c
|- align="center"
| [motion picture] || g || byte 33 = m
|- align="center"
| [slide] || g || byte 33 = s
|- align="center"
| [sound recording] || i ''or'' j ||
|- align="center"
| [transparency] || g || byte 33 = t
|- align="center"
| [vidoerecording] || g || byte 33 = v
|}
<div style=clear:both></div> 

To modify any values in this table, please indicate any changes in Step 2-7.

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

'''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]).

===017 field===
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.

===028 field===
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.

===032 field===
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.

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.

===260 field===
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''':
*'''028''' field with indicator values '''02''' is '''generated'''
*'''260 $d''' is moved to '''028 $a'''
*'''260 $b''' is copied to '''028 $b'''
*Punctuation in the 260 field is corrected, if necessary

The 260 field conversion option includes special routines that update the punctuation in all 260 fields in the bibliographic records being processed.

These punctuation routines update much of the punctuation in 260 fields to the current standards, including:
*<space> + <colon> before $b
*<comma> before $c
*Final field punctuation, as necessary

===262 field===
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').

If field 262 exists in a bibliographic record:
*262 is '''changed''' to 260
*Changes both indicators of new 260 to blank
*Retains these subfield codes: $a $b $c

For each 262 $k present:
*028 field with indicator values 02 is '''generated'''
*262 $k is '''moved''' to 028 $a subfield
*262 $b is '''copied''' to 028 $b

For each 262 $l (lowercase 'L') present:
*028 field with indicator values 12 '''generated'''
*262 $l is '''moved''' to 028 $a
*262 $b is '''copied''' to 028 $b

If the 262 field does not contain a $k or $l (lowecase 'L'), MARS 2.0 does the following additional conversions:
*262 $c is '''moved''' to 028 $a with indicator values 02
*262 $e is '''moved''' to 028 $b with indicator values 12
*262 $b is '''copied''' to 028 $b
*262 $d '''changed''' to $c code

After all conversions have been completed, the punctuation in the 028 fields and 260 field is updated.

===300 field===
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.

The following changes are made to the 300 $a:
*unp. or n.p. is '''changed''' to 1 v. (unpaged)
*Comma is added to page numbers if missing (e.g., 1264 p. becomes 1,264 p.)
*l. is '''changed''' to leaves
*approx. is '''changed''' to ca.
*p.l. is '''removed''' (e.g., 4 p.l., xv, 20 p. becomes xv, 20 p.)
*unnumbered is '''removed''' and brackets '''added''' (e.g., 48 unnumbered leaves becomes [48] leaves)
*[various pagings] is '''changed''' to (various pagings)

The following changes are made to the 300 $b:
*Illustrative matter is '''rearranged''' to be in correct order
*Obsolete illustrative matter is '''replaced''' with ill. (e.g., tables or fronts. becomes ill.)
*ill. is '''removed''' if followed by parenthetical illustrative matter (e.g., ill. (ports.) becomes ports.)
*illus. is '''changed''' to ill.

The following general changes are made to the 300:
*Various punctuation and spacing issues '''updated'''
*Adds ''';$c cm.''' if missing
*Adds '''300 $a p. ;$c cm.''' if record is monograph and 300 does not exist
*Numbered plate data in $b is '''moved''' to $a; if plate designation is not numbered, it is '''removed'''

 300 $a 22 l. :$b graphs.
300 $a unp. $b illus. $c 30 cm.

'''changes to:'''
300 $a 22 leaves :$b ill. ;$c cm.
300 $a 1 v. (unpaged) :$b ill. ;$c 30 cm.

===301 field===
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.

If field 301 exists in a bibliographic record, MARS 2.0:
*301 is '''changed''' to 300, with indicator values <blank><blank>
*Retains '''$a''' and '''$e''', with data
*$d is '''changed''' to $c
*$b $c $f data is '''combined''' into single $b

===305 field===
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.

If field 305 exists in a bibliographic record:
*305 is '''changed''' to 300, with indicator values <blank><blank>
*Retains '''$a''' and '''$c''', with data
*$b $d $e $f data is '''combined''' into single $b
*Updates the punctuation

For each $m present in the 305 field:
*305 $m is '''moved''' to 028 $a with indicator values 02
*260 $b is '''copied''' to 028 $b

 260 $a New York, N.Y. $b Columbia,$c 1959.
305 $a 1 sound disc (20 min.) :$b analog, 33 1/3 rpm, stereo. ;$c 12 in. $m STMA 8007

'''changes to''':
028 02 $a STMA 8007 $b Columbia
260 $a New York, N.Y. :$b Columbia, $c 1959.
300 $a 1 sound disc (20 min.) :$b analog, 33 1/3 rpm, stereo. ;$c 12 in.

For each $n present in the 305 field:
*305 $n is '''moved''' to 028 $a with indicator values 11
*260 $b is '''copied''' to 028 $b

 305 $a 1 sound disc (18 min.) $c 10 in. $b 74 rpm $d standard $e monaural $m STMA $n L27410X

'''changes to''':
028 02 $a STMA 3059
028 11 $a L27410X
300 $a 1 sound disc (18 min.) :$b 74 rpm, standard, monaural ;$c 10 in.

===705 & 715 field conversion===
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'''.

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

===X11 conference name headings===
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.

 '''Pre-AACR2'''
711 01 $a International Conference on the Chemistry and Uses of Molybdenum, $b 1st, $c University of Reading, $d 1973

'''changes to AACR2 form''':
711 0 $a International Conference on the Chemistry and Uses of Molybdenum $n (1st :$d 1973 :$c University of Reading)

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.1

2024-10-14T16:04:13Z

Casey: grammar fix

== Step 2.1: Validation ==
[[Image:rda2-1.png]] 

== Numeric Field Validation ==
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>

=== Historical fact ===
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.

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

== Pre-2001 LCCN ==
LCCN Structure A (2000 and earlier) numbers are formatted according to the following 6 divisions (separated by hyphens): 
 1 2 3 4 5 6
nb#-71-005810-#-/AC-/r86

#3-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''
#2 digits, usually the last 2 digits of the '''year'''
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits
#Blank '''space'''
#Optional variable length '''suffix''' and/or alphabetic identifier
#Optional '''revision date'''

Examples of LCCN Structure A (the character # represents a single space): 
 ###95156543# Displayed as: 95-156543
###94014580#/AC/r95 Displayed as: 94-14580/AC/r95
###79310919#//r86 Displayed as: 79-310919//r86
nb#71005810# Displayed as: nb71-5810

== Post-2000 LCCN ==
LCCN Structure B (2001 and later) numbers are formatted according to the following 3 divisions (separated by hyphens): 
 1 2 3
##-2005-256543

#2-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''
#4-digit '''year'''
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits

Examples of LCCN Structure B (the character # represents a single space): 
 ##2005256543 Displayed as: 2005-256543
##2010014580 Displayed as: 2010-14580
nb2005005810 Displayed as: nb2005-5810

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.

=== LCCN structure A corrections ===
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):
*If the first character of the LCCN is a number (no prefix is present), the programs insert 3 blanks (###) before the number:
 Original: 95-156543 Corrected to: ###95156543#

*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:
 Original: n95-156543 Corrected to: n##95156543#

*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:
 Original: nb95-156543 Corrected to: nb#95156543#

*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:
 Original: nb#9-156543 Corrected to: nb#09156543#
Original: nb#95-156543 Corrected to: nb#95156543#

*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:
 Original: nb#95-6543 Corrected to: nb#95006543#
Original: nb#95-56543 Corrected to: nb#95056543#

*If the LCCN contains a suffix, the suffix is removed in accordance with the revised LC standard for Structure A LCCNs:
 Original: nb#95-516543//r86 Corrected to: nb#95156543#

*If the LCCN does not end with a blank, MARS 2.0 programs insert a blank following the last digit:
 Original: nb#95-516543 Corrected to: nb#95156543#

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

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

*The following invalid LCCN prefixes are corrected to the valid format (# = blank):
 #a# -> a##
##a -> a##
#bc -> bc#
# -> ###
## -> ###

=== LCCN structure B corrections ===
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):
*If the first character of the LCCN is a number (no prefix is present), the programs insert 2 blanks before the number:
 Original: 2005-256543 Corrected to: ##2005256543

*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:
 Original: n2005-256543 Corrected to: n#2005256543
Original: nb2005-256543 Corrected to: nb2005256543

*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:
 Original: nb2005-6543 Corrected to: nb2005006543

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

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

*The following invalid LCCN prefixes are corrected to the valid format (# = blank):
 #a -> a#
#bc -> bc
# -> ##

== 020 Field ==
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:
*If there are 9 digits in the ISBN, a 0 (zero) is inserted before the first digit in the ISBN:
 Original: 873671008 Corrected to: 0873671008

*All hyphens are deleted:
 Original: 1-873671-008 Corrected to: 1873671008

*A lowercase x is converted to uppercase:
 Original: 187367100x Corrected to: 187367100X

*If ISBN is 13 digits, MARS 2.0 programs will verify that the first 3 digits are '''978'''.

*As an optional service, MARS 2.0 programs will correct the order of the ISBN (i.e. pairs of 13/10 and 13/10)

*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):
 Original: 1873671008 Corrected to: 9781873671000

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

=== Historical fact ===
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.

=== Ordering 020 fields ===
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: 
 ISBN-13: 978-1-873671-00-0
ISBN-10: 1-873671-008

=== Repeating 020 subfields ===
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: 
 020 $a 11111111 $a 22222222
Corrected to:
020 $a 11111111
020 $a 22222222

=== Binding information in 020 fields ===
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.

If the 020 field contains a $b and an 020 $a exists:
*$b delimiter and subfield code are deleted
*020 $b data is enclosed in parentheses
*A blank is inserted at the end of the immediately preceding 020 $a data
*020 $b data, enclosed in parentheses, is moved after the blank at the end of the 020 $a data
 Original: 020 $a 1873671008 $b pbk. Corrected to: 020 $a 1873671008 (pbk.)

=== 020 with missing $a ===
If the 020 field contains a $b and no 020 $a exists, the $b code will be changed to $c: 
 020 $b pbk.
Corrected to:
020 $c pbk.

=== 020 with multiple $c ===
If the 020 field contains multiple $c, each $c is placed in a separate 020 field: 
 020 $c 4.95 (lib. bdg.) $c 3.60 (pbk.)
Corrected to:
020 $c 4.95 (lib. bdg.)
020 $c 3.60 (pbk.)
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.

=== 020 with multiple $a and $c ===
MARS 2.0 programs correctly handle 020 fields with multiple $a and $c: 
 020 $a 11111111 $c 4.95 $a 22222222 $c 3.60 $c 8.97 $b pbk.
Corrected to:
020 $a 11111111 $c 4.95
020 $a 22222222 $c 3.60
020 $c 8.97 (pbk.)

== 022 Field ==
MARS 2.0 Update processing can validate 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): 
 1234-1234
1234-123X

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:
*If the ISSN has no hyphen, adds a hyphen between the fourth and fifth digits:
 Original: 12345678 Corrected to: 1234-5678

*Converts a lowercase '''x''' to uppercase:
 Original: 1234-567x Corrected to: 1234-567X

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

== 034 Field ==
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:
*Places each $a in a separate 034 field
*Changes each 034 field first indicator to value 1
 034 2_$a a $b 100000 $a a $b 120000
Corrected to:
034 1_$a a $b 100000
034 1_$a a $b 120000

=== Historical fact ===
First indicator value '''2''' became obsolete when field 034 was made repeatable in 1982. Older bibliographic records may still have first indicator value 2.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.1

2024-10-14T16:03:41Z

Casey: grammar fix

== Step 2.1: Validation ==
[[Image:rda2-1.png]] 

== Numeric Field Validation ==
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>

=== Historical fact ===
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.

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

== Pre-2001 LCCN ==
LCCN Structure A (2000 and earlier) numbers are formatted according to the following 6 divisions (separated by hyphens): 
 1 2 3 4 5 6
nb#-71-005810-#-/AC-/r86

#3-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''
#2 digits, usually the last 2 digits of the '''year'''
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits
#Blank '''space'''
#Optional variable length '''suffix''' and/or alphabetic identifier
#Optional '''revision date'''

Examples of LCCN Structure A (the character # represents a single space): 
 ###95156543# Displayed as: 95-156543
###94014580#/AC/r95 Displayed as: 94-14580/AC/r95
###79310919#//r86 Displayed as: 79-310919//r86
nb#71005810# Displayed as: nb71-5810

== Post-2000 LCCN ==
LCCN Structure B (2001 and later) numbers are formatted according to the following 3 divisions (separated by hyphens): 
 1 2 3
##-2005-256543

#2-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''
#4-digit '''year'''
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits

Examples of LCCN Structure B (the character # represents a single space): 
 ##2005256543 Displayed as: 2005-256543
##2010014580 Displayed as: 2010-14580
nb2005005810 Displayed as: nb2005-5810

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.

=== LCCN structure A corrections ===
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):
*If the first character of the LCCN is a number (no prefix is present), the programs insert 3 blanks (###) before the number:
 Original: 95-156543 Corrected to: ###95156543#

*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:
 Original: n95-156543 Corrected to: n##95156543#

*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:
 Original: nb95-156543 Corrected to: nb#95156543#

*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:
 Original: nb#9-156543 Corrected to: nb#09156543#
Original: nb#95-156543 Corrected to: nb#95156543#

*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:
 Original: nb#95-6543 Corrected to: nb#95006543#
Original: nb#95-56543 Corrected to: nb#95056543#

*If the LCCN contains a suffix, the suffix is removed in accordance with the revised LC standard for Structure A LCCNs:
 Original: nb#95-516543//r86 Corrected to: nb#95156543#

*If the LCCN does not end with a blank, MARS 2.0 programs insert a blank following the last digit:
 Original: nb#95-516543 Corrected to: nb#95156543#

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

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

*The following invalid LCCN prefixes are corrected to the valid format (# = blank):
 #a# -> a##
##a -> a##
#bc -> bc#
# -> ###
## -> ###

=== LCCN structure B corrections ===
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):
*If the first character of the LCCN is a number (no prefix is present), the programs insert 2 blanks before the number:
 Original: 2005-256543 Corrected to: ##2005256543

*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:
 Original: n2005-256543 Corrected to: n#2005256543
Original: nb2005-256543 Corrected to: nb2005256543

*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:
 Original: nb2005-6543 Corrected to: nb2005006543

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

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

*The following invalid LCCN prefixes are corrected to the valid format (# = blank):
 #a -> a#
#bc -> bc
# -> ##

== 020 Field ==
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:
*If there are 9 digits in the ISBN, a 0 (zero) is inserted before the first digit in the ISBN:
 Original: 873671008 Corrected to: 0873671008

*All hyphens are deleted:
 Original: 1-873671-008 Corrected to: 1873671008

*A lowercase x is converted to uppercase:
 Original: 187367100x Corrected to: 187367100X

*If ISBN is 13 digits, MARS 2.0 programs will verify that the first 3 digits are '''978'''.

*As an optional service, MARS 2.0 programs will correct the order of the ISBN (i.e. pairs of 13/10 and 13/10)

*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):
 Original: 1873671008 Corrected to: 9781873671000

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

=== Historical fact ===
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.

=== Ordering 020 fields ===
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: 
 ISBN-13: 978-1-873671-00-0
ISBN-10: 1-873671-008

=== Repeating 020 subfields ===
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: 
 020 $a 11111111 $a 22222222
Corrected to:
020 $a 11111111
020 $a 22222222

=== Binding information in 020 fields ===
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.

If the 020 field contains a $b and an 020 $a exists:
*$b delimiter and subfield code are deleted
*020 $b data is enclosed in parentheses
*A blank is inserted at the end of the immediately preceding 020 $a data
*020 $b data, enclosed in parentheses, is moved after the blank at the end of the 020 $a data
 Original: 020 $a 1873671008 $b pbk. Corrected to: 020 $a 1873671008 (pbk.)

=== 020 with missing $a ===
If the 020 field contains a $b and no 020 $a exists, the $b code will be changed to $c: 
 020 $b pbk.
Corrected to:
020 $c pbk.

=== 020 with multiple $c ===
If the 020 field contains multiple $c, each $c is placed in a separate 020 field: 
 020 $c 4.95 (lib. bdg.) $c 3.60 (pbk.)
Corrected to:
020 $c 4.95 (lib. bdg.)
020 $c 3.60 (pbk.)
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.

=== 020 with multiple $a and $c ===
MARS 2.0 programs correctly handle 020 fields with multiple $a and $c: 
 020 $a 11111111 $c 4.95 $a 22222222 $c 3.60 $c 8.97 $b pbk.
Corrected to:
020 $a 11111111 $c 4.95
020 $a 22222222 $c 3.60
020 $c 8.97 (pbk.)

== 022 Field ==
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): 
 1234-1234
1234-123X

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:
*If the ISSN has no hyphen, adds a hyphen between the fourth and fifth digits:
 Original: 12345678 Corrected to: 1234-5678

*Converts a lowercase '''x''' to uppercase:
 Original: 1234-567x Corrected to: 1234-567X

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

== 034 Field ==
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:
*Places each $a in a separate 034 field
*Changes each 034 field first indicator to value 1
 034 2_$a a $b 100000 $a a $b 120000
Corrected to:
034 1_$a a $b 100000
034 1_$a a $b 120000

=== Historical fact ===
First indicator value '''2''' became obsolete when field 034 was made repeatable in 1982. Older bibliographic records may still have first indicator value 2.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.12

2024-08-21T17:25:19Z

Casey:

==Step 3.12: Subject Term Conversions==
[[Image:A3-11new.jpg]] 
Over the years there has been growing interest in either supplementing existing LCSH vocabulary or replacing outdated/obsolete terminology. We offer a few different options to help meet your needs in term conversions.

===LCSH/LCGFT to FAST===
Some institutions find use in adding FAST headings when they are missing from a Bibliographic record so they are utilizing FAST as an additional faceted search option while others are moving towards an easier way to do subject analysis. Either way, often an automated approach is needed for addressing legacy items. Backstage has created a process that will take each LC term (LCSH or LCGFT) to add the appropriate FAST term (while retaining the original LC term). Options are available to omit the LCGFT match/addition.


'''original headings''':
650 0 $a Capitol Riot, Washington, D.C., 2021 $v Pictorial works.
650 0 $a Riots $z Washington (D.C.) $v Pictorial works.
650 0 $a Political violence $z Washington (D.C.) $v Pictorial works.

'''updated headings''':
650 0 $a Capitol Riot, Washington, D.C., 2021 $v Pictorial works.
650 0 $a Riots $z Washington (D.C.) $v Pictorial works.
650 0 $a Political violence $z Washington (D.C.) $v Pictorial works.
647 7 $a Capitol Riot $c (Washington, D.C. : $d 2021) $2 fast $0 (OCoLC)fst02032437
648 7 $a 2021 $2 fast
650 7 $a Political violence $2 fast $0 (OCoLC)fst01069902
650 7 $a Riots $2 fast $0 (OCoLC)fst01098069
651 7 $a Washington (D.C.) $2 fast $0 (OCoLC)fst01204505

===GSAFD to LCGFT===
The vocabulary for the Guidelines on Subject Access to Individual Works of Fiction, Drama, Etc. (GSAFD) predates the formation of LCGFT. As LCGFT became more widely used and accepted, the use of GSAFD waned and eventually the vocabulary was largely absorbed into LCGFT. We have the ability to convert legacy GSAFD terms into LCGFT where they exist. There are some instances where a conversion is not achievable since there is not a 1:1 correlation or there may not be a good LCGFT equivalent just yet. Reports are available to alert you to terms that we are unable to convert.

'''original headings''':
655 7 $a Mystery comic books, strips, etc. $2 gsafd
655 7 $a Medical drama (Films). $2 gsafd

'''Updated headings''':
655 7 $a Detective and mystery comics. $2 lcgft
655 7 $a Medical films (Motion pictures). $2 lcgft

===LCSH/LCGFT and MeSH to HOMOIT===
The Homosaurus vocabulary has been developed and maintained by virtue of multiple volunteers across the library world. Many institutions are now incorporating this vocabulary into new cataloging in order to give better description to their items where LCSAF and MeSH are unable to describe something in the current, preferred terminology. However, the issue of legacy data is still a problem, as there is not enough staff time to spend to manually assign subject terms. Backstage can assist with an automated crosswalk that was developed internally. The crosswalk will look for a list of terms that could appear in LCSH and will add the Homosaurus equivalent with a $2 homoit.

'''original headings''':
650 0 $a Black gay men.
650 0 $a Cruising (Sexual behavior).

'''updated headings''':
650 0 $a Black gay men.
650 0 $a Cruising (Sexual behavior).
650 7 $a Black gay men $2 homoit
650 7 $a Black LGBTQ+ people $2 homoit
650 7 $a Cruising (LGBTQ+ culture) $2 homoit
650 7 $a Sexual practices $2 homoit
650 7 $a Sex (Act) $2 homoit

'''All options available:'''
*Don't add Homosaurus if the same term is used in LCSH, but still add the Broader terms
*Don't add the Juvenile related $v
*Omit indicators _2 and _4 from the source fields from which to convert
*Omit ALL broader terms and add only the direct conversion as outlined in the crosswalk

Additionally, because LC often uses "Gays" and "Gay people" as an umbrella term for both Gay men and Lesbians, our crosswalk will add BOTH to your record because we are unable to determine which it should actually be. '''Report number R902 is available for this instance, if desired.'''

===Indigenous people===
In recent years there has been a push to alter terminology to essentially "Decolonize" the catalog. The goal is to remove terms assigned by non-Indigenous peoples to represent them. This is a larger effort that many different institutions are working on but as a starting point, Backstage will change "Indians of ..." subject headings to "Indigenous peoples $z ..." and remove the use of "Indians" in individual tribal/community names. Special handling of the Indigenous populations of Alaska and Canada are also included. The use of Backstage's locally created authority file will facilitate these changes and you will receive a copy of the associated authority records.

Some institutions are also opting to add additional terms such as "Native Americans" to broaden search capability for their patrons, so let us know if there are additional terms you'd like to add!

'''original headings''':
650 0 $a Art $x Indian influences.
650 0 $a Asto Indians.
650 0 $a Chilcotin Indians.
650 0 $a Indians of North America $x Boats $z Alaska.
650 0 $a Indians of North America $z Canada.
650 0 $a Indians of South America $x Missions.

'''Updated headings''':
650 7 $a Art $x Indigenous influences. $2 indig
650 7 $a Asto (South American people). $2 indig
650 7 $a Tsilhqot'in. $2 indig
650 7 $a Alaska Natives $x Boats. $2 indig
650 7 $a First Nations. $2 indig
650 7 $a Indigenous peoples $z South America $x Missions. $2 indig

You have the option of using the locally prescribed $2 above or instead using 2nd indicator 4, with no $2.

A full list of the terms being addressed can be found [https://docs.google.com/spreadsheets/d/1ZMg-yXkmUoVD79Mfg8lLBTzMz4Tccnhm/edit#gid=934320559 here]

===Undocumented immigrants===
Prior to LC's final decision to change "Illegal aliens" to "Noncitizens" plus "Illegal immigration" many institutions were opting to change "Illegal aliens" to "Undocumented immigrants". This local authority file will allow you to make this alternate change while still changing "Aliens" to "Noncitizens" as currently prescribed by LCSH.

===Enslaved Persons===
We are aware that there are efforts by the Library of Congress to begin addressing Enslaved Persons. Many of our clients, however, are still interested in making this change now. As such, as of November 2022 a new authority file for this term set is now available to begin making the change within your catalog. You can view the term list [https://docs.google.com/spreadsheets/d/1EXJLLEFb3UaOemigcffRngX15wf-GpVe8oADfukVqMg/edit#gid=0 here]

===Other potential changes===
We're trying to keep our pulse on other sets of terms that institutions are looking at changing. We're slowly compiling that list that come in as 1) custom requests from our clients, or 2) appear on the cataloginglab.org website. You can find suggested changes [https://docs.google.com/spreadsheets/d/1GmZYYspaeVa46C7jlG3fklXh1FOjuQ3U0YEn6gqau6g/edit#gid=0 here]. PLEASE NOTE that we would consider these "custom" changes to your catalog so you can alter what the "Preferred term" is for these. Please download the spreadsheet, make your changes, and supply us with the updated spreadsheet.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.12

2024-08-21T17:24:10Z

Casey: /* LCSH/LCGFT and MeSH to HOMOIT */

==Step 3.12: Subject Term Conversions==
[[Image:A3-11new.jpg]] 
Over the years there has been growing interest in either supplementing existing LCSH vocabulary or replacing outdated/obsolete terminology. We offer a few different options to help meet your needs in term conversions.

===LCSH/LCGFT to FAST===
Some institutions find use in adding FAST headings when they are missing from a Bibliographic record so they are utilizing FAST as an additional faceted search option while others are moving towards an easier way to do subject analysis. Either way, often an automated approach is needed for addressing legacy items. Backstage has created a process that will take each LC term (LCSH or LCGFT) to add the appropriate FAST term (while retaining the original LC term). Options are available to omit the LCGFT match/addition.


'''original headings''':
650 0 $a Capitol Riot, Washington, D.C., 2021 $v Pictorial works.
650 0 $a Riots $z Washington (D.C.) $v Pictorial works.
650 0 $a Political violence $z Washington (D.C.) $v Pictorial works.

'''updated headings''':
650 0 $a Capitol Riot, Washington, D.C., 2021 $v Pictorial works.
650 0 $a Riots $z Washington (D.C.) $v Pictorial works.
650 0 $a Political violence $z Washington (D.C.) $v Pictorial works.
647 7 $a Capitol Riot $c (Washington, D.C. : $d 2021) $2 fast $0 (OCoLC)fst02032437
648 7 $a 2021 $2 fast
650 7 $a Political violence $2 fast $0 (OCoLC)fst01069902
650 7 $a Riots $2 fast $0 (OCoLC)fst01098069
651 7 $a Washington (D.C.) $2 fast $0 (OCoLC)fst01204505

===GSAFD to LCGFT===
The vocabulary for the Guidelines on Subject Access to Individual Works of Fiction, Drama, Etc. (GSAFD) predates the formation of LCGFT. As LCGFT became more widely used and accepted, the use of GSAFD waned and eventually the vocabulary was largely absorbed into LCGFT. We have the ability to convert legacy GSAFD terms into LCGFT where they exist. There are some instances where a conversion is not achievable since there is not a 1:1 correlation or there may not be a good LCGFT equivalent just yet. Reports are available to alert you to terms that we are unable to convert.

'''original headings''':
655 7 $a Mystery comic books, strips, etc. $2 gsafd
655 7 $a Medical drama (Films). $2 gsafd

'''Updated headings''':
655 7 $a Detective and mystery comics. $2 lcgft
655 7 $a Medical films (Motion pictures). $2 lcgft

===LCSH/LCGFT and MeSH to HOMOIT===
The Homosaurus vocabulary has been developed and maintained by virtue of multiple volunteers across the library world. Many institutions are now incorporating this vocabulary into new cataloging in order to give better description to their items where LCSAF and MeSH are unable to describe something in the current, preferred terminology. However, the issue of legacy data is still a problem, as there is not enough staff time to spend to manually assign subject terms. Backstage can assist with an automated crosswalk that was developed internally. The crosswalk will look for a list of terms that could appear in LCSH and will add the Homosaurus equivalent with a $2 homoit.

'''original headings''':
650 0 $a Black gay men.
650 0 $a Cruising (Sexual behavior).

'''updated headings''':
650 0 $a Black gay men.
650 0 $a Cruising (Sexual behavior).
650 7 $a Black gay men $2 homoit
650 7 $a Black LGBTQ+ people $2 homoit
650 7 $a Cruising (LGBTQ+ culture) $2 homoit
650 7 $a Sexual practices $2 homoit
650 7 $a Sex (Act) $2 homoit

'''All options available:'''
*Don't add Homosaurus if the same term is used in LCSH, but still add the Broader terms
*Don't add the Juvenile related $v
*Omit indicators _2 and _4 from the source fields from which to convert
*Omit ALL broader terms and add only the direct conversion as outlined in the crosswalk

Additionally, because LC often uses "Gays" and "Gay people" as an umbrella term for both Gay men and Lesbians, our crosswalk will add BOTH to your record because we are unable to determine which it should actually be. '''Report number R902 is available for this instance, if desired.'''

===Indigenous people===
In recent years there has been a push to alter terminology to essentially "Decolonize" the catalog. The goal is to remove terms assigned by non-Indigenous peoples to represent them. This is a larger effort that many different institutions are working on but as a starting point, Backstage will change "Indians of ..." subject headings to "Indigenous peoples $z ..." and remove the use of "Indians" in individual tribal/community names. Special handling of the Indigenous populations of Alaska and Canada are also included. The use of Backstage's locally created authority file will facilitate these changes and you will receive a copy of the associated authority records.

Some institutions are also opting to add additional terms such as "Native Americans" to broaden search capability for their patrons, so let us know if there are additional terms you'd like to add!

'''original headings''':
650 0 $a Art $x Indian influences.
650 0 $a Asto Indians.
650 0 $a Chilcotin Indians.
650 0 $a Indians of North America $x Boats $z Alaska.
650 0 $a Indians of North America $z Canada.
650 0 $a Indians of South America $x Missions.

'''Updated headings''':
650 7 $a Art $x Indigenous influences. $2 indig
650 7 $a Asto (South American people). $2 indig
650 7 $a Tsilhqot'in. $2 indig
650 7 $a Alaska Natives $x Boats. $2 indig
650 7 $a First Nations. $2 indig
650 7 $a Indigenous peoples $z South America $x Missions. $2 indig

You have the option of using the locally prescribed $2 above or instead using 2nd indicator 4, with no $2.

A full list of the terms being addressed can be found [https://docs.google.com/spreadsheets/d/1ZMg-yXkmUoVD79Mfg8lLBTzMz4Tccnhm/edit#gid=934320559 here]

===Undocumented immigrants===
Prior to LC's final decision to change "Illegal aliens" to "Noncitizens" plus "Illegal immigration" many institutions were opting to change "Illegal aliens" to "Undocumented immigrants". This local authority file will allow you to make this alternate change while still changing "Aliens" to "Noncitizens" as currently prescribed by LCSH.

===Enslaved Persons===
We are aware that there are efforts by the Library of Congress to begin addressing Enslaved Persons. Many of our clients, however, are still interested in making this change now. As such, as of November 2022 a new authority file for this term set is now available to begin making the change within your catalog. You can view the term list [https://docs.google.com/spreadsheets/d/1EXJLLEFb3UaOemigcffRngX15wf-GpVe8oADfukVqMg/edit#gid=0 here]

===Other potential changes===
We're trying to keep our pulse on other sets of terms that institutions are looking at changing. We're slowly compiling that list that come in as 1) custom requests from our clients, or 2) appear on the cataloginglab.org website. You can find suggested changes [https://docs.google.com/spreadsheets/d/1GmZYYspaeVa46C7jlG3fklXh1FOjuQ3U0YEn6gqau6g/edit#gid=0 here]. PLEASE NOTE that we would consider these "custom" changes to your catalog so you can alter what the "Preferred term" is for these. Please download the spreadsheet, make your changes, and supply us with the updated spreadsheet.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.12

2024-06-18T17:24:41Z

Casey: /* Add $1 URIs to Access Points */

==Step 2.12: Identities Management==
[[Image:A2-12new.jpg]] 
MARS 2.0 offers multiple 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.

===Add $0 to Access Points===
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.

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.

Here is an example of a before/after record adding a matching authority identifier:

'''original record''':
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
650 #0 $a Anatomy, Artistic.
650 #2 $a Anatomy, Artistic.

'''updated record''':
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator $0 nr 99034050 
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
650 #0 $a Anatomy, Artistic. $0 sh 85004836 
650 #2 $a Anatomy, Artistic. $0 D000716 


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.

Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':

'''original record''':
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
650 #0 $a Anatomy, Artistic.
650 #2 $a Anatomy, Artistic.

'''updated record''':
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator $0 http://id.loc.gov/authorities/names/nr99034050
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
650 #0 $a Anatomy, Artistic. $0 http://id.loc.gov/authorities/subjects/sh85004836
650 #2 $a Anatomy, Artistic. $0 http://id.nlm.nih.gov/mesh/D000716


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.

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.

'''original record''':
100 1# $a Alderman, Naomi, $e author.
240 10 $a Power. $l Spanish

'''updated record''':
100 1# $a Alderman, Naomi, $e author. $0 http://id.loc.gov/authorities/names/n2006034931
240 10 $a Power. $l Spanish $0 http://id.loc.gov/authorities/names/no2018156991


We have two alternative options to this new standard for the 1XX/240. Please notify us if you would prefer either of these alternates.
1. Add name-only URI in the 1XX field; no URI to the 240
2. Add name/title URI to the 240 only; no URI to the 1XX

'''ILS Note:''' The TIND ILS requires a slightly different approach to placement of the $0 with the identifier. Instead of appearing at the end of the string, the $0 for TIND users will appear after the largest matching string. This means that you may have a $0 after a $a$x combination and a different $0 after a $z. This placement of the $0 ensures that global updates occur on the correct chuck of your Access Point when updated authority records are loaded into the system.

'''original record''':
100 1# $a Freccia Marino, $d 1503-1566.
240 10 $a De subfeudis baronum & investituris feudorum
245 10 $a Marini Frecciae, patricij Neapolitani militisque clariss. ciuitatis literae ... Commentarij feudales : $b in tres libros partiti.
650 #0 $a Feudal law $z Italy $z Naples (Kingdom).
650 #0 $a Feudal law $z Italy $z Sicily.

'''updated record''':
100 1# $a Freccia Marino, $d 1503-1566. $0 n 87890918 
240 10 $a De subfeudis baronum & investituris feudorum $0 n 87890919 
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
650 #0 $a Feudal law $0 sh 85047982 $z Italy $0 n 79021783 $z Naples (Kingdom).
650 #0 $a Feudal law $0 sh 85047982 $z Italy $0 n 79021783 $z Sicily.


===Add $4 to Access Points===
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.

Examples:
100 1_ $a Delaplanche, Chantal, $e author. $4 http://id.loc.gov/vocabulary/relators/aut
700 1_ $a Kirby, Luke. $4 act $4 http://id.loc.gov/vocabulary/relators/act

===Add $0 to non-Access Points===
With the continued conversations of moving beyond MARC to a linked data environment, the greater library community is continuing to explore other
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.
Examples:
043 ## $a n-us--- $0 http://id.loc.gov/vocabulary/geographicAreas/n-us
050 14 $a KF27 $b .E5525 2010b $0 http://id.loc.gov/authorities/classification/K
336 ## $a text $2 rdacontent $0 http://rdaregistry.info/termList/RDAContentType/1020
337 ## $a unmediated $2 rdamedia $0 http://rdaregistry.info/termList/RDAMediaType/1007
338 ## $a volume $2 rdacarrier $0 http://rdaregistry.info/termList/RDACarrierType/1049

340 ## $a plastic $2 rdamat $0 http://rdaregistry.info/termList/RDAMaterial/1029
340 ## $g polychrome $2 rdacc $0 http://rdaregistry.info/termList/RDAColourContent/1003
340 ## $a metal $2 rdamat $0 http://rdaregistry.info/termList/RDAMaterial/1022
344 ## $a digital $2 rdatr $0 http://rdaregistry.info/termList/typeRec/1002
344 ## $b optical $2 rdarm $0 http://rdaregistry.info/termList/recMedium/1001
344 ## $c 1.4 m/s
347 ## $b Blu-ray $d 1920 x 1080p $2 rda
347 ## $a video file $2 rdaft $0 http://rdaregistry.info/termList/fileType/1006

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.

===Add $1 URIs to Access Points===
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 WikiData, LC Agents, the Virtual International Authority File (VIAF), and the International Standard Name Identifier (ISNI).
Example:
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator. $1 http://id.loc.gov/rwo/agents/nr99034050
$1 https://www.wikidata.org/entity/Q987687 $1 http://viaf.org/viaf/64206515 $1 http://isni.org/isni/0000000122809802

===Add URIs to Authority Records===
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.

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

Here is an example of an authority record delivered with both 024 and 92X fields populated:

001 ## no2001000753
024 7# $a no2001000753 $2 lccn
024 7# $a 23238834 $2 viaf
024 7# $a 0000000116075005 $2 isni
100 1# $a Volkmann, Hans
920 ## $a http://id.loc.gov/authorities/names/no2001000753
921 ## $a http://viaf.org/viaf/23238834
922 ## $a http://isni.org/isni/0000000116075005


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.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 2.12

2024-06-18T17:24:03Z

Casey: /* Add $1 URIs to Access Points */

==Step 2.12: Identities Management==
[[Image:A2-12new.jpg]] 
MARS 2.0 offers multiple 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.

===Add $0 to Access Points===
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.

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.

Here is an example of a before/after record adding a matching authority identifier:

'''original record''':
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
650 #0 $a Anatomy, Artistic.
650 #2 $a Anatomy, Artistic.

'''updated record''':
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator $0 nr 99034050 
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
650 #0 $a Anatomy, Artistic. $0 sh 85004836 
650 #2 $a Anatomy, Artistic. $0 D000716 


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.

Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':

'''original record''':
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
650 #0 $a Anatomy, Artistic.
650 #2 $a Anatomy, Artistic.

'''updated record''':
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator $0 http://id.loc.gov/authorities/names/nr99034050
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
650 #0 $a Anatomy, Artistic. $0 http://id.loc.gov/authorities/subjects/sh85004836
650 #2 $a Anatomy, Artistic. $0 http://id.nlm.nih.gov/mesh/D000716


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.

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.

'''original record''':
100 1# $a Alderman, Naomi, $e author.
240 10 $a Power. $l Spanish

'''updated record''':
100 1# $a Alderman, Naomi, $e author. $0 http://id.loc.gov/authorities/names/n2006034931
240 10 $a Power. $l Spanish $0 http://id.loc.gov/authorities/names/no2018156991


We have two alternative options to this new standard for the 1XX/240. Please notify us if you would prefer either of these alternates.
1. Add name-only URI in the 1XX field; no URI to the 240
2. Add name/title URI to the 240 only; no URI to the 1XX

'''ILS Note:''' The TIND ILS requires a slightly different approach to placement of the $0 with the identifier. Instead of appearing at the end of the string, the $0 for TIND users will appear after the largest matching string. This means that you may have a $0 after a $a$x combination and a different $0 after a $z. This placement of the $0 ensures that global updates occur on the correct chuck of your Access Point when updated authority records are loaded into the system.

'''original record''':
100 1# $a Freccia Marino, $d 1503-1566.
240 10 $a De subfeudis baronum & investituris feudorum
245 10 $a Marini Frecciae, patricij Neapolitani militisque clariss. ciuitatis literae ... Commentarij feudales : $b in tres libros partiti.
650 #0 $a Feudal law $z Italy $z Naples (Kingdom).
650 #0 $a Feudal law $z Italy $z Sicily.

'''updated record''':
100 1# $a Freccia Marino, $d 1503-1566. $0 n 87890918 
240 10 $a De subfeudis baronum & investituris feudorum $0 n 87890919 
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.
650 #0 $a Feudal law $0 sh 85047982 $z Italy $0 n 79021783 $z Naples (Kingdom).
650 #0 $a Feudal law $0 sh 85047982 $z Italy $0 n 79021783 $z Sicily.


===Add $4 to Access Points===
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.

Examples:
100 1_ $a Delaplanche, Chantal, $e author. $4 http://id.loc.gov/vocabulary/relators/aut
700 1_ $a Kirby, Luke. $4 act $4 http://id.loc.gov/vocabulary/relators/act

===Add $0 to non-Access Points===
With the continued conversations of moving beyond MARC to a linked data environment, the greater library community is continuing to explore other
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.
Examples:
043 ## $a n-us--- $0 http://id.loc.gov/vocabulary/geographicAreas/n-us
050 14 $a KF27 $b .E5525 2010b $0 http://id.loc.gov/authorities/classification/K
336 ## $a text $2 rdacontent $0 http://rdaregistry.info/termList/RDAContentType/1020
337 ## $a unmediated $2 rdamedia $0 http://rdaregistry.info/termList/RDAMediaType/1007
338 ## $a volume $2 rdacarrier $0 http://rdaregistry.info/termList/RDACarrierType/1049

340 ## $a plastic $2 rdamat $0 http://rdaregistry.info/termList/RDAMaterial/1029
340 ## $g polychrome $2 rdacc $0 http://rdaregistry.info/termList/RDAColourContent/1003
340 ## $a metal $2 rdamat $0 http://rdaregistry.info/termList/RDAMaterial/1022
344 ## $a digital $2 rdatr $0 http://rdaregistry.info/termList/typeRec/1002
344 ## $b optical $2 rdarm $0 http://rdaregistry.info/termList/recMedium/1001
344 ## $c 1.4 m/s
347 ## $b Blu-ray $d 1920 x 1080p $2 rda
347 ## $a video file $2 rdaft $0 http://rdaregistry.info/termList/fileType/1006

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.

===Add $1 URIs to Access Points===
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 WikiData, LC Agents, the Virtual International Authority File (VIAF), and the International Standard Name Identifier (ISNI).
Example:
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator. $1 http://id.loc.gov/rwo/agents/nr99034050 $1 https://www.wikidata.org/entity/Q987687 $1 http://viaf.org/viaf/64206515 $1 http://isni.org/isni/0000000122809802

===Add URIs to Authority Records===
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.

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

Here is an example of an authority record delivered with both 024 and 92X fields populated:

001 ## no2001000753
024 7# $a no2001000753 $2 lccn
024 7# $a 23238834 $2 viaf
024 7# $a 0000000116075005 $2 isni
100 1# $a Volkmann, Hans
920 ## $a http://id.loc.gov/authorities/names/no2001000753
921 ## $a http://viaf.org/viaf/23238834
922 ## $a http://isni.org/isni/0000000116075005


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.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.1

2024-05-28T22:20:42Z

Casey: /* VIAF Name/Title matching */

==Step 3.1: Generic Name Headings==
[[Image:a3-1.png]] 

===Matching===
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:


'''generic bib heading''':
100 10 $a Campbell, John

'''finds match to authority below''':
001 n2001026796
100 10 $a Campbell, John, $d 1826-1910
400 10 $a Campbell, John

'''generic bib heading changes to''':
100 10 $a Campbell, John, $d 1826-1910

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.

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

===Normalization and matching===
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).

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.

Normalization of a name heading is as follows: 

'''original heading''':
700 $a Pinsent, John, $d 1922-

'''authority record''':
100 $a Pinsent, John, $d 1922-1995
400 $a Pinsent, John, $d 1922

'''normalized original''':
700 $ PINSENT, JOHN $ 1922

'''normalized authority''':
100 $ PINSENT, JOHN $ 1922 1995
400 $ PINSENT, JOHN $ 1922

'''updated heading''':
700 $a Pinsent, John, $d 1922-1995.

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.

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

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.

===Bibliographic text replaced===
When a heading matches a 1XX authorized heading or a 4XX unauthorized heading in an authority record, MARS 2.0 processing:
*Replaces the bibliographic heading text with the text from the 1XX field of the authority record
*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)

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.

==See From Tracings==
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):


'''original bib headings''':
650 0 $a Philippine American War, Philippines, 1899-1902.
651 0 $a Philippines $x History $y Insurrection, 1899-1901.
651 0 $a United States $x History $y Philippine Insurrection, 1899-1902.

The normalized headings from the bibliographic records are compared to the normalized authorized 1XX and the unauthorized 4XX authority record headings.


The headings above match headings contained in sh 85100792 - LC subject authority record:
001 sh 85100792
151 0 $a Philippines $x History $y Philippine American War, 1899-1902
450 0 $a Filipino American War, Philippines, 1899-1902
450 0 $a Philippine American War, Philippines, 1899-1902
450 0 $a Philippine Insurrection, Philippines, 1899-1902
451 0 $a Philippines $x History $y Insurrection, 1899-1901
451 0 $a United States $x History $y Philippine Insurrection, 1899-1902

The three unauthorized headings in the bibliographic record would all be replaced by the established form of the heading:
151 0 $a Philippines $x History $y Philippine American War, 1899-1902

MARS 2.0 then merges or deduplicates the three identical authority headings to form one heading:
651 0 $a Philippines $x History $y Philippine American War, 1899-1902

==Hierarchy==
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'''.

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.

Normalized headings are constructed for each level of hierarchy in the heading:

'''original bib heading''':
650 0 $a Electronic digital computers $x Programming $v Congresses.

'''levels of hierarchy for this heading''':
650 0 $a Electronic digital computers
650 0 $a Electronic digital computers $x Programming
650 0 $a Electronic digital computers $x Programming $v Congresses

'''partial match to 4XX heading in LC subject''' sh 85107310:
150 0 $a Computer programming
450 0 $a Electronic digital computers $x Programming

'''corrected form of heading in bib record (a partial match)''':
650 0 $a Computer programming $v Congresses.

===Constructing multiple levels of hierarchy===
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:


'''full heading''':
700 12 $a Freud, Sigmund, $d 1856-1939. $t Selections. $f 1990

'''highest level heading''':
700 12 $a Freud, Sigmund, $d 1856-1939

===Hierarchy record delivered to marc file===
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.

===Subfields representing highest level heading===
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:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" align="center" | Subfield Codes Indicating Highest Level Heading
|-
| 100, 400, 600, 700, 800 || a b c d q
|-
| 110, 410, 610, 710, 810 || a b
|-
| 111, 411, 611, 711, 811 || a b
|-
| 130, 430, 630, 730, 830 || a d
|-
| 440 || a
|-
| 650 || a c d
|-
| 651 || a
|-
| 655 || a
|}
<div style=clear:both></div> 

==Name/Title Headings==
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:


'''name/title combined headings''':
600 10 $a Twain, Mark, $d 1835-1910. $t Innocents abroad.
710 1 $a Canada. $t Treaties, etc. $d 1992 Oct. 7.

===Name/title split and temporary headings===
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:


'''bib headings''':
100 0 $a Aristotle.
240 10 $a Works. $l English. $f 1984

'''changes to''':
100 0 $a Aristotle. $t Works

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.


The temporary MARS 2.0 autohrity heading would then match the correct LC authority record n 8242241:
100 0 $a Aristotle. $t Works. $l English. $f 1984
400 0 $a Aristotle. $t Complete works of Aristotle. $f 1984

===Name/title tracing===
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:

Aristotle - Complete works of Aristotle - 1984
''See'' Aristotle - Works - English - 1984

===Name/title hierarchy===
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.

==Usage Codes==
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:

008 [12] – Type of series
008 [14] – Main or added entry
008 [15] – Subject added entry
008 [16] – Series added entry

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

==Reference Records==
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.

==MARS 2.0 Auxiliary File==
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.

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:


'''bib heading''':
651 0 $a Husum-Schwesing (Germany : Concentration camp)

'''changes to''':
610 20 $a Husum-Schwesing (Concentration camp)

==VIAF Name/Title matching==
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 deselecting the option in section 3-1.

'''NOTE May 2024: As of right now, we're aware there are issues with bad data in the VIAF database, we're working on some work-arounds. Until those are in place we temporarily NOT recommending searching against VIAF as there may be mismatches. Proceed with caution if you do opt for this.'''

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.

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.

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.

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

If desired, optional report '''R24 - Generic Names Flipped''' can be returned to help you review these updated headings.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 4.4

2024-05-28T20:05:21Z

Casey: /* Step 4.4: Authority Segmentation by Usage */

==Step 4.4: Authority Segmentation by Usage==
[[Image:a4-4.png]] 
MARS 2.0 can distribute authority records in single- or multiple-file combinations. The number of files that are used to distribute your authority records should '''mirror''' the setup of authority indexes in your system.

If all authority records in the ILS are in a single file, regardless of whether a record links to a main/added entry heading or a subject heading, all files can be '''combined'''.

If the local authority file is divided into multiple files based on heading usage within bibliographic records, files should be '''separated''' to mirror your ILS.

The following table shows the distribution of authority records by authority tag and bibliographic usage:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Files
! style="background:silver" | Authority Tags
! style="background:silver" | Bibliographic Usage
! style="background:silver" | Authority Usage
|-
| Name || 100, 110, 111 || 1XX*, 7XX* || name
|-
| Subject || 100, 110, 111, 150, 151 || 6XX* (excludes 655) || subject
|-
| Series || 130 || 4XX*, 8XX* || series
|-
| Title || 100, 110, 111 || 130, 440, 630, 730, 830 || name.title, subject.title, series.title
|-
| Genre || 155 || 655 || genre
|}
<div style=clear:both></div>
''*excludes bib 130, 440, 630, 730, 830 for these entries with asterisk''

It may be that your ILS requires certain combinations in order to load the indexes properly. MARS 2.0 can combine or separate the usage files in whatever method is desired.

For instance, if your ILS requires Subjects be loaded separately, MARS 2.0 will send you one file with '''Subjects''' (which includes Genre) and one file with '''Names''' (which contains the combined authorities for all Series and Title unless otherwise specified).

'''NOTE: Polaris, CARL, Koha, Evergreen, Sirsi Dynix systems, and FOLIO''' do NOT require Authorities to be separated by usage; a single authority file is generally returned. '''Sierra''' DOES require separation by usage, please check your current load tables to see how they're segmented. '''Alma''' does not have Authority records returned.

===Names as subjects===
Some authority records for names are coded for use as both a name and a subject. MARS 2.0 is able to distribute those names in the Name file, in the Subject file or in both files, as determined by the usage of the bib heading.

===Brief authority records===
For headings in bibliographic records which do not '''fully''' match a heading in any of the selected authority files, MARS 2.0 automatically generates '''brief''' authority records in MARC 21 Authority Format.

For libraries that subscribe to the '''Authority Notification Service''' (see Step 6), these brief authority records allow the program to track the library’s unmatched headings. During each update cycle, MARS 2.0 Notification Service uses these brief authority records to trigger distribution of new national-level authority records for unmatched headings in your database.

Most modern local systems either do '''not''' require an authority record to index unmatched bibliographic headings or can generate authority records for any heading not linked to an authority record. Therefore, most libraries do not need to have brief authority records included in their authority distribution files.

===LC validation records===
MARS 2.0 includes LC validation records as part of the match and delivery processing.

===Authority notification services===
After completing your bibliographic basefile processing, Backstage retains a copy of your authority records to build a '''Master Authority File''' for your library. This file is used when you '''subscribe''' to the '''Authority Notification''' or '''Current Cataloging Services''' (see Step 6).

===Authority file retention===
Backstage retains archive copies of your authorities distribution files for a minimum of one year following completion of MARS 2.0 projects. The Master Authority File for users of the Authority Notification or Current Cataloging Services will remain archived for at least 3 years.

===MARC21 format===
All authority records provided by MARS 2.0 are in MARC 21 format. If necessary, files can also be output as MARCXML.

==links==
<center>[[Step 4.1|4.1]] - [[Step 4.2|4.2]] - [[Step 4.3|4.3]] - [[Step 4.4|4.4]] - [[Step 4.5|4.5]] - [[Step 4.6|4.6]] - [[Step 4.7|4.7]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 4.4

2024-05-28T20:04:58Z

Casey: /* Step 4.4: Authority Segmentation by Usage */

==Step 4.4: Authority Segmentation by Usage==
[[Image:a4-4.png]] 
MARS 2.0 can distribute authority records in single- or multiple-file combinations. The number of files that are used to distribute your authority records should '''mirror''' the setup of authority indexes in your system.

If all authority records in the ILS are in a single file, regardless of whether a record links to a main/added entry heading or a subject heading, all files can be '''combined'''.

If the local authority file is divided into multiple files based on heading usage within bibliographic records, files should be '''separated''' to mirror your ILS.

The following table shows the distribution of authority records by authority tag and bibliographic usage:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Files
! style="background:silver" | Authority Tags
! style="background:silver" | Bibliographic Usage
! style="background:silver" | Authority Usage
|-
| Name || 100, 110, 111 || 1XX*, 7XX* || name
|-
| Subject || 100, 110, 111, 150, 151 || 6XX* (excludes 655) || subject
|-
| Series || 130 || 4XX*, 8XX* || series
|-
| Title || 100, 110, 111 || 130, 440, 630, 730, 830 || name.title, subject.title, series.title
|-
| Genre || 155 || 655 || genre
|}
<div style=clear:both></div>
''*excludes bib 130, 440, 630, 730, 830 for these entries with asterisk''

It may be that your ILS requires certain combinations in order to load the indexes properly. MARS 2.0 can combine or separate the usage files in whatever method is desired.

For instance, if your ILS requires Subjects be loaded separately, MARS 2.0 will send you one file with '''Subjects''' (which includes Genre) and one file with '''Names''' (which contains the combined authorities for all Series and Title unless otherwise specified).

'''NOTE: Polaris, CARL, Koha, Evergreen, Sirsi Dynix systems''', and FOLIO do NOT require Authorities to be separated by usage; a single authority file is generally returned. '''Sierra''' DOES require separation by usage, please check your current load tables to see how they're segmented. '''Alma''' does not have Authority records returned.

===Names as subjects===
Some authority records for names are coded for use as both a name and a subject. MARS 2.0 is able to distribute those names in the Name file, in the Subject file or in both files, as determined by the usage of the bib heading.

===Brief authority records===
For headings in bibliographic records which do not '''fully''' match a heading in any of the selected authority files, MARS 2.0 automatically generates '''brief''' authority records in MARC 21 Authority Format.

For libraries that subscribe to the '''Authority Notification Service''' (see Step 6), these brief authority records allow the program to track the library’s unmatched headings. During each update cycle, MARS 2.0 Notification Service uses these brief authority records to trigger distribution of new national-level authority records for unmatched headings in your database.

Most modern local systems either do '''not''' require an authority record to index unmatched bibliographic headings or can generate authority records for any heading not linked to an authority record. Therefore, most libraries do not need to have brief authority records included in their authority distribution files.

===LC validation records===
MARS 2.0 includes LC validation records as part of the match and delivery processing.

===Authority notification services===
After completing your bibliographic basefile processing, Backstage retains a copy of your authority records to build a '''Master Authority File''' for your library. This file is used when you '''subscribe''' to the '''Authority Notification''' or '''Current Cataloging Services''' (see Step 6).

===Authority file retention===
Backstage retains archive copies of your authorities distribution files for a minimum of one year following completion of MARS 2.0 projects. The Master Authority File for users of the Authority Notification or Current Cataloging Services will remain archived for at least 3 years.

===MARC21 format===
All authority records provided by MARS 2.0 are in MARC 21 format. If necessary, files can also be output as MARCXML.

==links==
<center>[[Step 4.1|4.1]] - [[Step 4.2|4.2]] - [[Step 4.3|4.3]] - [[Step 4.4|4.4]] - [[Step 4.5|4.5]] - [[Step 4.6|4.6]] - [[Step 4.7|4.7]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.0

2024-05-22T19:12:55Z

Casey: /* National authority files */

==Authority Cleanup Overview==
The first phase of MARS 2.0 Authority Control comprises a battery of routines that update and correct individual subfields and contiguous pairs of subfields, the purpose of which is to increase the likelihood of finding the appropriate authority match.

These corrections are based on a number of subfield update tables, maintained by MARS 2.0 authorities librarians.

MARS 2.0 subfield correction routines include:
* Updating obsolete forms of subdivisions to the current form
* Correcting common typographical errors
* Expanding abbreviations in subject subfields to their fuller form
* Converting common direct geographic subdivisions to their indirect form
* Deleting subject subdivisions which have been canceled or discontinued
* Correcting spacing, capitalization, and punctuation

===Update obsolete subdivisions===
MARS 2.0 uses a number of subfield correction tables to correct common errors in LC subfields


— Relations (General) with the United States

'''changes to''':
— Relations — United States

===Correct typographical errors===
MARS 2.0 also uses the subfield correction tables to correct common spelling errors in LC subdivisions:

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Histroy || History || LC 6XX $x
|-
| Untied States || United States || LC 650 $z and 651 $a
|}
<div style=clear:both></div>

===Expand abbreviations===
The subfield correction tables also support the expansion of outdated or invalid abbreviations in LC headings to the full form. Changes are made only when the outdated or invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Outdated / Invalid
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Hist. & crit. || History and criticism || LC 6XX $x
|-
| U.S. || United States || LC 651 $a, X10 $a, and 6XX $z
|-
| Econ. cond. || Economic conditions || LC 6XX $x
|}
<div style=clear:both></div>

===Direct-to-indirect geographic conversion===
MARS 2.0 uses a table to convert direct geographic subdivisions to the indirect form. Changes are made by the direct-to-indirect subfield conversion program only when the invalid form is the entire text of the $z '''and''' there is only one $z in the heading:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Direct Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $z Paris || $z France $z Paris || LC 6XX fields
|-
| $z Jefferson Co., Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|-
| $z Jefferson County, Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|}
<div style=clear:both></div>

===Chronological conversion===
MARS 2.0 uses a table to convert chronological headings '''$y''' to their correct form. Corrections are made to spelling and punctuation as well as to format:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $y Twentieth century || $y 20th century || LC 6XX fields
|-
| $z 20th century || $y 20th century || LC 6XX fields
|-
| $y 20th centry ||$y 20th century ||LC 6XX fields
|}
<div style=clear:both></div>

===Delete obsolete subdivisions===
MARS 2.0 uses a subfield deletion table to eliminate canceled subfields from LC bibliographic headings, deleting subfields only when the invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Deleted
! style="background:silver" | Field / Subfield
|-
| Addresses, essays, lectures || 6XX $x
|-
| Addresses, sermons, etc. || 6XX $x
|-
| Collected works || 6XX $x
|}
<div style=clear:both></div>

The subfield deletion table also includes common misspellings and typographical errors:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Field / Subfield
|-
| Adresses, essays, lectures || 6XX $x
|-
| Addressses, essays, lectures || 6XX $x
|-
| Collected work || 6XX $x
|}
<div style=clear:both></div>

===Retain selected subdivisions===
The subfield deletion table includes a section that prevents subfield conversions and deletions in headings meeting specific criteria.

— Yearbooks

'''changes to''':
— Periodicals
except when — Yearbooks ''is part of the subfield pair:''
— Students — Yearbooks

===Correct spacing, capitalization, and punctuation===
Most errors in spacing, capitalization and punctuation are corrected as an integral part of the authority cleanup and authority matching processes. Routines are also run to correct spacing and punctuation on the following fields:

1XX, 240, 243, 245, 260, 4XX, 6XX, 7XX, 8XX

These processes eliminate any excess spaces in each field, makes sure each field has the correct punctuation within and between each subfield, and makes sure each field has ending punctuation.


'''original headings''':
100 10 $a Black, Adam, $d 1974- .$t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001, $c Berlin, Germany)

'''updated headings''':
100 10 $a Black, Adam, $d 1974- $t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001 :$c Berlin, Germany)

==Authority Matching Overview==
While Authority Cleanup improves authority controlled headings using proprietary MARS 2.0 correcton tables, authority matching compares each authority controlled heading in your bibliographic records against authority record headings from any of a number of national and other authority files.

===National authority files===
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Abbrev.
! style="background:silver" | National Authority File
! style="background:silver" | Updates
! style="background:silver" | Size
|-
| ! align="center" | NAF || Library of Congress Names || ! align="center" | Weekly || ! align="center" | 8,212,000
|-
| ! align="center" | SAF || Library of Congress Subjects || ! align="center" | Weekly || ! align="center" | 8,611,000
|-
| ! align="center" | CHILD/CYAC || Library of Congress Children's and Young Adult Program || ! align="center" | Weekly || ! align="center" | 12,633
|-
| ! align="center" | LCGFT || Library of Congress Genre Form Terms || ! align="center" | Weekly || ! align="center" | 2,000
|-
| ! align="center" | LCMPT || Library of Congress Medium of Performance Terms || ! align="center" | TBD || ! align="center" | 876
|-
| ! align="center" | MESH || National Library of Medicine || ! align="center" | Annual || ! align="center" | 616,000
|-
| ! align="center" | NLC-N || Library Archives Canada Names || ! align="center" | Frozen || ! align="center" | 653,000
|-
| ! align="center" | NLC-S || Library Archives Canada Subjects || ! align="center" | Frozen || ! align="center" | 659,000
|-
| ! align="center" | AAT || Art & Architecture Thesaurus || ! align="center" | TBD || ! align="center" | 54,042
|-
| ! align="center" | RBMSCV || *Updated* Rare Books and Manuscripts Section Vocabularies || ! align="center" | TBD || ! align="center" | 1,463
|-
| ! align="center" | TGM || Thesaurus for Graphic Materials || ! align="center" | Frozen || ! align="center" | 7,812
|-
| ! align="center" | GSAFD || Guidelines on Subject Access to Individual Works of Fiction, Drama, etc || ! align="center" | Frozen || ! align="center" | 153
|-
| ! align="center" | FAST || Faceted Application of Subject Terminology || ! align="center" | Quarterly || ! align="center" | 1,821,179
|-
| ! align="center" | NASA || NASA Thesaurus || ! align="center" | TBD || ! align="center" | 18,336
|-
| ! align="center" | OLACVGGT || OLAC Video Game Genre Vocabulary || ! align="center" | Frozen || ! align="center" | 66
|-
| ! align="center" | EMBNE || National Library of Spain || ! align="center" | TBD|| ! align="center" | 4,085,978
|-
| ! align="center" | QLSP || Queens Library Spanish Language Subject Headings || ! align="center" | Frozen || ! align="center" | 11,745
|-
| ! align="center" | ERIC|| Education Resources Information Center (ERIC) Thesaurus || ! align="center" | TBD || ! align="center" | 4,552
|-
| ! align="center" | HOMOIT || Homosaurus || ! align="center" | Semi-annual || ! align="center" | 2,834
|}

<div style=clear:both></div>

NOTE: As of September 2018, the Canadiana Authorities product from Library and Archives Canada has been discontinued. Library and Archives Canada is joining NACO and authority records are expected to be distributed via LC.

NOTE: RBMSCV (formerly known as RBMS) was released early 2023; the vocabulary and authorities is fully live in the Backstage system.

===Goals of authority matching===
Authority matching uses the headings in authority records to update or correct the bibliographic headings so they conform to current standards.

Authority matching is also the basis for providing full authority records for your local system. The goals of authority matching are to:
*Update '''invalid headings''' to '''valid forms''' based on cross-references found in authority records (convert to the established form of heading)
*Modify headings that have incorrect '''spacing''', '''punctuation''', '''indicators''', or '''subfield codes''' to the correct form based on matches found
*Update '''invalid higher levels''' of a heading to their '''valid forms''', based on cross-references found in authority records
*Distribute '''matched authority records''' to your institution
*Identify headings requiring '''more attention''' by your staff, through the use of MARS 2.0 reports

===Fields under authority control===
MARS 2.0 corrects and updates the full range of authority controlled headings. The following bibliographic headings / fields are included in MARS 2.0 authority control processing:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" | Name, Title, and Series Authority Controlled Headings
|-
|Personal Names||100, 700
|-
|Corporate Names||110, 710
|-
|Conference Names||111, 711
|-
|Uniform Titles||130, 240, 730
|-
|Uniform Titles in a $t||600, 610, 611, 700, 710, 711
|-
|Series||400, 410, 411, 440, 800, 810, 811, 830
|}
<div style=clear:both></div>

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" |Subject Authority Controlled Headings
|-
|Personal Names||600
|-
|Corporate Names||610
|-
|Conference Names||611
|-
|Uniform Titles||630
|-
|Topical||650
|-
|Geographic||651
|-
|Genre||655
|}
<div style=clear:both></div>

===Subfields disregarded===
A number of MARC subfields are disregarded during MARS 2.0 authority matching. In the following headings, the volume designations in fields 810 and 440 $v, the heading linkage information in field 130 $6, and the ISSN in field 440 $x, are all examples of subfield information which is not under authority control:


810 2 $a John Bartholomew and Son. $t Bartholomew world travel series ;$v 10.
130 0 $6 880-01 $a ”Hsuuan lai his kan” his lieh.
440 4 $a Romanica Gothoburgensia ;$v 12, 16 $x 0080-3863

===Subfields matched or ignored===
The table below shows the subfields that are included in the MARS 2.0 authority matching process:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | MARC Field !!style="background:silver" | Subfields Retained During Matching !! style="background:silver" | Subfields Ignored During Matching
|-
|100, 400, 700, 800 || a b c d f g h k l m n o p q r s t y z || e u v w x 2 3 4 5 6
|-
|110, 410, 710, 810 || a b c d f g h k l m n o p r s t y z || e u v w x 2 3 4 5 6
|-
|111, 411, 711, 811 || a b c d e f g h k l m n o p q r s t u y z || v w x 2 3 4 5 6
|-
|130, 830 || a d f g h k l m n o p r s t x y z || v w 2 3 5 6
|-
|730 || a d f g h k l m n o p r s t y z || v w x 2 3 5 6
|-
|440 || a n p || v w x 6
|-
|600 || a b c d f g h k l m n o p q r s t v x y z || e u w 2 3 4 5 6
|-
|610 || a b c d f g h k l m n o p r s t v x y z || e u w 2 3 4 5 6
|-
|611 || a b c d e f g h k l m n o p q r s t u v x y z || 2 3 4 5 6
|-
|630 || a d f g h k l m n o p r s t v x y z || w 2 3 5 6
|-
|650 || a b c d v x y z || e w 2 3 6
|-
|651 || a b v x y z || w 2 3 6
|-
|655 || a b c v x y z || e w 2 3 6
|}
<div style=clear:both></div>

===Normalization===
Headings from both your bibliographic records and the MARS 2.0 national authority files are normalized before they are compared for matching. MARS 2.0 uses the NACO normalization standard. During normalization:
*Alphabetic characters are converted to '''uppercase'''
*The '''first comma will be retained''' in $a for personal name headings
*All other punctuation is '''removed'''
*Certain '''diacritics''' and '''hyphens''' are left in for JACKPHY normalization
*All other diacritics are '''removed'''
*Special characters are replaced by an '''alphabetic equivalent'''
*Subfield codes are '''removed'''
*Subfield delimiters for '''all but first subfield''' will be left in

'''bib record heading''':
$a Architecture $z Brazil $x S'ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Notice the subfield codes and the diacritic in '''S'ao Paulo''' have been discarded when constructing the normalized form of the heading.

Because subfield codes are ignored during the authority matching process, invalid subfield codes do not affect the matching and may be corrected during the process.

For this example, the normalized form of the established heading '''1XX''' in the authority record is:

'''authority heading''':
$a Architecture $z Brazil $z S~ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Since the normalized forms of the bibliographic and authority headings are the same, the established form in the authority record replaces the form in the bibliographic record.

The bibliographic heading then contains the correct diacritic ~ instead of ' and the subfield code for '''S'ao Paulo''' has been corrected to '''$z'''.

== Topics ==
* [[Step 3.1|Step 3.1]] - Generic Name Headings
* [[Step 3.2|Step 3.2]] - Tag Flipping
* [[Step 3.3|Step 3.3]] - Partial Matches
* [[Step 3.4|Step 3.4]] - Split Headings
* [[Step 3.5|Step 3.5]] - Series Processing
* [[Step 3.6|Step 3.6]] - Subdivision Updates
* [[Step 3.7|Step 3.7]] - Childrens Matching
* [[Step 3.8|Step 3.8]] - MESH Matching
* [[Step 3.9|Step 3.9]] - Canadian Matching
* [[Step 3.10|Step 3.10]] - Local Bibliographic Subject Matching
* [[Step 3.11|Step 3.11]] - Genre Form Matching
* [[Step 3.12|Step 3.12]] - Subject Term Conversions
* [[Step 3.13|Step 3.13]] - Other Subject Vocabulary Matching
* [[Step 3.14|Step 3.14]] - Local Fields in Authority Records
* [[Step 3.15|Step 3.15]] - Local Authority Master
* [[Step 3.16|Step 3.16]] - JACKPHY Vernacular
* [[Step 3.17|Step 3.17]] - Pseudonyms
* [[Step 3.18|Step 3.18]] - Deblinding XRefs

The rest of the information contained in Step 3 details the matching options for your bibliographic and authority records. As with each step of this profile, these options are suggestions though each one can be customized according to your preference.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.12

2024-02-07T17:46:00Z

Casey: /* Indigenous people */

==Step 3.12: Subject Term Conversions==
[[Image:A3-11new.jpg]] 
Over the years there has been growing interest in either supplementing existing LCSH vocabulary or replacing outdated/obsolete terminology. We offer a few different options to help meet your needs in term conversions.

===LCSH/LCGFT to FAST===
Some institutions find use in adding FAST headings when they are missing from a Bibliographic record so they are utilizing FAST as an additional faceted search option while others are moving towards an easier way to do subject analysis. Either way, often an automated approach is needed for addressing legacy items. Backstage has created a process that will take each LC term (LCSH or LCGFT) to add the appropriate FAST term (while retaining the original LC term). Options are available to omit the LCGFT match/addition.


'''original headings''':
650 0 $a Capitol Riot, Washington, D.C., 2021 $v Pictorial works.
650 0 $a Riots $z Washington (D.C.) $v Pictorial works.
650 0 $a Political violence $z Washington (D.C.) $v Pictorial works.

'''updated headings''':
650 0 $a Capitol Riot, Washington, D.C., 2021 $v Pictorial works.
650 0 $a Riots $z Washington (D.C.) $v Pictorial works.
650 0 $a Political violence $z Washington (D.C.) $v Pictorial works.
647 7 $a Capitol Riot $c (Washington, D.C. : $d 2021) $2 fast $0 (OCoLC)fst02032437
648 7 $a 2021 $2 fast
650 7 $a Political violence $2 fast $0 (OCoLC)fst01069902
650 7 $a Riots $2 fast $0 (OCoLC)fst01098069
651 7 $a Washington (D.C.) $2 fast $0 (OCoLC)fst01204505

===GSAFD to LCGFT===
The vocabulary for the Guidelines on Subject Access to Individual Works of Fiction, Drama, Etc. (GSAFD) predates the formation of LCGFT. As LCGFT became more widely used and accepted, the use of GSAFD waned and eventually the vocabulary was largely absorbed into LCGFT. We have the ability to convert legacy GSAFD terms into LCGFT where they exist. There are some instances where a conversion is not achievable since there is not a 1:1 correlation or there may not be a good LCGFT equivalent just yet. Reports are available to alert you to terms that we are unable to convert.

'''original headings''':
655 7 $a Mystery comic books, strips, etc. $2 gsafd
655 7 $a Medical drama (Films). $2 gsafd

'''Updated headings''':
655 7 $a Detective and mystery comics. $2 lcgft
655 7 $a Medical films (Motion pictures). $2 lcgft

===LCSH/LCGFT and MeSH to HOMOIT===
The Homosaurus vocabulary has been developed and maintained by virtue of multiple volunteers across the library world. Many institutions are now incorporating this vocabulary into new cataloging in order to give better description to their items where LCSAF and MeSH are unable to describe something in the current, preferred terminology. However, the issue of legacy data is still a problem, as there is not enough staff time to spend to manually assign subject terms. Backstage can assist with an automated crosswalk that was developed internally. The crosswalk will look for a list of terms that could appear in LCSH and will add the Homosaurus equivalent with a $2 homoit. You will have the option of retaining any original $v Juvenile form subdivision as well as opting out of adding the Homosaurus term when it perfectly duplicates LCSH.

'''original headings''':
650 0 $a Buddhist gays.
650 0 $a Cruising (Sexual behavior).

'''updated headings''':
650 0 $a Buddhist gays.
650 0 $a Cruising (Sexual behavior).
650 7 $a Gay Buddhists $2 homoit
650 7 $a LGBTQ+ Buddhists $2 homoit
650 7 $a Cruising $2 homoit
650 7 $a Sexual practices $2 homoit

===Indigenous people===
In recent years there has been a push to alter terminology to essentially "Decolonize" the catalog. The goal is to remove terms assigned by non-Indigenous peoples to represent them. This is a larger effort that many different institutions are working on but as a starting point, Backstage will change "Indians of ..." subject headings to "Indigenous peoples $z ..." and remove the use of "Indians" in individual tribal/community names. Special handling of the Indigenous populations of Alaska and Canada are also included. The use of Backstage's locally created authority file will facilitate these changes and you will receive a copy of the associated authority records.

Some institutions are also opting to add additional terms such as "Native Americans" to broaden search capability for their patrons, so let us know if there are additional terms you'd like to add!

'''original headings''':
650 0 $a Art $x Indian influences.
650 0 $a Asto Indians.
650 0 $a Chilcotin Indians.
650 0 $a Indians of North America $x Boats $z Alaska.
650 0 $a Indians of North America $z Canada.
650 0 $a Indians of South America $x Missions.

'''Updated headings''':
650 7 $a Art $x Indigenous influences. $2 indig
650 7 $a Asto (South American people). $2 indig
650 7 $a Tsilhqot'in. $2 indig
650 7 $a Alaska Natives $x Boats. $2 indig
650 7 $a First Nations. $2 indig
650 7 $a Indigenous peoples $z South America $x Missions. $2 indig

You have the option of using the locally prescribed $2 above or instead using 2nd indicator 4, with no $2.

A full list of the terms being addressed can be found [https://docs.google.com/spreadsheets/d/1ZMg-yXkmUoVD79Mfg8lLBTzMz4Tccnhm/edit#gid=934320559 here]

===Undocumented immigrants===
Prior to LC's final decision to change "Illegal aliens" to "Noncitizens" plus "Illegal immigration" many institutions were opting to change "Illegal aliens" to "Undocumented immigrants". This local authority file will allow you to make this alternate change while still changing "Aliens" to "Noncitizens" as currently prescribed by LCSH.

===Enslaved Persons===
We are aware that there are efforts by the Library of Congress to begin addressing Enslaved Persons. Many of our clients, however, are still interested in making this change now. As such, as of November 2022 a new authority file for this term set is now available to begin making the change within your catalog. You can view the term list [https://docs.google.com/spreadsheets/d/1EXJLLEFb3UaOemigcffRngX15wf-GpVe8oADfukVqMg/edit#gid=0 here]

===Other potential changes===
We're trying to keep our pulse on other sets of terms that institutions are looking at changing. We're slowly compiling that list that come in as 1) custom requests from our clients, or 2) appear on the cataloginglab.org website. You can find suggested changes [https://docs.google.com/spreadsheets/d/1GmZYYspaeVa46C7jlG3fklXh1FOjuQ3U0YEn6gqau6g/edit#gid=0 here]. PLEASE NOTE that we would consider these "custom" changes to your catalog so you can alter what the "Preferred term" is for these. Please download the spreadsheet, make your changes, and supply us with the updated spreadsheet.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.0

2023-08-10T19:51:52Z

Casey: /* National authority files */

==Authority Cleanup Overview==
The first phase of MARS 2.0 Authority Control comprises a battery of routines that update and correct individual subfields and contiguous pairs of subfields, the purpose of which is to increase the likelihood of finding the appropriate authority match.

These corrections are based on a number of subfield update tables, maintained by MARS 2.0 authorities librarians.

MARS 2.0 subfield correction routines include:
* Updating obsolete forms of subdivisions to the current form
* Correcting common typographical errors
* Expanding abbreviations in subject subfields to their fuller form
* Converting common direct geographic subdivisions to their indirect form
* Deleting subject subdivisions which have been canceled or discontinued
* Correcting spacing, capitalization, and punctuation

===Update obsolete subdivisions===
MARS 2.0 uses a number of subfield correction tables to correct common errors in LC subfields


— Relations (General) with the United States

'''changes to''':
— Relations — United States

===Correct typographical errors===
MARS 2.0 also uses the subfield correction tables to correct common spelling errors in LC subdivisions:

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Histroy || History || LC 6XX $x
|-
| Untied States || United States || LC 650 $z and 651 $a
|}
<div style=clear:both></div>

===Expand abbreviations===
The subfield correction tables also support the expansion of outdated or invalid abbreviations in LC headings to the full form. Changes are made only when the outdated or invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Outdated / Invalid
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| Hist. & crit. || History and criticism || LC 6XX $x
|-
| U.S. || United States || LC 651 $a, X10 $a, and 6XX $z
|-
| Econ. cond. || Economic conditions || LC 6XX $x
|}
<div style=clear:both></div>

===Direct-to-indirect geographic conversion===
MARS 2.0 uses a table to convert direct geographic subdivisions to the indirect form. Changes are made by the direct-to-indirect subfield conversion program only when the invalid form is the entire text of the $z '''and''' there is only one $z in the heading:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Direct Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $z Paris || $z France $z Paris || LC 6XX fields
|-
| $z Jefferson Co., Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|-
| $z Jefferson County, Kan. || $z Kansas $z Jefferson County || LC 6XX fields
|}
<div style=clear:both></div>

===Chronological conversion===
MARS 2.0 uses a table to convert chronological headings '''$y''' to their correct form. Corrections are made to spelling and punctuation as well as to format:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Subdivision
! style="background:silver" | Changes to
! style="background:silver" | In Field / Subfield
|-
| $y Twentieth century || $y 20th century || LC 6XX fields
|-
| $z 20th century || $y 20th century || LC 6XX fields
|-
| $y 20th centry ||$y 20th century ||LC 6XX fields
|}
<div style=clear:both></div>

===Delete obsolete subdivisions===
MARS 2.0 uses a subfield deletion table to eliminate canceled subfields from LC bibliographic headings, deleting subfields only when the invalid form is the entire text of the subfield:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Deleted
! style="background:silver" | Field / Subfield
|-
| Addresses, essays, lectures || 6XX $x
|-
| Addresses, sermons, etc. || 6XX $x
|-
| Collected works || 6XX $x
|}
<div style=clear:both></div>

The subfield deletion table also includes common misspellings and typographical errors:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Error
! style="background:silver" | Field / Subfield
|-
| Adresses, essays, lectures || 6XX $x
|-
| Addressses, essays, lectures || 6XX $x
|-
| Collected work || 6XX $x
|}
<div style=clear:both></div>

===Retain selected subdivisions===
The subfield deletion table includes a section that prevents subfield conversions and deletions in headings meeting specific criteria.

— Yearbooks

'''changes to''':
— Periodicals
except when — Yearbooks ''is part of the subfield pair:''
— Students — Yearbooks

===Correct spacing, capitalization, and punctuation===
Most errors in spacing, capitalization and punctuation are corrected as an integral part of the authority cleanup and authority matching processes. Routines are also run to correct spacing and punctuation on the following fields:

1XX, 240, 243, 245, 260, 4XX, 6XX, 7XX, 8XX

These processes eliminate any excess spaces in each field, makes sure each field has the correct punctuation within and between each subfield, and makes sure each field has ending punctuation.


'''original headings''':
100 10 $a Black, Adam, $d 1974- .$t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001, $c Berlin, Germany)

'''updated headings''':
100 10 $a Black, Adam, $d 1974- $t Crested geckos
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001 :$c Berlin, Germany)

==Authority Matching Overview==
While Authority Cleanup improves authority controlled headings using proprietary MARS 2.0 correcton tables, authority matching compares each authority controlled heading in your bibliographic records against authority record headings from any of a number of national and other authority files.

===National authority files===
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | Abbrev.
! style="background:silver" | National Authority File
! style="background:silver" | Updates
! style="background:silver" | Size
|-
| ! align="center" | NAF || Library of Congress Names || ! align="center" | Weekly || ! align="center" | 8,212,000
|-
| ! align="center" | SAF || Library of Congress Subjects || ! align="center" | Weekly || ! align="center" | 8,611,000
|-
| ! align="center" | CHILD/CYAC || Library of Congress Children's and Young Adult Program || ! align="center" | Weekly || ! align="center" | 12,633
|-
| ! align="center" | LCGFT || Library of Congress Genre Form Terms || ! align="center" | Weekly || ! align="center" | 2,000
|-
| ! align="center" | LCMPT || Library of Congress Medium of Performance Terms || ! align="center" | TBD || ! align="center" | 876
|-
| ! align="center" | MESH || National Library of Medicine || ! align="center" | Annual || ! align="center" | 616,000
|-
| ! align="center" | NLC-N || Library Archives Canada Names || ! align="center" | Frozen || ! align="center" | 653,000
|-
| ! align="center" | NLC-S || Library Archives Canada Subjects || ! align="center" | Frozen || ! align="center" | 659,000
|-
| ! align="center" | AAT || Art & Architecture Thesaurus || ! align="center" | TBD || ! align="center" | 54,042
|-
| ! align="center" | RBMSCV || *Updated* Rare Books and Manuscripts Section Vocabularies || ! align="center" | TBD || ! align="center" | 1,463
|-
| ! align="center" | TGM || Thesaurus for Graphic Materials || ! align="center" | Frozen || ! align="center" | 7,812
|-
| ! align="center" | GSAFD || Guidelines on Subject Access to Individual Works of Fiction, Drama, etc || ! align="center" | Frozen || ! align="center" | 153
|-
| ! align="center" | FAST || Faceted Application of Subject Terminology || ! align="center" | Quarterly || ! align="center" | 1,821,179
|-
| ! align="center" | NASA || NASA Thesaurus || ! align="center" | TBD || ! align="center" | 18,336
|-
| ! align="center" | OLACVGGT || OLAC Video Game Genre Vocabulary || ! align="center" | Frozen || ! align="center" | 66
|-
| ! align="center" | EMBNE || National Library of Spain || ! align="center" | Frozen || ! align="center" | 4,085,978
|-
| ! align="center" | QLSP || Queens Library Spanish Language Subject Headings || ! align="center" | Frozen || ! align="center" | 11,745
|-
| ! align="center" | ERIC|| Education Resources Information Center (ERIC) Thesaurus || ! align="center" | TBD || ! align="center" | 4,552
|-
| ! align="center" | HOMOIT || Homosaurus || ! align="center" | Semi-annual || ! align="center" | 2,834
|}

<div style=clear:both></div>

NOTE: As of September 2018, the Canadiana Authorities product from Library and Archives Canada has been discontinued. Library and Archives Canada is joining NACO and authority records are expected to be distributed via LC.

NOTE: RBMSCV (formerly known as RBMS) was released early 2023; the vocabulary and authorities is fully live in the Backstage system.

===Goals of authority matching===
Authority matching uses the headings in authority records to update or correct the bibliographic headings so they conform to current standards.

Authority matching is also the basis for providing full authority records for your local system. The goals of authority matching are to:
*Update '''invalid headings''' to '''valid forms''' based on cross-references found in authority records (convert to the established form of heading)
*Modify headings that have incorrect '''spacing''', '''punctuation''', '''indicators''', or '''subfield codes''' to the correct form based on matches found
*Update '''invalid higher levels''' of a heading to their '''valid forms''', based on cross-references found in authority records
*Distribute '''matched authority records''' to your institution
*Identify headings requiring '''more attention''' by your staff, through the use of MARS 2.0 reports

===Fields under authority control===
MARS 2.0 corrects and updates the full range of authority controlled headings. The following bibliographic headings / fields are included in MARS 2.0 authority control processing:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" | Name, Title, and Series Authority Controlled Headings
|-
|Personal Names||100, 700
|-
|Corporate Names||110, 710
|-
|Conference Names||111, 711
|-
|Uniform Titles||130, 240, 730
|-
|Uniform Titles in a $t||600, 610, 611, 700, 710, 711
|-
|Series||400, 410, 411, 440, 800, 810, 811, 830
|}
<div style=clear:both></div>

{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" colspan="2" |Subject Authority Controlled Headings
|-
|Personal Names||600
|-
|Corporate Names||610
|-
|Conference Names||611
|-
|Uniform Titles||630
|-
|Topical||650
|-
|Geographic||651
|-
|Genre||655
|}
<div style=clear:both></div>

===Subfields disregarded===
A number of MARC subfields are disregarded during MARS 2.0 authority matching. In the following headings, the volume designations in fields 810 and 440 $v, the heading linkage information in field 130 $6, and the ISSN in field 440 $x, are all examples of subfield information which is not under authority control:


810 2 $a John Bartholomew and Son. $t Bartholomew world travel series ;$v 10.
130 0 $6 880-01 $a ”Hsuuan lai his kan” his lieh.
440 4 $a Romanica Gothoburgensia ;$v 12, 16 $x 0080-3863

===Subfields matched or ignored===
The table below shows the subfields that are included in the MARS 2.0 authority matching process:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:silver" | MARC Field !!style="background:silver" | Subfields Retained During Matching !! style="background:silver" | Subfields Ignored During Matching
|-
|100, 400, 700, 800 || a b c d f g h k l m n o p q r s t y z || e u v w x 2 3 4 5 6
|-
|110, 410, 710, 810 || a b c d f g h k l m n o p r s t y z || e u v w x 2 3 4 5 6
|-
|111, 411, 711, 811 || a b c d e f g h k l m n o p q r s t u y z || v w x 2 3 4 5 6
|-
|130, 830 || a d f g h k l m n o p r s t x y z || v w 2 3 5 6
|-
|730 || a d f g h k l m n o p r s t y z || v w x 2 3 5 6
|-
|440 || a n p || v w x 6
|-
|600 || a b c d f g h k l m n o p q r s t v x y z || e u w 2 3 4 5 6
|-
|610 || a b c d f g h k l m n o p r s t v x y z || e u w 2 3 4 5 6
|-
|611 || a b c d e f g h k l m n o p q r s t u v x y z || 2 3 4 5 6
|-
|630 || a d f g h k l m n o p r s t v x y z || w 2 3 5 6
|-
|650 || a b c d v x y z || e w 2 3 6
|-
|651 || a b v x y z || w 2 3 6
|-
|655 || a b c v x y z || e w 2 3 6
|}
<div style=clear:both></div>

===Normalization===
Headings from both your bibliographic records and the MARS 2.0 national authority files are normalized before they are compared for matching. MARS 2.0 uses the NACO normalization standard. During normalization:
*Alphabetic characters are converted to '''uppercase'''
*The '''first comma will be retained''' in $a for personal name headings
*All other punctuation is '''removed'''
*Certain '''diacritics''' and '''hyphens''' are left in for JACKPHY normalization
*All other diacritics are '''removed'''
*Special characters are replaced by an '''alphabetic equivalent'''
*Subfield codes are '''removed'''
*Subfield delimiters for '''all but first subfield''' will be left in

'''bib record heading''':
$a Architecture $z Brazil $x S'ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Notice the subfield codes and the diacritic in '''S'ao Paulo''' have been discarded when constructing the normalized form of the heading.

Because subfield codes are ignored during the authority matching process, invalid subfield codes do not affect the matching and may be corrected during the process.

For this example, the normalized form of the established heading '''1XX''' in the authority record is:

'''authority heading''':
$a Architecture $z Brazil $z S~ao Paulo (State)

'''normalized heading''':
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE

Since the normalized forms of the bibliographic and authority headings are the same, the established form in the authority record replaces the form in the bibliographic record.

The bibliographic heading then contains the correct diacritic ~ instead of ' and the subfield code for '''S'ao Paulo''' has been corrected to '''$z'''.

== Topics ==
* [[Step 3.1|Step 3.1]] - Generic Name Headings
* [[Step 3.2|Step 3.2]] - Tag Flipping
* [[Step 3.3|Step 3.3]] - Partial Matches
* [[Step 3.4|Step 3.4]] - Split Headings
* [[Step 3.5|Step 3.5]] - Series Processing
* [[Step 3.6|Step 3.6]] - Subdivision Updates
* [[Step 3.7|Step 3.7]] - Childrens Matching
* [[Step 3.8|Step 3.8]] - MESH Matching
* [[Step 3.9|Step 3.9]] - Canadian Matching
* [[Step 3.10|Step 3.10]] - Local Bibliographic Subject Matching
* [[Step 3.11|Step 3.11]] - Genre Form Matching
* [[Step 3.12|Step 3.12]] - Subject Term Conversions
* [[Step 3.13|Step 3.13]] - Other Subject Vocabulary Matching
* [[Step 3.14|Step 3.14]] - Local Fields in Authority Records
* [[Step 3.15|Step 3.15]] - Local Authority Master
* [[Step 3.16|Step 3.16]] - JACKPHY Vernacular
* [[Step 3.17|Step 3.17]] - Pseudonyms
* [[Step 3.18|Step 3.18]] - Deblinding XRefs

The rest of the information contained in Step 3 details the matching options for your bibliographic and authority records. As with each step of this profile, these options are suggestions though each one can be customized according to your preference.

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.11

2023-08-07T20:25:53Z

Casey:

==Step 3.11: Genre Form Matching==
[[Image:a3-11b.png]] 
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.

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

==Library of Congress Genre Form Terms==
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:


'''use of $2 in heading''':
655 7 $a Fiction films $2 lcsh

'''updated to lcgft 655 tag''':
655 7 $a Fiction films $2 lcgft

LC has also added the subdivision '''Globes''' to the '''Map''' genre changes:


651 0 $a Washington (D.C.) $v Pictorial maps.
'''changes to''':
651 0 $a Washington (D.C.) $v Maps.
655 7 $a Pictorial maps. $2 lcgft

651 0 $a Ganymede (Satellite) $v Globes.
'''changes to''':
651 0 $a Ganymede (Satellite) $v Maps.
655 7 $a Globes. $2 lcgft

===Genre form terms in topical 650 headings===
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.

Topical subject headings are not affected in any way by the options selected for genre form headings.

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.

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:


'''Matching against''' LCGFT:
obsolete '''655 heading''':
655 0 $a Sitcoms (Television programs)

updated '''655 heading''':
655 7 $a Situation comedies (Television programs) $2 lcgft

'''Matching against''' GSAFD:
obsolete''' 655 heading''':
655 7 $a Sitcoms. $2 gsafd

updated''' 655 heading''':
655 7 $a Comedy television programs. $2 gsafd

===Genre form update reports===
Updates for genre form headings are included in '''Updated Headings''' report (see Step 5.2, R30).

==AAT Authority Records==
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'''):


obsolete''' 655 heading''':
655 7 $a catalogs, on-line. $2 aat

updated''' 655 heading''':
655 7 $a online catalogs. $2 aat

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

==GSAFD Authority Records==
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'''):


obsolete''' 655 heading''':
655 7 $a Utopias. $2 gsafd

updated''' 655 heading''':
655 7 $a Utopian fiction. $2 gsafd

==MeSH Genre Authority Records==
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:


obsolete''' 655 heading''':
655 7 $a Meeting Reports. $2 mesh

updated''' 655 heading''':
655 7 $a Congresses. $2 mesh

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:


'''use of $2 in 655''':
655 7 $a Almanacs. $2 mesh

'''updated 2nd indicator''' 2:
655 2 $a Almanacs.

==Rare Books Manuscripts Section Vocabularies==
MARS 2.0 can match against the NEW '''Rare Books and Manuscript Section''' genre authority files (hereafter referred to as '''RBMSCV'''). The original RBMS vocabulary was once 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'''. In 2023 the vocabulary was re-published as a single thesaurus on [https://id.loc.gov/vocabulary/rbmscv.html id.loc.gov/]

Backstage's process will automatically search those genre terms with the old RBMS $2 (differing for each of the eight thesauri) against the new single thesaurus ($2 rbmscv) and will update the term and the $2. URIs are also available for those who desire them.


obsolete''' 655 heading''':
655 7 $a Fine paper printings (Publishing). $2 rbpub

updated''' 655 heading''':
655 7 $a Fine paper printings. $2 rbmscv

'''Each client can determine whether they'd like to retain the subdivisions from the original vocabulary or remove them to conform to current vocabulary practice. Additionally, each client can decide if they'd like to retain or delete those that do not have an RBMSCV equivalent.'''

Questions have arisen regarding the old subdivisions that were allowed in the previous edition of RBMS. The vast majority of our clients that have asked about this old subdivisions DO want to retain them in the new vocabulary even though they're not technically allowed. Because of this, '''this is our default process'''. However, we're more than happy to delete them if you prefer! Another option to consider would be to copy the original RBMS heading to a local 6XX to retain the subdivisions, then delete them from the new/updated 655 RBMSCV heading.

==Thesaurus for Graphic Materials==
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:
{| border="0" cellspacing="0" cellpadding="5" style="border-collapse:collapse;"
|- align="left"
| gmgpc || genre terms || !- align="right" | 670 records
|- align="left"
| lctgm || subject terms || !- align="right" | 7,142 records
|}
<div style=clear:both></div> 

==Faceted Access for Subject Terminology==
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.

The FAST authority database comprises over 1.7 million authorities.

FAST authorities allow for a faceted approach to listing subject headings within bibliographic records:


LCSH
650 #0 $a American loyalists $z England.
651 #0 $a United States $x History $y Revolution, 1775-1783 $v Biography.
650 #0 $a Secret service $z Great Britain.
650 #0 $a Painters $z United States.

FAST
648 #7 $a 1775-1783. $2 fast
650 #7 $a American loyalists. $2 fast
611 27 $a American Revolution (1775-1783) $2 fast
650 #7 $a Secret service. $2 fast
650 #7 $a Painters. $2 fast
651 #7 $a England. $2 fast
651 #7 $a United States. $2 fast
651 #7 $a Great Britain. $2 fast
655 #7 $a Biography. $2 fast
655 #7 $a History. $2 fast


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.

<div style=clear:both></div> 

==OLACVGGT==
The OLAC Video Game Genre Terms is a vocabulary that implemented in 2018 and is not intended to be updated any further.


'''Bib 655 heading''':
655 7 $a 2D video games. $2 olacvggt

==Cartographic Update==
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:


Original fields
651 #0 $a Scotland $v Bathymetric maps.
651 #0 $a Scotland $v Globes.
651 #0 $a Scotland $v Maps, Outline.

Updated fields
651 #0 $a Scotland $v Maps.
655 #7 $a Bathymetric maps $2 lcgft.
655 #7 $a Globes $2 lcgft.
655 #7 $a Outline maps $2 lcgft.


<div style=clear:both></div> 

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]

Step 3.11

2023-08-04T20:22:49Z

Casey: /* Rare Books Manuscripts Section Vocabularies */

==Step 3.11: Genre Form Matching==
[[Image:a3-11b.png]] 
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.

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

==Library of Congress Genre Form Terms==
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:


'''use of $2 in heading''':
655 7 $a Fiction films $2 lcsh

'''updated to lcgft 655 tag''':
655 7 $a Fiction films $2 lcgft

LC has also added the subdivision '''Globes''' to the '''Map''' genre changes:


651 0 $a Washington (D.C.) $v Pictorial maps.
'''changes to''':
651 0 $a Washington (D.C.) $v Maps.
655 7 $a Pictorial maps. $2 lcgft

651 0 $a Ganymede (Satellite) $v Globes.
'''changes to''':
651 0 $a Ganymede (Satellite) $v Maps.
655 7 $a Globes. $2 lcgft

===Genre form terms in topical 650 headings===
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.

Topical subject headings are not affected in any way by the options selected for genre form headings.

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.

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:


'''Matching against''' LCGFT:
obsolete '''655 heading''':
655 0 $a Sitcoms (Television programs)

updated '''655 heading''':
655 7 $a Situation comedies (Television programs) $2 lcgft

'''Matching against''' GSAFD:
obsolete''' 655 heading''':
655 7 $a Sitcoms. $2 gsafd

updated''' 655 heading''':
655 7 $a Comedy television programs. $2 gsafd

===Genre form update reports===
Updates for genre form headings are included in '''Updated Headings''' report (see Step 5.2, R30).

==AAT Authority Records==
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'''):


obsolete''' 655 heading''':
655 7 $a catalogs, on-line. $2 aat

updated''' 655 heading''':
655 7 $a online catalogs. $2 aat

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

==GSAFD Authority Records==
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'''):


obsolete''' 655 heading''':
655 7 $a Utopias. $2 gsafd

updated''' 655 heading''':
655 7 $a Utopian fiction. $2 gsafd

==MeSH Genre Authority Records==
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:


obsolete''' 655 heading''':
655 7 $a Meeting Reports. $2 mesh

updated''' 655 heading''':
655 7 $a Congresses. $2 mesh

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:


'''use of $2 in 655''':
655 7 $a Almanacs. $2 mesh

'''updated 2nd indicator''' 2:
655 2 $a Almanacs.

==Rare Books Manuscripts Section Vocabularies==
MARS 2.0 can match against the NEW '''Rare Books and Manuscript Section''' genre authority files (hereafter referred to as '''RBMSCV'''). The original RBMS vocabulary was once 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'''. In 2023 the vocabulary was re-published as a single thesaurus on [https://id.loc.gov/vocabulary/rbmscv.html id.loc.gov/]

Backstage's process will automatically search those genre terms with the old RBMS $2 (differing for each of the eight thesauri) against the new single thesaurus ($2 rbmscv) and will update the term and the $2. URIs are also available for those who desire them.


obsolete''' 655 heading''':
655 7 $a Fine paper printings (Publishing). $2 rbpub

updated''' 655 heading''':
655 7 $a Fine paper printings. $2 rbmscv

'''Each client can determine whether they'd like to retain the subdivisions from the original vocabulary or remove them to conform to current vocabulary practice. Additionally, each client can decide if they'd like to retain or delete those that do not have an RBMSCV equivalent.'''

==Thesaurus for Graphic Materials==
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:
{| border="0" cellspacing="0" cellpadding="5" style="border-collapse:collapse;"
|- align="left"
| gmgpc || genre terms || !- align="right" | 670 records
|- align="left"
| lctgm || subject terms || !- align="right" | 7,142 records
|}
<div style=clear:both></div> 

==Faceted Access for Subject Terminology==
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.

The FAST authority database comprises over 1.7 million authorities.

FAST authorities allow for a faceted approach to listing subject headings within bibliographic records:


LCSH
650 #0 $a American loyalists $z England.
651 #0 $a United States $x History $y Revolution, 1775-1783 $v Biography.
650 #0 $a Secret service $z Great Britain.
650 #0 $a Painters $z United States.

FAST
648 #7 $a 1775-1783. $2 fast
650 #7 $a American loyalists. $2 fast
611 27 $a American Revolution (1775-1783) $2 fast
650 #7 $a Secret service. $2 fast
650 #7 $a Painters. $2 fast
651 #7 $a England. $2 fast
651 #7 $a United States. $2 fast
651 #7 $a Great Britain. $2 fast
655 #7 $a Biography. $2 fast
655 #7 $a History. $2 fast


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.

<div style=clear:both></div> 

==OLACVGGT==
The OLAC Video Game Genre Terms is a vocabulary that implemented in 2018 and is not intended to be updated any further.


'''Bib 655 heading''':
655 7 $a 2D video games. $2 olacvggt

==Cartographic Update==
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:


Original fields
651 #0 $a Scotland $v Bathymetric maps.
651 #0 $a Scotland $v Globes.
651 #0 $a Scotland $v Maps, Outline.

Updated fields
651 #0 $a Scotland $v Maps.
655 #7 $a Bathymetric maps $2 lcgft.
655 #7 $a Globes $2 lcgft.
655 #7 $a Outline maps $2 lcgft.


<div style=clear:both></div> 

==links==
<center>[[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]]
<hr>
[[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]]</center>
[[category:Profile Guide]]