Meeting Names--General Information
Record Type |
||
BIB |
||
Input Standards |
||
Applicable Fields (R=Repeatable NR=Nonrepeatable) | Input Standards (Full/Minimal) | |
111 | Main Entry--Meeting Name (NR) | Required if applicable/Required if applicable |
611 | Subject Added Entry--Meeting Name (R) | Required if applicable/Optional |
698 | Local Subject Added Entry--Meeting Name (R) | Optional/Optional |
711 | Added Entry--Meeting Name (R) | Required if applicable/Required if applicable |
792 | Local Added Entry--Meeting Name (R) | Optional/Optional |
798 | Local Added Entry--Meeting Name (R) | Optional/Optional |
811 | Series Added Entry--Meeting Name (R) | Required if applicable/Optional |
898 | Local Series Added Entry--Meeting Name (R) | Optional/Optional |
1st Indicator Type of conference or meeting name entry element [All fields] | ||
0 | Inverted name | |
1 | Jurisdiction name | |
2 | Name in direct order | |
2nd Indicator Undefined [111, 811, 898] | ||
Undefined | ||
2nd Indicator Thesaurus [611, 698] | ||
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 | |
2nd Indicator Type of added entry [711, 792, 798] | ||
No information provided | ||
2 | Analytical entry | |
Subfields (R=Repeatable NR=Nonrepeatable) | Input Standards (Full/Minimal) | |
ǂa | Meeting name or jurisdiction name as entry element (NR) [All fields] | Mandatory/Mandatory |
ǂc | Location of meeting (R) [All fields] | Required if applicable/Required if applicable |
ǂd | Date of meeting or treaty signing (R) [All fields] | Required if applicable/Required if applicable |
ǂe | Subordinate unit (R) [All fields] | Required if applicable/Required if applicable |
ǂg | Miscellaneous information (R) [All fields] | Required if applicable/Required if applicable |
ǂj | Relator term (R) [All fields] | Optional/Optional |
ǂn | Number of meeting (R) [All fields] | Required if applicable/Required if applicable |
ǂq | Name of meeting following jurisdiction name entry element (NR) [All fields] | Required if applicable/Required if applicable |
ǂu | Affiliation (NR) [All fields] | Optional/Optional |
ǂv | Form subdivision (R) [611, 698] | Required if applicable/Required if applicable |
ǂx | General subdivision (R) [611, 698] | Required if applicable/Required if applicable |
ǂy | Chronological subdivision (R) [611, 698] | Required if applicable/Required if applicable |
ǂy | Data provenance (R) [811] | Optional/Optional |
ǂz | Geographic subdivision (R) [611, 698] | Required if applicable/Required if applicable |
ǂ0 | Authority record control number or standard number (R) [All fields] | Optional/Optional |
ǂ1 | Real World Object URI (R) [All fields] | Optional/Optional |
ǂ2 | Source of heading or term (NR) [All fields] | Required if applicable/Required if applicable |
ǂ3 | Materials specified (NR) [611, 698, 711, 792, 798, 811, 898] | Optional/Optional |
ǂ4 | Relationship (R) [All fields] | Optional/Optional |
ǂ5 | Institution to which field applies (NR) [711, 792, 798, 811, 898] | Required if applicable/Required if applicable |
ǂ6 | Linkage (NR) [All fields] | System supplied/System supplied |
ǂ7 | Data provenance (R) [111, 611, 711] | Optional/Optional |
ǂ8 | Field link and sequence number (R) [611] | Optional/Optional |
ǂ9 | Special entry (NR) [698, 798, 898] | Optional/Optional |
Definition |
A conference or meeting name used as an authorized access point. The access point is assigned according to various cataloging rules to give access to the bibliographic record from meeting names. Conference or meeting names can be entered directly under its own name or indirectly under the name of a corporate body. If you enter a conference or meeting name indirectly (i.e., under the name of a corporate body), see Corporate Names--General Information. Use for the following types of meeting names:
OCLC also makes available nonstandard MARC fields to use for access points not supported by cataloging rules (e.g., donor or gift information or variant form). Enter information in fields 698, 792, 798, or 898 as you would in the corresponding standard MARC fields. These fields are not retained in the WorldCat record. However, they are retained in exported records and records delivered via other services. This page does not cover the title portion of name/title access points. Refer to the Preferred Titles--General Information for further information on constructing title access points and title related subfields. For information on punctuation, see the Punctuation section below. |
||||||||||||||||||
Guidelines |
Guidelines and links to guidelines, for applying all content designators are given below. A field-specific list of content designators and guidelines for applying the 1st and 2nd indicator positions are provided under the description for fields that contain a conference or meeting name. For current cataloging, construct conference or meeting names according to Resource Description and Access (RDA), Anglo-American Cataloguing Rules, 2nd edition (AACR2), Library of Congress Subject Headings (LCSH), and Library of Congress/Program for Cooperative Cataloging (LC/PCC) practice. Search the OCLC Authority File to verify forms of authorized access points. Use the current RDA, AACR2, or AACR2-compatible forms of the authorized access points. If an access point is not found, construct the access point according to RDA or AACR2. For retrospective cataloging, search the OCLC Authority File to verify the forms of the authorized access points. Use the current RDA, AACR2, or AACR2-compatible forms of the authorized access points. If an access point is not found, you may enter the pre-RDA form, but you are encouraged to construct the access point according to RDA or AACR2. For help in coding ambiguous access points, see the Subject Heading Manual, H 405. Jurisdictions will appear in the authority file in field 151 but when used as descriptive access points they will be coded with an x10 with a 1st indicator 1. |
||||||||||||||||||
Modifications | If constructing a conference or meeting access point according to pre-RDA instructions, make the following modifications:
|
||||||||||||||||||
1st Indicator |
Type of meeting name entry element. Value that identifies the form of the entry element of the field. The values distinguish among an inverted personal name, a jurisdiction name, and a conference or meeting name in direct order used as the entry element. . |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
2nd Indicator |
The definition of the 2nd indicator position is specific to each field. |
||||||||||||||||||
111, 811, 898 | Undefined. The 2nd indicator position is undefined and contains a blank.
|
||||||||||||||||||
611, 698 | Thesaurus. The thesaurus or established subject terminology used in constructing the subject access point. For more information, see 6xx Introduction. |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
711, 792, 798 | Type of added entry. The values distinguish between no information provided and an analytical entry. |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
Subfields |
Limited examples are given in this section. Refer to each specific field listed in the Input Standards above for more examples. |
||||||||||||||||||
ǂa Meeting name or jurisdiction name as entry element | Name of a conference or meeting or a jurisdiction name under which a conference or meeting is entered. Parenthetical qualifying information is not coded in a separate subfield. Conference or meeting names are not entered under jurisdiction names in RDA or AACR2.
|
||||||||||||||||||
ǂc Location of meeting | Place or institution name where a conference or meeting was held. Qualify place names by the larger jurisdiction as appropriate. Enter each subsequent location in a separate subfield ǂc.
|
||||||||||||||||||
ǂd Date of meeting or treaty signing | The actual or projected date or dates of a conference or meeting. For a date of treaty signing used with a title in a name/title field, see Preferred Titles--General Information.
|
||||||||||||||||||
ǂe Subordinate unit | Name of a subordinate unit entered under a conference or meeting name.
|
||||||||||||||||||
ǂg Miscellaneous information | Data not identified in other subfields. Use for subelements that are not more appropriately contained in subfield, ǂa, ǂb, ǂc, ǂd, ǂe, ǂn, or ǂq. Subfield ǂg is unlikely to be used. |
||||||||||||||||||
ǂj Relator term | A designation of function that describes the relationship between a corporate name and a work (e.g. work, expression, manifestation, item). For more information, see the PCC Training Manual for Applying Relationship Designators in Bibliographic Records.
|
||||||||||||||||||
ǂn Number of meeting | The number of a conference or meeting. For a number designation for a part/section of a work used with a title in a name/title field, see Preferred Titles--General Information for further information on constructing title access points and title related subfields.
|
||||||||||||||||||
ǂq Name of meeting following jurisdiction name entry element | Meeting name that is entered under a jurisdiction name contained in subfield ǂa. Under AACR2 and RDA cataloging instructions a conference or meeting name is entered in direct order in an x11 field or is entered subordinately under a corporate body in an x10 field. When possible, revise an access point that requires subfield ǂq to conform to AACR2 or RDA.
|
||||||||||||||||||
ǂu Affiliation | The affiliation or address of the conference or meeting name in subfield ǂa. Subfield ǂu is most commonly used for technical reports.
|
||||||||||||||||||
ǂv Form subdivision | A specific kind or genre of material defined by the thesaurus being used. Use only when a genre/form subdivision is added to a conference or meeting name. A form subdivision in subfield ǂv is generally the last subdivision in a subject access point. Enter each subsequent form subdivision in a separate subfield ǂv.
|
||||||||||||||||||
ǂx General subdivision | A subject subdivision that is not more appropriately contained in subfield ǂv, ǂy, or ǂz. Use subfield ǂx only when a topical subject subdivision is added to a conference or meeting name. Enter each subsequent topical subdivision in a separate subfield ǂx.
|
||||||||||||||||||
ǂy Chronological subdivision | A subject subdivision that represents a period of time. Use only when a chronological subject subdivision is added to a conference or meeting name. Enter each subsequent chronological subdivision in a separate subfield ǂy.
|
||||||||||||||||||
ǂy Data provenance | For information about subfield ǂy, see Data Provenance Subfields. |
||||||||||||||||||
ǂz Geographic subdivision | A subject subdivision that represents a jurisdiction or location. Use only when a geographic subject subdivision is added to a conference or meeting name. Enter each subsequent subdivision in a separate subfield ǂz.
|
||||||||||||||||||
ǂ0 Authority record control number or standard number | For information about subfield ǂ0, see Control Subfields. |
||||||||||||||||||
ǂ1 Real World Object URI | For information about subfield ǂ1, see Control Subfields. |
||||||||||||||||||
ǂ2 Source of heading or term | For information about subfield ǂ2, see Control Subfields. |
||||||||||||||||||
ǂ3 Materials specified | For information about subfield ǂ3, see Control Subfields. |
||||||||||||||||||
ǂ4 Relationship | For information about subfield ǂ4, see Control Subfields. |
||||||||||||||||||
ǂ5 Institution to which field applies | For information about subfield ǂ5, see Control Subfields. |
||||||||||||||||||
ǂ6 Linkage | Data that link fields when non-Latin script is entered. This subfield is system supplied and does not appear in OCLC online displays. Do not manually add subfield ǂ6. For more information about subfield ǂ6, see Control Subfields. |
||||||||||||||||||
ǂ7 Data provenance | For information about subfield ǂ7, see Data Provenance Subfields. |
||||||||||||||||||
ǂ8 Field link and sequence number | For information about subfield ǂ8, see Control Subfields. Subfield ǂ8 is used infrequently. |
||||||||||||||||||
ǂ9 Special entry | For information about subfield ǂ9, see Control Subfields. |
||||||||||||||||||
Punctuation |
Punctuation of the subelements of an access point is generally dictated by descriptive cataloging or subject system/thesaurus rules. These input conventions clarify MARC punctuation practices. Fields 111, 611, 711, and 811 may optionally end with terminal punctuation. Terminal punctuation consists of one of the following: ellipsis, hyphen, period, closing parenthesis, exclamation point, and question mark. Currently, the control heading process adds terminal periods to access points. If the final subfields are subfield ǂu, ǂ0, ǂ1, ǂ2, ǂ3, ǂ4, or ǂ5, the terminal punctuation precedes the first instance of those subfields. If the final subfield is ǂj, add a comma after the access point unless the access point ends with an open date. Separate multiple relator terms with commas and add a period after the last subfield ǂj. A conference or meeting name portion of a name/subordinate body or name/title access point ends with terminal punctuation. When an authorized access point ends with a quotation mark, the terminal punctuation is placed before the quotation mark. In the case of a conference or meeting name input as a subject access point and followed by a subject subdivision, omit the terminal punctuation unless the name ends with an abbreviation or initial/letter. See also 6xx Introduction for specific subject access point guidelines. Qualifier elements:
Non-qualifier elements:
For more information on punctuation, including OCLC policy, see section 2.8, Punctuation. |
||||||||||||||||||
Indexing |
For indexing and searching information, see Searching WorldCat Indexes for fields: 111, 611, 711, and 811. |
||||||||||||||||||
MARC 21 |
For more information, including content designator history, see MARC 21 Format for Bibliographic Data, x11. |