Tag 100 and names tags
Discover how names tags are used in OLIB.
| Tag(s) | 100, 110, 111, 600, 610, 611, 700, 710 and 711 |
|
|---|---|---|
| Indicators | 0-3, 0-7 | For 100, 600 and 700: The first indicator specifies whether the name given in $a begins with a Forename (0) or Surname (1) or specifies a Family Name (3) The value is retrieved from authors.firstind. If this is blank, then it will be set to '0' if there is no forename or '1' if there is a Forename. For the other tags this indicator advises the construction of the name specified in $a: Inverted, Jurisdiction or Name in Direct Order The value is retrieved from authors.firstind. If this is blank, then it will be set to '2'. The second indicator is undefined for the Main Entry tags (100, 110, 111). Refer to Subject handling notes for the meanings of the second indicator for 600, 610 and 611. |
| Subfields | a, b, c, q, d, g, t, u, 4 and 0 | These subfields are imported, defaulted and/or exported such that maintaining them manually should not be required for the vast majority of cataloguing activity. |
| Imports to | The data in these tags import into the Names domain and are linked to the Title during import. See below for a breakdown of this information. | |
| Exports from | Data for these tags are extracted from the Names linked to the Title during export. See below for a breakdown of this information. |
For the MARC21 notes on this tag, start here.
Example value:
17 $aPotter, Harry $c(Fictitious character) $2fast $0(OCoLC)fst01073565
| Subfield | Sample | Notes |
|---|---|---|
| a | Potter, Harry | This is mapped to the Surname, Forename and Initials fields in the Names domain for a Name linked to the Title being created/exported. The Surname value maps to and from the text up to the first comma (,). After this, the Forename value is mapped. During import initials are generated from the Forename text. |
| b | VI | Numeration - This value is mapped to and from the Numerals attribute in the Names domain. For Corporate Names this is mapped to and from the Subordinate Unit field. Whilst this is repeatable, OLIB only handles only a single occurrence per tag. |
| n | 32nd | Number of Part/Section/Meeting - For Corporate and Conference Names, this value is mapped to and from the Numerals attribute in the Names domain. Whilst this is repeatable, OLIB only handles only a single occurrence per tag. |
| c | (Fictitious character) | Titles and other words associated with the name. This subfield is repeatable, but OLIB handles only a single occurrence per tag. This maps to and from the Title attribute in the Names domain. Parentheses are added and removed automatically and need not be entered into the field during cataloguing. |
| Sheffield | For Corporate and Conference Names this is mapped to and from the Location field. | |
| q | Thomas Stearns | Fuller Form of Name / Meeting Name Following Jurisdiction Heading. For personal names this maps to and from the Fuller Form Of Name attribute in the Names domain. Parentheses are added and removed automatically and need not be entered into the field during cataloguing. For Conference names this maps to and from the Meeting Name Following Jurisdiction Heading attribute. This is labelled "Jurisdiction Meeting". NB: This mapping was corrected to the above in Service Pack 12. |
| d | 1564-1616 | This value is mapped to the Textual dates field in the Names domain. The value is parsed during import to ascertain, where possible, a date of birth (or establishment for Corporate Names) and potentially a date of death/cessation of business. Whilst this is repeatable for Corporate Names, OLIB only handles only a single occurrence per tag. |
| g | Miscellaneous information - this is mapped to and from the Notes attribute in the Names domain. Whilst this is repeatable, OLIB only handles only a single occurrence per tag. | |
| t | Hamlet | Title of Work - this is mapped to and from the Title of Work attribute in the Names domain. |
| u | Hogwarts | Affiliation - this is mapped to and from the Affiliation attribute in the Names domain. |
| e, j, 4 | editor | These Relator Term ($j for Conference Names) and Relator Codes subfield values are used to determine the Responsibility Type during import. The Export will supply a $4 from the first such Relator code associated with the Responsibility Type. For Corporate Names $e is mapped to and from the Subordinate Unit field. |
| 0 | orcid.org/0000-0002-1694-233X | This subfield is used by import and export to match authors on import and to provide the ORCiD, ISNI and/or VIAF number on export. When importing ORCiD, ISNI or VIAF data the qualifier is removed and the value is placed into the appropriate field in the Names domain. For Subject name records, such as the Potter, Harry example above, "(OCoLC)fst01073565" will be placed into the Authors RCN field. This will not be exported in MARC exports. |
Subfields that are not itemised above are not handled by OLIB.
When the incoming data does not include a $0, the matching for a MARC Import to identify an existing Name authority record for linking to the Title being created will include subfields a, b, n, c, q, d and t where present. The matching will ignore punctuation and case.