| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

Appendix C Core-Level Records

Page history last edited by Margaret Nichols 12 years, 2 months ago

Question: Does this concept (or the concept of the BIBCO Standard Record) apply at all to manuscripts?

 

Appendix C. Core-Level Records

 

Text subject to reconsideration in blue

Deletions subject to reconsideration are struck through: text being considered for deletion

 

C1. Introduction

 

 

The elements of description provided in DCRM(MSS) constitute a full set of information for describing single manuscripts. This appendix sets out a less-than-full level of description as a manuscripts counterpart to the Program for Cooperative Cataloging (PCC) standard for core-level records for rare print materials. The core record standard was defined by the PCC for use within the context of its national cataloging program, BIBCO, to support the goal of providing cost-effective cataloging that meets commonly accepted standards.

 

 

Although the core record standard originated with the BIBCO program for monographs, it can be used by any library, BIBCO participant or not. Authority records are not required for headings on DCRM(MSS) core-level records, but they are encouraged when a name is known to users in several different forms.

 

 

C2. Application

 

 

Catalogers may apply the core-level standard to any rare materials described using DCRM(MSS), with one exception: it is not to be applied to manuscripts created before 1600. DCRM(MSS) core-level records are especially appropriate when faithful and accurate descriptions are desirable, and the provision of subject and other access points is important, but abridged transcriptions and fewer notes are acceptable.

 

 

For manuscripts, the commitment, on the cataloger’s part, is to render bibliographic details of the manuscript as accurately as possible insofar as they are presented by the specimen in hand; also, to ensure that they are scrupulously stated, according to the provisions of DCRM(MSS). The strength of DCRM(MSS) is that it provides for “expanded coverage” of manuscripts deserving such treatment; conversely, it is possible to use those provisions for expansion as guidelines for trimming the description. By omitting most notes and taking the options given in DCRM(MSS) for abbreviating descriptive areas, or by not taking the options to expand the same areas, an effective DCRM(MSS) core-level record can be created.

 

 

 

C3. Elements of the bibliographic record

 

 

Use the guidelines set forth below, taken from the BIBCO Core Record Standards, to create core-level records using DCRM(MSS).

 

 

Leader and directory

 

 

Depending on the individual automated system or bibliographic utility, part or all of the leader and directory may be system-supplied. Generally speaking, the cataloger will have to supply values for the following leader positions:

 

 

            06        Type of record

 

 

            07        Bibliographic level

 

 

            17        Encoding level

 

 

            18        Descriptive cataloging form

 

 

Give the encoding level (Leader/17) a value of 4 to indicate a core-level record.

 

 

Control fields: 001, 003, 005

 

 

These fields are generally system-supplied.

 

 

Control field: 007

 

 

Code the following positions of the Microform 007 if appropriate:

 

 

            00        Category of material

 

 

            01        Specific material designation

 

 

Control field: 008

 

 

Code at least the following positions:

 

 

            06        Type of date/Publication status

 

 

            07-10   Date 1

 

 

            11-14   Date 2

 

 

            15-17   Place of publication, production or execution (for manuscripts, supply the code here for the place where the repository is located)

 

 

            22        Target audience

 

 

            23        Form of item

 

 

            28        Government publication

 

 

            33        Literary form

 

 

            34        Biography

 

 

            35-37   Language

 

 

            38        Modified record code

 

 

            39        Cataloging source

 

 

040 field: Cataloging source

 

 

Bibliographic records for manuscripts that reflect the DCRM(MSS) core-level standard must contain the designation “dcrmms” in subfield ‡e of field 040.

 

 

042 field: Authentication code

[Just omit this part, or explain that BIBCO doesn't apply here because it's for monographs only?]

 

For DCRM(MSS) core-level records contributed by members of the PCCBIBCO program, include the designation “pcc” in field 042. For other DCRM(B) core records, leave the field blank.

 

 

099 field: Call number

 

Call numbers for manuscripts are formulated according to local institutional practice. However, in keeping with DACS, the institution is encouraged to add the call number in a call number field as a unique identifier for the manuscript in question.

 

Since institutional practices for rare books often involve locally formulated call numbers, a requirement for a national standard classification could cause additional or undue effort for creators of DCRM(B) core-level records. However, if an institution supplies standard call numbers to materials covered by the DCRM(B) core record standard, it is encouraged to add these numbers in the appropriate call number field.

 

 

1XX field: Main entry

 

 

Mandatory if applicable. Authority records are not required for headings on DCRM(MSS) core-level records, but they are encouraged when a name is known to users in several different forms.

 

 

240 field: Uniform title

 

 

Mandatory if applicable. Supply a uniform title if it is known or can be readily inferred from the manuscript.

 

 

245-300 fields

 

 

Mandatory if applicable. One of the basic differences between AACR2 and DCRM(MSS) is the method and extent to which bibliographic details (fields 245-300) are recorded. As to method, bibliographic details should be recorded as correctly as possible, according to the descriptive conventions expected for the field. As to extent, DCRM(MSS) provides some options for abridging descriptive fields, and creators of core-level records for manuscripts are encouraged to implement these options wherever appropriate.

 

 

245 field: Title statement

 

 

Subfield ‡a is mandatory; all other subfields are mandatory if applicable. Subfield ‡h is mandatory for microforms or digital surrogates.

 

 

246 field: Varying form of title

 

 

Mandatory if applicable. Use judgment in assessing each item and assign a title variant if a variation is deemed important. The variants assigned are intended to reflect cataloger judgment and/or local institutional policy.

 

 

250 field: Edition statement

 

 

Mandatory if applicable.

 

 

260 field: Place and date of production

 

Subfield ‡c is mandatory.

 

 

300 field: Physical description

 

 

Subfield ‡a and subfield ‡c are mandatory. All other subfields are mandatory if applicable.

 

 

5XX fields: Notes

 

 

In DCRM(MSS) core-level records, a note indicating the transposition of any title area elements in the transcription is mandatory if applicable. (?) Other notes are not required in DCRM(MSS) core, except as indicated below, although they may be included, if considered important. Notes are not required to justify additional access points.

 

 

 

500 field: Source of title proper (if other than chief source)

 

 

Mandatory if applicable.

 

 

501 field: With note

 

 

Mandatory if applicable.

 

 

502 field: Dissertation note

 

 

Mandatory if applicable.

 

 

505 field: Formatted contents note

 

 

Mandatory if applicable. Optional. May be supplied as appropriate for collections, compilations, or for multipart manuscripts with separate titles.

 

 

510 field: Citation/references note

 

 

Addition of citation notes as a means of abbreviating detailed description of the manuscript is encouraged. Prefer sources that provide the fullest or most authoritative information, to keep the number of citations to a minimum.

 

6XX fields: Subject headings

 

 

Mandatory if applicable. Use judgment in assessing the manuscript and, if appropriate, assign a complement of headings that provides access to the primary/essential subject of the work (as opposed to secondary or tertiary aspects) at the appropriate level of specificity. Assign such headings from an established thesaurus or subject heading system recognized by the MARC 21 Format for Bibliographic Data. In focusing on the primary subject, follow the conventions of the particular subject heading system being used, including the use of paired or related headings where necessary to represent the subject fully.

 

 

655 field: Genre/form headings

 

 

Addition of genre/form terms to the DCRM(MSS) core-level record is encouraged if local policy calls for use of such terms, as appropriate to the piece. Prefer terms found in the official thesauri maintained by the RBMS Bibliographic Standards Committee[1]; terms from other authorized thesauri (e.g., the Art and Architecture Thesaurus) may also be used as appropriate.

 

 

7XX fields: Added entries Additional access points

 

 

Mandatory if applicable. Use judgment in assessing each item and assign a complement of additional access points that covers the primary relationships associated with the work. The inclusion and importance of additional access points are intended to reflect individual cataloger’s judgment and/or local institutional policy.

 

 

Authority records are not required for headings on DCRM(MSS) core-level records, but they are encouraged when a name is known to users in several different forms.

 

 

 

 



[1] These thesauri include: Binding Terms; Genre Terms; Paper Terms; Printing and Publishing Evidence; Provenance Evidence; and Type Evidence.

 

 

 

Comments (0)

You don't have permission to comment on this page.