Difference between revisions of "RDA 4.4"

From AC Wiki
Jump to: navigation, search
(LINKS)
Line 1: Line 1:
==STEP 4.4 : IMPRINT ABBREVIATIONS==
+
==RDA 4.4: Convert 260 to 264==
[[File:RDA_4.4.jpg]]
+
{| border="0" cellpadding="5" cellspacing="0" align="left"
===imprint abbreviations===
+
|-
Several abbreviations in the imprint field (260) in AACR2 are not valid with RDA.
+
|- align="left" style="background: white"
Here are several options for expanding these imprint abbreviations.
+
| || style="background: #CCFFFF;" | ☐ Yes ||
 +
|-
 +
| ||     ☐ With these modifications ||
 +
|-
 +
|}
 +
<div style=clear:both></div><br>
 +
===260 to 264 conversion===
 +
As there may not always be an easily identifiable way to distinguish between a publisher and distributor in 260 fields, this proposed conversion from 260 to 264 may not be completely reliable.
  
===latin abbreviations===
+
Still, as an attempt to transition 260 fields to 264 fields, this potential solution may be worth exploring on your part. Our recommendation is to follow through with this in sampling and then decide whether to keep it in your full processing.
AACR2 used latin abbreviations for the 260 $a and 260 $b when either the place
+
of publication or publisher name were not available. With RDA, new phrases
+
have replaced these Latin abbreviations.
+
  
  <font size="3">
+
==links==
  '''original field''':
+
<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]]
    260 $a <font color="red">[S.l. : $b s.n.]</font>, $c 1963.
+
 
+
  '''updated field''':
+
    260 $a <font color="red">[Place of publication not identified] : $b [publisher not identified]</font>, $c 1963.
+
  </font>
+
 
+
===month names===
+
With RDA, names of months of the year are not to be abbreviated in the 260.
+
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">
+
  '''original field''':
+
    260 $a Paris : $b Le Robert, $c <font color="red">Jan.</font> 2010.
+
 
+
  '''updated field''':
+
    260 $a Paris : $b Le Robert, $c <font color="red">January</font> 2010.
+
  </font>
+
 
+
===geographic names===
+
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
+
common abbreviations which will be expanded:
+
 
+
  <font size="3">
+
  '''original field''':
+
    260 $a Hoboken, <font color="red">N.J.</font> : $b Wiley, $c 2009.
+
 
+
  '''updated field''':
+
    260 $a Hoboken, <font color="red">New Jersey</font> : $b Wiley, $c 2009.
+
  </font>
+
 
+
===department===
+
As with the X10/X11 fields, dept. should no longer be abbreviated in the 260
+
field; it is to be expanded to department. The Library of Congress is currently
+
keeping department as an abbreviation:
+
 
+
  <font size="3">
+
  '''original field''':
+
    260 $a Raleigh : $b State <font color="red">Dept.</font> of Archives and History, $c 1954.
+
 
+
  '''updated field''':
+
    260 $a Raleigh : $b State <font color="red">Department</font> of Archives and History, $c 1954.
+
  </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:
+
 
+
  <font size="3">
+
  '''original field''':
+
    260 $a London : $b O. Hodgson, $c <font color="red">[ca. 1830]</font>
+
 
+
  '''updated field''':
+
    260 $a London : $b O. Hodgson, $c <font color="red">[1830?]</font>
+
  </font>
+
 
+
===dashes representing unknown numbers===
+
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">
+
  '''original fields''':
+
    260 $a New York : $b A. E. Chasmar, $c <font color="red">[188-]</font>
+
    260 $a London : $b J.T. Pickburn, $c <font color="red">[18--?]</font>
+
 
+
  '''updated fields''':
+
    260 $a New York : $b A. E. Chasmar, $c <font color="red">[between 1880 and 1889]</font>
+
    260 $a London : $b J.T. Pickburn, $c <font color="red">[between 1800 and 1899?]</font>
+
  </font>
+
 
+
===printing/pressing/copyright/phonogram===
+
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
+
for either the copyright symbol © or phonogram symbol ℗.
+
 
+
If only a copyright date is included, RDA dictates that [place of publication not
+
identified] should be added:
+
 
+
  <font size="3">
+
  '''original fields''':
+
    260 $a New York : $b Alfred A. Knopf, $c <font color="red">2010 printing.</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''':
+
    260 $a New York : $b Alfred A. Knopf, $c <font color="red">[2010?]</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>
+
 
+
==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]] - [[RDA_4.6|4.6]]
+
 
<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]]

Revision as of 08:24, 14 March 2013

RDA 4.4: Convert 260 to 264

☐ Yes
    ☐ With these modifications

260 to 264 conversion

As there may not always be an easily identifiable way to distinguish between a publisher and distributor in 260 fields, this proposed conversion from 260 to 264 may not be completely reliable.

Still, as an attempt to transition 260 fields to 264 fields, this potential solution may be worth exploring on your part. Our recommendation is to follow through with this in sampling and then decide whether to keep it in your full processing.

links

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