DCM Z1:  670  Source Data Found

LC series practice:  As of June 1, 2006, LC does not create or update SARs.

PCC series practice:  Transcription of the series statement is mandatory if applicable.  Searching for series authority records, tracing the series, and the creation and maintenance of series authority records are optional.

This 670 section covers the following topics:

Introduction

Format of 670 fields

Recording names and titles

Recording dates

Justifying variant access points

Justifying other elements

Recording other data

Special types of citations

Introduction:

The purpose of this field is to record information about the name or title represented in the 1XX field.  It includes facts that contribute to the identification of the entity, that justify the choice of the name or title and any additional elements used to construct the authorized access point (1XX).  The information also justifies, as needed, variant forms of the name or title (4XX), other identifying elements (046 and 3XX), and clarifies relationships between the 1XX and other entities in the file.

Functions of the 670 field:

To record information, from sources (e.g., books, phone calls, websites), in support of the choice and form of the authorized access point, variants, and other identifying elements.

To store information that may be used to break a conflict later.

To record information on relationships between entities (e.g., a person is the author of a work, a corporate body was absorbed by another corporate body).

To identify a person with works in diverse subject areas or of diverse forms.

To identify different individuals whose access points must remain identical for now (i.e., undifferentiated personal names).

To clarify whether different forms of a name or of a title are simply variations or reflect a change in the name or title.

To record research required by the current guidelines.

To facilitate authority and bibliographic file maintenance, i.e., the information in 670 fields aids in making decisions about duplicate authorized access points and misattributions.

To support machine manipulation based on algorithms using information in the 670.

The examples given throughout the following text have various conventions in regard to punctuation and style.  These conventions are not prescriptive and should be considered as best practices to facilitate the exchange of information in a shared database environment.  Catalogers are expected to use judgment and common sense.  Punctuation and style need not be consistent from record to record as long as the information is clear and accurate.

Generally, the first 670 field cites the resource for which the authority record is being established, i.e., the resource being cataloged; give subsequent 670 fields in any order, adding new fields after existing ones.  Do not routinely delete or change existing 670 fields when adding new 670 fields.

If the resource being cataloged or consulted provides no information to justify the authorized access point, variants, or other elements recorded in the NAR, see the 675 section of DCM Z1 for instructions on citing the resource in a 675 field.

It is not necessary to include a 670 field for every reference source consulted; use judgment in deciding what sources are important enough to retain in the permanent authority record.  For example, an NAR does not serve as a biographical sketch of a person, nor as an account of the detailed history of a corporate body.

Format of 670 fields:

General

With the exception of the eszett (ß or ſʒ) and the euro sign (€), all characters found in the MARC code table:  http://www.loc.gov/marc/specifications/specchartables.html, are valid for use in authority records contributed to the LC/NACO Authority File (cf. LC-PCC PS 1.4).

If a substitution for a symbol that cannot be reproduced is given in brackets, an explanation of that interpolation may also be provided (c.f. LC-PCC PS 1.7.5).

Example:

670  ##  $a Poch, Dina K. I [love] my in-laws, 2007: $b t.p. (I [love] my in-laws; “[love]” appears as a heart symbol on the t.p.)

Data must be given in romanized form.  Normally it is understood that the cataloger has provided the romanization; therefore, when transcribing romanization found in the source, add after it the bracketed phrase [in rom.].  If a cataloger chooses to provide nonroman script variant access points, the 670 $b should contain both the nonroman script transcription(s) found in the source, and the systematically romanized form(s).

In such languages as Arabic and Hebrew, where vowels are commonly omitted from the orthography of texts, the cataloger supplies the missing vowels when transcribing data.  When transcribing text that does include the vowels, add after it in brackets [voc.] or [part voc.] as appropriate.

When authority records are created using automated authority generation programs, additional information may be included.  This data may also be formatted in a different way than instructed in this document.  Generally, this data should be retained as generated to maintain the cost effectiveness of this process unless the data is confusing or causes validation errors.  The exceptions to this are 1) names and titles for which NARs are created and 2) BGN citations.  Follow the instructions in those sections for recording this data.

Subfield $a - Source citation

A 670 field should include the following data in subfield $a:

1.   The title proper of the resource being cited, complete enough for later identification in an online catalog.  Abbreviations and ellipses may be used.  Precede a generic or indistinctive title with the creator's name that would begin the authorized access point for the work.  If the authorized access point for the work is the same as the title proper plus a qualifier, it may be provided instead of the title proper to avoid ambiguity.  When information in subfield $a of a 670 field is provided to justify an authorized or variant access point, follow the additional instructions at Recording names and titles.

2.   The date of publication.

Examples:

670  ##  $a Barlow, Nadine G. Mars, 2008: $b t.p. ([data])

670  ##  $a Socialism (Routledge (Firm)), 2003: $b t.p. ([data])

Also see the guidelines below for specific categories:

Multipart monographs.  If the part is the first part, give the date of publication as an open date.

Serials other than monographic series.  Generally, use a chronological designation instead of a publication date.  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.

670  ##  $a The Verdict, February 1975: $b t.p. ([data])

not

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

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

not

670  ##  $a Studies in Confederate history, 1966, surrogate: $b cover ([data])

Integrating resources.  Apply the instructions at RDA 2.2.4.2 for source of the title proper of a website.  Identify the iteration from which information was taken (e.g., "viewed on" dates for updating websites, update number or release number for updating loose-leafs).

670  ##  $a Internet Broadway database, viewed on Jan. 21, 2003: $b about IBDB (League of American Theatres and Producers)

Subfield $b - Information found

A 670 field should include the following data in subfield $b:

1.   The specific location(s) of the information found.  For multipart resources with numbered parts, provide the designation of the part and the location within the part (e.g., v. 6, page 10; map recto, label).  Abbreviations may be used (e.g., t.p., jkt., v.6).

2.   Information found.  Following the location, cite the information found there, enclosed in parentheses.  As appropriate, give multiple occurrences of information from the same source following the location of the information.  (NOTE:  In SARs the parenthetical statement of the form of title proper was omitted until June 1989.)

Examples:

670  ##  $a The complete guide to creating enduring festivals, 2015: $b t.p. (Dr. Ros Derrett, OAM) p. xi (Roslyn Derrett)

670  ##  $a Da real world, 1999: $b container (Beyoncé)

670  ##  $a The World Book encyclopedia, 2010: $b v. 17, p. 106 (Sand, George; 1804-1876; pen name of Amantine-Lucile-Aurore  Dupin)

Also see the guidelines below for specific categories:

ECIPs.  If the authorized access point (1XX) is being constructed from an ECIP at the galley stage, precede the first location with "ECIP" (e.g., ECIP t.p., ECIP data view).

670  ##  $a Arts-based research in education, 2008: $b ECIP t.p. (Richard Siegesmund) galley (associate prof. in the Lamar Dodd School of Art, Univ. of Georgia)

Integrating resources.  For websites, provide the name of the location within the website if appropriate (e.g., about us; history, time line; government, executive branch).

670  ##  $a Amistad Research Center (Website), viewed on May 23, 2016: $b history of the center (Amistad Research Center; established in 1966)

Multiple locations within a resource.

---   NARs.  For NARs, generally, use "etc." to avoid giving more than two locations or a sequence of locations (e.g., p. 316, etc., for sequence p. 316-325, 329-331).

670  ##  $a Drevon, André. Alice Milliat, 2005: $b t.p. (Alice Milliat) p. 9, etc. (b. Alice Joséphine Marie Million on May 5, 1884 in Nantes; d. May 19, 1957; female athlete)

---   SARs.  For SARs, always give each location separately.

NOTE:  Specific location was not given on "n42-" (retrospective) SARs.

PCC series practice:  In post-cataloging authority work without the piece in hand, use the location "resource not in hand."  If the piece is examined again and the authority record is updated, it is allowable to edit the corresponding 670 field to provide a location and additional forms of series titles as needed.

670  ##  $a From child to adult, 1970: $b resource not in hand (American Museum sourcebooks in anthropology)

Subfield $u - Uniform Resource Identifier and Subfield $v - Source of the information

Follow the LC/PCC practice for subfield $u and subfield $v provided in the 046 field.

Catalogers may optionally provide a uniform resource identifier (URI) in subfield $u of the 670 citation to link to the cited resource if it contains significant information related to the established entity 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 authorized access point (including additions) or variants (this information will continue to be available if the site changes or disappears).  However, information found in online sources may be added to the 046 or 3XX fields with the appropriate citations in subfields $v and $u and not repeated in a 670 when that information is not used in the 1XX or a 4XX.  If a URI is included in a 670, it must be given in subfield $u.

Example:

670  ##  $a British Oceanographic Data Centre, viewed on 23 November 2009: $b about us (British Oceanographic Data Centre, National Environment Research Council; BODC, is a national facility for looking after and distributing data concerning the marine environment) $u http://www.bodc.ac.uk/

Recording names and titles:

Record names or series titles used in the authorized access point or variant access points in full, as they appear in the source, without abbreviation by the cataloger.

When preparing an authority record for the text of a law or a subject compilation of laws, if a source being cited contains an official short title or citation title, cite that title, preceded by the term "citation title" and its exact location, e.g.,

670  ##  $a Workers' compensation law of the state of North Carolina, c1980: $b t.p. (Workers' compensation law of the state of North Carolina) citation title, p. 49 (The North Carolina Workers' Compensation Act)

For corporate name authorities, include in the data cited all the hierarchy required to justify needed variant access points.  Use judgment in deciding what information (e.g., subordinate body's name) is extraneous to the record being created and should not be recorded.

For all of the above categories, if the only presentation of the name or title on the chief source of information is in the bibliographic title given in subfield $a of the 670 citation, repetition of the name in subfield $b may be omitted, provided no important information is lost.

If information about an earlier or later name or title is found in the same source as the name or title in the authorized access point, give all the information in the 670 field.  Do not separate the information about the earlier or later name or title and give it in a 675 field.

670  ##  $a Strafvollzug, 1985: $b t.p. (Rechtsgeschichte) p. 2 (Continues: Veröffentlichungen / Justizministerium Nordrhein-Westfalen)

Recording dates:

To facilitate international contribution and use of authority records, when giving record dates, generally use the spelled out or abbreviated forms for months as the U.S. practice for recording dates using numerals differs from the practice in some other countries.  (For dates recorded using automated authority generation programs, see the Format of 670 fields section of this document.)  Do not change the style of dates in existing records.  As a best practice, if a date is not included in subfield $d of the 100 field, consider adding a 046 field if dates are available.

Justifying variant access points:

Justify names or titles given as variant access points by information cited from sources.  However, justification is not required in the following cases:

1.   Variant access points made on the basis of the cataloger's awareness of different romanizations or orthographies;

2.   A variant title derived from the resource being cataloged, from other resources cataloged under the same access point, or from information in standard reference sources;

3.   References for authorized access points of corporate bodies reflecting changes due to national orthographic reform, changes in names due to an official language change, or changes involving only a parent body to which the body being established is subordinate.

4.   Optional references from AACR2 or pre-AACR2 forms on SARs and on retrospective NARs.

Justifying other elements:

Information recorded in the 046 or 3XX of the authority record should generally be justified unless it is otherwise obvious from information recorded in subfield $a of a 670 citation or it can be easily inferred from other identifying elements recorded, including the preferred name.

For the 046 field and many of the 3XX fields, a subfield $u or subfield $v recorded in the same field may be used instead of or in addition to a 670.  See the 046 section of this document for guidelines on subfield $u and subfield $v.

Recording other data:

NARs.  Use judgment to determine how much data to record in the permanent authority record.  Do not abbreviate or translate attributes such as title of the person (RDA 9.4) that appear in conjunction with personal names in statements of responsibility and that potentially could be used as part of the access point.  Other data may be abbreviated or summarized.  Generally informally translate other data from foreign languages into English, paraphrasing or summarizing as convenient.

SARs.  Use judgment to determine how much data other than forms of the title/phrase to record in the permanent authority record.  Numbering and names of issuing bodies are not required but may be given.

Special types of citations:

The most commonly occurring citations are listed below.  If these are not appropriate, devise others as needed.

LC/NAF

When converting information found in obsolete or non-active MARC fields (e.g., 664, 665, 666) into a 670 note, cite the LC/NAF in a citation such as those provided in the examples below:

670  ##  $a Info converted from 665 field in this record, [date of conversion] $b ([data converted from 665 field])

670  ##  $a 665 info formerly in this record $b ([data moved from 665 field])

LC database

For LC catalogers not working in OCLC, "LC database" as used in a 670 subfield $a equals name and series authority records and bibliographic records with the following values in the 906 $b:  cbc, cbu, rip, par, and vip.  Note that PREMARC records are now included in those categories of bibliographic records.  (LC catalogers:  See the separate document about policy decisions related to local authority control and PREMARC records.)

For LC catalogers working in OCLC and for NACO participants, there is no change in what is considered to be the "LC database" as used in 670 subfield $a.

NARs.  Give the date of the search, using month abbreviations.  In parentheses, prefaced by the label access point: (or MLC access point: if appropriate), give the access point (or access points) found, even if it is the same as the current authorized access point.

If different forms of the name appear in the bibliographic records, record the access point and also any forms found, including usage identical to the authorized access point.  Separate the access point from the other forms, and preface the other forms with an appropriate label, e.g., usage: or non-transcribed form:.  Do not normally cite specific bibliographic records or the exact location of the variations found.

670  ##  $a LC database, Jan. 5, 2015 $b (access point: Smith, Julius Harold, 1924-; usage: J. Harold Smith)

670  ##  $a LC database, Mar. 11, 2016 $b (access point: Swedish American Corporation; non-transcribed form: Swedish American Corp.)

SARs.  Give the date of the search, using month abbreviations, followed by the citation of the bibliographic record.  In parentheses give the series statement found in that record.

670  ##  $a LC database, Nov. 28, 1983, Les Déchets ménagers, c1980 $b (Les cahiers de l'AGHTM)

Minimal level cataloging records and less than fully authenticated serial records

Authority work normally has not been done for access points used in minimal level cataloging records and less than fully authenticated serial records (authentication field 042 does not contain any one of the codes lc, lcd, nlc, or gpo).  It may be necessary to reconsider the construction of the authorized access point.  If the authorized access point is different, do necessary bibliographic file maintenance.  Also, an MLC or less than fully authenticated serial record might provide useful information, such as a birth date not given elsewhere or usage not otherwise available.  Do not routinely cite MLC access points.  However, when the information is useful, document its source in the 670 field, e.g., MLC access point: or Less than fully authenticated serial usage:

LC manual authority card

LC practice:  When formulating the 670 citation for a manual authority card citation, use either LC manual auth. cd. or LC manual cat. (i.e., authority and bibliographic records) as appropriate.  Summarize and record data found, without specifying individual works cited on the manual authority card or other sources of information which may have been mentioned there.

Citing other files or catalogs

If an access point is found in a manual catalog or online database, use judgment in creating a 670 citation.  Begin the 670 field with a designation of the catalog/database in which these other bibliographic records were found.  There is no prescribed formulation of such citations; examples are listed below:

670  ##  $a LC in OCLC, [date] $b ([data])

670  ##  $a M/B/RS Collections Authority file $b ([data])

670  ##  $a New Delhi MARC file $b ([data])

670  ##  $a MWA/NAIP files $b ([data])

670  ##  $a NUC pre-56: $b ([data])

670  ##  $a NRMM $b ([data])

670  ##  $a BNF in VIAF, [date] $b ([data])

Library of Congress staff working with the National Union Catalog (NUC) reports used specific library reports in the 670 citations when creating name authority records.

670  ##  $a nuc85-70017: Lower and middle Pennsylvania stratigraphy ... 1982 $b (hdg. on AAP rept.: Sutherland, Patrick Kennedy, 1925- ; usage: Patrick K. Sutherland)

BGN

Provide the name of the database and the date searched in subfield $a.  For domestic names, cite GNIS (URL: http://geonames.usgs.gov/pls/gnispublic).  For foreign names, cite GEOnet (URL: http://geonames.nga.mil/gns/html).  In subfield $b provide names given for the entity, feature designation or class (e.g., ADM1, PPL, civil) coordinates, and name of larger place if appropriate.  (Other relevant information may also be provided.)  For foreign names, convey the name type by adding within brackets after the name, e.g, [conventional], [approved], [short].  Repeat the brackets after each name of this type.  Variant names (including non-roman script names) may be given in a single listing as shown below.  If possible, use the degree sign (not superscript zero) to show degrees, use the miagkii znak (modifier letter prime) for minutes and the tverdyi znak (modifer letter double prime) for seconds.

670  ##  $a GNIS, viewed May 5, 2016 $b (Allegany County; civil, 39°3717N 078°4156W, located in Maryland; variant: Alligany County)

670  ##  $a GEOnet, viewed April 12, 2014 $b (Bellinzona [approved]; PPLA in Ticino, Switzerland, 46°1143N, 009 0122E; also a district of the same name in Ticino)

670  ##  $a GEOnet, viewed May 4, 2016 $b (Taitung [conventional], Taitung County [conventional], Taidong [approved], Taidong Xian [approved]; ADM1 in Taiwan, 22°5301N 121°0254E; variants: Taidong Sian; T'ai-tung; T'ai-tung Hsien; non-roman script: ; )

Non-bibliographic sources

Give the non-bibliographic source, the date, and the information.  The source can be given specifically ("Letter 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 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.

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

670  ##  $a Letter from author, May 29, 1994 $b (correct birthdate for ______________ is Oct. 14, 1950)

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

670  ##  $a Email from publisher, April 3, 2016 $b (__________)

Citations for republication SARs

If an SAR is for a republication only, begin the 670 with the term for the type of republication and a slash.  Do not include a 670 for a republication if the SAR covers both the original and one or more republications.  Do not add additional 670 fields for other types of republications cataloged later.  (See 64X Series Treatment, Republications for more information about republications.)

670  ##  $a Large print edition/Fool's coach, c1989: $b CIP t.p.

[An Evans novel of the West.]

Citations for undifferentiated NARs

For information on existing 670 citations found in undifferentiated NARs, see DCM Z1, 008/32 Undifferentiated Personal Name.

For more information on DCM Z1 Instructions, select:

DCM Z1:  Introduction

DCM Z1