<html>
<body>
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:<br>
<a href="http://www.loc.gov/catdir/cpso/deathdates.html" eudora="autourl">
http://www.loc.gov/catdir/cpso/deathdates.html<br><br>
</a>At 04:23 PM 2/14/2006, you wrote:<br>
<blockquote type=cite class=cite cite="">Dear NACO catalogers,<br><br>
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. <br><br>
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."<br><br>
Let me know if anything below isn't clear.<br><br>
Thanks,<br>
-Manon<br><br>
========================================<br>
1. Optionally, Add Death Dates to Headings with Open Birth Dates<br><br>
LCRI 22.17:<br>
Optionally, add death dates to headings that have open birth dates.<br>
<a name="0-0-0-10709"></a>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).<br>
<br>
[Note: Please hold off on adding any death dates until a Yale policy has
been approved!]<br><br>
===========================================<br>
2. Include Diacritics on Initial Capital Letters in French, Spanish, and
Portuguese <br><br>
LCRI 1.0G.:<br>
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.<br>
With respect to acronyms, initialisms (including single capital letters
used in names), do not systematically add the accent. Instead:<br>
1) for purposes of transcription, follow the usage as found
in the data;<br>
2) for purposes of establishing the authorized form of a
corporate name, follow the usage as found on the body's own
publications.<br><br>
[Note: For existing records, no need to add the diacritic unless you are
updating the record for another reason]<br><br>
===================================================<br>
3. Optionally, Provide URI in Authority Record 670 $u <br><br>
MARC21 for Authority Records, LCGuidelines:<br>
NACO:<br>
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. <br>
<a name="0-0-0-17661"></a>Do not use subfields:<br>
<a name="0-0-0-17663"></a>$6, $8<br>
<br>
DCM Z1 670, Internet Resources:<br>
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:<br><br>
%7E for spacing tilde<br>
%5F for spacing underscore<br><br>
[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: <br>
<a name="0-0-0-12105"></a><br>
<a name="0-0-0-12107"></a>
<a href="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</a><a name="0-0-0-12107"></a> 1# $aKing, Stephen, $d1947-<br>
<a name="0-0-0-12109"></a>678 ## $aThe official Stephen King web
presence, viewed Oct. 26, 2001: $bThe man (Stephen Edwin King; b.
Portland, Maine, 1947) $u<a href="http://www.stephenking.com">http</a>
://<a href="http://www.stephenking.com/" eudora="autourl">
www.stephenking.com</a><a name="0-0-0-12109"></a> ]<br>
<br>
===================================================<br>
4. New Sources for Australian, New Zealand, and British Place
Names<br><br>
LCRI 23.2. Sources<br>
Apply the following for current place names:<br>
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 (
<a href="http://geonames.usgs.gov/" eudora="autourl">
http://geonames.usgs.gov/</a>). 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.<br>
2) For names in Australia, base the heading on the form found in the
Geoscience Australia Gazetteer of Australia database (
<a href="http://www.ga.gov.au/map/names/" eudora="autourl">
http://www.ga.gov.au/map/names/</a>).<br>
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 (
<a href="http://geonames.nrcan.gc.ca/search/search_e.php" eudora="autourl">
http://geonames.nrcan.gc.ca/search/search_e.php</a>).<br>
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
<a href="http://www.ordsvy.gov.uk/" eudora="autourl">
http://www.ordsvy.gov.uk/</a>. The site for searching a place name
is
<a href="http://www.ordnancesurvey.co.uk/oswebsite/site/help/index.html" eudora="autourl">
http://www.ordnancesurvey.co.uk/oswebsite/site/help/index.html</a><br>
5) For names in New Zealand, base the heading on the form found in Land
Information New Zealand's New Zealand Geographic Placenames Database (
<a href="http://www.linz.govt.nz/rcs/linz/pub/web/root/core/Placenames/SearchPlaceNames/searchplacenames/index.jsp" eudora="autourl">
http://www.linz.govt.nz/rcs/linz/pub/web/root/core/Placenames/SearchPlaceNames/searchplacenames/index.jsp</a>
).<br>
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.<br><br>
[Note: I have updated our existing web pages]:<br>
<a href="http://www.library.yale.edu/cataloging/authorities/geography.html" eudora="autourl">
http://www.library.yale.edu/cataloging/authorities/geography.html</a><br>
<a href="http://www.library.yale.edu/cataloging/authorities/geog.htm" eudora="autourl">
http://www.library.yale.edu/cataloging/authorities/geog.htm</a><br><br>
============================================<br>
5. American Indian Tribes as 151 not 110 <br><br>
LCRI 23.1. American Indian Tribes<br>
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.<br><br>
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.<br><br>
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
<a href="http://frwebgate2.access.gpo.gov/cgi-bin/waisgate.cgi?WAISdocID=573025501103+5+0+0&WAISaction=retrieve" eudora="autourl">
http://frwebgate2.access.gpo.gov/cgi-bin/waisgate.cgi?WAISdocID=573025501103+5+0+0&WAISaction=retrieve</a>
or
<a href="http://www.loc.gov/catdir/cpso/biaind.pdf" eudora="autourl">
http://www.loc.gov/catdir/cpso/biaind.pdf</a>. 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."<br><br>
Example of recognized tribe (complete name authority record fields not
provided):<br>
151 ## $a San Carlos Apache Tribe of the San Carlos Reservation,
Arizona<br>
670 ## $a BIA Indian Entities, 2005, Dec. 14, 2005 $b (San Carlos Apache
Tribe of the San Carlos Reservation, Arizona)<br><br>
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.<br>
151 ## $a Native Village of Nunapitchuk<br>
151 ## $a Nunapitchuk (Alaska)<br><br>
===========================================================<br>
6. Qualify Forests and Parks Used as Main/Added Entries with
(Agency)<br><br>
LCRI 24.1. Forests, Parks, Preserves, Etc.<br>
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)."<br><br>
110 2# $a Chugach National Forest (Agency)<br>
410 1# $a United States. $b Forest Service. $bChugach National
Forest<br><br>
110 2# $a Aniakchak National Monument and Preserve (Agency)<br>
410 1# $a United States. $b National Park Service. $b Aniakchak National
Monument and Preserve<br><br>
===================================================<br>
7. Exceptions for Canadian Tribes and Canadian Forests and Parks<br><br>
DCM Z1 appendix 2, section 3.3: Corporate names exceptions:<br>
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.<br>
LAC has also notified CPSO that Canadian First Nations will continue to
be established as 110 corporate name headings until further
notice.<br><br>
===================================================<br>
8. Do Not Add $5 DPCC Code To Existing SARs<br><br>
DCM Z1 642 and 645:<br>
PCC participants: existing SAR<br>
(1) If the national-level decision is not in the SAR, do not add
it.<br><br>
[Note: I have updated our Series Policy Doc]:<br>
<a href="http://www.library.yale.edu/cataloging/authorities/series_policy.htm" eudora="autourl">
http://www.library.yale.edu/cataloging/authorities/series_policy.htm</a>
<br><br>
<br><br>
<br><br>
_______________________________________________<br><br>
Manon Théroux<br>
Authority Control Librarian <br>
Catalog Department, SML, 2-8376 <br>
________________________________________<br><br>
YUL-NACO Archives:
<a href="http://mailman.yale.edu/pipermail/yul-naco/" eudora="autourl">
http://mailman.yale.edu/pipermail/yul-naco/</a> </blockquote>
<x-sigsep><p></x-sigsep>
----------------------------------------------------------<br>
Steven Arakawa <br>
Catalog Librarian for Training & Documentation<br>
Catalog Dept. Sterling Memorial Library. Yale University.<br>
P.O. Box 208240 New Haven, CT 06520-8240 <br>
(203)432-8286 steven.arakawa@yale.edu<br>
</body>
</html>