RDA 5.2 - Revision history

Nate: /* Flourished > active */

2014-04-04T19:13:37Z

‎Flourished > active

Karen: /* Birth date */

2014-03-19T00:15:59Z

‎Birth date

Nate at 21:40, 20 February 2014

2014-02-20T21:40:16Z

Nate: /* RDA 5.2: Date Abbreviations */

2014-02-20T21:36:43Z

‎RDA 5.2: Date Abbreviations

Karen: /* Other date abbreviations */

2014-01-22T23:59:31Z

‎Other date abbreviations

Karen: /* Month names */

2014-01-22T23:58:25Z

‎Month names

Karen: /* Flourished > active */

2014-01-22T23:57:13Z

‎Flourished > active

Karen: /* Death date */

2014-01-22T23:56:25Z

‎Death date

Karen: /* Birth date */

2014-01-22T23:55:38Z

‎Birth date

Karen: /* Date abbreviations */

2014-01-22T23:44:03Z

‎Date abbreviations

@@ Line 38: / Line 38: @@
 ===Flourished > active===
-There are two different ways that fl. or flourished can be changed using RDA
+The abbreviation '''fl.''' can be expanded to two different terms - '''flourished''' and '''active'''. While both are valid under RDA guidelines, LC/PCC policy is to use '''active'''. We will follow LC policy and change '''fl.''' to '''active''' in dates. Please see your Backstage project manager if you would like to use '''flourished''' instead.
-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'''. Similar to above, we have backed away from offering this last option to clients, unless they specifically request it.
-Current LC policy is to change these to active: [http://access.rdatoolkit.org/document.php?id=lcpschp9&target=lcps9-117# LC-PCC PS for 9.3.4.3] (html)
+Current LC policy is to change these to '''active''': [http://access.rdatoolkit.org/document.php?id=lcpschp9&target=lcps9-117# LC-PCC PS for 9.3.4.3] (html)
    <font size="3">

@@ Line 10: / Line 10: @@
 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'''. We have backed away from offering this last option as it contradicts LC policy and it poses a very probable risk that the heading would not find a match against LC authorities since LC does not use '''born''' as part of the heading.
+birth date. The other option is that '''b.''' can change to '''born'''. We have backed away from offering this last option as it contradicts LC policy and it poses a very probable risk that the heading would not find a match against LC authorities since LC does not use '''born''' as part of the heading. Please see your project manager if you would like to have the b. spelled out rather than use the hyphen.
 Current LC policy is to add the hyphen after the birth date: [http://access.rdatoolkit.org/document.php?id=lcpschp9&target=lcps9-110# LC-PCC PS for 9.3.2.3] (html)

@@ Line 10: / Line 10: @@
 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
+birth date. The other option is that '''b.''' can change to '''born'''. We have backed away from offering this last option as it contradicts LC policy and it poses a very probable risk that the heading would not find a match against LC authorities since LC does not use '''born''' as part of the heading.
 add the hyphen after the birth date: [http://access.rdatoolkit.org/document.php?id=lcpschp9&target=lcps9-110# LC-PCC PS for 9.3.2.3] (html)
    <font size="3">
@@ Line 19: / Line 20: @@
    '''updated field''':
 1  $a Mort, Paul R., $d <font color="red">1894-</font>               ''LC policy
    </font>
@@ Line 26: / Line 25: @@
 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
+death date with the d. being removed or else '''d.''' can be changed to '''died'''. Similar to above, we have backed away from offering this last option to clients, unless they specifically request it.
 LC policy is to add the hyphen before the date: [http://access.rdatoolkit.org/document.php?id=lcpschp9&target=lcps9-110# LC-PCC PS for 9.3.3.3] (html)
    <font size="3">
@@ Line 35: / Line 35: @@
    '''updated field''':
 1  $a Lewis, Georgina King, $d <font color="red">-1924.</font>       ''LC policy
    </font>
@@ Line 42: / Line 40: @@
 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.
+$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: [http://access.rdatoolkit.org/document.php?id=lcpschp9&target=lcps9-117# LC-PCC PS for 9.3.4.3] (html)
+to '''flourished'''. Similar to above, we have backed away from offering this last option to clients, unless they specifically request it.
    <font size="3">
@@ Line 51: / Line 51: @@
    '''updated field''':
 1  $a Brown, John, $d <font color="red">active</font> 1854.          ''LC policy
    </font>

@@ Line 1: / Line 1: @@
 ==RDA 5.2: Date Abbreviations==
-[[image:rda5-2.png]]
+[[image:rda5-2a.png]]
 ===Date abbreviations===
 There are many different abbreviations in $d (i.e., date) of 1XX, 6XX, 7XX, and

@@ Line 93: / Line 93: @@
 ===Other date abbreviations===
-A few additional abbreviations that can be expanded in date subfields include the following:
+A few additional abbreviations that can be expanded in date subfields include the following: [http://access.rdatoolkit.org/document.php?id=lcpschp9&target=lcps9-117# LC-PCC PS for 9.3.4.3] (html)
 {| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"

@@ Line 58: / Line 58: @@
 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.
+with month names. [http://access.rdatoolkit.org/document.php?id=rdaappb# RDA App. B] (html)
 {| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"

@@ Line 4: / Line 4: @@
 There are many different abbreviations in $d (i.e., date) of 1XX, 6XX, 7XX, and
 XX fields that can be expanded. The majority of these date changes only take
-place within X00 fields. [http://files.library.northwestern.edu/public/pccahitg/RDA_conversion.Subfield_d_and_f.doc NAF Conversion documentation X00 $d] (pdf) The main exception is expanding month names in X10,
+place within X00 fields. [http://files.library.northwestern.edu/public/pccahitg/RDA_conversion.Subfield_d_and_f.doc NAF Conversion documentation X00 $d] (pdf).  The main exception is expanding month names in X10,
 X11, and X30 fields. [http://access.rdatoolkit.org/document.php?id=rdaappb# RDA App. B] (html)