MODS/Dublin Core Record Utilization Task Group



PCC Task Group on AACR2 & RDA Acceptable Heading CategoriesFINAL REPORTAugust 2011INTRODUCTIONFor the first time in thirty years, much of the cataloging world will be shifting to a new cataloging code, RDA: Resource Description and Access. This new cataloging code is a set of instructions and guidelines based on a very different conceptual paradigm, the Functional Requirements for Bibliographic Records (FRBR). RDA holds great promise in making library metadata better able to integrate into our larger information environment and help patrons discover and access resources more easily. The shift to a new paradigm is never an easy one, though, and legacy data must be smoothly integrated into any transition.Authority files are a particularly complex problem whenever cataloging codes are changed. Any massive updating of authority records (and the attendant bibliographic file maintenance) is impractical, even in an automated environment, yet authority records must be reflective of the new cataloging code. In addition, authority records themselves must support bibliographic records created under the old cataloging code, AACR2, and the new cataloging code, RDA. Last, creation of new authority records is a crucial element in the cataloging process and in the period of transition to RDA the authority files must actively be used both by AACR2 and RDA catalogers in their day-to-day work. Although beyond the scope of our charge, the task group felt that all of these issues must be addressed in its final report in order to make a coherent set of recommendations. The essential part of the report is its statement of principles. Some questions remain to be answered, but if these principles are adopted any further work will dovetail with the guidelines proposed. All members of the task group were extremely valuable in our discussions but I would like to acknowledge the extraordinary work of Gary Strawn in providing the analysis that made the report possible and his ability to write about complex processes in a clear and consistent way. CHARGECharge: The PCC Task Group on AACR2 & RDA Acceptable Heading Categories is charged to: Discern types of headings currently existing within the authority file (LC NAF) that fall into one of the following three categories1)????? Headings constructed under AACR2 and valid under RDA, therefore usable as-is2)????? Headings constructed under AACR2, in need of change to be used as valid RDA headings 3)????? Gray areas, where the need for change is uncertainIdentify specs for writing a report that could be used to collect all the records for each type of heading aboveFor category 1 (headings valid under RDA), recommend whether 008/10 (Descriptive cataloging rules) should systematically be relabeled as “z” for RDA, or whether such headings should simply be “grandfathered in” as is.For category 2 (headings not valid under RDA), determine if it is possible to provide specifications for making changes to the headings in an automated batch mannerFor category 3, briefly explain why each type is ambiguous and recommend if possible how to proceed?A goal in this work is to find non-energy-intensive means of implementing a new set of rules, while gaining a maximum of the benefits from RDA.The Task Group’s report will be reviewed by the Policy Committee and then posted to the PCC web site.?? The Policy Committee will then look into what party(ies) are available to carry out any recommended batch actions on authority records.?? It may be possible for the PCC Secretariat to report to the cataloging community an estimate of the percentage of the existing name authority file’s records that are/were in need of a heading change.MEMBERSPhilip Schreur, ChairHead, Metadata DepartmentStanford UniversityDiane BoehrHead of CatalogingNational Library of MedicineRobert BremerSenior Consulting Database SpecialistOCLCAna CristánPolicy and Standards DivisionLibrary of CongressPaul FrankCooperative Programs SectionLibrary of CongressChamya KincyLife & Social Sciences CatalogerUCLAGary StrawnAuthorities LibrarianNorthwestern UniversityJohn WrightChair of the Cataloging Services DepartmentBrigham Young UniversitySUMMARYThe report is divided into five sections: Definitions, Principles, Details, Scheduling, and Additional Recommendations. It is followed by six appendices on various specific topics having to do with the authority file migration. Two principles were at the forefront of the task group’s mind as we made our deliberations. First, any changes to the authority file must be as minimal as possible. Massive changes to authority records and the attendant bibliographic file maintenance in OCLC and a myriad of individual catalogs had to be avoided. Second, both AACR2 and RDA catalogers need to make use of the authority files in their everyday work until the transition to RDA is complete. The task group strongly endorses the principle of no hybrid authority records, that is, all parts of a heading must be valid in the same rule set. However, in the interim period of transition to RDA, RDA catalogers must be able to create authority records for sub-bodies or uniform titles whose base element is currently coded as AACR2. A second issue that soon arose was that of scheduling. Currently, most catalogers have not been trained in RDA. To re-code the authority file too soon would make it very difficult for these catalogers to function. And yet, RDA catalogers must be able to do their jobs as well. Because of this, the task group strongly recommends a two-phased approach to the re-coding of the authority file. First, as soon as possible, those headings that cannot be considered valid under RDA should be identified and marked as such. The vast majority of headings remaining could then be considered as RDA-acceptable and used by both AACR2 and RDA catalogers. The second phase should be tied to the national libraries’ transition to RDA. At that point, those headings considered to be RDA-acceptable should be recoded as RDA and all the mechanical changes to headings recommended in the report should be processed. After that point, only RDA records should be added to the authority file. It is strongly recommended that these changes be done on a Day 1, however, the task group recognizes that this massive updating and reissuing of authority records could be difficult for downstream processes to absorb. Because of this, an alternative approach would be to complete all the mechanical changes on Day 1 but stretch out the re-coding of RDA-acceptable headings to RDA over a period of time to make the updates easier to absorb. The task group recognizes that not all mechanical changes needed to make current AACR2 headings RDA-acceptable, or identification of all types of headings that cannot be considered RDA-acceptable could be accomplished in our short timeframe. RDA itself is undergoing changes as well and what is currently considered an RDA-acceptable heading may change over the next number of months. Because of this, the task group recommends that the mechanical updates listed in this report be tested, added to, and revised over the next year so that by Day 1 a final set of parameters can be accepted with confidence. If the principles expressed in Section 2 are followed, any additions or changes will harmonize with what is currently proposed.The LC/NACO Authority File and RDADefinitions – p. 7Principles – p.7Details – p. 10Scheduling – p. 14Additional Recommendations – p. 17Appendix A. The handling of AACR2 conference headings – p. 19Appendix B. Subfield $c in personal name fields – p. 24Appendix C. Authority records for undifferentiated names – p. 31Appendix D. Full-record examples – p. 34Appendix E. Examples of changes to headings – p. 40Appendix F. Impact on the LC/NACO Authority File – p. 41Appendix G. Significant differences between 100 and 700 $a – p. 441. Definitions1.1Authority record: a MARC record in the LC/NACO Authority File; a MARC record whose 010 field contains subfield $a beginning "n".1.2For the purposes of this document, authority records are to be characterized by their descriptive cataloging rules code (008 field, byte 10) and associated MARC content designation. For example:RDA authority record: an authority record whose descriptive cataloging rules code is "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 descriptive cataloging rules code is "c". The category AACR2 authority record defined in this document explicitly excludes the category of AACR2-compatible authority records—authority records with the descriptive cataloging rules code "d".1.3Heading or access point: any variable field in an authority record with a tag in the 1XX, 4XX or 5XX groups. An AACR2 heading is a MARC field in an AACR2 authority record with a tag in the 1XX, 4XX or 5XX group, an RDA access point is a MARC field in an RDA authority record with a tag in the 1XX, 4XX or 5XX group, and so on. References to authority variable fields by type include only heading fields (so a reference to X00 fields refers only to the 100, 400 and 500 fields). By definition, authority records in the LC/NACO Authority File can only contain headings of the following types: X00, X10, X11, X30, X51.1.4The migration of the LC/NACO Authority File is an automated set of changes to the authority records in that file. Section 4 of this document describes the major steps in the migration, and how they might be accomplished.1.5Day 1 is the date on which RDA is implemented at the national libraries and by the PCC. At present, this is assumed to be a date not before Jan. 1, 2013.2. PrinciplesGeneral principles2.1AACR2 authority records can be placed into broad categories by considering characteristics of their 1XX fields in relation to RDA specifications. (These criteria apply only to 1XX fields, and not to 4XX or 5XX fields.)AACR2 authority records whose 1XX fields contain, or appear to contain, elements not provided for under RDA, or whose 1XX fields lack, or appear to lack, information believed to be essential under RDA. These authority records must be reviewed and upgraded before their 1XX fields can be used under RDA. Characteristics used to identify these authority records are defined in section 3.1 of this report. About 225,000 AACR2 authority records (about 2.8% of AACR2 authority records) fall into this category.AACR2 authority records whose 1XX fields can be used after one or more of the mechanical operations described in section 3.3 of this report. About 172,000 AACR2 authority records (about 2.1% of AACR2 authority records) fall into this category.AACR2 authority records whose 1XX fields can be used under RDA without further modification. About 7,631,000 AACR2 authority records (about 95.1% of AACR2 authority records) fall into this category.In this report, AACR2 authority records in the second and third of these categories are called acceptable for use under RDA; authority records in the second category alone are acceptable for use under RDA with changes, and authority records in the third category alone are acceptable for use under RDA as is. Authority records in either of the first two categories are not acceptable for use under RDA as is.2.2There is no category of "RDA-compatible" authority records, but this does not mean that an AACR2 1XX field acceptable for use under RDA must contain all possible RDA elements. RDA elements not present in the 1XX field may be preserved in the authority record in suitable non-1XX authority fields.2.3The category of authority records whose 1XX fields require review before they can be used under RDA also includes all pre-AACR2 authority records and AACR2-compatible authority records.2.4The migration of the LC/NACO Authority File involves the re-coding of AACR2 authority records with acceptable 1XX fields as RDA records, and mechanical changes to headings and to authority data other than headings in authority records of all types.2.5To enhance the use of the LC/NACO Authority File during a transition period in which the use of either AACR2 and RDA is permitted, the task group believes that AACR2 authority records whose 1XX fields are not acceptable for use under RDA as is should be re-coded by automated procedure; and that this re-coding should take place as soon as possible. On Day 1 or over a period of time following Day 1, authority records whose 1XX fields are acceptable for use under RDA as is should be re-coded as RDA records. Section 3.2 of this document includes the specifications for this re-coding; section 4 gives further information about the scheduling of the re-coding, and the performance of mechanical changes to authority records.2.6The RDA 7XX fields added during and after the RDA test are no longer needed. These fields are handled as described in section 3.4.2.7The authority file migration is an automated process; there will be no individual review of headings or records during the automated migration. The migration may be preceded or followed by one or more projects to make individual changes to authority records in certain categories.2.8An error rate of no more than 5% is an acceptable consequence of the migration. The term error in this case refers not to purely mechanical errors, which should never occur (Oct. in subfield $d of personal name headings should always become October and should never become Octagon), but to changes that result in an incorrectly-formulated heading. The task group did not have the time to make samplings to determine the error rates that might be produced by the changes it recommends. The task group believes that any questions about the workability or advisability of its recommendations should be addressed first by the examination of information sampled from existing authority records.Before and after the migration2.9At all times, a PCC bibliographic record stored in the database of 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-authenticated PCC RDA bibliographic record may contain only RDA preferred access points. Both before and after the migration, non-RDA and non-PCC bibliographic records may contain headings created under any mixture of cataloging rules.2.10Before the authority file migration, any AACR2 1XX field may be used as the base element in a new AACR2 heading; the descriptive cataloging rules code in the authority record for such a new heading is "c". Before the migration, any AACR2 1XX field deemed acceptable for use under RDA as is may be used as the base element in a new RDA access point; the descriptive cataloging rules code in the authority record for such a new heading is "z", with code "rda" in 040 subfield $e. After all appropriate AACR2 authority records have been re-coded as RDA, only RDA 1XX fields can be used as the base element in RDA access points.2.11Before the authority file migration, both AACR2 and RDA authority records may be added to the LC/NACO Authority File. After the migration, only RDA authority records may be added to the LC/NACO Authority File.2.12The 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 policy covers AACR2 headings acceptable for use under RDA. This PCC policy is subject to modification by PCC as circumstances warrant.2.134XX 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.2.14Effective immediately, no new 7XX fields for RDA access points should be added to LC/NACO authority records.3. Details3.1For the reasons stated in each of the following categories, certain AACR2 1XX fields are not covered by section 2.1; AACR2 authority records with 1XX fields in these categories cannot be re-coded by program as RDA. After Day 1 of the authority file migration, AACR2 authority records whose 1XX fields fall into one of the categories listed here must be evaluated individually. In most cases the existing authority record can be modified, the record re-coded as RDA, and the resulting RDA heading used in bibliographic records; in a few cases the existing authority record must be deleted and, as circumstances dictate, replaced by other authority records.With the exception of the category for undifferentiated personal names, the definitions in this section apply equally to authority records whose 1XX field consists of a basic name or title by itself, and a basic heading with additional subfields (such as a subordinate body, the title of a work or the name of a part). The category for undifferentiated personal names consists only of undifferentiated personal names alone, and does not include name/title or other extended headings.Authority records whose 1XX fields represent ongoing conferences. (Authority records for one-time conferences may safely be re-coded as RDA.) Appendix A describes the reason authority records for ongoing conferences cannot be re-coded as RDA, outlines the techniques suggested by the task group for the identification of ongoing and one-time conference headings, and describes the handling of authority records for conferences during the authority file migration.Authority records with 1XX fields that contain Polyglot in subfield $l. The designation Polyglot has no parallel under RDA. When authority records with such headings are encountered after the migration, the existing authority record should be deleted, and replaced by zero or more new records (depending on the presence of other authority records for translations of the same basic work); each such new record should contain the original record's 010 $a in its 010 $z. A search should be made at the same time for the deleted 1XX field as 5XX fields in related records, and those 5XX fields deleted or adjusted as appropriate. Any 4XX fields that contain Polyglot in subfield $l where the 1XX field does not also 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. When authority records with such headings are encountered after the migration, the existing authority record should be deleted, and replaced by zero or more new records (depending on the presence of other authority records for translations of the same basic work); each such new record should contain the original record's 010 $a in its 010 $z. A search should be made at the same time for the deleted 1XX field as 5XX fields in related records, and those 5XX fields deleted or adjusted as appropriate. Any 4XX fields that contain an ampersand in subfield $l where the 1XX field does not also contain an ampersand in subfield $l should be changed as encountered after the migration.Authority records for personal names that contain subfield $c. RDA uses significantly different criteria for the formulation of subfield $c than does AACR2. Personal names with subfield $c are handled as described in Appendix B; some such authority records are re-coded as RDA, but most are left for individual review after the migration.The handling of authority records for undifferentiated personal names remains an unsettled issue, and cannot be decided by this task group alone. Depending on the resolution of this question, AACR2 authority records for undifferentiated personal names, or certain subsets of them, may also be excluded from being re-coded as RDA. Appendix C describes some of the considerations that may apply to authority records for undifferentiated personal names before the migration to RDA, and under RDA.3.2Re-coding an AACR2 authority record whose 1XX field can be used under RDA without any modification involves the following steps: Change 008 byte 10 from "c" to "z"Add 040 $e with the text "rda"Re-coding an AACR2 authority record whose 1XX field can be used under RDA after one or more of the changes described in section 3.3 involves the following steps.Change 008 byte 10 from "c" to "z"Add 040 $e with a new code meaning "AACR2; may be used under RDA after changes "Add a 667 field as the first 667 field in the record with the following text in subfield $a: "THIS HEADING CANNOT BE USED UNDER RDA UNTIL IT HAS BEEN UPDATED"Re-coding an AACR2 authority record whose 1XX field cannot be used under RDA even if changed involves the following steps:Add 040 $e with a new code meaning "AACR2; may not be used under RDA without re-evaluation "Add a 667 field as the first 667 field in the record, with the following text in subfield $a: "THIS HEADING CANNOT BE USED UNDER RDA UNTIL IT HAS BEEN REVIEWED INDIVIDUALLY "3.3Headings in all authority records (whether being re-coded as RDA, or not) are subject to automated manipulation during the authority file migration. The mechanical changes described in this section do not in themselves entail any change to the cataloging rules code (008 byte 10), or to 040 subfield $e. The changes described in this section apply equally to all 1XX, 4XX and 5XX fields in all authority records, with the sole exception of 4XX fields that represent formerly-valid headings (those that contain a code other than "n" in byte 2 of subfield $w); 4XX fields for formerly-valid headings are carried forward without modification. The instructions in this section do not specify adjustments to punctuation or spacing that may be called for as a result of these changes.If any change described in this section affects an authority record's 1XX field, preserve the original 1XX field as a 4XX field with subfield $w containing "nnea", and delete any existing 4XX field that has the same NACO comparison form as the modified 1XX field.In subfields $a and $b of X10 fields, in subfields $a and $e of X11 fields, in parenthesized qualifiers of all subfields of X30 fields, and in subfield $a of X51 fields, replace the abbreviations "Dept." and "Dépt." with "Department" and "Département", respectively.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. NOTEREF _Ref301070423 \h \* MERGEFORMAT 9 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.Replace the abbreviation "d." at the beginning of subfield $d in X00 fields with a hyphen preceding all other text in subfield $d. NOTEREF _Ref300910314 \h \* MERGEFORMAT 10 Replace the abbreviation "arr." in subfield $o with "arranged".If subfield $t consists solely of "Selections", or if subfield $t begins "Selections” immediately followed by a parenthetical qualifier, 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 $p for a testament is itself immediately followed by a second occurrence of subfield $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, retain the subfield and replace its contents with "Old Testament" or "New Testament", respectively.If a change is made to RDA to use "cello" instead of "violoncello" in statements of the medium of performance, replace "violoncello" with "cello" in subfield $m in any heading field.In X30 fields that contain "Koran" in subfield $a, replace the text in subfield $a with "Qur’ān".3.4Use RDA access points contained in RDA 7XX fields of non-RDA authority records in the following operations. If the text in an RDA 7XX field is not identical with the text of the 1XX field, find RDA authority records whose headings contain the text in the 7XX field plus additional subfields; replace the matching text with the text from the authority record's 1XX field.If the text in an RDA 7XX field is not identical with the text of the 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 includes 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 includes 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.Delete the RDA 7XX field.3.5Make the following changes to any record in the LC/NACO Authority File, whether or not the authority record is 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 a 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 $qIf a 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 $d4. Scheduling4.1Having a clear distinction in the LC/NACO Authority File between those AACR2 headings that can be used under RDA and those that cannot is important for all users of the file, and is critical for the period leading up to the implementation of RDA. The task group believes that marking this distinction in the LC/NACO Authority File should be made as quickly as possible, and over the shortest possible time span.There are at least three ways to mark AACR2 authority records to reflect this distinction: re-code all AACR2 authority records; re-code just those AACR2 records whose 1XX can be used under RDA without change; or re-code those records whose 1XX cannot be used under RDA even with change. The last of these three requires re-issuing the smallest number of authority records, and so is the course recommended by the task group. Specifically, the task group recommends that the information in sections 3.1 and 3.2 be used to identify AACR2 authority records whose 1XX fields cannot be used under RDA without review, and that those authority records be re-coded as soon as possible, as described in section 3.3. This means a change to about 396,000 AACR2 authority records, about 4.9% of the total. Once this has been accomplished, the same criteria should be applied to all newly-created and newly-modified AACR2 authority records. Authority records re-coded in this manner should not be individually reviewed and upgraded to RDA before Day 1.After the identification of AACR2 authority records whose 1XX fields cannot be used under RDA as is, it should be clear which headings may be used in which contexts: headings in the re-labeled authority records can only be used in new AACR2 bibliographic and authority records, and headings in the untouched AACR2 authority records can be used in either AACR2 or RDA bibliographic and authority records, as individual circumstances warrant. 4.2The task group believes that the main work of the migration of the LC/NACO Authority File is best performed at a single stroke. This work consists of the following steps:Make the changes described in sections 3.3, 3,4 and 3.5Re-code AACR2 authority records as RDARe-code authority records whose 1XX fields are acceptable for use under RDA after the changes described in section 3.2 as RDA, removing also the temporary 667 fieldThe following considerations apply if the migration takes place all at once:The migration should take place in all coordinated copies of the LC/NACO Authority File at the same time.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 LC/NACO Authority File should be closed to maintenance of any other type while the migration is in process. 4.3If the migration of the LC/NACO Authority File cannot be performed a single stroke, the task group recommends that the work described in section 4.1 to identify AACR2 authority records that cannot be used under RDA as is be undertaken as soon as possible, and that the remaining work of the migration be performed in the following phases.Before Day 1:Over a period of time ending before Day 1, treat RDA 7XX fields as described in section 3.4.Over a period of time, not necessarily either beginning or ending before Day 1, perform the operations described in section 3.5.On Day 1:Apply the changes described in section 3.3 to all appropriate authority records. If the authority record is labeled as an AACR2 heading that cannot be used under RDA without modification, re-code the authority record as RDA and remove the temporary 667 field. Perform the operations described in section 3.5 to any authority record re-issued as a result of this work.After Day 1:Over a period of time (months, perhaps a few years) re-code as described in section 3.1 the remaining AACR2 authority records as RDA.Over a period of time (months, perhaps a few years) complete the application of section 3.5.At the end of the migration, all former AACR2 records will either have been re-coded as inappropriate for use under RDA until review, or will have been re-coded as RDA authority records.5. Additional recommendations5.1The changes described in section 3.3 should be made to headings in bibliographic records at the same time as they are made to headings in authority records.5.2PCC should request that authority 008 byte 29 (reference tracing evaluation) be made obsolete. The task group does not believe that the information provided in this byte any longer serves a useful function.5.3PCC should develop guidelines for the use and structure of non-Latin 4XX fields in LC/NACO authority records, and encourage participants to apply those guidelines to existing non-Latin 4XX fields.5.4The LCPS concerning fullness of personal names as applied to newly-created authority records 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.5.5The 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.5.6The 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).5.7Validation routines for authority records submitted to the LC/NACO Authority File should enforce the following rule: code "z" in 008 byte 10 must be accompanied by an acceptable value in 040 subfield $e. Enforcement of this validation rule (and other validation rules) should apply both to records contributed by operators and to records exchanged between copies of the authority file.5.8LCPS 9.3.2.3 and 9.3.3.3 should be re-written so that the practice under RDA for subfield $d in personal names is the same in general outline as the practice under AACR2: For persons known or assumed to be dead: if dates of both birth and death are available, give both dates, separated by a hyphen; if only a birth date is available, give the birth date preceded by “born”; if only a death date is available, give the death date preceded by “died”For persons known or assumed to be alive for whom a birth date is available, give the birth date, followed by a hyphenThe task group recognizes that the use of words instead of the hyphen reduces the degree to which the information can be comprehended by non-English users; but that this is not a significant consideration for a subfield that can also contain "active," "approximately," and “century”.5.9The 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.5.10The task group considered the following additional mechanical change for inclusion in section 3.3, but did not have time adequately to determine its safety or feasibility: If no X00 field in an authority record includes subfield $c and if one of the record's 670 fields contains the surname from the 100 field followed immediately (perhaps with intervening punctuation) by "Jr.", and if "Jr." is itself immediately followed by punctuation (or is the end of the field), add subfield $c with the text "Jr." to the 100 and 400 fields in the record. The effect of this change on 500 fields in related authority records can only be determined by performing a search for such 500 fields.5.11A project could be undertaken—either before or after the migration—to examine authority records where subfield $a in an RDA 700 field is significantly different from subfield $a of the 100 field and, as appropriate, change the 100 field. (Of the 13,514 RDA 700 fields found in AACR2 records, 11,968 are identical with the 100 field; 146 of these contain significant differences—including flagrant errors—in subfield $a. See Appendix G.)5.12The JSC should consider changes to RDA 11.3.1.3 and RDA 16.2.2.9.2, to remove the instruction to abbreviate places associated with corporate bodies or places in a state, territory or province. If this change is approved before the migration, recognizable abbreviated place names in the following locations should be replaced by the full forms locations during the migration:X00: any parenthesized qualifier in $t or following subfieldsX10: parenthesized qualifier in $a or $b; anywhere in $c; any parenthesized qualifier in $t or following subfieldsX11: parenthesized qualifier in $a or $e; anywhere in $c; any parenthesized qualifier in $t or following subfieldsX30: parenthesized qualifier in any subfieldX51: any parenthesized qualifier in $a5.13Subfield $e of the 040 field can at present appear at any position in the field—for example it could easily appear between two occurrences of subfield $d. It would be more obvious to users if 040 subfield $e were consistently displayed somewhere between subfields $a and $c—perhaps always immediately before subfield $c, following any occurrence of subfield $b. The examples included in this report reflect this recommendation.Appendix A. The handling of AACR2 conference headingsThe following paragraphs describe the task group’s opinions on the best handling of AACR2 headings for conferences. The task group believes that these opinions should not become a course of action without a sampling of the headings involved. If a suggested change to RDA—to omit a term for frequency from the preferred access point for a conference—is approved, this appendix becomes irrelevant. If this change to RDA is approved, AACR2 headings for conferences may be re-coded as RDA unless they fall into one of the other categories defined in section 3.1 of this document.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 NoiseRDA preferred access point: Biennial Symposium on Active Control of Vibration and NoiseThe 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 AACR2 heading; and without such reconsideration, the validity of AACR2 conference headings under RDA cannot be determined.In order to determine how to handle AACR2 headings for conferences, the task group reviewed samples of AACR2 conference headings. The task group guessed that for the purposes of the migration to RDA a useful first distinction might be made between authority records that represent one-time meetings and those that represent ongoing meetings, because the names of meetings that only occur once are likely not to involve a term for the frequency of the meeting. The belief was that the task group might be able to recommend one course of action for one-time meetings and another for ongoing meetings. Because some conference headings are tagged 111 and others are tagged 110, and because the 110 tag is also used for non-conference headings, making a distinction between one-time and ongoing meetings presented the task group with something of a problem. The presence of subfields $n, $d or $c can be used by a computer program to divide 111 headings into the two sub-categories of ongoing and one-time. A program can also find headings for one-time meetings tagged 110 by looking for 110s where subfield $b is immediately followed by subfield $n, $d or $c; but finding headings for ongoing meetings tagged 110 is not so simple.The task group's approach to the identification of 110s for ongoing meetings was to examine the terminal subfield $b in 110s for one-time meetings; this produced a list of texts likely to express the notion of "meeting" in some manner. This list is included at the end of this Appendix.All of the above means that a computer program could be designed to identify these four categories of headings for conferences:One-time 111 conference headings (111 tag with $n, $d or $c present)Ongoing 111 conference headings (11 tag with $n, $d or $c not present)One-time 110 conference headings (110 tag with $n, $d or $c present)Ongoing 110 conference headings (110 tag with $n, $d or $c not present; an instance of $b contains one of the terms in the list at the end of this appendix)If it is necessary to distinguish between one-time and ongoing AACR2 conference headings for the purposes of the migration to RDA, these categories can be used as the basis for this work. The following is a summary of the task group'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 $c before any subfield $t, the authority record can be re-coded from AACR2 to RDA unless it fits into one of the other categories defined in section 3.1.If the authority record has a 111 field without $n, $d and/or $c before any $t, the authority record cannot be re-coded from AACR2 to RDA.If the authority record has a 110 field with first indicator "2" and with at least one instance of subfield $b containing 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 with first indicator "1", or with first indicator "2" in which no instance of subfield $b contains one of the terms listed at the end of this appendix, the authority record can be re-coded from AACR2 to RDA unless it fits into one of the other categories defined in section 3.1.The following is a list of terms whose appearance in terminal subfield $b of a 110 field (with first indicator "2" and in 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.abschlusstagungadditional plenipotentiary conferencearbeitstagungart exhibitionasamblea constituyenteasia europe high level education forumasia regional congressassamblea generalassemblee generaleassemblyassembly meetingassisesateliercheng li da huicheng li ji xue shu tao lun huicheng li ta huichonghap haksul taehoecolloquecolloque internationalcolloque nationalcolloquiumcoloquioconferenceconference and exposition in africaconference on materials for research in american cultureconference on mother and newborn careconference on public budget modelingconference on the rule of st albert of jerusalemconferenzacongregatio generaliscongrescongres constitutifcongres internationalcongresocongreso internacionalcongresscongressocongresso internazionale di studicongresulconstitution in congress seminarconstitutional conferenceconstitutional conventionconstitutive sessionconsultationconsultative meetingconvegnoconvegno di studiconvegno di studioconvegno internazionaleconvegno nazionaleconvegno regionaleconventioncouncilcouncil of toledocurso de veranodai hoideng shan ke xue kao cha duieducational conferenceentretienseuropean meetingeuropean regional conferenceexhibitionfachkonferenzfachkongressfachtagungfall conferencefall meetingfield conferenceforo economicoforumgemeinsame jahrestagunggemeinschaftstagunggeneral assemblygeneral conferencegeneral meetinggiornata di studiogiornate di studiogrundungstagungguided expeditionherbsttagunghsin chiang tzu yuan kai fa tsung ho kao cha tuihsueh shu tao lun huihsueh shu tao lun huinhui ihui yihui yuan da huiinformation symposiuminformationstagunginterdisziplinares kolloquiuminternational colloquiuminternational conferenceinternational conventioninternational meetinginternational scientific conferenceinternational seminarinternational symposiuminternational workshopinternationale fachtagunginternationale konferenzinternationale tagunginternationale wissenschaftliche tagunginternationales kolloquiuminternationales symposioninternationales symposiumjoint assemblyjoint conferencejoint expert consultation on foods derived from biotechnologyjoint meetingjoint symposiumjoint symposium on carbon ion radiotherapyjornadasjourneejournee detudejournee detudesjourneesjournees detudejournees detudesjournees scientifiqueskolloquiumkonferencja naukowakonferentsiiakonferenzkongreskongresskongresszuskonsultasi nasionalkonverentslateran councillegatine councillondon conferencelondonskaia konferentsiiamanagement symposiummasagagaren gubaemeetingmeeting and exhibitsmeetingsmukernasmultaqa al ilmimutamarnadwahnadwah al ilmiyahnational conferencenational congressnational consultative conferencenational conventionnational meetingnational seminarnational symposiumnational workshopnauchnaia sessiianian huinien huiobshchepartiinaia konferentsiiaocherednaia sessiiaotdel dorevoliutsionnykh fondovparteitagpastors and christian workers conferenceplenumpostgraduate conferencepostgraduate coursepreconferenceprovinzialkonzilquan guo dai biao da huiquan guo dai biao hui yirapat anggotarapat kerja nasionalrastra mahasabhareformkongressregion 8 international conferenceregional conferenceregional meetingregional seminarregional technical conferenceregional workshopresearch conferencereunionreunion cientificareunion tecnicarhic winter workshopround tablesamecniero sesiasammankomstschuzescientific conferencescientific meetingseminaireseminarseminar nasionalseminarioseminario internacionalsesja naukowasessiiasessio plenariasessionsezdshinpojumusizedsimposiosimposio internacionalsinodoskoaisommerakademiesoritsu nijisshunen kinen kokusai seminasoveshchaniespecial conferencespecial meetingspecial sessionspecial session on childrenspecialist group meetingspecialists meetingspecialty conferencespring conferencespring field conferencespring meetingstate conventionstudietagungsummer meetingsummer schoolsummer seminarsymposiosymposionsymposiumsymposium on histaminesympozjumsynodsynode nationaltable rondetagungtaikaitechnical conferencetechnical meetingtechnical symposiumtechnical workshopteng shan ko hsueh kao cha tuitopical meetingtri conferencetukpyolchonuchreditelnyi sezdvatican councilvedecka conferencevserossiiskii siezd delegatovvsesoiuznaia konferentsiiavyezdnaia sessiiawinter meetingwissenschaftliche arbeitstagungwissenschaftliche konferenzwissenschaftliche tagungwissenschaftliches symposiumworking group meetingworkshopworld conferenceworld congresswriters workshopxinjiang zi yuan kai fa zong he kao cha duixizang ke xue kao cha duixizang yan hu kao cha duixue shu nian huixue shu tao lun huiyan tao huiyen tao huizasedaniezasiedaniezhong quan huizhumulangma feng ke xue kao cha fen duizilelezjazdAppendix B. Subfield $c in personal name fieldsIf the proposed revisions to RDA 9.4.1 and 9.19.1.2 are not approved, so that "Dame" and "Sir" are not to be considered for use in subfield $c: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 an X00 field is present in the following list and if the field is unique in the LC/NACO Authority File after the removal of the subfield $c, remove the subfield $c from the field.DameSirAfter the application of this rule:If 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 the only instances of subfield $c that remain in X00 fields in an authority record contain "Jr.," "Sr." or a roman numeral, 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 at least one instance of subfield $c remains in an X00 field in an authority record with a text other than "Jr.", "Sr." or a roman numeral, do not remove any instance of subfield $c from the authority record, and do not re-code the authority record as RDA.If the proposed revisions to RDA 9.4.1 and 9.19.1.2 are approved, and "Dame" and "Sir" are to be considered for use in subfield $c: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, do not re-code the authority record as RDA.DameSirJr.Sr.any roman numeralThe following list contains all texts that occur 10 or more times in subfield $c of AACR2 100 fields. (These 100 fields are not name/title headings, and the text in subfield $c does not begin with a parenthesis.) The texts are given in normalized form, in order of frequency of occurrence. Before the RDA migration, this list should be reviewed to see if additional $c texts can be identified that can be carried forward into RDA access points, in the same manner as “Jr.” and “Sr.”6118dr4643sir3182mrs2305ph d2185vocalist2017musician1526jr1232m d1226m1140baron1094mr977singer891earl of834pianist805rev763saint693guitarist661swami657u637esq598ha levi593m a589composer576prof558lady546conductor529freiherr von509captain506ha kohen416drummer414md381comte de330tenor328mlle320professor313abbe300iii298violinist296sister293graf von284graf263viscount259marquis de259soprano256bassist253saxophonist251lord251miss243organist234duke of234pope230percussionist219mon216dipl ing216merchant214conte214countess of210mons207phd201muni200gent199prof dr196capt196comte189baritone189violoncellist187kniaz185ma185shi184mme181shipmaster178m de176baron de174do170b a163colonel161dr ing161dr phil158himi158rn155flutist153arranger153photographer152madame151clarinetist150lyricist149cartographer144major142actor136bass135printer134ritter von131a rhan131duc de130sr129ll m128thich122ll b122s j121violist120phikkhu120r118earl118ing117father117msc115bookseller113director113sieur112dr iur109archimandrite109dancer109monsieur109publisher108baroness108haji108m sc107rabbi106trombonist103fray102ii102marques de101double bassist101lieutenant100conde de100j d100llb100trumpet player98m s98professeur96advocate96prince96producer95esquire95surveyor94drs93emperor of japan92grof92journalist92logkeeper92oboist92solicitor91al duktur89duchess of88dr rer nat87attorney87brother87pere86r n85mezzo soprano85mother81docteur81emperor of china80engineer80harpist79barrister at law79fiddler79sieur de79wan79whaling master78vicomte de77architect77illustrator77marchese77trumpeter76dr med76rgn76surgeon74artist74general74luang74phraya73bishop73dr jur73ed d73engraver73fr73svami72a m72barrister72phra khru72rechtsanwalt71princess70bsc70chevalier de70duktur69b sc69dame69docteur en droit69horn player67frei66daktar66padre65grafin von64comtesse de64kandidat iuridicheskikh nauk63d d63emperor of rome63marquess of62narrator61chief61mba61poet60king of egypt60phra60shipowner59citoyen59pastor58m r58raja57actress57cha ra57doctor57judge57sadhvi56freiherr55keyboardist54king of korea54marquise de54takkasuil54writer in edinburgh53duque de53p e52merchant in edinburgh51avocat51comte d51d d s51grafin51marquis of51maulana51phra maha49emperor of the east49greve49jun49m ed49reverend48king of england48ustad48writer47bhikkhu47lieutenant colonel47pseud47raden46d46de46ts45ba45countess45dato45kand tekhn nauk45kandidat istoricheskikh nauk45ms44banjoist44cardinal44gentleman44landowner44protoierei44soeur44viscountess43auctioneer43master43uncle42m c42merchant in glasgow42prof dr ing42songwriter42sthavira41bassoonist41dipl kfm41geologist41judr41m l41madame de41madre41mas41pandita41visconde de40baba40king of france40vicomte39baron von39count39d phil39doktor tekhnicheskikh nauk39graf zu39jazz musician39m labbe39monsieur de39of bucks county pa39of london39syed38acarya38col38farmer38junior38k i n37abbe de37dr rer pol37duc d37duchesse de37holy roman emperor37lt col37pandit37rapper36acharya36baro36bhai36chevalier36harmonica player36hieromonk36igumen36m b a36m phil35country musician35edler von35lawyer35phdr35physician35schoolmaster35teacher34cpa34don34economist34mere34nik34rinpoche34soldier33accordionist33army officer33bhaddanta33comtesse33datuk33freifrau von33furst von33gter ston33harpsichordist33mathematician33maung32andi32caliph32civil engineer32dvm32hrabia32marquis31aunt31da31lecturer31minister of the gospel31thera30banjo player30barone30blues musician30capitaine30cha ra to30chef30ha rav30hj30marquis d30mb30prince de30sor30student30sultan of the turks29accountant29archduke of austria29barao de29frere29h29hon29kandidat ekonomicheskikh nauk29ksiaze29of new jersey29stage name28bass player28daw28dokta28friherre28ir28king of portugal28mkhan po28performer27clerk27doktor iuridicheskikh nauk27gospel singer27grand duke of russia27iv27lama27ll d27marchioness of27mgr27novelist27r m27rev mr26archbishop26brahmachari26chemist26countertenor26inzh26llm26lt26mariner26monachos26mrcp26o p26of alexandria26polkovnik26screenwriter25apothecary25bhikshu25consultant25doc dr25doktor ekonomicheskikh nauk25dom25frcs25king of poland25kniaginia25ks25lic25o b e25o s b25obe25of camden n j25rndr25ship captain24contralto24d v m24doktor24fra24giani24ieromonakh24ingenieur24king of vietnam24mag24pfarrer24profesor24qc24rev dr24richter24sheikh24yogi23blacksmith23curator23dancing master23doktor istoricheskikh nauk23k t n23kand fiz mat nauk23kandidat filologicheskikh nauk23ki23maharaja23mbe23of edinburgh23of northampton mass23the younger23translator22al anba22choreographer22commandant22commissaire priseur22furst zu22justice of the peace22lieut22mestre22monakhinia22of dublin22of portland me22quaker22r p22union soldier21b s21conte di21dipl psych21khun21king of sweden21librarian21missionary21patriarch of constantinople21revd21seigneur de21shah of iran21tengku21yeoman20ashin20botanist20comedian20dds20gardener20ieroskhimonakh20justice20k f n20mademoiselle20minister20mph20reporter19baron van19d r tekhn nauk19deacon19doc dr hab19editor19elder19frater19historian19k e n19kand biol nauk19kand geogr nauk19keyboard player19merchant in aberdeen19mufti19nahimi19playwright19s h19sa khan19signor19sviashchennik19tan sri19taylor19teuku19tubist18alto18attorney at law18bass baritone18cha ra u18cuvami18da shi18dipl math18doktor meditsinskikh nauk18guru18hafiz18kand ist nauk18king of armenia18king of denmark18king of scotland18m s w18mbbs18mme de18mr de18of bristol18of the inner temple18q c18rmn18shoemaker18somdet18whaler17baron d17buil17commander17general maior17graf von der17j p17kandidat tekhnicheskikh nauk17kui17mayor17me17ministerialrat17monk17of falmouth me17of new london conn17of portsmouth n h17sheriff17voivode of wallachia16al shaykh16b d16canon16cartoonist16chaophraya16choral director16d r16doktor filosofskikh nauk16dr inz16dr theol16folk singer16freiin von16grafinia16kavi16king of aragon16king of spain16m arch16maha16mandolinist16marchese di16meister16of nantucket mass16of the middle temple16prince of prussia16princesse de16sok16srn16widow16writer on witchcraft15abbot15aine15contessa15cook15costume designer15d c15d min15dato haji15docteur es lettres15fca15film director15frcp15freiherr von der15kandidat filosofskikh nauk15king of norway15l l b15maharaj15major general15master of arts15mate15mudr15of maine15painter15prof dr med15professor dr15reverend mr15rin po che15sadhu15thanphuying15veuve15voivode of moldavia15writing master14assistant professor14brahmacari14collector14d e n14doktor pedagogicheskikh nauk14dr rer oec14filmmaker14frau14khan14king of castile and leon14king of hungary14king of navarre14king of siam14lala14land surveyor14mahathera14marchesa14medecin14merchant in leith14mrcvs14msn14nayaka sthavira14o s a14of glasgow14of lincolns inn14of norwich14of philadelphia14pgs ts14prinz zu14prof nadzw dr hab14rabi14school master14sister o p14sri14sultan of the seljuks14sunim13antipope13arkhimandrit13associate professor13baron of13baronne13baronne de13blues singer13bsc hons13c p a13country singer13da siena13designer13dge bses13doc ing13doktor fiziko matematicheskikh nauk13dr sc13furst13graaf van13inok13kand iurid nauk13kandidat biologicheskikh nauk13kapitan13kavinar13khenpo13khunying13king of ceylon13lithographer13m b13maestro13maitre13merchant in london13metropolitan13of grays inn13of new york13prinz von13private13regierungsdirektor13saw13sayyid13shaker13sultan of morocco13suor12a b12bey12c e12carpenter12catholicos of armenia12comtesse d12corporal12cousin12d sc12dipl volkswirt12doktor biologicheskikh nauk12doktor filologicheskikh nauk12dr hab12dr sc nat12duke of bavaria12elector of saxony12farrier12fils12freiherr von und zu12geshe12graphic designer12irmao12junr12kand ekon nauk12kandidat pedagogicheskikh nauk12king of assyria12laine12m p h12mag dr12magister12maharshi12mirza12osb12p12pater12philomath12presbyter12priest12prince of orange12prince son of mongkut king of siam12raden mas12rd12rig dzin12rock musician12senior12sergeant12sj12skhimonakhinia12sultan of egypt and syria12vardapet11aia11al sayyid11archaeologist11ba hons11bagpiper11banker11bass guitarist11besud11br11c eng11cha ra kri u11chanoine11chimney sweeper11clergyman11conde da11czar of bulgaria11dipl kfm dr11dipl pad11diplom volkswirt11dona11dra11dramatist11duke of wurttemberg11dulcimer player11educator11f s a11flute player11grand duke of kiev11grandma11grocer11igumeniia11journaliste11kandidat fiziko matematicheskikh nauk11king of the visigoths11librettist11linen draper11m b e11m p11m p a11m th11mantale11mercer11mlle de11mrcgp11mrcpsych11munshi11negus of ethiopia11nurse11oberregierungsrat11of athens11of windham me11of york11physicist11prince of transylvania11queen of egypt11rai bahadur11sailor11santa11saya11sayadaw11schwester11shaykh11supreme patriarch11syeikh11tacksman11weaver11writer of verse10abba10abuna10accomptant10alderman10architecte10archivist10businessman10cha ra to u10chaplain10da firenze10da rimini10da verona10dipl biol10dissenting minister10draftsman10duca di10edd10elector palatine10emperor of russia10frcr10gospel musician10halevi10kand filol nauk10king of burma10king of judah10king of persia10king of the franks10lecturer in law10m a ll b10m r c s10marquesa de10o f m10of boston mass10of newcastle upon tyne10of philadelphia pa10patriarch of antioch10psychoanalyst10psychologist10r ng10rav10ritter10saint patriarch of constantinople10skhiarkhimandrit10slave10sprul sku10t10tabla player10thien su10treasurer10tun10tunku10vicomte dAppendix C. Authority records for undifferentiated namesIntroductionThe handling of authority records for undifferentiated personal names under RDA was not a settled matter at the time of the writing of this report. The central question is whether there should continue to be one authority record for all persons sharing a common access point, or whether there should be a set of records, one for each person. The timing of any change to the current practice is complicated by the substantial modifications to computer systems that may be necessary if the latter course of action is taken.Although this matter has arisen as an aspect of the RDA migration, the handling of authority records for undifferentiated personal names is not necessarily tied to this migration, because RDA does not itself describe authority records for such names in any detail—no more than does AACR2. This means that any decision made to split composite authority records for undifferentiated personal names into individual authority records may in fact be made at any time, and can be independent of any migration to RDA.In its deliberations, the task group concerned itself primarily with the manner in which the splitting of authority records for undifferentiated personal names might be achieved, were it decided that such splitting should occur. The present appendix contains the task group’s conclusions. If it is decided that this splitting should occur, and if it is felt that the bulk of this splitting can be achieved well enough by computer program, the task group believes that such work can be folded into other tasks that must take place on Day 1; if not, then it can be performed at any other convenient time. MethodThe work described here can only be performed if an attempt is to be made to split authority records for undifferentiated personal names into multiple records, one for each entity. These steps can only be applied to authority records for undifferentiated personal names that have the following characteristics:Byte 32 of the 008 field contains value “b”The 100 field has no subfields other than $a, $b, $c, $d and $qThere are at least two "[Author of" statementsThere is no 670 field before the first "[Author of" statementEach "[Author of" statement is followed by at least one other 670 fieldThere is no 667 field that contains the text "additional persons"There is no field with any of the following tags: 046, 053, 37X, 5XX, 663, 665, 678Proceed as follows:Delete the existing authority record, and replace it with one new authority record for each "[Author of" (or equivalent statement). Each new record has these characteristics:The original 010 $a in 010 $zThe value "b" in 008 byte 32100 field from the original recordAll 667 fields present in the original recordAll Latin-alphabet 4XX fields present in the original recordThe 670 fields between one "[Author of" field and the nextDiscard any 675 field present in the original record.The headings in these new authority records are subject to the manipulations described in section 3.3; the new records are also subject to the manipulations described in sections 3.4 and 3.5.If no attempt is to be made at the time of the migration to split authority records for undifferentiated names into multiple records before or at the time of the migration, AACR2 authority records for undifferentiated personal name headings will be automatically re-coded as RDA authority records, or left for individual review and-recoding, as determined by other characteristics present in the records. All authority records for undifferentiated personal names are subject to the manipulations described in sections 3.4 through 3.6.Appendix D. Full-record examples1) 100 field acceptable for use as is under RDAAACR2 record before re-coding: 008 890501n| acannaab| |n aaa 010: : |a n 88202651 040: : |a DLC |c DLC |d DLC100:1 : |a Smithers, Elaine Vertz670: : |a Her Haley, Marshall, Getchell, Barlow genealogy, 1986: |b t.p. (Elaine Vertz Smithers; on label: Elaine Smithers; Waukesha, WI) RDA record after re-coding: 008 890501n| azannaab| |n aaa 010: : |a n 88202651 040: : |a DLC |e rda |c DLC |d DLCa100:1 : |a Smithers, Elaine Vertz670: : |a Her Haley, Marshall, Getchell, Barlow genealogy, 1986: |b t.p. (Elaine Vertz Smithers; on label: Elaine Smithers; Waukesha, WI) 2) 100 field that cannot be used under RDA without review (because of subfield $c)AACR2 record before re-coding: 008 840131n| acannaabn |a aaa 010: : |a n 82231868 040: : |a DLC |c DLC |d DLC |d NmU |d Uk100:1 : |a Hamilton, Paul, |c D. Phil.400:1 : |a Hamilton, P. W. A. |q (Paul W. A.)670: : |a His Coleridge's poetics, 1983: |b t.p. (Paul Hamilton) jkt. (fellow & tutor in English, Exeter Coll., Oxford)670: : |a BNB May-Aug. 1983 |b (Hamilton, Paul)670: : |a Commonwealth univ. yrbk., 1983 |b (Hamilton, P.W.A. [Exeter], MA Glas & Oxf, DPhil.); 1992 (Hamilton, P.W.A.; prof. of Eng. & dept. hd., Univ. of Southampton)670: : |a His Historicism, 1996: |b CIP t.p. (Paul Hamilton) data sheet (b. 06-06-60) galley (teaches English at Univ. of Southampton)670: : |a Percy Bysshe Shelley, 2000; |b t.p. (Paul Hamilton) p. 4 of cover (prof. of English and Head of Sch. of English and Drama, Queen Mary and Westfield Univ. of London; author of Coleridge's poetics (1983), Wordsworth (1986), and Historicism (1996))670: : |a Historicism, 2003: |b CIP t.p. (Paul Hamilton) data view (b. 11/02/50)670: : |a Letter from author, 8 Oct. 2003 |b (Paul William Alexander Hamilton, born 11 Feb. 1950)AACR2 record after re-coding: 008 840131n| acannaabn |a aaa 010: : |a n 82231868 040: : |a DLC |e <coding meaning "AACR2, cannot be used under RDA until evaluated"> |c DLC |d DLC |d NmU |d Uk100:1 : |a Hamilton, Paul, |c D. Phil.400:1 : |a Hamilton, P. W. A. |q (Paul W. A.)667: : |a THIS HEADING CANNOT BE USED UNDER RDA UNTIL IT HAS BEEN REVIEWED INDIVIDUALLY670: : |a His Coleridge's poetics, 1983: |b t.p. (Paul Hamilton) jkt. (fellow & tutor in English, Exeter Coll., Oxford)670: : |a BNB May-Aug. 1983 |b (Hamilton, Paul)670: : |a Commonwealth univ. yrbk., 1983 |b (Hamilton, P.W.A. [Exeter], MA Glas & Oxf, DPhil.); 1992 (Hamilton, P.W.A.; prof. of Eng. & dept. hd., Univ. of Southampton)670: : |a His Historicism, 1996: |b CIP t.p. (Paul Hamilton) data sheet (b. 06-06-60) galley (teaches English at Univ. of Southampton)670: : |a Percy Bysshe Shelley, 2000; |b t.p. (Paul Hamilton) p. 4 of cover (prof. of English and Head of Sch. of English and Drama, Queen Mary and Westfield Univ. of London; author of Coleridge's poetics (1983), Wordsworth (1986), and Historicism (1996))670: : |a Historicism, 2003: |b CIP t.p. (Paul Hamilton) data view (b. 11/02/50)670: : |a Letter from author, 8 Oct. 2003 |b (Paul William Alexander Hamilton, born 11 Feb. 1950)3) 100 field that can be used under RDA with changes (abbreviation in 100 $d)AACR2 record before re-coding: 008 860501n| acannaab |a aaa 010: : |a n 85325223 040: : |a DLC |b eng |c DLC |d Uk100:1 : |a Smith, Roland, |d 1943 Apr. 11-670: : |a His Soviet policy towards West Germany, 1985: |b t.p. (Roland Smith) p. 2 of cover (in Brit. Diplomatic Service; with Int'l Inst. for Strategic Studies 1983/84)670: : |a Dipl. Ser. list, 1985 |b (Smith, Roland Hedley; b. Apr. 11 1943; Counsellor and Head, Chancery BNG Berlin since 1984; at IISS 1983)AACR2 record after re-coding: 008 860501n| azannaab |a aaa 010: : |a n 85325223 040: : |a DLC |b eng |e <code meaning "AACR2; may not be used under RDA until modified">|c DLC |d Uk100:1 : |a Smith, Roland, |d 1943 Apr. 11-667: : |a THIS HEADING CANNOT BE USED UNDER RDA UNTIL IT HAS BEEN UPDATED670: : |a His Soviet policy towards West Germany, 1985: |b t.p. (Roland Smith) p. 2 of cover (in Brit. Diplomatic Service; with Int'l Inst. for Strategic Studies 1983/84)670: : |a Dipl. Ser. list, 1985 |b (Smith, Roland Hedley; b. Apr. 11 1943; Counsellor and Head, Chancery BNG Berlin since 1984; at IISS 1983)RDA record after the migration: 008 860501n| azannaab |a aaa 010: : |a n 85325223 040: : |a DLC |b eng |e rda |c DLC |d Uk046: : |f <representation for " 1943">100:1 : |a Smith, Roland, |d 1943 April 11-670: : |a His Soviet policy towards West Germany, 1985: |b t.p. (Roland Smith) p. 2 of cover (in Brit. Diplomatic Service; with Int'l Inst. for Strategic Studies 1983/84)670: : |a Dipl. Ser. list, 1985 |b (Smith, Roland Hedley; b. Apr. 11 1943; Counsellor and Head, Chancery BNG Berlin since 1984; at IISS 1983)4) 110 field that can be used under RDA with changes (abbreviations)AACR2 record before re-coding: 008 961104n| acannaab| |a ana c010: : |a no 96057488 |z n 92099552 040: : |a IWhN |c IWhN |d DLC110:1 : |a Chicago (Ill.). |b Dept. of Planning and Development410:1 : |a Chicago (Ill.). |b Dept. of Planning & Development410:1 : |a Chicago (Ill.). |b Planning and Development, Dept. of510:1 : |w a |a Chicago (Ill.). |b Dept. of Planning670: : |a Chicago neighborhood development, 1992 |b (City of Chicago, Department of Planning and Development)670: : |a Project recommendations, 1996: |b t.p. (Dept. of Planning & Development, Chicago)675: : |a Its Major population groups in ... 1980?: t.p. (City of Chicago, Department of Planning) AACR2 record after re-coding: 008 961104n| azannaab| |a ana c010: : |a no 96057488 |z n 92099552 040: : |a IWhN |e <code meaning "AACR2; may not be used under RDA until modified">|c IWhN |d DLC110:1 : |a Chicago (Ill.). |b Dept. of Planning and Development410:1 : |a Chicago (Ill.). |b Dept. of Planning & Development410:1 : |a Chicago (Ill.). |b Planning and Development, Dept. of510:1 : |w a |a Chicago (Ill.). |b Dept. of Planning667: : |a THIS HEADING CANNOT BE USED UNDER RDA UNTIL IT HAS BEEN UPDATED670: : |a Chicago neighborhood development, 1992 |b (City of Chicago, Department of Planning and Development)670: : |a Project recommendations, 1996: |b t.p. (Dept. of Planning & Development, Chicago)675: : |a Its Major population groups in ... 1980?: t.p. (City of Chicago, Department of Planning) RDA record after migration: 008 961104n| azannaab| |a ana c010: : |a no 96057488 |z n 92099552 035: : |a (OCoLC)oca04198281040: : |a IWhN |e rda |c IWhN |d DLC110:1 : |a Chicago (Ill.). |b Department of Planning and Development410:1 : |a Chicago (Ill.). |b Department of Planning & Development410:1 : |w nnea |a Chicago (Ill.). |b Dept. of Planning and Development410:1 : |a Chicago (Ill.). |b Planning and Development, Department of510:1 : |w a |a Chicago (Ill.). |b Department of Planning670: : |a Chicago neighborhood development, 1992 |b (City of Chicago, Department of Planning and Development)670: : |a Project recommendations, 1996: |b t.p. (Dept. of Planning & Development, Chicago)675: : |a Its Major population groups in ... 1980?: t.p. (City of Chicago, Department of Planning) 5) 100 field acceptable for use under RDA as is, showing generation of 046 and 378 fieldsAACR2 record before migration: 008 940621n| acannaab| |n aaa c010: : |a nr 94020575 040: : |a NjP |c NjP100:1 : |a Stevens, Jonathan H. |q (Jonathan Hodgdon), |d 1959-670: : |a Analysis and modeling of infiltration and solute transport ... 1994: |b t.p. (Jonathan H. Stevens)670: : |a Info. from Princeton University Graduate School, 6-16-94 |b (Stevens, Jonathan Hodgdon, b. 9-9-59) RDA record after migration: 008 940621n| azannaab| |n aaa c010: : |a nr 94020575 040: : |a NjP |e rda |c NjP046: : |f <representation for " 1959">100:1 : |a Stevens, Jonathan H. |q (Jonathan Hodgdon), |d 1959-378: : |q Jonathan Hodgdon670: : |a Analysis and modeling of infiltration and solute transport ... 1994: |b t.p. (Jonathan H. Stevens)670: : |a Info. from Princeton University Graduate School, 6-16-94 |b (Stevens, Jonathan Hodgdon, b. 9-9-59) 6) Undifferentiated personal name otherwise acceptable for use under RDAThis example is prepared under the assumption that most AACR2 authority records for undifferentiated personal names will be split apart during the migration.AACR2 record before migration: 008 970228n| acannaabn |n aba 010: : |a n 97021312 035: : |a (OCoLC)oca04282928035: : |a (Uk)003362301040: : |a DLC |b eng |c DLC |d Uk |d IOrQBI |d Uk100:1 : |a Roberts, Elizabeth670: : |a [Author of Animal train]670: : |a Animal train, 1994: |b t.p. (Elizabeth Roberts)670: : |a [Author of Snwffyn a'r bêl bigog]670: : |a Snwffyn a'r bêl bigog, c1989: |b t.p. (Elizabeth Roberts)670: : |a [Author of After a fashion]670: : |a After a fashion, 2009: |b t.p. (Elizabeth Roberts) back jacket flap (editor of Black & white photography magazine; of Queen Elizabeth II published in 2008 and Margaret Thatcher published in 2009 by Ammonite Press)670: : |a [Author of Sitka spruce] 670: : |a Sitka spruce, c2002 |b verso t.p. (research & text by Elizabeth Roberts) Above record is deleted, and replaced by the following new records: 008 121231n| azannaabn |n aba 010: : |a <new 010> |z n 97021312 040: : |a DLC |b eng |e rda |c DLC100:1 : |a Roberts, Elizabeth670: : |a Animal train, 1994: |b t.p. (Elizabeth Roberts)008 121231n| azannaabn |n aba 010: : |a <new 010> |z n 97021312 040: : |a DLC |b eng |e rda |c DLC100:1 : |a Roberts, Elizabeth670: : |a Snwffyn a'r bêl bigog, c1989: |b t.p. (Elizabeth Roberts)008 121231n| azannaabn |n aba 010: : |a <new 010> |z n 97021312 040: : |a DLC |b eng |e rda |c DLC100:1 : |a Roberts, Elizabeth670: : |a After a fashion, 2009: |b t.p. (Elizabeth Roberts) back jacket flap (editor of Black & white photography magazine; of Queen Elizabeth II published in 2008 and Margaret Thatcher published in 2009 by Ammonite Press)008 121231n| azannaabn |n aba 010: : |a <new 010> |z n 97021312 040: : |a DLC |b eng |e rda |c DLC100:1 : |a Roberts, Elizabeth670: : |a Sitka spruce, c2002 |b verso t.p. (research & text by Elizabeth Roberts) Appendix E. Examples of changes to headingsEach group shows one currently-established heading in two forms: as given in the current version of its authority record, and as modified by the instructions in this document.100:1 : |a Schubert, Franz, |d 1797-1828. |t Quartets, |m strings, |n D. 804, |r A minor; |o arr.100:1 : |a Schubert, Franz, |d 1797-1828. |t Quartets, |m strings, |n D. 804, |r A minor; |o arranged130: 0: |a Bible. |p O.T. |p Jeremiah. |l Dutch130: 0: |a Bible. |p Jeremiah. |l Dutch130: 0: |a Bible. |p N.T. 130: 0: |a Bible. |p New Testament130: 0: |a Bible. |p N.T. |l Ewondo130: 0: |a Bible. |p New Testament. |l Ewondo130: 0: |a Occasional paper (University of Guelph. Dept. of Geography)130: 0: |a Occasional paper (University of Guelph. Department of Geography)100:1 :|a Jones, Alan, |d 1946 Nov. 2-100:1 :|a Jones, Alan, |d 1946 November 2-100:1: |a Jones, Amelia M., |d fl. 1853100:1: |a Jones, Amelia M., |d active 1853100:1 : |a Jones, Ambrose, |d d. 1678100:1 : |a Jones, Ambrose, |d -1678100:1 : |a Jones, Kelsey, |d 1922-2004. |t Selections100:1 : |a Jones, Kelsey, |d 1922-2004. |t Works. |k Selections130: 0: |a Koran. |l Greek130: 0: |a Qur’ān. |l GreekAppendix F. Impact on the LC/NACO Authority FileThe following assumptions prevailed during the gathering of the statistics reported in this appendix:Subfield $c in AACR2 personal name headings that may be used under RDA may include "Dame," "Sir", "Sr.", "Jr." or a roman numeral; other occurrences of subfield $c in AACR2 headings identify names that must be reviewed for use under RDAAuthority records for undifferentiated personal names should be split apart when possibleThe 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 typeRecordsRe-coded to RDARecords with changes other than re-coding Pre-AACR56,096010,046AACR126,28404,542AACR2 not re-codable218,258036,766AACR2 re-codable7,795,5207,795,5201,954,214AACR2-compatible42,194014,150RDA11,53402,124Other120011Total8,150,0067,795,5202,021,853As a result of the migration, 7,863,159 authority records (7,795,520 AACR2 records re-coded to RDA plus the following records changed but not re-coded: 10,046 pre-AACR, 4,542 AACR1, 36,766 excluded AACR2, 14,150 AACR2-compatible, 2,124 RDA, 11 other) will be modified in some manner. This represents over 96% of the 8,150,006 records in the LC/NACO Authority File; nearly the entire LC/NACO Authority File must be re-issued at some point as a result of the changes recommended in this document.The following table shows the reasons certain AACR2 records are not to be re-coded as RDA.Reason for exclusionRecordsChangedContain Polyglot688132Contain &14,6722,812Ongoing 111 conference70,443108Ongoing 110 conference13,260324Personal name with $c119,19533,390one more category: undifferentiated names that can’t be split (assuming the split)The following table shows the effect on headings of the mechanical changes described in sections 3.3, 3.4 and 3.5 of this document, and Appendix D.CategoryFields affected046 field created from 100/700 subfield $d1,633,681378 field added from 100/700 subfield $q425,600X00 arr. expanded3989X00 b. changed to trailing hyphen109,554X00 cent. expanded38,447X00 ca. expanded85,319X00 d. changed to leading hyphen116,425X00 fl. expanded56,404X00 violoncello replaced7,962X00 abbreviated month replaced6979X00 Selections changed23,609X10 arr. expanded2X10 Dept. expanded127,236X10 Dépt. expanded6X10 Selections changed7X11 Dept. expanded52X11 abbreviated month replaced2X11 Selections changed1X30 arr. Expanded9X30 testament removed from Bible heading1595X30 abbreviated testament expanded in Bible heading377X30 Dept. expanded2951X30 violoncello changed to cello3X30 Koran changed261X51 Dept. expanded3277XX deleted16,769Undifferentiated name records require review6,575Undifferentiated name records deleted49,556Undifferentiated name records created126,317Only 218,372 of the AACR2 1XX fields in those authority records that can be re-coded as RDA require some change. This means that under the criteria specified in this document all but about 2.8% of otherwise-acceptable AACR2 headings can be used under RDA without any change.Appendix G. Significant differences between 100 and 700 $aThe following list identifies those authority records whose 100 subfield $a differs (in a normalized comparison) from its 700 subfield $a. A few of these are simple errors (Tryon/Tyron); a few of the remainder might be useful in a project such as that envisioned in section 5.11.LCCN100 subfield $a700 subfield $aN 00099340vasquez g, magalyvasquez gonzalez, magalyN 2001059916lilienthal, m elilienthal, maxN 2002063029weissbrot, johannesweissbrodt, johannesN 2004017377gourley, d rgourley, dick rN 2004094107wills, a jwills, andy jN 2004103585kitinov, b ukitinov, baatr uN 2004116575evans, markaustad, mark evansN 2006001545menandermeananderN 2006001545menandermeananderN 2006019081vargas, joao helion costavargas, joao h costaN 50000674ristikivi, karlriistikivi, karlN 50002405ashley, michaelashley, mikeN 50009777sen, sukumarsena, sukumaraN 50011735tryon, thomastyron, thomasN 50017256barrault, jean louisbarrault, j lN 50022521primo de rivera, jose antoniojose antonioN 78008189rovira i planas, pererovira, pereN 78036676zosimoszosimusN 78088994holliday, john henryholliday, docN 79000823stanfield, j ronstanfield, james ronaldN 79018345guevara, ernestoguevara, cheN 79020254nelson, billnelson, william aN 79029972rubinshtain, shimonrubinstein, shimonN 79077964ortuzar s, juan de diosortuzar, juan de diosN 79083307bahya ben joseph ibn pakudabachja ibn josef ibn paqudaN 80011305konzhiev, nikolai mikhailovichkonzhiev, n mN 80015622resnick, michael dresnick michael dN 80043620challes, robertchasles, robertN 80044275linkov, vladimir iakovlevichlinkov, v iaN 80057167feshin, nikolai ivanovichfechin, nicolaiN 80059506moses israelfeldman, mosheh yisraelN 80063394ephraim fishl ben moses israelfeldman, efrayim fishlN 80087651keogh, james edwardkeogh, jimN 80094361canellas lopez, angelcanellas, angelN 80097546bateson, p p gbateson, patrickN 80102038milchin, arkadii emmanuilovichmilchin, a eN 80103825frolov, ivan timofeevichfrolov, i tN 80109211iashkin, ivan iakaulevichiashkin, i iaN 80125767chlenov, mikhail anatolevichchlenov, m aN 80144747rosetti, constantin alexandrurosetti, c aN 81011070paredes nunez, juanparedes, juanN 81019792kargalov, vadim viktorovichkargalov, v vN 81029903kuvakin, valerii aleksandrovichkuvakin, valeryN 81038417averintsev, sergei sergeevichaverintsev, s sN 81046348rubim, albinorubim, antonio albino canelasN 81047796rozhin, vasilii pavlovichrozhin, v pN 81053041malchow, howard lmalchow, h lN 81070061payne, stephen mpayne stephen mN 81077020bhattacaryya, jivananda vidyasagaravidyasagara, jivanandaN 81101944taylor, anne robinsontaylor, a rN 81123614majumdar, badiul alammajumadara, badiula alamaN 81123744voznesenskii, ndimitriiN 82002575trimbaciu, stefantrambaciu, stefanN 82013207razlogov, kirill emilevichrazlogov, k eN 82040797maksimov, v imaksimov, vladimir ivanovichN 82068348ruiz de la pena, juan ignacioruiz de la pena solar, juan ignacioN 82126597sahin, mehmet cetinsahin, m cetinN 82161885madsen, jakob schowschow madsen, jakobN 82225774lai, chuenyan davidlai, chuen yan davidN 82247568abi hasira, jacob ben masoudabihatsira, jacobN 82275102popescu vilcea, gpopescu valcea, gheorgheN 83024211sena, paritoshasen, paritoshN 83050824espino, gonzaloespino reluce, gonzaloN 83071792arueti, inaharuetty, inaN 83133988kopp, p ekopp, ekkehardN 83237837brants, keesbrants, kornelis louis karelN 84009577kidd, kathy hkidd, kathryn hN 84804640muntner, sussmannmuntner, zismanN 85099019cahoon, g acahoon, garth aN 85177403millet, robert lmillett, robert lN 85205607lochhaas, thomas alochhaas, tomN 85211137raza, sayed haiderraza, s hN 85230187melamed, avrahammelamed, abrahamN 85237581kieszczynski, lucjanlucjan kieszczynskiN 85283654parczewski, alfonsparczewski, a jN 85327029millas garcia, juan josemillas, juan joseN 85334705welch, d rwelch, danny rN 85338184mani, buddha rashmimani, b rN 85378924berke, wmberke, williamN 85387264pitt ford, t rpitt ford, thomas rN 85821775ramirez, carlos framirez aznar, carlos fN 86064228santos, antonio duarte dosduarte, antonioN 86087622zur lippe, ernstlippe weissenfeld, ernstN 86820578lafontaine, thomas plafontaine, tomN 86822899martinez reverte, javierreverte, javierN 86837278roggenkamp, gerhard heinrich wilhelmroggenkamp, gerhard h wN 87877078gorringe, timothygorringe, t jN 87887835baifus, yaakov yisraelbaifus, y yN 87891784lagos, maria ineslagos pope, maria inesN 87916674freericks, bernardfeericks, bernardN 88078221yamada, toruyamada, thoruN 88119150matsliah, talmazliah, talN 88121329ruso, nirahrousso, niraN 89123286look, p f a vanlook, paul f a vanN 89125617riviere, j edmondriviere, jim eN 91043711vasquez t, carlosvasquez tamayo, carlosN 91064236tsivian, yuritsivian, iu gN 91112390chapman, d achapman, davidN 93109017zavala, robertozavala maldonaldo, robertoN 93109466munoz quiros, j mamunoz quiros, jose mariaN 94087887sniegoski, tomsniegoski, thomas eN 94108343beck, georgette cbeck brandt, georgette cN 94117338cuadra l, elviracuadra, elviraN 95031343kent, steve lkent, steven lN 95044785munguia, dioniciomunguia, dionisioN 95087592ivanova, i aivanova, izolda anatolevnaN 95106763villavicencio, danielvillavicencio carbajal, daniel hN 96005617mungiu, alinamungiu pippidi, alinaN 96051323matvejev, sergej dmatvejev, sergije dN 96077889thornhill, c jthornhill, chrisN 97036245rantzer, philiprantser, philipN 98067685garner, jenny penickgarner, jenny lou penickN 98075565checa, franciscocheca y olmos, franciscoN 98803158falcone, tommasofalcone, tomassoN 99273836arjona, angelesarjona garrido, angelesN 99800441kingsnorth, a nkingsnorth, andrew nNB 99036685dalton, j pdalton, john pNB2001080021kozitskii, g vkozitskii, grigorii vasilevichNB2004014201kleinert, sabinekleinert, inge sabineNO 00022085desouza, davidde souza, davidNO 00068946majumadara, manasijamajumder, manasijNO 90016180mende, rana vonmende altayli, rana vonNO 95011756liria, carlos ffernandez liria, carlosNO 95027651meredith, m mmeredith, madison monroeNO2001019621berlichingen, adolf vonberlichingen, adolf gotz vonNO2001021541fortune, seanforturne, seanNO2001083942fowler, j efowler, jamesNO2002059525pockels, karl friedrichpockels, carl friedrichNO2003002527striphas, theodore gstriphas, tedNO2003017414burshtain, derorburstein, drorNO2003029121costa i font, joancosta font, joanNO2004123533kustov, s vkustov, sergei vladimirovichNO2005082258hadad, davidhaddad, davidNO2007055084polacco, joseph cpolacco, joe cNO2008075387payas, gertrudispayas puigarnau, gertrudisNO2009011096mash, samuel davidmash, s davidNO2010150218foster, john alexander hastingsfoster, j a hNO2010188617klain, yehudah ben yehielklain, yehudah yehielNO2011000987frolov, ivan timofeevichfrolov, i tNR 00010429fierro, merarifierro villavicencio, merariNR 00019204basok, moshehbassok, mosheNR 90021467barlev, yehiel avraham ben binyaminbarlev, yechiel avrahamNR 91029887ungar, shemuel davidungar, samuel dNR 92002952avigdor mordekhai ben avraham ezrakats, avigdor mordekhai ben avraham ezraNR 93035511abu shaqrah, faridabu shakra, faridNR 93050001grissgott, yehoshua hayimgrussgott, s cNR 95013089lissner, e elissner, ernest ernestovichNR 95013930rumi, ahmad ibn abd al qadirahmad al rumi al aqhisariNR 95040162burovskii, andrei mikhailovichburovskii, a mNR 96018918shisha, yosefschischa, josephNR 98015731hintze, f fhintze, ferdinand fNR2003026259melnikov, dmelnikov dNR2004016078kulefski, yaakov moshehkulefsky, y mNR2004028778argov, hagaiargov, haggaiNR2005001006zbylut, michelle lzbylut, michelle ramsdenNR2005006405warren, jerrylecotier, jaquesNR2007001446vaikhbroit, yehoshua elimelekh ben shemuel davidweichbrod, yehoshua ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download