Difference between revisions of "RDA 4.3"

From AC Wiki
Jump to: navigation, search
(links)
 
(27 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
==RDA 4.3 : 260 field (Imprints)==
 
==RDA 4.3 : 260 field (Imprints)==
 +
[[image:rda4-3.png]]
 +
===Bracketed imprint information===
 +
In AACR2, all information taken from outside the resource was put under the same set of brackets. Due to a change in ISBD, each element taken from outside the resource should be in its own set of brackets.  MARS 2.0 will separate subfields contained in a single set of brackets into separate brackets around each subfield. [http://access.rdatoolkit.org/document.php?id=rdaappd&target=rdad-2628# RDA D.1.2.1] (html)
 +
  <font size="3">
 +
  (a) original field:
 +
    260 $a <font color="red">[</font>New York :$b Macmillan, $c 1973<font color="red">]</font>
 +
  updated field:
 +
    260 $a <font color="red">[</font>New York<font color="red">]</font> :$b <font color="red">[</font>Macmillan<font color="red">]</font>, $c <font color="red">[</font>1973<font color="red">]</font></font>
  
===Imprint abbreviations===
+
==Default==
Several abbreviations in the imprint field (260) in AACR2 are not valid with RDA.
+
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
Here are several options for expanding these imprint abbreviations.
+
|- style="background:#CCFFFF; font-size: 110%;"
 +
| Expand all abbreviations & make all updates in 260 field.
 +
|}
 +
<div style=clear:both></div><br>
  
 
===Latin abbreviations===
 
===Latin abbreviations===
AACR2 used latin abbreviations for the 260 $a and 260 $b when either the place
+
AACR2 used the Latin abbreviations '''S.l.''', '''s.n.''', '''n.d.''' in the 260 $a, $b, $c, $e, $f, $g when the place
of publication or publisher name were not available. With RDA, new phrases
+
of publication, publisher name, or dates were not available. With RDA, new phrases have replaced these Latin abbreviations.
have replaced these Latin abbreviations.
+
 
 +
*[S.l.] in $a is replaced with [Place of publication not identified] [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-6377# RDA 2.8.2.6] (html)
 +
*S.l. in $e is replaced with [Place of manufacture not identified] [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-7294# RDA 2.10.2.6] (html)
 +
*s.n. in $b is replaced with [publisher not identified] [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-6648# RDA 2.8.4.7] (html)
 +
*s.n. in $f is replaced with [manufacturer not identified] [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-7462# RDA 2.10.4.7] (html)
 +
*n.d. (rarely used) in $c is replaced with [date of publication not identified] [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-6792# RDA 2.8.6.6] (html)
 +
*n.d. (rarely used) in $g is replaced with [date of manufacture not identified] [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-7524# RDA 2.10.6.6] (html)
  
 
   <font size="3">
 
   <font size="3">
Line 18: Line 35:
 
   </font>
 
   </font>
  
===Month names===
+
===Create 500 from 260 i.e.===
With RDA, names of months of the year are not to be abbreviated in the 260.
+
Sometimes an '''i.e.''' note is included in 260 $a. MARS 2.0 can move this information to a separate 500 field, if desired:
This rule uses the same month abbreviation table as is used for the X00/X10/
+
X11/X30 fields (see Step 4.2):
+
  
 
   <font size="3">
 
   <font size="3">
 
   '''original field''':
 
   '''original field''':
     260 $a Paris : $b Le Robert, $c <font color="red">Jan.</font> 2010.
+
     260 $a Garden City, N. York <font color="red">[i.e. New York]</font> :$b Doubleday, $c 1979.
 
    
 
    
   '''updated field''':
+
   '''updated fields''':
     260 $a Paris : $b Le Robert, $c <font color="red">January</font> 2010.
+
     260 $a Garden City, New York :$b Doubleday, $c 1979.
 +
    500 $a Published in New York.
 
   </font>
 
   </font>
  
===Geographic names===
+
Please note that '''New York''' in 260 $a is spelled out also as part of Step 4.3, but the '''i.e.''' part is what ends up in the 500 field as a '''Published in''' note.
Geographic place names (e.g. states, countries, etc.) should no longer be
+
 
abbreviated. MARS 2.0 uses a list of many different geographic terms and their
+
===Abbreviations expanded===
common abbreviations which will be expanded:
+
RDA uses standard abbreviations for most places such as states, countries, etc. Place names that don’t have a standard RDA abbreviation will be spelled out in the 260 $a and $e. Also abbreviations such as Dept. and Co. that may be found in the 260 $b and $f can be spelled out.  If you choose to have these changes made, be aware that it is ‘all or nothing’.  The system cannot determine if the abbreviation was that way on the resource. [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-6406# RDA 2.8.1.4] (html)
  
 
   <font size="3">
 
   <font size="3">
 
   '''original field''':
 
   '''original field''':
     260 $a Hoboken, <font color="red">N.J.</font> : $b Wiley, $c 2009.
+
     260 $a <font color="red">Am. Samoa</font> : $b <font color="red">Dept. of Safety</font>, $c 1987.
 
    
 
    
 
   '''updated field''':
 
   '''updated field''':
     260 $a Hoboken, <font color="red">New Jersey</font> : $b Wiley, $c 2009.
+
     260 $a <font color="red">American Samoa</font> : $b <font color="red">Department of Safety</font>, $c 1987.
 
   </font>
 
   </font>
  
===Department===
+
===Dates===
As with the X10/X11 fields, dept. should no longer be abbreviated in the 260
+
There are many changes in the way dates are recorded from AACR2 to RDA. The following are changes that can be applied by machine to the 260 $c. These changes are explained below.
field; it is to be expanded to department. The Library of Congress is currently
+
keeping department as an abbreviation:
+
With RDA, names of months of the year are not to be abbreviated in the 260. [http://access.rdatoolkit.org/document.php?id=rdaappb&target=rdab-95# RDA B.5.11] (html)  This change uses the same month abbreviation table as is used for changing access fields (see Step 5.2)
  
 
   <font size="3">
 
   <font size="3">
 
   '''original field''':
 
   '''original field''':
     260 $a Raleigh : $b State <font color="red">Dept.</font> of Archives and History, $c 1954.
+
     260 $a Paris : $b Le Robert, $c <font color="red">Jan. 2010</font>.
 
    
 
    
 
   '''updated field''':
 
   '''updated field''':
     260 $a Raleigh : $b State <font color="red">Department</font> of Archives and History, $c 1954.
+
     260 $a Paris : $b Le Robert, $c <font color="red">January 2010</font>.
 
   </font>
 
   </font>
  
===ca.===
+
In the 260 $c and $g, '''ca.''' is no longer used to represent '''circa''' or '''approximately'''. Instead, a question mark ? should be added after the date: [http://access.rdatoolkit.org/rdachp1_rda1-1072.html RDA 1.9.2.3] (html)
In the 260 $c and $g, ca. is no longer used to represent circa or approximately.
+
Instead, a question mark ? should be added after the date:
+
  
 
   <font size="3">
 
   <font size="3">
 
   '''original field''':
 
   '''original field''':
     260 $a London : $b O. Hodgson, $c <font color="red">[ca. 1830]</font>
+
     260 $a London : $b O.Hodgson, $c <font color="red">[ca. 1830]</font>
 
    
 
    
 
   '''updated field''':
 
   '''updated field''':
     260 $a London : $b O. Hodgson, $c <font color="red">[1830?]</font>
+
     260 $a London : $b O.Hodgson, $c <font color="red">[1830?]</font>
 
   </font>
 
   </font>
  
===Dashes representing unknown numbers===
+
Printing or pressing dates can be used to supply a publishing date and enclosed within square brackets. [http://access.rdatoolkit.org/document.php?id=lcpschp2&target=lcps2-1702#lcps2-1702 LC-PCC PS for 2.10.6] (html)
With AACR2, a dash could be used to represent an unknown number within a
+
date. In using RDA, the dash is no longer used. A range of dates encompassing
+
the unknown number should now be used.
+
 
+
If there is a question mark included in the date, the question mark should
+
remain at the end of the date range:
+
  
 
   <font size="3">
 
   <font size="3">
   '''original fields''':
+
   '''original field''':
     260 $a New York : $b A. E. Chasmar, $c <font color="red">[188-]</font>
+
     260 __ $a New York : $b Knopf, $c <font color="red">2010 printing</font>.
    260 $a London : $b J.T. Pickburn, $c <font color="red">[18--?]</font>
+
 
    
 
    
   '''updated fields''':
+
   '''updated field''':
     260 $a New York : $b A. E. Chasmar, $c <font color="red">[between 1880 and 1889]</font>
+
     <font color="red">264 _3</font> $a New York : $b Knopf, $c <font color="red">[2010]</font>
    260 $a London : $b J.T. Pickburn, $c <font color="red">[between 1800 and 1899?]</font>
+
 
   </font>
 
   </font>
  
===Printing/pressing/copyright/phonogram===
+
Note that '''printing''' can also be useful if converting the 260 to 264 field(s).
Printing or pressing dates should now be enclosed within square brackets with a
+
question mark at the end of the date.
+
  
When either a c or p is the character right before a date, they should be changed
+
With AACR2, a dash could be used to represent an unknown number within a date. In using RDA, the dash is no longer used. A range of dates encompassing the unknown number should now be used.  If there is a question mark included in the date, the question mark should remain at the end of the date range. [http://access.rdatoolkit.org/rdachp1_rda1-1078.html RDA 1.9.2.4] (html) The following types would be changed in 260 $c:
for either the copyright symbol © or phonogram symbol ℗.
+
*Decade is certain:  [197-] becomes [between 1970 and 1979]
 +
*Probable decade:  [197-?] becomes [between 1970 and 1979?]
 +
*Century certain:  [18--]  becomes [between 1800 and 1899]
 +
*Probable century:  [18--?]  becomes [between 1800 and 1899?]
 +
 +
When either a c or p is the character right before a date, they should be changed for either the copyright symbol © or phonogram symbol ℗. The words ‘copyright’ and ‘phonogram’ should also be changed to the appropriate symbol. [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-7611# RDA 2.11.1.3] (html)
  
If only a copyright date is included, RDA dictates that [place of publication not
+
  <font size="3">
identified] should be added:
+
  '''original field''':
 +
    260 $a Berlin : $b Gerschel, $c <font color="red">c1964</font>.
 +
 
 +
  '''updated field''':
 +
    260 $a Berlin : $b Gerschel, $c <font color="red">©1964</font>.
 +
 
 +
  '''original field''':
 +
    260 $a New York : $b Anchor Books, $c <font color="red">p2001</font>.
 +
 
 +
  '''updated field''':
 +
    260 $a New York : $b Anchor Books, $c <font color="red">Ⓟ2001</font>.
 +
  </font>
 +
 +
As explained above, the copyright or phonogram date can be used to supply a publishing date when missing. [http://access.rdatoolkit.org/document.php?id=lcpschp2&target=lcps2-1467# LC PCC PS for 2.8.6.6] (html)
 +
 
 +
===Missing publication date===
 +
PCC/LC policy is to try to supply a date of publication if at all possible rather than use the phrase ‘date of publication not identified’ [http://access.rdatoolkit.org/document.php?id=lcpschp2&target=lcps2-1467# LC PCC PS for 2.8.6.6] (html).  If the publication date is not available and a copyright date, or phonogram date is available, we can use these dates to supply a probable publication date.  Or if preferred, we can include the phrase [date of publication not identified]  
  
 
   <font size="3">
 
   <font size="3">
   '''original fields''':
+
   '''original field''':
     260 $a New York : $b Alfred A. Knopf, $c <font color="red">2010 printing.</font>
+
     260 $a London : $b Collins, $c <font color="red">c1965</font>.
    260 $a Berlin : $b Louis Gerschel, $c <font color="red">c1964.</font>
+
    260 $a New York : $b Anchor Books, $c <font color="red">p2001.</font>
+
 
    
 
    
   '''updated fields''':
+
   '''updated field''':
     260 $a New York : $b Alfred A. Knopf, $c <font color="red">[2010?]</font>
+
     260 $a London : $b Collins, $c <font color="red">[1965], c1965</font>.
    260 $a Berlin : $b Louis Gerschel, $c <font color="red">[date of publication not identified], ©1964.</font>
+
    260 $a New York : $b Anchor Books, $c <font color="red">℗2001.</font>
+
 
   </font>
 
   </font>
  
 
==links==
 
==links==
<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]]
+
<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]] - [[RDA_4.8|4.8]]
 
<hr>
 
<hr>
 
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]]</font></center>
 
[[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>
 
[[category:RDA Profile Guide]]
 
[[category:RDA Profile Guide]]

Latest revision as of 09:37, 27 July 2017

RDA 4.3 : 260 field (Imprints)

Rda4-3.png

Bracketed imprint information

In AACR2, all information taken from outside the resource was put under the same set of brackets. Due to a change in ISBD, each element taken from outside the resource should be in its own set of brackets. MARS 2.0 will separate subfields contained in a single set of brackets into separate brackets around each subfield. RDA D.1.2.1 (html)

 
 (a) original field:
   260 $a [New York :$b Macmillan, $c 1973]
 updated field:
   260 $a [New York] :$b [Macmillan], $c [1973]

Default

Expand all abbreviations & make all updates in 260 field.

Latin abbreviations

AACR2 used the Latin abbreviations S.l., s.n., n.d. in the 260 $a, $b, $c, $e, $f, $g when the place of publication, publisher name, or dates were not available. With RDA, new phrases have replaced these Latin abbreviations.

  • [S.l.] in $a is replaced with [Place of publication not identified] RDA 2.8.2.6 (html)
  • S.l. in $e is replaced with [Place of manufacture not identified] RDA 2.10.2.6 (html)
  • s.n. in $b is replaced with [publisher not identified] RDA 2.8.4.7 (html)
  • s.n. in $f is replaced with [manufacturer not identified] RDA 2.10.4.7 (html)
  • n.d. (rarely used) in $c is replaced with [date of publication not identified] RDA 2.8.6.6 (html)
  • n.d. (rarely used) in $g is replaced with [date of manufacture not identified] RDA 2.10.6.6 (html)
 
 original field:
    260 $a [S.l. : $b s.n.], $c 1963.
  
 updated field:
    260 $a [Place of publication not identified] : $b [publisher not identified], $c 1963.
 

Create 500 from 260 i.e.

Sometimes an i.e. note is included in 260 $a. MARS 2.0 can move this information to a separate 500 field, if desired:

 
 original field:
    260 $a Garden City, N. York [i.e. New York] :$b Doubleday, $c 1979.
  
 updated fields:
    260 $a Garden City, New York :$b Doubleday, $c 1979.
    500 $a Published in New York.
 

Please note that New York in 260 $a is spelled out also as part of Step 4.3, but the i.e. part is what ends up in the 500 field as a Published in note.

Abbreviations expanded

RDA uses standard abbreviations for most places such as states, countries, etc. Place names that don’t have a standard RDA abbreviation will be spelled out in the 260 $a and $e. Also abbreviations such as Dept. and Co. that may be found in the 260 $b and $f can be spelled out. If you choose to have these changes made, be aware that it is ‘all or nothing’. The system cannot determine if the abbreviation was that way on the resource. RDA 2.8.1.4 (html)

 
 original field:
    260 $a Am. Samoa : $b Dept. of Safety, $c 1987.
  
 updated field:
    260 $a American Samoa : $b Department of Safety, $c 1987.
 

Dates

There are many changes in the way dates are recorded from AACR2 to RDA. The following are changes that can be applied by machine to the 260 $c. These changes are explained below.

With RDA, names of months of the year are not to be abbreviated in the 260. RDA B.5.11 (html) This change uses the same month abbreviation table as is used for changing access fields (see Step 5.2)

 
 original field:
    260 $a Paris : $b Le Robert, $c Jan. 2010.
  
 updated field:
    260 $a Paris : $b Le Robert, $c January 2010.
 

In the 260 $c and $g, ca. is no longer used to represent circa or approximately. Instead, a question mark ? should be added after the date: RDA 1.9.2.3 (html)

 
 original field:
    260 $a London : $b O.Hodgson, $c [ca. 1830]
  
 updated field:
    260 $a London : $b O.Hodgson, $c [1830?]
 

Printing or pressing dates can be used to supply a publishing date and enclosed within square brackets. LC-PCC PS for 2.10.6 (html)

 
 original field:
    260 __ $a New York : $b Knopf, $c 2010 printing.
  
 updated field:
    264 _3 $a New York : $b Knopf, $c [2010]
 

Note that printing can also be useful if converting the 260 to 264 field(s).

With AACR2, a dash could be used to represent an unknown number within a date. In using RDA, the dash is no longer used. A range of dates encompassing the unknown number should now be used. If there is a question mark included in the date, the question mark should remain at the end of the date range. RDA 1.9.2.4 (html) The following types would be changed in 260 $c:

  • Decade is certain: [197-] becomes [between 1970 and 1979]
  • Probable decade: [197-?] becomes [between 1970 and 1979?]
  • Century certain: [18--] becomes [between 1800 and 1899]
  • Probable century: [18--?] becomes [between 1800 and 1899?]

When either a c or p is the character right before a date, they should be changed for either the copyright symbol © or phonogram symbol ℗. The words ‘copyright’ and ‘phonogram’ should also be changed to the appropriate symbol. RDA 2.11.1.3 (html)

 
 original field:
    260 $a Berlin : $b Gerschel, $c c1964.
  
 updated field:
    260 $a Berlin : $b Gerschel, $c ©1964.
 original field:
    260 $a New York : $b Anchor Books, $c p2001.
  
 updated field:
    260 $a New York : $b Anchor Books, $c Ⓟ2001.
 

As explained above, the copyright or phonogram date can be used to supply a publishing date when missing. LC PCC PS for 2.8.6.6 (html)

Missing publication date

PCC/LC policy is to try to supply a date of publication if at all possible rather than use the phrase ‘date of publication not identified’ LC PCC PS for 2.8.6.6 (html). If the publication date is not available and a copyright date, or phonogram date is available, we can use these dates to supply a probable publication date. Or if preferred, we can include the phrase [date of publication not identified]

 
 original field:
    260 $a London : $b Collins, $c c1965.
  
 updated field:
    260 $a London : $b Collins, $c [1965], c1965.
 

links

4.1 - 4.2 - 4.3 - 4.4 - 4.5 - 4.6 - 4.7 - 4.8
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0