X11 - Meeting Names-General Information
MARC 21 Community Information
October 2007
"Full" documentation refers to the MARC 21 Format for Community Information that contains detailed descriptions of every data element, along with examples, input conventions and history sections.
"Concise" documentation refers to the MARC 21 Concise Format for Community Information that contains abridged descriptions of every data element, along with examples.
611 - Subject Added Entry - Meeting Name (R)
Full |
Concise
First Indicator
Type of meeting name entry element
0 - Inverted name
1 - Jurisdiction name
2 - Name in direct order |
Second Indicator
111
-
Undefined
# - Undefined
611
-
Thesaurus
0 - Library of Congress Subject Headings
1 - LC subject headings for children's literature
2 - Medical Subject Headings
3 - National Agricultural Library subject authority file
4 - Source not specified
5 - Canadian Subject Headings
6 - Répertoire de vedettes-matière
7 - Source specified in subfield $2
711
-
Undefined
# - Undefined |
|
|
Subfield Codes
|
Name portion
$a - Meeting name or jurisdiction name as entry element (NR)
$c - Location of meeting (NR)
$d - Date of meeting (NR)
$e - Subordinate unit (R)
$j - Relator term (R)
$q - Name of meeting following jurisdiction name entry element (NR)
$u - Affiliation (NR)
$4 - Relator code (R)
Title portion
$f - Date of a work (NR) [611/711]
$p - Name of part/section (R) [611/711]
$s - Version (NR) [611/711]
$t - Title (NR) [611/711] | Name and title portions
$g - Miscellaneous information (NR)
$n - Number of part/section/meeting (R)
Subject subdivision portion
$v - Form subdivision (R) [611]
$x - General subdivision (R) [611]
$y - Chronological subdivision (R) [611]
$z - Geographic subdivision (R) [611]
Control subfields
$0 - Authority record control number (R
$2 - Source of heading or term (NR) [611]
$6 - Linkage (NR)
$8 - Field link and sequence number (R) |
GUIDELINES FOR APPLYING CONTENT DESIGNATORS
Subelements occurring in meeting name fields. 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.
Guidelines for applying all content designators except the second indicator position are
given in this section. A field-specific list of content designators and guidelines for
applying the second indicator position are provided under the description for each
specific X11 field.
■ INDICATORS
First Indicator - Type of meeting name entry element Form of the entry element of the field. The values distinguish among an inverted
personal name, a jurisdiction name, and a meeting name in direct order used as the
entry element.
0 - Inverted name Meeting name begins with a personal name in inverted order (surname,
forename).Meeting names beginning with a personal surname alone, a personal name in
direct order (not inverted), or containing a personal name other than as the
entry element are identified by value 2.
1 - Jurisdiction name Jurisdiction name under which a meeting name is entered.Meeting names containing a jurisdiction name as an integral part of the name or
qualified by a jurisdiction name are identified by value 2.
2 - Name in direct order Heading may contain a parenthetical qualifier or may be an acronym or
initialism.
Second Indicator Unique to the function of the meeting name field. It is described under the
following fields: 111 (Primary Name-Meeting); 611 (Subject Added Entry-Meeting
Name); or 711 (Added Entry-Meeting Name).
■ SUBFIELD CODES
$a - Meeting name or jurisdiction name as entry element Name of a meeting or a jurisdiction name under which a meeting is entered.
Parenthetical qualifying information is not separately subfield coded.
$c - Location of meeting Place name or a name of an institution where a meeting is held. Multiple adjacent
locations are contained in a single subfield $c.
Place name is added parenthetically to a meeting name to distinguish between
identical names is not separately subfield coded.
$d - Date of meeting Date is added parenthetically to a meeting name to distinguish between identical
names is not separately subfield coded.
$e - Subordinate unit Name of a subordinate unit entered under a meeting name.
$f - Date of a work [611/711]Date of publication used with a title of a work in a name/title field.
$g - Miscellaneous information Data element that is not more appropriately contained in another defined
subfield.
$j - Relator term Describes the relationship between a name and a community information entity.
$n - Number of part/section/meeting In music uniform titles, the serial, opus, or thematic index number, or a date
used to distinguish one work from another, is contained in subfield $n.
Multiple alternative numberings (often separated by a comma) are contained in a
single subfield $n. Multiple numberings that are hierarchical (often
separated by a period) are contained in separate occurrences of subfield
$n.
$p - Name of part/section [611/711]Name designation of a part/section of a work used with a title in a
name/title field. It can also contain a name designation of a
part/section of an event, program, etc. used with a title of an event, program,
etc. in a name/title field.
$q - Name of meeting following jurisdiction name entry element Meeting name that is entered under a jurisdiction name contained in subfield
$a.
$s - Version [611/711]Version, edition, etc., information added to a title of a work in a name/title
field.
$t - Title [611/711]Title page title of a work or the name of an event, program, etc. used in a
name/title field.
$u - Affiliation Affiliation or address of the meeting or conference.
$v - Form subdivision [611]Form subdivision that designates a specific kind or genre of material as defined
by the thesaurus being used. Subfield $v is appropriate only when a
form subject subdivision is added to a meeting name or name/title heading to form
an extended subject heading. Subfield $v is used for form terms when
they function as indicated above. Subfield $x may be used if the terms
function as general subdivisions. A form subdivision in subfield $v is
generally the last subfield in the field. The subfield may be repeated if more
than one form subdivision is used.
|
|
|
|
|
|
|
|
|
|
| 611 |
20$aPurdue Pest Control Conference$vPeriodicals. |
| 611 |
20$aInternational Congress of Writers for the Defense of
Culture$n(1st :$d1935:$cParis, France)$vFiction.
|
$x - General subdivision [611]Subject subdivision that is not more appropriately contained in subfield
$v (Form subdivision), subfield $y (Chronological
subdivision) or subfield $z (Geographic subdivision). Subfield
$x is appropriate only when a general topical subdivision is added to a
name or a name/title.
$y - Chronological subdivision [611]Subject subdivision that represents a period of time. Subfield $y is
appropriate only when a chronological subject subdivision is added to a name or a
name/title field.
$z - Geographic subdivision [611]Geographic subject subdivision. Subfield $z is appropriate only when a
geographic subject subdivision is added to a name or a name/title field.
$0 - Authority record control number
$2 - Source of heading or term [611]MARC code that identifies the thesaurus or authority file that is the source list
from which the heading or term in a Subject Added Entry field was assigned. It is
used only when the second indicator position contains value 7 (Source specified in
subfield $2). Code from:
MARC Code
Lists for Relators, Sources, Description Conventions.
$4 - Relator code MARC code that specifies the relationship between a name and a community
information entity. More than one relator code may be used if the meeting has more
than one function. Code from:
MARC Code Lists for Relators,
Sources, Description Conventions . The code is given after the name portion in name/title fields.
$8 - Field link and sequence number
INPUT CONVENTIONS
Ambiguous Headings - See Appendix D: Ambiguous Headings.
Punctuation - Fields 111, 611, and 711 end with a mark of punctuation or a closing parenthesis. If the
final subfield is subfield $0, $2 or $4, the mark of punctuation or
closing parenthesis precedes these subfields. The name portion of a name/subordinate
body or name/title field ends with a mark of punctuation. The mark of punctuation is
placed inside a closing quotation mark. A name or title portion followed by a subject
subdivision does not end with a mark of punctuation unless the name or title portion
ends with an abbreviation, initial/letter, or open date.
Spacing - No spaces are used in initialisms or personal name initials/letters. One space is used
between preceding and succeeding initials if an abbreviation consists of more than a
single phrase.
Display Constant - Dash that precedes a subject subdivision in an extended subject heading is not carried
in the machine-readable record. It may be system generated as a display constant
associated with the content of subfields $v, $x, $y,
and $z.
Initial Articles - Initial articles (e.g., Het) occurring at the beginning of name heading fields are
usually omitted in most languages (except when the intent is to file on the article).
Initial articles occurring at the beginning of the title and/or part portion of a
name/title added entry (i.e., 611 or 711) are also omitted. Any diacritics and/or
special characters occurring at the beginning of fields are retained. Note that such
characters are usually ignored for purposes of sorting and filing.
CONTENT DESIGNATOR HISTORY
$j - Relator term [NEW, 2006]
$0 - Authority record control number [NEW, 2007]