3.1 Theses and Dissertations

3.2 Reproductions and Original Microform Publications

3.3 Technical Reports

3.4 "In" Analytics

3.5 Offprints and Detached Copies

3.6 Supplementary Items

3.7 Locally Made Videorecordings

3.8 Copy- or Institution-Specific Notes and Added Entries

3.9 Electronic Resources

3.10 Parallel Records for Language of Cataloging

3.11 Guidelines for Integrating Resources

This chapter has guidelines for materials and cataloging practices that present unique problems to online catalogers.

Historically, most theses and dissertations are unpublished items made available through copies.

Electronic theses and dissertations that are remotely accessible via the Web should be treated as published items and cataloged as original electronic publications, as explained in AACR2 9.4B2. For more information, see Cataloging Electronic Resources: OCLC-MARC Coding Guidelines ( http://www.oclc.org/support/documentation/worldcat/cataloging/electronicresources/).

Use the following for theses and dissertations:

• Most microforms of theses, such as those from University Microfilms (UMI), are reproductions of unpublished copies of theses. Catalog them as such.
• Use BKS format ( Type code t–Manuscript language material) for book-like theses, VIS format for theses in an audiovisual medium, REC format for recorded theses, etc. Use Type code d (Manuscript music) for Score theses and Type code f (Manuscript cartographic material) for Map theses.
• Use code xx in Ctry for both original and reproduced theses.
• For all reproduced theses, code DtSt for the original.
• Omit place and publisher in field 260 (Publication, Distribution, Etc. [Imprint]) per AACR2, rule 4.4.
• Omit series statements in 4xx per AACR2, rule 4.6.
• Omit added entries for advisors, the institution, made-up thesis collection or series titles in fields 246, 700–740 and 8xx. Use the 79x fields for these kinds of added entries.
• Enter a thesis note in field 502 (Dissertation Note).
• If you are cataloging a copy from a commercial producer and a record exists for another copy in the same medium (photocopy or microform) from the same producer, use the existing record, even if the date of reproduction differs. Since such theses are copies, cataloging rules allow the dates to vary from earlier copies. In such cases, if date information would be the only change, do not create a new record.
• Optional. If you describe a reproduced thesis in field 533 (Reproduction Note), you may enter a Ctry code for the place of reproduction in field 539 (Fixed-Length Data Elements of Reproduction Note) subfield ‡d (Place of publication, production or execution). You may also enter date information for the reproduced thesis in field 539 subfields ‡a, ‡b and ‡c. Such information is based on the data in field 533. See field 539 for more information.

The Library of Congress follows Anglo-American Cataloguing Rules, first edition (AACR1) for descriptions of electronic, microform and "on demand" photocopy reproductions of previously existing materials. The principles of AACR1, described in LCRIs for AACR2, chapter 11, state that you should base the bibliographic description on the original publication and place data relating to the reproduction in a secondary position.

LC applies AACR2 for the form of the description of the original and for choice and form of access points (headings). You should follow LC policy.

Library and Archives Canada (NLC) serial records follow AACR2 for microform reproductions. See chapter 4, " When to Input a New Record," for more information.

• Follow LC policy when cataloging electronic, microform and "on demand" photocopy reproductions (e.g., those issued by ERIC, NTIS, etc.). Emphasize the original item and describe the reproduction in a note. Follow AACR2 rules for the form and content of the description of the original and for choice and form of entry.
• Do not create a new record if you retrieve a record with fixed fields coded for the reproduction (in Ctry, Dates, etc.). Instead, locally edit the record to code the fixed field elements for the original item. Differences in form (e.g., microfilm vs. microfiche), publisher, or series justify a new record. See chapter 4, " 533 Reproduction Note." Note: To have the master record corrected, see chapter 5.6, " Reporting Errors."
• Use the GMD "microform" for microform reproductions.

  245

  ‡h [microform]

• Use the GMD "electronic resource" for electronic reproductions of works previously published in print form.

  245

  ‡h [electronic resource]

• Do not use a GMD for photocopies.

Code microform and macroform reproductions cataloged according to LCRIs for AACR2, chapter 11.

If you search using a date qualifier, you may want to search using both the original date and the date of reproduction because records can be coded with either. Database conversions have corrected many, but not all, records coded with previous practices.

• Code electronic, microform and macroform reproduction fixed-field elements, except Form, for the original item described in the body of the entry, not for the reproduction, which you describe in field 533.
• Code the fixed-field element Form for the type of reproduction described in field 533. Use a workform appropriate for the original work.

LC links bibliographic records for microform reproductions of monographs to records for the corresponding hardcopy originals.

LC adds field 776 (Additional Physical Form Entry) to records representing microform reproductions. Field 776 consists of subfield ‡c (Qualifying information) with "Original" and subfield ‡w (Record control number) with the MARC Organization Code in parentheses followed by the control number of the record for the hardcopy original.

The preceding example shows a link for a microform reproduction of The Toll of the Sands, LCCN 20-1. Do not use a similar linking field on the record for the hardcopy original to connect it with its microform reproductions.

To record the LCCN of the original item when cataloging a microform reproduction, include such data in field 776.

United States Newspaper Program (USNP) participants catalog the original paper version of a newspaper and attach union list local data records to the master record for all formats (e.g., microform, paper, paper reprints, reproductions). The Newspaper Cataloging and Union Listing Manual, CONSER/USNP Edition, describes USNP cataloging guidelines. It is available from the Library of Congress, Cataloging Distribution Service.

The U.S. Government Printing Office (GPO) sometimes has the original, microform and electronic versions available. GPO catalogs the original (paper), sends microform to some depository libraries, and makes electronic versions available on government web sites.

The bibliographic record represents cataloging for the original but may contain item numbers for microform, electronic and the original in separate 074 fields. A note concerning availability in microform and/or electronic versions may appear in field 530.

You may enter a separate record for a government document if it is in a medium different from that in the GPO record. You may use the GPO record, but it would not accurately reflect what your library holds. See field 074 for more information.

If you are cataloging an original microform publication, follow AACR2 exclusively. Use the appropriate workform to describe the item (AACR2, chapter 11).

Catalog items that are microreproductions of material prepared or assembled specifically for bringing out an original edition in microform (AACR2, chapter 11). For example, catalog a microform collection that reproduces previously existing material, but has not itself existed previously as a bibliographic entity, according to chapter 11.

According to ANSI Z39.23 (1983),

. . . a technical report is a document that gives the result of research or developmental investigations, or both, or other technical studies. . . A technical report is initially submitted to the person or body for which the investigation was carried out or by which it was sponsored. Copies of it may subsequently be made available in limited quantities. . . , but these copies are not produced commercially and are not available from booksellers or other commercial sources. . . . Technical reports are usually published irregularly, either in series or as separate monographs. Technical reports are not typeset but are reproduced from typescript by near-print processes, and they are usually concerned with only one specific subject or with a few closely related subjects.

Use the following optional guidelines for selected fixed-field elements and variable fields when cataloging a technical report:

If a separate bibliographic record is necessary for a component, you may prepare an "in" analytic entry. A component is a bibliographic unit that is physically contained in another bibliographic unit (host item) in such a way that the host item must be identified to locate the component (e.g., one article in a serial, one chapter or paper in a book or one track on a sound recording).

Do not use "in" analytic cataloging conventions for offprints, reprints or detached copies.

Use the following guidelines:

Element	Guidelines for "In" Analytics
BLvl	Code for the component (e.g., a for monograph, b for serial).
Ctry	If country information is available in field 773 (Host Item Entry) subfield ‡d (Place, publisher and date of publication), code accordingly. Otherwise, code Ctry as unknown ( xx ).
Dates	Use date in field 773 subfields ‡d or ‡g (Relationship information) as appropriate.
018	Use for copyright article-fee code.
260	Do not use field 260.
300	For records coded AACR2 (Desc: a) paging should appear in field 300 ‡a and not in field 773.
580	Use for linking entry complexity notes.
773	Use for host item entries. Subfield ‡d (Place, publisher, and date of publication) is typically used when the host item is a monograph.

In the case of host items that are serial or multi-volume in nature, information in subfield ‡g is necessary to point to the exact location of the component part within the bibliographic item.

Example: Host item is a serial

Example: Host item is a serial

Example: Host item is a monograph

Example: Host item is a monograph

Use the following guidelines for offprints and detached copies:

• If a separate bibliographic record is needed for an offprint or detached copy, catalog the item as a separate bibliographic item. Do not use "In" analytic cataloging conventions for offprints, reprints or detached copies.
• Use AACR2 rule 2.5B6 to record pagination. In a field 500 note, indicate the relationship to the larger work. Begin the note with "Offprint:" or "Detached from:" as appropriate.
• If the larger work is a serial, use the title in AACR2 catalog entry form, followed by the numeric and/or alphabetic designation (preceded by a period). If appropriate, use the chronological designation enclosed in parentheses.
• If the item is detached from another monograph, follow AACR2 rule 1.7A3 in citing the source. Under the provision of rule 21.30G, added entries may be made for the larger work.

Use the following guidelines for cataloging supplementary items. You may catalog supplementary items independently (i.e., in a separate record) or dependently (i.e., in the record for the main item).

• If cataloging independently, include the LC card number and the OCLC number of the main item, if available, in the appropriate 7xx linking entry field.

• Use the publication pattern to determine whether the supplementary item should be cataloged as a monograph or a serial. Monographs have a finite number of parts. Serials are intended to continue indefinitely.

• Treat items with monograph title page (or equivalent) as monographs.
• Treat subsequent parts that update the item, have different titles and are issued indefinitely as serials.
• Relate any separate bibliographic record for supplements to the record for the main work (parent) via the appropriate added entry or serial linking field.
• Do not create records for the updates to loose-leaf publications.
• Optional. Create a record for both the main work and its supplement. Such records are not duplicates.
• Optional. Catalog supplements to loose-leaf publications that are cataloged as serials separately as another serial in a separate record, particularly if the supplement has a separate title.

• If cataloging dependently, i.e., on the same records as the main item, add 006 fields to reflect fixed-field coding of the supplementary items, especially if it is in a different format.

This section discusses three types of locally made videorecordings.

The guidelines below apply to all local video reproduction media, including videotape, videodisc, streaming video, electronic video files, etc.

Use the following guidelines:

• Treat locally produced videorecordings as unpublished materials. They may exist as either unique copies or as a small number of copies for limited distribution.
• Transcribe title and statement of responsibility information ( field 245) from the piece.
• If the videorecording lacks a title, supply one (AACR2, rule 7.1B2).
• The Publication, Distribution, etc. area ( field 260) should have only the date of recording in subfield ‡c, unless the date already appears in field 245.

Treat locally reproduced videorecordings as copies by adding information to an existing record or by inputting a new record.

Adding information to an existing record. Add a local note ( field 590) indicating the existence of a copy to the record of the original item. Describe it briefly (e.g., Motion picture noncirculating, videocassette (VHS) available for loan).

If a record exists for the reproduced copy in the same physical format (e.g., VHS videocassette or 1/2 in. videoreel), use that record even if the dates of the copies differ. Edit the record to reflect those differences.

Use the following guidelines:

• Transcribe the title, statement of responsibility and publication information from the original.
• For tangible video reproductions, including videotape and videodisc, use the General Material Designation 'videorecording' in field 245 subfield ‡h.
• For remote and other electronic video reproductions, including streaming video and video files, use the GMD 'electronic resource.'
• For tangible video reproductions, including videotape and videodisc, enter the physical description in field 300. For remotely accessed video reproductions, including streaming video, the use of field 300 is optional (see AACR2 rules 9.5A1b, 9.5B3, and 9.5C3).
• Enter necessary notes related to the intellectual content, cast and credits.
• Enter a note indicating the original format (e.g., Originally issued as super 8 mm. film cartridge).
• Enter a note that gives the recording date and indicates that the copy was made with permission.
• Use the country of producer (from Ctry) of the original.
• Use the information from the copy for other fixed-field elements and field 300.
• For a video copy of another videorecording, use code r (Reprint/reissue date and original date) in DtSt.
• For a video copy of a motion picture or other audiovisual medium, use code p (Date of distribution/release/issue and date of production/recording session when different) in DtSt.
• Use the date of the copy in DATE 1. Use the date of the original in DATE 2.

Treat all off-air recordings as unpublished materials. Broadcasting does not constitute publication.

If a record exists for a commercially available video version of a television program, you may edit that record for local use. Or, you may input a new record.

If you input a new record, use the following guidelines:

• Transcribe the title and statement of responsibility information ( field 245) from the title and credits of the existing record.
• Enter only the year of the recording in field 260 subfield ‡c (Date of publication, distribution, etc.).
• Enter data in field 300 (Physical Description) that reflects the copy.
• Enter a note indicating that the copy was made under license and a note for the name of the television station that broadcast the program.
• Code the fixed field and field 007 for the copy.

If a record exists for an off-air copy in the same physical format (e.g., VHS videocassette or 1/2 in. videoreel) as the piece in hand, use that record, even if the date of the copy and the name of the television station that broadcast the program differ. Edit the record to reflect those differences.

If the copy is retained by your institution, making an unlicensed copy of a television broadcast may be an infringement of copyright law.

See the U. S. Copyright Office Circular 21, Reproductions of Copyrighted Works by Educators and Librarians, section "Guidelines for off-air recording of broadcast programming for educational purposes" ( http://www.loc.gov/copyright/circs/cir21.pdf).

You may supply copy-specific or institution-specific notes and added entries for rare and special-collections materials. However, do not create new records because single master records can have such information for more than one copy or institution.

Master records for published materials represent all copies of a work, the "universal description" of the item. MARC 21 defines subfield ‡5 (Institution to which field applies) for use in notes and added entries that do not apply to the universal description. Usually, only rare and special-collections materials are candidates for fields containing subfield ‡5.

Use subfield ‡5 in fields 246, 500, 501, 506, 526, 540, 541, 561, 562, 583, 584, 585, 655, 700, 710, 711, 730, 740, and 851 to identify the institution to which the copy- or institution-specific notes and added entries apply (by MARC Organization Code, formerly called NUC Code).

Consider the usefulness of the information in accessing and identifying the item versus the likelihood that the record will be used in copy-cataloging or found by others who will not need your copy- or institution-specific notes and added entries.

Do not include subfield ‡5 in master records for unpublished items and collections. Such notes and added entries do apply to the universal description, since they are single items.

Do not include subfield ‡5 in master records for works that you do not own. It is difficult to confirm the validity of the information, even if the information is from LC printed copy.

If the copy- or institution-specific note or added entry is of local interest only and you want to include the information for your local processing, use the appropriate 590, 599, 790, 791, 792, 793, 796, 797, 798, or 799 field. These fields are not retained in master records. Subfield ‡5 is also valid in fields 790, 791, 792, 793, 796, 797, 798, and 799.

If you add subfield ‡5, use the following guidelines:

• Enter subfield ‡5 as the last subfield. Enter the MARC Organization Code of the institution holding the copy. To find these codes, see Find an OCLC Library ( http://www.oclc.org/contacts/libraries) or the MARC Code List for Organizations ( http://www.loc.gov/marc/organizations/).

• Do not include terminal punctuation as part of ‡5. Terminal punctuation should be included in the subfield immediately preceeding ‡5.
• Use field 501 ("With" Note) with subfield ‡5 for "with" notes for items bound together after publication.
• Use field 710 (Added Entry–Corporate Name) with subfield ‡5 for an added entry for the name of a special collection.

According to AACR2, 2005 Update, an electronic resource is: "Material (data and/or program(s)) encoded for manipulation by a computerized device. This material may require the use of a peripheral directly connected to a computerized device (e.g., CD-ROM drive) or a connection to a computer network (e.g., the Internet)." This definition does not include electronic resources that do not require the use of a computer, for example, music compact discs and videodiscs.

In Type, use code m (Computer file) only for the following general classes of electronic resources:

• Computer software (including programs, games, fonts)
• Numeric data
• Computer-oriented multimedia
• Online systems or services

For these classes, if there is a significant aspect that causes it to fall into another Type category, code for that significant aspect. For instance, vector data that is cartographic is not coded as numeric but as cartographic. Other classes of electronic resources are coded for their most significant aspect (for instance, language material, graphic, cartographic material, sound, music, moving image). In case of doubt or if the most significant aspect cannot be determined, consider the item a computer file. If the resource is essentially the equivalent of a print item but in electronic form, use the same Type code you would use for the print version.

Example : A copy of Homer's Iliad available via the Internet.

• Former practice: Type code m
• Current practice: Type code a

Since the item is basically textual, Type is coded a (Language material). The electronic aspect is secondary.

Example : TurboTax software.

• Former practice: Type code m
• Current practice: Type code m

Since the item is software and no other Type code applies, there is no change in practice.

When cataloging an electronic resource that has a Type code other than m, use code s in Form for electronic resource.

Creating separate records for an item is preferable when both remote and directly tangible (non-remote) versions exist.

If you are cataloging a remote item, however, you need not verify the physical existence of the non-remote version or whether it has been cataloged. Similarly, when you catalog a non-remote item, you need not verify whether a remote version exists.

In both cases, you may catalog the item as if no other version exists. Apply the input convention in Cataloging Electronic Resources: OCLC-MARC Coding Guidelines ( http://www.oclc.org/support/documentation/worldcat/cataloging/electronicresources/) if you have verification that remote and non-remote versions exist and you want to record the existence of both.

When cataloging digital versions of print materials, generally create separate records for the digital version of an item. For information about digital masters, see the Digital Library Federation Registry of Digital Masters Record Creation Guidelines ( http://www.diglib.org/collections/reg/DigRegGuide200705.htm).

The decision to code an electronic resource as a monograph or as a serial is a decision made separately from the Type code decision. Note that for electronic serials where Type is not a or m, two 006 fields will be necessary, one for the electronic aspects and one for the serial aspects.

Apply the current AACR2 definitions of monograph and serial to electronic resources. Treat as serials ( BLvl   Bibliographic Level: s (or b)) only those continuing resources issued in a succession of discrete parts with no predetermined conclusion. The parts may constitute an issue, or in some cases, an individual article.

Applying the current AACR2 definitions may result in different manifestations receiving different cataloging treatment. For example, a manifestation in print form, such as an annual directory, is cataloged as a serial but it is cataloged as an integrating resource when the directory takes on the form of an electronic file that is continuously updated. The Library of Congress and CONSER adhere to current definitions, and OCLC recommends its users do the same. These remotely accessed electronic resources that change frequently are currently excluded from serial treatment (they should be cataloged as integrating resources or monographs, as appropriate):

• Databases (including directories, A&I services, etc.)
• Electronic discussion groups (e.g., SERIALST)
• Electronic discussion group digests (e.g., AUTOCAT digest)
• Gopher servers (e.g., LC-MARVEL)
• Online public access catalogs (e.g., OCLC)
• Online services (e.g., America Online)
• Web sites (e.g., the CONSER home page)

For further guidance on coding serials, see the Library of Congress document Use of Fixed Fields 006/007/008 and Leader codes in CONSER records ( http://www.loc.gov/acq/conser/ffuse.html).

See Cataloging Electronic Resources: OCLC-MARC Coding Guidelines ( http://www.oclc.org/support/documentation/worldcat/cataloging/electronicresources/).

In 2003, OCLC policy changed to allow for parallel records within WorldCat by language of cataloging. It has long been envisioned that WorldCat would need a parallel record structure to display records by language of cataloging.

When an institution applies a local descriptive cataloging convention, supply subfield ‡e in the 040 field with the code local followed by a slash and either the MARC Organization code or the OCLC symbol of the institution (for instance, ‡e local/SiSiNL or ‡e local/SINLB).

Note: Only one record per language of descriptive cataloging is allowed for each manifestation of a title. In the case of Chinese cataloging, do not create separate parallel records in both Chinese traditional script and Chinese simplified script. Transcribe the script as it appears on the resource. If access to the alternative script is useful, use field 246.

Previously, records for the same title, but cataloged in different languages, such as English, Spanish and French, were considered duplicate records.

OCLC no longer considers these records duplicates, but considers them parallel records.

The parallel record exception for vendor records, which was announced with the parallel records policy in 2003, is no longer in effect. Treat vendor records the same as other records when determining whether to create or consider a record a parallel record.

A parallel record is characterized by the use of a single language of cataloging in these fields:

• Field 040 contains a code for language of cataloging in subfield ‡b
• Field 300
• Non-quoted notes in 5xx field(s)
• The GMD in the 245 ‡h

Note: The language of the subject headings (65x fields) is not a factor when determining the language of cataloging.

Language of descriptive cataloging is coded in field 040 (Cataloging Source), subfield ‡b (Language of cataloging) of the record. If subfield ‡b is not present, the language of descriptive cataloging is assumed to be English.

Subfield ‡b is in records created by libraries for which English is not the language of the cataloging agency. The language is indicated by a three-letter language code. For a list of these codes, see the MARC Code List for Languages ( http://www.loc.gov/marc/languages/).

The language of descriptive cataloging ( field 040 subfield ‡b) is not to be confused with the language of the item, which is recorded in the fixed-field element Lang (Language Code) of the record.

When searching WorldCat, if the matching record is cataloged in a language other than that used by the inputting library, the library may enter a parallel record in its language of descriptive cataloging. When using an existing record for copy cataloging, however, do not change the language of cataloging if upgrading the Master Record unless the code in field 040 subfield ‡b (language of cataloging) does not reflect the language of the record.

Examples

A library using Spanish as the language of cataloging that finds a record with English as the language of cataloging, may create a record with Spanish as the language of cataloging.

A library with English as the language of cataloging, that finds a record with Italian as the language of cataloging, may create a record with English as the language of cataloging.

When using an existing record for copy cataloging, do not change the language of cataloging when upgrading the master record unless the language of cataloging coded in field 040 ‡b does not accurately reflect the actual language of the cataloging record.

Record appropriately cataloged in French

Record appropriately cataloged in Dutch

Record appropriately cataloged in Chinese

A hybrid record contains descriptive cataloging data in more than one language, which is not standard practice. More specifically, a record where these fields contain data in different languages is considered a hybrid:

• The coding of 040 subfield ‡b (does not match the language used in the rest of the record)
• Field 245 subfield ‡h (GMD)
• Field 300 (physical description)
• Non-quoted notes (5xx fields)

Note: The language of the subject headings (65x fields) is not a factor when determining the language of cataloging.

Hybrid records should be corrected to represent a single language of cataloging.

Take these factors into account when considering a change in coding for the language of cataloging:

• The intent of the cataloging agency
• The number of descriptive cataloging elements in different languages. As a general rule, a record's language of cataloging should reflect the predominant language used in the descriptive cataloging elements.

Based on these factors, if you determine that the language of the record matches the language used in your library, then correct the errors and use the record for cataloging.

If you determine that the language of the record does not match the language used in your library, then create a new record.

However, if you suspect that the record was incorrectly changed from one cataloging language into another and if the change may have occurred within the last 90 days, then contact OCLC's Quality Control Section (see " Reporting hybrid records"). The last date replaced does not necessarily determine when the language of cataloging may have been changed. The Quality Control Section will analyze the data and decide whether to change the record back to its original language of cataloging and contact the library that changed it.

These examples demonstrate three common hybrid record situations. Use judgment in dealing with hybrid records that do not reflect the examples below.

Language of cataloging (040 ‡b) and physical description (300) do not match notes (5xx)

This record has the language of cataloging in field 040 ‡b as swe, the 300 field has s. for sidor (pages), but it also includes a note in English (field 504), which makes the record a hybrid. Institution S3O is the National Library of Sweden, which catalogs most of its material in Swedish. Only field 504 is inconsistent with the language of cataloging.

If the language of cataloging used at your library is Swedish, then change the note in field 504 to Swedish: Innehåller bibliografiska referenser och index.

If the language of cataloging used at your library is not Swedish, search for a record or input a new record in your language, as appropriate. Report the hybrid to OCLC for correction.

Missing subfield ‡b in field 040

This record does not have subfield ‡b in field 040, so the language of cataloging is assumed to be English. But the 300 field and the note (field 504) are in Spanish.

If the language of cataloging used at your library is Spanish, add subfield ‡b coded spa to field 040.

If the language of cataloging used at your library is not Spanish, search for a record or input a new record in your language, as appropriate. Report the hybrid record to OCLC for correction.

Edited record with inappropriate code in field 040 subfield ‡b

This record either became a hybrid record as a result of editing or was entered originally as a hybrid record. Field 040 subfield ‡b is coded pol, but the rest of the record is English.

If the language of cataloging used at your library is English, change field 040 subfield ‡b from pol to eng.

If the language of cataloging used at your library is not English, search for a record or input a new record in your language, as appropriate. Report the hybrid record to OCLC for correction.

Record with language of cataloging inappropriately coded as Swedish

In this example, change field 040 subfield ‡b to eng because English is used in field 300 and in the majority of note fields (500, 504).

If you cannot correct the master record, you can edit the record locally and also report it so that OCLC can edit the master record for all OCLC member libraries. To report the record use:

• E-mail: bibchange@oclc.org
• The Report Error function in the Action menu in Connexion

For more information, see chapter 5.6 " Reporting Errors."

Assign the Type code appropriate to the content and type of material. For example, assign Type code a for language material.

Use BLvl i for integrating resources.

DtSt : For integrating resources that are currently published, use code c (rather than the former practice of code m). For integrating resources that have ceased publication, use code d (rather than the former practice of code m).

For language material integrating resources ( Type a, BLvl i), code the fixed field elements as follows:

• Form : For electronic integrating resources, continue to use code s in Form .
• Freq and Regl : If the integrating resource is truly "continuously updated" (for instance, a constantly updating database, a newspaper's Web site that gets updated as news occurs, etc.), use the Frequency Code k, which means "the item is updated more frequently than daily;" in that case, the correct Regularity code is likely to be r for Regular. More commonly, when the resource is updated less frequently than daily and none of the other Frequency codes apply, use blank ( ) for Frequency and x for Regularity.
• S/L : Use code 2 to indicate that the record was formulated using the rules for integrated entry.
• SrTp : Use code d for updating databases, code l for updating loose-leafs, or code w for updating Web sites, as appropriate.

For electronic integrating resources, continue to include a computer file 006 and a computer file 007 field. For a language material integrating resource, the typical computer file 006 and 007 fields will be coded as follows

• COM 006: Type: m Audn: File: d GPub:
• COM 007: c ‡b r ‡d c ‡e n

See Cataloging Electronic Resources: OCLC-MARC Coding Guidelines, especially the section on Integrating Resources ( http://www.oclc.org/support/documentation/worldcat/cataloging/electronicresources/#10).