Note that field names below reflect SIRSI Unicorn usage, though USMARC equivalents are given where they exist.

--Leader--

ENC_LVL (LDR/17)

Policy: For both copy and original cataloguing, this should be set to blank.

Policy: Except for RECON titles and pamphlets, this should always be "a"

--Fixed fields (008)--

Policy: Ignore this field when editing contributed/member copy. Code date YYMMDD for original cataloguing and "near copy" coded 040 CaNfsm|cCaNfsm

--Variable length fields--

001: System control number

Policy: Leave as is. If there is no 001, cut and paste in the Unicorn control number. This is required to identify non-matching records in OCLC post-processing reports.

Policy: Ignore; this shows the NUC symbol of the library or system whose control number originally appeared in the 001. On LaserQuest records this will usually be DLC; on OCLC records OCoLC. Unlike the 040 which has been unceremoniously removed by the GRC folks, the 003 at least tells you from whence the record came.

Policy: Ignore. Unicorn relies on the item record to supply this information, so it has no effect.

Policy: Retain where appropriate (ie. it describes the piece in hand (a computer file/map, for example), or we own both formats in a case like one where we have both the microform and paper version of a serial)

Policy: Add LC card number where it is absent from copy but known to cataloguer from CIP or NUC copy.

Policy: Ignore this field

Policy: Retain, but do not copy 016 information to 015

Policy: Retain

Policy: Ignore

Policy: Delete, after copying contents of valid ones to 020

Policy: Insert hyphen after fourth numeric position when lacking in ISSN.

Policy: Retain 035 where the contents are an (OCoLC) control number. Other numbers should removed (including barcode numbers).

Policy: Rename as 035 where used in serial records for utility control number. This tag is supposed to have been used for computer files as Original study number.

Policy: Retain as found except where copy is used as "near copy" only (for another edition). For original cataloguing and "near copy" use 040 CaNfsm|cCaNfsm.

Policy: Retain and check for accuracy, as this code , along with 008/35-37 (LANG) is used for qualifying an OPAC search by language. Where appropriate, add this field when not present in copy.

Policy: Retain. Code where absent and appropriate to the material. This field is keyword searchable using WORD OR PHRASE {043}.

Policy: Retain. While these do have some useful searching potential, there are too many conflicting standards (coded date range, single date, etc.) and they have been added too sporadically to ensure their utility. If present leave alone, otherwise ignore.

Policy: Ignore.

Policy: Ignore.

Policy: Retain. This may prove useful to other libraries using our record as their own cataloguing copy.

Policy: Retain. This may prove useful to other libraries using our record as their own cataloguing copy.

Policy: Retain. This may prove useful to other libraries using our record as their own cataloguing copy.

Policy: Delete, except for serial or other records where our full holdings are not reflected in Unicorn item data. Rename contributed/member copy 090s to 050 4 or 055 3 as appropriate.

Policy: Relabel as 082 04.

Policy: Ignore. These are useful historically and Acquisitions is continuing to "receive" orders on the old 098 at present, but Cataloguing has nothing to do with this field anymore, including |s.

Policy: Ignore.

Policy: We will use formatted contents notes in the following cases:
Conference proceedings where the 505 includes titles and authors of presented papers.

Festschriften and other compilations of academic articles.

Multi-volume sets where individual volumes bear distinctive titles. This would end the need for transcribing title twice--once in the contents note and once in corresponding 7xx.

Literary works where the 505 includes titles and authors of included short stories, poems, novellettes, etc. In cases where there are only a few works in the collection, we should stick to current practice of establishing author/title uniform titles in 700|a|t. Under version 8, 7xx|t will finally move into the title indexes.

Where possible, works which represent compendiums of various specific laws, standards, etc. likely to be requested by specific title.

We will NOT establish formatted contents notes for the following:
Scores and sound recordings where controlled access (uniform titles and authority-controlled name headings) is the preferred means of access.

Contents notes with generic and/or non-distinctive titles (eg. v. 1. Executive summary -- v. 2. Final report -- v. 3. Appendices)

Chapter headings and other cases where primary patron access would be by subject rather than by author or title.

Policy: Relabel as 590.

Policy: Delete

Policy: Retain

Policy: Leave as 740 on older copy in cases where we would now use 246. When adding new title access, use 246 or 740 as appropriate.

Policy: Retain. URLs should be checked by copying |u into Netscape to ensure currency of address. If host doesn't respond, server may be down. If NOT FOUND, try next level up in URL by removing the filename (usually "filename.html") and searching for home document or directory.

Procedure: Guidelines for the use of 856 / Library of Congress Network Development Office; Cataloging Internet Resources. Appendix A: field 856 / Nancy B. Olson.

Policy: Ignore. While these have no effect on Unicorn, they would have to be removed using a globaledit should the library need to copy active item information into this field prior to a system changeover.

Policy: Ignore