Home | Resources | Services | Hosting | Publications | Collaboration | Joining CERL | About CERL |

500 Related Personal Name (O;R)

Field Definition and Scope

This field contains one of the standard forms from another personal name record relating to the present record. It is repeatable, in order to link to more than one related record. The CERL Thesaurus number in $3 links to the other record. This field might be used in any record, it is not restricted to personal names records.

Application of Content Designators

Indicators

Indicator 1: undefined (blank) Type of Name Form
The first indicator specifies, whether the name form given in this field is fictional or non-fictional: * 0 Name (default) * 1 Fictional name

Indicator 2: Type of Input
The second indicator specifies, whether this field has been input manually or by automated addition. The value of this indicator has an impact on the behaviour of this field in automated update processes:

  • 0 Form of name has been input or corrected by cataloguer; this form of name cannot be overwritten in automated updating processes
  • 1 Form of name has been input by automated addition; review by cataloguer may be necessary

Subfields

$1 Sort Indicator (O;R)
see the description of numerical subfields

$3 CERL Thesaurus Record Identifier (O;NR) Subfield $3 holds the record identifier of the record describing the person named in this field. From this subfield a hyperlink is created in the CERL Thesaurus web interface. Further, the use of subfield $3 provides for the retrieval of this record from the target record by the Related Records function.

$5 Tracing and Indexing Control (M;NR)
Subfield $5 contains a two letter code of which the first letter indicates the kind of relationship between the the name given in this field and the entity described by the record which contains the present field. * a The person named in this field is the predecessor of the entity described by the record as a whole. * b The person named in this field is the successor of the entity described by the record as a whole. * f The person named in this field has a family relationship with the entity described by the record as a whole. * s The person named in this field has worked with / is a collaborator of the entity described by the record as a whole. * t The person named in this field is a student of the entity described by the record as a whole. * z The type of the relationship of the person named in this field and the entity described by the record as a whole is not specified. The second character position specifies the whether the name given in this field is indexed/displayed or not. This code does affect only the standard (full) display, it has no impact on records displayed in the internal format view. * 0 Name in $a etc. is indexed and displayed. * 1 Name in $a etc. is not indexed but displayed. * 2 Name in $a etc. is indexed but not displayed. * 3 Name in $a etc. is neither indexed nor displayed. This subfield is not repeatable. Its use is mandatory in every occurrence of this field.


$6 Source File Reference (O;NR)
see the description of numerical subfields.


$8 Language Code (O;R)
see the description of numerical subfields. Mandatory to precede each subfield $n.

$a Entry Element (M;NR)
Subfield $a contains the part of the name used as the entry element in a heading. This is in most cases the last name. The use of this field is mandatory in every occurrence of this field.

$b First name (O;NR) Subfield $b contains the part of the name that does not form the entry element in a heading. This is in most cases the first name. Additions to the name like epithets or Roman numeration should be given in subfield $r.

$e Non-sorting Part of Name (O;NR)
Any part of the entry element, which would be skipped if entry elements are sorted alphabetically.

$n General Note (O;R)
Any note or comment on the person named in this field or the relationship between this person and the entity described by the record as a whole. This subfield is always preceded by a subfield $8 indicating the language of this subfield's content.

$r Addition to the Name (O;R)
Subfield $r contains any addition to the name given in this field. This might be an epithet, a Roman numeral or any other filing qualifier used by the underlying source file or prescribed by the applied cataloguing rules.

$s Source Note (O;R)
Subfield $s contains a reference to the source consulted by the cataloguer for this specific information. The use of this subfield shall be restricted to information specifically explaning the relationsip to the personal named in this field. All other source information will be carried by the related record.
This subfield should be used only in case the source reference has not been given in field 290 Source referred to in a record (O;NR) or in case two or more sources hold contradicting information.

$z Chronological Note (O;NR)
Subfield $z contains a year or a range of years indicating that the relationship between the person named in this field and the entity described by the record itself is connected or limited to a certain point in time or a certain time period. It should not contain the biographical data of the person mentioned in this field.
E.g. if a field 500 in a record gives the name of the husband of the person described by the record as a whole, subfield $z of this field would contain the beginning and end of the marriage.

$9 Temporary Data (O;NR)
see the description of numerical subfields.

$0 Type of Relationship (M;NR)
An indication of the type of the relationship between the entity described in the record and the person mentioned in this field. The following values are currently supported:

ex:hasPredecessorthe person is the predecessor of the entity described in the record
ex:hasSuccessorthe person is the successor of the entity described in the record
ex:hasFamilyRelationthe person is kin to the entity described in the record
ex:hasCollaboratorthe person is a collaborator of the entity described in the record
ex:isStudentOfthe person is a student of the entity described in the record
ex:hasRelatedEntityany other type of relationship
ex:hasSpousethe person is the husband or wife of the person described in the record
ex:hasChildthe person is the child of the person described in the record
ex:hasParentthe person is a parent of the person described in the record

Input Conventions

If a link to another CERL Thesaurus record in field 500 is input manually, the first heading form of the target record is used as name form in this field, unless the reference work consulted has a different name form.

If this field is used in a personal name or imprint name record, it is recommended to use 0 at the second code position in subfield $5. This is also recommended if this field is used in a corporate name record, which actually represents a person (e.g. a bishop of the Anglican church etc.)

Examples

  1. 212 #1$aChurch of England$bDiocese of London$bBishop$r1587-1604$rBancroft$cGB$5ESTC
    500 01$5z0$aBancroft$bRichard$3cnp00000001
  2. 200 #1$aOstrowski$bJoseph-Chrétien$cDE$5GyFmDB
    500 01$5z0$aOstrowski$bAntoni$8ger$nVater$3cnp00564784
  3. 200 #1$aTrygophorus$bEva$cDE$5GyFmDB
    500 01$5z0$aTrygophorus$bCaleb$8ger$nEhemann
  4. 210 #0$aSchipper$bJan Jacobsz$cNL$5NeHKB
    500 00$5z0$aSchipper$bJan Jacobsz$3cnp00065144

Internal Representation

{"data": {"related": [{
    "tmp": "Temporary data ($9)",
    "part": [
        {"entry": "Entry element ($a)"},
        {"firstname": "First name or subdivision ($b)"},
        {"nonsort": "Non-sorting part of name ($e)"},
        {"addition": "Addition to the name ($r)"}
    ],
    "typeOfRelationship": "Type of relationship ($0)",
    "typeOfEntity": "Type of entity",
    "source": ["source of information ($s)"],
    "start": year ($z),
    "end": year ($z),
    "note": [{
        "lang": "Language code ($8)",
        "text": "Text of note ($n)"
    }],
    "id": "Record identifier of related record ($3)",
    "prc": 1
}]}}

Change history

  • 17.07.2017: The first indicator will become obsolete, once the CT has been migrated into its new environment
  • 17.07.2017: Subfield $1 will no longer be supported, once the CT has been migrated to its new environment.
  • 17.07.2017: Subfield $6 will no longer be supported, once the CT has been migrated into its new environment
  • 17.07.2017: Subfield $5 will no longer be supported, once the CT has been moved into its new environment. During ingest any information on the type of relationship will automatically be converted to $0.
This website uses cookies to ensure you get the best experience from it.
 resources/cerl_thesaurus/editing/format/500.txt · Last modified: 2017/08/07 17:37 by jahnke

 

 

Recent changes RSS feed Valid XHTML 1.0 Driven by DokuWiki