Section I - 670 Field

This section is organized as follows:

1. Introduction and basic format

The 670 field is used to justify the heading and the cross references created. It may also contain further important information that is necessary to identify the person, corporate body, uniform title, or information that can be used to clarify relationships between the heading and other headings in the file.

At least one 670 field is required in each authority record. In most cases, it is necessary to create only a single 670 field, citing the work being cataloged and giving the form(s) of the name found therein.

In certain other cases, it will be necessary to create additional 670 fields, citing other sources where the name was found, such as bibliographic records in RLIN21, OCLC, and the Library and Archives of Canada, or in reference sources. It is not always necessary to include a 670 for every reference source consulted; use judgment in deciding what sources are important enough to retain in the permanent authority record.

A 670 is required to justify all elements of a heading and references. However, it is not necessary to add 670 fields to justify references in the following cases:

1. References justified by rules or rule interpretations only, usually because the reference is derived from inverting, shortening, etc., the heading or giving a substitute form in the heading.

2. References made on the basis of the cataloger's awareness of different romanizations or orthographies.

3. Name/title cross references derived from the work being cataloged, from other works cataloged under the same heading, or from information in standard reference sources.

4. References to earlier/later headings of corporate bodies reflecting changes due to national or orthographic reform, changes in government headings due to an official language change, or changes involving only a parent body to which the body being established is subordinate.

5. References made on the basis of information from the British Library as part of the English Short Title Catalogue project.

The 670 field for the work cataloged, normally the first 670 in the record, contains the following elements:

$a Title proper, imprint or other date: $b first location of data cited ([data found]) other location ([data found])

The main entry, formerly given as the first element of the 670, is no longer required. However, if the title is generic in nature ("Minutes," "Report," etc.) or the cataloger feels that the main entry adds pertinent information to the record, it may be cited. In cases where automated tools are used to assist in the generation of authority records, main entries may be added to 670 fields algorithmically; such entries may be left in place in the interest of saving time, or deleted at the cataloger’s discretion. The General Material Designation (GMD) is no longer cited in the 670. NOTE: Examples of past cataloging practices can be found in the LC/NAF.

Examples:

670 ## $a Die kleine Rodung, 1978: $b t.p. (Huguette Meier-David) p. 16 (Huguette Meyer-David; resident of Cologne)

670 ## $a Milne, D. Guitar concerto, p1984: $b label (The Chamber Music Players of London)

670 ## $a Etude sur les codes précision ... 1987: $b t.p. (Compagnie générale fiduciaire; C.G.F.; Dakar)

Examples for Archival Materials and Manuscripts:

If manuscripts or archival collections are being cataloged, no "location of data" is necessary. Normally, it will be necessary to cite the main entry, due to the generic nature of the "title":

670 ## $a Austin, W.L. Papers, 1855-1932 $b (Burnham, Parry, Williams & Co.)

670 ## $a Johnston, A. Papers, 1865-1948 $b (Bethlehem Iron Company; later became the Bethlehem Steel Corporation)

670 ## $a Fowler, A.V. Papers, 1923-1970 $b (Albert W. Fowler; Albert Wose Fowler; Quaker librarian & archivist; b. 1940, son of Albert V. & Helen W. Fowler)

670 ## $a Oberlin College. Office of Business and Finance. Records, 1927-1988 $b (Lewis R. Tower, appointed first business manager of Oberlin College in 1954; retired in 1971)

Examples for Publications Viewed Electronically:

In citations for publications viewed electronically, give information in $a in the context of the publication rather than how it was viewed; in $b, give location and information. For Internet resources used as reference sources, see section 15 below.

670 ## $a Dr. Bill’s get your fill diet, 2003: $b readme file (William P. McHugh, Ph.D.)

670 ## $a Cambridge Lear CD-ROM, c2001: $b title screen (Cambridge University Press) PDF file (University Printing House)

670 ## $a WebTrends 5.0, c2002: $b disc label (NetIQ Corporation) administrator’s guide (Net IQ Corporation) jewel case (NIC)

2. Citing the main entry (Optional)

Supplying a main entry or a substitute (e.g., his, her, its, author’s) is no longer a NACO practice.

NOTE: In authority records created using macros or an automated authority generation program, the 670 information may include the main entry name as it appears in the bibliographic record for which the authority record is being made. In order to maintain the cost effectiveness of this process, it is recommended that catalogers accept the additional information as generated.

Examples of any number of past citation practices can be found in the LC/NAF.

3. Citing the title

A. It is only necessary to cite the title proper; in most cases, other title information need not be given. However, if the title is relatively brief, cite it in full.

B. If the title is long, shorten it by abbreviating words or by using the 3-dot mark of omission after the first four or five words.

When shortening the title, do not obscure the subject area of the work.

Example of a Whole Title:

110 2# $a Bentley Historical Library

670 ## $a Guide to manuscripts in the Bentley Historical Library, 1976.

[Note that in this example, it is not necessary to give the name of the library in parentheses, since it appears in its full form in the title of the work. This is the only case where the $b and data in parentheses may be omitted; see 7. Citing the Data, A.1.]

Example of an Abbreviated Title:

670 ## $a Obstetrical Soc. of Phila. Records, 1946-1993 $b (Paul A. Bowers)

Example of a Mark of Omission:

670 ## $a The moral and intellectual diversity of races ... 1856: $b t.p. (H. Hotz)

4. Citing the imprint or other date

The format for citing the date in the 670 field is governed by how it appears in the bibliographic record for the work cataloged. Generally, they will be the same. The date in the authority record does not include brackets even when they are used on the bibliographic record. The following should also be included when citing the date:

Other symbols used, including the copyright "c" or phonogram copyright "p," question marks, and hyphens.

Multiple dates, if the bibliographic record has them.

The Gregorian date only, if the bibliographic record has both Gregorian and non-Gregorian dates.

Examples:

Bibliographic record:

260 ## $a London : $b Macmillan, $c 1986.

Authority record:

670 ## $a George Orwell, 1986: $b t.p. (Adrian Quine)

Bibliographic record:

260 ## $a Ky: $b BenridTaish15 [1926]

Authority record:

670 ## $a Shina kachsatsu, 1926: $b colophon (Tanaka Denzabur[in rom.])

Bibliographic record:

260 ## $a Washington : $b NASA, $c c1974, distributed 1975.

Authority record:

670 ## $a Apollo to the moon, c1974, distributed 1975: $b cover (Harry S. Galene)

5. Citing numeric/chronological designation

A. If the item cataloged is the first volume of a numbered multipart item, record the date of publication as an open date.

B. Generally, use a chronological designation instead of a publication date when giving a 670 for a serial other than a monographic series. If there is no designation date, use the numeric designation and the date of publication. Indicate, following the designation statement, if a surrogate was used.

C. Do not translate designation statements.

D. Capitalize the first word or abbreviation used with the numeric designation.

Examples:

If the work being cataloged is: The verdict, vol. 2, no. 1 (Feb. 1975)

cite as: 670 ## $a The verdict, Feb. 1975: $b t.p. ([data])

["Feb. 1975" is the designation date.]

Not 670 ## $a The Verdict, vol. 2, no. 1 (Feb. 1975): $b t.p.

670 ## $a Studies in Confederate history, no. 1 (1966), surrogate: $b t.p. ([data])

Not 670 ## $a Studies in Confederate history, 1966, surrogate: $b t.p. ([data])

670 ## $a A New image of man ... 1977- : $b pt. 1, p. i (International Research Institute for Man-Centered Environmental Sciences and Medicine)

6. Citing location of data found

The 670 field for the work being cataloged specifies the form(s) of the heading found in the piece and indicates where in the piece the forms are found. In these cases, add $b immediately after the date.

A. Generally cite the chief source of information first, followed, if necessary, by other sources. Note that when the cover, or any other source, substitutes for the chief source it will be cited as "t.p.", “disc label”, “container”, etc. Use standard terms and abbreviations including, but not limited to:

t.p.

jkt.

cover

verso t.p.

label

colophon

map recto

p. 3 of cover

back cover

title screen

disc label

jewel case

sleeve

container

home page

HTML header

B. If the information comes from a specific page of a print resource or digital reproduction of a print resource, cite the page. Omit brackets when citing unnumbered pages.

C. If the information comes from the cover of a print resource or digital reproduction of a print resource, cite as:

cover
(for front cover)

p. 2 of cover
(for inside front cover)

p. 3 of cover
(for inside back cover)

p. 4 of cover
(for back cover)

D. For numbered multipart print resources or digital reproductions of a multipart digital resource, include the volume number of the item with the specific location.

E. The cataloger may use "etc." to avoid giving more than two locations or a sequence of locations on a print resource or digital reproduction of a print resource (e.g., "p. 316, etc.").

Examples:

670 ## $a Conflict and cooperation in police labour relations, c1980: $b t.p. (Richard L. Jackson) p. 239 (Professor Rick Jackson, School of Business, Queen's Univ.)

670 ## $a Grunts, 1976: $b v. 1-3, t.p. (Charles R. Anderson) v. 2, p. 316, etc. (ex-Marine; b. Elgin, Ill.; teaches English in Japan)

670 ## $a CommerceTrends 3.0, c2002: $b disc label (WebTrends Corp.) user’s guide t.p. (Web Trends Corp.)

670 ## $a Harry Potter and the Chamber of Secrets, 2002: $b title screen (Chris Columbus) credits (Christopher Columbus)

7. Citing the data

A. General Information

1. Give the name as it appears in full in the source being cited (including the work being cataloged. If the entire heading (1XX) appears exactly the same in the title of the work cited, it is not necessary to repeat the heading in parentheses. This is the only case where the parenthetical statement may be omitted. (See 3. Citing the Title: example.)

2. Automated authority record generation programs may supply additional information from the bibliographic record from which the authority record is being made, e.g., complete statements of responsibility. In order to maintain the cost effectiveness of these programs, use judgment in deciding what information can remain in the $b and what is really extraneous to the record being created and should be deleted.

3. If the name or information about the name appears in the same form in different locations in a single source, do not repeat this information.

4. If the name cited is not in the nominative case, it is not necessary to amplify the citation to "explain" this, although a mark of omission may be used to indicate that surrounding words have been omitted.

5. All data must be given in standard romanized form. It is understood that any romanization transcribed is the cataloger's romanization. When transcribing a romanized form found in a non-roman item, add after it the bracketed phrase: [in rom.]. In such languages as Arabic and Hebrew, vowels are commonly omitted from the orthography of texts, and the cataloger supplies the missing vowels in transcribing data. When transcribing text that does include the vowels, add after it in brackets [voc.] or [part voc.] to note vocalization, as appropriate.

6. Data other than names should be given in as brief a form as possible. Abbreviate liberally. Generally translate data in foreign languages into English, paraphrasing or summarizing where possible. However, do not translate names and titles, or other distinguishing terms that could be used in the 1XX field to break a conflict.

7. To facilitate international contribution and use of records in the authority file, when giving dates use the abbreviated forms for months given in AACR Appendix B.15.

B. Personal Names

1. Record all forms of the name found on the chief source of the item being cataloged. Be selective about citing forms of the name not on the chief source. Record only those judged to add important information about the name (such as a fuller form) or those that justify cross references.

2. Cite birth and death dates explicitly whenever they appear in sources. Use abbreviated forms for months.

3. Do not translate distinguishing terms such as titles of address or office that appear with personal names in conjunction with the name in statements of responsibility or in reference sources that potentially could be used as part of the heading or in a reference. Distinguishing terms may be needed to resolve a conflict. Transcribe the terms as they appear.

Examples of Titles of Address:

kand. biol. nauk

Ph.D.

Rev.

Dr.

Prof. Dr.

Examples:

670 ## $a Acid rain and waterfowl, 1987: $b t.p. (Paul Hansen; Upper Miss. Reg. Repr., Izaak Walton League of Amer.) cover (Dr. Paul W. Hansen)

670 ## $a A History of Iowa, 1937: $b t.p. (Samuel S. Gribble) p. 105 (Rev. Gribble; b. July 7, 1861; d. Aug. 23, 1943)

670 ## $a A scuola da Bettina, 1986: $b t.p. (M. Elisabetta Mazza) p. 15 (Maria Elisabetta Mazza; family name, Bettina; b. Jan. 21, 1886) p. 206 (d. Aug. 29, 1950)

C. Corporate Names and Conference Names

1. In establishing corporate headings, when elements of a hierarchy not included in the heading appear in a source found, include in the data cited all the hierarchy required to justify needed cross references.

Each element of hierarchy in a heading or its cross references is established separately.

Examples:

110 2# $a San Francisco Widget Research Institute. $b Employee Benefits Division

410 2# $a San Francisco Widget Research Institute. $b Personnel Dept. $b Employee Benefits Division

670 ## $a Top U.S. widget executives benefit packages, 1986: $b t.p. (San Francisco Widget Research Institute, Personnel Department, Employee Benefits Division)

110 2# $a San Francisco Widget Research Institute. $b Personnel Dept.

670 ## $a Top U.S. widget executives benefit packages, 1986: $b t.p. (San Francisco Widget Research Institute, Personnel Department)

2. For conferences, generally record the place and date of the meeting, even if the qualifiers are not included in the heading being established.

Example:

111 2# $a Congreso Internacional de Tribunales de Cuentas

670 ## $a Memoria del Primer Congreso Internacional de Tribunales de Cuentas, 1954: $b t.p. (2. Congreso Internacional de Tribunales de Cuentas; held in Havana, 2-9 Nov. 1953)

8. Obsolete conventions for punctuation, spacing, abbreviations

NOTE: These guidelines are retained as historical information and for understanding information already present in 670 fields. Style and punctuation are no longer prescribed as of the 1996 revised DCM Z1.

A. Follow the date or edition statement of the source with a colon if the next element is the first unit of location. The date is followed by no punctuation if the next element is in parentheses. If an open date ending with a hyphen is being transcribed, follow it by a single space before the colon (e.g., 1909- :).

B. Do not use brackets around numbers for unnumbered pages, volumes, etc.

C. Information cited from the source as cited in the 670 in enclosed within parentheses.

D. Use a single space and no punctuation to separate the various locations and data. EXCEPTION: Use a semicolon to separate information cited from different issues of a serial.

E. Give citations of the name in full, but abbreviate other words liberally whenever the context makes the meaning clear.

Examples:

670 ## $a Looking at America's canyons, c1983: $b t.p. (P. Jonathan Phillips) cover p. 4 (Geology Dept. Chair, Univ. of British Columbia)

670 ## $a Police administration statistics, 1972: $b t.p. (Statistics Canada, Judicial Division); 1973/74: t.p. (Statistics Canada, Judicial Statistics Division)

670 ## $a RLIN, Aug. 31, 2000 $b (hdg.: Calisch, Edward Nathaniel, 1865-1946; usage: Edward N. Calisch)

670 ## $a The History of the Dakota Presbytery of the Presbyterian Church in the United States of America, 1892: $b t.p. (Presbytery of Dakota) p. 3 (org. 1844)

670 ## $a OCLC, Sept. 24, 2001 $b (hdg.: Harris, John Lowrey, 1953- ; usage: John Lowrey Harris)

670 ## $a Telephone call to author, June 12, 2005 $b (Christopher C.L. Murphy, b. Aug. 19, 1948)

9. Citing bibliographic records (LC and non-LC)

A. Full-level LC Bibliographic Records

If a search of the RLIN21 and/or OCLC bibliographic files retrieved any instances of pre-AACR2 usage of the heading on Library of Congress records input by LC (i.e., not transcribed by another library—see Appendices I & II on Identifying LC Bibliographic Records in RLIN21 and OCLC), record this in a 670 field. (For LC minimal level cataloging (MLC) records retrieved, see section 9, B.)

The information found in these records may be used, as appropriate, in formulating the heading.

The format for the 670 field citing LC in RLIN21 or OCLC is:

670 ## $a RLIN21, [date of search] $b (hdg.: [data]; usage: [data])

670 ## $a OCLC, [date of search] $b (hdg.: [data]; usage: [data])

670 ## $a LC database, [date of search] $b (hdg.: [data]; usage: [data])

(The last format is used if the library has accessed LC's catalog through the Internet.)

1. If the heading on the LC bibliographic record(s) match(es) the usage on the work being cataloged, generally consider the heading on the LC record to be AACR and do not examine or record the usage from the LC record. Use the heading from the LC record as the NACO heading.

NOTE: Usage on bibliographic records refers to literal transcriptions of the forms of name usually found in the statement of responsibility on a bibliographic record. Literal transcriptions may also appear in other parts of the bibliographic record, such as in the title proper or in a quoted note. Be sure to transcribe the name as it appeared on the publication and not as it was formulated because of cataloging rules. Variant refers to forms of the name other than usage.

Examples:

100 1# $a Grant, James, $d 1771 or 2-1833

670 ## $a The narrative of a voyage of discovery, 1803: $b t.p. (James Grant, lieutenant in the Royal Navy)

670 ## $a RLIN, Aug. 23, 1993 $b (hdg.: Grant, James, 1771 or 2-1833)

110 2# $a Asesoramiento y Gestión Económica, S.A.

410 2# $a AGECO

670 ## $a Datos básicos sobre la evolución, 1972: $b cover (Asesoramiento y Gestión Económica, S.A.) t.p. verso (AGECO)

670 ## $a OCLC, Feb. 19, 1993 $b (hdg.: Asesoramiento y Gestión Económica, S.A.)

2. If the heading on the LC bibliographic record(s) does not match the usage on the work being cataloged, consider the usage(s) on the LC records and on the item to determine the AACR heading. Often the pre-AACR2 forms will contain fuller forms of forenames or dates to be used as additions. Record both the LC heading and any usage(s) found. Use a semicolon to separate the heading from the usage.

Example:

100 1# $a Guillermin, Gilbert

400 1# $w nna $a Guillermin de Montpinay, Gilbert

670 ## $a Journal historique de la révolution de la partie de l'est de Saint-Domingue, 1810: $b t.p. (Gilbert Guillermin, chef d'escadron attaché à l'Etat-major de l'armée de Saint-Domingue)

670 ## $a RLIN, Aug. 24, 1993 $b (hdg.: Guillermin de Montpinay, Gilbert; usage: Gilbert Guillermin)

Do not code the $w control subfield to show that the tracing refers to a pre-AACR2 heading, if the database being searched is OCLC.

Example:

100 1# $a Phelps, Reginald H. $q (Reginald Henry)

400 1# $a Phelps, Reginald Henry

670 ## $a The German scientific heritage, 1962: $b t.p. (Reginald H. Phelps)

670 ## $a OCLC, Jan. 29, 1993 $b (hdg.: Phelps, Reginald Henry; usage: Reginald H. Phelps)

In this example, the cross reference is optional because the primary elements are not affected. See LCRI 26.2.

3. If a new heading would be the same as another one on pre-AACR2 records, try to resolve the conflict. For instance, add dates or qualifiers to the newly established heading if possible. If the conflict cannot be resolved, a non-unique name record will be needed.

B. Minimal-level LC Cataloging (MLC) Records and Less Than Fully Authenticated Serial Records

Authority work normally has not been done for headings used (1) in minimal level cataloging records which are indicated by a value of 7 in Leader/17 fixed field and (2) in serial records where the authentication field 042 does not contain either lc, lcd, or nlc. Headings in LC MLC records or less than fully authenticated serial records may or may not be properly established AACR forms. These headings should be verified to ensure that they conform to AACR and the LCRIs.

1. In preparing authority records, ignore MLC records and less than fully authenticated serial records unless the heading, usage, or statement of responsibility provides important information not found on the piece or in full-level, pre-AACR2 records.

2. Statements of responsibility found in these records should be taken into account as usage. However, these headings do not have equal status with those found on full-level, pre-AACR2 records, even when the statements of responsibility provide additional information.

For example, if the piece does not contain the author's birth date and there is both a full-level, pre-AACR2 heading on an LC bibliographic record without a birth date and an LC MLC record with a date, the AACR heading will not include the date. (See LCRI 22.17). The MLC heading with the date will be cited in the 670 field for informational purposes only.

However, if there is no existing full-level, pre-AACR2 bibliographic record and there is an LC MLC record with the date, the date will appear in the heading.

Format for MLC headings:

670 ## $a RLIN21, [date of search] $b (MLC hdg.: [data]; MLC usage: [data])

670 ## $a OCLC, [date of search] $b (MLC hdg.: [data]; MLC usage: [data])

Format for a combination of an MLC heading and a full-level heading in the same 670:

670 ## $a RLIN21, [date of search] $b (hdg.: [data]; MLC hdg.: [data]; MLC usage: [data])

670 ## $a OCLC, [date of search] $b (hdg.: [data]; MLC hdg.: [data]; MLC usage: [data])

Format for less than fully authenticated serial heading:

670 ## $a RLIN21, [date of search] $b (Less than fully authenticated serial hdg.: [data])

670 ## $a OCLC, [date of search] $b (Less than fully authenticated serial hdg.: [data])

Examples:

100 1# $a Charles, Lloyd, $d 1945-

670 ## $a Housing construction in Jamaica, 1988: $b t.p. (Lloyd Charles)

670 ## $a RLIN, May 27, 2002 $b (MLC hdg.: Charles, Lloyd, 1945- )

100 1# $a Houlihan, Diane, $d 1937-

670 ## $a United States foreign relations with China, 1987: $b t.p. (Diane Houlihan)

670 ## $a OCLC, Sept. 7, 1993 $b (Less than fully authenticated serial hdg.: Houlihan, Diane, 1937- )

110 2# $a Barrington & Wilder

410 2# $a Barrington and Wilder

670 ## $a Barrington & Wilder Records, 1875-1910 $b (Barrington & Wilder)

670 ## $a OCLC, July 20, 2001 $b (MLC hdg.: Barrington and Wilder; MLC usage: Barrington & Wilder)

C. Non-LC Bibliographic Records

NOTE: In constructing headings and references, and recording information, NACO participants may make use of all bibliographic records in the file against which the searching and cataloging is being done.

Non-LC libraries' records in RLIN21 and OCLC may be cited in 670 fields, and usage found in these records may be used in formulating the AACR heading.

The format for citing these records is the same as for full-level LC bibliographic records (see section A).

10. Citing reference sources

In certain cases AACR and the LCRIs require the cataloger to search reference sources beyond the work in hand. Examples: Headings for persons, LCRI 22.3B2 (Names in vernacular and Greek or Latin forms), 22.3C ("well established in English-language reference sources"), and 22.13B (saints); and geographic names, LCRI 23.2.

Further research is also needed to resolve conflicts. This will be especially important for common names and geographic names.

A. When doing extra research, record the information in a 670 field and take the information into account when formulating the heading.

B. Use abbreviations when citing standard reference sources, including a year of publication or edition. Include location of data found unless the reference source is a strictly alphabetized source, such as the Dictionary of American Biography, Who Was Who, or an encyclopedia. When using abbreviations, make sure they are understandable.

Examples:

670 ## $a Nat. fac. dir., 1987 $b (Elizabeth Jackson Hall; Loyola University Chicago, Ph.D., 1976; philosophy prof., Loyola University Chicago)

670 ## $a Brockhaus, 1974: $b Bd. 19, p. 823 (under Walkenried: Zisterzienserabtei W.; founded 1127)

670 ## $a New Cath. enc. $b (Guibert of Gembloux; Benedictine abbot; b. ca. 1125; d. Feb. 22, 1213; became abbot of Gembloux, 1193)

670 ## $a DAB $b (Adolph Papageorge Falcón; b. Mar. 16, 1963, Corpus Christi, Tex.; A.B., Yale Univ., 1985; M.P.P., Harvard Univ., 1987)

670 ## $a Martindale-Hubbell, 1992: $b v. 6, p. IL311P (Bruce, Joseph J.; b. 1952)

670 ## $a Baker, 8th ed. $b (Loewengard, Max Julius; b. Oct. 2, 1860, Frankfurt am Main; d. Nov. 19, 1915, Hamburg; German writer on music, teacher, and composer)

11. Citing the National Union Catalog (NUC)

Catalogers may need to consult the NUC when seeking additional information about a heading. Note that headings found in the NUC are not considered authoritative pre-AACR2 headings. If, however, the NACO member has genuine cause to search the NUC or NUC pre-1956 (primarily for resolving a conflict) and finds useful additional information, he should record the information found in a 670 field and in the 1XX, if appropriate.

Examples:

100 1# $a Hunt, John, $d 1775-1848

670 ## $a Report of the proceedings on an information filed ex officio ... 1811: $b t.p. (John Hunt)

670 ## $a NUC pre-56 $b (Hunt, John, 1775-1848)

100 1# $a Cater, Katherine, $d 1945-

670 ## $a Legal research for librarians, 1968: $b t.p. (Katherine Cater)

670 ## $a NUC 1968-72 $b (Cater, Katherine, 1945- )

12. Citing in-house files

It is possible to cite in-house (usually manual) files in a 670 field. Do not add full histories or biographies.

It is suggested that the NACO member use his institution’s MARC organization symbol, followed by the word "files," $b and data. It is not necessary to identify the type of file consulted. Do not give local call numbers or classification schemes in the citation.

Examples:

100 1# $a Freeman, Constant, $d 1757-1824

400 1# $a Freeman, Const. $q (Constant), $d 1757-1824

670 ## $a Letter from the secretary of the Navy, transmitting a statement of the expenditures and application of the moneys drawn from the treasury on account of the Navy, 1821: $b folded leaf (Const. Freeman, fourth auditor)

670 ## $a MWA/NAIP files, Dec. 12, 1995 $b (hdg.: Freeman, Constant, 1757-1824; note: joined U.S. Army, 1st lt., Nov. 9, 1776; reached rank of col.; hon. disch., June 15, 1815; auditor of the U.S. Navy Dept.)

100 1# $a Meeker, George H. $q (George Herbert), $d b. 1871

670 ## $a Biographical memoir of Edgar Fahs Smith, 1936: $b t.p. (George H. Meeker)

670 ## $a PU-Ar files, Jan. 21, 2000 $b (George Herbert Meeker; b. 1871)

100 1# $a Wallace, Robert J. $q (Robert John), $d 1846-1909

670 ## $a Trevor's taxes on succession, 1881: $b t.p. (Robert J. Wallace, of the Legacy and Succession Duty Office)

670 ## $a MoSU-L/NLT files, June 5, 1992 $b (hdg.: Wallace, Robert John, 1846-1909)

100 1# $a Richardson, Hannah White, $d 1811?-1882

670 ## $a White, J. Papers, 1796-1906 $b (Hannah White Richardson)

670 ## $a PHC files, May 15, 1999 $b (Hannah White Richardson; b. 1811?; d. 1882; Quaker author of spiritual works and founder and benefactor of Medical College of Pennsylvania)

13. Citing the BGN and other reference source for place names

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) (http://geonames.usgs.gov/index.html). 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 and New Zealand, base the heading on the form found on the GEOnet Names Server (GNS) (http://164.214.2.59/gns/html/index.html). A gazetteer published within the last two years may also be used when access to the World Wide Web is not available.

3. For names in Canada, use the heading provided by the Library and Archives of Canada (LAC). Search the AMICUS Web site (http://www.collectionscanada.ca/amicus/), if available, or further consult DCM Z1 Appendix for Canadian Headings.

4. For names in Great Britain, base the name on a recent edition of the Ordnance Survey Gazetteer of Great Britain. This resource is available online at http://www.ordsvy.gov.uk/. Select “Place name gazetteer” to begin a search.

5. For other names, base the heading on the form found in the work being cataloged together with consideration of the form found on GNS (or an appropriate gazetteer if access to the World Wide Web is not available).

6. For geographic names established on the basis of information from the United States Board of Geographic Names (BGN), convey a designated short form of name by adding within brackets immediately after the appropriate element the statement “[short form].” Repeat the short form if needed for clarity. (Do this even if the long form is chosen for the heading.) Retain the phrases “[conventional],” “[(language)],” etc. when used by BGN. Give the date of the search in the online file and include the feature designation (e.g. ADM1, PPL), coordinates, and variants. If searching the latest available gazetteer because online access is not available, do not include the date but do include the feature designation and coordinates. NOTE: In published gazetteers the short form is shown with the use of boldface type.

Examples:

670 ## $a BGN, May 13, 1989 $b (Coast [short form] Province; ADM1, 3°00'S 39°30'E)

670 ## $a BGN, July 7, 1992 $b (Varese [short form], Provincia di; PROV, 45°48'N 8°48'E)

670 ## $a GEOnet Oct. 7, 2003 $b (Macetown, PPL, NZ; 44°52'00'S, 168°58'00'E)

14. Citing non-bibliographic sources

Occasionally, the name of a personal author or a corporate body may be verified by telephone or other means. In such cases, record the information in a 670 field.

Give the non-bibliographic source, the date, and the information. The source can be given specifically ("Email from author," "Phone call to publisher," etc.) or in general terms ("information from author," "information from publisher," etc.). When noting a specific source, it isn't necessary to show how information was received, e.g., that a letter was received via FAX rather than via mail. When a telephone call to a publisher/agency/organization is cited, usually give the name of the group called, rather than the title or name of the person contacted.

Examples:

670 ## $a Phone call to Timber Mgt., May 12, 1993 $b (not same as United States, Forest Service, Timber Management Research; Timber Mgt. is subord. to National Forest System, a branch of Forest Serv.; Timber Mgt. Res. was subord. to Forest Serv. Research, a different branch of Forest Serv., and became Forest Management Research ca. 1991)

670 ## $a Personal communication from author, Sept. 1, 1993 $b (rare book cataloguer; b. Deborah J. Jackson on 26 July 1958)

670 ## $a Phone call to H. Jones, Jan. 31, 1992 $b (Harry Jones is the real name of Lionel James)

670 ## $a Information from publ., Feb. 6, 1991 $b (James Allan's middle name is Stephen, not Steven)

670 ## $a Email from U. Tex. at Arlington, Jan. 30, 1996 $b (James Edwin Thayer; Ph.D. in linguistics from Ind. U. 1973; M.S. in materials sci. from U. Tex. at Arlington in 1987)

15. Citing internet resources

Give the title or name of the Internet resource, an indication of the delivery mechanism, and the date it was consulted in $a. Titles or names should be taken from resource or constructed by the cataloger to best represent the site (see section 6). In $b, give the location, if appropriate, and the information found.

One of the three following constructions should generally be used to cite Web pages:

[Title or name] WWW site, [date of search]: $b [location] ([information])

[Title or name], via WWW, [date of search]: $b [location] ([information])

[Title or name] WWW home page, [date of search]: $b ([information])

In the above patterns, punctuation is not prescribed.

Examples:

670 ## $a British Oceanographic Data Centre WWW home page, Sept. 6, 2000 $b (BODC, est. Apr. 1989)

670 ## $a Family search, via WWW, Feb. 4, 2002 $b (Sarah Ann Whitney; b. 22 Mar 1825, Kirtland, Ohio; d. 4 Sep 1873, Salt Lake City, Utah; married Joseph Smith 27, Jul 1842 Nauvoo, Ill.; married Heber Chase Kimball 17 Mar 1845, Nauvoo, Ill.)

670 ## $a Centre for AIDS Development, Research and Evaluation WWW site, Dec. 14, 2004: $b contact us page (Kevin Kelly, research director)

670 ## $a Free on-line dictionary of computing, via WWW, Jan. 31, 2005 $b (Bill Gates; William Henry Gates III, CEO of Microsoft)

670 ## $a Advisory Committee on Gulf War Veterans’ Illnesses WWW site, July 2, 2003: $b HTML header (RAC-GWVI)

Using URLs is not preferred since addresses often change. Citing the URL is allowed in very rare cases when a title or name cannot be sufficiently determined or constructed.

The following construction is generally used to cite a Web page by its URL:

Internet, URL: [URL address],[date of search] $b ([information])

If a URL is given that includes a spacing tilde or a spacing underscore, replace the character with its corresponding hex code, preceded by a percent sign: %7E for spacing tilde; %5F for spacing underscore.