Field definition and scope:

Field 111 contains a meeting or conference name used as a main entry in a bibliographic record.  According to various cataloging rules, main entry under a meeting name is assigned to works that contain proceedings, reports, etc.  (For guidelines on meeting names, select:  Ambiguous headings for Meeting Names.)

Meetings entered subordinately to a corporate body that are used as main entries are recorded in field 110.

The National level record requirement for this field is Mandatory if applicable.

Field 111 is NOT repeatable.

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.

For indicator and subfield code definitions and examples, National-level (NLR) and Minimal-level (MLR) record requirements, and designator repeatability, see table below:

Position

Description

NLR

MLR

Repeatability

Field 111

Main Entry - Meeting Name

A

A

NR

Indicator:

 

 

 

 

First

Type of meeting name entry element

M

 

 

0

Inverted name

A

 

 

1

Jurisdiction name

A

 

 

2

Name in direct order

A

 

 

 

 

 

 

 

Second

Undefined; contains a blank

M

 

 

 

 

 

 

 

Subfield code:

 

 

 

 

$a

Meeting name or jurisdiction name as entry element

M

M

NR

$c

Location of meeting

A

A

R

$d

Date of meeting

A

A

NR

$e

Subordinate unit

A

A

R

$f

Date of a work

A

O

NR

$g

Miscellaneous information

A

O

R

$j

Relator term

O

O

R

$k

Form subheading

A

O

R

$l

Language of a work

A

O

NR

$n

Number of part/section/meeting

A

A

R

$p

Name of part/section of a work

A

O

R

$q

Name of meeting following jurisdiction name entry element

A

O

NR

$t

Title of a work

A

O

NR

$u

Affiliation

O

O

NR

$0

Authority record control number or standard number

O

O

R

$4

Relationship

O

A

R

$6

Linkage

A

A

NR

$8

Field link and sequence number

O

O

R

 

See:  Examples for this field.

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  (BK MU SE)  [obsolete]:  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).

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 $g - Miscellaneous information  [changed, 2014]:  In 2014, subfield $g was made repeatable.

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 $0 - Authority record control number  [new, 2007]

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

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.

Related MARC fields or documents:

X11  Meeting Names - General Information

RDA in MARC Bibliographic Data

See also:

1XX  Main Entry Fields

Variable Data Fields