Principles for the Transition of the Authority Files to RDA

The LC/NACO Authority File and RDA Definitions 1.1 1.2 1.3 1.4 1.5 Authority record: a MARC record in the LC/NACO authority file; a MARC record whose 010 field contains subfield $a beginning "n" RDA authority record: an authority record whose cataloging rules code (008 byte 10) has the value "z" and whose 040 field contains subfield $e with the value "rda" Non-RDA authority record: any authority record that is not an RDA authority record AACR2 authority record: an authority record whose cataloging rules code (008 byte 10) has the value "c" The category AACR2 authority record defined in this document explicitly excludes the category of AACR2-compatible authority records—authority records with the value "d" in 008 byte 10 Heading or access point: any 1XX, 4XX or 5XX field in an authority record An AACR2 heading is a 1XX, 4XX or 5XX field in an AACR2 authority record, an RDA access point is a 1XX, 4XX or 5XX field in an RDA authority record, and so on 1.6 The migration of the LC/NACO authority file is a set of automated changes to the authority records in that file Principles General principles 2.1 2.2 2.3 2.4 With the exception of authority records whose 1XX fields that fall into one or more of the categories identified in section 3.1 of this document, all 1XX fields in AACR2 authority records are deemed acceptable for initial use under RDA The 1XX fields in AACR2 authority records deemed acceptable for use under RDA may later be changed only as described in section 2.12 The category of AACR2 headings acceptable for use under RDA includes headings whose content is susceptible to one or more of the automated manipulations described in section 3.2 of this document An AACR2 heading acceptable for use under RDA need not contain all possible RDA elements RDA elements not present in the heading may be preserved in the authority record in suitable non-heading authority fields AACR2 authority records whose 1XX fields are deemed acceptable for use under RDA are to be re-coded by automated procedure as RDA records to reflect their status Section 3.3 of this document provides the specifications for this re-coding 2.5 2.6 2.7 2.8 There is no category of "RDA-compatible" AACR2 authority records The 1XX fields in most AACR2 authority records can continue to be used in their current form (or after certain mechanical changes) under RDA All other 1XX fields must be reviewed and upgraded before they can be used under RDA The category of 1XX fields that require review includes all pre-AACR2 headings, and AACR2compatible headings The migration of the LC/NACO authority file involves principally the re-coding of AACR2 authority records with acceptable 1XX fields as RDA records The migration also involves changes to headings, and changes to authority data other than headings, in authority records of all types The RDA 7XX fields added during and after the RDA test are not needed after the migration These fields are handled as described in section 3.5 The authority file migration is an automated process; there will be no individual review of headings An error rate of no more than 5% is an acceptable consequence of the migration of the authority file The term error in this case refers not to purely mechanical errors (Oct should always become October and should never become Octagon) but to errors of commission.1 Before and after the migration 2.9 2.10 At all times, a PCC bibliographic record contains current authorized forms of name as found in the LC/NACO authority file Before the authority file migration, a PCC RDA bibliographic record may contain a mixture of established AACR2 headings and RDA preferred access points After the authority file migration, a newly-authorized PCC RDA bibliographic record may contain only RDA preferred access points Both before and after the migration, a non-RDA bibliographic record may contain headings created under any mixture of cataloging rules Before the authority file migration, those AACR2 1XX fields deemed acceptable for use under RDA (i.e., those that not fit into any of the categories identified in section 3.1) and that not need any of the changes described in section 3.2 may be used as the base element in new AACR2 headings and new RDA access points (For example, an acceptable AACR2 100 field may be used as the base element in a new AACR2 or RDA name/title heading, and an acceptable AACR2 110 field may be used as the base element in an AACR2 heading or RDA access For example, during the migration all occurrences of Dept in certain contexts will become Department The tasks force recognizes that a very few of the original AACR2 headings correctly contain the abbreviation and not the full form; because these are in the distinct minority of all headings containing Dept the task force believes it is better to change all occurrences of the abbreviation during the migration, and allow for those very few that should contain the abbreviation to be considered errors and changed back as the headings come under later review 2.11 2.12 2.13 2.14 point for a subordinate body; but a Bible heading that includes an abbreviation for the New Testament cannot be used as the basis for an RDA access point until after the migration.) The cataloging rules code (008/10, and 040 $e when applicable) in the new authority record for a heading that takes as its initial element or elements an acceptable AACR2 1XX heading, is the code for the rules used to formulate the element or elements added to the base heading After the authority file migration, only RDA authority records may be added to the LC/NACO authority file The PCC policy on changes to authority 1XX fields applies both before and after the migration At present, this policy holds that no change is to be made to an authority 1XX field that is not in error in a matter of fact and is not in conflict with other authority data A non-conflicting authority 1XX field is not to be changed simply because additional information becomes available—the new information may be preserved in suitable non-1XX authority variable fields This PCC policy is subject to modification by PCC as circumstances warrant 4XX fields in AACR2 authority records re-coded as RDA are to be considered "evaluated" and need not be reviewed or revised unless found to be in conflict with other authority data After the authority file migration, no new 7XX fields for RDA access points will be added to LC/NACO authority records Details 3.1 For the reasons stated in each of the following categories, certain AACR2 1XX fields are not covered by section 2.1; authority records with 1XX fields in these categories cannot be re-coded by program as RDA After the authority file migration, AACR2 authority records whose 1XX fields fall into one of the categories listed here except the last (which involves deletion of the AACR2 authority record during the migration) must be re-evaluated individually, and their authority records re-coded as RDA, before they can be used in RDA bibliographic records  Authority records whose 1XX fields represent ongoing conferences (Authority records for one-time conferences may safely be re-coded as AACR2.) Appendix A outlines the techniques suggested by the task force for the identification of various categories of conference headings, and their handling during the authority file migration      3.2 Authority records with 1XX fields that contain Polyglot in subfield $l2 The designation Polyglot has no parallel under RDA.3 4XX fields that contain Polyglot in subfield $l should be changed as encountered after the migration Authority records with 1XX fields that contain an ampersand ("&") in subfield $l Such authority records need to be replaced by a separate RDA authority record for each language Because of the difficulty in determining by program whether the second language in subfield $l represents the original language or the language of a second translation, appropriate new authority records cannot be created automatically; all such headings must be re-evaluated and replacement records created after the authority file migration.4 4XX fields that contain an ampersand in subfield $l may be changed as encountered after the migration Authority records whose 1XX field consists of an AACR2 1XX field excluded from the migration, plus additional subfields.5 Authority records for personal names that contain subfield $c are handled as described in Appendix B; some such authority records are re-coded as RDA, and some are left as is for individual review Authority records to be deleted, and automatically replaced by new RDA authority records (see section 3.4 of this document) Headings in non-RDA authority records (whether being re-coded as RDA, or not) are subject to automated manipulation during the authority file migration The changes described in section 3.2 not in themselves entail any change to the cataloging rules code (008 byte 10), or to 040 subfield $e With two exceptions, changes described in this section apply equally to all 1XX, 4XX and 5XX fields in non-RDA authority records These two exceptions are: 4XX fields that contain a Here and elsewhere in this document, the specification of a text to be found in existing records should be understood to cover all variations in casing of that text For example, the present rule covers the texts Polyglot, polyglot, POLYGLOT and all other variations in casing When this document specifies a replacement text ("January", "active"), the casing shown is the only acceptable form When authority records with such headings are encountered, the existing authority record should be deleted, and replaced by zero or more new records; each such new record should contain the original record's 010 $a in its 010 $z When authority records with such headings are encountered, the existing authority record should be deleted, and replaced by one or more new records; each such new record should contain the original record's 010 $a in its 010 $z For example, an AACR2 name/title authority record whose name portion is represented by an authority record coded AACR2-compatible is not to be re-coded as RDA The implication of this exception is that all authority records that are otherwise excluded from being re-coded as RDA headings must be identified first; the 1XX fields in these records can be used to identify those AACR2 authority records whose 1XX fields contain excluded headings plus additional subfields Headings in RDA authority records that appear to need the manipulations described in this section have been modified as a side-product of the work of this task force Have they? See table in Appendix C code other than "n" in byte of subfield $w, and 4XX fields for vernacular forms of name;7 these exceptional 4XX fields are to be carried forward into the updated authority record without change If any change described in this section involves an authority record's 1XX field, the original 1XX field will be preserved as a 4XX field, with the addition of subfield $w containing code "e" in byte 2, and the deletion of any existing 4XX field that has the same NACO comparison form as the modified 1XX field The instructions in section 3.2 not specify adjustments to punctuation and spacing that may be called for as a result of other changes          In subfields $a and $b of X10 and X51 fields, in subfields $a and $e of X11 fields, and in parenthesized qualifiers of all subfields of X30 fields, replace the abbreviations "Dept." and "Dépt." with "Department" and "Département", respectively.8 In subfield $d of X00, X10 and X11 fields, replace the abbreviations "cent.", "Jan.", "Feb.", "Mar.", "Apr.", "Jun.", "Jul.", "Aug.", "Sept.", "Oct.", "Nov." and "Dec." with "century", "January", "February", "March", "April", "June", "July", "August", "September", "October", "November" and "December", respectively In subfield $d of X00 fields, replace the abbreviations "ca." and "fl." with "approximately" and "active", respectively As instructed in Appendix B, remove subfield $c from certain X00 fields Replace the abbreviation "b." at the beginning of subfield $d in X00 fields with a hyphen following the date in subfield $d.10 Replace the abbreviation "d." at the beginning of subfield $d in X00 fields with a hyphen preceding all other text in subfield $d Replace the abbreviation "arr." in subfield $o of X00, X10 and X11 fields with "arranged" If subfield $t consists of "Selections" or "Selections.", or if subfield $t begins "Selections (", change the subfield code of that subfield to $k and precede that subfield with subfield $t containing "Works." In X30 fields that contain "Bible" in subfield $a and where $a is immediately followed by an instance of subfield $p that contains "O.T." or "N.T": if the subfield The task force used the following definition in its work: a vernacular form of name is any 4XX field containing any Unicode character at code point U+0370 or higher, excepting code points U+FE20 through U+FE23 inclusive In rare cases the consistent usage of a corporate body involves the abbreviation, not the full form Such converted headings fall under the aegis of section 2.12 because they are incorrect in a matter of fact; as such headings are discovered, the full form should be replaced by the abbreviated form During the task group's investigations, some headings in the LC/NACO authority file were found to contain non-standard variant abbreviations for the names of months, and were corrected 10 See 5.8 for the task force's preferred replacements for "b." and "d."  3.3 $p for a testament is itself followed by a second occurrence of $p, delete the first subfield $p and its contents; if the subfield $p for a testament is not immediately followed by a second occurrence of subfield $p, replace the contents of this subfield $p with "Old Testament" or "New Testament", respectively In X30 fields that contain "Koran" in subfield $a, replace the text in subfield $a with "Quran" Re-coding an AACR2 authority record as RDA involves the following steps:    3.4 change 008 byte 10 from "c" to "z" add 040 $e with the text "rda" add a new 667 field containing this text in subfield $a: "Pre-RDA heading deemed acceptable for continued use under RDA" If TG1 decides that AACR2 authority records for undifferentiated personal names11 should be split into separate records, one for each entity, proceed as follows The work described here can only be applied to authority records for undifferentiated personal names that have the following characteristics: they contain at least two "[Author of" (etc.) statements, they contain no 670 fields before the first "[Author of" statement, and they contain no 667 field that contains the text "additional persons"; records that not meet these tests must be reviewed individually and handled as appropriate   Delete the existing authority record Create one new authority record for each "[Author of" (or equivalent) statement Each new authority record will contain the original 010 $a in its 010 $z, will have the value "b" in 008 byte 32, will contain one original "[Author of" field re-tagged as a 667 field, and will contain the 670 fields that follow its "[Author of" (or equivalent) statement in the original record, up to but not including the next "[Author of" (or equivalent) statement Each such new authority record will contain a copy of any 4XX, 5XX and 675 fields present in the original record The handling of other fields in the original authority record (for example: call number fields, 667 fields) remains to be determined The headings in these new authority records are subject to the manipulations described in section 3.2; the new records are also subject to the manipulations described in sections 3.5 and 3.6 If instead TG1 recommends retaining authority records for undifferentiated names as presently constituted (at least until some point after the authority file migration), An authority record for an undifferentiated personal name is an authority record with value "b" in 008 byte 32 that contains a 100 field with only subfields $a, $b, $c, $d and $q 11 AACR2 authority records for undifferentiated personal name headings will be automatically re-coded as RDA authority records, or left for individual review andrecoding; the handling of these records will be determined by other characteristics present the records, as described elsewhere in this document 3.5 RDA access points contained in 7XX fields of non-RDA authority records will be used in the following operations at the time of the authority file migration       3.6 Find RDA authority records whose headings contain the text in the 7XX field plus additional subfields; replace the matching that text with the text from the authority record's 1XX field Replace access points in RDA bibliographic records that match the authority 7XX field with the text from the authority record's 1XX field If the authority record contains an RDA 700 field that contains subfield $q, and if that 700 field contains no subfields other than $a, $b, $c, $d or $q, and if the authority record does not already contain a 378 field, create a 378 field from subfield $q of the 700 field If the authority record contains an RDA 700 field that contains subfield $d, and if that 700 field contains no subfields other than $a, $b, $c, $d or $q, and if the authority record does not already contain an 046 field with subfield $f and/or $g, create an 046 field from subfield $d of the 700 field If the NACO comparison form of an RDA 7XX field does not match the NACO comparison form of an existing 1XX, 4XX or 5XX field in the authority record, create a 4XX field from the RDA 7XX field Do not include subfield $w in this 4XX field Delete the RDA 7XX field Make the following changes to any record in the LC/NACO authority file at the time of the authority file migration, whether or not the authority record is being re-coded from AACR2 to RDA Such a change does not in itself entail any change to the cataloging rules code (008 byte 10) or to 040 subfield $e   If the 100 field contains subfield $q and no subfields other than $a, $b, $c, $d and $q, and if the authority record does not contain a 378 field, create a 378 field from 100 subfield $q If the 100 field contains subfield $d and no subfields other than $a, $b, $c, $d and $q, and if the authority record does not contain an 046 field with subfields $f and/or $g, create an 046 field from 100 subfield $d Scheduling 4.1 4.2 4.3 The migration of data in the LC/NACO authority file described in this document should be performed at the same time in all coordinated copies of the file The work of the migration may extend over more than one day; during the migration, the file should be closed to maintenance of any other type The migration of the LC/NACO authority file should be timed in coordination with the weekly issues of updates to that file; records updated during the migration should be included in a single weekly issue Because of the large number of updated records involved in the migration, the Library of Congress should consider re-issuing to subscribers a complete copy of the file as it exists at the end of the migration The migration of data in the LC/NACO authority file will take place in one or, preferably two, phases The task force suggests that the migration be done in two phases, as described below, because authority records whose headings can be used under RDA without change will be clearly labeled as a result of the work done in the first phase If it is determined that the migration can only be done in a single phase, all of the work described in this document will be performed at once If the work can be done in two phases, the task force recommends the following contents for each phase:   4.4 Phase 1: RDA 7XX fields should be treated as described in section 2.8, and the 667 field described in section 3.3 should be added to those RDA records whose 1XX fields are not also susceptible to the manipulations described in section 3.2 Phase 2: all other work described in this document: the re-coding of acceptable AACR2 records as RDA, manipulations, and changes to other fields The migration of data in the LC/NACO authority file (or, if the migration is performed in two phases, the second phase) will be scheduled in appropriate relation to the national libraries' transition to RDA (i.e., not before Jan 1, 2013) 5 Additional recommendations 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 The changes described in section 3.2 should be made to headings in bibliographic records at the same time as they are made to headings in authority records 12 PCC should request that authority 008 byte 29 (reference tracing evaluation) be made obsolete The task force does not believe that the information provided in this byte serves any useful function PCC should develop guidelines for the use and structure of vernacular 4XX fields in LC/NACO authority records, and encourage participants to apply those guidelines to existing vernacular 4XX fields The LCPS concerning fullness of personal names should be replaced by a policy statement (based in large part on the current LCRI 22.18) that calls for the addition of subfield $q in the following cases: 1) in case of conflict, 2) when subfield $a of the heading contains an abbreviation or initials, or 3) when the heading consists of a surname alone (whether or not followed by subfield $c) This policy statement should explicitly proscribe the use of subfield $q for names not otherwise present in the heading simply because those additional names are available The PCC should, in coordination with the operators of large bibliographic databases and the vendors of automated library systems, set a schedule for the implementation of the full Unicode character repertoire in bibliographic and authority records The PCC should, in coordination with the operators of large bibliographic databases and the vendors of automated library systems, set a schedule for the implementation of the non-filing zone markers (Unicode code points U+0098 and U+009C) Validation routines for authority records submitted to the LC/NACO authority file should enforce the following rules: code "z" in 008 byte 10 must be accompanied by an acceptable value in 040 subfield $e; the presence of subfield $e in the 040 field requires code "z" in 008 byte 10 Enforcement of these validation rules (and other validation rules) should apply both to records contributed by operators and to records exchanged between copies of the authority file An extremely limited number of AACR2 headings to be re-coded as RDA will be found to be uncomfortable in the RDA world As is the case at present, there should be provision for LC's Policy and Standards Division or other suitable body to change existing RDA authorized access points even with there is no conflict Additional abbreviated forms (such as "Sep." instead of "Sept.") may be expected in those bibliographic headings not supported by LC/NACO authority records 12 5.9 5.10 and the headings are not wrong in a matter of fact Such changed authority records should bear a 667 field describing the reason for the change, and name the authorizing body Consideration should be given to a change to RDA so that the pre-RDA abbreviations "b." and "d." in X00 subfield $d are replaced with "born" and "died" instead of hyphens The sense of the current LCRI 24.2D, expressing preference for a spelled-out form for the name of a corporate name over the body's initials, should be embodied in an LCPS Appendix A The handling of AACR2 conference headings Headings for conferences present a special problem, because of different heading content under AACR2 and RDA AACR2 rule 24.7A1 provides for the omission from the heading for a conference of a term for the frequency of the conference, but RDA does not include such a provision This means that when such a term is available the AACR2 heading and RDA access point will differ AACR2 1XX heading: Symposium on Active Control of Vibration and Noise RDA preferred access point: Biennial Symposium on Active Control of Vibration and Noise The difficulty is that without reconsideration of the source materials used to construct a conference heading, it is not possible to know whether a term for frequency has been omitted from the heading; and without such examination, the validity of AACR2 conference headings under RDA cannot be determined In a XX% sampling of authority records for one-time conferences,13 the task force found that in under XX% of the headings a term for frequency should be included in the heading Therefore, the task force recommends that authority records for one-time conferences be re-coded from AACR2 to RDA The task force believes that the XX% error rate resulting from this re-coding is acceptable In a XX% sampling of authority records for ongoing conferences,14 the task force found that XX% of headings require the addition of a term for frequency The task force believes that an error rate of XX% were these records to be re-coded from AACR2 to RDA is not acceptable, and so recommends that authority records for ongoing conferences not be re-coded from AACR2 to RDA Identification of authority records for ongoing conferences requires the definition of two sub-categories   One sub-category of ongoing conferences is easily identified: the authority record contains a 111 field that does not contain $n, $d and/or $p before any subfield $t The remaining sub-category of ongoing conferences—those whose authority records contain 110 fields—cannot be identified so simply In an attempt to find these headings, the task force drew up a list of the terminal subfield $b in 110 fields for one-time conferences (those that contain subfield $n, $d and/or $p), under the assumption that A note here on the method, including definition of the category: those with a 110 or 111 field containing subfield $n, $d and/or $c before any subfield %t 14 A note here on the method, including definition of the sample category: those with 111 field not containing $n, $d and/or $c before any subfield $t 13 the terms in $b of these headings are likely to be equivalent to "conference", whether one-time or ongoing A list of these terms is included at the end of this appendix The task force believes that the appearance of any of these terms in the terminal subfield $b of any 110 field means that the authority record represents an ongoing conference, and so cannot be re-coded from AACR2 to RDA The following is a summary of the task force's recommendations for the handling of AACR2 authority records with 110 and 111 fields:     If the authority record's 110 or 111 field contains subfield $n, $d and/or $p before any subfield $t, the authority record can be re-coded from AACR2 to RDA If the authority record has a 111 field without $n, $d and/or $p before any $t, the authority record cannot be re-coded from AACR2 to RDA If the authority record has a 110 field whose terminal subfield $b is one of the terms listed at the end of this appendix, the authority record cannot be re-coded from AACR2 to RDA If the authority record has a 110 field whose terminal subfield $b is not one of the terms listed at the end of this appendix, the authority record can be re-coded from AACR2 to RDA The following is a list of terms whose appearance in terminal subfield $b of a 110 field (n the absence of $n, $d and/or $c) suggests that the authority record represents an ongoing conference, and so requires review before the record can be re-coded as RDA 15 abschlusstagung additional plenipotentiary conference arbeitstagung art exhibition asamblea constituyente asamblea nacional constituyente asia europe high level educationforum asia regional congress assamblea general assemblea nacional constituinte assemblee constituante assemblee generale assembleia constituinte assembleia nacional constituinte assembly assembly meeting assises atelier ayuntamiento cheng lid a hui The task force was not able to evaluate the nature of subfield $b texts for all languages The task force hopes that there will be additional review of the terms in this list before it is used in an implementation This list does not include texts discovered during the course of the task force's explorations that represent expeditions, texts that imply frequency ("Annual conference"; "Jahrestagung"), texts that imply a one-time nature ("50th Anniversary Conference"; "Founding Conference"), texts from headings that appear to be constructed improperly ("Dept of Criminal Justice Services"), and texts that represent joint meetings with named participants 15 cheng li ji xue shu tao lun hui cheng li ta hui chonghap haksul taehoe colloque colloque international colloque national colloquium coloquio concilium vaticanum conference conference and exposition in africa conference nationale conference nationale souveraine conference on materials for research in american culture conference on mother and newborn care conference on public budget modeling conference on the rule of st albert of jerusalem conferenza congregation generalis congres congres constitutive congres international congreso congreso constituyente congreso de angostura congreso general congreso internacional congress16 congresso congresso internazionale di studi congresul constituent assembly constitution in congress seminar constitutional assembly constitutional conference constitutional convention constitutive session consultation consultative meeting But if "congress" in subfield $b is preceded by "United States" in subfield $a, the authority record should be re-coded from AACR2 to RDA 16 convegno convegno di studi convegno di studio convegno internazionale convegno nazionale convegno regionale convencion nacional convencion nacional constituyente convention council council of toledo curso de verano dai hoi deng shan ke xue kao cha dui educational conference enquete gentechnik entretiens european meeting european regional conference exhibition expertengesprach exposition universelle et international fachkolloquium fachkonferenz fachkongress fachtagung fall conference fall meeting field conference foro economico foro universitario forum gemeinsame jahrestagung gemeinschaftstagung general assembly general conference general meeting giornata di studio giornate di studio grundungstagung guided expedition herbsttagung hsin chiang tzu yuan kai fa tsung ho kao cha tui hsueh shu tao lun hui hsueh shu tao lun huin hui i hui yi hui yuan da hui information symposium informationstagung interdisziplinares colloquium interdisziplinares colloquium der universitaten aachen und reims international colloquium international conference international convention international meeting international scientific conference international seminar international seminar for local government administration international symposium international workshop internationale fachtagung internationale konferenz international tagung internationale wissenschaftliche tagung internationales kolloquium internationales symposion internationales symposium joint assembly joint conference joint expert consultation on foods derived from biotechnology joint meeting joint symposium joint symposium on carbon ion radiotherapy jornadas journee journee detude journee detudes journees detude journees detudes journees scientifiques journees techniques kokusai shinpojumu kolloquium konferencja naukowa konferentsiia konferenz kongres kongress kongresszus konsultasi nasional konverents landtag lateran council leadership seminar legatine council legislature london conference londonskaia konferentsiia management symposium masagagaren gubae meeting meeting and exhibits meetings members meeting mukernas multaqa al ilmi mutamar nadwah nadwah al ilmiyah national conference national congress national consultative conference national convention national meeting national seminar national symposium national workshop nauchnaia sessiia niah hui nien hui obshchepartiinaia konferentsiia ocherednaia sessiia opcinska konferencija otdel dorevoliutsionnykh fondov parliament parteitag pastors and christian workers conference planning conference plenipotentiary conference plenum postgraduate conference postgraduate course preconference provinzialkonzil quan guo dai biao da hui quan guo dai biao hui yi rapat anggota rapat kerja nasional rastra mahasabha reformkongress region international conference regional conference regional meeting regional seminar regional technical conference regional workshop reichstag research conference reunion reunion cientifica reunion tecnica rhic winter workshop round table samecniero sesia sammankomst schuze scientific conference scientific meeting seminaire seminar seminar nasional seminario seminario internacional sesja naukowa seminario di studi settimana di studio sesja sesja naukowa sessiia sessio plenaria session sezd shinpojumu sized simposio simposio internacional sinodo skoai sommerakademie soritsu nijisshunen kinen kokusai semina soveshchanie special conference special meeting special session special session on children specialist group meeting specialists meeting specialty conference spring conference spring field conference spring meeting state convention studietagung summer institute summer meeting summer school summer seminar summit symposio symposion symposium symposium on histamine sympozjum synod synode national table ronde tagung taikai technical conference technical meeting technical symposium technical workshop teng shan ko hsueh kao cha tui topical meeting tri conference tukpyolchon uchreditelnyi sezd vatican council vedecka conference vserossiiskii sized delegatov vsesoiuznaia konferentsiia vyezdnaia sessiia winter meeting wissenschaftliche arbeitstagung wissenschaftliche konferenz wissenschaftliche tagung wissenschaftliches symposium working group meeting workshop world conference world congress writers workshop xinjiang zi yuan kai fa zong he kao cha dui xizang ke xue kao cha dui xizang yan hu kao cha dui xue shu nian hui xue shu tao lun hui yan tao hui yen tao hui zasedanie zasiedanie zhong quan hui zhumulangma feng ke xue kao cha fen dui zilele zjazd Appendix B Subfield $c in personal name fields If the proposed revisions to RDA 9.4.1 and 9.19.1.2 are not approved: Apply the following rule to any AACR2 authority record that contains an X00 field with subfield $c: If the text in an occurrence of subfield $c in a personal name field is present in the following list and if the heading is unique in the LC/NACO authority file after the removal of the subfield $c,17 remove the subfield $c from the field   Dame Sir If after application of this rule no instances of subfield $c remain in X00 fields in an authority record, the authority record can be re-coded as RDA provided it does not fall into any of the other categories for exclusion from this re-coding If after application of this rule at least one instance of subfield $c remains in an X00 field in an authority record, not remove any instance of subfield $c from the authority record, and not re-code the authority record as RDA If the proposed revisions to RDA 9.4.1 and 9.19.1.2 are approved: If the only texts in subfield $c in X00 fields in an authority record are present in the following list, re-code the authority record as RDA; if any subfield $c in an X00 field contains any $c text not in the following list, not re-code the authority record as RDA   Dame Sir Specifically, each modified 1XX field must be distinct from every other 1XX and 4XX field in the LC/NACO authority file; each modified 4XX must be distinct from every 1XX in the LC/NACO authority file Apply this test to the name portion alone of headings that build on a basic personal name heading— the name portion of name/title headings, for example 17 Appendix C Impact on the LC/NACO authority file The statistics presented in this appendix were gathered by examining in detail the authority file maintained by Northwestern University Library This file contains of a copy of the LC/NACO authority file, updated by weekly loads,18 and is essentially the same as copies of the LC/NACO authority file maintained at the Library of Congress, OCLC, and other institutions Despite likely small differences, statistics gathered from this file should be sufficient for planning purposes The following table shows the overall effect of the changes described in this document, in categories defined by the cataloging rules code in byte 10 of the 008 field AACR2 records are separated into two groups: those that are excluded from re-coding to RDA, and those that can be re-coded as RDA Record type Pre-AACR AACR1 AACR2 not re-codable19 AACR2 re-codable AACR2-compatible RDA Total Records 56,096 26,284 226,547 7,787,235 42,194 11,534 8,149,890 Re-coded to RDA 0 7,787,235 0 7,787,2 35 Records with changes other than re-coding 10,041 4,542 41,011 1,944,638 14,037 2,118 2,016,387 As a result of the migration, 7,858,984 authority records (7,787,235 AACR2 records re-coded to RDA plus the following records changed but not re-coded: 10,041 pre-AACR, 4,542 AACR1, 41,011 excluded AACR2, 14,037 AACR2-compatible, 2,118 RDA) will be modified in some manner and must be reissued This represents about 95% of the 8,149,890 records in the LC/NACO authority file The following table shows the reasons certain AACR2 records are not to be re-coded as RDA Reason for exclusion Contain Polyglot Records 688 This file also contains a complete set of LCSH and MeSH authority records, and records created locally but not contributed to any program These additional records are not included in the counts presented in this document The statistics were gathered after the loading of names weekly issue 2011.29 19 This figure includes undifferentiated name records that cannot be split into records for individual personalities If it is decided that undifferentiated name records should be maintained as they are at present, at least until after the migration, this figure will be about 4,000 lower Also, no attempt was made to identify and exclude authority records whose 1XX fields contain excluded 1XX fields plus additional subfields; the final number of AACR2 headings excluded from being re-coded as RDA will be higher than the number shown here, but the size of the change is not known 18 Contain & Ongoing 111 conference Ongoing 110 conference Personal name with $c 14,672 70,443 14,240 127,082 The following table shows the effect on headings of the mechanical changes described in sections 3.2, 3.4, 3.5 and 3.6 of this document Category 046 field created from 100/700 subfield $d 378 field added from 100/700 subfield $q X00 arr expanded20 X00 cent expanded X00 b changed to trailing hyphen X00 ca expanded X00 d changed to leading hyphen X00 fl expanded X00 abbreviated month replaced X10 arr expanded X10 Dept expanded X10 Dépt expanded X11 Dept expanded X11 abbreviated month replaced X30 arr Expanded X30 testament removed from Bible heading X30 abbreviated testament expanded X30 Dept expanded X30 Koran changed X51 Dept expanded X00 $t Selections replaced X10 $t Selections replaced X11 $t Selections replaced RDA 1XX fields changed via 7XX in other records 7XX deleted Undifferentiated name records require review Undifferentiated name records deleted Undifferentiated name records created Fields affected 1,633,675 425,598 3,986 53,992 515,992 83,168 112,422 53,003 6,200 127,229 51 1,595 377 2,950 261 327 23,385 16,769 4,874 51,284 131,500 At the time these statistics were gathered, Northwestern's copy of the LC/NACO authority file contained 5,965,783 100 fields, 4,157,518 400 fields and 58,714 500 fields; 1,378,644 110 fields, 1,844,536 410 fields and 274,636 510 fields; 174,484 111 fields, 188,626 411 fields and 15,961 511 fields; 506,425 130 fields, 334,212 430 fields and 32,647 530 fields; and 124,677 151 fields, 122,118 451 fields and 11,723 551 fields Counts of 4XX and 5XX fields in Northwestern's copy of the file will be found to be slightly elevated from counts in other copies of the file, because of locally-added fields 20 Of the AACR2 1XX fields in authority records that can be re-coded as RDA, only 215,885 require some change (chiefly an expansion of an abbreviation) This means that under the criteria specified in this document over 97% of acceptable AACR2 headings can be used under RDA Appendix D Full-record examples before-and-after Appendix E Examples of changes to headings before-and-after ... heading, is the code for the rules used to formulate the element or elements added to the base heading After the authority file migration, only RDA authority records may be added to the LC/NACO authority. .. sampling of authority records for one-time conferences,13 the task force found that in under XX% of the headings a term for frequency should be included in the heading Therefore, the task force... during the migration, the file should be closed to maintenance of any other type The migration of the LC/NACO authority file should be timed in coordination with the weekly issues of updates to that