511 See Also From Tracing - Meeting Name (R) (Variable Data Field)
Field 511 contains a tracing for a meeting name see also from reference. It is used in an established heading record or an established heading and subdivision record to trace a see also from reference from an established meeting name to a related established heading.
The National level record requirement for this field is Mandatory if applicable.
Field 511 is repeatable.
Guidelines for applying content designators:
The content designators identify the subelements occurring in meeting name headings 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) record requirements, and designator repeatability, see table below:
| Position | Description | NLR | Repeatability | 
| Field 511 | See Also From Tracing - Meeting Name | A | R | 
| Indicator: | 
 | 
 | 
 | 
| First | M | 
 | |
| 0 | A | 
 | |
| 1 | A | 
 | |
| 2 | A | 
 | |
| 
 | 
 | 
 | 
 | 
| Second | Undefined; contains a blank | M | 
 | 
| 
 | 
 | 
 | 
 | 
| Subfield code: | 
 | 
 | 
 | 
| $a | M | NR | |
| $c | A | R | |
| $d | A | R | |
| $e | A | R | |
| $f | A | NR | |
| $g | A | R | |
| $h | O | NR | |
| $i | current - A earlier - A | R | |
| $j | O | R | |
| $k | A | R | |
| $l | A | NR | |
| $n | A | R | |
| $p | A | R | |
| $q | A | NR | |
| $s | A | R | |
| $t | A | NR | |
| $v | A | R | |
| $w | A | NR | |
| 
 | O | 
 | |
| 
 | O | 
 | |
| 
 | O | 
 | |
| 
 | O | 
 | |
| $x | A | R | |
| $y | A | R | |
| $z | A | R | |
| $0 | A | R | |
| $1 | 
 | R | |
| $4 | O | R | |
| $5 | A | R | |
| $6 | A | NR | |
| $8 | O | R | 
See: Examples for this field.
 Ambiguous 
 headings  (what is considered a "meeting" name)
Ambiguous 
 headings  (what is considered a "meeting" name)
 Display 
 constant for X11 fields
Display 
 constant for X11 fields
 Display 
 constants for cross references
Display 
 constants for cross references
 Second 
 Indicator - Nonfiling 
 characters  [obsolete]:  The second indicator position 
 was made obsolete in fields 111, 411, and 511 in 1993.  The values 
 were:  0-9 (Number of nonfiling 
 characters present).
Second 
 Indicator - Nonfiling 
 characters  [obsolete]:  The second indicator position 
 was made obsolete in fields 111, 411, and 511 in 1993.  The values 
 were:  0-9 (Number of nonfiling 
 characters present).
 Subfield $b 
 - Number  [obsolete]: 
  In 1980, the definition of subfield $n 
 was expanded to include meeting numbers and subfield $b 
 was made obsolete.  Records created before this change may contain 
 the number of the meeting in subfield $b.
Subfield $b 
 - Number  [obsolete]: 
  In 1980, the definition of subfield $n 
 was expanded to include meeting numbers and subfield $b 
 was made obsolete.  Records created before this change may contain 
 the number of the meeting in subfield $b.
 Subfield $c 
 - Location of meeting  [changed, 
 2014]:  In 2014, subfield $c 
 was made repeatable.
Subfield $c 
 - Location of meeting  [changed, 
 2014]:  In 2014, subfield $c 
 was made repeatable.
 Subfield $d 
 - Date of meeting  [redefined, 
 2017]:  In 2017, subfield $d 
 was redefined and made repeatable.
Subfield $d 
 - Date of meeting  [redefined, 
 2017]:  In 2017, subfield $d 
 was redefined and made repeatable.
 Subfield $g 
 - Miscellaneous 
 information  [changed, 
 2014]:  In 2014, subfield $g 
 was made repeatable.
Subfield $g 
 - Miscellaneous 
 information  [changed, 
 2014]:  In 2014, subfield $g 
 was made repeatable.
 Subfield 
 $i - Reference 
 instruction phrase  [redefined, 2009]:  Subfield 
 $i was renamed Relationship information and 
 broadened to include relationship designations in addition to textual 
 reference phrases.  The subfield was changed from Not repeatable 
 (NR) to Repeatable (R).
Subfield 
 $i - Reference 
 instruction phrase  [redefined, 2009]:  Subfield 
 $i was renamed Relationship information and 
 broadened to include relationship designations in addition to textual 
 reference phrases.  The subfield was changed from Not repeatable 
 (NR) to Repeatable (R).
 Subfield 
 $j - Relator 
 term  [new, 2006]
Subfield 
 $j - Relator 
 term  [new, 2006]
 Subfield $s 
 - Version  [changed, 2017]: 
  Subfield $s was made 
 repeatable.
Subfield $s 
 - Version  [changed, 2017]: 
  Subfield $s was made 
 repeatable.
 Subfields  $v 
 - Form subdivision 
  [redefined]
Subfields  $v 
 - Form subdivision 
  [redefined]
$0 - Record control number [new, 1997]
$0 - Record control number [redefined, 2010]
$3 - Authority record control number [obsolete, 1997] [CAN/MARC only]
In USMARC, from 1993 to 1995, subfield $v was defined as Record control number in the 7XX Heading Linking Entry fields. When subfield $v was adapted for form subdivisions in MARC bibliographic and authority heading fields in 1995, subfield $v was redefined as Form subdivision. In 1997, subfield $0 was added as Record control number in 5XX and 7XX fields.
 Subfield $w/0 
 - Print constant code 
  [redefined, 1997]  [CAN/MARC 
 only]:  The following values were redefined:  g 
 (Full name), h (Real name), and 
 i (Real name (reputedly)).  The 
 following values were made obsolete:  j 
 (Name originally), k (Name in 
 religion), l (Secular name), m (Stage name of), o 
 (Variant name), p (Abbreviated 
 name), q (Official name), r (Broader term), s 
 (Narrower term), x (Print constant 
 generated from tag value), and z 
 (Text carried in subfield $i).
Subfield $w/0 
 - Print constant code 
  [redefined, 1997]  [CAN/MARC 
 only]:  The following values were redefined:  g 
 (Full name), h (Real name), and 
 i (Real name (reputedly)).  The 
 following values were made obsolete:  j 
 (Name originally), k (Name in 
 religion), l (Secular name), m (Stage name of), o 
 (Variant name), p (Abbreviated 
 name), q (Official name), r (Broader term), s 
 (Narrower term), x (Print constant 
 generated from tag value), and z 
 (Text carried in subfield $i).
 Subfield 
 $w/0 - Special relationship
Subfield 
 $w/0 - Special relationship
Code r - Relationship information in subfield $i or $4 [new, 2009]
 Subfield 
 $w/1 - Tracing use restriction
Subfield 
 $w/1 - Tracing use restriction
Code h - No reference structures [new, 2007]
 Subfield 
 $w/2 - Earlier form of heading
Subfield 
 $w/2 - Earlier form of heading
Code x - Tracing is not the form of heading established under earlier cataloguing rules [obsolete, 1997] [CAN/MARC only]
 Subfield 
 $w/3 - Reference display
Subfield 
 $w/3 - Reference display
Code e - Note only generated from the tracing [obsolete, 1997] [CAN/MARC only]
Code i - Invisible see from reference [obsolete, 1997] [CAN/MARC only]
Code x - Reference is generated from the tracing [obsolete, 1997] [CAN/MARC only]
 Subfield $w/4 
 - Formerly established 
 heading code  [obsolete, 1997]  [CAN/MARC 
 only]:  The following values were defined:  d 
 (Formerly accepted heading replaced by the heading in the 1XX field), 
 s (Formerly accepted heading replaced 
 by other headings, one of which is in the 1XX field), and x 
 (Not a formerly accepted heading).
Subfield $w/4 
 - Formerly established 
 heading code  [obsolete, 1997]  [CAN/MARC 
 only]:  The following values were defined:  d 
 (Formerly accepted heading replaced by the heading in the 1XX field), 
 s (Formerly accepted heading replaced 
 by other headings, one of which is in the 1XX field), and x 
 (Not a formerly accepted heading).
 Subfield 
 $1 - Real 
 World Object URI  [new, 2017]
Subfield 
 $1 - Real 
 World Object URI  [new, 2017]
 Subfield $4 
 - Relationship code 
  [new, 2009]
Subfield $4 
 - Relationship code 
  [new, 2009]
 Subfield 
 $4 - Relationship 
 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 
 $4 - Relationship 
 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.
 511  See Also From Tracing - Meeting Name
  511  See Also From Tracing - Meeting Name
Tracings and References - 5XX Fields [General Information]
 511 
  See Also From Tracing - Meeting Name
  511 
  See Also From Tracing - Meeting Name
5XX See Also From Tracings [General Information]
Related MARC fields or documents:
X11 Meeting Names - General Information
Tracings and References - General Information
See also: