https://ac.bslw.com/community/wiki/api.php?action=feedcontributions&feedformat=atom&user=NateAC Wiki - User contributions [en]2026-04-24T06:53:01ZUser contributionsMediaWiki 1.23.14https://ac.bslw.com/community/wiki/index.php/Step_2.11Step 2.112016-11-18T20:14:46Z<p>Nate: /* Lexile Measures */</p>
<hr />
<div>==Step 2.10: Accelerated Reader & Lexile Measures==<br />
[[Image:a2-10.png]]<br><br><br />
MARS 2.0 offers two types of enrichment options for your collection of juvenile records: accelerated reader & lexile measures. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Accelerated Reader===<br />
For more information about Accelerated Reader, quiz points and reading levels, please visit http://www.renaissance.com/:<br/><br />
Accelerated Reader (AR) is a computer program that helps teachers and librarians manage and monitor children’s independent reading practice. Your child picks<br />
a book at his own level and reads it at his own pace. When finished, your child takes a short quiz on the computer. (Passing the quiz is an<br />
indication that your child understood what was read.) AR gives children, teachers, and librarians feedback based on the quiz results, which<br />
the teacher then uses to help your child set goals and direct ongoing reading practice.<br />
<br />
Children using AR choose their own books to read, rather than having one<br />
assigned to them. This makes reading a much more enjoyable experience<br />
as they can choose books that are interesting to them.<br />
<br />
Teachers and librarians help your child choose books at an appropriate<br />
readability level that are challenging without being frustrating, ensuring<br />
that your child can pass the quiz and experience success. <br />
<br />
There are currently over '''870,000 ISBNs''' represented in the Accelerated Reader database.<br />
<br />
Here is an example of a before/after record with the AR enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">526 ## $a Accelerated Reader $b UG $c 5.1 $d 17 $e 17 $z 166237</font></font><br />
<br />
===Lexile Measures===<br />
For more information about Lexile Measures, please visit '''www.lexile.com''':<br/><br />
The Lexile framework is a scientific way to match readers with text using the same scale. Recognized as the standard for matching readers with texts, Lexile&#174; measures connect learners of all ages with resources at the right level of challenge. Lexile measures provide a clear way to monitor progress toward college and career readiness. There are currently over '''500,000 ISBNs''' represented within the Lexile database.<br />
<br />
Here is an example of a before/after record with the Lexile enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">521 8# $a HL720L $b Lexile</font></font><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.11Step 2.112016-11-18T20:14:30Z<p>Nate: /* Step 2.10: Accelerated Reader & Lexile Measures */</p>
<hr />
<div>==Step 2.10: Accelerated Reader & Lexile Measures==<br />
[[Image:a2-10.png]]<br><br><br />
MARS 2.0 offers two types of enrichment options for your collection of juvenile records: accelerated reader & lexile measures. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Accelerated Reader===<br />
For more information about Accelerated Reader, quiz points and reading levels, please visit http://www.renaissance.com/:<br/><br />
Accelerated Reader (AR) is a computer program that helps teachers and librarians manage and monitor children’s independent reading practice. Your child picks<br />
a book at his own level and reads it at his own pace. When finished, your child takes a short quiz on the computer. (Passing the quiz is an<br />
indication that your child understood what was read.) AR gives children, teachers, and librarians feedback based on the quiz results, which<br />
the teacher then uses to help your child set goals and direct ongoing reading practice.<br />
<br />
Children using AR choose their own books to read, rather than having one<br />
assigned to them. This makes reading a much more enjoyable experience<br />
as they can choose books that are interesting to them.<br />
<br />
Teachers and librarians help your child choose books at an appropriate<br />
readability level that are challenging without being frustrating, ensuring<br />
that your child can pass the quiz and experience success. <br />
<br />
There are currently over '''870,000 ISBNs''' represented in the Accelerated Reader database.<br />
<br />
Here is an example of a before/after record with the AR enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">526 ## $a Accelerated Reader $b UG $c 5.1 $d 17 $e 17 $z 166237</font></font><br />
<br />
===Lexile Measures===<br />
For more information about Lexile Measures, please visit '''www.lexile.com''':<br/><br />
The Lexile framework is a scientific way to match readers with text using the same scale. Recognized as the standard for matching readers with texts, Lexile&#174; measures connect learners of all ages with resources at the right level of challenge. Lexile measures provide a clear way to monitor progress toward college and career readiness. There are currently over '''500,000 ISBNs''' that are represented within the Lexile database.<br />
<br />
Here is an example of a before/after record with the Lexile enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">521 8# $a HL720L $b Lexile</font></font><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.11Step 2.112016-11-18T17:14:34Z<p>Nate: /* Lexile Measures */</p>
<hr />
<div>==Step 2.10: Accelerated Reader & Lexile Measures==<br />
[[Image:a2-10.png]]<br><br><br />
MARS 2.0 offers two types of enrichment options for your collection of juvenile records: accelerated reader & lexile measures. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Accelerated Reader===<br />
For more information about Accelerated Reader, quiz points and reading levels, please visit http://www.renaissance.com/:<br/><br />
Accelerated Reader (AR) is a computer program that helps teachers and librarians manage and monitor children’s independent reading practice. Your child picks<br />
a book at his own level and reads it at his own pace. When finished, your child takes a short quiz on the computer. (Passing the quiz is an<br />
indication that your child understood what was read.) AR gives children, teachers, and librarians feedback based on the quiz results, which<br />
the teacher then uses to help your child set goals and direct ongoing reading practice.<br />
<br />
Children using AR choose their own books to read, rather than having one<br />
assigned to them. This makes reading a much more enjoyable experience<br />
as they can choose books that are interesting to them.<br />
<br />
Teachers and librarians help your child choose books at an appropriate<br />
readability level that are challenging without being frustrating, ensuring<br />
that your child can pass the quiz and experience success. <br />
<br />
Here is an example of a before/after record with the AR enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">526 ## $a Accelerated Reader $b UG $c 5.1 $d 17 $e 17 $z 166237</font></font><br />
<br />
===Lexile Measures===<br />
For more information about Lexile Measures, please visit '''www.lexile.com''':<br/><br />
The Lexile framework is a scientific way to match readers with text using the same scale. Recognized as the standard for matching readers with texts, Lexile&#174; measures connect learners of all ages with resources at the right level of challenge. Lexile measures provide a clear way to monitor progress toward college and career readiness. There are currently over '''500,000 ISBNs''' that are represented within the Lexile database.<br />
<br />
Here is an example of a before/after record with the Lexile enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">521 8# $a HL720L $b Lexile</font></font><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_3.0Step 3.02016-11-18T17:08:54Z<p>Nate: /* National authority files */</p>
<hr />
<div>==Authority Cleanup Overview==<br />
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.<br />
<br />
These corrections are based on a number of subfield update tables, maintained by MARS 2.0 authorities librarians.<br />
<br />
MARS 2.0 subfield correction routines include:<br />
* Updating obsolete forms of subdivisions to the current form<br />
* Correcting common typographical errors<br />
* Expanding abbreviations in subject subfields to their fuller form<br />
* Converting common direct geographic subdivisions to their indirect form<br />
* Deleting subject subdivisions which have been canceled or discontinued<br />
* Correcting spacing, capitalization, and punctuation<br />
<br />
===Update obsolete subdivisions===<br />
MARS 2.0 uses a number of subfield correction tables to correct common errors in LC subfields<br />
<br />
<font size="3"><br />
— Relations <font color="red">(General) with the</font> United States<br />
<br />
'''changes to''':<br />
— Relations <font color="red">—</font> United States</font><br />
<br />
===Correct typographical errors===<br />
MARS 2.0 also uses the subfield correction tables to correct common spelling errors in LC subdivisions:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Error <br />
! style="background:silver" | Changes to <br />
! style="background:silver" | In Field / Subfield<br />
|- <br />
| Histroy || History || LC 6XX $x<br />
|-<br />
| Untied States || United States || LC 650 $z and 651 $a<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Expand abbreviations===<br />
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:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Outdated / Invalid <br />
! style="background:silver" | Changes to <br />
! style="background:silver" | In Field / Subfield<br />
|-<br />
| Hist. & crit. || History and criticism || LC 6XX $x<br />
|-<br />
| U.S. || United States || LC 651 $a, X10 $a, and 6XX $z<br />
|-<br />
| Econ. cond. || Economic conditions || LC 6XX $x<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Direct-to-indirect geographic conversion===<br />
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:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Direct Subdivision<br />
! style="background:silver" | Changes to<br />
! style="background:silver" | In Field / Subfield<br />
|-<br />
| $z Paris || $z France $z Paris || LC 6XX fields<br />
|-<br />
| $z Jefferson Co., Kan. || $z Kansas $z Jefferson County || LC 6XX fields<br />
|-<br />
| $z Jefferson County, Kan. || $z Kansas $z Jefferson County || LC 6XX fields<br />
|}<br />
<div style=clear:both></div><br />
<br />
<br />
===Chronological conversion===<br />
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:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Subdivision<br />
! style="background:silver" | Changes to<br />
! style="background:silver" | In Field / Subfield<br />
|-<br />
| $y Twentieth century || $y 20th century || LC 6XX fields<br />
|-<br />
| $z 20th century || $y 20th century || LC 6XX fields<br />
|-<br />
| $y 20th centry ||$y 20th century ||LC 6XX fields<br />
|}<br />
<div style=clear:both></div><br />
<br />
<br />
===Delete obsolete subdivisions===<br />
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:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Deleted<br />
! style="background:silver" | Field / Subfield<br />
|-<br />
| Addresses, essays, lectures || 6XX $x<br />
|-<br />
| Addresses, sermons, etc. || 6XX $x<br />
|-<br />
| Collected works || 6XX $x<br />
|}<br />
<div style=clear:both></div><br />
<br />
<br />
The subfield deletion table also includes common misspellings and typographical errors:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Error <br />
! style="background:silver" | Field / Subfield<br />
|-<br />
| Adresses, essays, lectures || 6XX $x<br />
|-<br />
| Addressses, essays, lectures || 6XX $x<br />
|-<br />
| Collected work || 6XX $x<br />
|}<br />
<div style=clear:both></div><br />
<br />
<br />
===Retain selected subdivisions===<br />
The subfield deletion table includes a section that prevents subfield conversions and deletions in headings meeting specific criteria.<br />
<font size="3"><br />
— Yearbooks<br />
<br />
'''changes to''':<br />
— Periodicals<br />
except when <font color="red">— Yearbooks</font> ''is part of the subfield pair:''<br />
— Students — Yearbooks</font><br />
<br />
===Correct spacing, capitalization, and punctuation===<br />
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:<br />
<font size="3"><br />
1XX, 240, 243, 245, 260, 4XX, 6XX, 7XX, 8XX</font><br />
<br />
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.<br />
<br />
<font size="3"><br />
'''original headings''':<br />
100 10 $a Black, Adam, $d 1974- <font color="red">.</font>$t Crested geckos<br />
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001<font color="red">,</font> $c Berlin, Germany)<br />
<br />
'''updated headings''':<br />
100 10 $a Black, Adam, $d 1974- $t Crested geckos<br />
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001 <font color="red">:</font>$c Berlin, Germany)</font><br />
<br />
==Authority Matching Overview== <br />
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.<br />
<br />
===National authority files===<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbrev.<br />
! style="background:silver" | National Authority File<br />
! style="background:silver" | Updates<br />
! style="background:silver" | Size<br />
|-<br />
| ! align="center" | NAF || Library of Congress Names || ! align="center" | Weekly || ! align="center" | 8,212,000<br />
|-<br />
| ! align="center" | SAF || Library of Congress Subjects || ! align="center" | Weekly || ! align="center" | 8,611,000<br />
|-<br />
| ! align="center" | CHILD || Library of Congress Annotated Card Program Subjects || ! align="center" | Weekly || ! align="center" | 1,000<br />
|-<br />
| ! align="center" | LCGFT || Library of Congress Genre Form Terms || ! align="center" | Weekly || ! align="center" | 2,000<br />
|-<br />
| ! align="center" | MESH || National Library of Medicine || ! align="center" | Annual || ! align="center" | 616,000<br />
|-<br />
| ! align="center" | NLC-N || Library Archives Canada Names || ! align="center" | Semi-Annual || ! align="center" | 653,000<br />
|-<br />
| ! align="center" | NLC-S || Library Archives Canada Subjects || ! align="center" | Monthly || ! align="center" | 659,000<br />
|-<br />
| ! align="center" | AAT || Art & Architecture Thesaurus || ! align="center" | Frozen || ! align="center" | 35,000<br />
|-<br />
| ! align="center" | RBMS || Rare Books and Manuscripts Section Vocabularies || ! align="center" | Frozen || ! align="center" | 1,600<br />
|-<br />
| ! align="center" | TGM || Thesaurus for Graphic Materials || ! align="center" | Frozen || ! align="center" | 7,900<br />
|-<br />
| ! align="center" | GSAFD || Guidelines on Subject Access to Individual Works of Fiction, Drama, etc || ! align="center" | Frozen || ! align="center" | 160<br />
|-<br />
| ! align="center" | FAST || Faceted Application of Subject Terminology || ! align="center" | Quarterly || ! align="center" | 1,700,000<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Goals of authority matching===<br />
Authority matching uses the headings in authority records to update or correct the bibliographic headings so they conform to current standards.<br />
<br />
Authority matching is also the basis for providing full authority records for your local system. The goals of authority matching are to:<br />
*Update '''invalid headings''' to '''valid forms''' based on cross-references found in authority records (convert to the established form of heading)<br />
*Modify headings that have incorrect '''spacing''', '''punctuation''', '''indicators''', or '''subfield codes''' to the correct form based on matches found<br />
*Update '''invalid higher levels''' of a heading to their '''valid forms''', based on cross-references found in authority records<br />
*Distribute '''matched authority records''' to your institution<br />
*Identify headings requiring '''more attention''' by your staff, through the use of MARS 2.0 reports<br />
<br />
===Fields under authority control===<br />
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:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" colspan="2" | Name, Title, and Series Authority Controlled Headings<br />
|-<br />
|Personal Names||100, 700<br />
|-<br />
|Corporate Names||110, 710<br />
|-<br />
|Conference Names||111, 711<br />
|-<br />
|Uniform Titles||130, 240, 730<br />
|-<br />
|Uniform Titles in a $t||600, 610, 611, 700, 710, 711<br />
|-<br />
|Series||400, 410, 411, 440, 800, 810, 811, 830<br />
|}<br />
<div style=clear:both></div><br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" colspan="2" |Subject Authority Controlled Headings<br />
|-<br />
|Personal Names||600<br />
|-<br />
|Corporate Names||610<br />
|-<br />
|Conference Names||611<br />
|-<br />
|Uniform Titles||630<br />
|-<br />
|Topical||650<br />
|-<br />
|Geographic||651<br />
|-<br />
|Genre||655<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Subfields disregarded===<br />
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:<br />
<br />
<font size="3"><br />
810 2 $a John Bartholomew and Son. $t Bartholomew world travel series <font color="red">;$v 10.</font><br />
130 0 <font color="red">$6 880-01</font> $a ”Hsuuan lai his kan” his lieh.<br />
440 4 $a Romanica Gothoburgensia <font color="red">;$v 12, 16 $x 0080-3863</font></font><br />
<br />
===Subfields matched or ignored===<br />
The table below shows the subfields that are included in the MARS 2.0 authority matching process:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | MARC Field !!style="background:silver" | Subfields Retained During Matching !! style="background:silver" | Subfields Ignored During Matching<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|730 || a d f g h k l m n o p r s t y z || v w x 2 3 5 6<br />
|-<br />
|440 || a n p || v w x 6<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|630 || a d f g h k l m n o p r s t v x y z || w 2 3 5 6<br />
|-<br />
|650 || a b c d v x y z || e w 2 3 6<br />
|-<br />
|651 || a b v x y z || w 2 3 6<br />
|-<br />
|655 || a b c v x y z || e w 2 3 6<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Normalization===<br />
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:<br />
*Alphabetic characters are converted to '''uppercase'''<br />
*The '''first comma will be retained''' in $a for personal name headings<br />
*All other punctuation is '''removed'''<br />
*Certain '''diacritics''' and '''hyphens''' are left in for JACKPHY normalization<br />
*All other diacritics are '''removed'''<br />
*Special characters are replaced by an '''alphabetic equivalent'''<br />
*Subfield codes are '''removed'''<br />
*Subfield delimiters for '''all but first subfield''' will be left in<br />
<br />
<font size="3">'''bib record heading''':<br />
<font color="red">$a</font> Architecture $<font color="red">z</font> Brazil $<font color="red">x</font> S<font color="red">'</font>ao Paulo <font color="red">(</font>State<font color="red">)</font><br />
<br />
'''normalized heading''':<br />
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE</font><br />
<br />
Notice the subfield codes and the diacritic in '''S'ao Paulo''' have been discarded when constructing the normalized form of the heading.<br />
<br />
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.<br />
<br />
For this example, the normalized form of the established heading '''1XX''' in the authority record is:<br />
<br />
<font size="3">'''authority heading''':<br />
<font color="red">$a</font> Architecture $<font color="red">z</font> Brazil $<font color="red">z</font> S<font color="red">~</font>ao Paulo <font color="red">(</font>State<font color="red">)</font><br />
<br />
'''normalized heading''':<br />
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE</font><br />
<br />
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.<br />
<br />
The bibliographic heading then contains the correct diacritic ~ instead of ' and the subfield code for '''S'ao Paulo''' has been corrected to '''$z'''.<br />
<br />
== Topics ==<br />
* [[Step 3.1|Step 3.1]] - Generic Name Headings<br />
* [[Step 3.2|Step 3.2]] - Tag Flipping<br />
* [[Step 3.3|Step 3.3]] - Partial Matches<br />
* [[Step 3.4|Step 3.4]] - Split Headings<br />
* [[Step 3.5|Step 3.5]] - Series Processing<br />
* [[Step 3.6|Step 3.6]] - Subdivision Updates<br />
* [[Step 3.7|Step 3.7]] - Childrens Matching<br />
* [[Step 3.8|Step 3.8]] - MESH Matching<br />
* [[Step 3.9|Step 3.9]] - Canadian Matching<br />
* [[Step 3.10|Step 3.10]] - Local Bibliographic Subject Matching<br />
* [[Step 3.11|Step 3.11]] - Genre Form Matching<br />
* [[Step 3.12|Step 3.12]] - Local Fields in Authority Records<br />
* [[Step 3.13|Step 3.13]] - Local Authority Master<br />
* [[Step 3.14|Step 3.14]] - JACKPHY Vernacular<br />
* [[Step 3.15|Step 3.15]] - Pseudonyms<br />
* [[Step 3.16|Step 3.16]] - Deblinding XRefs<br />
<br />
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.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122016-10-20T15:07:52Z<p>Nate: /* Step 2.11: Identities Management */</p>
<hr />
<div>==Step 2.11: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([http://stackoverflow.com/questions/176264/what-is-the-difference-between-a-uri-a-url-and-a-urn link]) within your records. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> http://id.loc.gov/authorities/names/nr99034050<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> http://id.loc.gov/authorities/subjects/sh85004836<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> http://id.nlm.nih.gov/mesh/D000716<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the '''identifier''' only in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html link]) and ISNI ([http://www.isni.org/ link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another client decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other client also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a http://id.loc.gov/authorities/names/no2001000753<br />
921 ## $a http://viaf.org/viaf/23238834<br />
922 ## $a http://isni.org/isni/0000000116075005<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122016-10-20T15:04:31Z<p>Nate: /* Add URIs to Authority Records */</p>
<hr />
<div>==Step 2.11: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([http://stackoverflow.com/questions/176264/what-is-the-difference-between-a-uri-a-url-and-a-urn| link]) within your records. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> http://id.loc.gov/authorities/names/nr99034050<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> http://id.loc.gov/authorities/subjects/sh85004836<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> http://id.nlm.nih.gov/mesh/D000716<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the '''identifier''' only in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html| link]) and ISNI ([http://www.isni.org/| link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another client decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other client also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html| link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a http://id.loc.gov/authorities/names/no2001000753<br />
921 ## $a http://viaf.org/viaf/23238834<br />
922 ## $a http://isni.org/isni/0000000116075005<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122016-10-20T15:02:28Z<p>Nate: /* Add $0 to Access Points */</p>
<hr />
<div>==Step 2.11: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([http://stackoverflow.com/questions/176264/what-is-the-difference-between-a-uri-a-url-and-a-urn| link]) within your records. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> http://id.loc.gov/authorities/names/nr99034050<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> http://id.loc.gov/authorities/subjects/sh85004836<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> http://id.nlm.nih.gov/mesh/D000716<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the '''identifier''' only in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html| link]) and ISNI ([http://www.isni.org/| link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another client decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other client also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html| link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a [http://id.loc.gov/authorities/names/no2001000753| http://id.loc.gov/authorities/names/no2001000753]<br />
921 ## $a [http://viaf.org/viaf/23238834| http://viaf.org/viaf/23238834]<br />
922 ## $a [http://isni.org/isni/0000000116075005| http://isni.org/isni/0000000116075005]<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122016-10-20T15:02:00Z<p>Nate: /* Add $0 to Access Points */</p>
<hr />
<div>==Step 2.11: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([http://stackoverflow.com/questions/176264/what-is-the-difference-between-a-uri-a-url-and-a-urn| link]) within your records. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> http://id.loc.gov/authorities/names/nr99034050<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> http://id.loc.gov/authorities/subjects/sh85004836<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> http://id.nlm.nih.gov/mesh/D000716<br />
''Please note that the NLM URI may not work at this time as the NLM URI site is currently still in beta.''<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the '''identifier''' only in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html| link]) and ISNI ([http://www.isni.org/| link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another client decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other client also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html| link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a [http://id.loc.gov/authorities/names/no2001000753| http://id.loc.gov/authorities/names/no2001000753]<br />
921 ## $a [http://viaf.org/viaf/23238834| http://viaf.org/viaf/23238834]<br />
922 ## $a [http://isni.org/isni/0000000116075005| http://isni.org/isni/0000000116075005]<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122016-10-20T14:58:50Z<p>Nate: /* Add URIs to Authority Records */</p>
<hr />
<div>==Step 2.11: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([http://stackoverflow.com/questions/176264/what-is-the-difference-between-a-uri-a-url-and-a-urn| link]) within your records. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> [http://id.loc.gov/authorities/names/nr99034050| http://id.loc.gov/authorities/names/nr99034050]<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> [http://id.loc.gov/authorities/subjects/sh85004836| http://id.loc.gov/authorities/subjects/sh85004836]<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> [http://id.nlm.nih.gov/mesh/D000716| http://id.nlm.nih.gov/mesh/D000716]<br />
''Please note that the NLM URI may not work at this time as the NLM URI site is currently still in beta.''<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the '''identifier''' only in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html| link]) and ISNI ([http://www.isni.org/| link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another client decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other client also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html| link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a [http://id.loc.gov/authorities/names/no2001000753| http://id.loc.gov/authorities/names/no2001000753]<br />
921 ## $a [http://viaf.org/viaf/23238834| http://viaf.org/viaf/23238834]<br />
922 ## $a [http://isni.org/isni/0000000116075005| http://isni.org/isni/0000000116075005]<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122016-10-20T14:58:14Z<p>Nate: /* Add URIs to Authority Records */</p>
<hr />
<div>==Step 2.11: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([http://stackoverflow.com/questions/176264/what-is-the-difference-between-a-uri-a-url-and-a-urn| link]) within your records. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> [http://id.loc.gov/authorities/names/nr99034050| http://id.loc.gov/authorities/names/nr99034050]<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> [http://id.loc.gov/authorities/subjects/sh85004836| http://id.loc.gov/authorities/subjects/sh85004836]<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> [http://id.nlm.nih.gov/mesh/D000716| http://id.nlm.nih.gov/mesh/D000716]<br />
''Please note that the NLM URI may not work at this time as the NLM URI site is currently still in beta.''<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the '''identifier''' only in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html| link]) and ISNI ([http://www.isni.org/| link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another client decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other vendor also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html| link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a [http://id.loc.gov/authorities/names/no2001000753| http://id.loc.gov/authorities/names/no2001000753]<br />
921 ## $a [http://viaf.org/viaf/23238834| http://viaf.org/viaf/23238834]<br />
922 ## $a [http://isni.org/isni/0000000116075005| http://isni.org/isni/0000000116075005]<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_3.0Step 3.02016-10-03T19:17:36Z<p>Nate: /* National authority files */</p>
<hr />
<div>==Authority Cleanup Overview==<br />
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.<br />
<br />
These corrections are based on a number of subfield update tables, maintained by MARS 2.0 authorities librarians.<br />
<br />
MARS 2.0 subfield correction routines include:<br />
* Updating obsolete forms of subdivisions to the current form<br />
* Correcting common typographical errors<br />
* Expanding abbreviations in subject subfields to their fuller form<br />
* Converting common direct geographic subdivisions to their indirect form<br />
* Deleting subject subdivisions which have been canceled or discontinued<br />
* Correcting spacing, capitalization, and punctuation<br />
<br />
===Update obsolete subdivisions===<br />
MARS 2.0 uses a number of subfield correction tables to correct common errors in LC subfields<br />
<br />
<font size="3"><br />
— Relations <font color="red">(General) with the</font> United States<br />
<br />
'''changes to''':<br />
— Relations <font color="red">—</font> United States</font><br />
<br />
===Correct typographical errors===<br />
MARS 2.0 also uses the subfield correction tables to correct common spelling errors in LC subdivisions:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Error <br />
! style="background:silver" | Changes to <br />
! style="background:silver" | In Field / Subfield<br />
|- <br />
| Histroy || History || LC 6XX $x<br />
|-<br />
| Untied States || United States || LC 650 $z and 651 $a<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Expand abbreviations===<br />
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:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Outdated / Invalid <br />
! style="background:silver" | Changes to <br />
! style="background:silver" | In Field / Subfield<br />
|-<br />
| Hist. & crit. || History and criticism || LC 6XX $x<br />
|-<br />
| U.S. || United States || LC 651 $a, X10 $a, and 6XX $z<br />
|-<br />
| Econ. cond. || Economic conditions || LC 6XX $x<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Direct-to-indirect geographic conversion===<br />
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:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Direct Subdivision<br />
! style="background:silver" | Changes to<br />
! style="background:silver" | In Field / Subfield<br />
|-<br />
| $z Paris || $z France $z Paris || LC 6XX fields<br />
|-<br />
| $z Jefferson Co., Kan. || $z Kansas $z Jefferson County || LC 6XX fields<br />
|-<br />
| $z Jefferson County, Kan. || $z Kansas $z Jefferson County || LC 6XX fields<br />
|}<br />
<div style=clear:both></div><br />
<br />
<br />
===Chronological conversion===<br />
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:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Subdivision<br />
! style="background:silver" | Changes to<br />
! style="background:silver" | In Field / Subfield<br />
|-<br />
| $y Twentieth century || $y 20th century || LC 6XX fields<br />
|-<br />
| $z 20th century || $y 20th century || LC 6XX fields<br />
|-<br />
| $y 20th centry ||$y 20th century ||LC 6XX fields<br />
|}<br />
<div style=clear:both></div><br />
<br />
<br />
===Delete obsolete subdivisions===<br />
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:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Deleted<br />
! style="background:silver" | Field / Subfield<br />
|-<br />
| Addresses, essays, lectures || 6XX $x<br />
|-<br />
| Addresses, sermons, etc. || 6XX $x<br />
|-<br />
| Collected works || 6XX $x<br />
|}<br />
<div style=clear:both></div><br />
<br />
<br />
The subfield deletion table also includes common misspellings and typographical errors:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Error <br />
! style="background:silver" | Field / Subfield<br />
|-<br />
| Adresses, essays, lectures || 6XX $x<br />
|-<br />
| Addressses, essays, lectures || 6XX $x<br />
|-<br />
| Collected work || 6XX $x<br />
|}<br />
<div style=clear:both></div><br />
<br />
<br />
===Retain selected subdivisions===<br />
The subfield deletion table includes a section that prevents subfield conversions and deletions in headings meeting specific criteria.<br />
<font size="3"><br />
— Yearbooks<br />
<br />
'''changes to''':<br />
— Periodicals<br />
except when <font color="red">— Yearbooks</font> ''is part of the subfield pair:''<br />
— Students — Yearbooks</font><br />
<br />
===Correct spacing, capitalization, and punctuation===<br />
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:<br />
<font size="3"><br />
1XX, 240, 243, 245, 260, 4XX, 6XX, 7XX, 8XX</font><br />
<br />
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.<br />
<br />
<font size="3"><br />
'''original headings''':<br />
100 10 $a Black, Adam, $d 1974- <font color="red">.</font>$t Crested geckos<br />
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001<font color="red">,</font> $c Berlin, Germany)<br />
<br />
'''updated headings''':<br />
100 10 $a Black, Adam, $d 1974- $t Crested geckos<br />
111 20 $a IEEE 1394 (FireWire) Workshop $d (2001 <font color="red">:</font>$c Berlin, Germany)</font><br />
<br />
==Authority Matching Overview== <br />
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.<br />
<br />
===National authority files===<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbrev.<br />
! style="background:silver" | National Authority File<br />
! style="background:silver" | Updates<br />
! style="background:silver" | Size<br />
|-<br />
| ! align="center" | NAF || Library of Congress Names || ! align="center" | Weekly || ! align="center" | 8,212,000<br />
|-<br />
| ! align="center" | SAF || Library of Congress Subjects || ! align="center" | Weekly || ! align="center" | 8,611,000<br />
|-<br />
| ! align="center" | CHILD || Library of Congress Annotated Card Program Subjects || ! align="center" | Weekly || ! align="center" | 1,000<br />
|-<br />
| ! align="center" | LCGFT || Library of Congress Genre Form Terms || ! align="center" | Weekly || ! align="center" | 800<br />
|-<br />
| ! align="center" | MESH || National Library of Medicine || ! align="center" | Annual || ! align="center" | 616,000<br />
|-<br />
| ! align="center" | NLC-N || Library Archives Canada Names || ! align="center" | Semi-Annual || ! align="center" | 653,000<br />
|-<br />
| ! align="center" | NLC-S || Library Archives Canada Subjects || ! align="center" | Monthly || ! align="center" | 659,000<br />
|-<br />
| ! align="center" | AAT || Art & Architecture Thesaurus || ! align="center" | Frozen || ! align="center" | 35,000<br />
|-<br />
| ! align="center" | RBMS || Rare Books and Manuscripts Section Vocabularies || ! align="center" | Frozen || ! align="center" | 1,600<br />
|-<br />
| ! align="center" | TGM || Thesaurus for Graphic Materials || ! align="center" | Frozen || ! align="center" | 7,900<br />
|-<br />
| ! align="center" | GSAFD || Guidelines on Subject Access to Individual Works of Fiction, Drama, etc || ! align="center" | Frozen || ! align="center" | 160<br />
|-<br />
| ! align="center" | FAST || Faceted Application of Subject Terminology || ! align="center" | Quarterly || ! align="center" | 1,700,000<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Goals of authority matching===<br />
Authority matching uses the headings in authority records to update or correct the bibliographic headings so they conform to current standards.<br />
<br />
Authority matching is also the basis for providing full authority records for your local system. The goals of authority matching are to:<br />
*Update '''invalid headings''' to '''valid forms''' based on cross-references found in authority records (convert to the established form of heading)<br />
*Modify headings that have incorrect '''spacing''', '''punctuation''', '''indicators''', or '''subfield codes''' to the correct form based on matches found<br />
*Update '''invalid higher levels''' of a heading to their '''valid forms''', based on cross-references found in authority records<br />
*Distribute '''matched authority records''' to your institution<br />
*Identify headings requiring '''more attention''' by your staff, through the use of MARS 2.0 reports<br />
<br />
===Fields under authority control===<br />
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:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" colspan="2" | Name, Title, and Series Authority Controlled Headings<br />
|-<br />
|Personal Names||100, 700<br />
|-<br />
|Corporate Names||110, 710<br />
|-<br />
|Conference Names||111, 711<br />
|-<br />
|Uniform Titles||130, 240, 730<br />
|-<br />
|Uniform Titles in a $t||600, 610, 611, 700, 710, 711<br />
|-<br />
|Series||400, 410, 411, 440, 800, 810, 811, 830<br />
|}<br />
<div style=clear:both></div><br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" colspan="2" |Subject Authority Controlled Headings<br />
|-<br />
|Personal Names||600<br />
|-<br />
|Corporate Names||610<br />
|-<br />
|Conference Names||611<br />
|-<br />
|Uniform Titles||630<br />
|-<br />
|Topical||650<br />
|-<br />
|Geographic||651<br />
|-<br />
|Genre||655<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Subfields disregarded===<br />
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:<br />
<br />
<font size="3"><br />
810 2 $a John Bartholomew and Son. $t Bartholomew world travel series <font color="red">;$v 10.</font><br />
130 0 <font color="red">$6 880-01</font> $a ”Hsuuan lai his kan” his lieh.<br />
440 4 $a Romanica Gothoburgensia <font color="red">;$v 12, 16 $x 0080-3863</font></font><br />
<br />
===Subfields matched or ignored===<br />
The table below shows the subfields that are included in the MARS 2.0 authority matching process:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | MARC Field !!style="background:silver" | Subfields Retained During Matching !! style="background:silver" | Subfields Ignored During Matching<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|730 || a d f g h k l m n o p r s t y z || v w x 2 3 5 6<br />
|-<br />
|440 || a n p || v w x 6<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|630 || a d f g h k l m n o p r s t v x y z || w 2 3 5 6<br />
|-<br />
|650 || a b c d v x y z || e w 2 3 6<br />
|-<br />
|651 || a b v x y z || w 2 3 6<br />
|-<br />
|655 || a b c v x y z || e w 2 3 6<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Normalization===<br />
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:<br />
*Alphabetic characters are converted to '''uppercase'''<br />
*The '''first comma will be retained''' in $a for personal name headings<br />
*All other punctuation is '''removed'''<br />
*Certain '''diacritics''' and '''hyphens''' are left in for JACKPHY normalization<br />
*All other diacritics are '''removed'''<br />
*Special characters are replaced by an '''alphabetic equivalent'''<br />
*Subfield codes are '''removed'''<br />
*Subfield delimiters for '''all but first subfield''' will be left in<br />
<br />
<font size="3">'''bib record heading''':<br />
<font color="red">$a</font> Architecture $<font color="red">z</font> Brazil $<font color="red">x</font> S<font color="red">'</font>ao Paulo <font color="red">(</font>State<font color="red">)</font><br />
<br />
'''normalized heading''':<br />
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE</font><br />
<br />
Notice the subfield codes and the diacritic in '''S'ao Paulo''' have been discarded when constructing the normalized form of the heading.<br />
<br />
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.<br />
<br />
For this example, the normalized form of the established heading '''1XX''' in the authority record is:<br />
<br />
<font size="3">'''authority heading''':<br />
<font color="red">$a</font> Architecture $<font color="red">z</font> Brazil $<font color="red">z</font> S<font color="red">~</font>ao Paulo <font color="red">(</font>State<font color="red">)</font><br />
<br />
'''normalized heading''':<br />
ARCHITECTURE $ BRAZIL $ SAO PAULO STATE</font><br />
<br />
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.<br />
<br />
The bibliographic heading then contains the correct diacritic ~ instead of ' and the subfield code for '''S'ao Paulo''' has been corrected to '''$z'''.<br />
<br />
== Topics ==<br />
* [[Step 3.1|Step 3.1]] - Generic Name Headings<br />
* [[Step 3.2|Step 3.2]] - Tag Flipping<br />
* [[Step 3.3|Step 3.3]] - Partial Matches<br />
* [[Step 3.4|Step 3.4]] - Split Headings<br />
* [[Step 3.5|Step 3.5]] - Series Processing<br />
* [[Step 3.6|Step 3.6]] - Subdivision Updates<br />
* [[Step 3.7|Step 3.7]] - Childrens Matching<br />
* [[Step 3.8|Step 3.8]] - MESH Matching<br />
* [[Step 3.9|Step 3.9]] - Canadian Matching<br />
* [[Step 3.10|Step 3.10]] - Local Bibliographic Subject Matching<br />
* [[Step 3.11|Step 3.11]] - Genre Form Matching<br />
* [[Step 3.12|Step 3.12]] - Local Fields in Authority Records<br />
* [[Step 3.13|Step 3.13]] - Local Authority Master<br />
* [[Step 3.14|Step 3.14]] - JACKPHY Vernacular<br />
* [[Step 3.15|Step 3.15]] - Pseudonyms<br />
* [[Step 3.16|Step 3.16]] - Deblinding XRefs<br />
<br />
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.<br />
<br />
==links==<br />
<center><font size="4">[[Step 3.1|3.1]] - [[Step 3.2|3.2]] - [[Step 3.3|3.3]] - [[Step 3.4|3.4]] - [[Step 3.5|3.5]] - [[Step 3.6|3.6]] - [[Step 3.7|3.7]] - [[Step 3.8|3.8]] - [[Step 3.9|3.9]] - [[Step 3.10|3.10]] - [[Step 3.11|3.11]] - [[Step 3.12|3.12]] - [[Step 3.13|3.13]] - [[Step 3.14|3.14]] - [[Step 3.15|3.15]] - [[Step 3.16|3.16]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.11Step 2.112016-08-30T15:56:00Z<p>Nate: /* Accelerated Reader */</p>
<hr />
<div>==Step 2.10: Accelerated Reader & Lexile Measures==<br />
[[Image:a2-10.png]]<br><br><br />
MARS 2.0 offers two types of enrichment options for your collection of juvenile records: accelerated reader & lexile measures. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Accelerated Reader===<br />
For more information about Accelerated Reader, quiz points and reading levels, please visit http://www.renaissance.com/:<br/><br />
Accelerated Reader (AR) is a computer program that helps teachers and librarians manage and monitor children’s independent reading practice. Your child picks<br />
a book at his own level and reads it at his own pace. When finished, your child takes a short quiz on the computer. (Passing the quiz is an<br />
indication that your child understood what was read.) AR gives children, teachers, and librarians feedback based on the quiz results, which<br />
the teacher then uses to help your child set goals and direct ongoing reading practice.<br />
<br />
Children using AR choose their own books to read, rather than having one<br />
assigned to them. This makes reading a much more enjoyable experience<br />
as they can choose books that are interesting to them.<br />
<br />
Teachers and librarians help your child choose books at an appropriate<br />
readability level that are challenging without being frustrating, ensuring<br />
that your child can pass the quiz and experience success. <br />
<br />
Here is an example of a before/after record with the AR enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">526 ## $a Accelerated Reader $b UG $c 5.1 $d 17 $e 17 $z 166237</font></font><br />
<br />
===Lexile Measures===<br />
For more information about Lexile Measures, please visit '''www.lexile.com''':<br/><br />
The Lexile framework is a scientific way to match readers with text using the same scale. Recognized as the standard for matching readers with texts, Lexile&#174; measures connect learners of all ages with resources at the right level of challenge. Lexile measures provide a clear way to monitor progress toward college and career readiness.<br />
<br />
Here is an example of a before/after record with the Lexile enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">521 8# $a HL720L $b Lexile</font></font><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/RDA_3.0RDA 3.02016-07-13T16:32:30Z<p>Nate: /* Sample GMD to CMC conversion table */</p>
<hr />
<div>==RDA 3.0: GMD to CMC Conversion==<br />
This phase of RDA processing comprises a series of routines that compare<br />
existing GMDs (245 $h) as well as specific positions of the leader and fixed fields<br />
to determine the best RDA Content Type [http://access.rdatoolkit.org/document.php?id=rdachp6&target=rda6-3410# RDA 6.9] (RDA), Media Type [http://access.rdatoolkit.org/document.php?id=rdachp3&target=rda3-2026#rda3-2026 RDA 3.2] (RDA), and Carrier Type [http://access.rdatoolkit.org/document.php?id=rdachp3&target=rda3-2026#rda3-2026 RDA 3.3] (RDA) types to add to<br />
the 33X fields in your records.<br />
<br />
===Sample GMD to CMC conversion table===<br />
Here is a sample GMD to CMC conversion table. The full table consists<br />
of over 1,400 different variations. Fields taken into account in adding the 33X<br />
include the Leader, 007, 008, 245 $h and 300 $a.<br />
<br />
If your local practices for assigning GMD or CMC differ from MARS 2.0 processing, please<br />
contact your project manager to discuss options for altering the way GMDs and<br />
CMCs are processed in your records.<br />
<br />
'''Note''': ''Custom mappings can also be generated upon request.''<br />
<br />
'''GMD = 245 $h [sound recording]<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | LDR/06<br />
! style="background:silver" | 007/00<br />
! style="background:silver" | 007/01<br />
! style="background:silver" | 008/30,31<br />
! style="background:silver" | Content Type (336)<br />
! style="background:silver" | Media Type (337)<br />
! style="background:silver" | Carrier Type (338)<br />
|-<br />
| i || s || g || s || sounds || audio || audio cartridge<br />
|-<br />
| i || s || e || s || sounds || audio || audio cylinder<br />
|-<br />
| i || s || d || s || sounds || audio || audio disc<br />
|-<br />
| i || s || i || s || sounds || audio || sound track reel<br />
|-<br />
| i || s || q || s || sounds || audio || audio roll<br />
|-<br />
| i || s || s || s || sounds || audio || audiocassette<br />
|-<br />
| i || s || t || s || sounds || audio || audiotape reel<br />
|-<br />
| i || s || z || s || sounds || audio || other audio carrier<br />
|-<br />
| i || s || g || || spoken word || audio || audio cartridge<br />
|-<br />
| i || s || e || || spoken word || audio || audio cylinder<br />
|-<br />
| i || s || d || || spoken word || audio || audio disc<br />
|-<br />
| i || s || i || || spoken word || audio || sound track reel<br />
|}<br />
<div style=clear:both></div><br />
<br />
== Topics==<br />
* [[RDA_3.1|Step 3.1]] - GMD Standardization<br />
* [[RDA_3.2|Step 3.2]] - GMD Processing<br />
* [[RDA_3.3|Step 3.3]] - CMC Processing<br />
<br />
==links==<br />
<center><font size="4">[[RDA_3.1|3.1]] - [[RDA_3.2|3.2]] - [[RDA_3.3|3.3]]<br />
<hr><br />
[[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]]</font></center><br />
[[category:RDA Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Authority_Control_Client_DemographicsAuthority Control Client Demographics2016-07-12T20:39:09Z<p>Nate: /* BY Library ILS */</p>
<hr />
<div>==Authority Control Backstage Library Works Client Demographics==<br />
This data has been updated as of July 2016.<br />
<br />
===By Library Type===<br />
Library Type defined as the following: If we do not have a count we assume it is small.<br />
<br />
* 27% - Large Academic (over 500,000 bibs)<br />
* 26% - Small Academic (under 500,000 Bibs)<br />
* 8% - Large Public (over 500,000 bibs)<br />
* 17% - Small Public (under 500,000 bibs)<br />
* 23% - Others, Special Libraries, Law Libraries etc.<br />
<br />
Please note that consortia are represented within the other category listed above.<br />
<br />
[[Image:demo-1.png]]<br />
<hr><br />
<br />
===Territory by Geographic Area===<br />
Library Territory defined in conjunction with Sales Territory:<br />
<br />
* 19% - West - AK, AZ, CA, HI, ID, NV, OR, UT, WA<br />
* 22% - Southern Tier - AL, AR, CO, FL, GA, KS, LA, MO, MS, NC, NM, OK, SC, TN, TX<br />
* 17% - Northern Tier - IA, IL, IN, MI, MN, MT, ND, NE, SD, WI, WY<br />
* 17% - Mid-Atlantic - DC, KY, VA, WV, NY - DE, MD, NJ, NY, PA<br />
* 15% - Northeast - CT, MA, ME, NH, OH, RI, VT<br />
* 4% - Canada<br />
* 6% - Europe & rest of the world<br />
<br />
[[Image:demo-2.png]]<br />
<hr><br />
===BY Library ILS===<br />
<br />
Library ILS:<br/><br />
[[Image:demo-3.png]]<br />
<br />
* 20% - Ex Libris Aleph, Alma, Voyager<br />
** 20% - Aleph<br />
** 17% - Alma<br />
** 63% - Voyager<br />
[[Image:demo-exl.png]]<br />
<hr><br />
<br />
* 20% - Sirsi Dynix - Symphony, Horizon<br />
** 59% - Symphony<br />
** 41% - Horizon<br />
<br />
[[Image:demo-sd.png]]<br />
<hr><br />
* 50% - Innovative III (Millennium, Polaris, Sierra, VTLS)<br />
** 43% - Millennium<br />
** 11% - Polaris<br />
** 45% - Sierra<br />
** 1% - VTLS<br />
[[Image:demo-iii.png]]<br />
<hr><br />
<br />
* 7% - Others or unknown (Spydus, CARL, Kuali OLE, LISTEN2000, Koha)<br />
* 3% - Evergreen<br />
<br />
<hr><br />
<br />
[[category:Authority_Control]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Authority_Control_Client_DemographicsAuthority Control Client Demographics2016-07-12T20:38:16Z<p>Nate: /* BY Library ILS */</p>
<hr />
<div>==Authority Control Backstage Library Works Client Demographics==<br />
This data has been updated as of July 2016.<br />
<br />
===By Library Type===<br />
Library Type defined as the following: If we do not have a count we assume it is small.<br />
<br />
* 27% - Large Academic (over 500,000 bibs)<br />
* 26% - Small Academic (under 500,000 Bibs)<br />
* 8% - Large Public (over 500,000 bibs)<br />
* 17% - Small Public (under 500,000 bibs)<br />
* 23% - Others, Special Libraries, Law Libraries etc.<br />
<br />
Please note that consortia are represented within the other category listed above.<br />
<br />
[[Image:demo-1.png]]<br />
<hr><br />
<br />
===Territory by Geographic Area===<br />
Library Territory defined in conjunction with Sales Territory:<br />
<br />
* 19% - West - AK, AZ, CA, HI, ID, NV, OR, UT, WA<br />
* 22% - Southern Tier - AL, AR, CO, FL, GA, KS, LA, MO, MS, NC, NM, OK, SC, TN, TX<br />
* 17% - Northern Tier - IA, IL, IN, MI, MN, MT, ND, NE, SD, WI, WY<br />
* 17% - Mid-Atlantic - DC, KY, VA, WV, NY - DE, MD, NJ, NY, PA<br />
* 15% - Northeast - CT, MA, ME, NH, OH, RI, VT<br />
* 4% - Canada<br />
* 6% - Europe & rest of the world<br />
<br />
[[Image:demo-2.png]]<br />
<hr><br />
===BY Library ILS===<br />
<br />
Library ILS:<br />
[[Image:demo-3.png]]<br />
<br />
* 20% - Ex Libris Aleph, Alma, Voyager<br />
** 20% - Aleph<br />
** 17% - Alma<br />
** 63% - Voyager<br />
[[Image:demo-exl.png]]<br />
<hr><br />
<br />
* 20% - Sirsi Dynix - Symphony, Horizon<br />
** 59% - Symphony<br />
** 41% - Horizon<br />
<br />
[[Image:demo-sd.png]]<br />
<hr><br />
* 50% - Innovative III (Millennium, Polaris, Sierra, VTLS)<br />
** 43% - Millennium<br />
** 11% - Polaris<br />
** 45% - Sierra<br />
** 1% - VTLS<br />
[[Image:demo-iii.png]]<br />
<hr><br />
<br />
* 7% - Others or unknown (Spydus, CARL, Kuali OLE, LISTEN2000, Koha)<br />
* 3% - Evergreen<br />
<br />
<hr><br />
<br />
[[category:Authority_Control]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/File:Demo-3.pngFile:Demo-3.png2016-07-12T20:37:08Z<p>Nate: uploaded a new version of &quot;File:Demo-3.png&quot;</p>
<hr />
<div></div>Natehttps://ac.bslw.com/community/wiki/index.php/Authority_Control_Client_DemographicsAuthority Control Client Demographics2016-07-12T20:36:17Z<p>Nate: </p>
<hr />
<div>==Authority Control Backstage Library Works Client Demographics==<br />
This data has been updated as of July 2016.<br />
<br />
===By Library Type===<br />
Library Type defined as the following: If we do not have a count we assume it is small.<br />
<br />
* 27% - Large Academic (over 500,000 bibs)<br />
* 26% - Small Academic (under 500,000 Bibs)<br />
* 8% - Large Public (over 500,000 bibs)<br />
* 17% - Small Public (under 500,000 bibs)<br />
* 23% - Others, Special Libraries, Law Libraries etc.<br />
<br />
Please note that consortia are represented within the other category listed above.<br />
<br />
[[Image:demo-1.png]]<br />
<hr><br />
<br />
===Territory by Geographic Area===<br />
Library Territory defined in conjunction with Sales Territory:<br />
<br />
* 19% - West - AK, AZ, CA, HI, ID, NV, OR, UT, WA<br />
* 22% - Southern Tier - AL, AR, CO, FL, GA, KS, LA, MO, MS, NC, NM, OK, SC, TN, TX<br />
* 17% - Northern Tier - IA, IL, IN, MI, MN, MT, ND, NE, SD, WI, WY<br />
* 17% - Mid-Atlantic - DC, KY, VA, WV, NY - DE, MD, NJ, NY, PA<br />
* 15% - Northeast - CT, MA, ME, NH, OH, RI, VT<br />
* 4% - Canada<br />
* 6% - Europe & rest of the world<br />
<br />
[[Image:demo-2.png]]<br />
<hr><br />
===BY Library ILS===<br />
<br />
Library ILS:<br />
<br />
* 20% - Ex Libris Aleph, Alma, Voyager<br />
** 20% - Aleph<br />
** 17% - Alma<br />
** 63% - Voyager<br />
* 20% - Sirsi Dynix - Symphony, Horizon<br />
** 59% - Symphony<br />
** 41% - Horizon<br />
* 50% - Innovative III (Millennium, Polaris, Sierra, VTLS)<br />
** 43% - Millennium<br />
** 11% - Polaris<br />
** 45% - Sierra<br />
** 1% - VTLS<br />
* 7% - Others or unknown (Spydus, CARL, Kuali OLE, LISTEN2000, Koha)<br />
* 3% - Evergreen<br />
<br />
[[Image:demo-3.png]]<br />
<hr><br />
<br />
[[category:Authority_Control]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Authority_Control_Client_DemographicsAuthority Control Client Demographics2016-07-12T20:01:22Z<p>Nate: </p>
<hr />
<div>==Authority Control Backstage Library Works Client Demographics==<br />
This data has been updated as of July 2016.<br />
<br />
===By Library Type===<br />
Library Type defined as the following: If we do not have a count we assume it is small.<br />
<br />
* 27% - Large Academic (over 500,000 bibs)<br />
* 26% - Small Academic (under 500,000 Bibs)<br />
* 8% - Large Public (over 500,000 bibs)<br />
* 17% - Small Public (under 500,000 bibs)<br />
* 23% - Others, Special Libraries, Law Libraries etc.<br />
<br />
Please note that consortia are represented within the other category listed above.<br />
<br />
[[Image:demo-1.png]]<br />
<br />
===Territory by Geographic Area===<br />
Library Territory defined in conjunction with Sales Territory:<br />
<br />
* 19% - West - AK, AZ, CA, HI, ID, NV, OR, UT, WA<br />
* 22% - Southern Tier - AL, AR, CO, FL, GA, KS, LA, MO, MS, NC, NM, OK, SC, TN, TX<br />
* 17% - Northern Tier - IA, IL, IN, MI, MN, MT, ND, NE, SD, WI, WY<br />
* 17% - Mid-Atlantic - DC, KY, VA, WV, NY - DE, MD, NJ, NY, PA<br />
* 15% - Northeast - CT, MA, ME, NH, OH, RI, VT<br />
* 4% - Canada<br />
* 6% - Europe & rest of the world<br />
<br />
===BY Library ILS===<br />
<br />
Library ILS:<br />
<br />
* 20% - Ex Libris Aleph, Alma, Voyager<br />
** 20% - Aleph<br />
** 17% - Alma<br />
** 63% - Voyager<br />
* 20% - Sirsi Dynix - Symphony, Horizon<br />
** 59% - Symphony<br />
** 41% - Horizon<br />
* 50% - Innovative III (Millennium, Polaris, Sierra, VTLS)<br />
** 43% - Millennium<br />
** 11% - Polaris<br />
** 45% - Sierra<br />
** 1% - VTLS<br />
* 7% - Others or unknown (Spydus, CARL, Kuali OLE, LISTEN2000, Koha)<br />
* 3% - Evergreen<br />
<br />
[[category:Authority_Control]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/File:Demo-sd.pngFile:Demo-sd.png2016-07-12T19:57:15Z<p>Nate: </p>
<hr />
<div></div>Natehttps://ac.bslw.com/community/wiki/index.php/File:Demo-iii.pngFile:Demo-iii.png2016-07-12T19:57:03Z<p>Nate: </p>
<hr />
<div></div>Natehttps://ac.bslw.com/community/wiki/index.php/File:Demo-exl.pngFile:Demo-exl.png2016-07-12T19:56:51Z<p>Nate: </p>
<hr />
<div></div>Natehttps://ac.bslw.com/community/wiki/index.php/File:Demo-3.pngFile:Demo-3.png2016-07-12T19:56:35Z<p>Nate: uploaded a new version of &quot;File:Demo-3.png&quot;</p>
<hr />
<div></div>Natehttps://ac.bslw.com/community/wiki/index.php/File:Demo-2.pngFile:Demo-2.png2016-07-12T19:56:22Z<p>Nate: </p>
<hr />
<div></div>Natehttps://ac.bslw.com/community/wiki/index.php/File:Demo-3.pngFile:Demo-3.png2016-07-12T19:56:09Z<p>Nate: </p>
<hr />
<div></div>Natehttps://ac.bslw.com/community/wiki/index.php/File:Demo-1.pngFile:Demo-1.png2016-07-12T19:55:44Z<p>Nate: </p>
<hr />
<div></div>Natehttps://ac.bslw.com/community/wiki/index.php/Authority_Control_Client_DemographicsAuthority Control Client Demographics2016-07-11T21:49:21Z<p>Nate: </p>
<hr />
<div><font size = "4">'''<br />
<br />
'''</font><br />
<br />
<font size = "4">'''Authority Control Backstage Library Works Client Demographics'''</font><br />
<br />
<font size = "4">'''July 2016'''</font><br />
<br />
'''By Library Type'''<br />
<br />
Library Type defined as the following: If we do not have a count we assume it is small.<br />
<br />
* 27% - Large Academic (over 500,000 bibs)<br />
* 26% - Small Academic (under 500,000 Bibs)<br />
* 8% - Large Public (over 500,000 bibs)<br />
* 17% - Small Public (under 500,000 bibs)<br />
* 23% - Others, Special Libraries, Law Libraries etc.<br />
<br />
Please note that we have consortia are represented within the other category listed above.<br />
<br />
<hr><br />
<br />
'''Territory by Geographic Area'''<br />
<br />
Library Territory defined in conjunction with Sales Territory:<br />
<br />
* 19% - West - AK, AZ, CA, HI, ID, NV, OR, UT, WA<br />
* 22% - Southern Tier - AL, AR, CO, FL, GA, KS, LA, MO, MS, NC, NM, OK, SC, TN, TX<br />
* 17% - Northern Tier - IA, IL, IN, MI, MN, MT, ND, NE, SD, WI, WY<br />
* 17% - Mid-Atlantic - DC, KY, VA, WV, NY - DE, MD, NJ, NY, PA<br />
* 15% - Northeast - CT, MA, ME, NH, OH, RI, VT<br />
* 4% - Canada<br />
* 6% - Europe & rest of the world<br />
<br />
<hr><br />
<br />
'''BY Library ILS'''<br />
<br />
Library ILS:<br />
<br />
* 20% - Ex Libris Aleph, Alma, Voyager<br />
** 20% - Aleph<br />
** 17% - Alma<br />
** 63% - Voyager<br />
* 20% - Sirsi Dynix - Symphony, Horizon<br />
** 59% - Symphony<br />
** 41% - Horizon<br />
* 50% - Innovative III (Millennium, Polaris, Sierra, VTLS)<br />
** 43% - Millennium<br />
** 11% - Polaris<br />
** 45% - Sierra<br />
** 1% - VTLS<br />
* 7% - Others or unknown (Spydus, CARL, Kuali OLE, LISTEN2000, Koha)<br />
* 3% - Evergreen<br />
<br />
[[category:Authority_Control]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Terminology-UTerminology-U2016-07-11T21:41:54Z<p>Nate: /* Unicode Normalization */</p>
<hr />
<div>==Terminology… U==<br />
<br />
===Unauthorized Heading (form)===<br />
4xx of authority record ''see See From Tracings''<br />
<br />
===Unicode===<br />
In [http://en.wikipedia.org/wiki/Computing computing], '''Unicode''' is an [http://en.wikipedia.org/wiki/Industry_standard industry standard] allowing [http://en.wikipedia.org/wiki/Computer computers] to consistently represent and manipulate [http://en.wikipedia.org/wiki/Character_(computing) text] expressed in most of the world<nowiki>’</nowiki>s [http://en.wikipedia.org/wiki/Writing_system writing systems]. Developed in tandem with the [http://en.wikipedia.org/wiki/Universal_Character_Set Universal Character Set] standard and published in book form as ''The Unicode Standard'', Unicode consists of a repertoire of more than 100,000 [http://en.wikipedia.org/wiki/Character_(computing) characters], a set of code charts for visual reference, an encoding methodology and set of standard [http://en.wikipedia.org/wiki/Character_encoding character encodings], an enumeration of character properties such as upper and lower [http://en.wikipedia.org/wiki/Letter_case case], a set of reference data [http://en.wikipedia.org/wiki/Computer_file computer files], and a number of related items. (wp)<br />
<br />
===Unicode Normalization===<br />
Unicode '''normalization''' is a form of [http://en.wikipedia.org/wiki/Text_normalization text normalization] that transforms equivalent sequences of characters into the same representation, called a '''normalization''' '''form''' in the Unicode standard, but which will be called simply [http://en.wikipedia.org/wiki/Normal_form_(term_rewriting) normal form] in this article. For each of the two equivalence notions, Unicode defines two canonical forms, one fully composed, and one fully decomposed, resulting in four normal forms, abbreviated NFC, NFD, NFKC, and NFKD, which are detailed in this article. Unicode normalization is important in Unicode text processing applications, because it affects the semantics of comparing, searching, and sorting Unicode sequences. (wp)<br />
<br />
===Uniform Titles===<br />
A uniform title in [http://en.wikipedia.org/wiki/Library_catalog library cataloging] is a title assigned to a work which either has no title or has appeared under more than one title. It is part of [http://en.wikipedia.org/wiki/Authority_control authority control]. A uniform title allows all of the works to fall under one title and will reference all of the items to which the uniform title applies. (wp) A heading consisting of the title by which an item or a series is identified for cataloging purposes when the title is not entered under a personal, corporate, meeting, or jurisdiction name in a name/title heading construction. (m21)<br />
<br />
===Undifferentiated Authority Records===<br />
An undifferentiated heading lacks qualifiers that make it unique. This is usually found with name headings. A birth or death date is often used to differentiate. Sometimes undifferentiated headings are not qualified and are used to represent more than one person. (ac)<br />
<br />
===Unestablished Heading===<br />
A heading that is ''not'' authorized for use in other MARC records as the lead element of a main, added, series, or subject access field. An unestablished heading may be a reference to a variant form of the established heading, a form of the heading used only for authority file organizational purposes, or a subject subdivision that is authorized for use with an established heading in an extended subject heading. In authority records, unestablished headings are used in the 1XX (heading) and 4XX (tracing) fields of reference (008/09, code b or c), subdivision (code d), reference and subdivision (code g), and node label (code e) records. An unestablished heading may also be used in the 4XX fields of established heading (code a or f) records. (m21)<br />
<br />
===Unmatched headings===<br />
Headings under authorization in the bibliographic record, 1XX, 4XX, 6XX, 7XX, 8XX, that do not have a national level authority record associated with it. 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 Authority Update, MARS 2.0 programs search for a national-level authority record corresponding to these unmatched headings. (mpg)<br />
<br />
===Untraced===<br />
A series is "untraced" if 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. Series are treated as '''untraced''' if the authority match does not have a 645 $a "t" '''AND''' 008<nowiki>[</nowiki>12<nowiki>]</nowiki> = <nowiki>’</nowiki>c<nowiki>’</nowiki> (mpg)<br />
<br />
===Uploading===<br />
Uploading describes the [http://en.wikipedia.org/wiki/File_transfer transfer of electronic data] between two computers or similar systems. To ''upload'', is to send data from a local system to a remote system, FTP server, or website. The difference between uploading and downloading is downloading means to receive and uploading means to send. (google)<br />
<br />
===Usage Code===<br />
The ''MARC 21 Format for Authority Data'' identifies three categories of heading usage in records: '''main''' or '''added entry''' (008/14); '''subject added entry''' (008/15); and '''series added entry''' (008/16). Only established headings may be used as the lead element of access points in bibliographic records. Name, name/title, and uniform title established headings may be appropriately used as any one, two, or three of the 008/14-16 usage categories. Topical term and extended subject headings may be used only as subject added entries. Subdivision headings may be used only in extended subject heading added entries. (m21)<br />
<br />
===USMARC===<br />
''see MARC21'' - The American version of MARC became known as USMARC in the 1980s. It merged with the Canadian version of MARC (CAN/MARC) in 1997 to create MARC 21. (google)<br />
<br />
===UTF-8 Format===<br />
'''UTF-8''' (8-[http://en.wikipedia.org/wiki/Bit bit] [http://en.wikipedia.org/wiki/Universal_Character_Set UCS]/[http://en.wikipedia.org/wiki/Unicode_Transformation_Format Unicode Transformation Format]) is a [http://en.wikipedia.org/wiki/Variable-width_encoding variable-length] [http://en.wikipedia.org/wiki/Character_encoding character encoding] for [http://en.wikipedia.org/wiki/Unicode Unicode]. It is able to represent any character in the Unicode standard, yet the initial encoding of byte codes and character assignments for UTF-8 is [http://en.wikipedia.org/wiki/Backwards_compatible backwards compatible] with [http://en.wikipedia.org/wiki/ASCII ASCII]. For these reasons, it is steadily becoming the preferred encoding for [http://en.wikipedia.org/wiki/E-mail e-mail], [http://en.wikipedia.org/wiki/Web_pages web pages]<sup><nowiki>[</nowiki>1<nowiki>]</nowiki></sup>, and other places where characters are [http://en.wikipedia.org/wiki/Computer_data_storage stored] or [http://en.wikipedia.org/wiki/Stream_(computing) streamed]. (wp) <br />
<br />
[[category:General Information]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Terminology-MTerminology-M2016-07-11T21:40:14Z<p>Nate: /* MARS Authority Control Profiles */</p>
<hr />
<div>==Terminology… M==<br />
<br />
===Manual Review===<br />
Manual Review is a visual examination of authority controlled headings in your bibliographic records. MARS 2.0 Manual Review is performed by experienced MARS 2.0 staff librarians and library technicians, and results in a catalog of records with fewer errors and inconsistencies than machine processing alone can provide. (mpg)<br />
<br />
===MARC===<br />
MARC is an acronym, used in the field of library science that stands for [http://en.wikipedia.org/wiki/Machine_readable '''MA'''chine-'''R'''eadable] [http://en.wikipedia.org/wiki/Cataloging '''C'''ataloging]. The '''MARC standards''' consist of the MARC formats, which are standards for the [http://en.wikipedia.org/wiki/Representation representation] and [http://en.wikipedia.org/wiki/Communication communication] of bibliographic and related information in machine-readable form, and related documentation. It defines a [http://en.wikipedia.org/wiki/Bibliography bibliographic] [http://en.wikipedia.org/wiki/Data data] format that was developed by [http://en.wikipedia.org/wiki/Henriette_Avram Henriette Avram] at the [http://en.wikipedia.org/wiki/Library_of_Congress Library of Congress] beginning in the 1960s. It provides the [http://en.wikipedia.org/wiki/Communications_protocol protocol] by which [http://en.wikipedia.org/wiki/Computers computers] exchange, use, and interpret bibliographic information. Its [http://en.wikipedia.org/wiki/Data_element data elements] make up the foundation of most [http://en.wikipedia.org/wiki/Library_catalog library catalogs] used today. (wp)<br />
<br />
===MARC 8 format===<br />
MARC-8 is based on [http://en.wikipedia.org/wiki/ISO_2022 ISO 2022] and allows the use of Hebrew, Cyrillic, Arabic, Greek, and East Asian scripts. (wp)<br />
<br />
===MARC-21 Field Conversions===<br />
During the automated authority control process there are several areas of the bibliographic record that require more complex changing to the tag or subfield. 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: (mpg)<br />
<br />
* Add missing format data<br />
* Add missing subfield data<br />
* Complex field conversions<br />
<br />
===MARC 21 Format===<br />
MARC 21 is a result of the combination of the United States and Canadian MARC formats (USMARC and CAN/MARC). MARC21 is based on the [http://en.wikipedia.org/wiki/American_National_Standards_Institute ANSI] standard Z39.2, which allows users of different software products to communicate with each other and to exchange data.<sup><nowiki>[</nowiki>4<nowiki>]</nowiki></sup> MARC 21 was designed to redefine the original MARC record format for the 21st century and to make it more accessible to the international community. MARC 21 has formats for the following five types of data: Bibliographic Format, Authority Format, Holdings Format, Community Format, and Classification Data Format.<sup><nowiki>[</nowiki>5<nowiki>]</nowiki></sup> Currently MARC 21 has been implemented successfully by The British Library, the European Institutions and the major library institutions in the United States, and [http://en.wikipedia.org/wiki/Canada Canada]. MARC 21 allows the use of two character sets, either MARC-8 or [http://en.wikipedia.org/wiki/Unicode Unicode] encoded as [http://en.wikipedia.org/wiki/UTF-8 UTF-8]. (wp)<br />
<br />
===MARC delimiter===<br />
A character or sequence of characters found in a MARC record marking the beginning or end of a unit of data. Field delimiters separate data fields. Record delimiters separate groups of fields. All records contain the following standard MARC delimiters: (wp, mpg) ''' '''''see also subfield delimiter''<br />
<br />
* Record terminators (ACSII 1d16)<br />
* Field terminators (ASCII 1E16)<br />
* Subfield delimiters (ASCII 1f16)<br />
<br />
===MARC Organizational Code===<br />
Specific code created for the MARC record to represent an organization. The code can be found in the 040 Tag of the Authority Record. It is used when ever an organization modifies the MARC record. For Backstage it is UtOrBLW. MARC code for or the name of the organization(s) that created the original bibliographic record, assigned MARC content designation and transcribed the record into machine-readable form, or modified (except for the addition of holdings symbols) an existing MARC record. These data and the code in 008/39 (Cataloging source) specify the parties responsible for the bibliographic record. See Appendix I: [http://www.loc.gov/marc/bibliographic/ecbdorg.html <font color="#0000FF"><u>''Organization Code Sources]''</u> </font>for a listing of sources used in MARC 21 records. (m21)<br />
<br />
===MARC Tag===<br />
Often referred to as a MARC Field, a MARC tag is a string of data prefaced by a three digit number. It represents a unique part of the bibliographic record. For example, all 100 tags are the personal name of the author of a works. There are 999 possible MARC tags, many of which have been established by the library of congress as fields in the various MARC formats. (ac)<br />
<br />
===MARS===<br />
MARS is an acronym '''for MARC Record Service''' '''(MARS)'''. It is automated authority control software originally created by WLN (Western Library Network) in 1989. In 2004 Backstage Library Works partnered with OCLC for the purchase of the OCLC MARS Authority Control services. The MARS software, databases, client files, profiles, and other MARS components were successfully transferred to Backstage Library Work<nowiki>’</nowiki>s care over a six month period, including several months of parallel processing on both OCLC and BSLW systems. In 2008 Backstage Library Works enhanced the software making it compatible with new technology. The current version of the software is called '''MARS 2.0'''. (mpg)<br />
<br />
===MARS Master Authority File===<br />
MARS 2.0 maintains a Master Authority File for each institution that has been supported by any of the MARS 2.0 Authority Control services. A library<nowiki>’</nowiki>s MARS 2.0 Master Authority File can actually consist of a number of separate authority files, based on the profile options selected by the library: (mpg)<br />
<br />
* National-level authority records (separate files for LC, MeSH, NLC, etc.)<br />
* Locally generated records that conflict with LC practices, but are required for your catalog<br />
* Locally generated records to be replaced by national-level records<br />
* National-level authority records with local tags & subfields to be merged with updates in national records<br />
* 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<br />
<br />
===MARS Authority Control Profiles===<br />
A quick reference or set of instructions the automated authority control client fills out to determine how they would like the MARS 2.0 software to process their data. There are six steps/profiles in all that cover the following. (mpg)<br />
<br />
* Step 1 Database<br />
* Step 2 Cleanup<br />
* Step 3 Matching<br />
* Step 4 Output<br />
* Step 5 Reports<br />
* Step 6 Ongoing<br />
<br />
===MARS stamp===<br />
The text '''MARS''' can be added in a subfield $a in a field you specify, for example a 945 field. MARS 2.0 programs can '''stamp''' each bibliographic record with one or all of the following identifiers or only stamp those bibliographic records that were changed during the MARS 2.0 process. (MPG)<br />
<br />
040 $d "UtOrBLW<br />
<br />
MARS Stamp<br />
<br />
Leader byte 23 "M"<br />
<br />
Update/Add 005 Field with date and time stamp<br />
<br />
Other that library specifies.<br />
<br />
===Medical Headings===<br />
''see MeSH''<br />
<br />
===Merge===<br />
''see Local Authority Field Merge''<br />
<br />
===MeSH National Library of Medicine Authority File===<br />
Medical Subject Headings (MeSH) is a huge [http://en.wikipedia.org/wiki/Controlled_vocabulary controlled vocabulary] (or [http://en.wikipedia.org/wiki/Metadata_(computing) metadata] system) for the purpose of [http://en.wikipedia.org/wiki/Index_(publishing) indexing] journal articles and books in the life sciences. Created and updated by the [http://en.wikipedia.org/wiki/United_States_National_Library_of_Medicine United States National Library of Medicine] (NLM), it is used by the [http://en.wikipedia.org/wiki/MEDLINE MEDLINE]/[http://en.wikipedia.org/wiki/PubMed PubMed] article database and by NLM<nowiki>’</nowiki>s catalog of book holdings. MeSH can be browsed and downloaded free of charge on the Internet. The yearly printed version was discontinued in 2007. (wp) The current MeSH authority file contains just over 580,000 authority records for descriptors, qualifiers, and descriptor/qualifier combinations. Over 300,000 new and updated authority records are issued by NLM in the MeSH annual update. (mpg)<br />
<br />
===Metadata===<br />
Metadata (meta data) is "data about data", of any sort in any media. An item of metadata may describe an individual [http://en.wikipedia.org/wiki/Datum datum], or content item, or a collection of data including multiple content items and hierarchical levels, for example a [http://en.wikipedia.org/wiki/Database_schema database schema]. Metadata provides context for data. Metadata is used to facilitate the understanding, characteristics, and management usage of data. (wp)<br />
<br />
===Model Heading===<br />
See [[Terminology-P#Pattern_heading|Pattern heading]]. (lchspa)<br />
<br />
===Multiple matches===<br />
On occasion multiple matches occur when the normalized version of the heading matches two or more national authority records. When this happens the MARS 2.0 software will not replace the bib heading with any of the 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 an optional report '''R10 - Heading Matches Established Headings in Multiple Authority Records'''. (mpg) <br />
<br />
[[category:General Information]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Terminology-MTerminology-M2016-07-11T21:40:01Z<p>Nate: /* MARS Authority Control Profiles */</p>
<hr />
<div>==Terminology… M==<br />
<br />
===Manual Review===<br />
Manual Review is a visual examination of authority controlled headings in your bibliographic records. MARS 2.0 Manual Review is performed by experienced MARS 2.0 staff librarians and library technicians, and results in a catalog of records with fewer errors and inconsistencies than machine processing alone can provide. (mpg)<br />
<br />
===MARC===<br />
MARC is an acronym, used in the field of library science that stands for [http://en.wikipedia.org/wiki/Machine_readable '''MA'''chine-'''R'''eadable] [http://en.wikipedia.org/wiki/Cataloging '''C'''ataloging]. The '''MARC standards''' consist of the MARC formats, which are standards for the [http://en.wikipedia.org/wiki/Representation representation] and [http://en.wikipedia.org/wiki/Communication communication] of bibliographic and related information in machine-readable form, and related documentation. It defines a [http://en.wikipedia.org/wiki/Bibliography bibliographic] [http://en.wikipedia.org/wiki/Data data] format that was developed by [http://en.wikipedia.org/wiki/Henriette_Avram Henriette Avram] at the [http://en.wikipedia.org/wiki/Library_of_Congress Library of Congress] beginning in the 1960s. It provides the [http://en.wikipedia.org/wiki/Communications_protocol protocol] by which [http://en.wikipedia.org/wiki/Computers computers] exchange, use, and interpret bibliographic information. Its [http://en.wikipedia.org/wiki/Data_element data elements] make up the foundation of most [http://en.wikipedia.org/wiki/Library_catalog library catalogs] used today. (wp)<br />
<br />
===MARC 8 format===<br />
MARC-8 is based on [http://en.wikipedia.org/wiki/ISO_2022 ISO 2022] and allows the use of Hebrew, Cyrillic, Arabic, Greek, and East Asian scripts. (wp)<br />
<br />
===MARC-21 Field Conversions===<br />
During the automated authority control process there are several areas of the bibliographic record that require more complex changing to the tag or subfield. 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: (mpg)<br />
<br />
* Add missing format data<br />
* Add missing subfield data<br />
* Complex field conversions<br />
<br />
===MARC 21 Format===<br />
MARC 21 is a result of the combination of the United States and Canadian MARC formats (USMARC and CAN/MARC). MARC21 is based on the [http://en.wikipedia.org/wiki/American_National_Standards_Institute ANSI] standard Z39.2, which allows users of different software products to communicate with each other and to exchange data.<sup><nowiki>[</nowiki>4<nowiki>]</nowiki></sup> MARC 21 was designed to redefine the original MARC record format for the 21st century and to make it more accessible to the international community. MARC 21 has formats for the following five types of data: Bibliographic Format, Authority Format, Holdings Format, Community Format, and Classification Data Format.<sup><nowiki>[</nowiki>5<nowiki>]</nowiki></sup> Currently MARC 21 has been implemented successfully by The British Library, the European Institutions and the major library institutions in the United States, and [http://en.wikipedia.org/wiki/Canada Canada]. MARC 21 allows the use of two character sets, either MARC-8 or [http://en.wikipedia.org/wiki/Unicode Unicode] encoded as [http://en.wikipedia.org/wiki/UTF-8 UTF-8]. (wp)<br />
<br />
===MARC delimiter===<br />
A character or sequence of characters found in a MARC record marking the beginning or end of a unit of data. Field delimiters separate data fields. Record delimiters separate groups of fields. All records contain the following standard MARC delimiters: (wp, mpg) ''' '''''see also subfield delimiter''<br />
<br />
* Record terminators (ACSII 1d16)<br />
* Field terminators (ASCII 1E16)<br />
* Subfield delimiters (ASCII 1f16)<br />
<br />
===MARC Organizational Code===<br />
Specific code created for the MARC record to represent an organization. The code can be found in the 040 Tag of the Authority Record. It is used when ever an organization modifies the MARC record. For Backstage it is UtOrBLW. MARC code for or the name of the organization(s) that created the original bibliographic record, assigned MARC content designation and transcribed the record into machine-readable form, or modified (except for the addition of holdings symbols) an existing MARC record. These data and the code in 008/39 (Cataloging source) specify the parties responsible for the bibliographic record. See Appendix I: [http://www.loc.gov/marc/bibliographic/ecbdorg.html <font color="#0000FF"><u>''Organization Code Sources]''</u> </font>for a listing of sources used in MARC 21 records. (m21)<br />
<br />
===MARC Tag===<br />
Often referred to as a MARC Field, a MARC tag is a string of data prefaced by a three digit number. It represents a unique part of the bibliographic record. For example, all 100 tags are the personal name of the author of a works. There are 999 possible MARC tags, many of which have been established by the library of congress as fields in the various MARC formats. (ac)<br />
<br />
===MARS===<br />
MARS is an acronym '''for MARC Record Service''' '''(MARS)'''. It is automated authority control software originally created by WLN (Western Library Network) in 1989. In 2004 Backstage Library Works partnered with OCLC for the purchase of the OCLC MARS Authority Control services. The MARS software, databases, client files, profiles, and other MARS components were successfully transferred to Backstage Library Work<nowiki>’</nowiki>s care over a six month period, including several months of parallel processing on both OCLC and BSLW systems. In 2008 Backstage Library Works enhanced the software making it compatible with new technology. The current version of the software is called '''MARS 2.0'''. (mpg)<br />
<br />
===MARS Master Authority File===<br />
MARS 2.0 maintains a Master Authority File for each institution that has been supported by any of the MARS 2.0 Authority Control services. A library<nowiki>’</nowiki>s MARS 2.0 Master Authority File can actually consist of a number of separate authority files, based on the profile options selected by the library: (mpg)<br />
<br />
* National-level authority records (separate files for LC, MeSH, NLC, etc.)<br />
* Locally generated records that conflict with LC practices, but are required for your catalog<br />
* Locally generated records to be replaced by national-level records<br />
* National-level authority records with local tags & subfields to be merged with updates in national records<br />
* 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<br />
<br />
===MARS Authority Control Profiles===<br />
A quick reference or set of instructions the automated authority control client fills out to determine how they would like the MARS 2.0 software to process their data. There are seven steps/profiles in all that cover the following. (mpg)<br />
<br />
* Step 1 Database<br />
* Step 2 Cleanup<br />
* Step 3 Matching<br />
* Step 4 Output<br />
* Step 5 Reports<br />
* Step 6 Ongoing<br />
<br />
===MARS stamp===<br />
The text '''MARS''' can be added in a subfield $a in a field you specify, for example a 945 field. MARS 2.0 programs can '''stamp''' each bibliographic record with one or all of the following identifiers or only stamp those bibliographic records that were changed during the MARS 2.0 process. (MPG)<br />
<br />
040 $d "UtOrBLW<br />
<br />
MARS Stamp<br />
<br />
Leader byte 23 "M"<br />
<br />
Update/Add 005 Field with date and time stamp<br />
<br />
Other that library specifies.<br />
<br />
===Medical Headings===<br />
''see MeSH''<br />
<br />
===Merge===<br />
''see Local Authority Field Merge''<br />
<br />
===MeSH National Library of Medicine Authority File===<br />
Medical Subject Headings (MeSH) is a huge [http://en.wikipedia.org/wiki/Controlled_vocabulary controlled vocabulary] (or [http://en.wikipedia.org/wiki/Metadata_(computing) metadata] system) for the purpose of [http://en.wikipedia.org/wiki/Index_(publishing) indexing] journal articles and books in the life sciences. Created and updated by the [http://en.wikipedia.org/wiki/United_States_National_Library_of_Medicine United States National Library of Medicine] (NLM), it is used by the [http://en.wikipedia.org/wiki/MEDLINE MEDLINE]/[http://en.wikipedia.org/wiki/PubMed PubMed] article database and by NLM<nowiki>’</nowiki>s catalog of book holdings. MeSH can be browsed and downloaded free of charge on the Internet. The yearly printed version was discontinued in 2007. (wp) The current MeSH authority file contains just over 580,000 authority records for descriptors, qualifiers, and descriptor/qualifier combinations. Over 300,000 new and updated authority records are issued by NLM in the MeSH annual update. (mpg)<br />
<br />
===Metadata===<br />
Metadata (meta data) is "data about data", of any sort in any media. An item of metadata may describe an individual [http://en.wikipedia.org/wiki/Datum datum], or content item, or a collection of data including multiple content items and hierarchical levels, for example a [http://en.wikipedia.org/wiki/Database_schema database schema]. Metadata provides context for data. Metadata is used to facilitate the understanding, characteristics, and management usage of data. (wp)<br />
<br />
===Model Heading===<br />
See [[Terminology-P#Pattern_heading|Pattern heading]]. (lchspa)<br />
<br />
===Multiple matches===<br />
On occasion multiple matches occur when the normalized version of the heading matches two or more national authority records. When this happens the MARS 2.0 software will not replace the bib heading with any of the 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 an optional report '''R10 - Heading Matches Established Headings in Multiple Authority Records'''. (mpg) <br />
<br />
[[category:General Information]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Terminology-ITerminology-I2016-07-11T21:38:38Z<p>Nate: /* ILS Vendors */</p>
<hr />
<div>==Terminology… I==<br />
<br />
===ILS System===<br />
An '''integrated library system''', or '''ILS''', is an [http://en.wikipedia.org/wiki/Enterprise_resource_planning enterprise resource planning] system for a [http://en.wikipedia.org/wiki/Library library], used to track items owned, orders made, bills paid, and patrons who have borrowed. An ILS is usually comprised of a [http://en.wikipedia.org/wiki/Relational_database relational database], software to act on that database, and two [http://en.wikipedia.org/wiki/Graphical_user_interface graphical user interfaces] (one for patrons, one for staff). Most ILSes separate software functions into discrete programs called modules, which are then integrated into a unified interface. Examples of modules include: acquisitions (ordering, receiving, and invoicing materials), [http://en.wikipedia.org/wiki/Library_catalog cataloging] (classifying and indexing materials), circulation (lending materials to patrons and receiving them back), [http://en.wikipedia.org/wiki/Serial_number serials] (tracking magazine and newspaper holdings), and the [http://en.wikipedia.org/wiki/OPAC OPAC] (public interface for users). Each patron and item has a unique ID in the database that allows the ILS to track its activity. (wp)<br />
<br />
===ILS System Migration===<br />
Typically three to five years after a library has had an Integrated Library System they will consider or need to migrate off of the system to a new. The factors determining a migration and an ILS migration are system performance, software functionality, money and vendor service. (ac)<br />
<br />
===ILS Vendors===<br />
'''Note:''' This list was created in March 2009. If there are any ILS vendors left off please notify Backstage Library Works.<br />
<br />
1. '''Auto-Graphics, Inc.''' - [http://www4.auto-graphics.com/ http://www4.auto-graphics.com/]<br />
* Agent Verso<br />
<br />
2. '''Civica/''' – [http://www.civicaplc.com/AUS/Sectors/Library/ http://www.civicaplc.com/AUS/Sectors/Library/] Joe Keller [mailto:kellerJE@civicacmi.com kellerJE@civicacmi.com] Australia, New Zealand $ South East Asia<br />
* Spydus<br />
<br />
3. '''Companion Corporation''' [http://www.companioncorp.com/ http://www.companioncorp.com/] / Alexandria Library Automation Software [http://www.goalexandria.com/ http://www.goalexandria.com/]<br />
* Alexandria<br />
<br />
4. '''EOS International''' [http://www.eosintl.com/ http://www.eosintl.com/]<br />
* EOS.Web<br />
<br />
5. '''Equinox Software Inc.''' [http://www.esilibrary.com/esi/ http://www.esilibrary.com/esi/] (open source support group)<br />
* Evegreen<br />
<br />
6. '''Ex Libris''' [http://www.exlibris.co.il/ http://www.exlibris.co.il/]<br />
* Alma<br />
* Voyager<br />
* Aleph 500<br />
<br />
7. '''Follett Library Resources''' [http://www.follett.com/ http://www.follett.com/]<br />
* Destiny (Flagship)<br />
<br />
8. '''Info Library and Information Solutions''' [http://vubis-smart.com/html/homeeng.htm http://vubis-smart.com/html/homeeng.htm]<br />
* Vubis Smart – Client/Server ILS (Flagship)<br />
* V-smart – Web Based ILS<br />
<br />
9. '''Innovative Interfaces, Inc.''' [http://www.iii.com/ http://www.iii.com/]<br />
* Millennium<br />
* Sierra<br />
* Polaris<br />
* Virtua<br />
<br />
10. '''Jaywil software Development Inc.''' [http://www.resourcemate.com/privacy.html http://www.resourcemate.com/privacy.html]<br />
* ResourceMate 3.0<br />
<br />
11. '''Liblime''' (open source solutions) [http://liblime.com/koha http://liblime.com/koha]<br />
* Koha<br />
<br />
12. '''MINISIS Inc.''' [http://www.minisisinc.com/ http://www.minisisinc.com/]<br />
* M2L – Management for Libraries<br />
<br />
13. '''OPALS''' (open Source) [http://opals-na.org/ http://opals-na.org/]<br />
<br />
14. '''Sirsi''' [http://www.sirsidynix.com/ http://www.sirsidynix.com/]<br />
* Horizon (legacy)<br />
* Unicorn (Symphony) (Flagship)<br />
* Dynix (Legacy)<br />
<br />
15. '''Lucidea''' [http://www.lucidea.com/ http://www.lucidea.com/]<br />
* Sydney<br />
* Inmagic<br />
* STAR Knowledge Center for Libraries<br />
<br />
16. '''TLC, The Library Corporation''' [http://www.tlcdelivers.com/library-automation/ http://www.tlcdelivers.com/library-automation/]<br />
* Library.solution (Flagship)<br />
* CARL, CARLX (legacy)<br />
(web)<br />
<br />
===Indicator===<br />
The first two character positions in the variable data fields that contain values which interpret or supplement the data found in the field. Indicator values are interpreted independently, that is, meaning is not ascribed to the two indicators taken together. Indicator values may be a lowercase alphabetic or a numeric character. A blank (ASCII SPACE), represented in this document as a #, is used in an undefined indicator position. In a defined indicator position, a blank may be assigned a meaning, or may mean ''no information provided''. (m21)<br />
<br />
===Indirect Geographic Subdivisions===<br />
An indirect geographic subdivision is ordered from largest body to smallest body. An example would be $zKansas$zJefferson County. (mpg)<br />
<br />
===Initial Article===<br />
An '''article''' is a [http://en.wikipedia.org/wiki/Word word] that combines with a [http://en.wikipedia.org/wiki/Noun noun] to indicate the type of reference being made by the noun. The three main articles in the English language are ''the'', ''an'' and ''a''. An initial article occurs at the beginning of the title of many books. In the MARC record it is typically not indexed as part of the title of the book. The filing indicator found in the MARC record determines the first letter of the title to be indexed. (wp, ac)<br />
<br />
===Institution Code===<br />
''see OCLC Institution Code''<br />
<br />
===Interesting Authorities===<br />
The MARS 2.0 automated authority control process allows the user to restrict the number of updated records delivered by choose to receive only authority records that are ''interesting''. MARS 2.0 defines an authority record as interesting if it contains one or more of the following fields: (mpg)<br />
<br />
* 260—Complex ''See'' Reference (Subject)<br />
* 360—Complex ''See Also'' Reference (Subject)<br />
* 4XX—''See From'' Cross Reference<br />
* 5XX—''See From Also'' Cross Reference<br />
* 64X—Series Treatment Note<br />
* 66X—Reference Note<br />
* 678—Biographical or Historical Data<br />
* 680-682, 688—Public General or Tracing Note, Deleted Heading Information, or History Note<br />
<br />
===ISBN===<br />
International Standard Book Number, tag 020. The International Standard Book Number (ISBN) is a unique, numerical [http://en.wikipedia.org/wiki/Commerce commercial] [http://en.wikipedia.org/wiki/Book book] [http://en.wikipedia.org/wiki/Identifier identifier], based upon the 9-digit Standard Book Numbering (SBN) [http://en.wikipedia.org/wiki/Code code] created in the UK. The 10-digit ''International'' Standard Book Number (ISBN) format was developed by the [http://en.wikipedia.org/wiki/International_Organization_for_Standardization International Organization for Standardization] and published as an international standard in 1970. Since [http://en.wikipedia.org/wiki/January_1 1 January] [http://en.wikipedia.org/wiki/2007 2007], International Standard Book Numbers have been 13 digits. (wp)<br />
<br />
===ISSN===<br />
International Standard Series Number, tag 022, is a unique eight-digit number used to identify a print or electronic [http://en.wikipedia.org/wiki/Periodical_publication periodical publication]. The ISSN system was adopted as [http://en.wikipedia.org/wiki/International_standard international standard] [http://en.wikipedia.org/wiki/International_Organization_for_Standardization ISO] 3297 in 1975.''' '''The format of the ISSN is an eight digit number, divided by a hyphen into two four-digit numbers. The last digit, which may be 0–9 or an X, is a [http://en.wikipedia.org/wiki/Check_digit check digit]. (wp) <br />
<br />
[[category:General Information]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Terminology-FTerminology-F2016-07-11T21:32:16Z<p>Nate: /* Faceted classification system */</p>
<hr />
<div>==Terminology… F==<br />
<br />
===Faceted Access for Subject Terminology===<br />
OCLC has created an authority database for FAST headings and made this available for matching against. MARS 2.0 can process your FAST headings via our processing upon your request. The 655 fields would need to have 2nd indicator value of '''7''' and '''$2 fast''' in order for our system to process these genre headings.<br />
<br />
The FAST authority database comprises over 1.7 million authorities.<br />
<br />
FAST authorities allow for a faceted approach to listing subject headings within bibliographic records:<br />
<br />
<font size="3"><br />
<u>LCSH</u><br />
650 #0 $a American loyalists $z England.<br />
651 #0 $a United States $x History $y Revolution, 1775-1783 $v Biography.<br />
650 #0 $a Secret service $z Great Britain.<br />
650 #0 $a Painters $z United States.<br />
<br />
<u>FAST</u><br />
648 #0 $a 1775-1783<br />
650 #0 $a American loyalists<br />
650 #0 $a Revolution (United States, 1775-1783)<br />
650 #0 $a Secret service<br />
650 #0 $a Painters<br />
651 #0 $a England<br />
651 #0 $a United States<br />
651 #0 $a Great Britain<br />
655 #0 $a Biography<br />
655 #0 $a History<br />
</font><br />
<br />
So each term within the original LC subject headings are broken out into a faceted network of headings. This could potentially enable discovery systems to make better links to subjects for patrons. Rather than searching for '''American loyalists in England''' patrons could search for '''American loyalists''' and then decide whether to pursue that to '''England''' or explore other countries with that term.<br />
<br />
===Faceted classification system===<br />
A faceted classification system allows the assignment of multiple classifications to an object, enabling the classifications to be ordered in multiple ways, rather than in a single, pre-determined, [http://en.wikipedia.org/wiki/Taxonomy taxonomic] order. The most prominent use of faceted classification is in faceted navigation systems that enable a user to navigate information hierarchically, going from a category to its sub-categories, but choosing the order in which the categories are presented. This contrasts with traditional taxonomies in which the hierarchy of categories is fixed and unchanging. (wp)<br />
<br />
===False Positives===<br />
A match made by an automated authority control process that is not an authorized match and results in bogus authority data in the authority file and authority headings. (ac) ''(The MARS 2.0 programs have been designed to eliminate the occurrence of "false positives" in authority matching.)''<br />
<br />
===Field===<br />
In [http://en.wikipedia.org/wiki/Computer_science computer science], data that has several parts can be divided into '''fields'''. For example, a computer may represent today<nowiki>’</nowiki>s date as three distinct fields: the day, the month and the year. (wp) In library science field and Tag are synonymous. In the MARC record the field is data that follows the three digit number refer to as a tag. The hierarchal parts of a field are termed, "subfield" and are typically represented by a lower case letter in the alphabet or a number. (wp, ac)<br />
<br />
===Field Deletes Table===<br />
In the MARS 2.0 automated authority control process field/tag updates are determined by tables set up to determine which fields are obsolete. The Field Deletes table has a set of default deletes but can be customized to fit the needs of the individual library. (mpg)<br />
<br />
===Field Distribution===<br />
Field Distribution is part of the MARS 2.0 Summary Report. It is a statistical analysis of the distribution of fields (by tag) within the bibliographic file. Included are how many records had none, one, or two instances of each field, and how many fields changed (by tag). Changes listed in this section correspond with MARC Update Processing. (mpg)<br />
<br />
===Field Update Tables===<br />
Also called Tag update Tables. In the MARS 2.0 automated authority control process field/tag update table refers to the set of fields/tags that are changed from one tag to another because the MARC 21 standards have changed over the years. An example of a Field update would be Tag 308 changed to Tag 300. The Field Update table has a set of default deletes but can be customized to fit the needs of the individual library. (mpg)<br />
<br />
===File segmentation===<br />
''see Authority file segmentation''<br />
<br />
===Filing Indicator===<br />
A filing indicator is used to indicate the number of characters that are to be ignored when a title is indexed. The characters ignored are initial articles on a title and vary depending on the language of the title. The MARC fields that have filing indicators are 242, 245 and 440. The second indicator is the filing indicator. (ac)<br />
<br />
===Fixed Field===<br />
A field of the MARC record containing a fixed number of characters. The 24 character leader field 001 or the 005, 006, 007 and 008 are all fixed fields. Each position of a fixed field is defined by a character or code and it is in that static position within the field. Other MARC fields are variable length fields where data within the field varies in length. (ac)<br />
<br />
===Flip authority headings===<br />
''see Heading flips''<br />
<br />
===Folksonomy===<br />
'''Folksonomy''' (also known as '''collaborative tagging''', '''social classification''', '''social indexing''', and '''social tagging''') is the practice and method of [http://en.wikipedia.org/wiki/Collaborative collaboratively] creating and managing [http://en.wikipedia.org/wiki/Tag_(metadata) tags] to annotate and [http://en.wikipedia.org/wiki/Categorization categorize] [http://en.wikipedia.org/wiki/Content_(media_and_publishing) content]. In contrast to traditional [http://en.wikipedia.org/wiki/Subject_indexing subject indexing], metadata is generated not only by experts but also by creators and consumers of the content. Usually, freely chosen [http://en.wikipedia.org/wiki/Keyword keywords] are used instead of a [http://en.wikipedia.org/wiki/Controlled_vocabulary controlled vocabulary].<sup><nowiki>[</nowiki>1<nowiki>]</nowiki></sup> ''Folksonomy'' is a [http://en.wikipedia.org/wiki/Portmanteau portmanteau] of the words ''folk'' and [http://en.wikipedia.org/wiki/Taxonomy ''taxonomy]'', hence a folksonomy is a [http://en.wikipedia.org/wiki/User_generated_content user generated] taxonomy. (wp)<br />
<br />
===Form Subdivisions===<br />
The form subdivision is subfield $v of the topical subject heading (650). Form subdivisions (periodicals, bibliography, etc.) were 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 subfields in February, 1999. MARS 2.0 incorporated a number of enhancements to fully support subfield $v. (mpg)<br />
<br />
===Form/Genre Headings===<br />
''see Genre/Form''<br />
<br />
===FRAD===<br />
Functional Requirements for Authority Data. Entity-relationship model for authority control. Authority Control<nowiki>’</nowiki>s counterpart to FRBR (Functional Requirements for Bibliographic Records). FRAD Entities are defined as Name, Identifier and Controlled Access point. The basic FRAD Model is Bibliographic Entities known by Names and or identifiers which are the basis for a controlled access point(s) to the bibliographic record. (Power point presentation - "FRBR and FRAD: Foundations for RDA by Pat Riva Chair, IFLA FRBR Review Group.) (google)<br />
<br />
===Free-floating subdivisions===<br />
''see Subdivision headings''<br />
<br />
===FTP===<br />
File Transfer Protocol. Data exchange format used to transfer data over the internet. MARS can accept a wide variety of input media, but the most common exchange format is Internet File Transfer Protocol (FTP). (mpg)<br />
<br />
===Functional Requirements for Bibliographic Records===<br />
Or '''FRBR'''-- is a conceptual [http://en.wikipedia.org/wiki/Entity-relationship_model entity-relationship model] developed by the [http://en.wikipedia.org/wiki/International_Federation_of_Library_Associations_and_Institutions International Federation of Library Associations and Institutions] (IFLA) that relates user tasks of retrieval and access in online library catalogues and bibliographic databases from a user<nowiki>’</nowiki>s perspective. It represents a more holistic approach to retrieval and access as the relationships between the entities provide links to navigate through the hierarchy of relationships. The model is significant because it is separate from specific cataloguing standards such as [http://en.wikipedia.org/wiki/AACR2 AACR2] or [http://en.wikipedia.org/wiki/International_Standard_Bibliographic_Description International Standard Bibliographic Description] (ISBD). (wp) <br />
<br />
[[category:General Information]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Series_Processing_TableSeries Processing Table2016-06-22T19:44:12Z<p>Nate: /* 490 0_ Tags */</p>
<hr />
<div>In conjunction with the Library of Congress announcement that the 440 tag will no longer be standard, many clients have wondered what this will mean for our standard series processing. This series chart shows you exactly how each 4XX series tag will act based on it being matched, unmatched, matched and traced or untraced and so on. Please let your Project Manager know whether you prefer this current standard series processing.<br />
<br />
==440 Tags==<br />
This table describes how 440 series tags are handled under the new LC standard.<br />
{|border="2" cellspacing="0" cellpadding="4" width="100%"<br />
|bgcolor = "#A6A6A6" width="5%"|&nbsp;<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''A'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''B'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''C'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''D'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''E'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''F'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''G'''<br />
<br />
|-<br />
|&nbsp;<br />
|'''Original Field in Bib Record'''<br />
|'''Conversion of 4xx / 830'''<br />
|'''8xx match to national authority file'''<br />
|'''Series traced* or not? 645 t/008[12]a/b/z or not?'''<br />
|'''Preferred treatment for 490 1 field'''<br />
|'''Preferred treatment for 8xx field'''<br />
|'''490 1 / 8xx identical or different?'''<br />
<br />
|-<br />
|'''1.'''<br />
|440<br />
|440 converted to 490 1 and added to 830<br />
|8xx matches 1xx in natl auth file <br />
|Yes<br />
|Retain 490 1 in original form<br />
|Retain 8xx<br />
|Identical<br />
<br />
|-<br />
|'''2.'''<br />
|440<br />
|440 converted to 490 1 and added to 830<br />
|8xx matches '''4xx''' in natl auth file <br />
|Yes<br />
|Retain 490 1 in original form<br />
|Convert 8xx to 1xx of natl auth file<br />
|Different <br />
<br />
|-<br />
|'''3.'''<br />
|440<br />
|440 converted to 490 1 and added to 830<br />
|8xx matches 1xx in natl auth file <br />
|'''No''' <br />
|Convert 490 1 to 490 0. <br />
|Delete 8xx<br />
|N/A<br />
<br />
|-<br />
|'''4.'''<br />
|440<br />
|440 converted to 490 1 and added to 830<br />
|8xx matches '''4xx''' in natl auth file <br />
|'''No''' <br />
|Convert 490 1 to 490 0<br />
|Delete 8xx<br />
|N/A<br />
<br />
|-<br />
|'''5.'''<br />
|440<br />
|440 converted to 490 1 and added to 830<br />
|8xx '''doesn<nowiki>’</nowiki>t '''match any national auth file heading (neither a 1xx or 4xx) <br />
|N/A<br />
|Retain 490 1 in original form<br />
|Retain 8xx in original form<br />
|Identical<br />
<br />
|}<br />
<br />
==490 1_ Tags ==<br />
This table describes how 490 1_ Series tags are handled under the new LC Series Standard<br />
{|border="2" cellspacing="0" cellpadding="4" width="100%"<br />
|bgcolor = "#A6A6A6" width="5%"|&nbsp;<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''A'''<br><br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''B'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''C'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''D'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''E'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''F'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''G'''<br />
<br />
|-<br />
|&nbsp;<br />
|'''Original Field in Bib Record'''<br />
|'''Conversion of 4xx / 830'''<br />
|'''8xx match to national authority file'''<br />
|'''Series traced* or not? 645 t/008[12]a/b/z or not?'''<br />
|'''Preferred treatment for 490 1 field'''<br />
|'''Preferred treatment for 8xx field'''<br />
|'''490 1 / 8xx identical or different?'''<br />
<br />
|-<br />
|'''6.'''<br />
|490 1<br />
|490 1 and 8xx retained<br />
|8xx matches 1xx in natl auth file <br />
|Yes<br />
|Retain 490 1 in original form<br />
|Retain 8xx<br />
|Identical<br />
<br />
|-<br />
|'''7.'''<br />
|490 1<br />
|490 1 and 8xx retained<br />
|8xx matches '''4xx '''in natl auth file <br />
|Yes<br />
|Retain 490 1 in original form<br />
|Convert 8xx to 1xx of natl auth file<br />
|Different <br />
<br />
|-<br />
|'''8.'''<br />
|490 1<br />
|490 1 and 8xx retained<br />
|8xx matches 1xx in natl auth file <br />
|'''No''' <br />
|Convert 490 1 to 490 0. <br />
|Delete 8xx<br />
|N/A<br />
<br />
|-<br />
|'''9.'''<br />
|490 1<br />
|490 1 and 8xx retained<br />
|8xx matches '''4xx''' in natl auth file <br />
|'''No''' <br />
|Convert 490 1 to 490 0<br />
|Delete 8xx<br />
|N/A<br />
<br />
|-<br />
|'''10.'''<br />
|490 1<br />
|490 1 and 8xx retained<br />
|8xx '''doesn<nowiki>’</nowiki>t''' match any national auth file heading (neither a 1xx or 4xx) <br />
|N/A<br />
|Retain 490 1 in original form<br />
|Retain 8xx in original form<br />
|Identical<br />
<br />
|}<br />
<br />
==490 0_ Tags==<br />
This table describes how 490 0_ Series tags are handled under the new LC Series Standard<br />
{|border="2" cellspacing="0" cellpadding="4" width="100%"<br />
|bgcolor = "#A6A6A6" width="5%"|&nbsp;<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''A'''<br><br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''B'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''C'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''D'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''E'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''F'''<br />
|align = "center" bgcolor = "#A6A6A6" width="12%"|'''G'''<br />
<br />
|-<br />
|&nbsp;<br />
|'''Original Field in Bib Record'''<br />
|'''Conversion of 4xx / 830'''<br />
|'''8xx match to national authority file'''<br />
|'''Series traced* or not? 645 t/008[12]a/b/z or not?'''<br />
|'''Preferred treatment for 490 1 field'''<br />
|'''Preferred treatment for 8xx field'''<br />
|'''490 1 / 8xx identical or different?'''<br />
<br />
|-<br />
|'''11.'''<br />
|490 0<br />
|490 0 converted to 490 1 and added to 830<br />
|8xx matches 1xx in natl auth file <br />
|Yes<br />
|Retain 490 1 in original form<br />
|Retain 8xx<br />
|Identical<br />
<br />
|-<br />
|'''12.'''<br />
|490 0<br />
|490 0 converted to 490 1 and added to 830<br />
|8xx matches '''4xx '''in natl auth file <br />
|Yes<br />
|Retain 490 1 in original form<br />
|Convert 8xx to 1xx of natl auth file<br />
|Different <br />
<br />
|-<br />
|'''13.'''<br />
|490 0<br />
|490 0 converted to 490 1 and added to 830<br />
|8xx matches 1xx in natl auth file <br />
|'''No''' <br />
|Convert 490 1 back to 490 0. <br />
|Delete 8xx<br />
|N/A<br />
<br />
|-<br />
|'''14.'''<br />
|490 0<br />
|490 0 converted to 490 1 and added to 830<br />
|8xx matches '''4xx''' in natl auth file <br />
|'''No ''' <br />
|Convert 490 1 back to 490 0<br />
|Delete 8xx<br />
|N/A<br />
<br />
|-<br />
|'''15.'''<br />
|490 0<br />
|490 0 converted to 490 1 and added to 830<br />
|8xx '''doesn<nowiki>’</nowiki>t''' match any national auth file heading (neither a 1xx or 4xx) <br />
|N/A<br />
|Convert 490 1 back to 490 0<br />
|Delete 8xx<br />
|N/A<br />
<br />
|}<br />
<br />
<nowiki>*</nowiki>Traced means any series record with a 645$at OR a value of <nowiki>’</nowiki>a<nowiki>’</nowiki> or <nowiki>’</nowiki>b<nowiki>’</nowiki> or <nowiki>’</nowiki>z<nowiki>’</nowiki> in the 008<nowiki>[</nowiki>12<nowiki>]</nowiki><br />
<br />
<font size='3'>Special thank you to Amey Park of Kent State for allowing us to use this chart.</font><br />
<br />
[[category:Series Processing]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Main_PageMain Page2016-06-07T17:58:53Z<p>Nate: /* Contribute Your Knowledge */</p>
<hr />
<div><big>'''Automated Services'''</big><br />
<br />
Welcome to the Backstage Library Works Automation Services Wiki. Automated services are an integral part of the library world. They allow libraries and their staff to enact positive changes to a large amount of data in a relatively short time period and usually at a much reduced cost compared to manual services. This wiki covers the following automated services: Authority Control, RDA Enrichment, and Record De-duplication.<br />
<br />
Authority control is a key component of maintaining consistency across your collection, but it can also be a difficult to understand topic, especially if you're not familiar with all of the rules and terminology.<br />
<br />
== Exploring this Wiki ==<br />
To make the most of this Wiki, you will need to search for the topics that interest you.<br />
<br />
Explore these Automation Services Profiles:<br />
* [[Profile_Guide|Authority Matching Profile]]<br />
* [[RDA_Profile_Guide|RDA Profile]]<br />
* [[Dedupe_Profile_Guide|Dedupe Profile]]<br />
<br />
== Popular Pages ==<br />
We have found that there some entries have information that the community has found to be very valuable. In order to share this information with the widest audience we have included links here.<br />
* [[:Category:Authority_Control|General Authority Control]]<br />
* [[:Category:Authority_Control_Processing|Authority Control Processing]]<br />
* [[Series_Processing_Table|New Series]] -or- [[Old_Series_Processing_Table|Old Series]]<br />
* [[Authority_Control_Client_Demographics|Authority Control Client Demographics]]<br />
* [[:Category:General_Information|General Information]] - (with [[Authority_Control_Terminology|Terminology]])<br />
* [[:Category:Authority_Providers|Information on Authority Control Sources]]<br />
<br />
== Outside of the Wiki ==<br />
<br />
* Learn a bit more about AC by taking a look at our [[Authority Control Terminology|extensive terminology page]].<br />
* [http://mailman.xmission.com/cgi-bin/mailman/listinfo/bslwac Sign up for the BSLW AC Listserv]<br />
* [http://ac.bslw.com/mars Log into your AC account]<br />
* [http://www.bslw.com/ Visit BSLW main site]<br />
<br />
== Contribute Your Knowledge ==<br />
We would love to have your help in making this Wiki the most extensive knowledge base for Authority Control. If you would like to contribute an article, please email it to [mailto:info@bslw.com| info@bslw.com] - please include name of the author for proper credit. We may edit or correct any contributions for correctness and formatting.<br />
<br />
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.</div>Natehttps://ac.bslw.com/community/wiki/index.php/Main_PageMain Page2016-06-07T17:57:57Z<p>Nate: /* Exploring this Wiki */</p>
<hr />
<div><big>'''Automated Services'''</big><br />
<br />
Welcome to the Backstage Library Works Automation Services Wiki. Automated services are an integral part of the library world. They allow libraries and their staff to enact positive changes to a large amount of data in a relatively short time period and usually at a much reduced cost compared to manual services. This wiki covers the following automated services: Authority Control, RDA Enrichment, and Record De-duplication.<br />
<br />
Authority control is a key component of maintaining consistency across your collection, but it can also be a difficult to understand topic, especially if you're not familiar with all of the rules and terminology.<br />
<br />
== Exploring this Wiki ==<br />
To make the most of this Wiki, you will need to search for the topics that interest you.<br />
<br />
Explore these Automation Services Profiles:<br />
* [[Profile_Guide|Authority Matching Profile]]<br />
* [[RDA_Profile_Guide|RDA Profile]]<br />
* [[Dedupe_Profile_Guide|Dedupe Profile]]<br />
<br />
== Popular Pages ==<br />
We have found that there some entries have information that the community has found to be very valuable. In order to share this information with the widest audience we have included links here.<br />
* [[:Category:Authority_Control|General Authority Control]]<br />
* [[:Category:Authority_Control_Processing|Authority Control Processing]]<br />
* [[Series_Processing_Table|New Series]] -or- [[Old_Series_Processing_Table|Old Series]]<br />
* [[Authority_Control_Client_Demographics|Authority Control Client Demographics]]<br />
* [[:Category:General_Information|General Information]] - (with [[Authority_Control_Terminology|Terminology]])<br />
* [[:Category:Authority_Providers|Information on Authority Control Sources]]<br />
<br />
== Outside of the Wiki ==<br />
<br />
* Learn a bit more about AC by taking a look at our [[Authority Control Terminology|extensive terminology page]].<br />
* [http://mailman.xmission.com/cgi-bin/mailman/listinfo/bslwac Sign up for the BSLW AC Listserv]<br />
* [http://ac.bslw.com/mars Log into your AC account]<br />
* [http://www.bslw.com/ Visit BSLW main site]<br />
<br />
== Contribute Your Knowledge ==<br />
We would love to have your help in making this Wiki the most extensive knowledge base for Authority Control. If you would like to contribute an article, please email it to info@bslw.com - please include name of the author for proper credit. We may edit or correct any contributions for correctness and formatting.<br />
<br />
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.</div>Natehttps://ac.bslw.com/community/wiki/index.php/Main_PageMain Page2016-06-07T17:57:21Z<p>Nate: </p>
<hr />
<div><big>'''Automated Services'''</big><br />
<br />
Welcome to the Backstage Library Works Automation Services Wiki. Automated services are an integral part of the library world. They allow libraries and their staff to enact positive changes to a large amount of data in a relatively short time period and usually at a much reduced cost compared to manual services. This wiki covers the following automated services: Authority Control, RDA Enrichment, and Record De-duplication.<br />
<br />
Authority control is a key component of maintaining consistency across your collection, but it can also be a difficult to understand topic, especially if you're not familiar with all of the rules and terminology.<br />
<br />
== Exploring this Wiki ==<br />
To make the most of this Wiki, you will need to search for the topics that interest you.<br />
<br />
Explore these Automated Services Profiles:<br />
* [[Profile_Guide|Authority Matching Profile]]<br />
* [[RDA_Profile_Guide|RDA Profile]]<br />
* [[Dedupe_Profile_Guide|Dedupe Profile]]<br />
<br />
== Popular Pages ==<br />
We have found that there some entries have information that the community has found to be very valuable. In order to share this information with the widest audience we have included links here.<br />
* [[:Category:Authority_Control|General Authority Control]]<br />
* [[:Category:Authority_Control_Processing|Authority Control Processing]]<br />
* [[Series_Processing_Table|New Series]] -or- [[Old_Series_Processing_Table|Old Series]]<br />
* [[Authority_Control_Client_Demographics|Authority Control Client Demographics]]<br />
* [[:Category:General_Information|General Information]] - (with [[Authority_Control_Terminology|Terminology]])<br />
* [[:Category:Authority_Providers|Information on Authority Control Sources]]<br />
<br />
== Outside of the Wiki ==<br />
<br />
* Learn a bit more about AC by taking a look at our [[Authority Control Terminology|extensive terminology page]].<br />
* [http://mailman.xmission.com/cgi-bin/mailman/listinfo/bslwac Sign up for the BSLW AC Listserv]<br />
* [http://ac.bslw.com/mars Log into your AC account]<br />
* [http://www.bslw.com/ Visit BSLW main site]<br />
<br />
== Contribute Your Knowledge ==<br />
We would love to have your help in making this Wiki the most extensive knowledge base for Authority Control. If you would like to contribute an article, please email it to info@bslw.com - please include name of the author for proper credit. We may edit or correct any contributions for correctness and formatting.<br />
<br />
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122016-05-19T19:11:58Z<p>Nate: /* Step 2.11: Identities Management */</p>
<hr />
<div>==Step 2.11: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([http://stackoverflow.com/questions/176264/what-is-the-difference-between-a-uri-a-url-and-a-urn| link]) within your records. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> [http://id.loc.gov/authorities/names/nr99034050| http://id.loc.gov/authorities/names/nr99034050]<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> [http://id.loc.gov/authorities/subjects/sh85004836| http://id.loc.gov/authorities/subjects/sh85004836]<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> [http://id.nlm.nih.gov/mesh/D000716| http://id.nlm.nih.gov/mesh/D000716]<br />
''Please note that the NLM URI may not work at this time as the NLM URI site is currently still in beta.''<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the '''identifier''' only in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html| link]) and ISNI ([http://www.isni.org/| link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another vendor decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other vendor also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html| link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a [http://id.loc.gov/authorities/names/no2001000753| http://id.loc.gov/authorities/names/no2001000753]<br />
921 ## $a [http://viaf.org/viaf/23238834| http://viaf.org/viaf/23238834]<br />
922 ## $a [http://isni.org/isni/0000000116075005| http://isni.org/isni/0000000116075005]<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122016-05-19T19:10:17Z<p>Nate: /* Add $0 to Access Points */</p>
<hr />
<div>==Step 2.11: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([https://en.wikipedia.org/wiki/Uniform_Resource_Identifier| link]) within your records. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> [http://id.loc.gov/authorities/names/nr99034050| http://id.loc.gov/authorities/names/nr99034050]<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> [http://id.loc.gov/authorities/subjects/sh85004836| http://id.loc.gov/authorities/subjects/sh85004836]<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> [http://id.nlm.nih.gov/mesh/D000716| http://id.nlm.nih.gov/mesh/D000716]<br />
''Please note that the NLM URI may not work at this time as the NLM URI site is currently still in beta.''<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the '''identifier''' only in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html| link]) and ISNI ([http://www.isni.org/| link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another vendor decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other vendor also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html| link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a [http://id.loc.gov/authorities/names/no2001000753| http://id.loc.gov/authorities/names/no2001000753]<br />
921 ## $a [http://viaf.org/viaf/23238834| http://viaf.org/viaf/23238834]<br />
922 ## $a [http://isni.org/isni/0000000116075005| http://isni.org/isni/0000000116075005]<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122016-05-19T19:06:24Z<p>Nate: /* Add $0 to Access Points */</p>
<hr />
<div>==Step 2.11: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([https://en.wikipedia.org/wiki/Uniform_Resource_Identifier| link]) within your records. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> [http://id.loc.gov/authorities/names/nr99034050| http://id.loc.gov/authorities/names/nr99034050]<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> [http://id.loc.gov/authorities/subjects/sh85004836| http://id.loc.gov/authorities/subjects/sh85004836]<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> http://id.nlm.nih.gov/mesh/D000716| http://id.nlm.nih.gov/mesh/D000716]<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the '''identifier''' only in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html| link]) and ISNI ([http://www.isni.org/| link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another vendor decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other vendor also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html| link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a [http://id.loc.gov/authorities/names/no2001000753| http://id.loc.gov/authorities/names/no2001000753]<br />
921 ## $a [http://viaf.org/viaf/23238834| http://viaf.org/viaf/23238834]<br />
922 ## $a [http://isni.org/isni/0000000116075005| http://isni.org/isni/0000000116075005]<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122016-05-19T19:05:39Z<p>Nate: /* Add URIs to Authority Records */</p>
<hr />
<div>==Step 2.11: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([https://en.wikipedia.org/wiki/Uniform_Resource_Identifier| link]) within your records. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> [http://id.loc.gov/authorities/names/nr99034050| http://id.loc.gov/authorities/names/nr99034050]<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> [http://id.loc.gov/authorities/subjects/sh85004836| http://id.loc.gov/authorities/subjects/sh85004836]<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> [https://id.nlm.nih.gov/mesh/D000716.html| https://id.nlm.nih.gov/mesh/D000716.html]<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the '''identifier''' only in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([http://www.oclc.org/developer/develop/web-services/viaf.en.html| link]) and ISNI ([http://www.isni.org/| link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another vendor decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other vendor also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html| link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a [http://id.loc.gov/authorities/names/no2001000753| http://id.loc.gov/authorities/names/no2001000753]<br />
921 ## $a [http://viaf.org/viaf/23238834| http://viaf.org/viaf/23238834]<br />
922 ## $a [http://isni.org/isni/0000000116075005| http://isni.org/isni/0000000116075005]<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.11Step 2.112016-05-19T19:04:48Z<p>Nate: /* links */</p>
<hr />
<div>==Step 2.10: Accelerated Reader & Lexile Measures==<br />
[[Image:a2-10.png]]<br><br><br />
MARS 2.0 offers two types of enrichment options for your collection of juvenile records: accelerated reader & lexile measures. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Accelerated Reader===<br />
For more information about Accelerated Reader, quiz points and reading levels, please visit [http://www.renaissance.com/products/accelerated-reader| http://www.renaissance.com/products/accelerated-reader]:<br/><br />
Accelerated Reader (AR) is a computer program that helps teachers and librarians manage and monitor children’s independent reading practice. Your child picks<br />
a book at his own level and reads it at his own pace. When finished, your child takes a short quiz on the computer. (Passing the quiz is an<br />
indication that your child understood what was read.) AR gives children, teachers, and librarians feedback based on the quiz results, which<br />
the teacher then uses to help your child set goals and direct ongoing reading practice.<br />
<br />
Children using AR choose their own books to read, rather than having one<br />
assigned to them. This makes reading a much more enjoyable experience<br />
as they can choose books that are interesting to them.<br />
<br />
Teachers and librarians help your child choose books at an appropriate<br />
readability level that are challenging without being frustrating, ensuring<br />
that your child can pass the quiz and experience success. <br />
<br />
Here is an example of a before/after record with the AR enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">526 ## $a Accelerated Reader $b UG $c 5.1 $d 17 $e 17 $z 166237</font></font><br />
<br />
===Lexile Measures===<br />
For more information about Lexile Measures, please visit '''www.lexile.com''':<br/><br />
The Lexile framework is a scientific way to match readers with text using the same scale. Recognized as the standard for matching readers with texts, Lexile&#174; measures connect learners of all ages with resources at the right level of challenge. Lexile measures provide a clear way to monitor progress toward college and career readiness.<br />
<br />
Here is an example of a before/after record with the Lexile enrichment:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<br />
'''updated record''':<br />
100 1# $a Paige, D. M.<br />
245 10 $a Dorothy must die :$b stories /$c Danielle Paige.<br />
300 ## $a 377, 27 pages ;$c 21 cm.<br />
<font color="blue">521 8# $a HL720L $b Lexile</font></font><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.8Step 2.82016-05-19T19:04:33Z<p>Nate: /* links */</p>
<hr />
<div>==Step 2.8: GMD Standardization==<br />
[[Image:rda3-1.png]]<br><br><br />
MARS 2.0 updates obsolete General Material Designations (GMDs) to the current authorized form, and corrects most incorrectly spelled GMD variants.<br />
<br />
Please indicate which GMD table you would like to use and your preferred bracket practice by filling out both parts of Step 2.8.<br />
<br />
===GMD location===<br />
MARS 2.0 assumes it has reached the end of the 245 $h when it encounters one of the following characters: subfield delimiter, end-of-field delimiter, forward slash, back slash, colon, semicolon, equals sign, or period.<br />
<br />
The 245 $h will be moved:<br />
*Before $b or after $n or $p in headings with a $b<br />
*Before a $c in headings without a $b, $n, or $p<br />
<br />
<font size="3"> 245 10 $a Royal gazette /$c New Brunswick <font color="red">$h microform</font><br />
245 00 $a Daily report. <font color="red">$h kit</font> $p People's Republic of China.<br />
<br />
'''changes to''':<br />
245 10 $a Royal gazette <font color="red">$h [microform]</font> /$c New Brunswick.<br />
245 00 $a Daily report. $p People's Republic of China <font color="red">$h [kit]</font>.</font><br />
<br />
=== AACR2 standard terms (level 1) ===<br />
In the AACR2 Standard Terms option (GMD Level 1), MARS 2.0 processing will convert as many GMDs as possible to the terms authorized in the current edition of AACR2.<br />
<br />
For example, both '''$h [computer file]''' and '''$h [computer fillle]''' would be modified to '''$h [electronic resource]'''.<br />
<br />
=== Common practice terms (level 2) ===<br />
In some local catalogs, there may exist GMDs which are not included in the AACR2 list of authorized GMDs (AACR2 paragraph 1.1C). The MARS 2.0 Level 2 GMD list contains '''common''' terms used in many libraries.<br />
<br />
For example, using the Level 2 Common Practice Terms table, the GMD '''$h [audicassette]''' would be corrected to '''$h [audiocassette]''', while in the AACR2 Standard Terms option (Level 1) '''$h [audicassette]''' would be corrected to the standard AACR2 GMD '''$h [sound recording]'''.<br />
<br />
Obsolete terms (i.e., terms that were once authorized by AACR2 and have been replaced by a different term) are normally updated to the replacement term even in Level 2. For example, '''$h [computer file]''' is replaced by the newer term '''$h [electronic resource]'''.<br />
<br />
=== Custom terms ===<br />
You can easily modify either of the GMD term options available in MARS 2.0. For example, if you would like to standardize all your GMDs to the AACR2 Standard Terms, but retain the non-standard terms “microfiche” and “microfilm”, simply notate it in Step 2.9 under Additional Information.<br />
<br />
=== Unrecognized terms===<br />
If the MARS 2.0 GMD tables do not contain a particular GMD variant, that GMD will be included in the '''Unrecognized GMD Report''' (see Step 5.2, R51).<br />
<br />
==Brackets==<br />
MARS 2.0 can also add square brackets around the GMD if not present. Similarly, if the GMD is enclosed in parentheses, angle brackets, etc. MARS 2.0 changes them to square brackets. MARS 2.0 can also remove brackets from GMDs to support systems in which the brackets cause display problems.<br />
<br />
<font size="3"> 245 14 $a The royal gazette <font color="red">$h microform</font> /$c New Brunswick.<br />
245 10 $a Pride and prejudice <font color="red">$h (vidrecording)</font> /$c Metro-Goldwyn-Mayer.<br />
<br />
'''changes to''': <br />
245 14 $a The royal gazette <font color="red">$h [microform]</font> /$c New Brunswick.<br />
245 10 $a Pride and prejudice <font color="red">$h [videorecording]</font> /$c Metro-Goldwyn-Mayer.</font><br />
<br />
The MARS 2.0 staff recommends adding square brackets to the 245 $h. Even if your present local system generates the necessary square brackets, it is likely a future system will require them in the record.<br />
<br />
'''Note''': ''Brackets around GMDs can only be added or removed if GMDs are being standardized. If GMDs are not being standardized, no changes will occur in the 245 $h.''<br />
<br />
==GMD Table Summary==<br />
The table below shows the results of selecting the various GMD Standardization options in Step 2.8:<br />
<br />
Original Form of GMD in Bibliographic Record: '''$h audiocasste'''<br><br><br />
[[Image:29a.png]]<br><br><br />
===AACR2 standard terms===<br />
(spelling variants not shown)<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Level 1<br />
! style="background:silver" align="center" | Level 1<br />
! style="background:silver" align="center" | Level 1<br />
|- align="left"<br />
| activity card || flash card || object<br />
|- align="left"<br />
| art original || game || picture<br />
|- align="left"<br />
| art reproduction || kit || realia<br />
|- align="left"<br />
| braille || manuscript || slide<br />
|- align="left"<br />
| cartographic material || microform || sound recording<br />
|- align="left"<br />
| cartographic material (tactile) || microscope slide || technical drawing<br />
|- align="left"<br />
| chart || model || text<br />
|- align="left"<br />
| chart (large print) || motion picture || text (large print)<br />
|- align="left"<br />
| diorama || multimedia || toy<br />
|- align="left"<br />
| electronic resource || music || transparency<br />
|- align="left"<br />
| filmstrip || music (braille) || videorecording<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Common terms===<br />
(spelling variants not shown)<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Level 2<br />
! style="background:silver" align="center" | Level 2<br />
! style="background:silver" align="center" | Level 2<br />
|- align="left"<br />
| activity card || globe || record<br />
|- align="left"<br />
| art original || government document || serial<br />
|- align="left"<br />
| art reproduction || graphic || slide set<br />
|- align="left"<br />
| atlas || kit || sound recording<br />
|- align="left"<br />
| audiocassette || large print || sound recording (cassette)<br />
|- align="left"<br />
| braille || laser disc || sound recording (compact disc)<br />
|- align="left"<br />
| cartographic chart || LP || sound recording (CD)<br />
|- align="left"<br />
| cartographic material || manuscript || sound recording (LP)<br />
|- align="left"<br />
| cartographic material (tactile) || map || study print<br />
|- align="left"<br />
| CD recording || map (tactile) || technical drawing<br />
|- align="left"<br />
| CD-ROM || microfiche || text<br />
|- align="left"<br />
| CDV || microfilm || text (large print)<br />
|- align="left"<br />
| chart || microform || toy<br />
|- align="left"<br />
| chart (large print) || microopaque || transparency<br />
|- align="left"<br />
| compact disc || microprint || US document<br />
|- align="left"<br />
| diorama || microscope slide || VHS<br />
|- align="left"<br />
| DVD || model || video CD<br />
|- align="left"<br />
| DVD-ROM || motion picture || video single disc<br />
|- align="left"<br />
| electronic resource || music || videocassette<br />
|- align="left"<br />
| electronic resource (CD-ROM) || music (braille) || videodisc<br />
|- align="left"<br />
| federal document || newspaper || videodisc (DVD)<br />
|- align="left"<br />
| filmstrip || periodical || videorecording<br />
|- align="left"<br />
| flash card || photograph || videorecording (DVD)<br />
|- align="left"<br />
| floppy || picture || videorecording (VHS)<br />
|- align="left"<br />
| game || realia || VSD<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.7Step 2.72016-05-19T19:04:23Z<p>Nate: /* links */</p>
<hr />
<div>==Step 2.7: Initial Articles & Indicators==<br />
[[Image:rda2-1.png]]<br><br><br />
MARS 2.0 supports the standard practice of omitting most initial articles even if a nonfiling character indicator has been defined for the field.<br />
<br />
Initial articles are retained, and the filing indicator correctly set, for the 245 Title Statement and 440 Series Statement/Title Added Entry fields.<br />
<br />
The MARS 2.0 Initial Article Table is an important part of the initial article processing routines. A copy is included at the end of this section. It is based on the Initial Definite and Indefinite Articles table that starts on page 40.<br />
<br />
===Corporate heading initial article check===<br />
You can choose to have corporate heading fields checked for initial articles. This MARS 2.0 option examines $t in these fields: '''110''', '''410''', '''610''', '''710''' and '''810'''.<br />
<br />
If $t begins with '''The''', the initial article is deleted and the first letter of the subsequent word is capitalized. Additionally, if the first word is '''A''' or '''An''', MARS 2.0 includes it in the Possible Leading Articles Report (see [http://ac.bslw.com/community/wiki/index.php5/Profile_Guide_Chapter_5#MARS_2.0_Bib_Reports_List Step 5.2, R14]).<br />
<br />
===245 & 440 fields===<br />
MARS 2.0 checks $a for any initial article in the language of the item (as coded in fixed field 008, bytes 35-37). If an initial article is found in field 245 or 440, the 2nd indicator (Nonfiling Characters) is set to the value in the MARS 2.0 Initial Article Table.<br />
<br />
If the field does not begin with an article in the language of the item, and the Nonfiling Characters indicator contains a number, no processing is done. This prevents setting an incorrect indicator value when a heading has been correctly coded for an initial article in a language other than that of the item as a whole.<br />
<br />
If the 2nd indicator contains a blank (or any other character except a number), MARS 2.0 looks for the presence of an initial A, An, or The. If the heading begins with one of these three text strings, the heading is included in the Possible Leading Articles report (see Step 5.2, R14).<br />
<br />
If no other condition is satisfied, a blank Nonfiling Characters indicator is set to zero.<br />
<br />
MARS 2.0 initial article processing is fully compliant with the February 20, 2003 Library of Congress change in counting non-filing characters.<br />
<br />
Diacritics associated with the initial letter of the following word are no longer included in the filing indicator:<br />
<br />
<font size="3"> 245 0<font color="red">5</font> $a <font color="red">Der ö</font>ffentliche Dienst …<br />
440 <font color="red">5</font> $a <font color="red">Los ú</font>ltimos alazapas ;$v 2<br />
<br />
'''changes to''':<br />
245 0<font color="red">4</font> $a <font color="red">Der ö</font>ffentliche Dienst …<br />
440 <font color="red">4</font> $a <font color="red">Los ú</font>ltimos alazapas ;$v 2</font><br />
<br />
Diacritics associated with the initial article and special characters other than diacritics, however, continue to be included in the filing indicator as shown in the examples below:<br />
<br />
<font size="3"> 245 0<font color="red">5</font> $a <font color="red">[The P</font>art of Pennsylvania that … townships].<br />
245 1<font color="red">5</font> $a <font color="red">The “o</font>ther” person …</font><br />
<br />
MARS 2.0 does '''not''' examine $p.<br />
<br />
==Other Fields==<br />
MARS 2.0 examines the beginning of each instance of these fields and subfields for initial articles:<br><br />
===Subfield $a===<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- align="center"<br />
| 130 || 630 || 730 || 740 || 830<br />
|- align="center"<br />
| 210 || 211 || 212 || 214 || 222<br />
|- align="center"<br />
| 240 || 242 || 243 || 246 || 247<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Subfield $t===<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- align="center"<br />
| 100 || 110 || 111<br />
|- align="center"<br />
| 400 || 410 || 411<br />
|- align="center"<br />
| 600 || 610 || 611<br />
|- align="center"<br />
| 700 || 710 || 711<br />
|- align="center"<br />
| 800 || 810 || 811<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
For fields that have a Nonfiling Characters indicator defined, the initial word is extracted based on the filing indicator and is compared with all articles in the MARS 2.0 Initial Article Table.<br />
<br />
If the initial word is an article:<br />
*The word is deleted<br />
*The first letter of the subsequent word is capitalized<br />
*The filing indicator is reset to zero<br />
<br />
If the article is not found, MARS 2.0 includes the field in the '''Suspicious Filing Indicators Report''' for local review (see Step 5.2, R13).<br />
<br />
MARS 2.0 uses a different process if:<br />
*The filing indicator is a zero or a blank<br />
*No filing indicator has been defined for the field<br />
*The subfield being examined is $t<br />
*If the subfield begins with '''The''':<br />
*The initial article is deleted<br />
*The first letter of the subsequent word is capitalized<br />
*The filing indicator (if defined) is reset to zero<br />
<br />
Additionally, if the first word is '''A''' or '''An''', it is included in the '''Possible Leading Articles Report''' (see Step 5.2, R14).<br />
<br />
==Counting Non-Filing Characters==<br />
With the advent of MARC21, the method of counting non-filing characters was clarified. On February 20, 2003 the Library of Congress implemented a change in practice for counting non-filing characters to reflect the MARC21 clarification.<br />
<br />
This change applies when definite or indefinite articles are present and the first filing word following the article begins with a character modified by a diacritic. When an initial article is present, the rule for counting non-filing characters is as follows:<br />
<blockquote>Count the article, diacritics associated with the article, any blank space, an alif, an ayn, or any mark of punctuation preceding the first filing character. Do '''not''' count a diacritic associated with the first filing character (the alif and ayn are not diacritics, they are special spacing characters not considered for filing).</blockquote><br />
<br />
This practice is best illustrated by the following examples.<br />
<br />
<font size="3"> '''Old practice''':<br />
245 1<font color="red">3</font> $a <font color="red">L’é</font>té …<br />
245 1<font color="red">5</font> $a <font color="red">Los ú</font>ltimos …<br />
245 0<font color="red">5</font> $a <font color="red">Der ö</font>ffentliche Dienst …<br />
245 1<font color="red">5</font> $a <font color="red">al-‘A</font>lam …<br />
<br />
'''New practice''':<br />
245 1<font color="red">2</font> $a <font color="red">L’</font>été …<br />
245 1<font color="red">4</font> $a <font color="red">Los </font>últimos …<br />
245 0<font color="red">4</font> $a <font color="red">Der </font>öffentliche Dienst …<br />
245 1<font color="red">4</font> $a <font color="red">al-‘</font>Alam …</font><br />
<br />
Other helpful examples with and without initial articles (these do '''not''' reflect a change in practice):<br />
<br />
<font size="3"> 245 0<font color="red">4</font> $a <font color="red">al-‘</font>Arabiyah …<br />
245 1<font color="red">4</font> $a <font color="red">He </font>Mone …<br />
245 1<font color="red">2</font> $a <font color="red">L’</font>enfant criminal.<br />
245 0<font color="red">5</font> $a <font color="red">[The P</font>art of Pennsylvania that … townships].<br />
245 1<font color="red">5</font> $a <font color="red">The “</font>other” person …<br />
245 1<font color="red">0</font> $a <font color="red">[</font>Diary] …<br />
245 1<font color="red">0</font> $a <font color="red">”</font>Full steam ahead!” …</font><br />
<br />
'''Note''': ''The following characters can be considered candidates as “the first filing character”:''<br />
*Latin letters<br />
*Arabic numbers<br />
*Super or subscript numbers<br />
*Æ – AE digraph<br />
*ΠРOE digraph<br />
*Ð – Crossed d<br />
*ð – Eth<br />
*i – Turkish i<br />
*L – Polish l<br />
*l – Script l<br />
*O – Hooked o<br />
*U – Hooked u<br />
*Ø – Slashed o<br />
*Þ – Icelandic thorn<br />
*Hatch mark (#)<br />
*& – Ampersand<br />
*+ – Plus sign<br />
<br />
==MARS 2.0 Initial Article Table==<br />
The table shown lists each initial article, and the associated filing indicator, by language.<br />
<br />
This table is not intended as a comprehensive list, but rather a tool that is used within a specific automated process. Generally, initial articles that cannot be correctly converted in all headings without manual review are not included in the table.<br />
<br />
'''MARS 2.0 Initial Article Table'''<br><br />
[[Image:28a.png]]<br><br><br />
<br />
'''MARS 2.0 Initial Article Table'''<br><br />
[[Image:28b.png]]<br><br><br />
<br />
'''MARS 2.0 Initial Article Table'''<br><br />
[[Image:28c.png]]<br><br><br />
<br />
'''MARS 2.0 Initial Article Table'''<br><br />
[[Image:28d.png]]<br><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.6Step 2.62016-05-19T19:04:13Z<p>Nate: /* links */</p>
<hr />
<div>==Step 2.6: Special Conversions & Additions==<br />
[[Image:rda2-1.png]]<br><br><br />
A number of MARC update conversions are more complex than simply changing a field tag or subfield code to the current value. Some fields, such as the 007, often need to be added to a record. The special MARC field conversion and additions currently provided are:<br />
*Add missing format data<br />
**007<br />
**245 $h (for AACR2 records, not RDA unless by request)<br />
*Add missing subfield data<br />
**017 $b<br />
**032 $b<br />
*Complex field conversions<br />
**1XX Main-Entry-Is-Subject<br />
**260 $d to 028 $a<br />
**262 to 260<br />
**300<br />
**301 to 300<br />
**305 to 300<br />
**705 to 700<br />
**715 to 710<br />
**X11<br />
<br />
Describe modifications to processing listed above. Provide a different default for the 007 field by listing specific values for each position.<br />
<br />
If any of the MARS 2.0 update special field conversions adds a field identical to a pre-existing field, the identical fields will be deduplicated.<br />
<br />
==Specific Fields==<br />
===007 field===<br />
MARS 2.0 can add an 007 Physical Description Fixed Field containing default values. This table shows the format of the record, the values the format is based on and the values in each default 007 field:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Record Format<br />
! style="background:silver" align="center" | LDR Byte Values<br />
! style="background:silver" align="center" | Default 007<br />
|- align="left"<br />
| Map || 06 = e or f || ajlcanzn<br />
|- align="left"<br />
| Sound Recording || 06 = I or j || sdluungnnmmneu<br />
|- align="left"<br />
| Videorecording || 06 = g ''and'' 008, 33 = v || vdlcbahou<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===1xx main-entry-is-subject===<br />
In the past, a value of '''1''' in the 2nd indicator meant the 1XX heading represented both the '''main entry''' and a '''topical subject''' access point. A MARC update in 1990 made use of the 1XX 2nd indicator for this purpose obsolete.<br />
<br />
MARS 2.0 generates a 6XX Subject Added Entry field when the 1XX Main Entry field has 2nd indicator value 1 (main entry is subject). The 2nd indicator of the 1XX Main Entry field is changed to a '''blank'''—the only value currently authorized for a 1XX 2nd indicator. The 1st indicator of the new 6XX field will match the 1XX field and the 2nd indicator will be ‘0’.<br />
<br />
===245 $h added (medium-aacr2)===<br />
MARS 2.0 processing can check for the absence of a $h (Medium) in the 245 Title Statement and add a missing General Material Designation (GMD) in some cases:<br />
<font size="3"> 245 10 $a Olympia town square /$c by Fred Smith.<br />
<br />
'''changes to''':<br />
245 10 $a Olympia town square <font color="red">$h [cartographic material]</font> /$c by Fred Smith.</font><br />
The following 245 $h GMDs are added based on the values indicated:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | 245 $h<br />
! style="background:silver" align="center" | LDR Byte 06 Value<br />
! style="background:silver" align="center" | 008 contains<br />
|- align="center"<br />
| [cartographic material] || e ''or'' f || <br />
|- align="center"<br />
| [electronic resource] || m || <br />
|- align="center"<br />
| [filmstrip] || g || byte 33 = f<br />
|- align="center"<br />
| [kit] || o || <br />
|- align="center"<br />
| [microform] || a ''or'' t || byte 23 = a, b ''or'' c<br />
|- align="center"<br />
| [motion picture] || g || byte 33 = m<br />
|- align="center"<br />
| [slide] || g || byte 33 = s<br />
|- align="center"<br />
| [sound recording] || i ''or'' j || <br />
|- align="center"<br />
| [transparency] || g || byte 33 = t<br />
|- align="center"<br />
| [vidoerecording] || g || byte 33 = v<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
To modify any values in this tables, please indicate any changes in Step 2-7.<br />
<br />
MARS 2.0 can also standardize GMDs already present in the 245 $h subfield. MARS 2.0 GMD Standardization is described in [http://ac.bslw.com/community/wiki/index.php5?title=Profile_Guide_Step_2.9&action=edit Step 2-9].<br />
<br />
'''Note''': $h (Medium) in other title fields and subfields are normally deleted in keeping with current cataloging practice (see the [http://ac.bslw.com/community/wiki/index.php5/Profile_Guide_Step_2.5#Subfield_Deletes_Table Subfield Deletes table] in [http://ac.bslw.com/community/wiki/index.php5/Profile_Guide_Step_2.5 Step 2-5]).<br />
<br />
===017 field===<br />
MARS 2.0 adds $b (Source) if not present in field 017 Copyright Registration Number. The $b in field 017 carries the name of the agency assigning the copyright registration number. Because the $b is now required, and records input before 1980 do not contain it, MARS 2.0 can add the appropriate $b code and data “U.S. Copyright Office” to field 017.<br />
<br />
===028 field===<br />
If the subfield order in an 028 field is $b $a, MARS 2.0 reorders the subfields so they follow the current standard order of $a $b.<br />
<br />
===032 field===<br />
MARS 2.0 adds $b (Source) if not present in field 032 Postal Registration Number. The $b in the 032 field carries the name of the agency assigning the postal registration number.<br />
<br />
Because $b is now required and records input before the subfield was defined do not contain it, MARS 2.0 can add the appropriate $b code and data “USPS” to field 032.<br />
<br />
===260 field===<br />
MARS 2.0 can convert field 260 $d to field 028 $a. Field 260 $d was defined as “Plate or publisher number,” but was made obsolete when field 028 Publisher Number for Music was defined. If a 260 $d exists in a bibliographic record and the value in Leader byte 06 is '''c''', '''d''', '''i''', or '''j''':<br />
*'''028''' field with indicator values '''02''' is '''generated'''<br />
*'''260 $d''' is moved to '''028 $a'''<br />
*'''260 $b''' is copied to '''028 $b'''<br />
*Punctuation in the 260 field is corrected, if necessary<br />
<br />
The 260 field conversion option includes special routines that update the punctuation in all 260 fields in the bibliographic records being processed.<br />
<br />
These punctuation routines update much of the punctuation in 260 fields to the current standards, including:<br />
*<space> + <colon> before $b<br />
*<comma> before $c<br />
*Final field punctuation, as necessary<br />
<br />
===262 field===<br />
Field 262 is restricted to pre-AACR2 records for sound recordings. Field 260 is valid for use with all music materials including sound recordings for the data contained in the 262 $a $b $c. Field 028 was defined for the data in the 262 $k $l (lowercase 'L').<br />
<br />
If field 262 exists in a bibliographic record:<br />
*262 is '''changed''' to 260<br />
*Changes both indicators of new 260 to blank<br />
*Retains these subfield codes: $a $b $c<br />
<br />
For each 262 $k present:<br />
*028 field with indicator values 02 is '''generated'''<br />
*262 $k is '''moved''' to 028 $a subfield<br />
*262 $b is '''copied''' to 028 $b<br />
<br />
For each 262 $l (lowercase 'L') present:<br />
*028 field with indicator values 12 '''generated'''<br />
*262 $l is '''moved''' to 028 $a<br />
*262 $b is '''copied''' to 028 $b<br />
<br />
If the 262 field does not contain a $k or $l (lowecase 'L'), MARS 2.0 does the following additional conversions:<br />
*262 $c is '''moved''' to 028 $a with indicator values 02<br />
*262 $e is '''moved''' to 028 $b with indicator values 12<br />
*262 $b is '''copied''' to 028 $b<br />
*262 $d '''changed''' to $c code<br />
<br />
After all conversions have been completed, the punctuation in the 028 fields and 260 field is updated.<br />
<br />
===300 field===<br />
Field 300 Physical Description of the described item includes validation and cleanup for language materials only (Leader byte 06 = a). Each option described below can be customized according to your preference.<br />
<br />
The following changes are made to the 300 $a:<br />
*unp. or n.p. is '''changed''' to 1 v. (unpaged)<br />
*Comma is added to page numbers if missing (e.g., 1264 p. becomes 1,264 p.)<br />
*l. is '''changed''' to leaves<br />
*approx. is '''changed''' to ca.<br />
*p.l. is '''removed''' (e.g., 4 p.l., xv, 20 p. becomes xv, 20 p.)<br />
*unnumbered is '''removed''' and brackets '''added''' (e.g., 48 unnumbered leaves becomes [48] leaves)<br />
*[various pagings] is '''changed''' to (various pagings)<br />
<br />
The following changes are made to the 300 $b:<br />
*Illustrative matter is '''rearranged''' to be in correct order<br />
*Obsolete illustrative matter is '''replaced''' with ill. (e.g., tables or fronts. becomes ill.)<br />
*ill. is '''removed''' if followed by parenthetical illustrative matter (e.g., ill. (ports.) becomes ports.)<br />
*illus. is '''changed''' to ill.<br />
<br />
The following general changes are made to the 300:<br />
*Various punctuation and spacing issues '''updated'''<br />
*Adds ''';$c cm.''' if missing<br />
*Adds '''300 $a p. ;$c cm.''' if record is monograph and 300 does not exist<br />
*Numbered plate data in $b is '''moved''' to $a; if plate designation is not numbered, it is '''removed'''<br />
<br />
<font size="3"> 300 $a 22 <font color="red">l.</font> :$b <font color="red">graphs</font>.<br />
300 $a <font color="red">unp.</font> $b ill<font color="red">us</font>. $c 30 cm.<br />
<br />
'''changes to:'''<br />
300 $a 22 <font color="red">leaves</font> :$b <font color="red">ill.</font> ;$c cm.<br />
300 $a <font color="red">1 v. (unpaged)</font> :$b ill. ;$c 30 cm.</font><br />
<br />
===301 field===<br />
In 1983, field 301 was made obsolete for visual materials. Physical description data is now carried in field 300 Physical Description, with the formerly separate color ($c), sound ($b) and videorecording speed ($f) data recorded in field 300 $b.<br />
<br />
If field 301 exists in a bibliographic record, MARS 2.0:<br />
*301 is '''changed''' to 300, with indicator values <blank><blank><br />
*Retains '''$a''' and '''$e''', with data<br />
*$d is '''changed''' to $c<br />
*$b $c $f data is '''combined''' into single $b<br />
<br />
===305 field===<br />
Field 305 Physical Description for Sound Recordings is a pre-AACR2 field made obsolete by format integration. Field 305 was functionally replaced by field 300 Physical Description.<br />
<br />
If field 305 exists in a bibliographic record:<br />
*305 is '''changed''' to 300, with indicator values <blank><blank><br />
*Retains '''$a''' and '''$c''', with data<br />
*$b $d $e $f data is '''combined''' into single $b<br />
*Updates the punctuation<br />
<br />
For each $m present in the 305 field:<br />
*305 $m is '''moved''' to 028 $a with indicator values 02<br />
*260 $b is '''copied''' to 028 $b<br />
<br />
<font size="3"> 260 $a New York, N.Y. <font color="red">$b Columbia</font>,$c 1959.<br />
305 $a 1 sound disc (20 min.) :$b analog, 33 1/3 rpm, stereo. ;$c 12 in. <font color="red">$m STMA 8007</font><br />
<br />
'''changes to''':<br />
<font color="red">028</font> 02 $a STMA 8007 $b Columbia<br />
260 $a New York, N.Y. :$b Columbia, $c 1959.<br />
300 $a 1 sound disc (20 min.) :$b analog, 33 1/3 rpm, stereo. ;$c 12 in.</font><br />
<br />
For each $n present in the 305 field:<br />
*305 $n is '''moved''' to 028 $a with indicator values 11<br />
*260 $b is '''copied''' to 028 $b<br />
<br />
<font size="3"> 305 $a 1 sound disc (18 min.) $c 10 in. $b 74 rpm $d standard <font color="red">$e</font> monaural <font color="red">$m STMA $n L27410X</font><br />
<br />
'''changes to''':<br />
<font color="red">028</font> 02 $a STMA 3059<br />
<font color="red">028</font> 11 $a L27410X<br />
300 $a 1 sound disc (18 min.) :$b 74 rpm, standard<font color="red">,</font> monaural ;$c 10 in.</font><br />
<br />
===705 & 715 field conversion===<br />
MARS 2.0 converts 705 tags to the equivalent 700 tag and 715 tags to 710, while also adding a Relator Code $4. The default content of the added $4 is '''prf''', the code for '''performer'''.<br />
<br />
'''Note''': ''Indicate in Step 2.6 if you would like a value different from '''prf''' in the new $4. The 705 Added Entry-Personal Name (Performer) and 715 Added Entry-Corporate Name (Performing Group) fields were made obsolete in 1980.''<br />
<br />
===X11 conference name headings===<br />
MARS 2.0 updates Conference Name fields '''111''', '''611''', '''711''', '''811''' to conform to AACR2 and current MARC21 standards. To change the obsolete $b code to $n, MARS 2.0 rearranges the subfields in AACR2 order and corrects the punctuation.<br />
<br />
<font size="3"> '''Pre-AACR2'''<br />
711 01 $a International Conference on the Chemistry and Uses of Molybdenum, <font color="red">$b</font> 1st, <font color="red">$c</font> University of Reading, <font color="red">$d</font> 1973<br />
<br />
'''changes to AACR2 form''':<br />
711 0 $a International Conference on the Chemistry and Uses of Molybdenum <font color="red">$n</font> (1st :<font color="red">$d</font> 1973 :<font color="red">$c</font> University of Reading)</font><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.5Step 2.52016-05-19T19:04:04Z<p>Nate: /* links */</p>
<hr />
<div>==Step 2.5: Indicator Updates==<br />
[[Image:rda2-1.png]]<br><br><br />
The following tables show the standard updates to 1st and 2nd indicators.<br />
<br />
===1st indicator updates table===<br />
MARS 2.0 makes these changes to the 1st indicator:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! align="center" |<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 017 || any || # || ! style="background:lightgray" | || 505 || # || 0<br />
|- align="center"<br />
| 048 || 012 || # || ! style="background:lightgray" | || 511 || #23 || 0<br />
|- align="center"<br />
| 082 || # || 0 || ! style="background:lightgray" | || 534 || 01 || #<br />
|- align="center"<br />
| 082 || 2 || 1 || ! style="background:lightgray" | || 535 || 03 || 1<br />
|- align="center"<br />
| 100 || #2 || 1 || ! style="background:lightgray" | || 550 || any || #<br />
|- align="center"<br />
| 110, 111 || # || 2 || ! style="background:lightgray" | || 600 || #2 || 1<br />
|- align="center"<br />
| 130 || # || 0 || ! style="background:lightgray" | || 610, 611 || # || 2<br />
|- align="center"<br />
| 210 || # || 1 || ! style="background:lightgray" | || 630 || # || 0<br />
|- align="center"<br />
| 222 || any || # || ! style="background:lightgray" | || 700 || #2 || 1<br />
|- align="center"<br />
| 240, 243 || 2 || 0 || ! style="background:lightgray" | || 710, 711 || # || 2<br />
|- align="center"<br />
| 240, 243 || 3 || 1 || ! style="background:lightgray" | || 730 || # || 0<br />
|- align="center"<br />
| 260 || 01456789 || # || ! style="background:lightgray" | || 800 || #2 || 1<br />
|- align="center"<br />
| 400 || #2 || 1 || ! style="background:lightgray" | || 810 || # || 2<br />
|- align="center"<br />
| 410, 411 || # || 2 || ! style="background:lightgray" | || 811 || # || 2<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===2nd indicator updates table===<br />
MARS 2.0 makes these changes to the 2nd indicator:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! align="center" |<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 050 || #123 || 0 || ! style="background:lightgray" | || 210 || 123456789 || #<br />
|- align="center"<br />
| 051 || 0123 || # || ! style="background:lightgray" | || 260 || any || #<br />
|- align="center"<br />
| 060 || #123 || 0 || ! style="background:lightgray" | || 440 || # || 0<br />
|- align="center"<br />
| 061 || 0123 || # || ! style="background:lightgray" | || 490 || any || #<br />
|- align="center"<br />
| 070, 071 || 0123 || # || ! style="background:lightgray" | || 600, 610, 611, 630 || # || 0<br />
|- align="center"<br />
| 072 || # || 0 || ! style="background:lightgray" | || 650, 651 || # || 0<br />
|- align="center"<br />
| 100, 110, 111, 130 || any || # || ! style="background:lightgray" | || 700, 710, 711, 730, 740 || 013 || #<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.4Step 2.42016-05-19T19:03:55Z<p>Nate: /* links */</p>
<hr />
<div>==Step 2.4: Subfield Updates & Deletes ==<br />
[[Image:rda2-1.png]]<br><br><br />
<br />
== Subfield Code Updates Table ==<br />
MARS 2.0 converts these subfield codes:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 024 || $b || $d<br />
|- align="center"<br />
| 050 || $d || $a<br />
|- align="center"<br />
| 111 || $b || $n<br />
|- align="center"<br />
| 242, 245, 246, 247 || $d || $n<br />
|- align="center"<br />
| 242, 245, 246, 247 || $e || $p<br />
|- align="center"<br />
| 411, 611, 711, 811 || $b || $n<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
== Subfield Deletes Table==<br />
MARS 2.0 deletes these subfields:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Tags<br />
! style="background:silver" align="center" | Subfield<br />
|- align="right"<br />
| 052 || $c<br />
|- align="right"<br />
| 100, 110, 111, 130, 240 || $h<br />
|- align="right"<br />
| 100, 110, 111, 130, 240, 247 || $w<br />
|- align="right"<br />
| 400, 410, 411 || $w<br />
|- align="right"<br />
| 500 || $l, $x, $z<br />
|- align="right"<br />
| 600, 610, 611, 630 || $h<br />
|- align="right"<br />
| 600, 610, 611, 630, 650, 651 || $w<br />
|- align="right"<br />
| 700, 710, 711, 730 || $h<br />
|- align="right"<br />
| 700, 710, 711, 730 || $w<br />
|- align="right"<br />
| 760, 762, 765, 767, 770 || $q<br />
|- align="right"<br />
| 772, 773, 774, 775, 776 || $q<br />
|- align="right"<br />
| 776, 777, 780, 785, 786, 787 || $q<br />
|- align="right"<br />
| 800, 810, 811, 830 || $w<br />
|- align="right"<br />
| 830 || $h, $x<br />
|- align="right"<br />
| 850 || $b<br />
|- align="right"<br />
| 850 || $d<br />
|- align="right"<br />
| 850 || $e<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
== Relator $e Deletions==<br />
Current cataloging practice restricts the use of Relator Term $e subfields in 100 Main Entry and 700 Added Entry-Personal Name fields. A common exception is the continued use of the relator term '''ill.''' for '''illustrators'''. Since there are many variants of '''ill.''' our MARS 2.0 software will look for these as well.<br />
<br />
===Relator terms table===<br />
MARS 2.0 deletes $e and its data in fields 100 and 700 if it contains one of these Relator Terms. If not found in this list, the information remains unchanged:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- align="left"<br />
| arr. || ed. || joint ed.<br />
|- align="left"<br />
| author || editor & translator || joint editor<br />
|- align="left"<br />
| comp. & arr. || editor and translator || joint tr.<br />
|- align="left"<br />
| comp. & tr. || editor || jt. auth.<br />
|- align="left"<br />
| comp. and arr. || joint auth. || jt. author<br />
|- align="left"<br />
| comp. and tr. || joint author || jt. ed.<br />
|- align="left"<br />
| comp. || joint authors || tr. & ed.<br />
|- align="left"<br />
| compiler || joint comp. || tr. and ed.<br />
|- align="left"<br />
| ed. & arr. || joint compiler || tr.<br />
|- align="left"<br />
| ed. & tr. || joint ed. & tr. || trans.<br />
|- align="left"<br />
| ed. and arr. || joint ed. and tr. || translator<br />
|- align="left"<br />
| ed. and tr.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Terms table for “ill.” changes===<br />
MARS 2.0 also changes the following variations to '''ill.''' in $e in fields 100 and 700:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- align="left"<br />
| comp. & illus. || ed. and illus. || jt. illus<br />
|- align="left"<br />
| comp. & ill. || ed. and ill. || jt. ill.<br />
|- align="left"<br />
| comp. and illus. || ill || tr. & illus.<br />
|- align="left"<br />
| comp. and ill. || illus || tr. & ill.<br />
|- align="left"<br />
| ed. & illus. || illustrator || tr. and illus<br />
|- align="left"<br />
| ed. & ill. || joint illus || tr. and ill.<br />
|}<br />
<div style=clear:both></div><br><br />
'''Note''': ''These are AACR2 tables. Some or all entries within RDA tables may be different. RDA processing options can be found in our separate MARS 2.0 guide.''<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.3Step 2.32016-05-19T19:03:45Z<p>Nate: /* links */</p>
<hr />
<div>==Step 2.3: Field Updates & Deletes==<br />
[[Image:rda2-1.png]]<br><br><br />
<br />
Changes to the MARC21 communications format have made many fields obsolete. If one field has been replaced by another, the change is shown in the Tag Updates table in this section.<br />
<br />
If the field has been made obsolete without being replaced, the field is simply deleted from the bibliographic record. Fields that are deleted as part of MARS 2.0 are listed in the Field Deletes List in this section.<br />
<br />
==Field Updates Table==<br />
Fields and subfields converted by MARS 2.0.<br><br />
(‘x’ represents any 2nd indicator value, ‘#’ represents a blank 2nd indicator value):<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! align="center" ! style="background:lightgray" |<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
|- align="center"<br />
| 023 || 024 [8#] || ! style="background:lightgray" | || 315 || 310<br />
|- align="center"<br />
| 211 [0x] || 246 [2#] || ! style="background:lightgray" | || 350$a $b || 037$c (CF,CR)<br />
|- align="center"<br />
| 211 [1x] || 246 [3#] || ! style="background:lightgray" | || 350$a || 020$c or 037$c* (BK,VM,MU)<br />
|- align="center"<br />
| 212 [0x] || 246 [2#] || ! style="background:lightgray" | || 503 || 500<br />
|- align="center"<br />
| 212 [1x] || 246 [3#] || ! style="background:lightgray" | || 507 || 255 (MP)<br />
|- align="center"<br />
| 212 [2x] || 246 [3#] || ! style="background:lightgray" | || 512 || 500<br />
|- align="center"<br />
| 212 [3x] || 246 [3#] || ! style="background:lightgray" | || 523 || 500<br />
|- align="center"<br />
| 214 [0x] || 246 [2#] || ! style="background:lightgray" | || 527 || 500<br />
|- align="center"<br />
| 214 [1x] || 246 [3#] || ! style="background:lightgray" | || 537 || 500<br />
|- align="center"<br />
| 265 $a || 037 $b || ! style="background:lightgray" | || 543 || 583<br />
|- align="center"<br />
| 308 $a & b || 300 $a || ! style="background:lightgray" | || 570 || 500<br />
|- align="center"<br />
| 308 $c, $d & f || 300 $b || ! style="background:lightgray" | || 755 || 655<br />
|- align="center"<br />
| 308 $e || 300 $c || ! style="background:lightgray" | || 840 || 830<br />
|}<br />
<div style=clear:both></div><br><br />
*MARS Processing will first attempt to convert 350$a to 020$c, but if unable to do so based on multiple or no ISBN, or multiple 350$a then it will fall back to 037$c.<br />
<br />
==Field Deletes List==<br />
MARS 2.0 removes the following fields:<br />
<br />
{| border="1" cellspacing="0" cellpadding="8" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | 0XX<br />
! style="background:silver" align="center" | 2XX<br />
! style="background:silver" align="center" | 3XX<br />
! style="background:silver" align="center" | 5XX<br />
! style="background:silver" align="center" | 6XX<br />
! style="background:silver" align="center" | 8XX<br />
|- align="center"<br />
| 009 || 241 || 302 || 517 || 652 || 851<br />
|- align="center"<br />
| 011 || ! style="background:lightgray" | || 303 || 582 || 680 || ! style="background:lightgray" | <br />
|- align="center"<br />
| 087 || ! style="background:lightgray" | || 304 || ! style="background:lightgray" | || 681 || ! style="background:lightgray" | <br />
|- align="center"<br />
| 091 || ! style="background:lightgray" | || 359 || ! style="background:lightgray" | || 683 || ! style="background:lightgray" | <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.2Step 2.22016-05-19T19:03:33Z<p>Nate: /* links */</p>
<hr />
<div>== Step 2.2 : Leader & Fixed Field Updates ==<br />
[[Image:rda2-1.png]]<br><br><br />
MARS 2.0 provides a variety of updates and corrections to values in the Leader and fixed fields (006, 007, 008).<br />
<br />
Step 2.2 can be customized according to your preference. If there is other information you wish to convey to us on this step, fill in '''With these modifications''' with more details.<br />
<br />
===Fixed field updates===<br />
Changes to MARC21 replaced many fixed field values or made them obsolete. In the leader, for example, the value '''p''' designating a “Record in partial ISBD form” in byte 18, Descriptive Cataloging Form, was made obsolete in 1987 and is now coded using value '''I''' (ISBD). MARS 2.0 Update converts an '''h''' value in Leader byte 18 to '''i'''.<br />
<br />
Bytes 18 (Frequency) and 19 (Regularity) in the 008 fixed field for Computer files/Electronic resources format materials were made obsolete in 1995. Additionally, 008 bytes 18-19 are undefined (should not be used) for Mixed materials format. MARS 2.0, therefore, converts any values in 008 bytes 18-19 to blanks for Computer files/Electronic resources and Mixed materials records.<br />
<br />
==MARS 2.0 Leader & Fixed Field Updates Table==<br />
In the following table, byte position is counted with the first byte being “00” (zero) to be consistent with MARC21 Bibliographic Format documentation. The table uses the following symbols:<br />
<font size="3"> # = blank space<br />
| = fill character</font><br />
<br />
Format codes are as follows (see [[Record_Format|Record Format]] for more details):<br />
<font size="3"> BK = Books<br />
CF = Computer files/Electronic resources<br />
MP = Maps<br />
MU = Music<br />
CR = Continuing resources (serials, etc.)<br />
VM = Visual materials<br />
MX = Mixed materials (includes obsolete Archival and Manuscripts control)</font><br />
<br />
'''Note''': ''‘x’ denotes record types affected''<br />
<br><br><br />
'''Leader'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 06 || h b n || a || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || p || i || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || r || i || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''006 Field'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| All || hex ‘00’ || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 06 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 07 || any || # || || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 08 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 09 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 10 || any || # || || || || || || ! style="background:lightgray" | x || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''007 Field'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| All || hex ‘00’ || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 02 || any || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos. 06-22'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| All || hex ‘00’ || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 06 || c || t || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 06 || d || e || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 18 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 19 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 19 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 20 || any || # || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 20 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 20 || any || # || || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 21 || a || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 21 || any || # || || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 21 || h || c || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 22 || any || # || || || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 22 || ghixz || # || || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 22 || uv || # || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || || || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos.23-25'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 23 || any || # || || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 23 || ghiz || # || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 23 || jpt || # || || || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 23 || x || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 24 || any || # || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 24 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 24 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 24 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 24 || y || # || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 24 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 24 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 24 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 25 || any || # || || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 25 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 25 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 25 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 25 || y || # || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 25 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 25 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 25 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos.26-27'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 26 || any || # || || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 26 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 26 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 26 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 26 || y || # || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 26 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 26 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 26 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 27 || any || # || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 27 || h || f || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 27 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 27 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 27 || y || # || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 27 || x || t || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 27 || 3 || k || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 27 || 4 || q || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
'''008 Field, pos.28-34'''<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" align="center" | Byte<br />
! style="background:silver" align="center" | From<br />
! style="background:silver" align="center" | To<br />
! style="background:silver" align="center" | BK<br />
! style="background:silver" align="center" | CF<br />
! style="background:silver" align="center" | MP<br />
! style="background:silver" align="center" | MU<br />
! style="background:silver" align="center" | CR<br />
! style="background:silver" align="center" | VM<br />
! style="background:silver" align="center" | MX<br />
|- align="center"<br />
| 28 || any || # || || || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 28 || n || o || ! style="background:lightgray" | x || || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 28 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 28 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 29 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 29 || j || i || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 29 || n || # || || || || ! style="background:lightgray" | x || || || <br />
|- align="center"<br />
| 30 || any || # || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 31 || any || # || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 32 || any || # || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 33 || any || # || || ! style="background:lightgray" | x || || || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 33 || abcdfghmq || z || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 33 || e || v || || || || || || ! style="background:lightgray" | x || <br />
|- align="center"<br />
| 33 || # || 0 || ! style="background:lightgray" | x || || || || || || <br />
|- align="center"<br />
| 34 || any || # || || ! style="background:lightgray" | x || || ! style="background:lightgray" | x || || || ! style="background:lightgray" | x<br />
|- align="center"<br />
| 34 || abcdfghmq || z || || || ! style="background:lightgray" | x || || || || <br />
|- align="center"<br />
| 34 || dmt || # || || || || || ! style="background:lightgray" | x || || <br />
|- align="center"<br />
| 34 || # || n || || || || || || ! style="background:lightgray" | x || <br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.1Step 2.12016-05-19T19:03:20Z<p>Nate: /* links */</p>
<hr />
<div>== Step 2.1: Validation ==<br />
[[Image:rda2-1.png]]<br><br />
<br />
== Numeric Field Validation ==<br />
MARC fields that are incorrectly formatted often cause user searches to fail and prevent items in the collection from being included in the system indexes. MARS 2.0 software can validate the structure of numeric data in the following fields:<ul><li>010: Library of Congress Control Number (LCCN)<li>020: International Standard Book Number (ISBN)<li>022: International Standard Serial Number (ISSN)<li>034: Coded Cartographic Mathematic Data (CCMD)</ul><br />
<br />
=== Historical fact ===<br />
LC changed the structure of the LCCN beginning on Jan. 1, 2001 in order to accommodate a four-digit year. The length of the control number remains 12 characters as it was prior to the change. However, in the old LCCN structure (A), suffixes were occasionally used. Under the new LCCN structure (B), the location of elements is slightly altered to accommodate a four-digit year. Under both structures, the prefix, year and serial number are the basic elements required to make a LCCN unique.<br />
<br />
Please indicate on Step 2.1 what kind of validation you would like performed on your 010, 020, 022, or 034 fields. Choosing '''Yes, With these modifications''' means that you would like the MARS 2.0 software to perform a modified validation (e.g., validate fields 020 and 022, but not fields 010 or 034).<br />
<br />
== Pre-2001 LCCN ==<br />
LCCN Structure A (2000 and earlier) numbers are formatted according to the following 6 divisions (separated by hyphens):<br><br />
<font size="3"> 1 2 3 4 5 6<br />
nb#-71-005810-#-/AC-/r86</font><br />
<br />
#3-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''<br />
#2 digits, usually the last 2 digits of the '''year'''<br />
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits<br />
#Blank '''space'''<br />
#Optional variable length '''suffix''' and/or alphabetic identifier<br />
#Optional '''revision date'''<br />
<br />
Examples of LCCN Structure A (the character # represents a single space):<br><br />
<font size="3"> ###95156543# Displayed as: 95-156543<br />
###94014580#/AC/r95 Displayed as: 94-14580/AC/r95<br />
###79310919#//r86 Displayed as: 79-310919//r86<br />
nb#71005810# Displayed as: nb71-5810</font><br />
<br />
== Post-2000 LCCN ==<br />
LCCN Structure B (2001 and later) numbers are formatted according the following 3 divisions (separated by hyphens):<br><br />
<font size="3"> 1 2 3<br />
##-2005-256543</font><br />
<br />
#2-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''<br />
#4-digit '''year'''<br />
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits<br />
<br />
Examples of LCCN Structure B (the character # represents a single space):<br><br />
<font size="3"> ##2005256543 Displayed as: 2005-256543<br />
##2010014580 Displayed as: 2010-14580<br />
nb2005005810 Displayed as: nb2005-5810</font><br />
<br />
According to the Library of Congress, Structure A LCCNs will not be changed to Structure B. This minimizes the impact of the LCCN change for local systems. Since LCCN structures A and B will continue to exist in authority and bibliographic records, MARS 2.0 programs provide for validation of both old and new LCCN formats. No provision is necessary, therefore, for the conversion of Structure A to the new Structure B formats, or vice versa.<br />
<br />
=== LCCN structure A corrections ===<br />
If the LCCN in the 010 $a is identified as a Structure A LCCN and does '''not''' have a valid structure, MARS 2.0 programs make the following format corrections (all changes are subsequently checked for validity):<br />
*If the first character of the LCCN is a number (no prefix is present), the programs insert 3 blanks (###) before the number:<br />
<font size="3"> Original: 95-156543 Corrected to: ###95156543#</font><br />
<br />
*If the first character of the LCCN is an alphabetic character and the second character is a number, MARS 2.0 programs insert 2 blanks (##) between the alphabetic character and the number to make a valid 3-character prefix:<br />
<font size="3"> Original: n95-156543 Corrected to: n##95156543#</font><br />
<br />
*If the first 2 characters of the LCCN are alphabetic and the third character is a number, MARS 2.0 programs insert 1 blank (#) between the alphabetic characters and the number to make a valid 3-character prefix:<br />
<font size="3"> Original: nb95-156543 Corrected to: nb#95156543#</font><br />
<br />
*If a hyphen appears in the 010 $a, MARS 2.0 programs count the number of digits before the hyphen. If one digit is before the hyphen, a 0 (zero) is inserted before the first digit in the LCCN (following the prefix). If 2 digits are before the hyphen, no zeroes are inserted at the beginning of the LCCN:<br />
<font size="3"> Original: nb#9-156543 Corrected to: nb#09156543#<br />
Original: nb#95-156543 Corrected to: nb#95156543#</font><br />
<br />
*MARS 2.0 programs also count the number of digits following the hyphen. If there are fewer than 6 digits, zeroes are added following the first 2 digits (##-) of the LCCN to make 6 digits (for a total of 8 digits). The hyphen is deleted from the LCCN:<br />
<font size="3"> Original: nb#95-6543 Corrected to: nb#95006543#<br />
Original: nb#95-56543 Corrected to: nb#95056543#</font><br />
<br />
*If the LCCN contains a suffix, the suffix is removed in accordance with the revised LC standard for Structure A LCCNs:<br />
<font size="3"> Original: nb#95-516543//r86 Corrected to: nb#95156543#</font><br />
<br />
*If the LCCN does not end with a blank, MARS 2.0 programs insert a blank following the last digit:<br />
<font size="3"> Original: nb#95-516543 Corrected to: nb#95156543#</font><br />
<br />
*If the 010 field data has been modified, the 010 field length is recalculated and the 010 directory entry is updated. The record length is recalculated and updated in the record leader.<br />
<br />
*If MARS 2.0 programs cannot correct the format of the LCCN in the 010 $a (e.g., there are 4 characters in the prefix or there are 9 digits), the 010 $a code is changed to $z and a report can be generated. See report R50 in step 5 for more information about this report.<br />
<br />
*The following invalid LCCN prefixes are corrected to the valid format (# = blank):<br />
<font size="3"> #a# -> a##<br />
##a -> a##<br />
#bc -> bc#<br />
# -> ###<br />
## -> ###</font><br />
<br />
=== LCCN structure B corrections ===<br />
If the LCCN in the 010 $a is identified as a Structure B LCCN and does not have a valid structure, MARS 2.0 programs attempt to correct it by making these conversions (all changes are subsequently checked for validity):<br />
*If the first character of the LCCN is a number (no prefix is present), the programs insert 2 blanks before the number:<br />
<font size="3"> Original: 2005-256543 Corrected to: ##2005256543</font><br />
<br />
*If the first character of the LCCN is an alphabetic character and the second character is a number, MARS 2.0 programs insert 1 blank (#) between the alphabetic character and the number to make a valid 2-character prefix:<br />
<font size="3"> Original: n2005-256543 Corrected to: n#2005256543<br />
Original: nb2005-256543 Corrected to: nb2005256543</font><br />
<br />
*If a hyphen or blank space appears in the 010 $a, MARS 2.0 programs count the number of digits following the hypen. If there are fewer than 6 digits, zeroes are added following the first 4 digits (####-) of the LCCN to make 6 digits (for a total of 10 digits). The hyphen is deleted from the LCCN:<br />
<font size="3"> Original: nb2005-6543 Corrected to: nb2005006543</font><br />
<br />
*If the 010 field data has been modified, the 010 field length is recalculated and the 010 directory entry is updated. The record length is recalculated and updated in the record leader.<br />
<br />
*If MARS 2.0 programs cannot correct the format of the LCCN in the 010 $a (e.g., there are 3 characters in the prefix or there are 11 digits), the 010 $a code is changed to $z and a report can be generated. See report R50 in Step 5 for more information about this report.<br />
<br />
*The following invalid LCCN prefixes are corrected to the valid format (# = blank):<br />
<font size="3"> #a -> a#<br />
#bc -> bc<br />
# -> ##</font><br />
<br />
== 020 Field ==<br />
Some automated systems do not index an ISBN if the format is invalid. An ISBN in field 020 $a should be 10 digits or 13 digits. If the ISBN in 020 $a does not have the valid structure, MARS 2.0 programs attempt to correct the ISBN structure by performing the following conversions:<br />
*If there are 9 digits in the ISBN, a 0 (zero) is inserted before the first digit in the ISBN:<br />
<font size="3"> Original: 873671008 Corrected to: 0873671008</font><br />
<br />
*All hyphens are deleted:<br />
<font size="3"> Original: 1-873671-008 Corrected to: 1873671008</font><br />
<br />
*A lowercase x is converted to uppercase:<br />
<font size="3"> Original: 187367100x Corrected to: 187367100X</font><br />
<br />
*If ISBN is 13 digits, MARS 2.0 programs will verify that the first 3 digits are '''978'''.<br />
<br />
*As an optional service, MARS 2.0 programs will correct the order of the ISBN (i.e. pairs of 13/10 and 13/10)<br />
<br />
*As an optional service, MARS 2.0 programs will convert ISBN-10 to ISBN-13 (includes check-sum value for both 10 and 13 length ISBNs):<br />
<font size="3"> Original: 1873671008 Corrected to: 9781873671000</font><br />
<br />
*If MARS 2.0 programs cannot correct the format of the ISBN in the 020 $a (e.g., there are 11 digits), the 020 $a code is changed to $z and a report is generated. See report R50 in Step 5 for more information about this report.<br />
<br />
=== Historical fact ===<br />
The structure of the ISBN has changed over the past thirty years. Prior to 1977, the 020 field was not repeatable and multiple ISBNs and related information were placed in repeated subfields. Older bibliographic records may still have multiple ISBNs in a single 020 field rather than in multiple 020 fields. January 1, 2007 marked the final date for fully adopting ISBN-13. Between 2005 and 2008, publishers were encouraged to supply both an ISBN-10 and an ISBN-13 for the same manifestation, based on guidelines issued by the International ISBN Agency (IIA). The Library of Congress began accommodating ISBN-13 on October 1, 2004. At the beginning of 2007 is when publishers were expected to supply only ISBN-13.<br />
<br />
=== Ordering 020 fields ===<br />
LC will accept both an ISBN-13 and an ISBN-10 for the same manifestation. These numbers are shown by publishers according to guidelines issued by the IIA, which call for grouping the pairs of ISBNs by manifestation. In printed products the ISBN-13 appears first, and each number is preceded by a print constant as in the following example:<br><br />
<font size="3"> ISBN-13: 978-1-873671-00-0<br />
ISBN-10: 1-873671-008</font><br />
<br />
=== Repeating 020 subfields ===<br />
MARS 2.0 Update processing validates an 020 field for correct subfield repeatability. If the 020 field contains multiple $a, each $a is placed in a separate 020 field:<br><br />
<font size="3"> 020 $a 11111111 $a 22222222<br />
Corrected to:<br />
020 $a 11111111<br />
020 $a 22222222</font><br />
<br />
=== Binding information in 020 fields ===<br />
Prior to 1978, binding information was placed in a $b. Older bibliographic records may have binding information in a $b rather than as a parenthetical qualifier in the $a.<br />
<br />
If the 020 field contains a $b and an 020 $a exists:<br />
*$b delimiter and subfield code are deleted<br />
*020 $b data is enclosed in parentheses<br />
*A blank is inserted at the end of the immediately preceding 020 $a data<br />
*020 $b data, enclosed in parentheses, is moved after the blank at the end of the 020 $a data<br />
<font size="3"> Original: 020 $a 1873671008 $b pbk. Corrected to: 020 $a 1873671008 (pbk.)</font><br />
<br />
=== 020 with missing $a ===<br />
If the 020 field contains a $b and no 020 $a exists, the $b code will be changed to $c:<br><br />
<font size="3"> 020 $b pbk.<br />
Corrected to:<br />
020 $c pbk.</font><br />
<br />
=== 020 with multiple $c ===<br />
If the 020 field contains multiple $c, each $c is placed in a separate 020 field:<br><br />
<font size="3"> 020 $c 4.95 (lib. bdg.) $c 3.60 (pbk.)<br />
Corrected to:<br />
020 $c 4.95 (lib. bdg.)<br />
020 $c 3.60 (pbk.)</font><br />
Please note that if 020 $c follows an existing $q in the '''same field''', the 020 $c will '''not''' be moved to a separate 020 field.<br />
<br />
=== 020 with multiple $a and $c ===<br />
MARS 2.0 programs correctly handle 020 fields with multiple $a and $c:<br><br />
<font size="3"> 020 $a 11111111 $c 4.95 $a 22222222 $c 3.60 $c 8.97 $b pbk.<br />
Corrected to:<br />
020 $a 11111111 $c 4.95<br />
020 $a 22222222 $c 3.60<br />
020 $c 8.97 (pbk.)</font><br />
<br />
== 022 Field ==<br />
MARS 2.0 Update processing can validated the format of the ISSN in field 022 $a. Some automated systems do not index an ISSN if the format is invalid. A valid ISSN in field 022 $a has the following structure: 4 digits, hyphen, 4 digits (or digits and an X):<br><br />
<font size="3"> 1234-1234<br />
1234-123X</font><br />
<br />
If the ISSN in field 022 $a does not have the valid structure, MARS 2.0 programs attempt to correct it by making these conversions:<br />
*If the ISSN has no hyphen, adds a hyphen between the fourth and fifth digits:<br />
<font size="3"> Original: 123<u>4</u>5678 Corrected to: 123<u>4-5</u>678</font><br />
<br />
*Converts a lowercase '''x''' to uppercase:<br />
<font size="3"> Original: 1234-567<u>x</u> Corrected to: 1234-567<u>X</u></font><br />
<br />
*If MARS 2.0 programs cannot correct the format of the ISSN in the 022 $a (e.g., there are 9 digits), the 022 $a code is changed to $y and a report is generated. See report R50 in Step 5 for more information about this report.<br />
<br />
== 034 Field ==<br />
MARS 2.0 Update processing can validate field 034 CMD (Coded Mathematical Data) for correct format. If the 034 field first indicator has value 2 and the 034 field contains multiple $a, MARS 2.0 Update processing:<br />
*Places each $a in a separate 034 field<br />
*Changes each 034 field first indicator to value 1<br />
<font size="3"> 034 2_$a a $b 100000 $a a $b 120000<br />
Corrected to:<br />
034 1_$a a $b 100000<br />
034 1_$a a $b 120000</font><br />
<br />
=== Historical fact ===<br />
First indicator value '''2''' became obsolete when field 034 was made repeatable in 1982. Older bibliographic records may still have first indicator value 2.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.0Step 2.02016-05-19T19:03:00Z<p>Nate: /* Topics */</p>
<hr />
<div>==Bibliographic Validation & Cleanup==<br />
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.<br />
<br />
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.<br />
<br />
=== Standard MARC21 validation ===<br />
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><br />
'''Note''': ''MARS 2.0 programs can process MARC21 records that lack 001, 008 or other fields.''<br />
<br />
== Topics ==<br />
Section 2 is one of our most comprehensive documents, and as such is too large for a single page. <br />
* [[Step 2.1|Step 2.1]] - Validate 010, 020, 022, 034 fields<br />
* [[Step 2.2|Step 2.2]] - Leader & fixed field updates<br />
* [[Step 2.3|Step 2.3]] - Field updates & deletes<br />
* [[Step 2.4|Step 2.4]] - Subfield updates & deletes<br />
* [[Step 2.5|Step 2.5]] - Indicator values<br />
* [[Step 2.6|Step 2.6]] - Field conversions & additions<br />
* [[Step 2.7|Step 2.7]] - Initial article & filing indicators<br />
* [[Step 2.8|Step 2.8]] - GMD standardization<br />
* [[Step 2.10|Step 2.10]] - Accelerated Reader & Lexile Measures<br />
* [[Step 2.11|Step 2.11]] - Identities Management<br />
<br />
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.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Natehttps://ac.bslw.com/community/wiki/index.php/Step_2.12Step 2.122016-05-19T18:58:05Z<p>Nate: Created page with "==Step 2.11: Identities Management== Image:a2-11.png<br><br> MARS 2.0 offers two types of identities management options for identifiers or URIs ([https://en.wikipedia.org/wik..."</p>
<hr />
<div>==Step 2.11: Identities Management==<br />
[[Image:a2-11.png]]<br><br><br />
MARS 2.0 offers two types of identities management options for identifiers or URIs ([https://en.wikipedia.org/wiki/Uniform_Resource_Identifier| link]) within your records. Please check with your project manager for any fees that may be associated with these options.<br />
<br />
===Add $0 to Access Points===<br />
Adding either the identifier or URI onto the ends of matching access points within a bibliographic record can help facilitate easier matching between bibs and authorities. The identifiers or URIs may also assist library management systems (LMS) in harvesting that data and making further use of it in a semantic way.<br />
<br />
This particular option allows us to add the '''$0''' at the end of a given access point which has found an authority match against a database which also references a URI. Essentially, our processing can add either the identifier or the URI itself onto your headings.<br />
<br />
Here is an example of a before/after record adding a matching authority identifier:<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0 nr 99034050 </font><br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0 sh 85004836 </font><br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0 D000716 </font><br />
</font><br />
<br />
Please note that, in addition to adding identifiers from Library of Congress, the processing also added a matching identifier from the National Library of Medicine.<br />
<br />
Adding the actual URIs is very similar to the examples above, except the full URI link is added to the corresponding '''$0''':<br />
<font size="3"><br />
'''original record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator.<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic.<br />
650 #2 $a Anatomy, Artistic.<br />
<br />
'''updated record''':<br />
100 1# $a Bouchardon, Edme, $d 1698-1762, $e illustrator <font color='blue'>$0</font> [http://id.loc.gov/authorities/names/nr99034050| http://id.loc.gov/authorities/names/nr99034050]<br />
245 12 $a L'anatomie necessaire pour l'usage du dessein /$c par Edme Bouchardon.<br />
650 #0 $a Anatomy, Artistic. <font color='blue'>$0</font> [http://id.loc.gov/authorities/subjects/sh85004836| http://id.loc.gov/authorities/subjects/sh85004836]<br />
650 #2 $a Anatomy, Artistic. <font color='blue'>$0</font> [https://id.nlm.nih.gov/mesh/D000716.html| https://id.nlm.nih.gov/mesh/D000716.html]<br />
</font><br />
<br />
Depending on your ultimate goal with receiving identifiers vs URIs will help inform your decision as to which one to receive within your bibliographic records. If you select this option in your profile, our ''default'' is to add the '''identifier''' only in the '''$0'''. One thing to note is that, while we also default to adding the $0 at the ''end of the access point'', we can also add it after the ''last matching portion'' of your heading. Some libraries may prefer this, especially in the case of partially matched headings, though most libraries elect to add it to the end of the heading itself.<br />
<br />
===Add URIs to Authority Records===<br />
With this option, libraries can elect to receive the identifiers and URIs directly within delivered authority records. This can be especially useful when considering multiple sets of identifiers or URIs associated with a particular heading. For example, in addition to Library of Congress, MARS 2.0 can currently also query VIAF ([https://viaf.org/| link]) and ISNI ([http://www.isni.org/| link]) URIs to insert into matching authorities.<br />
<br />
One of our clients decided to use '''92X''' fields within the authority records as it looked like those fields were currently unused by most institutions and record-distributor vendors. Another vendor decided to take this option a step further; in addition to adding the 92X fields that corresponded to national authority file URIs, this other vendor also wanted the associated ''identifiers'' added to '''024''' fields ([http://www.loc.gov/marc/authority/ad024.html| link]).<br />
<br />
Here is an example of an authority record delivered with both 024 and 92X fields populated:<br />
<font size="3"><br />
001 ## no2001000753<br />
024 7# $a <font color='blue'>no2001000753</font> $2 lccn<br />
024 7# $a <font color='blue'>23238834</font> $2 viaf<br />
024 7# $a <font color='blue'>0000000116075005</font> $2 isni<br />
100 1# $a Volkmann, Hans<br />
920 ## $a [http://id.loc.gov/authorities/names/no2001000753| http://id.loc.gov/authorities/names/no2001000753]<br />
921 ## $a [http://viaf.org/viaf/23238834| http://viaf.org/viaf/23238834]<br />
922 ## $a [http://isni.org/isni/0000000116075005| http://isni.org/isni/0000000116075005]<br />
</font><br />
<br />
This option is typically processed in a retrospective manner, taking all of your existing authority records and enriching them with identifiers/URIs. Ongoing authority work (where authorities are delivered) can also incorporate this option.<br />
<br />
==links==<br />
<center><font size="4">[[Step 2.1|2.1]] - [[Step 2.2|2.2]] - [[Step 2.3|2.3]] - [[Step 2.4|2.4]] - [[Step 2.5|2.5]] - [[Step 2.6|2.6]] - [[Step 2.7|2.7]] - [[Step 2.8|2.8]] - [[Step 2.10|2.10]] - [[Step 2.11|2.11]]<br />
<hr><br />
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center><br />
[[category:Profile Guide]]</div>Nate