515 Related Place (O;R)

This field contains the name of the place where a printer or publisher has been working, a corporate body has been active or a person has been born, died or lived. It can also contain a reference to a place the place described in the current record is related to.

Indicator 1: undefined (blank)

Indicator 2: Specifies the type of input:

• 0 Field has been input or corrected by cataloguer and cannot be overwritten in automated updating processes
• 1 Field has been input by automated addition; review by cataloguer may be necessary

$a Entry Element (M;NR)
Subfield $a contains the part of the name used as the entry element in a heading.

$d Address (O;NR)
Address as printed in the book.

$e Printer device used in conection with address (O;R)
Any graphical sign which is related to a printer's address given in $d.
Any device, which a printer used throughout different places or different addresses is filed in field 516.

$n Cataloguer's note (O;R)
Forming a pair with the preceding $8 subfield. Any cataloguer's comment on this category

$r Part of name other than entry element (O;R)
Remainder of the name, if given in a separate subfield in the source record.

$z Chronological subdivision (O;NR)
Used in conjunction with $a Preferrred form of entry: yyyy-yyyy or yyyy- or -yyyy

$3 CERL Thesaurus record number (M;NR)
Record ID of the record to which the link points

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

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

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

for personal names, imprint names and corporate names records

for place records

• inst should be used only in place name records that hold 3 in 110 Coded Data Field: Type of Name used as Standard Form (M;NR) subfield $a.
• part can only be used in place name records that hold 0 in 110 Coded Data Field: Type of Name used as Standard Form (M;NR) subfield $a.

The places and addresses are given in chronological order, where possible.

When creating an RDF description, the following mapping is applied

• rdaGr2 represents the namespace “http://rdvocab.info/ElementsGr2/”
• Whenever a link to a place name record is available, the RDF triple will point to it as a resource.
• The RDA ontologies are registerd with the open metadata registry (http://metadataregistry.org/schemaprop/show/id/1141.html)

1. 515 #1$0actv$aLondon$z1650
2. 515 #1$0resd$aHaarlem$dBouwery Steghe (de)$z1631
   515 #1$0resd$aHaarlem$dNoorder School-steegh (de)$z1637-1648
3. 515 #1$0actv$aGroningen$z1654-1670
   515 #1$0resd$aGroningen$dHeere-straet (de)$eGroote orangien-croone (in de)$z1655

{"data": {"place": [{
    "tmp": "Temporary data ($9)",
    "part": [
        {"name": "Entry element ($a)"},
        {"address": "Address ($d)"},
        {"sign": "Sign ($e)"},
        {"addition": "Addition to the name ($r)"}
    ],
    "typeOfPlace": "Type of place ($0)",
    "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
}]}}

• 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: Added new subfield $0 to the format description
• 16.01.2020: Added codes for related places and adapted field definition