This is intended as a brief update on our RDA changes we are implementing for all clients that currently have us enriching their records with RDA elements. 264 Field Ordering We have had some inquiries regarding re-ordering 264 fields based on 2nd indicator values. So when records have been updated, they might look like this: 264 _4 $a (c)2005. 264 _1 $a Mason City, Iowa :$b Sunburst, $c [1992] Now, our system will reorder the 264 fields while taking into account the 2nd indicator values. So the two fields above will be ordered as below: 264 _1 $a Mason City, Iowa :$b Sunburst, $c [1992] 264 _4 $a (c)2005. This situation caused some issues with proper indexing in a few different ILS. 264 / 880 Field Linking Our system was converting 260 fields to 264 fields as expected, but in the cases where an 880 field also exists (which linked to the old 260 field), it would break that link (note: I have excluded other information from the conversion to simplify the example): 260 __ $6 880-03 $c c1995. 880 __ $6 260-03 $c c1995. This updated to: 264 _4 $6 880-00 $c (c)1995. 880 __ $6 260-03 $c c1995. Now the system will retain the old 880 link as well as update the 880 $6 to reflect the new 264 field: 264 _4 $6 880-03 $c (c)1995. 880 __ $6 264-03 $c c1995. Please note that in cases where a single 260 field is converted to multiple 264 fields, only the original linking 264 field will have its $6 updated; additional 264 fields that were added during the conversion process will not link to the same 880 field after processing nor will they contain a $6 field at all. As always, please let us know any questions you may have about these updates. Nate Nate Cothran | Vice President, Automation Services Backstage Library Works | Provo, Utah & Bethlehem, Pennsylvania 801.342.5697 | nate@bslw.com <mailto:nate@bslw.com?subject=Automation%20Services%20-%20Inquiry> | bslw.com <http://www.bslw.com/> | ac.bslw.com/mars <http://ac.bslw.com/mars>
