Field definition and scope:

Each meeting name field is unique in its definition and scope.  For specific information, select from the list below.

111  Main Entry - Meeting Name  (NR)

411  Series Statement - Meeting Name  (R)  (USA only)

611  Subject Added Entry - Meeting Name  (R)

711  Added Entry - Meeting Name  (R)

811  Series Added Entry - Meeting Name  (R)

Record requirements:  The National level record requirement for the meeting name fields is Mandatory if applicable.  For the national level requirements by subfield, and the minimal level record and subfield requirements, see the specific field.

Field repeatability:  See the specific field for its repeatability.

Guidelines for applying content designators:

The content designators identify the subelements occurring in meeting name fields constructed according to the generally accepted cataloging and thesaurus-building rules [e.g., Anglo-American Cataloguing Rules (AACR 2), Library of Congress Subject Headings (LCSH)].

A named meeting that is entered under a corporate name is contained in the X10 fields.  Corporate names that include such words as conference or congress are also contained in the X10 fields.  For example, the Congress of Neurological Surgeons, a professional group, is a corporate name.

The indicators, subfield codes, and input conventions for the meeting name fields 111, 411, 611, 711, and 811 follow similar patterns.  Guidelines for applying the first indicator and subfield codes are below.  Subfields are grouped by type of entry.  See the specific field for the second indicator information.

For indicator and subfield code definitions and examples, National-level (NLR) and Minimal-level (MLR) record requirements, and designator repeatability, see table below.  An asterisk ( * ) in the column indicates that the requirement varies.  See table in the specific field.:

Position

Description

NLR

MLR

Repeatability

Field X11

Meeting Names

A

*

*

Indicator:

 

 

 

 

First

Type of meeting name entry element

M

 

 

0

Inverted name

A

 

 

1

Jurisdiction name

A

 

 

2

Name in direct order

A

 

 

 

 

 

 

 

Second

Second indicator position

M

 

 

 

 

 

 

 

Subfield code:

 

 

 

 

 

Name portion

 

 

 

$a

Meeting name or jurisdiction name as entry element

M

*

NR

$c

Location of meeting

A

*

R

$d

Date of meeting or treaty signing

A

*

R

$e

Subordinate unit

A

*

R

$j

Relator term

O

O

R

$q

Name of meeting following jurisdiction name entry element

A

O

NR

$u

Affiliation

O

O

NR

$4

Relationship

O

*

R

 

 

 

 

 

 

Title portion

 

 

 

$f

Date of a work

A

O

NR

$h

Medium  [611, 711, 811]

O

O

NR

$i

Relationship information  [711]

O

O

R

$k

Form subheading

A

O

R

$l

Language of a work

A

O

NR

$p

Name of part/section of a work

A

O

R

$s

Version  [611, 711, 811]

A

O

R

$t

Title of a work

*

O

NR

$v

Volume/sequential designation  [ 411, 811]

A

O

NR

$x

International Standard Serial Number  [ 411, 711, 811]

*

O

NR

 

 

 

 

 

 

Name and title portions

 

 

 

$g

Miscellaneous information

A

O

R

$n

Number of part/section/meeting

A

*

R

 

 

 

 

 

 

Subject subdivision portion

 

 

 

$v

Form subdivision  [611]

A

O

R

$x

General subdivision  [611]

A

O

R

$y

Chronological subdivision  [611]

A

O

R

$z

Geographic subdivision  [611]

A

O

R

 

 

 

 

 

 

Control subfields

 

 

 

$w

Bibliographic record control number  [811]

O

O

R

$0

Authority record control number or standard number

O

O

R

$1

Real World Object URI

 

 

R

$2

Source of heading or term

A

O

NR

$3

Materials specified  [611, 711, 811]

O

O

NR

$5

Institution to which field applies  [711, 811]

A

O

NR

$6

Linkage

A

*

NR

$7

Control subfield  [811]

 

 

NR

 

/0 - Type of record

 

 

 

 

/1 - Bibliographic level

 

 

 

$8

Field link and sequence number

O

O

R

Input conventions:

Ambiguous headings  (what is considered a "meeting" name)

Punctuation

Spacing

Initial articles  (includes information on diacritics or special characters)

Content designator history:

Second indicator - Main entry/subject relationship  [111]  (BK MU SE)  [obsolete, 1990]:  The use of the second indicator in field 111 to indicate the main entry/subject relationship was made obsolete in 1990.  The values were:  0 (Main entry/subject relationship irrelevant) and 1 (Main entry is subject).

Second indicator - Type of added entry  [711]

Values  0 - Alternative entry  (BK AM CF MP MU SE)  [obsolete]

1 - Secondary entry  (BK AM CF MP MU SE)  [obsolete]

1 - Printed on card  (VM)  [obsolete]

3 - Not printed on card  (VM)  [obsolete]

In 1993, second indicator values 0 (Alternative entry) and 1 (Secondary entry) were made obsolete in the books, archival and manuscripts control, computer files, maps, music, and serials specifications.  Values 1 (Printed on card) and 3 (Not printed on card) were made obsolete in the visual materials specifications.

Subfield $a - Meeting name or jurisdiction name as entry element  [redefined, 1972]

Subfield $b - Number  [obsolete, 1980]:  In 1980, the definition of subfield $n was expanded to include meeting numbers and subfield $b was made obsolete.

Subfield $c - Location of meeting  [changed, 2014]:  In 2014, subfield $c was made repeatable.

Subfield $d - Date of meeting  [redefined, 2017]:  Subfield $d was redefined and made repeatable.

Subfield $g - Miscellaneous information  [changed, 2014]:  In 2014, subfield $g was made repeatable.

Subfield $i - Relationship information  [711]  [new, 2009]

Subfield $j - Relator term  [new, 2006]

Subfield $n - Number of part/section/meeting  [new, 1979]

Subfield $p - Name of part/section of a work  [redefined, 1979]:  In 1979, subfield $n was defined for numbered parts/sections and subfield $p (Part) was redefined to include only named parts/sections.  Prior to that change, both the number and the name of a part were contained in one $p subfield.

Subfield $q - Name of meeting following jurisdiction name entry element  [new, 1972]:  The name of a meeting entered under a jurisdiction name was not separately subfield coded prior to the definition of subfield $q in 1972.  At the same time, subfield $a was expanded to include a jurisdiction name as entry element.

Subfield $s - Version  [changed, 2017]:  Subfield $s was made repeatable.

Subfield $w - Bibliographic record control number  [811]  [new, 2007]

Subfield $x - International Standard Serial Number  [811]  [new, 2008]

Subfield $0 - Authority record control number  [new, 2007]

Subfield $0 - Authority record control number  [redefined, 2010]

Subfield $1 - Real World Object URI  [new, 2017]

Subfield $2 - Source of heading or term  [111, 711, 811]  [new, 2019]:  Subfield $2 was previously defined in field 611 only.

Subfield $3 - Materials specified  [811]  [new, 2008]

Subfield $4 - Relator code  [renamed, 2017] [redescribed, 2017]:  Subfield $4 was renamed to Relationship and redescribed to allow for the recording of relationship URIs in addition to MARC and non-MARC codes.

Subfield $5 - Institution to which field applies  [811]  [new, 2010]

Subfield $7 - Control subfield  [811]  [new, 2013]

For specific field information, select a field:

111  Main Entry - Meeting Name

411  Series Statement - Meeting Name  (USA only)

611  Subject Added Entry - Meeting Name

711  Added Entry - Meeting Name

811  Series Added Entry - Meeting Name

Related MARC fields or documents:

RDA in MARC Bibliographic Data

MARC Code List for Organizations

MARC Code List for Relators

Source Codes for Vocabularies, Rules, and Schemes

See also:

Headings:  X00-X30 Fields

Variable Data Fields