Document r-5 marc 21 encoding to accommodate rda elements: lc practice note




Дата канвертавання22.04.2016
Памер92.99 Kb.

Document R-5
MARC 21 encoding to accommodate RDA elements: LC practice

NOTE: This document records the recommended LC practice when giving the information in LC records. See the separate document on which RDA elements are core elements for LC; other elements are given according to cataloger’s judgment.
Bibliographic Format: LC will continue to supply ISBD punctuation; LC will not use the bibliographic format when creating records for works and expressions.


Tag

Attribute(s)

Proposed LC practice


Leader/06

Type of record

Code for primary content.

Leader/07

Bibliographic level

Use value “m” for both “single unit” and “multipart monograph” when recording RDA Mode of issuance.

Leader/18

Descriptive cataloging form

Use value “i” (ISBD)

006

Additional material characteristics

Code for some serials and some electronic resources.

007

Physical description fixed field

Use new values as appropriate.

008

Fixed-length data elements

Use new values as appropriate.

If a copyright date is recorded in 264 $c of a single-part monograph or other resource published in a single year:

code 008/06 as “t”;

give publication, etc., date in 008/07-10;

give copyright date in 008/11-14.


033 (R)

Date/Time, and place of an event

$a Formatted date/time (R)

$b Geographic classification area code (R)

$c Geographic classification subarea code (R)

$p Place of event (R)

$0 Record control number (R)

$2 Source of term (R)

$3 Material specified (NR)



Generally give information in field 518, unless there is a compelling data manipulation need to use more standardized information as allowed in 033 (e.g., an ISO-standard date, a class number for place).
Do not give subfield $0. Give other subfields, as applicable, if readily available.

040 $b

Language of cataloging

Use value “eng”

040 $e

Description conventions

Use value “rda” (okay before or after $c or $d)

046

Special coded dates

For new date subfields related to work/expression, give in authority, not bibliographic, record.

100-130 $0 (R)

Authority record control number

Do not use (workload issue until subfield can be machine-generated and community agreement on identifiers).

100-111 $e (R)

Relationship designator

Cataloger judgment to use designator.

100-111 $4 (R)

Relator code

Do not give.

245 $h

AACR2: GMD

Not valid in an RDA record; see 336-338 below.

255 $a (NR)

Scale

Give term “Scale” at beginning of the subfield if not already part of the content.

255 $e (NR)

Equinox; epoch

Give terms “equinox” and “epoch,” as appropriate, preceding the information.

264 $c

Copyright date

Give in separate 264 field with 2nd indicator “4” (i.e., do not use a date of copyright notice in publication, distribution, manufacture, or production statement)

300 (R)

Carrier description

Repeat as needed.

336 (R)

Content type

$a Content type term (R)

$b Content type code (R)

$2 Source (NR)

$3 Materials specified (NR)


Repeat field, not subfield $a, as needed.
Give subfield $a, using term from RDA 6.9; in subfield $2 give “rdacontent.” Do not give subfield $b; accept subfield $b if present.

337 (R)

Media type

$a Media type term (R)

$b Media type code (R)

$2 Source (NR)

$3 Materials specified (NR)


Repeat field, not subfield $a, as needed.
Give subfield $a, using term from RDA 3.2; in subfield $2 give “rdamedia.” Do not give subfield $b; accept subfield $b if present.

338 (R)

Carrier type

$a Carrier type term (R)

$b Carrier type code (R)

$2 Source (NR)

$3 Materials specified (NR)


Repeat field, not subfield $a, as needed.
Give subfield $a, using term from RDA 3.3; in subfield $2 give “rdacarrier.” Do not give subfield $b; accept subfield $b if present.

380 (R)

Form of work

Give in authority, not bibliographic, record.

381 (R)

Other distinguishing characteristic of the work/… of the expression

Give in authority, not bibliographic, record.

382 (R)

Medium of performance

Give in authority; may also give in the bibliographic, record.

Do not use newly defined subfields ($b, $d, $p, $n, $s, $v) or indicators until LC implementation announced.



383 (R)

Numeric designation of a musical work

Give in authority, not bibliographic, record.

384 (NR)

Key

Give in authority, not bibliographic, record.

490 $x (R)

ISSN

If ISSN of both main series and subseries are present on the resource, give both.

502 (R)


Dissertation

$a Dissertation note (NR)

$b Degree type (NR)

$c Name of granting institution (NR)

$d Year degree granted (NR)

$g Miscellaneous information (R)

$o Dissertation identifier (R)


Use subfields $b, $c, $d, $g, and $o if specific information is available. If specific information is not available, give available information in a 500 field.


588 (R)

Source of description

$a Source of description note (NR)

$5 Institution to which field applies (NR)


Give information (1) about issue, part, or iteration used for description if not the one specified in RDA; (2) date online resource was viewed; (3) if ONIX information used. Generally, do not give subfield $5. Always include in a CONSER Standard Record.

700-730 $0 (R)

Authority record control number

Do not use (workload issue until subfield can be machine-generated).

700-711 $e (R)

Relationship designator (term)

Give “illustrator” for illustrator of resource intended for children; for other roles, cataloger judgment.

700-711 $4 (R)

Relator code

Do not give. (This recommendation applies also to catalogers who use MOIM guidelines.)

700-730 $i (R)

Relationship designator (phrase)

Give RDA appendix J term according to LC policy for these relationships. Give subfield $i as the first subfield unless the content designation already indicates the relationship; in subfield $i, capitalize the first word of the designator and follow the designator with a colon.

76X-78X

$i (R)


Relationship information

Give RDA appendix J term according to LC policy for these relationships. Give subfield $i as the first subfield unless the content designation already indicates the relationship; in subfield $i, capitalize the first word of the designator and follow the designator with a colon.

76X-78X $4 (R)

Relationship code

Do not give.

775 (R)

Other edition entry

Give to link to original when reproduction is in the same type of carrier.

776 (R)

Additional physical form entry

Give to link to original when reproduction is in a different type of carrier.



Authority Format: LC will use the authority format when creating an NAR to record the form of the authorized access point for a work or expression.


Tag

Attribute(s)

Proposed LC practice


008/10

Descriptive cataloging rules

Use value “z” (Other). [A value is not defined for RDA.]

040 $e

Description conventions

Give; use value “rda.”

046 (R)

Special coded dates

$f Birth date (NR)

$g Death date (NR)

$k Beginning or single date created (NR)

$l Ending date created (NR)

$s Start period (NR)

$t End period (NR)

$u Uniform Resource Identifier (R)*

$v Source of information (R)*

$2 Source of date scheme (NR)



Give subfields, as applicable, if readily available.
Use $2 edtf for certain dates; see information at the end of this document (also in LCPS 9.3.1.3)



100-111 $e (R)

Relator term

Do not give relationship designators in 100-111 fields.

336 (R)

Content type

$a Content type term (R)

$b Content type code (R)

$2 Source (NR)

$3 Materials specified (NR)


LC/PCC practice: do not give 336 field in authority records for expressions until policies for expression records are established.

368 (R)

Other corporate body attributes

$a Type of corporate body (R)

$b Type of jurisdiction (R)

$c Other designation (R)

$0 Record control number (R)

$2 Source (NR)



Do not give subfield $0

370 (R)


Associated place

$a Place of birth (NR)

$b Place of death (NR)

$c Associated country (R)

$e Place of residence/headquarters (R)

$f Other associated place (R)

$g Place of origin of work (R)

$s Start period (NR)

$t End period (NR)

$u Uniform Resource Identifier (R)*

$v Source of information (R)*

$0 Record control number (R)

$2 Source of term (R)


Do not give subfield $0. Give other subfields, as applicable, if readily available.
If the place is a jurisdiction, give the RDA form it would have as an addition to an authorized access point. Do not give subfield $2 naf even if there is an NAR for the jurisdiction. An NAR for the jurisdiction is required only if the jurisdiction is also an addition to the established form in the 1XX field.
If the place is not a jurisdiction, indicate the source of the form of place in subfield $2.



371 (R)


Address

$a Address (R)

$b City (NR)

$c Intermediate jurisdiction (NR)

$d Country (NR)

$e Postal code (NR)

$m Electronic mail address (R)

$s Start period (NR)

$t End period (NR)

$u Uniform Resource Identifier (R)*

$v Source of information (R)*

$z Public note (R)

$4 Relator code (R)


Do not give subfield $4. Give other subfields, as applicable, if readily available.



372 (R)


Field of activity

$a Field of activity (R)

$s Start period (NR)

$t End period (NR)

$u Uniform Resource Identifier (R)*

$v Source of information (R)*

$0 Record control number (R)

$2 Source of term (NR)



Do not give subfield $0. Give other subfields, as applicable, if readily available.
Capitalize the first word in subfield $a.



373 (R)

Associated group

$a Associated group (R)

$s Start period (NR)

$t End period (NR)

$u Uniform Resource Identifier (R)*

$v Source of information (R)*

$0 Record control number (R)

$2 Source of term (NR)



Do not give subfield $0. Give other subfields, as applicable, if readily available.
Give the affiliation in the form found on the resource.



374 (R)


Occupation

$a Occupation (R)

$s Start period (NR)

$t End period (NR)

$u Uniform Resource Identifier (R)*

$v Source of information (R)*

$0 Record control number (R)

$2 Source of term (NR)



Do not give subfield $0. Give other subfields, as applicable, if readily available.
Capitalize the first word in subfield $a.



375 (R)


Gender

$a Gender (R)

$s Start period (NR)

$t End period (NR)

$u Uniform Resource Identifier (R)*

$v Source of information (R)*

$2 Source of term (NR)


Give subfields, as applicable, if readily available.



376 (R)


Family information

$a Type of family (R)

$b Name of prominent member (R)

$c Hereditary title (R)

$s Start period (NR)

$t End period (NR)

$u Uniform Resource Identifier (R)*

$v Source of information (R)*

$0 Record control number (R)

$2 Source of term (NR)



Do not give subfield $0. Give other subfields, as applicable, if readily available. For names of prominent members, give the authorized access point form.



377 (R)


Associated language

$a Language code (R)

$l Language term (R)

$2 Source of code (NR)



Give subfield $a if readily available. Use blank as 2nd indicator (using the MARC language code list; do not give subfield $2). Use $l for specific language when $a code is a ‘bucket’ code

378 (NR)

Fuller form of personal name

$q Fuller form of personal name (R)

$u Uniform Resource Identifier (R)*

$v Source of information (R)*



Give only as applicable to 100, not 400

380 (R)

Form of work

$a Form of work (R)

$0 Record control number (R)

$2 Source of term (NR)



Do not give subfield $0. Give other subfields, as applicable, if readily available.


381 (R)

Other distinguishing characteristics of work or expression

$a Other distinguishing characteristic (R)

$u Uniform Resource Locator (R)*

$v Source of information (R)*

$0 Record control number (R)

$2 Source of term (NR)



Do not give subfield $0. Give other subfields, as applicable, if readily available.



382 (R)

Medium of performance

$a Medium of performance (R)

$0 Record control number (R)

$2 Source of term (NR)



Do not give subfield $0. Give other subfields, as applicable, if readily available.
Do not use newly defined subfields $b, $d, $p, $n, $s, $v or first indicator until LC implementation is announced.


383 (R)

Numeric designation of a musical work

$a Serial number (R)

$b Opus number (R)

$c Thematic index number (R)

$d Thematic index code (NR)

$e Publisher associated with opus number (NR)

$2 Source (NR)


Give one or more subfields as appropriate.

384 (NR)

Key

$a Key


Give subfield $a if readily available, using 1st indicator of # (relationship to original unknown,) 0 (original). or 1 (transposed) as appropriate.

400-411 $e

Relator code

Do not give relationship designators in 400-411 fields.

400-430 $i

Relationship information

Do not give relationship information in 400-430 fields.

500-530


Subfields for relationship designators

$i Relationship information

$4 Relationship code

$w/0 Control subfield - special relationship

-- value “i” Reference instruction phrase in subfield $i, or

-- value “r” Relationship designation in subfield $i or $4



Use subfield $w for relationships included there: earlier/later, pseudonym. Use subfield $i for other relationships; give RDA appendix J term (name/title or title in 500-530) or appendix K term (name in 500-511) according to LC policy for these relationships.
Do not give subfield $4.
When using subfield $i, give value “r” in subfield $w/0.


*Use of $v and $u in Authority Format fields

The following represents PCC practice on recording sources of information in $u and $v in fields where they are defined, and/or in field 670:

1. 670s must be used to support information used as part of a heading in 1XX and 4XX.

2. For 046, 37X, 381:

a. if the same source is already cited in the 670, no $v is needed

b. use $v if the source is not cited in a 670

c. optionally, use $v even if the same source is cited in a 670

3. Use of $u is optional, and should always be preceded by $v.


Coding Dates in Field 046

Some dates can be coded easily using ISO 8601 in the appropriate subfield of optional field 046; others need a specialized standard such as the Extended Date/Time Format (EDTF)—here are typical examples of each:




RDA dates in ISO 8601 date scheme (no need to provide a source in $2)

Category

RDA presentation

ISO 8601 coding in 046

Single year

1964

1964

Year/Month/Day

1964 June 27

19640627

Early A.D. date

65 A.D.

0065

B.C. date

361 B.C.

-0360 (note there is a difference of one because the B.C. system has no year zero)

Century

20th century

19




RDA dates in EDTF date scheme (provide ‘edtf’ in 046 $2)

Category

RDA presentation

EDTF coding in 046

Probable date

1816?

1816?

Approximate date

Approximately 931

0931~

Known to be one of two years

1666 or 1667

[1666,1667]




LC Training for RDA: R-document R-5 MARC21 changes (LC)

May 29, 2012


База данных защищена авторским правом ©shkola.of.by 2016
звярнуцца да адміністрацыі

    Галоўная старонка