https://ac.bslw.com/community/wiki/api.php?action=feedcontributions&user=Judy&feedformat=atomAC Wiki - User contributions [en]2024-03-28T16:00:22ZUser contributionsMediaWiki 1.23.14https://ac.bslw.com/community/wiki/index.php/RDA_4.5RDA 4.52014-05-19T19:59:46Z<p>Judy: /* SMD Update Table */</p>
<hr />
<div>==RDA 4.5: 300 field (Physical Description)==<br />
[[image:rda4-5.png]]<br />
<br />
The following sections detail the abbreviations that will be spelled out in this step. [http://access.rdatoolkit.org/document.php?id=rdachp1&target=rda1-885# RDA 1.7.8] (html)<br />
===Extent===<br />
This table lists extent abbreviations that will be expanded in the 300 $a: [http://access.rdatoolkit.org/document.php?id=rdachp3&target=rda3-2085# RDA 3.4.1.3] (html)<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| approx. || approximately || l. #-# || leaves<br />
|-<br />
| ca. || approximately || lvs. || leaves<br />
|-<br />
| col. || color || numb. || numbered<br />
|-<br />
| cov. || cover || obl. || oblong<br />
|-<br />
| dia. || diameter || p. # || page<br />
|-<br />
| diagr. || diagram || p. #-# || pages<br />
|-<br />
| diagrs. || diagrams || p.l. || preliminary leaves<br />
|-<br />
| fig. || figures || pent. || pentagram<br />
|-<br />
| fold. || folded || pp. || pages<br />
|-<br />
| front. || frontispiece || unnum. || unnumbered<br />
|-<br />
| frontis. || frontispiece || unp. || unpaged<br />
|-<br />
| fronts. || frontispiece || v. # || volume<br />
|-<br />
| ill. || illustrations || v. #-# || volumes<br />
|-<br />
| illus. || illustrations || v. #-# || volumes<br />
|-<br />
| irr. || irregular || vol. #-# || volumes<br />
|-<br />
| l. # || leaf || vols. || volumes<br />
|}<br />
<div style=clear:both></div><br />
<br />
Some additional changes that are made to the 300 $a include the following:<br />
*A number followed by brackets with i.e. will be changed to ''''that is'''': [http://access.rdatoolkit.org/document.php?id=rdachp3&target=rda3-2834# RDA 3.4.5.5] (html)<br />
**'''48 [i.e. 52] p.''' becomes '''48, that is 52, pages'''.<br />
<br />
*Brackets around a number will be changed to ''''unnumbered'''': [http://access.rdatoolkit.org/document.php?id=rdachp3&target=rda3-2732# RDA 3.4.5.3] (html)<br />
**'''[16] p.''' becomes '''16 unnumbered pages'''.<br />
<br />
===Other physical details===<br />
Abbreviations within the 300 $b (other physical details) that will be expanded include the following: [http://access.rdatoolkit.org/document.php?id=rdachp7&target=rda7-1090# RDA 7.15.1] (html)<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| b&w || black & white || ill. || illustrations<br />
|-<br />
| col. || color || illus. || illustrations<br />
|-<br />
| diagr. || diagram || incl. || including<br />
|-<br />
| diagrs. || diagrams || l. || leaves<br />
|-<br />
| fac. || facsimiles || phot. || photographs<br />
|-<br />
| facs. || facsimiles || photo. || photographs<br />
|-<br />
| facsim. || facsimiles || port. || portrait<br />
|-<br />
| facsims. || facsimiles || ports. || portraits<br />
|-<br />
| fig. || figures || sam. || samples<br />
|-<br />
| fold. || folded || samp. || samples<br />
|-<br />
| front. || frontispiece || sd. || sound<br />
|-<br />
| frontis. || frontispiece || si. || silent<br />
|-<br />
| gen. || genealogical || snd. || sound<br />
|-<br />
| geneal. || genealogical || tab. || tables<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Dimensions===<br />
Many abbreviations are still allowed in the dimensions subfield (300 $c). For instance, ''''in.'''' is still authorized to represent inches. ("cm" is considered a symbol, not an abbreviation.) [http://access.rdatoolkit.org/document.php?id=rdachp3&target=rda3-3165# RDA 3.5.1.3] (html) However (for continuity), the following table lists the abbreviations that will change in the 300 $c:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| ca. || approximately || inches || in.<br />
|-<br />
| cov. || cover || irr. || irregular<br />
|-<br />
| dia. || diameter || lvs. || leaves<br />
|-<br />
| feet || ft. || numb. || numbered<br />
|-<br />
| fol. || folio || obl. || oblong<br />
|-<br />
| fold. || folded || p. || pages<br />
|-<br />
| foot || ft. || pent. || pentagram<br />
|-<br />
| inch || in. || pp. || pages<br />
|-<br />
| || || unnum. || unnumbered<br />
|}<br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
300 $a 300 <font color="red">p.</font> : $b <font color="red">ill.</font> ; $c 4to.<br />
300 $a [<font color="red">unp.</font>] : $b <font color="red">ill.</font> (some <font color="red">col.</font>) ; $c 6 in.<br />
300 $a 3 <font color="red">v.</font> : $b <font color="red">facsims.</font>, <font color="red">ports.</font> ; $c 24 x 36 cm.<br />
300 $a 3 <font color="red">p.l.</font>, <font color="red">ca.</font> 245 <font color="red">pp.</font> : $b <font color="red">geneal.</font> tables ; $c <font color="red">fol.</font><br />
300 $a 92 <font color="red">[i.e. 96] pp.</font> : $b <font color="red">sd., col.</font> ; $c 24mo.<br />
300 $a <font color="red">[16] p.</font> of plates : $b <font color="red">col. illus.</font> ; $c 12mo.<br />
<br />
'''updated fields''':<br />
300 $a 300 <font color="red">pages</font> : $b <font color="red">illustrations</font> ; $c 4to.<br />
300 $a [<font color="red">unpaged</font>] : $b <font color="red">illustrations</font> (some <font color="red">color</font>) ; $c 6 in.<br />
300 $a 3 <font color="red">volumes</font> : $b <font color="red">facsimiles</font>, <font color="red">portraits</font> ; $c 24 x 36 cm<br />
300 $a 3 <font color="red">preliminary leaves</font>, <font color="red">approximately</font> 245 <font color="red">pages</font> : $b <font color="red">genealogical</font> tables ; $c <font color="red">folio.</font><br />
300 $a 92<font color="red">, that is 96, pages</font> : $b <font color="red">sound, color</font> ; $c 24mo.<br />
300 $a <font color="red">16 unnumbered pages</font> of plates : $b <font color="red">color illustrations</font> ; $c 12mo.</font><br />
<br />
==SMD Update Table==<br />
MARS 2.0 updates common SMD's to their RDA equivalent. The following chart shows a sampling:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | AACR2 Term<br />
! style="background:silver" | RDA Term<br />
|-<br />
| quad. || Quadraphonic<br />
|-<br />
| transparency || overhead transparency<br />
|-<br />
| computer disk || computer disc<br />
|-<br />
| computer optical disc || computer disc<br />
|-<br />
| sound disk || audio disc<br />
|-<br />
| sound cassette || audiocassette<br />
|-<br />
<br />
|}<br />
<div style=clear:both></div><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Make all physical description updates in 300 field.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.5RDA 5.52014-05-19T19:36:08Z<p>Judy: /* Special Note */</p>
<hr />
<div>==RDA 5.5: Relator Terms==<br />
[[image:rda5-5.png]]<br />
===Relator terms===<br />
In AACR2, many relator terms were not included on headings. With RDA, the relator terms are retained and expanded if they are in their abbreviated form. MARS 2.0 will retain all relator terms in X00 $e, X10 $e, and X11 $j (unless otherwise directed). [http://access.rdatoolkit.org/document.php?id=rdachp18&target=rda18-274# RDA 18.5.1.3] (html) [http://www.loc.gov/marc/relators/ MARC relators] (html) <br />
<br />
The following relator term abbreviations will be expanded:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" style="border-collapse:collapse;"<br />
|-<br />
|- align="center" style="background: #C0C0C0"<br />
| Abbreviated || Expanded || Abbreviated || Expanded<br />
|- align="center" style="background: white"<br />
| arr. || arranger || joint tr. || translator<br />
|- align="center" style="background: white"<br />
| auth. || author || joint trans. || translator<br />
|- align="center" style="background: white"<br />
| comp. || compiler || jt. || <br />
|- align="center" style="background: white"<br />
| ed. || editor || jt. auth. || author<br />
|- align="center" style="background: white"<br />
| edit. || editor || jt. comp. || compiler<br />
|- align="center" style="background: white"<br />
| eds. || editor || jt. ed. || editor<br />
|- align="center" style="background: white"<br />
| edt. || editor || jt. ill. || illustrator<br />
|- align="center" style="background: white"<br />
| ill. || illustrator || jt. illus. || illustrator<br />
|- align="center" style="background: white"<br />
| illus. || illustrator || jt. tr. || translator<br />
|- align="center" style="background: white"<br />
| joint auth. || author || jt. trans. || translator<br />
|- align="center" style="background: white"<br />
| joint comp. || compiler || lbt || librettist<br />
|- align="center" style="background: white"<br />
| joint ed. || editor || pub || publisher<br />
|- align="center" style="background: white"<br />
| joint ill. || illustrator || publ || publisher<br />
|- align="center" style="background: white"<br />
| joint illus. || illustrator || tr. || translator<br />
|- align="center" style="background: white"<br />
| || || trans. || translator<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Open Metadata Registry===<br />
MARS 2.0 also utilizes an RDF-derived list of relator terms from the [http://metadataregistry.org/schemaprop/list/schema_id/4.html Open Metadata Registry] as well as the [http://www.loc.gov/marc/relators/relaterm.html Relator Term List]. At the time of this update, there are over 460 unique terms that MARS 2.0 utilizes to check your relator terms. If any relator terms do not appear on this list, they are flagged for one of our standard reports ([http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms R119]). In addition to this, Backstage also employs common typo lists to check and correct for errors (e.g., 'astor' corrected to 'actor').<br />
<br />
==Convert $e term to $4 code==<br />
MARS 2.0 processing can convert your $e relator terms to $4 relator codes, provided there is a match against our extensive list of available relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e actor</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e director</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e politician</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- </font><br />
Note that '''$e politician''' is not a currently acceptable $e relator term. MARS 2.0 processing will flag this unrecognized relator term and add it to a standard report (see [http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms Step 6.2, R119]).<br />
<br />
==Convert $4 code to $e term==<br />
MARS 2.0 processing can also convert $4 relator codes to $e relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 pro</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e actor</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e director</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e producer</font></font><br />
===Special Note===<br />
(1) PCC guidelines do not currently recommend using a relator term in $e in conjunction with a relator code in $4, within the same field. Backstage offers this as an option should you wish to pursue it.<br />
<br />
(2) In the 700 and 710 fields that have a $t, we will remove any occurring $e. In the 711 field that has a $t, we will remove any occurring $j.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Expand relator term abbreviations in X00 $e, X10 $e, and X11 $j fields.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.5RDA 5.52014-05-19T19:25:40Z<p>Judy: /* Convert $4 code to $e term */</p>
<hr />
<div>==RDA 5.5: Relator Terms==<br />
[[image:rda5-5.png]]<br />
===Relator terms===<br />
In AACR2, many relator terms were not included on headings. With RDA, the relator terms are retained and expanded if they are in their abbreviated form. MARS 2.0 will retain all relator terms in X00 $e, X10 $e, and X11 $j (unless otherwise directed). [http://access.rdatoolkit.org/document.php?id=rdachp18&target=rda18-274# RDA 18.5.1.3] (html) [http://www.loc.gov/marc/relators/ MARC relators] (html) <br />
<br />
The following relator term abbreviations will be expanded:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" style="border-collapse:collapse;"<br />
|-<br />
|- align="center" style="background: #C0C0C0"<br />
| Abbreviated || Expanded || Abbreviated || Expanded<br />
|- align="center" style="background: white"<br />
| arr. || arranger || joint tr. || translator<br />
|- align="center" style="background: white"<br />
| auth. || author || joint trans. || translator<br />
|- align="center" style="background: white"<br />
| comp. || compiler || jt. || <br />
|- align="center" style="background: white"<br />
| ed. || editor || jt. auth. || author<br />
|- align="center" style="background: white"<br />
| edit. || editor || jt. comp. || compiler<br />
|- align="center" style="background: white"<br />
| eds. || editor || jt. ed. || editor<br />
|- align="center" style="background: white"<br />
| edt. || editor || jt. ill. || illustrator<br />
|- align="center" style="background: white"<br />
| ill. || illustrator || jt. illus. || illustrator<br />
|- align="center" style="background: white"<br />
| illus. || illustrator || jt. tr. || translator<br />
|- align="center" style="background: white"<br />
| joint auth. || author || jt. trans. || translator<br />
|- align="center" style="background: white"<br />
| joint comp. || compiler || lbt || librettist<br />
|- align="center" style="background: white"<br />
| joint ed. || editor || pub || publisher<br />
|- align="center" style="background: white"<br />
| joint ill. || illustrator || publ || publisher<br />
|- align="center" style="background: white"<br />
| joint illus. || illustrator || tr. || translator<br />
|- align="center" style="background: white"<br />
| || || trans. || translator<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Open Metadata Registry===<br />
MARS 2.0 also utilizes an RDF-derived list of relator terms from the [http://metadataregistry.org/schemaprop/list/schema_id/4.html Open Metadata Registry] as well as the [http://www.loc.gov/marc/relators/relaterm.html Relator Term List]. At the time of this update, there are over 460 unique terms that MARS 2.0 utilizes to check your relator terms. If any relator terms do not appear on this list, they are flagged for one of our standard reports ([http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms R119]). In addition to this, Backstage also employs common typo lists to check and correct for errors (e.g., 'astor' corrected to 'actor').<br />
<br />
==Convert $e term to $4 code==<br />
MARS 2.0 processing can convert your $e relator terms to $4 relator codes, provided there is a match against our extensive list of available relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e actor</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e director</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e politician</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- </font><br />
Note that '''$e politician''' is not a currently acceptable $e relator term. MARS 2.0 processing will flag this unrecognized relator term and add it to a standard report (see [http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms Step 6.2, R119]).<br />
<br />
==Convert $4 code to $e term==<br />
MARS 2.0 processing can also convert $4 relator codes to $e relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 pro</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e actor</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e director</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e producer</font></font><br />
===Special Note===<br />
PCC guidelines do not currently recommend using a relator term in $e in conjunction with a relator code in $4, within the same field. Backstage offers this as an option should you wish to pursue it.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Expand relator term abbreviations in X00 $e, X10 $e, and X11 $j fields.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.5RDA 5.52014-05-19T19:25:12Z<p>Judy: /* Relator terms */</p>
<hr />
<div>==RDA 5.5: Relator Terms==<br />
[[image:rda5-5.png]]<br />
===Relator terms===<br />
In AACR2, many relator terms were not included on headings. With RDA, the relator terms are retained and expanded if they are in their abbreviated form. MARS 2.0 will retain all relator terms in X00 $e, X10 $e, and X11 $j (unless otherwise directed). [http://access.rdatoolkit.org/document.php?id=rdachp18&target=rda18-274# RDA 18.5.1.3] (html) [http://www.loc.gov/marc/relators/ MARC relators] (html) <br />
<br />
The following relator term abbreviations will be expanded:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" style="border-collapse:collapse;"<br />
|-<br />
|- align="center" style="background: #C0C0C0"<br />
| Abbreviated || Expanded || Abbreviated || Expanded<br />
|- align="center" style="background: white"<br />
| arr. || arranger || joint tr. || translator<br />
|- align="center" style="background: white"<br />
| auth. || author || joint trans. || translator<br />
|- align="center" style="background: white"<br />
| comp. || compiler || jt. || <br />
|- align="center" style="background: white"<br />
| ed. || editor || jt. auth. || author<br />
|- align="center" style="background: white"<br />
| edit. || editor || jt. comp. || compiler<br />
|- align="center" style="background: white"<br />
| eds. || editor || jt. ed. || editor<br />
|- align="center" style="background: white"<br />
| edt. || editor || jt. ill. || illustrator<br />
|- align="center" style="background: white"<br />
| ill. || illustrator || jt. illus. || illustrator<br />
|- align="center" style="background: white"<br />
| illus. || illustrator || jt. tr. || translator<br />
|- align="center" style="background: white"<br />
| joint auth. || author || jt. trans. || translator<br />
|- align="center" style="background: white"<br />
| joint comp. || compiler || lbt || librettist<br />
|- align="center" style="background: white"<br />
| joint ed. || editor || pub || publisher<br />
|- align="center" style="background: white"<br />
| joint ill. || illustrator || publ || publisher<br />
|- align="center" style="background: white"<br />
| joint illus. || illustrator || tr. || translator<br />
|- align="center" style="background: white"<br />
| || || trans. || translator<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Open Metadata Registry===<br />
MARS 2.0 also utilizes an RDF-derived list of relator terms from the [http://metadataregistry.org/schemaprop/list/schema_id/4.html Open Metadata Registry] as well as the [http://www.loc.gov/marc/relators/relaterm.html Relator Term List]. At the time of this update, there are over 460 unique terms that MARS 2.0 utilizes to check your relator terms. If any relator terms do not appear on this list, they are flagged for one of our standard reports ([http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms R119]). In addition to this, Backstage also employs common typo lists to check and correct for errors (e.g., 'astor' corrected to 'actor').<br />
<br />
==Convert $e term to $4 code==<br />
MARS 2.0 processing can convert your $e relator terms to $4 relator codes, provided there is a match against our extensive list of available relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e actor</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e director</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e politician</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- </font><br />
Note that '''$e politician''' is not a currently acceptable $e relator term. MARS 2.0 processing will flag this unrecognized relator term and add it to a standard report (see [http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms Step 6.2, R119]).<br />
<br />
==Convert $4 code to $e term==<br />
MARS 2.0 processing can also convert $4 relator codes to $e relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 pro</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Actor</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Director</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Producer</font></font><br />
===Special Note===<br />
PCC guidelines do not currently recommend using a relator term in $e in conjunction with a relator code in $4, within the same field. Backstage offers this as an option should you wish to pursue it.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Expand relator term abbreviations in X00 $e, X10 $e, and X11 $j fields.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.2RDA 4.22013-10-07T18:22:34Z<p>Judy: /* 250 field */</p>
<hr />
<div>==RDA 4.2: 25X Fields (Edition)==<br />
[[image:rda4-2.png]]<br />
===250 field===<br />
This step will bring abbreviations commonly used in the Edition Statement (250) and the Cartographic Mathematical Data (255) fields in line with RDA practices a much as possible by machine manipulation. By using lists that can be updated and expanded as needed it’s possible to modify the changes to either of these fields to fit your needs.<br />
<br />
Abbreviations spelled out in 250 fields include numeric designations (1st to first, 3d to third, etc.), ed. to editor, rev. to revised, etc.<br />
<br />
This table lists some abbreviations that will be expanded in 250 $a (edition statement):<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
! |<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| 1st || First || || 6th || Sixth<br />
|-<br />
| 2nd || Second || || 7th || Seventh<br />
|-<br />
| 3rd || Third || || 8th || Eighth<br />
|-<br />
| 4th || Fourth || || 9th || Ninth<br />
|-<br />
| 5th || Fifth || || 10th || Tenth<br />
|-<br />
| ed. || edition || || rev. || revised<br />
|-<br />
|et. al. || and others<br />
|}<br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original field''':<br />
250 $a <font color="red">3rd rev. ed.</font><br />
<br />
'''updated field''':<br />
250 $a <font color="red">Third revised edition.</font><br />
</font><br />
<br />
'''Note''': RDA Enrichment also includes expanding abbreviations for other language versions of '''edition''', '''edited''', '''revised''', '''enlarged''', '''corrected''', '''new''', '''improved''', and '''updated'''. All told, the following languages have edition statement abbreviations expanded: '''Czech''', '''Danish''', '''Dutch''', '''English''', '''French''', '''German''', '''Hungarian''', '''Indonesian''', '''Italian''', '''Norwegian''', '''Polish''', '''Russian''', '''Slavic''', '''Spanish''', and '''Swedish'''.<br />
<br />
===255 field===<br />
Abbreviations to be spelled out in 255 fields include RA to Right ascension, Decl. to Declination, eq. to quinox, hour to hr., and ca. changed to approximately and brackets removed.<br />
<br />
<font size="3"><br />
'''original field''':<br />
255 $c <font color="red">Scale [ca. 1:90,000]</font>.<br />
<br />
'''updated field''':<br />
255 $c <font color="red">Scale approximately 1:90,000</font>.<br />
<br />
'''original field''':<br />
255 $c <font color="red">(RA 16 hr./Decl. -23° ; eq. 1950)</font>.<br />
<br />
'''updated field''':<br />
255 $c <font color="red">(Right ascension 16 hr./Declination -23° ; equinox 1950)</font>.</font><br />
<br />
Note: No changes will be made to 255 $b Statement of Projection as it is a transcribed field.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Expand all abbreviations in 25X fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.7RDA 4.72013-10-07T18:12:33Z<p>Judy: /* 500 and 504 fields */</p>
<hr />
<div>==RDA 4.7: Note Fields - 5XX==<br />
[[image:rda4-7.png]]<br />
<br />
===500 and 504 fields===<br />
<br />
<br />
This table shows the terms that MARS 2.0 will spell out in 500 and 504 field if these options are chosen:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| acc. arr. || accompaniment arranged<br />
|-<br />
| bib. || bibliographical<br />
|-<br />
| ca. || approximately<br />
|-<br />
| ed. || edition<br />
|-<br />
| et. al. || and others<br />
|-<br />
| incl. || includes<br />
|-<br />
| ind. || index<br />
|-<br />
| introd. || introduction<br />
|-<br />
| l. || leaves<br />
|-<br />
| p. || pages<br />
|-<br />
| t.p. || title page<br />
|} <br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original field''':<br />
500 $a "Also attributed to Jonathan Swift"--<font color="red">Introd.</font><br />
<br />
'''updated field''':<br />
500 $a "Also attributed to Jonathan Swift"--<font color="red">Introduction.</font><br />
</font><br />
<br />
<font size="3"><br />
'''original field''':<br />
504 $a Includes <font color="red">bib.</font> references (p. 299-302).<br />
<br />
'''updated field''':<br />
504 $a Includes <font color="red">bibliographical</font> references (p. 299-302).<br />
</font><br />
<br />
===502 field===<br />
<br />
RDA rules allow for the content of 502 fields to be broken up into separate subfields for specificity. If the existing 502 notes follow AACR2 formatting, MARS 2.0 can break up the information into multiple subfields.<br />
<br />
<font size="3"><br />
'''original field''':<br />
502 <font color="red">$a Thesis (M.A.)--University College, London, 1969</font>.<br />
<br />
'''updated field''':<br />
502 <font color="red">$a Thesis $b M.A. $c University College, London $d 1969</font>.<br />
</font><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Do not expand abbreviations in notes fields or convert 502 field.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.4RDA 5.42013-07-19T18:29:29Z<p>Judy: /* 240 $l > individual 700 fields */</p>
<hr />
<div>==RDA 5.4: Uniform Title Updates (X00, X10, X30, 240)==<br />
[[image:rda5-4.png]]<br />
===Music abbreviations===<br />
Certain abbreviations should no longer used in the arranged statement for music (240 $o, 6XX $o, 7XX $o): acc., arr., unacc.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| acc. || accompanied<br />
|-<br />
| arr. || arranged<br />
|-<br />
| unacc. || unaccompanied<br />
|} <br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arr</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unacc</font>.<br />
<br />
'''updated fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arranged</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unaccompanied</font>.</font><br />
<br />
===240 $l > individual 700 fields===<br />
When a 240 $l contains two languages, this can be separated into two 700 fields with individual $l subfields, and the 240 removed:<br />
<br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
100 0 $a Plato<br />
240 10 $a Works. $l <font color="red">English & Greek</font>. $f 1914<br />
<br />
'''updated fields''':<br />
700 0 $a Plato. $t Works. $l <font color="red">English</font>. $f 1914.<br />
700 0 $a Plato. $t Works. $l <font color="red">Greek</font>. $f 1914.<br />
<font size="2"><br />
Currently, not all Library of Congress authorities have been updated to reflect this type of change, so these new 700 fields may no longer match the LC authority file and you may see them on our Unmatched Headings Report. As these changes are made in LC, authorities for the unmatched headings will be delivered as part of ongoing processing.<br />
<br />
Also, please note that when a 240 contains $l Polyglot an automated system cannot determine what the multiple languages are without the item in hand. These will be reported so you can add your own 700's, at will.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Make all changes & expand abbreviations for uniform titles in 240, X00, X10, X11, X30 fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.1RDA 4.12013-06-24T18:20:50Z<p>Judy: /* Statement of responsibility */</p>
<hr />
<div>==RDA 4.1: 245 field (Title)==<br />
[[image:rda4-1.png]]<br />
===Bracketed title information===<br />
If the LDR position 06 is not equal to e or the 007 position 00 is not m then certain terms within the 245 $b which are enclosed in square brackets (e.g. announcement, novel, poems, proceedings, program, selections) will be deleted. If there is nothing remaining in the $b, the $b will be deleted:<br />
<font size="3"><br />
'''original field''':<br />
245 00 $a Seattle Film Festival <font color="red">:$b [program]</font>.<br />
<br />
'''updated field''':<br />
245 00 $a Seattle Film Festival.</font><br />
<br />
===Parallel titles===<br />
If there is an equal sign = preceeding the $b, then the text that follows the equal sign will be copied into a 246 field with indicators of 31. The new 246 will not be added if the exact same 246 field already exists:<br />
<font size="3"><br />
'''original field''':<br />
245 00 $a International meteorological vocabulary <font color="red">=$b Vocabulaire météorologique international = Mezhdunarodnyi meterologicheskii slovar' = Vocabulario meteorologico internacional</font>.<br />
<br />
'''updated fields''':<br />
245 00 $a International meteorological vocabulary =$b Vocabulaire météorologique international = Mezhdunarodnyi meterologicheskii slovar' = Vocabulario meteorologico internacional.<br />
<font color="red">246 31 $a Vocabulaire météorologique international<br />
246 31 $a Mezhdunarodnyi meterologicheskii slovar'<br />
246 31 $a Vocabulario meteorologico internacional</font></font><br />
<br />
===Statement of responsibility===<br />
Within the 245 $b, certain terms which come right before the $c will be moved into the $c IF the $c has "by" [creator]. This includes the following terms: a novel, dramatised adaptations, novel, research and text, and stories:<br />
<font size="3"><br />
'''original field''':<br />
245 10 $a Characters From Dickens <font color="red">:$b dramatised adaptations</font> /$c by Barry Campbell<br />
<br />
'''updated field''':<br />
245 10 $a Characters From Dickens <font color="red">/$c dramatised adaptations</font> by Barry Campbell</font><br />
<br />
===[et al.] changes to [and others]===<br />
Another major change from AACR2 to RDA is the lack of a “rule of three”. In RDA there is no limit to the number of names that can be put into the statement of responsibility. If the number of names is going to be limited you use [and others] or indicate how many others. Our process can change the former practice of using elipses and [et al.] to the current use of [and others].<br />
<br />
Within the statement of responsibility (245 $c), … [et. al.] will be changed to [and others]:<br />
<font size="3"><br />
'''original field''':<br />
245 10 $a Second growth /$c Sean Markey <font color="red">... [et al.]</font>.<br />
<br />
'''updated field''':<br />
245 10 $a Second growth /$c Sean Markey <font color="red">[and others]</font>.</font><br />
<br />
This change will be flagged on Report 152 Title Field Updates in case you would like to add additional contributors to the statement of responsibility.<br />
<br />
===Flagged records===<br />
There are a few changes to RDA that cannot be fully completed through an automated process. For some of these, the system will make a minor change as described below, and then flag the field on Report 155 Title Field Contains [sic] or [i.e.] Flag so the record so the cataloger can review the record and make the necessary changes and additions:<br />
*Spelling errors in the title field (245) should no longer be marked with '[sic]'. MARS 2.0 will remove [sic] and flag the record on a report so that a cataloger can add any necessary 246 fields<br />
*Other indicators of a mistake within the title may have been marked with '[i.e.]' in the 245 field. As with spelling errors, MARS 2.0 will remove the [i.e.] and flag the record on a report<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Make all title field updates in 245 fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.4RDA 5.42013-05-30T22:51:24Z<p>Judy: /* 240 $l > individual 700 fields */</p>
<hr />
<div>==RDA 5.4: Uniform Title Updates (X00, X10, X30, 240)==<br />
[[image:rda5-4.png]]<br />
===Music abbreviations===<br />
Certain abbreviations should no longer used in the arranged statement for music (240 $o, 6XX $o, 7XX $o): acc., arr., unacc.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| acc. || accompanied<br />
|-<br />
| arr. || arranged<br />
|-<br />
| unacc. || unaccompanied<br />
|} <br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arr</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unacc</font>.<br />
<br />
'''updated fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arranged</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unaccompanied</font>.</font><br />
<br />
===240 $l > individual 700 fields===<br />
When a 240 $l contains two languages, this can be separated into two 700 fields with individual $l subfields, and the 240 removed:<br />
<br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
100 0 $a Plato<br />
240 10 $a Works. $l <font color="red">English & Greek</font>. $f 1914<br />
<br />
'''updated fields''':<br />
700 0 $a Plato. $t Works. $l <font color="red">English</font>. $f 1914.<br />
700 0 $a Plato. $t Works. $l <font color="red">Greek</font>. $f 1914.<br />
<font size="2"><br />
Please note that when a 240 contains $l Polyglot an automated system cannot determine what the multiple languages are without the item in hand. These will be reported so you can add your own 700's, at will.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Make all changes & expand abbreviations for uniform titles in 240, X00, X10, X11, X30 fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.4RDA 5.42013-05-30T22:50:58Z<p>Judy: /* 240 $l */</p>
<hr />
<div>==RDA 5.4: Uniform Title Updates (X00, X10, X30, 240)==<br />
[[image:rda5-4.png]]<br />
===Music abbreviations===<br />
Certain abbreviations should no longer used in the arranged statement for music (240 $o, 6XX $o, 7XX $o): acc., arr., unacc.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| acc. || accompanied<br />
|-<br />
| arr. || arranged<br />
|-<br />
| unacc. || unaccompanied<br />
|} <br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arr</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unacc</font>.<br />
<br />
'''updated fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arranged</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unaccompanied</font>.</font><br />
<br />
===240 $l > individual 700 fields===<br />
When a 240 $l contains two languages, this can be separated into two 700 fields with individual $l subfields, and the 240 removed:<br />
<br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
100 0 $a Plato<br />
240 10 $a Works. $l <font color="red">English & Greek</font>. $f 1914<br />
<br />
'''updated fields''':<br />
700 0 $a Plato. $t Works. $l <font color="red">English</font>. $f 1914.<br />
700 0 $a Plato. $t Works. $l <font color="red">Greek</font>. $f 1914.<br />
<br />
<font size="2"><br />
Please note that when a 240 contains $l Polyglot an automated system cannot determine what the multiple languages are without the item in hand. These will be reported so you can add your own 700's, at will.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Make all changes & expand abbreviations for uniform titles in 240, X00, X10, X11, X30 fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.4RDA 5.42013-05-30T22:49:59Z<p>Judy: /* 240 $l */</p>
<hr />
<div>==RDA 5.4: Uniform Title Updates (X00, X10, X30, 240)==<br />
[[image:rda5-4.png]]<br />
===Music abbreviations===<br />
Certain abbreviations should no longer used in the arranged statement for music (240 $o, 6XX $o, 7XX $o): acc., arr., unacc.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| acc. || accompanied<br />
|-<br />
| arr. || arranged<br />
|-<br />
| unacc. || unaccompanied<br />
|} <br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arr</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unacc</font>.<br />
<br />
'''updated fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arranged</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unaccompanied</font>.</font><br />
<br />
===240 $l===<br />
When a 240 $l contains two languages, this can be separated into two 700 fields with individual $l subfields, and the 240 removed:<br />
<br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
100 0 $a Plato<br />
240 10 $a Works. $l <font color="red">English & Greek</font>. $f 1914<br />
<br />
'''updated fields''':<br />
700 0 $a Plato. $t Works. $l <font color="red">English</font>. $f 1914.<br />
700 0 $a Plato. $t Works. $l <font color="red">Greek</font>. $f 1914.<br />
<br />
Please note that when a 240 contains $l Polyglot an automated system cannot determine what the multiple languages are without the item in hand. These will be reported so you can add your own 700's, at will.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Make all changes & expand abbreviations for uniform titles in 240, X00, X10, X11, X30 fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.4RDA 5.42013-05-30T22:47:15Z<p>Judy: /* Music abbreviations */</p>
<hr />
<div>==RDA 5.4: Uniform Title Updates (X00, X10, X30, 240)==<br />
[[image:rda5-4.png]]<br />
===Music abbreviations===<br />
Certain abbreviations should no longer used in the arranged statement for music (240 $o, 6XX $o, 7XX $o): acc., arr., unacc.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| acc. || accompanied<br />
|-<br />
| arr. || arranged<br />
|-<br />
| unacc. || unaccompanied<br />
|} <br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arr</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unacc</font>.<br />
<br />
'''updated fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arranged</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unaccompanied</font>.</font><br />
<br />
===240 $l===<br />
When a 240 $l contains two languages, this can be separated into two 700 fields with individual $l subfields, and the 240 removed:<br />
<br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
100 0 $a Plato<br />
240 10 $a Works. $l <font color="red">English & Greek</font>. $f 1914<br />
<br />
'''updated fields''':<br />
700 0 $a Plato. $t Works. $l <font color="red">English</font>. $f 1914.<br />
700 0 $a Plato. $t Works. $l <font color="red">Greek</font>. $f 1914.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Make all changes & expand abbreviations for uniform titles in 240, X00, X10, X11, X30 fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.4RDA 5.42013-05-30T22:33:03Z<p>Judy: /* RDA 5.4: Music */</p>
<hr />
<div>==RDA 5.4: Uniform Title Updates (X00, X10, X30, 240)==<br />
[[image:rda5-4.png]]<br />
===Music abbreviations===<br />
Certain abbreviations should no longer used in the arranged statement for music (240 $o, 6XX $o, 7XX $o): acc., arr., unacc.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| acc. || accompanied<br />
|-<br />
| arr. || arranged<br />
|-<br />
| unacc. || unaccompanied<br />
|} <br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arr</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unacc</font>.<br />
<br />
'''updated fields''':<br />
240 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">arranged</font>.<br />
630 00 $a Wedding of Gloriana. $k Selections; $o <font color="red">unaccompanied</font>.</font><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Make all changes & expand abbreviations for uniform titles in 240, X00, X10, X11, X30 fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.5RDA 5.52013-05-28T18:48:06Z<p>Judy: /* Relator terms */</p>
<hr />
<div>==RDA 5.5: Relator Terms==<br />
[[image:rda5-5.png]]<br />
===Relator terms===<br />
In AACR2, many relator terms were not included on headings. With RDA, the relator terms are retained and expanded if they are in their abbreviated form. MARS 2.0 will retain all relator terms in X00 $e, X10 $e, and X11 $j (unless otherwise directed).<br />
<br />
The following relator term abbreviations will be expanded:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" style="border-collapse:collapse;"<br />
|-<br />
|- align="center" style="background: #C0C0C0"<br />
| Abbreviated || Expanded || Abbreviated || Expanded<br />
|- align="center" style="background: white"<br />
| arr. || arranger || joint tr. || joint translator<br />
|- align="center" style="background: white"<br />
| auth. || author || joint trans. || joint translator<br />
|- align="center" style="background: white"<br />
| comp. || compiler || jt. || joint<br />
|- align="center" style="background: white"<br />
| ed. || editor || jt. auth. || joint author<br />
|- align="center" style="background: white"<br />
| edit. || editor || jt. comp. || joint compiler<br />
|- align="center" style="background: white"<br />
| eds. || editor || jt. ed. || joint editor<br />
|- align="center" style="background: white"<br />
| edt. || editor || jt. ill. || joint illustrator<br />
|- align="center" style="background: white"<br />
| ill. || illustrator || jt. illus. || joint illustrator<br />
|- align="center" style="background: white"<br />
| illus. || illustrator || jt. tr. || joint translator<br />
|- align="center" style="background: white"<br />
| joint auth. || joint author || jt. trans. || joint translator<br />
|- align="center" style="background: white"<br />
| joint comp. || joint compiler || lbt || librettist<br />
|- align="center" style="background: white"<br />
| joint ed. || joint editor || pub || publisher<br />
|- align="center" style="background: white"<br />
| joint ill. || joint illustrator || publ || publisher<br />
|- align="center" style="background: white"<br />
| joint illus. || joint illustrator || tr. || translator<br />
|- align="center" style="background: white"<br />
| || || trans. || translator<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Open Metadata Registry===<br />
MARS 2.0 also utilizes an RDF-derived list of relator terms from the [http://metadataregistry.org/schemaprop/list/schema_id/4.html Open Metadata Registry] as well as the [http://www.loc.gov/marc/relators/relaterm.html Relator Term List]. At the time of this update, there are over 460 unique terms that MARS 2.0 utilizes to check your relator terms. If any do not appear on this list, they are flagged for one of our reports ([http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms R119]). In addition to this, Backstage also employs common typo lists to check and correct for errors (e.g., 'astor' corrected to 'actor').<br />
<br />
==Convert $e term to $4 code==<br />
MARS 2.0 processing can convert your $e relator terms to $4 relator codes, provided there is a match against our extensive list of available relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e actor</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e director</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e politician</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- $e <font color="blue">A</font>ctor <font color="blue">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- $e <font color="blue">D</font>irector <font color="blue">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e politican</font></font><br />
Note that '''$e politican''' is not a currently acceptable $e relator term. MARS 2.0 processing will flag this unrecognized relator term and add it to a standard report (see [http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms Step 6.2, R119]).<br />
<br />
==Convert $4 code to $e term==<br />
MARS 2.0 processing can also convert $4 relator codes to $e relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 pro</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Actor</font> $4 act<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Director</font> $4 drt<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Producer</font> $4 pro</font><br />
===Special Note===<br />
PCC guidelines do not currently recommend using a relator term in $e in conjunction with a relator code in $4, within the same field. Backstage offers this as an option should you wish to pursue it.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Expand relator term abbreviations in X00 $e, X10 $e, and X11 $j fields.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.5RDA 5.52013-05-28T18:38:06Z<p>Judy: /* Relator terms */</p>
<hr />
<div>==RDA 5.5: Relator Terms==<br />
[[image:rda5-5.png]]<br />
===Relator terms===<br />
In AACR2, many relator terms were not included on headings. With RDA, the relator terms are retained and expanded if they are in their abbreviated form. MARS 2.0 will retain all relator terms in X00 $e, X10 $e, and X11 $j (unless otherwise directed).<br />
<br />
The following relator term abbreviations will be expanded:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" style="border-collapse:collapse;"<br />
|-<br />
|- align="center" style="background: #C0C0C0"<br />
| Abbreviated || Expanded<br />
|- align="center" style="background: white"<br />
| arr. || arranger<br />
|- align="center" style="background: white"<br />
| auth. || author<br />
|- align="center" style="background: white"<br />
| comp. || compiler<br />
|- align="center" style="background: white"<br />
| ed. || editor<br />
|- align="center" style="background: white"<br />
| edit. || editor<br />
|- align="center" style="background: white"<br />
| eds. || editor<br />
|- align="center" style="background: white"<br />
| edt. || editor<br />
|- align="center" style="background: white"<br />
| ill. || illustrator<br />
|- align="center" style="background: white"<br />
| illus. || illustrator<br />
|- align="center" style="background: white"<br />
<br />
|- align="center" style="background: white"<br />
| joint auth. || joint author<br />
|- align="center" style="background: white"<br />
| joint comp. || joint compiler<br />
|- align="center" style="background: white"<br />
| joint ed. || joint editor<br />
|- align="center" style="background: white"<br />
| joint ill. || joint illustrator<br />
|- align="center" style="background: white"<br />
| joint illus. || joint illustrator<br />
|- align="center" style="background: white"<br />
| joint tr. || joint translator<br />
|- align="center" style="background: white"<br />
| joint trans. || joint translator<br />
| jt. || joint<br />
|- align="center" style="background: white"<br />
| jt. auth. || joint author<br />
|- align="center" style="background: white"<br />
| jt. comp. || joint compiler<br />
|- align="center" style="background: white"<br />
| jt. ed. || joint editor<br />
|- align="center" style="background: white"<br />
| jt. ill. || joint illustrator<br />
|- align="center" style="background: white"<br />
| jt. illus. || joint illustrator<br />
|- align="center" style="background: white"<br />
| jt. tr. || joint translator<br />
|- align="center" style="background: white"<br />
| jt. trans. || joint translator<br />
|- align="center" style="background: white"<br />
| lbt || librettist<br />
|- align="center" style="background: white"<br />
| pub || publisher<br />
|- align="center" style="background: white"<br />
| publ || publisher<br />
|- align="center" style="background: white"<br />
| tr. || translator<br />
|- align="center" style="background: white"<br />
| trans. || translator<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Open Metadata Registry===<br />
MARS 2.0 also utilizes an RDF-derived list of relator terms from the [http://metadataregistry.org/schemaprop/list/schema_id/4.html Open Metadata Registry] as well as the [http://www.loc.gov/marc/relators/relaterm.html Relator Term List]. At the time of this update, there are over 460 unique terms that MARS 2.0 utilizes to check your relator terms. If any do not appear on this list, they are flagged for one of our reports ([http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms R119]). In addition to this, Backstage also employs common typo lists to check and correct for errors (e.g., 'astor' corrected to 'actor').<br />
<br />
==Convert $e term to $4 code==<br />
MARS 2.0 processing can convert your $e relator terms to $4 relator codes, provided there is a match against our extensive list of available relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e actor</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e director</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e politician</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- $e <font color="blue">A</font>ctor <font color="blue">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- $e <font color="blue">D</font>irector <font color="blue">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e politican</font></font><br />
Note that '''$e politican''' is not a currently acceptable $e relator term. MARS 2.0 processing will flag this unrecognized relator term and add it to a standard report (see [http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms Step 6.2, R119]).<br />
<br />
==Convert $4 code to $e term==<br />
MARS 2.0 processing can also convert $4 relator codes to $e relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 pro</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Actor</font> $4 act<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Director</font> $4 drt<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Producer</font> $4 pro</font><br />
===Special Note===<br />
PCC guidelines do not currently recommend using a relator term in $e in conjunction with a relator code in $4, within the same field. Backstage offers this as an option should you wish to pursue it.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Expand relator term abbreviations in X00 $e, X10 $e, and X11 $j fields.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.5RDA 5.52013-05-25T19:33:20Z<p>Judy: /* Relator terms */</p>
<hr />
<div>==RDA 5.5: Relator Terms==<br />
[[image:rda5-5.png]]<br />
===Relator terms===<br />
In AACR2, many relator terms were not included on headings. With RDA, the relator terms are retained and expanded if they are in their abbreviated form. MARS 2.0 will retain all relator terms in X00 $e, X10 $e, and X11 $j (unless otherwise directed).<br />
<br />
The following relator term abbreviations will be expanded:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" style="border-collapse:collapse;"<br />
|-<br />
|- align="center" style="background: #C0C0C0"<br />
| Abbreviated || Expanded<br />
|- align="center" style="background: white"<br />
| arr. || arranger<br />
|- align="center" style="background: white"<br />
| auth. || author<br />
|- align="center" style="background: white"<br />
| comp. || compiler<br />
|- align="center" style="background: white"<br />
| ed. || editor<br />
|- align="center" style="background: white"<br />
| ill. || illustrator<br />
|- align="center" style="background: white"<br />
| illus. || illustrator<br />
|- align="center" style="background: white"<br />
| jt. || joint<br />
|- align="center" style="background: white"<br />
| jt. auth. || joint author<br />
|- align="center" style="background: white"<br />
| jt. comp. || joint compiler<br />
|- align="center" style="background: white"<br />
| jt. ed. || joint editor<br />
|- align="center" style="background: white"<br />
| jt. ill. || joint illustrator<br />
|- align="center" style="background: white"<br />
| jt. illus. || joint illustrator<br />
|- align="center" style="background: white"<br />
| joint illus. || joint illustrator<br />
|- align="center" style="background: white"<br />
| tr. || translator<br />
|- align="center" style="background: white"<br />
| trans. || translator<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Open Metadata Registry===<br />
MARS 2.0 also utilizes an RDF-derived list of relator terms from the [http://metadataregistry.org/schemaprop/list/schema_id/4.html Open Metadata Registry] as well as the [http://www.loc.gov/marc/relators/relaterm.html Relator Term List]. At the time of this update, there are over 460 unique terms that MARS 2.0 utilizes to check your relator terms. If any do not appear on this list, they are flagged for one of our reports ([http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms R119]). In addition to this, Backstage also employs common typo lists to check and correct for errors (e.g., 'astor' corrected to 'actor').<br />
<br />
==Convert $e term to $4 code==<br />
MARS 2.0 processing can convert your $e relator terms to $4 relator codes, provided there is a match against our extensive list of available relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e actor</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e director</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e politician</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- $e <font color="blue">A</font>ctor <font color="blue">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- $e <font color="blue">D</font>irector <font color="blue">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e politican</font></font><br />
Note that '''$e politican''' is not a currently acceptable $e relator term. MARS 2.0 processing will flag this unrecognized relator term and add it to a standard report (see [http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms Step 6.2, R119]).<br />
<br />
==Convert $4 code to $e term==<br />
MARS 2.0 processing can also convert $4 relator codes to $e relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 pro</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Actor</font> $4 act<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Director</font> $4 drt<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Producer</font> $4 pro</font><br />
===Special Note===<br />
PCC guidelines do not currently recommend using a relator term in $e in conjunction with a relator code in $4, within the same field. Backstage offers this as an option should you wish to pursue it.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Expand relator term abbreviations in X00 $e, X10 $e, and X11 $j fields.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.5RDA 4.52013-05-20T19:07:28Z<p>Judy: /* Dimensions */</p>
<hr />
<div>==RDA 4.5: 300 field (Physical Description)==<br />
[[image:rda4-5.png]]<br />
===Extent===<br />
This table lists extent abbreviations that will be expanded in the 300 $a:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| approx. || approximately || lvs. || leaves<br />
|-<br />
| ca. || approximately || numb. || numbered<br />
|-<br />
| cov. || cover || obl. || oblong<br />
|-<br />
| dia. || diameter || p. || page (singular)<br />
|-<br />
| diagr. || diagram || p. || pages (plural)<br />
|-<br />
| diagrs. || diagrams || p.l. || preliminary leaves<br />
|-<br />
| fig. || figures || pent. || pentagram<br />
|-<br />
| fold. || folded || pp. || pages<br />
|-<br />
| front. || frontispiece || unnum. || unnumbered<br />
|-<br />
| frontis. || frontispiece || unp. || unpaged<br />
|-<br />
| fronts. || frontispiece || v. || volume (singular)<br />
|-<br />
| ill. || illustrations || v. || volumes (plural)<br />
|-<br />
| illus. || illustrations || vol. || volume (singular)<br />
|-<br />
| irr. || irregular || vol. || volumes (plural)<br />
|-<br />
| l. || leaf (singular) || vols. || volumes<br />
|-<br />
| l. || leaves (plural)<br />
|}<br />
<div style=clear:both></div><br />
<br />
Some additional changes that are made to the 300 $a include the following:<br />
*A number followed by brackets with i.e. will be changed to ''''that is'''':<br />
**'''48 [i.e. 52] p.''' becomes '''48, that is 52, pages'''.<br />
<br />
*Brackets around a number will be changed to ''''unnumbered'''':<br />
**'''[16] p.''' becomes '''16 unnumbered pages'''.<br />
<br />
===Other physical details===<br />
Abbreviations within the 300 $b (other physical details) that will be expanded include the following:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| b&w || black & white || ill. || illustrations<br />
|-<br />
| col. || color || illus. || illustrations<br />
|-<br />
| diagr. || diagram || incl. || including<br />
|-<br />
| diagrs. || diagrams || l. || leaves<br />
|-<br />
| fac. || facsimiles || phot. || photographs<br />
|-<br />
| facs. || facsimiles || photo. || photographs<br />
|-<br />
| facsim. || facsimiles || port. || portrait<br />
|-<br />
| facsims. || facsimiles || ports. || portraits<br />
|-<br />
| fig. || figures || sam. || samples<br />
|-<br />
| fold. || folded || samp. || samples<br />
|-<br />
| front. || frontispiece || sd. || sound<br />
|-<br />
| gen. || genealogical || si. || silent<br />
|-<br />
| geneal. || genealogical || snd. || sound<br />
|-<br />
| || || tab. || tables<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Dimensions===<br />
Many abbreviations are still allowed in the dimensions subfield (300 $c). For instance, ''''cm.'''' and ''''in.'''' are still authorized to represent centimeters and inches. However (for continuity), the following table lists the abbreviations that will change in the 300 $c:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| ca. || approximately || inches || in.<br />
|-<br />
| cov. || cover || irr. || irregular<br />
|-<br />
| dia. || diameter || lvs. || leaves<br />
|-<br />
| feet || ft. || numb. || numbered<br />
|-<br />
| fol. || folio || obl. || oblong<br />
|-<br />
| fold. || folded || p. || pages<br />
|-<br />
| foot || ft. || pent. || pentagram<br />
|-<br />
| inch || in. || pp. || pages<br />
|-<br />
| || || unnum. || unnumbered<br />
|}<br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
300 $a 300 <font color="red">p.</font> : $b <font color="red">ill.</font> ; $c 4to.<br />
300 $a [<font color="red">unp.</font>] : $b <font color="red">ill.</font> (some <font color="red">col.</font>) ; $c 6 in.<br />
300 $a 3 <font color="red">v.</font> : $b <font color="red">facsims.</font>, <font color="red">ports.</font> ; $c 24 x 36 cm.<br />
300 $a 3 <font color="red">p.l.</font>, <font color="red">ca.</font> 245 <font color="red">pp.</font> : $b <font color="red">geneal.</font> tables ; $c <font color="red">fol.</font><br />
300 $a 92 <font color="red">[i.e. 96] pp.</font> : $b <font color="red">sd., col.</font> ; $c 24mo.<br />
300 $a <font color="red">[16] p.</font> of plates : $b <font color="red">col. illus.</font> ; $c 12mo.<br />
<br />
'''updated fields''':<br />
300 $a 300 <font color="red">pages</font> : $b <font color="red">illustrations</font> ; $c 4to.<br />
300 $a [<font color="red">unpaged</font>] : $b <font color="red">illustrations</font> (some <font color="red">color</font>) ; $c 6 in.<br />
300 $a 3 <font color="red">volumes</font> : $b <font color="red">facsimiles</font>, <font color="red">portraits</font> ; $c 24 x 36 cm.<br />
300 $a 3 <font color="red">preliminary leaves</font>, <font color="red">approximately</font> 245 <font color="red">pages</font> : $b <font color="red">genealogical</font> tables ; $c <font color="red">folio.</font><br />
300 $a 92<font color="red">, that is 96, pages</font> : $b <font color="red">sound, color</font> ; $c 24mo.<br />
300 $a <font color="red">16 unnumbered pages</font> of plates : $b <font color="red">color illustrations</font> ; $c 12mo.</font><br />
<br />
==SMD Update Table==<br />
MARS 2.0 can update the following AACR2 terms to their RDA equivalent:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | AACR2 Term<br />
! style="background:silver" | RDA Term<br />
|-<br />
| quad. || Quadraphonic<br />
|-<br />
| transparency || overhead transparency<br />
|-<br />
| computer disk || computer disc<br />
|-<br />
| computer optical disc || computer disc<br />
|-<br />
<br />
|}<br />
<div style=clear:both></div><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Make all physical description updates in 300 field.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.5RDA 4.52013-05-20T18:59:50Z<p>Judy: /* Other physical details */</p>
<hr />
<div>==RDA 4.5: 300 field (Physical Description)==<br />
[[image:rda4-5.png]]<br />
===Extent===<br />
This table lists extent abbreviations that will be expanded in the 300 $a:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| approx. || approximately || lvs. || leaves<br />
|-<br />
| ca. || approximately || numb. || numbered<br />
|-<br />
| cov. || cover || obl. || oblong<br />
|-<br />
| dia. || diameter || p. || page (singular)<br />
|-<br />
| diagr. || diagram || p. || pages (plural)<br />
|-<br />
| diagrs. || diagrams || p.l. || preliminary leaves<br />
|-<br />
| fig. || figures || pent. || pentagram<br />
|-<br />
| fold. || folded || pp. || pages<br />
|-<br />
| front. || frontispiece || unnum. || unnumbered<br />
|-<br />
| frontis. || frontispiece || unp. || unpaged<br />
|-<br />
| fronts. || frontispiece || v. || volume (singular)<br />
|-<br />
| ill. || illustrations || v. || volumes (plural)<br />
|-<br />
| illus. || illustrations || vol. || volume (singular)<br />
|-<br />
| irr. || irregular || vol. || volumes (plural)<br />
|-<br />
| l. || leaf (singular) || vols. || volumes<br />
|-<br />
| l. || leaves (plural)<br />
|}<br />
<div style=clear:both></div><br />
<br />
Some additional changes that are made to the 300 $a include the following:<br />
*A number followed by brackets with i.e. will be changed to ''''that is'''':<br />
**'''48 [i.e. 52] p.''' becomes '''48, that is 52, pages'''.<br />
<br />
*Brackets around a number will be changed to ''''unnumbered'''':<br />
**'''[16] p.''' becomes '''16 unnumbered pages'''.<br />
<br />
===Other physical details===<br />
Abbreviations within the 300 $b (other physical details) that will be expanded include the following:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| b&w || black & white || ill. || illustrations<br />
|-<br />
| col. || color || illus. || illustrations<br />
|-<br />
| diagr. || diagram || incl. || including<br />
|-<br />
| diagrs. || diagrams || l. || leaves<br />
|-<br />
| fac. || facsimiles || phot. || photographs<br />
|-<br />
| facs. || facsimiles || photo. || photographs<br />
|-<br />
| facsim. || facsimiles || port. || portrait<br />
|-<br />
| facsims. || facsimiles || ports. || portraits<br />
|-<br />
| fig. || figures || sam. || samples<br />
|-<br />
| fold. || folded || samp. || samples<br />
|-<br />
| front. || frontispiece || sd. || sound<br />
|-<br />
| gen. || genealogical || si. || silent<br />
|-<br />
| geneal. || genealogical || snd. || sound<br />
|-<br />
| || || tab. || tables<br />
|}<br />
<div style=clear:both></div><br />
<br />
===Dimensions===<br />
Many abbreviations are still allowed in the dimensions subfield (300 $c). For instance, ''''cm.'''' and ''''in.'''' are still authorized to represent centimeters and inches. However (for continuity), the following table lists the abbreviations that will change in the 300 $c:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| ca. || approximately || numb. || numbered<br />
|-<br />
| cov. || cover || obl. || oblong<br />
|-<br />
| dia. || diameter || p. || page (singular)<br />
|-<br />
| fol. || folio || p. || pages (plural)<br />
|-<br />
| fold. || folded || pent. || pentagram<br />
|-<br />
| irr. || irregular || pp. || pages<br />
|-<br />
| lvs. || leaves || unnum. || unnumbered<br />
|-<br />
<br />
|}<br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original fields''':<br />
300 $a 300 <font color="red">p.</font> : $b <font color="red">ill.</font> ; $c 4to.<br />
300 $a [<font color="red">unp.</font>] : $b <font color="red">ill.</font> (some <font color="red">col.</font>) ; $c 6 in.<br />
300 $a 3 <font color="red">v.</font> : $b <font color="red">facsims.</font>, <font color="red">ports.</font> ; $c 24 x 36 cm.<br />
300 $a 3 <font color="red">p.l.</font>, <font color="red">ca.</font> 245 <font color="red">pp.</font> : $b <font color="red">geneal.</font> tables ; $c <font color="red">fol.</font><br />
300 $a 92 <font color="red">[i.e. 96] pp.</font> : $b <font color="red">sd., col.</font> ; $c 24mo.<br />
300 $a <font color="red">[16] p.</font> of plates : $b <font color="red">col. illus.</font> ; $c 12mo.<br />
<br />
'''updated fields''':<br />
300 $a 300 <font color="red">pages</font> : $b <font color="red">illustrations</font> ; $c 4to.<br />
300 $a [<font color="red">unpaged</font>] : $b <font color="red">illustrations</font> (some <font color="red">color</font>) ; $c 6 in.<br />
300 $a 3 <font color="red">volumes</font> : $b <font color="red">facsimiles</font>, <font color="red">portraits</font> ; $c 24 x 36 cm.<br />
300 $a 3 <font color="red">preliminary leaves</font>, <font color="red">approximately</font> 245 <font color="red">pages</font> : $b <font color="red">genealogical</font> tables ; $c <font color="red">folio.</font><br />
300 $a 92<font color="red">, that is 96, pages</font> : $b <font color="red">sound, color</font> ; $c 24mo.<br />
300 $a <font color="red">16 unnumbered pages</font> of plates : $b <font color="red">color illustrations</font> ; $c 12mo.</font><br />
==SMD Update Table==<br />
MARS 2.0 can update the following AACR2 terms to their RDA equivalent:<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | AACR2 Term<br />
! style="background:silver" | RDA Term<br />
|-<br />
| quad. || Quadraphonic<br />
|-<br />
| transparency || overhead transparency<br />
|-<br />
| computer disk || computer disc<br />
|-<br />
| computer optical disc || computer disc<br />
|-<br />
<br />
|}<br />
<div style=clear:both></div><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Make all physical description updates in 300 field.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.7RDA 4.72013-05-20T18:40:14Z<p>Judy: /* 500 and 504 fields */</p>
<hr />
<div>==RDA 4.7: Note Fields - 5XX==<br />
[[image:rda4-7.png]]<br />
<br />
===500 and 504 fields===<br />
<br />
<br />
This table shows the terms that MARS 2.0 will spell out in 500 and 504 field if these options are chosen:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
! style="background:silver" | Abbreviated<br />
! style="background:silver" | Expanded<br />
|-<br />
| acc. arr. || accompaniment arranged<br />
|-<br />
| bib. || bibliographical<br />
|-<br />
| ca. || approximately<br />
|-<br />
| ed. || edition<br />
|-<br />
| incl. || includes<br />
|-<br />
| ind. || index<br />
|-<br />
| introd. || introduction<br />
|-<br />
| l. || leaves<br />
|-<br />
| p. || pages<br />
|-<br />
| t.p. || title page<br />
|} <br />
<div style=clear:both></div><br />
<br />
<font size="3"><br />
'''original field''':<br />
500 $a "Also attributed to Jonathan Swift"--<font color="red">Introd.</font><br />
<br />
'''updated field''':<br />
500 $a "Also attributed to Jonathan Swift"--<font color="red">Introduction.</font><br />
</font><br />
<br />
<font size="3"><br />
'''original field''':<br />
504 $a Includes <font color="red">bib.</font> references (p. 299-302).<br />
<br />
'''updated field''':<br />
504 $a Includes <font color="red">bibliographical</font> references (p. 299-302).<br />
</font><br />
<br />
===502 field===<br />
<br />
RDA rules allow for the content of 502 fields to be broken up into separate subfields for specificity. If the existing 502 notes follow AACR2 formatting, MARS 2.0 can break up the information into multiple subfields.<br />
<br />
<font size="3"><br />
'''original field''':<br />
502 <font color="red">$a Thesis (M.A.)--University College, London, 1969</font>.<br />
<br />
'''updated field''':<br />
502 <font color="red">$a Thesis $b M.A. $c University College, London $d 1969</font>.<br />
</font><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Do not expand abbreviations in notes fields or convert 502 field.<br />
|}<br />
<div style=clear:both></div><br><br />
==links==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_3.0RDA 3.02013-05-15T23:34:06Z<p>Judy: /* 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, Media, and Carrier (CMC) 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 600 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 />
'''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/26<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 || h || sounds || audio || audio cartridge<br />
|-<br />
| i || s || e || h || sounds || audio || audio cylinder<br />
|-<br />
| i || s || d || h || sounds || audio || audio disc<br />
|-<br />
| i || s || i || h || sounds || audio || sound track reel<br />
|-<br />
| i || s || q || h || sounds || audio || audio roll<br />
|-<br />
| i || s || s || h || sounds || audio || audiocassette<br />
|-<br />
| i || s || t || h || sounds || audio || audiotape reel<br />
|-<br />
| i || s || z || h || 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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_5.5RDA 5.52013-05-13T22:58:43Z<p>Judy: /* Relator terms */</p>
<hr />
<div>==RDA 5.5: Relator Terms==<br />
[[image:rda5-5.png]]<br />
===Relator terms===<br />
In AACR2, many relator terms were not included on headings. With RDA, the relator terms are retained and expanded if they are in their abbreviated form. MARS 2.0 will retain all relator terms in X00 $e, X10 $e, and X11 $j (unless otherwise directed).<br />
<br />
The following relator term abbreviations will be expanded:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" style="border-collapse:collapse;"<br />
|-<br />
|- align="center" style="background: #C0C0C0"<br />
| Abbreviated || Expanded<br />
|- align="center" style="background: white"<br />
| arr. || arranger<br />
|- align="center" style="background: white"<br />
| comp. || compiler<br />
|- align="center" style="background: white"<br />
| ed. || editor<br />
|- align="center" style="background: white"<br />
| ill. || illustrator<br />
|- align="center" style="background: white"<br />
| illus. || illustrator<br />
|- align="center" style="background: white"<br />
| comp. || compiler<br />
|- align="center" style="background: white"<br />
| arr. || arranger<br />
|- align="center" style="background: white"<br />
| tr. || translator<br />
|- align="center" style="background: white"<br />
| auth. || author<br />
|- align="center" style="background: white"<br />
| jt. || joint<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===Open Metadata Registry===<br />
MARS 2.0 also utilizes an RDF-derived list of relator terms from the [http://metadataregistry.org/schemaprop/list/schema_id/4.html Open Metadata Registry] as well as the [http://www.loc.gov/marc/relators/relaterm.html Relator Term List]. At the time of this update, there are over 460 unique terms that MARS 2.0 utilizes to check your relator terms. If any do not appear on this list, they are flagged for one of our reports ([http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms R119]). In addition to this, Backstage also employs common typo lists to check and correct for errors (e.g., 'astor' corrected to 'actor').<br />
<br />
==Convert $e term to $4 code==<br />
MARS 2.0 processing can convert your $e relator terms to $4 relator codes, provided there is a match against our extensive list of available relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e actor</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e director</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e politician</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- $e <font color="blue">A</font>ctor <font color="blue">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- $e <font color="blue">D</font>irector <font color="blue">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$e politican</font></font><br />
Note that '''$e politican''' is not a currently acceptable $e relator term. MARS 2.0 processing will flag this unrecognized relator term and add it to a standard report (see [http://ac.bslw.com/community/wiki/index.php5/RDA_6.2#R119_-_Unrecognized_Relator_Terms Step 6.2, R119]).<br />
<br />
==Convert $4 code to $e term==<br />
MARS 2.0 processing can also convert $4 relator codes to $e relator terms:<br />
<font size="3"><br />
'''original headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 act</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 drt</font><br />
100 $a Eastwood, Clint, $d 1930- <font color="red">$4 pro</font><br />
<br />
'''updated headings''':<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Actor</font> $4 act<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Director</font> $4 drt<br />
100 $a Eastwood, Clint, $d 1930- <font color="blue">$e Producer</font> $4 pro</font><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Expand relator term abbreviations in X00 $e, X10 $e, and X11 $j fields.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]] - [[RDA_5.5|5.5]] - [[RDA_5.6|5.6]] - [[RDA_5.7|5.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.6RDA 4.62013-04-03T00:04:17Z<p>Judy: /* Special Note for the 38X fields */</p>
<hr />
<div>==STEP 4.6 : OTHER ABBREVIATIONS==<br />
[[image:rda4-6.png]]<br />
===046 field===<br />
046 fields are useful when your dates cannot be correctly coded in X00 $d due to B.C. dates or incorrect dates being used [http://www.loc.gov/marc/bibliographic/bd046.html (1)]. This may be another means to make that date available or understandable:<br />
<font size="3"><br />
'''original field''':<br />
100 $a Smith, John, $d 1950-1952<br />
<br />
'''created field''':<br />
<font color="red">046 $a m $c 1950 $e 1952</font><br />
</font><br />
Here we have an example where the birth & death date of the person in question doesn't appear to be correct, so we can create an 046 field from the 100 $d in this instance. The '''m''' designates that we are working with '''multiple dates''' and the '''c''' and '''e''' subfields let us know that these dates are part of the '''Common Era'''.<br />
<br />
==Special Note for the 38X fields==<br />
Currently Backstage only adds the 382, 383, and 384 fields derived from the 240 field. If you need 38X's added from the 7XX fields please see your project manager, as there are complications that will need to be addressed.<br />
<br />
===382 field===<br />
38X fields can be added to your records to correspond with music headings in a way to help break up the original music heading into a more machine-actionable set of fields [http://www.loc.gov/marc/bibliographic/bd382.html (2)]. In particular, 382 fields ('''Medium of Performance''') chunk the music heading's medium into its own field:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Telemann, Georg Philipp, $d 1681-1767.<br />
240 $a Suites, <font color="red">$m string orchestra</font>, $r D major.<br />
<br />
'''added field''':<br />
<font color="red">382 $a string orchestra</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 382 '''$a''' to denote the Medium of Performance.<br />
<br />
MARS 2.0 processing will not attempt to add a 382 field if any of the following is present:<br />
*382 field already exists in record<br />
*240 field has $k, $o, $p, "brasses", "plucked instrument", or "keyboard instruments"<br />
*240 $m contains "strings", "woodwinds", "winds" '''and''' 240 $t does '''not''' contain "trio", "quartet", or "quintet"<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Hoffmeister, Franz Anton, $d 1754-1812. $t Quintets, <font color="red">$m violins, violas, cello</font>, $r A major<br />
100 $a Bonazzi, F. $q (Ferdinando), $d 1746-1845. $t Sonatas, <font color="red">$m organs (2)</font>, $r C major<br />
100 $a Huybrechts, Albert, $d 1899-1938. $t Suites, <font color="red">$m piano (Sketches)</font><br />
<br />
'''added fields''':<br />
<font color="red">382 $a violins, violas, cello<br />
382 $a organs (2)<br />
382 $a piano</font><br />
</font><br />
<br />
===383 field===<br />
383 fields ('''Numerical Designation of Musical Work''') list the number associated with the musical work [http://www.loc.gov/marc/bibliographic/bd383.html (3)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Callhoff, Herbert, $d 1933-<br />
240 $a Quartets, strings, <font color="red">$n no. 2</font><br />
<br />
'''added field''':<br />
<font color="red">383 $a no. 2</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 383 '''$a''' to denote the Numeric Designation of Musical Work.<br />
<br />
===384 field===<br />
384 fields ('''Key''') help to differentiate between identical musical works, but in different keys tonally [http://www.loc.gov/marc/bibliographic/bd384.html (4)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Johann Joseph Ranier Rudolph, $c Erzherzog von Oesterreich.<br />
240 $a Sonatas, clarinet, piano, $n op. 2, <font color="red">$r A major</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a A major</font><br />
</font><br />
In this example, the 240 '''$r''' is mapped to 384 '''$a''' to denote the Key.<br />
<br />
Parenthetical information is typically discarded when mapping to 384 fields:<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Dowland, John, $d 1563?-1626. $t Galliards, $m lute, $n P. 31, <font color="red">$r G minor</font><br />
100 $a Mozart, Wolfgang Amadeus, $d 1756-1791. $t Requiem, $n K. 626, <font color="red">$r D minor (Süssmayr)</font><br />
100 $a Torelli, Giuseppe, $d 1658-1709. $t Solos, $m violins (2), <font color="red">$r D minor (Ms. British Library. Additional 64965, no. 9(a))</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a G minor<br />
384 $a D minor<br />
384 $a D minor</font><br />
</font><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Do not create 046 field or add 38X fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==LINKS==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.6RDA 4.62013-04-03T00:01:51Z<p>Judy: /* 046 field */</p>
<hr />
<div>==STEP 4.6 : OTHER ABBREVIATIONS==<br />
[[image:rda4-6.png]]<br />
===046 field===<br />
046 fields are useful when your dates cannot be correctly coded in X00 $d due to B.C. dates or incorrect dates being used [http://www.loc.gov/marc/bibliographic/bd046.html (1)]. This may be another means to make that date available or understandable:<br />
<font size="3"><br />
'''original field''':<br />
100 $a Smith, John, $d 1950-1952<br />
<br />
'''created field''':<br />
<font color="red">046 $a m $c 1950 $e 1952</font><br />
</font><br />
Here we have an example where the birth & death date of the person in question doesn't appear to be correct, so we can create an 046 field from the 100 $d in this instance. The '''m''' designates that we are working with '''multiple dates''' and the '''c''' and '''e''' subfields let us know that these dates are part of the '''Common Era'''.<br />
<br />
==Special Note for the 38X fields==<br />
Currently Backstage will only add the 382, 383, and 384 fields derived from the 240 field. If you need 38X's added from the 7XX fields please see your project manager, as there are complications that will need to be addressed.<br />
<br />
===382 field===<br />
38X fields can be added to your records to correspond with music headings in a way to help break up the original music heading into a more machine-actionable set of fields [http://www.loc.gov/marc/bibliographic/bd382.html (2)]. In particular, 382 fields ('''Medium of Performance''') chunk the music heading's medium into its own field:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Telemann, Georg Philipp, $d 1681-1767.<br />
240 $a Suites, <font color="red">$m string orchestra</font>, $r D major.<br />
<br />
'''added field''':<br />
<font color="red">382 $a string orchestra</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 382 '''$a''' to denote the Medium of Performance.<br />
<br />
MARS 2.0 processing will not attempt to add a 382 field if any of the following is present:<br />
*382 field already exists in record<br />
*240 field has $k, $o, $p, "brasses", "plucked instrument", or "keyboard instruments"<br />
*240 $m contains "strings", "woodwinds", "winds" '''and''' 240 $t does '''not''' contain "trio", "quartet", or "quintet"<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Hoffmeister, Franz Anton, $d 1754-1812. $t Quintets, <font color="red">$m violins, violas, cello</font>, $r A major<br />
100 $a Bonazzi, F. $q (Ferdinando), $d 1746-1845. $t Sonatas, <font color="red">$m organs (2)</font>, $r C major<br />
100 $a Huybrechts, Albert, $d 1899-1938. $t Suites, <font color="red">$m piano (Sketches)</font><br />
<br />
'''added fields''':<br />
<font color="red">382 $a violins, violas, cello<br />
382 $a organs (2)<br />
382 $a piano</font><br />
</font><br />
<br />
===383 field===<br />
383 fields ('''Numerical Designation of Musical Work''') list the number associated with the musical work [http://www.loc.gov/marc/bibliographic/bd383.html (3)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Callhoff, Herbert, $d 1933-<br />
240 $a Quartets, strings, <font color="red">$n no. 2</font><br />
<br />
'''added field''':<br />
<font color="red">383 $a no. 2</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 383 '''$a''' to denote the Numeric Designation of Musical Work.<br />
<br />
===384 field===<br />
384 fields ('''Key''') help to differentiate between identical musical works, but in different keys tonally [http://www.loc.gov/marc/bibliographic/bd384.html (4)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Johann Joseph Ranier Rudolph, $c Erzherzog von Oesterreich.<br />
240 $a Sonatas, clarinet, piano, $n op. 2, <font color="red">$r A major</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a A major</font><br />
</font><br />
In this example, the 240 '''$r''' is mapped to 384 '''$a''' to denote the Key.<br />
<br />
Parenthetical information is typically discarded when mapping to 384 fields:<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Dowland, John, $d 1563?-1626. $t Galliards, $m lute, $n P. 31, <font color="red">$r G minor</font><br />
100 $a Mozart, Wolfgang Amadeus, $d 1756-1791. $t Requiem, $n K. 626, <font color="red">$r D minor (Süssmayr)</font><br />
100 $a Torelli, Giuseppe, $d 1658-1709. $t Solos, $m violins (2), <font color="red">$r D minor (Ms. British Library. Additional 64965, no. 9(a))</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a G minor<br />
384 $a D minor<br />
384 $a D minor</font><br />
</font><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Do not create 046 field or add 38X fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==LINKS==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.6RDA 4.62013-04-03T00:01:19Z<p>Judy: /* 382 field */</p>
<hr />
<div>==STEP 4.6 : OTHER ABBREVIATIONS==<br />
[[image:rda4-6.png]]<br />
===046 field===<br />
046 fields are useful when your dates cannot be correctly coded in X00 $d, due to B.C. dates or incorrect dates being used [http://www.loc.gov/marc/bibliographic/bd046.html (1)]. This may be another means to make that date available or understandable:<br />
<font size="3"><br />
'''original field''':<br />
100 $a Smith, John, $d 1950-1952<br />
<br />
'''created field''':<br />
<font color="red">046 $a m $c 1950 $e 1952</font><br />
</font><br />
Here we have an example where the birth & death date of the person in question doesn't appear to be correct, so we can create an 046 field from the 100 $d in this instance. The '''m''' designates that we are working with '''multiple dates''' and the '''c''' and '''e''' subfields let us know that these dates are part of the '''Common Era'''.<br />
<br />
==Special Note for the 38X fields==<br />
Currently Backstage will only add the 382, 383, and 384 fields derived from the 240 field. If you need 38X's added from the 7XX fields please see your project manager, as there are complications that will need to be addressed.<br />
<br />
===382 field===<br />
38X fields can be added to your records to correspond with music headings in a way to help break up the original music heading into a more machine-actionable set of fields [http://www.loc.gov/marc/bibliographic/bd382.html (2)]. In particular, 382 fields ('''Medium of Performance''') chunk the music heading's medium into its own field:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Telemann, Georg Philipp, $d 1681-1767.<br />
240 $a Suites, <font color="red">$m string orchestra</font>, $r D major.<br />
<br />
'''added field''':<br />
<font color="red">382 $a string orchestra</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 382 '''$a''' to denote the Medium of Performance.<br />
<br />
MARS 2.0 processing will not attempt to add a 382 field if any of the following is present:<br />
*382 field already exists in record<br />
*240 field has $k, $o, $p, "brasses", "plucked instrument", or "keyboard instruments"<br />
*240 $m contains "strings", "woodwinds", "winds" '''and''' 240 $t does '''not''' contain "trio", "quartet", or "quintet"<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Hoffmeister, Franz Anton, $d 1754-1812. $t Quintets, <font color="red">$m violins, violas, cello</font>, $r A major<br />
100 $a Bonazzi, F. $q (Ferdinando), $d 1746-1845. $t Sonatas, <font color="red">$m organs (2)</font>, $r C major<br />
100 $a Huybrechts, Albert, $d 1899-1938. $t Suites, <font color="red">$m piano (Sketches)</font><br />
<br />
'''added fields''':<br />
<font color="red">382 $a violins, violas, cello<br />
382 $a organs (2)<br />
382 $a piano</font><br />
</font><br />
<br />
===383 field===<br />
383 fields ('''Numerical Designation of Musical Work''') list the number associated with the musical work [http://www.loc.gov/marc/bibliographic/bd383.html (3)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Callhoff, Herbert, $d 1933-<br />
240 $a Quartets, strings, <font color="red">$n no. 2</font><br />
<br />
'''added field''':<br />
<font color="red">383 $a no. 2</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 383 '''$a''' to denote the Numeric Designation of Musical Work.<br />
<br />
===384 field===<br />
384 fields ('''Key''') help to differentiate between identical musical works, but in different keys tonally [http://www.loc.gov/marc/bibliographic/bd384.html (4)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Johann Joseph Ranier Rudolph, $c Erzherzog von Oesterreich.<br />
240 $a Sonatas, clarinet, piano, $n op. 2, <font color="red">$r A major</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a A major</font><br />
</font><br />
In this example, the 240 '''$r''' is mapped to 384 '''$a''' to denote the Key.<br />
<br />
Parenthetical information is typically discarded when mapping to 384 fields:<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Dowland, John, $d 1563?-1626. $t Galliards, $m lute, $n P. 31, <font color="red">$r G minor</font><br />
100 $a Mozart, Wolfgang Amadeus, $d 1756-1791. $t Requiem, $n K. 626, <font color="red">$r D minor (Süssmayr)</font><br />
100 $a Torelli, Giuseppe, $d 1658-1709. $t Solos, $m violins (2), <font color="red">$r D minor (Ms. British Library. Additional 64965, no. 9(a))</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a G minor<br />
384 $a D minor<br />
384 $a D minor</font><br />
</font><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Do not create 046 field or add 38X fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==LINKS==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.6RDA 4.62013-04-02T23:56:30Z<p>Judy: /* 046 field */</p>
<hr />
<div>==STEP 4.6 : OTHER ABBREVIATIONS==<br />
[[image:rda4-6.png]]<br />
===046 field===<br />
046 fields are useful when your dates cannot be correctly coded in X00 $d, due to B.C. dates or incorrect dates being used [http://www.loc.gov/marc/bibliographic/bd046.html (1)]. This may be another means to make that date available or understandable:<br />
<font size="3"><br />
'''original field''':<br />
100 $a Smith, John, $d 1950-1952<br />
<br />
'''created field''':<br />
<font color="red">046 $a m $c 1950 $e 1952</font><br />
</font><br />
Here we have an example where the birth & death date of the person in question doesn't appear to be correct, so we can create an 046 field from the 100 $d in this instance. The '''m''' designates that we are working with '''multiple dates''' and the '''c''' and '''e''' subfields let us know that these dates are part of the '''Common Era'''.<br />
<br />
===382 field===<br />
38X fields can be added to your records to correspond with music headings in a way to help break up the original music heading into a more machine-actionable set of fields [http://www.loc.gov/marc/bibliographic/bd382.html (2)]. In particular, 382 fields ('''Medium of Performance''') chunk the music heading's medium into its own field:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Telemann, Georg Philipp, $d 1681-1767.<br />
240 $a Suites, <font color="red">$m string orchestra</font>, $r D major.<br />
<br />
'''added field''':<br />
<font color="red">382 $a string orchestra</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 382 '''$a''' to denote the Medium of Performance.<br />
<br />
MARS 2.0 processing will not attempt to add a 382 field if any of the following is present:<br />
*382 field already exists in record<br />
*240 field has $k, $o, $p, "brasses", "plucked instrument", or "keyboard instruments"<br />
*240 $m contains "strings", "woodwinds", "winds" '''and''' 240 $t does '''not''' contain "trio", "quartet", or "quintet"<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Hoffmeister, Franz Anton, $d 1754-1812. $t Quintets, <font color="red">$m violins, violas, cello</font>, $r A major<br />
100 $a Bonazzi, F. $q (Ferdinando), $d 1746-1845. $t Sonatas, <font color="red">$m organs (2)</font>, $r C major<br />
100 $a Huybrechts, Albert, $d 1899-1938. $t Suites, <font color="red">$m piano (Sketches)</font><br />
<br />
'''added fields''':<br />
<font color="red">382 $a violins, violas, cello<br />
382 $a organs (2)<br />
382 $a piano</font><br />
</font><br />
<br />
===383 field===<br />
383 fields ('''Numerical Designation of Musical Work''') list the number associated with the musical work [http://www.loc.gov/marc/bibliographic/bd383.html (3)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Callhoff, Herbert, $d 1933-<br />
240 $a Quartets, strings, <font color="red">$n no. 2</font><br />
<br />
'''added field''':<br />
<font color="red">383 $a no. 2</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 383 '''$a''' to denote the Numeric Designation of Musical Work.<br />
<br />
===384 field===<br />
384 fields ('''Key''') help to differentiate between identical musical works, but in different keys tonally [http://www.loc.gov/marc/bibliographic/bd384.html (4)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Johann Joseph Ranier Rudolph, $c Erzherzog von Oesterreich.<br />
240 $a Sonatas, clarinet, piano, $n op. 2, <font color="red">$r A major</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a A major</font><br />
</font><br />
In this example, the 240 '''$r''' is mapped to 384 '''$a''' to denote the Key.<br />
<br />
Parenthetical information is typically discarded when mapping to 384 fields:<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Dowland, John, $d 1563?-1626. $t Galliards, $m lute, $n P. 31, <font color="red">$r G minor</font><br />
100 $a Mozart, Wolfgang Amadeus, $d 1756-1791. $t Requiem, $n K. 626, <font color="red">$r D minor (Süssmayr)</font><br />
100 $a Torelli, Giuseppe, $d 1658-1709. $t Solos, $m violins (2), <font color="red">$r D minor (Ms. British Library. Additional 64965, no. 9(a))</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a G minor<br />
384 $a D minor<br />
384 $a D minor</font><br />
</font><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Do not create 046 field or add 38X fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==LINKS==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.6RDA 4.62013-04-02T23:55:51Z<p>Judy: /* Special Note */</p>
<hr />
<div>==STEP 4.6 : OTHER ABBREVIATIONS==<br />
[[image:rda4-6.png]]<br />
===046 field===<br />
046 fields are useful when your dates cannot be correctly coded in X00 $d, due to B.C. dates or incorrect dates being used [http://www.loc.gov/marc/bibliographic/bd046.html (1)]. This may another means to make that date available or understandable:<br />
<font size="3"><br />
'''original field''':<br />
100 $a Smith, John, $d 1950-1952<br />
<br />
'''created field''':<br />
<font color="red">046 $a m $c 1950 $e 1952</font><br />
</font><br />
Here we have an example where the birth & death date of the person in question doesn't appear to be correct, so we can create an 046 field from the 100 $d in this instance. The '''m''' designates that we are working with '''multiple dates''' and the '''c''' and '''e''' subfields let us know that these dates are part of the '''Common Era'''.<br />
===382 field===<br />
38X fields can be added to your records to correspond with music headings in a way to help break up the original music heading into a more machine-actionable set of fields [http://www.loc.gov/marc/bibliographic/bd382.html (2)]. In particular, 382 fields ('''Medium of Performance''') chunk the music heading's medium into its own field:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Telemann, Georg Philipp, $d 1681-1767.<br />
240 $a Suites, <font color="red">$m string orchestra</font>, $r D major.<br />
<br />
'''added field''':<br />
<font color="red">382 $a string orchestra</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 382 '''$a''' to denote the Medium of Performance.<br />
<br />
MARS 2.0 processing will not attempt to add a 382 field if any of the following is present:<br />
*382 field already exists in record<br />
*240 field has $k, $o, $p, "brasses", "plucked instrument", or "keyboard instruments"<br />
*240 $m contains "strings", "woodwinds", "winds" '''and''' 240 $t does '''not''' contain "trio", "quartet", or "quintet"<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Hoffmeister, Franz Anton, $d 1754-1812. $t Quintets, <font color="red">$m violins, violas, cello</font>, $r A major<br />
100 $a Bonazzi, F. $q (Ferdinando), $d 1746-1845. $t Sonatas, <font color="red">$m organs (2)</font>, $r C major<br />
100 $a Huybrechts, Albert, $d 1899-1938. $t Suites, <font color="red">$m piano (Sketches)</font><br />
<br />
'''added fields''':<br />
<font color="red">382 $a violins, violas, cello<br />
382 $a organs (2)<br />
382 $a piano</font><br />
</font><br />
<br />
===383 field===<br />
383 fields ('''Numerical Designation of Musical Work''') list the number associated with the musical work [http://www.loc.gov/marc/bibliographic/bd383.html (3)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Callhoff, Herbert, $d 1933-<br />
240 $a Quartets, strings, <font color="red">$n no. 2</font><br />
<br />
'''added field''':<br />
<font color="red">383 $a no. 2</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 383 '''$a''' to denote the Numeric Designation of Musical Work.<br />
<br />
===384 field===<br />
384 fields ('''Key''') help to differentiate between identical musical works, but in different keys tonally [http://www.loc.gov/marc/bibliographic/bd384.html (4)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Johann Joseph Ranier Rudolph, $c Erzherzog von Oesterreich.<br />
240 $a Sonatas, clarinet, piano, $n op. 2, <font color="red">$r A major</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a A major</font><br />
</font><br />
In this example, the 240 '''$r''' is mapped to 384 '''$a''' to denote the Key.<br />
<br />
Parenthetical information is typically discarded when mapping to 384 fields:<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Dowland, John, $d 1563?-1626. $t Galliards, $m lute, $n P. 31, <font color="red">$r G minor</font><br />
100 $a Mozart, Wolfgang Amadeus, $d 1756-1791. $t Requiem, $n K. 626, <font color="red">$r D minor (Süssmayr)</font><br />
100 $a Torelli, Giuseppe, $d 1658-1709. $t Solos, $m violins (2), <font color="red">$r D minor (Ms. British Library. Additional 64965, no. 9(a))</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a G minor<br />
384 $a D minor<br />
384 $a D minor</font><br />
</font><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Do not create 046 field or add 38X fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==LINKS==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.6RDA 4.62013-04-02T22:49:33Z<p>Judy: /* Special Note */</p>
<hr />
<div>==STEP 4.6 : OTHER ABBREVIATIONS==<br />
[[image:rda4-6.png]]<br />
==Special Note==<br />
If you are having any or all of these fields added to a bibliographic record, it is important to know that if there are multiple headings these fields can be added from, they will be added in the order they are encountered. So the 382, 383, and 384 fields will be added first from 240 fields, then from each 7XX field in the order that they appear in the record. If you need to have these fields linked in some way, please see your project manager.<br />
===046 field===<br />
046 fields are useful when your dates cannot be correctly coded in X00 $d, due to B.C. dates or incorrect dates being used [http://www.loc.gov/marc/bibliographic/bd046.html (1)]. This may another means to make that date available or understandable:<br />
<font size="3"><br />
'''original field''':<br />
100 $a Smith, John, $d 1950-1952<br />
<br />
'''created field''':<br />
<font color="red">046 $a m $c 1950 $e 1952</font><br />
</font><br />
Here we have an example where the birth & death date of the person in question doesn't appear to be correct, so we can create an 046 field from the 100 $d in this instance. The '''m''' designates that we are working with '''multiple dates''' and the '''c''' and '''e''' subfields let us know that these dates are part of the '''Common Era'''.<br />
===382 field===<br />
38X fields can be added to your records to correspond with music headings in a way to help break up the original music heading into a more machine-actionable set of fields [http://www.loc.gov/marc/bibliographic/bd382.html (2)]. In particular, 382 fields ('''Medium of Performance''') chunk the music heading's medium into its own field:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Telemann, Georg Philipp, $d 1681-1767.<br />
240 $a Suites, <font color="red">$m string orchestra</font>, $r D major.<br />
<br />
'''added field''':<br />
<font color="red">382 $a string orchestra</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 382 '''$a''' to denote the Medium of Performance.<br />
<br />
MARS 2.0 processing will not attempt to add a 382 field if any of the following is present:<br />
*382 field already exists in record<br />
*240 field has $k, $o, $p, "brasses", "plucked instrument", or "keyboard instruments"<br />
*240 $m contains "strings", "woodwinds", "winds" '''and''' 240 $t does '''not''' contain "trio", "quartet", or "quintet"<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Hoffmeister, Franz Anton, $d 1754-1812. $t Quintets, <font color="red">$m violins, violas, cello</font>, $r A major<br />
100 $a Bonazzi, F. $q (Ferdinando), $d 1746-1845. $t Sonatas, <font color="red">$m organs (2)</font>, $r C major<br />
100 $a Huybrechts, Albert, $d 1899-1938. $t Suites, <font color="red">$m piano (Sketches)</font><br />
<br />
'''added fields''':<br />
<font color="red">382 $a violins, violas, cello<br />
382 $a organs (2)<br />
382 $a piano</font><br />
</font><br />
<br />
===383 field===<br />
383 fields ('''Numerical Designation of Musical Work''') list the number associated with the musical work [http://www.loc.gov/marc/bibliographic/bd383.html (3)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Callhoff, Herbert, $d 1933-<br />
240 $a Quartets, strings, <font color="red">$n no. 2</font><br />
<br />
'''added field''':<br />
<font color="red">383 $a no. 2</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 383 '''$a''' to denote the Numeric Designation of Musical Work.<br />
<br />
===384 field===<br />
384 fields ('''Key''') help to differentiate between identical musical works, but in different keys tonally [http://www.loc.gov/marc/bibliographic/bd384.html (4)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Johann Joseph Ranier Rudolph, $c Erzherzog von Oesterreich.<br />
240 $a Sonatas, clarinet, piano, $n op. 2, <font color="red">$r A major</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a A major</font><br />
</font><br />
In this example, the 240 '''$r''' is mapped to 384 '''$a''' to denote the Key.<br />
<br />
Parenthetical information is typically discarded when mapping to 384 fields:<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Dowland, John, $d 1563?-1626. $t Galliards, $m lute, $n P. 31, <font color="red">$r G minor</font><br />
100 $a Mozart, Wolfgang Amadeus, $d 1756-1791. $t Requiem, $n K. 626, <font color="red">$r D minor (Süssmayr)</font><br />
100 $a Torelli, Giuseppe, $d 1658-1709. $t Solos, $m violins (2), <font color="red">$r D minor (Ms. British Library. Additional 64965, no. 9(a))</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a G minor<br />
384 $a D minor<br />
384 $a D minor</font><br />
</font><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Do not create 046 field or add 38X fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==LINKS==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_4.6RDA 4.62013-04-02T22:48:25Z<p>Judy: /* Special Note */</p>
<hr />
<div>==STEP 4.6 : OTHER ABBREVIATIONS==<br />
[[image:rda4-6.png]]<br />
==Special Note==<br />
If you are having any or all of these fields added to a bibliographic record, it is important to know that if there are multiple headings these fields can be added from, they will be added in the order they are encountered. So the 382, 383, and 384 fields will be added first from 240 fields, then each 7XX field in order that those appear in the record. If you need to have these fields linked in some way, please see your project manager.<br />
===046 field===<br />
046 fields are useful when your dates cannot be correctly coded in X00 $d, due to B.C. dates or incorrect dates being used [http://www.loc.gov/marc/bibliographic/bd046.html (1)]. This may another means to make that date available or understandable:<br />
<font size="3"><br />
'''original field''':<br />
100 $a Smith, John, $d 1950-1952<br />
<br />
'''created field''':<br />
<font color="red">046 $a m $c 1950 $e 1952</font><br />
</font><br />
Here we have an example where the birth & death date of the person in question doesn't appear to be correct, so we can create an 046 field from the 100 $d in this instance. The '''m''' designates that we are working with '''multiple dates''' and the '''c''' and '''e''' subfields let us know that these dates are part of the '''Common Era'''.<br />
===382 field===<br />
38X fields can be added to your records to correspond with music headings in a way to help break up the original music heading into a more machine-actionable set of fields [http://www.loc.gov/marc/bibliographic/bd382.html (2)]. In particular, 382 fields ('''Medium of Performance''') chunk the music heading's medium into its own field:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Telemann, Georg Philipp, $d 1681-1767.<br />
240 $a Suites, <font color="red">$m string orchestra</font>, $r D major.<br />
<br />
'''added field''':<br />
<font color="red">382 $a string orchestra</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 382 '''$a''' to denote the Medium of Performance.<br />
<br />
MARS 2.0 processing will not attempt to add a 382 field if any of the following is present:<br />
*382 field already exists in record<br />
*240 field has $k, $o, $p, "brasses", "plucked instrument", or "keyboard instruments"<br />
*240 $m contains "strings", "woodwinds", "winds" '''and''' 240 $t does '''not''' contain "trio", "quartet", or "quintet"<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Hoffmeister, Franz Anton, $d 1754-1812. $t Quintets, <font color="red">$m violins, violas, cello</font>, $r A major<br />
100 $a Bonazzi, F. $q (Ferdinando), $d 1746-1845. $t Sonatas, <font color="red">$m organs (2)</font>, $r C major<br />
100 $a Huybrechts, Albert, $d 1899-1938. $t Suites, <font color="red">$m piano (Sketches)</font><br />
<br />
'''added fields''':<br />
<font color="red">382 $a violins, violas, cello<br />
382 $a organs (2)<br />
382 $a piano</font><br />
</font><br />
<br />
===383 field===<br />
383 fields ('''Numerical Designation of Musical Work''') list the number associated with the musical work [http://www.loc.gov/marc/bibliographic/bd383.html (3)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Callhoff, Herbert, $d 1933-<br />
240 $a Quartets, strings, <font color="red">$n no. 2</font><br />
<br />
'''added field''':<br />
<font color="red">383 $a no. 2</font><br />
</font><br />
In this example, the 240 '''$m''' is mapped to 383 '''$a''' to denote the Numeric Designation of Musical Work.<br />
<br />
===384 field===<br />
384 fields ('''Key''') help to differentiate between identical musical works, but in different keys tonally [http://www.loc.gov/marc/bibliographic/bd384.html (4)]:<br />
<br />
<font size="3"><br />
'''original field''':<br />
100 $a Johann Joseph Ranier Rudolph, $c Erzherzog von Oesterreich.<br />
240 $a Sonatas, clarinet, piano, $n op. 2, <font color="red">$r A major</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a A major</font><br />
</font><br />
In this example, the 240 '''$r''' is mapped to 384 '''$a''' to denote the Key.<br />
<br />
Parenthetical information is typically discarded when mapping to 384 fields:<br />
<font size="3"><br />
'''original fields''':<br />
100 $a Dowland, John, $d 1563?-1626. $t Galliards, $m lute, $n P. 31, <font color="red">$r G minor</font><br />
100 $a Mozart, Wolfgang Amadeus, $d 1756-1791. $t Requiem, $n K. 626, <font color="red">$r D minor (Süssmayr)</font><br />
100 $a Torelli, Giuseppe, $d 1658-1709. $t Solos, $m violins (2), <font color="red">$r D minor (Ms. British Library. Additional 64965, no. 9(a))</font><br />
<br />
'''added fields''':<br />
<font color="red">384 $a G minor<br />
384 $a D minor<br />
384 $a D minor</font><br />
</font><br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Do not create 046 field or add 38X fields.<br />
|}<br />
<div style=clear:both></div><br><br />
==LINKS==<br />
<center><font size="4">[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]] - [[RDA_4.7|4.7]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T20:19:14Z<p>Judy: /* FTP options */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
=USING THE WEBSITE=<br />
<br />
== Website Portal==<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
The Summary Tab dynamically updates as you save each step in your profile. It is our hope that the Summary provides you with a quick synopsis of the settings you wish to see throughout your profile.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
== Jobs Options==<br />
Backstage refers to any file that has been uploaded or delivered to our customers as a job.<br />
<br />
A job is tracked separately from any other job or file that is processed. Uploading files using our website is made to be as intuitive as attaching documents to an email.<br />
<br />
=== Adding jobs===<br />
After you choose to add a job from the main menu, you will be taken to a page that lists various options. The first option is asking what kind of job this is, with the default choice being '''Current Cataloging'''. You can change this to the type of file you are uploading.<br />
<br />
From there, you just need to choose the file to upload. If you are uploading multiple files, you will need to select each file one at a time as a security precaution on our side.<br />
<br />
Navigate to the location of your file(s), whether they are on your computer desktop, a network directory, or on some other media. Then, if you have all of the files necessary for that job, just click on '''Send'''.<br />
<br />
=== Tracking jobs===<br />
Many kinds of jobs are processed on a daily basis at Backstage. In order to keep track of all of these different kinds of jobs, we created a tool on our website for this purpose.<br />
<br />
After a job is created, it is put into a queue based on the type of job. It might be awaiting processing or currently in processing, or part of our finished jobs queue.<br />
<br />
Start and finish times are listed, as is the type of job and job number. Each tracked job can also be viewed or edited at any time. '''Finished jobs will remain online a minimum of one year after processing'''.<br />
<br />
Both original files uploaded, and processed files delivered are available within the same tracked job. This is useful when it is necessary to view the original file by either Backstage or the customer, in order to resolve potential concerns.<br />
<br />
=== FTP options===<br />
Please see your Backstage project manager for more details on using traditional FTP methods for uploading or retrieving your files.<br />
<br />
Please feel free to name your files whatever makes the most sense to you. Our web server can handle most any file name.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T20:18:20Z<p>Judy: /* Tracking jobs */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
=USING THE WEBSITE=<br />
<br />
== Website Portal==<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
The Summary Tab dynamically updates as you save each step in your profile. It is our hope that the Summary provides you with a quick synopsis of the settings you wish to see throughout your profile.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
== Jobs Options==<br />
Backstage refers to any file that has been uploaded or delivered to our customers as a job.<br />
<br />
A job is tracked separately from any other job or file that is processed. Uploading files using our website is made to be as intuitive as attaching documents to an email.<br />
<br />
=== Adding jobs===<br />
After you choose to add a job from the main menu, you will be taken to a page that lists various options. The first option is asking what kind of job this is, with the default choice being '''Current Cataloging'''. You can change this to the type of file you are uploading.<br />
<br />
From there, you just need to choose the file to upload. If you are uploading multiple files, you will need to select each file one at a time as a security precaution on our side.<br />
<br />
Navigate to the location of your file(s), whether they are on your computer desktop, a network directory, or on some other media. Then, if you have all of the files necessary for that job, just click on '''Send'''.<br />
<br />
=== Tracking jobs===<br />
Many kinds of jobs are processed on a daily basis at Backstage. In order to keep track of all of these different kinds of jobs, we created a tool on our website for this purpose.<br />
<br />
After a job is created, it is put into a queue based on the type of job. It might be awaiting processing or currently in processing, or part of our finished jobs queue.<br />
<br />
Start and finish times are listed, as is the type of job and job number. Each tracked job can also be viewed or edited at any time. '''Finished jobs will remain online a minimum of one year after processing'''.<br />
<br />
Both original files uploaded, and processed files delivered are available within the same tracked job. This is useful when it is necessary to view the original file by either Backstage or the customer, in order to resolve potential concerns.<br />
<br />
=== FTP options===<br />
Please see your Backstage project manager for more details on using traditional FTP methods for uploading or retrieving your files.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T20:17:49Z<p>Judy: /* Tracking jobs */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
=USING THE WEBSITE=<br />
<br />
== Website Portal==<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
The Summary Tab dynamically updates as you save each step in your profile. It is our hope that the Summary provides you with a quick synopsis of the settings you wish to see throughout your profile.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
== Jobs Options==<br />
Backstage refers to any file that has been uploaded or delivered to our customers as a job.<br />
<br />
A job is tracked separately from any other job or file that is processed. Uploading files using our website is made to be as intuitive as attaching documents to an email.<br />
<br />
=== Adding jobs===<br />
After you choose to add a job from the main menu, you will be taken to a page that lists various options. The first option is asking what kind of job this is, with the default choice being '''Current Cataloging'''. You can change this to the type of file you are uploading.<br />
<br />
From there, you just need to choose the file to upload. If you are uploading multiple files, you will need to select each file one at a time as a security precaution on our side.<br />
<br />
Navigate to the location of your file(s), whether they are on your computer desktop, a network directory, or on some other media. Then, if you have all of the files necessary for that job, just click on '''Send'''.<br />
<br />
=== Tracking jobs===<br />
Many kinds of jobs are processed on a daily basis at Backstage. In order to keep track of all of these different kinds of jobs, we created a tool on our website for this purpose.<br />
<br />
After a job is created, it is put into a queue based on the type of job. It might be awaiting processing or currently in processing, or part of our finished jobs queue.<br />
<br />
Start and finish times are listed, as is the type of job and job number. Each tracked job can also be viewed or edited at any time. '''Finished jobs will remain online a minimum of one year after processing'''.<br />
<br />
Both original files uploaded, and processed files delivered are available within the same tracked job. This is useful when it is necessary to view the original file, by either Backstage or the customer, in order to resolve potential concerns.<br />
<br />
=== FTP options===<br />
Please see your Backstage project manager for more details on using traditional FTP methods for uploading or retrieving your files.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T20:16:04Z<p>Judy: /* Adding jobs */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
=USING THE WEBSITE=<br />
<br />
== Website Portal==<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
The Summary Tab dynamically updates as you save each step in your profile. It is our hope that the Summary provides you with a quick synopsis of the settings you wish to see throughout your profile.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
== Jobs Options==<br />
Backstage refers to any file that has been uploaded or delivered to our customers as a job.<br />
<br />
A job is tracked separately from any other job or file that is processed. Uploading files using our website is made to be as intuitive as attaching documents to an email.<br />
<br />
=== Adding jobs===<br />
After you choose to add a job from the main menu, you will be taken to a page that lists various options. The first option is asking what kind of job this is, with the default choice being '''Current Cataloging'''. You can change this to the type of file you are uploading.<br />
<br />
From there, you just need to choose the file to upload. If you are uploading multiple files, you will need to select each file one at a time as a security precaution on our side.<br />
<br />
Navigate to the location of your file(s), whether they are on your computer desktop, a network directory, or on some other media. Then, if you have all of the files necessary for that job, just click on '''Send'''.<br />
<br />
=== Tracking jobs===<br />
Many kinds of jobs are processed on a daily basis at Backstage. In order to keep track of all of these different kinds of jobs, we created a tool on our website for this purpose.<br />
<br />
After a job is created, it is put into a queue based on the type of job. It might be awaiting processing or currently in processing, or part of our finished jobs queue.<br />
<br />
Start and finish times are listed, as is the type of job and job number. Each tracked job can also be viewed or edited at any time. Finished jobs will remain online a minimum of one year after processing.<br />
<br />
Both original files uploaded, and processed files delivered are available within the same tracked job. This is useful when it is necessary to view the original file, by either Backstage or the customer, in order to resolve potential concerns.<br />
<br />
=== FTP options===<br />
Please see your Backstage project manager for more details on using traditional FTP methods for uploading or retrieving your files.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T20:11:58Z<p>Judy: /* Adding jobs */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
=USING THE WEBSITE=<br />
<br />
== Website Portal==<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
The Summary Tab dynamically updates as you save each step in your profile. It is our hope that the Summary provides you with a quick synopsis of the settings you wish to see throughout your profile.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
== Jobs Options==<br />
Backstage refers to any file that has been uploaded or delivered to our customers as a job.<br />
<br />
A job is tracked separately from any other job or file that is processed. Uploading files using our website is made to be as intuitive as attaching documents to an email.<br />
<br />
=== Adding jobs===<br />
After you choose to add a job from the main menu, you will be taken to a page that lists various options. The first option is asking what kind of job this is, with the default choice being '''Current Cataloging'''. You can change this to the type of file you are uploading.<br />
<br />
From there, you just need to choose the file to upload. If you are uploading multiple files, you will need to select each file one at a time as a security precaution on our side.<br />
<br />
Navigate to the location of your file(s), whether they are on your computer desktop, a network directory, or on some other media. Then, if you have all of the files necessary for that job, just click on '''Send'''.<br />
<br />
=== FTP options===<br />
Please see your Backstage project manager for more details on using traditional FTP methods for uploading or retrieving your files.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T20:09:59Z<p>Judy: /* Website Portal */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
=USING THE WEBSITE=<br />
<br />
== Website Portal==<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
The Summary Tab dynamically updates as you save each step in your profile. It is our hope that the Summary provides you with a quick synopsis of the settings you wish to see throughout your profile.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
== Jobs Options==<br />
Backstage refers to any file that has been uploaded or delivered to our customers as a job.<br />
<br />
A job is tracked separately from any other job or file that is processed. Uploading files using our website is made to be as intuitive as attaching documents to an email.<br />
<br />
=== Adding jobs===<br />
After you choose to add a job from the main menu, you will be taken to a page that lists various options. The first option is asking what kind of job this is, with the default choice being '''Current Cataloging'''. You can change this to the type of file you are uploading.<br />
<br />
From there, you just need to choose the file to upload. If you are uploading multiple files, you will need to upload each file one at a time as a security precaution on our side.<br />
<br />
Navigate to the location of your file(s), whether they are on your computer desktop, a network directory, or on some other media. Then, if you have all of the files necessary for that job, just click on '''Send'''.<br />
<br />
=== FTP options===<br />
Please see your Backstage project manager for more details on using traditional FTP methods for uploading or retrieving your files.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T20:09:44Z<p>Judy: /* Profile questions */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
=USING THE WEBSITE=<br />
<br />
=== Website Portal===<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
The Summary Tab dynamically updates as you save each step in your profile. It is our hope that the Summary provides you with a quick synopsis of the settings you wish to see throughout your profile.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
== Jobs Options==<br />
Backstage refers to any file that has been uploaded or delivered to our customers as a job.<br />
<br />
A job is tracked separately from any other job or file that is processed. Uploading files using our website is made to be as intuitive as attaching documents to an email.<br />
<br />
=== Adding jobs===<br />
After you choose to add a job from the main menu, you will be taken to a page that lists various options. The first option is asking what kind of job this is, with the default choice being '''Current Cataloging'''. You can change this to the type of file you are uploading.<br />
<br />
From there, you just need to choose the file to upload. If you are uploading multiple files, you will need to upload each file one at a time as a security precaution on our side.<br />
<br />
Navigate to the location of your file(s), whether they are on your computer desktop, a network directory, or on some other media. Then, if you have all of the files necessary for that job, just click on '''Send'''.<br />
<br />
=== FTP options===<br />
Please see your Backstage project manager for more details on using traditional FTP methods for uploading or retrieving your files.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T20:06:29Z<p>Judy: /* Profile options */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
=USING THE WEBSITE=<br />
<br />
=== Website Portal===<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
The Summary Tab dynamically updates as you save each step in your profile. It is our hope that the Summary provides you with a quick synopsis of the settings you wish to see throughout your profile.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T20:02:51Z<p>Judy: /* Website Portal */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
=USING THE WEBSITE=<br />
<br />
=== Website Portal===<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T20:02:00Z<p>Judy: /* USING THE WEBSITE */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
=USING THE WEBSITE=<br />
<br />
== Website Portal==<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T20:01:09Z<p>Judy: /* USING THE WEBSITE */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
===USING THE WEBSITE===<br />
<br />
== Website Portal==<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T19:58:39Z<p>Judy: /* USING THE WEBSITE */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==USING THE WEBSITE==<br />
<br />
== Website Portal==<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
=== Profile options===<br />
Each of the 6 steps in the online profile has an option to fill in the defaults listed within this guide. The defaults are intended as guideposts only. Every part of the profile can be customized according to your preference.<br />
<br />
Multiple staff members can fill out the online profile at the same time, as long as they are in different steps when they do so. This allows our customers to assign certain steps based on priority without worrying about the need to exit the profile while doing so.<br />
<br />
Each step can be saved at anytime, whether the step has been completely filled out or is only partially finished. This ensures that should any questions arise during the profile, those can be addressed with the assistance of your Backstage project manager.<br />
<br />
Profiles can also be printed, either one step at a time or in their entirety. Multiple profiles can be established, depending on processing criteria desired.<br />
<br />
=== Profile questions===<br />
Every question has an associated Wiki link next to it. The link corresponds to the printed information contained in this guide, but in online format. This is especially useful when more information is necessary in order to choose the appropriate option for each question.<br />
<br />
The default for each question will be highlighted or offset from the other options in order to make it easier to discern.<br />
<br />
Steps should be saved before navigating to other parts of the online profile, otherwise any changes made will be lost. However, profile steps can be saved multiple times in case many different changes need to be made to the same step.<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T19:57:42Z<p>Judy: /* Default */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==USING THE WEBSITE==<br />
<br />
Our customers<br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T19:50:11Z<p>Judy: /* RDA 1.5: Backstage Change Stamp */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.5RDA 1.52013-04-02T19:21:50Z<p>Judy: /* RDA 1.5: Backstage Change Stamp */</p>
<hr />
<div>==RDA 1.5: Backstage Change Stamp==<br />
[[Image:rda1-5.png]]<br><br><br />
Backstage can '''stamp''' each bibliographic record with one or more of the<br />
following identifiers, or we can stamp only those bibliographic records that were changed<br />
during the RDA processing.<br />
<br />
Indicate in Step 1.5 which, if any, of the following stamp options you would like<br />
in your bibliographic records:<br />
*'''040''' — MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.<br />
*'''005''' — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.<br />
*'''9XX''' — The text '''MARS''' can be added in a $a in a field you specify (e.g., 945 $a MARS).<br />
*'''9XX 'RDA ENRICHED'''' — The text '''RDA ENRICHED''' can be added in a $a in a field you specify (e.g., 945 $a RDA ENRICHED).<br />
*'''Other''' — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.<br />
<br />
'''Although not allowed by PCC, our processing can also add 040 $e rda to your AACR2 records that have been enriched with RDA elements. The idea is that records should not be coded as RDA (040 $e rda) unless those records have undergone complete redescription with the actual item in hand. However, if you do want the 040 $e we can add it.'''<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Add 040 $d UtOrBLW & 005 (add or update) to all bibs.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.4RDA 1.42013-04-02T19:18:29Z<p>Judy: /* Bibliographic file segmentation */</p>
<hr />
<div>==RDA 1.4: Records to Deliver==<br />
[[Image:rda1-4.png]]<br><br><br />
===All bib records===<br />
If you prefer, you may have all bibs returned whether they have had any changes or not.<br />
<br />
===Changed bibs only===<br />
This option encompasses all changes made during the RDA processing. If you<br />
want the RDA processing to only take place when enriching and validating<br />
existing RDA bib records, then you could choose to have only changed bib<br />
records returned.<br />
<br />
===Bibliographic file segmentation===<br />
ILS limitations or requirements for loading and indexing updated records are a<br />
consideration in determining maximum bibliographic output size.<br />
<br />
The response time in some local systems is sometimes degraded during<br />
prolonged loads. In other ILS, essential online system tasks cannot be<br />
performed during a load.<br />
<br />
While Backstage can handle files in excess of 1,000,000 records, we can also<br />
distribute files broken up into more appropriate chunks to facilitate the loading<br />
and indexing processes on your side.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| All bibliographic records returned in a single file.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.4RDA 1.42013-04-02T19:06:20Z<p>Judy: /* Changed bibs only */</p>
<hr />
<div>==RDA 1.4: Records to Deliver==<br />
[[Image:rda1-4.png]]<br><br><br />
===All bib records===<br />
If you prefer, you may have all bibs returned whether they have had any changes or not.<br />
<br />
===Changed bibs only===<br />
This option encompasses all changes made during the RDA processing. If you<br />
want the RDA processing to only take place when enriching and validating<br />
existing RDA bib records, then you could choose to have only changed bib<br />
records returned.<br />
<br />
===Bibliographic file segmentation===<br />
ILS limitations or requirements for loading and indexing updated records are a<br />
consideration in determining maximum bibliographic output size.<br />
<br />
The response time in some local systems is sometimes degraded during<br />
prolonged loads. In other ILS, essential online system tasks cannot be<br />
performed during a load.<br />
<br />
While Backstage can handle files in excess of 1,000,000 records, we can also<br />
distribute files broken up into more appropriate chunks to facilitate the loading<br />
and indexing processes at your side.<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| All bibliographic records returned in a single file.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.1RDA 1.12013-04-02T18:54:47Z<p>Judy: /* Website Portal */</p>
<hr />
<div>==RDA 1.1: Records Uploaded to Backstage==<br />
[[Image:rda1-1.png]]<br><br><br />
=== Bibliographic records ===<br />
There are all kinds of records nowadays, comprising many different formats:<br />
MARC, MARCXML, ONIX, etc. Files of these types may contain similar<br />
information, yet it is broken up into different fields or elements, depending on<br />
format.<br />
<br />
While BSLW processes records natively in MARC format, we have many<br />
tools available to successfully convert to or from any of the other formats listed<br />
above.<br />
<br />
A library can process all or part of the bibliographic records from its local ILS<br />
system or process bibliographic records purchased from a different cataloging<br />
source.<br />
<br />
=== File handling ===<br />
At Backstage, we enjoy providing our customers with options. Each part of<br />
our profile is geared to be as customizable as possible, providing you with a<br />
few different options to get you started. Any part of the profile may then be<br />
expanded upon in order to match your expectations to the desired results.<br />
<br />
Our preferred method of file-handling is through our website portal. Each<br />
customer will have their own login and password to access the site. Once logged<br />
in, our customers can view or edit their profile at any time, upload new files for<br />
processing, or retrieve files at their convenience.<br />
<br />
However, we also recognize that our customers may already have upload and download<br />
scripts written on their side. So it may make more sense to use a traditional FTP<br />
method to transfer files between Backstage and your system.<br />
<br />
In this first step, we think it is a good time to also discuss the format of your<br />
MARC records. Here you can let us know which format the file submitted will be<br />
sent as: MARC-8 or UTF-8. If you do not know, chances are excellent that we can<br />
easily inform you once you upload your file to us.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Files are uploaded in UTF-8 format through the website.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.1RDA 1.12013-04-02T18:49:01Z<p>Judy: /* File handling */</p>
<hr />
<div>==RDA 1.1: Records Uploaded to Backstage==<br />
[[Image:rda1-1.png]]<br><br><br />
=== Bibliographic records ===<br />
There are all kinds of records nowadays, comprising many different formats:<br />
MARC, MARCXML, ONIX, etc. Files of these types may contain similar<br />
information, yet it is broken up into different fields or elements, depending on<br />
format.<br />
<br />
While BSLW processes records natively in MARC format, we have many<br />
tools available to successfully convert to or from any of the other formats listed<br />
above.<br />
<br />
A library can process all or part of the bibliographic records from its local ILS<br />
system or process bibliographic records purchased from a different cataloging<br />
source.<br />
<br />
=== File handling ===<br />
At Backstage, we enjoy providing our customers with options. Each part of<br />
our profile is geared to be as customizable as possible, providing you with a<br />
few different options to get you started. Any part of the profile may then be<br />
expanded upon in order to match your expectations to the desired results.<br />
<br />
Our preferred method of file-handling is through our website portal. Each<br />
customer will have their own login and password to access the site. Once logged<br />
in, our customers can view or edit their profile at any time, upload new files for<br />
processing, or retrieve files at their convenience.<br />
<br />
However, we also recognize that our customers may already have upload and download<br />
scripts written on their side. So it may make more sense to use a traditional FTP<br />
method to transfer files between Backstage and your system.<br />
<br />
In this first step, we think it is a good time to also discuss the format of your<br />
MARC records. Here you can let us know which format the file submitted will be<br />
sent as: MARC-8 or UTF-8. If you do not know, chances are excellent that we can<br />
easily inform you once you upload your file to us.<br />
<br />
== Website Portal==<br />
[http://ac.bslw.com/mars| http://ac.bslw.com/mars]<br><br />
Our customers can login to the site listed above at anytime in order to view or edit their profile settings, upload new files for processing, or retrieve files.<br />
<br />
As our team continues to refine the user experience for navigating our website portal, including screen shots in this guide will be kept to a minimum to avoid inconsistencies.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Files are uploaded in UTF-8 format through the website.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.0RDA 1.02013-04-02T18:25:43Z<p>Judy: /* Overview */</p>
<hr />
<div>== RDA Planning Guide ==<br />
The RDA Planning Guide from Backstage Library Works explains the range of options available through our RDA MARC record services. This includes the validation of existing RDA bibliographic records and enriching and upgrading AACR2 records with RDA elements.<br />
<br />
Please contact your Sales representative to request additional no-charge copies of this Guide: '''800.288.1265'''. The information contained within this guide should be shared with cataloging managers and system managers. You may also want to share it with your local system representatives.<br />
<br />
=== Overview ===<br />
Resource Description and Access (RDA) is a set of instructions or rules for the description of books and other materials or resources. RDA is intended to replace Anglo-American Cataloging Rules 2nd Edition (AACR2), the current US standard for cataloging.<br />
<br />
RDA is built on foundations established in AACR2 and the cataloging traditions on which they were based. A key difference in the RDA design is its use of the Functional Requirements for Bibliographic Records and Authority Data (FRBR and FRAD).<br />
<br />
RDA uses the language and terminology of FRBR and FRAD. The FRBR entities, attributes, and relationships are used for bibliographic description.<br />
<br />
=== RDA rules ===<br />
The RDA rules are organized to relate bibliographic description to the FRBR entities, attributes, and relationships. The first 4 sections of RDA cover elements corresponding to the entity attributes defined in FRBR and FRAD. <br />
<br />
Records produced using the instructions of RDA are intended to be compatible with the large number of existing records created under the rules of AACR2.<br />
<br />
RDA is a content standard, not a display, database, or coding standard. It is designed to be used with many different schemas such as ISBD, MARC, and Dublin Core.<br />
<br />
=== RDA services ===<br />
MARS 2.0 RDA Services provide a variety of options that enhance your patron access by improving heading consistency within your catalog by bringing all MARC records under the same standard. Our Automation Services team can assist you in completing each step of your profile.<br />
<br />
An ongoing dialogue between you and our staff helps us better understand your needs and expectations as well as your specific system-related issues. Throughout your project, our staff is available to answer any questions, providing you with the highest quality and most cost-effective support possible.<br />
<br />
If your particular custom needs are not outlined in this guide, please contact your project manager for further options.<br />
<br />
=== 6 steps===<br />
Over the years, we have continually made improvements to our documentation in order to simplify the process of completing each type of profile. We hope that our guide still provides the in-depth details and examples that you are used to and manages to guide you along at an intuitive pace.<br />
<br />
To customize your RDA service, complete these '''6''' steps:<br />
<br />
*'''1. Data Information:''' Data exchange format specifications<br />
*'''2. Validation Options:''' Validation and updates<br />
*'''3. GMD to CMC:''' Convert GMD terms to Content, Media, and Carrier fields<br />
*'''4. Descriptive Fields:''' Add RDA elements, spell out abbreviations<br />
*'''5. Access Fields:''' Additional changes made to title and access fields<br />
*'''6. Reports:''' Format and layout options for reports<br />
<br />
=== Online profile support ===<br />
We think it is only natural that, as you look through this planning guide or fill out the profiles online, you may have questions. Each question in our online profile also contains a direct Wiki link that corresponds to this Wiki and the planning guide.<br />
<br />
In addition to online help, we are always available to answer any questions or concerns you may have about your profile options or processing results. In fact, we recommend filling out the online profile with our support once you and your staff have had a hand at selecting your desired options.<br />
<br />
In addition to the profile guide being freely available on our site online, our Automation Services staff is available by phone or email to answer any of your questions: '''800.288.1265 - info@bslw.com'''.<br />
<br />
=== ILS handling ===<br />
Typically, an Integrated Library System (ILS) has very specific criteria when it comes to exporting and importing the bibs or authorities from your library. Knowing which ILS your library uses helps us understand your needs and expectations.<br />
<br />
Your ILS may have a different methodology when it comes to importing vs exporting records. Contacting your ILS vendor will help clear these steps up. Since our RDA services can process bibliographic records in MARC 21 format from almost any source, it may be necessary to contact your ILS vendor regarding the best way to export the records in the proper format.<br />
<br />
Bibliographic records in your local ILS are often the only copies that contain all the updates, modifications and enhancements made over the years. Most<br />
systems have an export feature that can create files of bibliographic records in MARC format.<br />
<br />
Some ILS allow export by date or record number ranges, enabling a library to periodically send files of new and updated records for RDA processing.<br />
<br />
== Topics==<br />
* [[RDA_1.1|Step 1.1]] - Records Uploaded to Backstage<br />
* [[RDA_1.2|Step 1.2]] - Records Delivered by Backstage<br />
* [[RDA_1.3|Step 1.3]] - Records to Process<br />
* [[RDA_1.4|Step 1.4]] - Records to Deliver<br />
* [[RDA_1.5|Step 1.5]] - Backstage Change Stamp<br />
<br />
==link==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.0RDA 1.02013-04-02T18:24:01Z<p>Judy: /* RDA Planning Guide */</p>
<hr />
<div>== RDA Planning Guide ==<br />
The RDA Planning Guide from Backstage Library Works explains the range of options available through our RDA MARC record services. This includes the validation of existing RDA bibliographic records and enriching and upgrading AACR2 records with RDA elements.<br />
<br />
Please contact your Sales representative to request additional no-charge copies of this Guide: '''800.288.1265'''. The information contained within this guide should be shared with cataloging managers and system managers. You may also want to share it with your local system representatives.<br />
<br />
=== Overview ===<br />
Resource Description and Access (RDA) is a set of instructions or rules for the description of books and other materials or resources. RDA is intended to replace Anglo-American Cataloging Rules 2nd Edition (AACR2), the current US standard for cataloging.<br />
<br />
RDA is built on foundations established in AACR2, and the cataloging traditions on which they were based. A key difference in the RDA design is its use of the Functional Requirements for Bibliographic Records and Authority Data (FRBR and FRAD).<br />
<br />
RDA uses the language and terminology of FRBR and FRAD. The FRBR entities, attributes, and relationships are used for bibliographic description.<br />
<br />
=== RDA rules ===<br />
The RDA rules are organized to relate bibliographic description to the FRBR entities, attributes, and relationships. The first 4 sections of RDA cover elements corresponding to the entity attributes defined in FRBR and FRAD. <br />
<br />
Records produced using the instructions of RDA are intended to be compatible with the large number of existing records created under the rules of AACR2.<br />
<br />
RDA is a content standard, not a display, database, or coding standard. It is designed to be used with many different schemas such as ISBD, MARC, and Dublin Core.<br />
<br />
=== RDA services ===<br />
MARS 2.0 RDA Services provide a variety of options that enhance your patron access by improving heading consistency within your catalog by bringing all MARC records under the same standard. Our Automation Services team can assist you in completing each step of your profile.<br />
<br />
An ongoing dialogue between you and our staff helps us better understand your needs and expectations as well as your specific system-related issues. Throughout your project, our staff is available to answer any questions, providing you with the highest quality and most cost-effective support possible.<br />
<br />
If your particular custom needs are not outlined in this guide, please contact your project manager for further options.<br />
<br />
=== 6 steps===<br />
Over the years, we have continually made improvements to our documentation in order to simplify the process of completing each type of profile. We hope that our guide still provides the in-depth details and examples that you are used to and manages to guide you along at an intuitive pace.<br />
<br />
To customize your RDA service, complete these '''6''' steps:<br />
<br />
*'''1. Data Information:''' Data exchange format specifications<br />
*'''2. Validation Options:''' Validation and updates<br />
*'''3. GMD to CMC:''' Convert GMD terms to Content, Media, and Carrier fields<br />
*'''4. Descriptive Fields:''' Add RDA elements, spell out abbreviations<br />
*'''5. Access Fields:''' Additional changes made to title and access fields<br />
*'''6. Reports:''' Format and layout options for reports<br />
<br />
=== Online profile support ===<br />
We think it is only natural that, as you look through this planning guide or fill out the profiles online, you may have questions. Each question in our online profile also contains a direct Wiki link that corresponds to this Wiki and the planning guide.<br />
<br />
In addition to online help, we are always available to answer any questions or concerns you may have about your profile options or processing results. In fact, we recommend filling out the online profile with our support once you and your staff have had a hand at selecting your desired options.<br />
<br />
In addition to the profile guide being freely available on our site online, our Automation Services staff is available by phone or email to answer any of your questions: '''800.288.1265 - info@bslw.com'''.<br />
<br />
=== ILS handling ===<br />
Typically, an Integrated Library System (ILS) has very specific criteria when it comes to exporting and importing the bibs or authorities from your library. Knowing which ILS your library uses helps us understand your needs and expectations.<br />
<br />
Your ILS may have a different methodology when it comes to importing vs exporting records. Contacting your ILS vendor will help clear these steps up. Since our RDA services can process bibliographic records in MARC 21 format from almost any source, it may be necessary to contact your ILS vendor regarding the best way to export the records in the proper format.<br />
<br />
Bibliographic records in your local ILS are often the only copies that contain all the updates, modifications and enhancements made over the years. Most<br />
systems have an export feature that can create files of bibliographic records in MARC format.<br />
<br />
Some ILS allow export by date or record number ranges, enabling a library to periodically send files of new and updated records for RDA processing.<br />
<br />
== Topics==<br />
* [[RDA_1.1|Step 1.1]] - Records Uploaded to Backstage<br />
* [[RDA_1.2|Step 1.2]] - Records Delivered by Backstage<br />
* [[RDA_1.3|Step 1.3]] - Records to Process<br />
* [[RDA_1.4|Step 1.4]] - Records to Deliver<br />
* [[RDA_1.5|Step 1.5]] - Backstage Change Stamp<br />
<br />
==link==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judyhttps://ac.bslw.com/community/wiki/index.php/RDA_1.2RDA 1.22013-03-28T22:51:11Z<p>Judy: /* UTF-8 vs MARC-8 format */</p>
<hr />
<div>==RDA 1.2: Records Delivered by Backstage==<br />
[[Image:rda1-1.png]]<br><br><br />
===UTF-8 vs MARC-8 format===<br />
MARC-8 has been the standard format for MARC-21 records since 1968. Nearly every system that can export records in MARC format can do so in MARC-8 format. The MARC-8 character set uses 8-bit characters. Due to the limitation of<br />
characters that this allows, MARC-8 also includes methods to extend the<br />
displayable characters: spacing based characters (for cursor movement) and<br />
non-spacing characters (diacritics).<br />
<br />
MARC-8 also employs the use of alternate character sets in order to tackle the<br />
diacritic display issue. This is done by using escape sequences, which are special<br />
codes to indicate which character set is being selected for display: subscripts,<br />
superscripts, CJK characters, etc.<br />
<br />
While these methods allow for many additional characters to be used, it is still<br />
limited and somewhat burdensome. For example, built into the MARC-21 format is a limitation that no record can exceed 99,999 characters, and no field can exceed 9,999 characters. If a record exceeds the field or record size limits, there may be truncation or loss of data.<br />
<br />
UTF-8 has been in use since early 1993, and is a standard based on 16-bit characters. The main difference between MARC-8 and UTF-8 is that UTF-8 allows for more character types to be used within the records. Since UTF-8 can represent many more characters than MARC-8, the files tend to be larger in size. Each character in UTF-8 is between 1 - 4 bytes (whereas MARC-8 is only 1 byte in length).<br />
<br />
If your system uses UTF-8, please also let us know whether the characters are in precomposed or decomposed format. Precomposed characters use combined diacritics (e.g., n & ~ are combined to form: ñ). Decomposed format separates the characters.<br />
<br />
Additionally, to handle the various ways a composite character could be displayed,<br />
normalization forms have been defined. Normalization Form Decomposed (NFD) and Normalization Form Composed<br />
(NFC) are standardized forms for handling composite characters. In NFD, every character that can be decomposed is converted to its most<br />
decomposed form following rules for canonical decomposition. In NFC, the characters are first decomposed as in NFD, then composed into<br />
precomposed (composite) forms following canonical rules. This may result in<br />
the sequence of characters for a given character changing into an alternate,<br />
equivalent form.<br />
<br />
==Default==<br />
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"<br />
|- style="background:#CCFFFF; font-size: 110%;"<br />
| Files are delivered in UTF-8 format through the website.<br />
|}<br />
<div style=clear:both></div><br><br />
<br />
==links==<br />
<center><font size="4">[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]<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>Judy