RDA 4.4 - Revision history

Casey: /* links */

2017-07-27T15:37:46Z

‎links

Nate: /* Default */

2014-04-04T16:53:46Z

‎Default

Karen: /* 260 to 264 conversion */

2014-01-22T01:41:22Z

‎260 to 264 conversion

Karen: /* 260 to 264 conversion */

2014-01-22T01:37:24Z

‎260 to 264 conversion

Nate: /* 260 to 264 conversion */

2013-04-03T18:42:10Z

‎260 to 264 conversion

Nate: /* 260 to 264 conversion */

2013-04-03T14:45:21Z

‎260 to 264 conversion

Nate: /* 260 to 264 conversion */

2013-04-03T14:42:58Z

‎260 to 264 conversion

Nate: /* 260 to 264 conversion */

2013-04-03T14:42:45Z

‎260 to 264 conversion

Nate: /* 260 to 264 conversion */

2013-04-02T21:59:20Z

‎260 to 264 conversion

Nate: /* links */

2013-03-27T15:01:52Z

‎links

@@ Line 30: / Line 30: @@
 ==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]] - [[RDA_4.7|4.7]]
+<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>
 [[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]]

@@ Line 19: / Line 19: @@
    '''converted to 264 field''':
   1 <font color="red">$a</font> [place of publication not identified] :<font color="red">$b</font> [publisher not identified], <font color="red">$c</font> 2005.</font>
 ==Default==
 {| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
 |- style="background:#CCFFFF; font-size: 110%;"
-| Attempt to convert 260 fields to 264 fields, removing the original 260 fields in the process.
+| Convert 260 to 264, and remove 260 in the process.
 |}
 <div style=clear:both></div><br>
 ==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]] - [[RDA_4.7|4.7]]

@@ Line 2: / Line 2: @@
 [[image:rda2-1.png]]
 ===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. [http://www.loc.gov/aba/pcc/documents/264-Guidelines.doc PCC Guidelines] (pdf)
+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. The PCC does not recommend converting 260 to 264. [http://www.loc.gov/aba/pcc/rda/RDA%20Task%20groups%20and%20charges/PCC-Hybrid-Bib-Rec-Guidelines-TG-Report.docx PCC Guidelines p. 20] (pdf)
 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. [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-6048# RDA 2.7.1 Production statement] (html) [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-6382# RDA 2.8.1 Publication statement] (html) [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-6939# RDA 2.9.1 Distribution statement] (html) [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-7298# RDA 2.10.1 Manufacture statement] (html) [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-7601# RDA 2.11.1 Copyright date] (html)

@@ Line 2: / Line 2: @@
 [[image:rda2-1.png]]
 ===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.
+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. [http://www.loc.gov/aba/pcc/documents/264-Guidelines.doc PCC Guidelines] (pdf)
-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.
+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. [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-6048# RDA 2.7.1 Production statement] (html) [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-6382# RDA 2.8.1 Publication statement] (html) [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-6939# RDA 2.9.1 Distribution statement] (html) [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-7298# RDA 2.10.1 Manufacture statement] (html) [http://access.rdatoolkit.org/document.php?id=rdachp2&target=rda2-7601# RDA 2.11.1 Copyright date] (html)
    <font size="3">
    '''original field''':

@@ Line 19: / Line 19: @@
    '''converted to 264 field''':
   1 <font color="red">$a</font> [place of publication not identified] :<font color="red">$b</font> [publisher not identified], <font color="red">$c</font> 2005.</font>
 ==Default==

@@ Line 7: / Line 7: @@
    <font size="3">
    '''original field''':
-    $a Mason City, Iowa :$b Sunburst Pub., $c c1992.
+    <font color="red">$a</font> Mason City, Iowa :<font color="red">$b</font> Sunburst Pub., <font color="red">$c</font> c1992.
    '''converted to 264 fields''':
-  1 $a Mason City, Iowa :$b Sunburst Pub., $c [1992]
+  1 <font color="red">$a</font> Mason City, Iowa :<font color="red">$b</font> Sunburst Pub., <font color="red">$c</font> [1992]
-  4 $c &copy;1992</font>
+  4 <font color="red">$c</font> &copy;1992</font>
    <font size="3">
    '''original field''':
-    $c 2005.
+    <font color="red">$c</font> 2005.
    '''converted to 264 field''':
-  1 $a [place of publication not identified] :$b [publisher not identified], $c 2005.</font>
+  1 <font color="red">$a</font> [place of publication not identified] :<font color="red">$b</font> [publisher not identified], <font color="red">$c</font> 2005.</font>
    <font size="3">
    '''original field''':
-    $a Berlin :$b N. Simrock ;$a Paris :$b Maison G. Flaxland, successeurs, $c [1908?]
+    <font color="red">$a</font> Berlin :<font color="red">$b</font> N. Simrock ;<font color="red">$a</font> Paris :<font color="red">$b</font> Maison G. Flaxland, successeurs, <font color="red">$c</font> [1908?]
    '''converted to 264 fields''':
-  1 $a Berlin :$b N. Simrock, $c [1908?]
+  1 <font color="red">$a</font> Berlin :<font color="red">$b</font> N. Simrock, <font color="red">$c</font> [1908?]
-  2 $a Paris :$b Maison G. Flaxland, successeurs, $c [date of distribution not identified]</font>
+  2 <font color="red">$a</font> Paris :<font color="red">$b</font> Maison G. Flaxland, successeurs, <font color="red">$c</font> [date of distribution not identified]</font>
 ==Default==

← Older revision		Revision as of 21:59, 2 April 2013
Line 5:		Line 5:

	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.		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.
		+	<font size="3">
		+	'''original field''':
		+	260 $a Mason City, Iowa :$b Sunburst Pub., $c c1992.
		+
		+	'''converted to 264 fields''':
		+	264 1 $a Mason City, Iowa :$b Sunburst Pub., $c [1992]
		+	264 4 $c ©1992</font>
		+
		+	<font size="3">
		+	'''original field''':
		+	260 $c 2005.
		+
		+	'''converted to 264 field''':
		+	264 1 $a [Place of publication not identified] :$b [Publisher not identified], $c 2005.</font>

	==Default==		==Default==