[yul-naco] Recap of recent rule changes

Tue Feb 14 18:21:25 EST 2006

Might be worth noting that LC has "a little list" of about 300 names CPSO 
plans to close off. "On February 6, 2006, CPSO will commence a special 
project to add death dates to a selected list of name headings. The project 
is expected to end by Summer 2006." See:
http://www.loc.gov/catdir/cpso/deathdates.html

At 04:23 PM 2/14/2006, you wrote:
>Dear NACO catalogers,
>
>A brief message went out on YULCAT-L recently announcing the latest issue 
>of Cataloger's Desktop and the rule changes that it contains. Since many 
>of these changes affect how headings get established, the NACO 
>Coordinating Committee thought it would be good to reiterate them here on 
>this list in greater detail. I've listed the major changes below and 
>copied the relevant documentation from the LCRIs, etc.
>
>Remember, too, that whenever a new issue of Cataloger's Desktop comes out, 
>you can see the latest updates in any resource (LCRIs, DCMZ1, etc.) by 
>going to that resource and clicking on the link on the title screen called 
>"Most Recent Update."
>
>Let me know if anything below isn't clear.
>
>Thanks,
>-Manon
>
>========================================
>1. Optionally, Add Death Dates to Headings with Open Birth Dates
>
>LCRI 22.17:
>Optionally, add death dates to headings that have open birth dates.
>Do not add the date (birth or death) to an existing heading without dates 
>represented by a name authority record that has already been coded "AACR2" 
>or "AACR2 compatible" (including in either case those labeled 
>"preliminary" -- 008 byte 33 = d). However, if such a heading must be 
>revised later, add the date(s).
>
>[Note: Please hold off on adding any death dates until a Yale policy has 
>been approved!]
>
>===========================================
>2. Include Diacritics on Initial Capital Letters in French, Spanish, and 
>Portuguese
>
>LCRI 1.0G.:
>Note: Prior to January 2006 catalogers did not add a diacritic to initial 
>capital letters in French, Spanish, and Portuguese. This exception no 
>longer applies. With respect to capital letters appearing at the beginning 
>of names or words, add diacritics according to the usage of the language. 
>When in current cataloging a change is otherwise needed to an existing 
>bibliographic or name authority record in these languages, catalogers are 
>asked to add the diacritic at the same time.
>With respect to acronyms, initialisms (including single capital letters 
>used in names), do not systematically add the accent. Instead:
>1)   for purposes of transcription, follow the usage as found in the data;
>2)   for purposes of establishing the authorized form of a corporate name, 
>follow the usage as found on the body's own publications.
>
>[Note: For existing records, no need to add the diacritic unless you are 
>updating the record for another reason]
>
>===================================================
>3. Optionally, Provide URI in Authority Record 670 $u
>
>MARC21 for Authority Records, LCGuidelines:
>NACO:
>As of January 2006, catalogers may supply a subfield $u in 670s of 
>Name/series authority records following the guidelines in Descriptive 
>Cataloging Manual Z1, supplement to the MARC 21 Format for Authority Data. 
>These guidelines suggest that a cataloger should use judgement in 
>supplying URIs because, 1) URIs are subject to rapid change thus incurring 
>an increased need for maintenance and 2) URIs are unnecessary when a 
>well-crafted 670 note provides enough information to identify the 1XX and 
>references.
>Do not use subfields:
>$6, $8
>
>DCM Z1 670, Internet Resources:
>Catalogers may optionally provide a uniform resource identifier (URI) in 
>the 670 citation to link to the cited resource if it contains significant 
>information related to the established heading that cannot be cited 
>succinctly in the authority record. Note that use of a URI in the 670 $u 
>does not take the place of the requirement to cite relevant data in 
>subfields $a and $b of the 670 field needed to support the heading or 
>references (this information will continue to be available if the site 
>changes or disappears). Do not provide URIs for general reference sources 
>and/or web-based reference sources that are included in the LCRIs (e.g., 
>Contemporary Authors online, GNIS, GEOnet, ). If a URI is included, it 
>must be given in subfield $u. If the URI contains a spacing tilde or a 
>spacing underscore, replace the character with its corresponding hex code, 
>preceded by the percent sign:
>
>%7E for spacing tilde
>%5F for spacing underscore
>
>[Note: URI stands for Uniform Resource Identifier and is another way of 
>saying URL; also, note that MARC21 Format for Authority Data has a tagging 
>error in the example it provides of a $u; the 678 should be a 670:
>
><http://desktop.loc.gov/nxt/gateway.dll?f=xhitlist$xhitlist_x=Advanced$xhitlist_vpc=first$xhitlist_xsl=querylink.xsl$xhitlist_sel=title;path;content-type;home-title$xhitlist_d=%7BMaauth%7D$xhitlist_q=%5Bfield%20folio-destination-name:%27100%27%5D$xhitlist_md=target-id=0-0-0-357>100 
>1# $aKing, Stephen, $d1947-
>678 ## $aThe official Stephen King web presence, viewed Oct. 26, 2001: 
>$bThe man (Stephen Edwin King; b. Portland, Maine, 1947) 
>$u<http://www.stephenking.com>http ://www.stephenking.com ]
>
>===================================================
>4. New Sources for Australian, New Zealand, and British Place Names
>
>LCRI 23.2. Sources
>Apply the following for current place names:
>1) For names in the United States, base the heading on the form found in 
>the Geographic Names Information System (GNIS), U.S. Geological Survey 
>(United States Board on Geographic Names (BGN) domestic names system). 
>GNIS may be accessed through the World Wide Web ( 
>http://geonames.usgs.gov/). A recent edition of the Rand McNally 
>Commercial Atlas and Marketing Guide may also be used when access to the 
>World Wide Web is not available.
>2) For names in Australia, base the heading on the form found in the 
>Geoscience Australia Gazetteer of Australia database ( 
>http://www.ga.gov.au/map/names/).
>3) For names in Canada, use the heading provided by the National Library 
>of Canada (NLC). Accept the NLC form, even if it differs from LC policy in 
>such matters as abbreviations, diacritics, fullness, qualifiers, etc. 
>Additional information on Canadian place names may also be found in 
>Natural Resources Canada's Canadian Geographical Names Data Base ( 
>http://geonames.nrcan.gc.ca/search/search_e.php).
>4) For names in Great Britain, base the name on a recent edition of The 
>Ordnance Survey gazetteer of Great Britain. Online access may be found at 
>http://www.ordsvy.gov.uk/. The site for searching a place name 
>is  http://www.ordnancesurvey.co.uk/oswebsite/site/help/index.html
>5) For names in New Zealand, base the heading on the form found in Land 
>Information New Zealand's New Zealand Geographic Placenames Database ( 
>http://www.linz.govt.nz/rcs/linz/pub/web/root/core/Placenames/SearchPlaceNames/searchplacenames/index.jsp 
>).
>6) For other names, base the heading on the form found in the work being 
>cataloged together with a consideration of the form found on GNS (or an 
>appropriate gazetteer if access to the World Wide Web is not available). 
>In all cases, a gazetteer published within the last two years may also be 
>used when access to the World Wide Web is not available.
>
>[Note: I have updated our existing web pages]:
>http://www.library.yale.edu/cataloging/authorities/geography.html
>http://www.library.yale.edu/cataloging/authorities/geog.htm
>
>============================================
>5. American Indian Tribes as 151 not 110
>
>LCRI 23.1. American Indian Tribes
>The appropriate MARC 21 field for names of U.S. government recognized 
>tribes as legal entities in name authority records will henceforth be the 
>151 (Geographic name) field instead of the previously used 110 (Corporate 
>name) field. This is in keeping with the guidance provided in rule 21.35 
>of the Anglo American Cataloguing Rules 2nd edition (AACR2) in regard to 
>treating tribal entities as national governments.
>
>Tribes recognized by the U.S. government are independent, autonomous 
>political entities with inherent powers of self-government; they possess 
>sovereignty and are equal to federal states. There are over 500 recognized 
>tribes within the continental United States. Virtually all federally 
>recognized tribes have jurisdiction over some delimited area of land, a 
>geographic place, although land and area vary with each tribe.
>
>When establishing headings for American Indian tribes of the United 
>States, consult the official list created and maintained by the Department 
>of the Interior, Bureau of Indian Affairs, published and updated in the 
>Federal Register. The list of federally recognized tribes published Nov. 
>25, 2005, entitled: Indian Entities Recognized and Eligible to Receive 
>Services from the United States Bureau of Indian Affairs is available at 
>http://frwebgate2.access.gpo.gov/cgi-bin/waisgate.cgi?WAISdocID=573025501103+5+0+0&WAISaction=retrieve 
>or http://www.loc.gov/catdir/cpso/biaind.pdf. Updated lists of tribal 
>entities from the Federal Register will be posted as received. This 
>source, the date of publication, and the date accessed should be recorded 
>in a 670 field in the name authority record and may be cited as "BIA 
>Indian Entities."
>
>Example of recognized tribe (complete name authority record fields not 
>provided):
>151 ## $a San Carlos Apache Tribe of the San Carlos Reservation, Arizona
>670 ## $a BIA Indian Entities, 2005, Dec. 14, 2005 $b (San Carlos Apache 
>Tribe of the San Carlos Reservation, Arizona)
>
>Some tribes have a federally approved name that sounds as if the name were 
>for a populated place rather than a tribe. Confusion may result when there 
>actually is a populated place of that name. In such cases, the tribe and 
>the populated place are separate entities, and both may be established as 
>needed.
>151 ## $a Native Village of Nunapitchuk
>151 ## $a Nunapitchuk (Alaska)
>
>===========================================================
>6. Qualify Forests and Parks Used as Main/Added Entries with (Agency)
>
>LCRI 24.1. Forests, Parks, Preserves, Etc.
>When a forest, park, preserve, etc. (commonly a unit of the United States 
>National Park Service or the United States Forest Service), is needed as a 
>main or added entry on a bibliographic record because the forest, park, 
>preserve, etc., has some responsibility for the intellectual content of 
>the item, create a name authority record for the forest, park, preserve, 
>etc., under its name as a corporate body and qualify the name with "(Agency)."
>
>110 2# $a Chugach National Forest (Agency)
>410 1# $a United States. $b Forest Service. $bChugach National Forest
>
>110 2# $a Aniakchak National Monument and Preserve (Agency)
>410 1# $a United States. $b National Park Service. $b Aniakchak National 
>Monument and Preserve
>
>===================================================
>7. Exceptions for Canadian Tribes and Canadian Forests and Parks
>
>DCM Z1 appendix 2, section 3.3: Corporate names exceptions:
>LAC has notified CPSO that all headings for Canadian parks and forests 
>will continue to be established as subject headings (cf. Subject 
>Cataloging Manual: Subject Headings, H1925, Parks, Reserves, National 
>Monuments) and therefore, do not fall under the guidelines provided in 
>LCRI 24.1 for U.S. parks and forests.
>LAC has also notified CPSO that Canadian First Nations will continue to be 
>established as 110 corporate name headings until further notice.
>
>===================================================
>8. Do Not Add $5 DPCC Code To Existing SARs
>
>DCM Z1 642 and 645:
>PCC participants: existing SAR
>(1) If the national-level decision is not in the SAR, do not add it.
>
>[Note: I have updated our Series Policy Doc]:
>http://www.library.yale.edu/cataloging/authorities/series_policy.htm
>
>
>
>
>
>_______________________________________________
>
>Manon Théroux
>Authority Control Librarian
>Catalog Department, SML, 2-8376
>________________________________________
>
>YUL-NACO Archives: http://mailman.yale.edu/pipermail/yul-naco/

----------------------------------------------------------
Steven Arakawa
Catalog Librarian for Training & Documentation
Catalog Dept. Sterling Memorial Library. Yale University.
P.O. Box 208240 New Haven, CT 06520-8240
(203)432-8286 steven.arakawa at yale.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.yale.edu/pipermail/yul-naco/attachments/20060214/b98ccad8/attachment-0001.htm