 |
 |
As a partial response to Wayne's question, Adam Schiff offers a couple of pages of guidance, with examples, on citing web resources in authority records in the SACO Participants' Manual. The principles would seem equally applicable to NACO work. As with any 670, surely the point is to be able to offer someone else looking at your citation some indication of what info you found and where, even if that "someone else" doesn't have access to the resource (in the case of print, because they don't have it, or can't spare the time to go retrieve it; in the case of online resources, because it's not where it was at the time the initial research was carried out). And I hope the folk at LC will forgive me for pasting here in full one of the FAQs relating to use of the 670 field. Note the final sentence... "Now that subfield $u has been implemented in the 670 field, it it OK to include URls at will in NARs? Within reason. Although subfield $u was authorized for use in NARs on February 1, 2006, NACO catalogers are expected to judiciously apply its use. Optional use of the 670$u should be for those cases when the source contains significant information related to the established heading that cannot be cited succinctly in the 670. Remember—citing a URI in 670$u does not take the place of the requirement to cite relevant data in subfields $a and $b of the 670 (i.e., enough information to support the heading/references, which will be available to future users even if the Internet site itself disappears)." http://www.loc.gov/catdir/pcc/naco/670faq.html#13 Hugh -- Hugh Taylor Head, Collection Development and Description Cambridge University Library West Road, Cambridge CB3 9DR, England email: [log in to unmask] fax: +44 (0)1223 333160 phone: +44 (0)1223 333069 (with voicemail) or phone: +44 (0)1223 333000 (ask for pager 036) Wayne Richter said - in whole or part - on 09/03/2007 16:46: > > > Sherman Clarke wrote: > > <<On to URLs. When you're establishing a heading, a website can be real > handy in identifying the nature of a body or how it names (brands) > itself, at least at the moment. > > In both cases though, the bibliographic or authority records cannot > entirely substitute for a new analysis of the situation. With our > friends Google and other browsers, that new analysis can be done when > we need to do it. A 670 with a solid explanation of the website where > you found the information may be more helpful as a guide to a browser > search than a URL gone bad. That is, it is better in the long term to > say "Comune di Vicenza WWW home page" > than "http://www.comune.vicenza.it/">> > > In my opinion, Sherman is right on target with the above comments. > > I frequently use web sites for untangling corporate body relationships > and history, and they are especially useful for government agencies. I > have recently been cleaning up a number of Mongolian governmental and > non-governmental corporate body authority records which would be > extremely difficult without the official web sites. I usually use the > history pages which may be in Mongolian, English or both. These are not > overly useful for determining names if in English only (e.g. English > "Institute" can be translation of a number of different Mongolian words > depending on the structure of the organization to which it belongs), but > still useful for history. In citing these in 670s I usually use "history > page" or "history pages" following the name of the web site, and > followed by the date viewed. I rarely find the information I need on the > home page so I wonder if this is common and recommended practice (i.e. > citing particular areas of a web site)? > > Thank you. > > Wayne Richter > Asian Materials Specialist/PCC Liaison > The Libraries > Western Washington University > Bellingham, WA 98225-9103