Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Resource licensed for use only at specific workstations.  Include both a 506 general access restrictions note and an 856 $z note with specific access instructions in the Voyager record. The Mfhd location must be something other than SERV,REMO -- example.

EZ PROXY TO ENSURE SMOOTH ACCESS FROM OFF-CAMPUS  

...

130 -- Uniform title. When a uniform title is needed to distinguish an online version from a print version, use the qualifier "Online". If you need to distinguish multiple electronic versions that are distributed by different publishers or aggregators, use a uniform title with multiple qualifiers. Uniform titles are not used for reproductions. Examples.

245 -- Transcribe the title exactly as to wording, order, and spelling, but not necessarily as to punctuation and capitalization. Do not transcribe words that serve as an introduction and are not intended to be part of the title (i.e., the title appears on resource as: Welcome to NASA quest. Transcribe the 245 as NASA quest).

Always give the source of the title proper in a note. See Example.

245 -- GMD. Use $h [electronic resource].

...

246 -- Variant titles. Enter any variant title which pertains to the entire work in this field. Remote access resources may contain variant titles on the title screen or at other locations in the file. Such variants may include: "at head of title" phrases, running titles, or abbreviated titles in header information or at the end of the file. File or directory names may constitute other legitimate variant titles if it may be reasonably assumed that a user would search for the resource using those names. The title bar in the Web browser displays the HTML document title as coded in the document source. Such a title can be recorded as a title variant or can confirm as the title proper another variant that is not clearly presented in the publication. Examples.

247 -- Former title proper. For title changes, when all issues have been reformatted with new title, 247 contains the earlier title proper and what is known about the dates it carried. See CONSER Manual 31.18

250 -- Edition statement. Include only if present on the resource. Examples.

260 -- Publication, distribution, etc. Publisher and date are sometimes difficult to find and establish. If the resource lacks a formal publication statement, but internal or external evidence indicates that it emanates from an institution or organization, consider the institution or organization to be the publisher and the location of the institution or organization to be the place of publication.

300 -- Physical description. Use“1 online resource” See Examples.

310 -- Frequency. for continuing resources, consider the frequency of updates to be the frequency of resource. See Examples.

362 -- Designation. Use the unformatted 362 (1st indicator 1) to supply numbering/dates of publication whenever this information is available. See Examples.  

500/588 -- Source of title proper/ Source of description. For any electronic resource, the source of title proper must be specified. Add the date the title was viewed in parentheses following the source of title proper -- examples.

506 -- Access restrictions. When a resource is not freely available, and the electronic location is given in the 856 field, the restriction is noted in the 506 field. For record-sharing purposes, use generic wording in this note rather than Cornell-specific language. See examples.

520 -- Summary. Provide a brief, objective summary of the purpose and content of the item, if needed. The content of the note may be derived from the resource’s introductory information or composed by the cataloger (in consultation with the selector, if necessary). Use phrases or complete sentences, but be sure to include several key words that identify the item’s use and purpose.

...

530 -- Other physical formats. If the site comprises the online version of a print title, or the material is also available on CD-ROM, include this information in a 530 note -- examples.

538 -- System requirements. For remote access files, this note identifies a specific program or type of program needed for use with the file, or special hardware requirements -- example.

538 -- Mode of access. This field is required only to record non-standard modes of access.-- examples.

6XX -- LCSH. Assign LC subject headings according to the guidelines in LC’s Subject Cataloging Manual: Subject Headings.

653 -- Local Subject Captions. See Examples. Use only on records for Database Names.

...

948 -- Local statistics and marker field. Code the $f Special format appropriately for the type of electronic resource. Refer to Examples.

975 -- Gateway genre designation. See Local MARC Fields document. Use only on records for Database Names.

...