Difference between revisions of "RDA 4.2"

From AC Wiki
Jump to: navigation, search
(Created page with "==STEP 4.2 : X== ==LINKS== <center><font size="4">4.1 - 4.2 - 4.3 - 4.4 - 4.5 - 4.6 <hr> 1.0...")
 
(STEP 4.2 : X)
Line 1: Line 1:
==STEP 4.2 : X==
+
==STEP 4.2 : DATE ABBREVIATIONS==
  
 +
===date abbreviations===
 +
There are many different abbreviations in $d (i.e., date) of 1XX, 6XX, 7XX, and
 +
8XX fields that can be expanded. The majority of these date changes only take
 +
place within X00 fields. The main exception is expanding month names in X10,
 +
X11, and X30 fields.
 +
 +
===birth date===
 +
RDA rules say that there are two possibilities for when the abbreviation b. has
 +
been used in a date. The first option is to remove b. and add a hyphen after the
 +
birth date. The other option is that b. can change to born. Current LC policy is to
 +
add the hyphen after the birth date:
 +
 +
  <font size="3">
 +
  '''original field''':
 +
    100 1_ $a Mort, Paul R., $d <font color="red">b. 1894.</font>
 +
 
 +
  '''updated field''':
 +
    100 1_ $a Mort, Paul R., $d <font color="red">1894-</font>  ''LC policy
 +
        OR
 +
    100 1_ $a Mort, Paul R., $d <font color="red">born 1894.</font>
 +
  </font>
 +
 +
===death date===
 +
As with the birth date, there are also two options for expanding the abbreviation
 +
for a death date. When a d. is encountered, a hyphen can be added before the
 +
death date with the d. being removed or else d. can be changed to died. Current
 +
LC policy is to add the hyphen before the date:
 +
 +
  <font size="3">
 +
  '''original field''':
 +
    100 1_ $a Lewis, Georgina King, $d <font color="red">d. 1924.</font>
 +
 
 +
  '''updated field''':
 +
    100 1_ $a Lewis, Georgina King, $d <font color="red">-1924.</font>  ''LC policy
 +
        OR
 +
    100 1_ $a Lewis, Georgina King, $d <font color="red">died 1924.</font>
 +
  </font>
 +
 +
===flourished => active===
 +
There are two different ways that fl. or flourished can be changed using RDA
 +
guidelines. The first way is to change these to active in the same position of the
 +
$d (typically right before the date). The other way to handle this is to expand fl.
 +
to flourished. Current LC policy is to change these to active:
 +
 +
  <font size="3">
 +
  '''original field''':
 +
    100 1_ $a Brown, John, $d <font color="red">fl.</font> 1854.
 +
 
 +
  '''updated field''':
 +
    100 1_ $a Brown, John, $d <font color="red">active</font> 1854.  ''LC policy
 +
        OR
 +
    100 1_ $a Brown, John, $d <font color="red">flourished</font> 1854.
 +
  </font>
 +
 +
===month names===
 +
In AACR2, month names were generally abbreviated. In RDA, month names
 +
should be expanded. The following table shows the changes that will be made
 +
with month names.
 +
 +
{| border="1" cellspacing="0" cellpadding="5" align="left"
 +
! style="background:silver" | Abbreviated
 +
! style="background:silver" | Expanded
 +
|-
 +
| Jan. || January
 +
|-
 +
| Feb. || February
 +
|-
 +
| Mar. || March
 +
|-
 +
| Apr. || April
 +
|-
 +
| Jun. || June
 +
|-
 +
| Jul. || July
 +
|-
 +
| Aug. || August
 +
|-
 +
| Sep. || September
 +
|-
 +
| Sept. || September
 +
|-
 +
| Oct. || October
 +
|-
 +
| Nov. || November
 +
|-
 +
| Dec. || December
 +
|}
 +
<div style=clear:both></div>
 +
 +
  <font size="3">
 +
  '''original fields''':
 +
    100 1_ $a Einhorn, Richard, $d 1952 <font color="red">Aug.</font> 2-
 +
    730 _0 $a Geneva Conventions $d (1949). $k Protocols, etc., $d 2005 <font color="red">Dec.</font> 8.
 +
 
 +
  '''updated fields:
 +
    100 1_ $a Einhorn, Richard, $d 1952 <font color="red">August</font> 2-
 +
    730 _0 $a Geneva Conventions $d (1949). $k Protocols, etc., $d 2005 <font color="red">December</font> 8.
 +
  </font>
 +
 +
===other date abbreviations===
 +
A few additional abbreviations that can be expanded in date subfields include the following:
 +
 +
{| border="1" cellspacing="0" cellpadding="5" align="left"
 +
! style="background:silver" | Abbreviated
 +
! style="background:silver" | Expanded
 +
|-
 +
| ca. || approximately
 +
|-
 +
| cent. || century
 +
|-
 +
| cen. || century
 +
|}
 +
<div style=clear:both></div>
 +
 +
  <font size="3">
 +
  '''original fields''':
 +
    100 1_ $a Fenton, Geoffrey, $d <font color="red">ca.</font> 1539-1608.
 +
    600 10 $a Seghers, Hercules, $d 17th <font color="red">cent.</font>
 +
    700 0_ $a Raol, $d 12th <font color="red">cen.</font>
 +
 
 +
  '''updated fields:
 +
    100 1_ $a Fenton, Geoffrey, $d <font color="red">approximately</font> 1539-1608.
 +
    600 10 $a Seghers, Hercules, $d 17th <font color="red">century.</font>
 +
    700 0_ $a Raol, $d 12th <font color="red">century.</font>
 +
  </font>
  
 
==LINKS==
 
==LINKS==

Revision as of 11:43, 5 January 2012

STEP 4.2 : DATE ABBREVIATIONS

date abbreviations

There are many different abbreviations in $d (i.e., date) of 1XX, 6XX, 7XX, and 8XX fields that can be expanded. The majority of these date changes only take place within X00 fields. The main exception is expanding month names in X10, X11, and X30 fields.

birth date

RDA rules say that there are two possibilities for when the abbreviation b. has been used in a date. The first option is to remove b. and add a hyphen after the birth date. The other option is that b. can change to born. Current LC policy is to add the hyphen after the birth date:

 
 original field:
    100 1_ $a Mort, Paul R., $d b. 1894.
  
 updated field:
    100 1_ $a Mort, Paul R., $d 1894-   LC policy
       OR
    100 1_ $a Mort, Paul R., $d born 1894.
 

death date

As with the birth date, there are also two options for expanding the abbreviation for a death date. When a d. is encountered, a hyphen can be added before the death date with the d. being removed or else d. can be changed to died. Current LC policy is to add the hyphen before the date:

 
 original field:
    100 1_ $a Lewis, Georgina King, $d d. 1924.
  
 updated field:
    100 1_ $a Lewis, Georgina King, $d -1924.   LC policy
       OR
    100 1_ $a Lewis, Georgina King, $d died 1924.
 

flourished => active

There are two different ways that fl. or flourished can be changed using RDA guidelines. The first way is to change these to active in the same position of the $d (typically right before the date). The other way to handle this is to expand fl. to flourished. Current LC policy is to change these to active:

 
 original field:
    100 1_ $a Brown, John, $d fl. 1854.
  
 updated field:
    100 1_ $a Brown, John, $d active 1854.   LC policy
       OR
    100 1_ $a Brown, John, $d flourished 1854.
 

month names

In AACR2, month names were generally abbreviated. In RDA, month names should be expanded. The following table shows the changes that will be made with month names.

Abbreviated Expanded
Jan. January
Feb. February
Mar. March
Apr. April
Jun. June
Jul. July
Aug. August
Sep. September
Sept. September
Oct. October
Nov. November
Dec. December
 
 original fields:
    100 1_ $a Einhorn, Richard, $d 1952 Aug. 2-
    730 _0 $a Geneva Conventions $d (1949). $k Protocols, etc., $d 2005 Dec. 8.
  
 updated fields:
    100 1_ $a Einhorn, Richard, $d 1952 August 2-
    730 _0 $a Geneva Conventions $d (1949). $k Protocols, etc., $d 2005 December 8.
 

other date abbreviations

A few additional abbreviations that can be expanded in date subfields include the following:

Abbreviated Expanded
ca. approximately
cent. century
cen. century
 
 original fields:
    100 1_ $a Fenton, Geoffrey, $d ca. 1539-1608.
    600 10 $a Seghers, Hercules, $d 17th cent.
    700 0_ $a Raol, $d 12th cen.
  
 updated fields:
    100 1_ $a Fenton, Geoffrey, $d approximately 1539-1608.
    600 10 $a Seghers, Hercules, $d 17th century.
    700 0_ $a Raol, $d 12th century.
 

LINKS

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