====== 215 Place Name (Heading) (O;R) ======

==== Field Definition and Scope ====
This field holds the name of a place in a standardised form used by a library or similar institution, a regional or international authority file or any other source that standardises geographic names.


==== Application of Content Designators ====

=== Indicators ===

**Indicator 1:** undefined (blank)

**Indicator 2: Specifies the type of input:**

  * **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 ===
\\
**$5 Institution to which the information in this field applies. (O;R)**\\ A code from the [[List of insitution and file codes used in heading fields]] indicates that this institution or authority file uses the name form in $a as a heading form or a preferred from. //For backwards compatibility an additional subfield $c holding either a country code or 'XX' is rendered with every subfield $5 by the system. This subfield $c should not be input manually, since the code in subfield $5 is sufficient to identify the institution responsible for the given heading//
\\
\\
**$a Entry element (M;NR)**\\
Name form as used as a heading or preferred form by the institution given in subfield $5.
\\
\\
**$e Non-Sorting part of name (O;NR)**\\
Any part of the entry element, which should be skipped if entry elements are sorted alphabetically.
\\
\\
**$r Addition other than names to entry element (O;R)**\\
Any additions to then name that are not considered part of the name (e.g. "Hansestadt")








==== Input Conventions ====
This field is repeatable to show standard forms used by different institutions. As there is no preferred form in a CERL Thesaurus record, no standard form has precedence over the other standard forms.

Although, it is technical possible to enter standard forms without an indication of the institution responsible for that form, this is not encouraged.



==== Mapping ===
For the Export to RDF, the following mapping is applied
|$a|rdaGr3:nameOfThePlace| |

  * rdaGr3 represents the namespace "http://rdvocab.info/ElementsGr3/"
  * The RDA ontologies are registerd with the open metadata registry ([[http://metadataregistry.org/schemaprop/show/id/1141.html]])

**Mapping Example**
<code>
<rdf:Description rdf:about="http://cttest.cerl.org/cnl00002390">
   <rdaGr3:nameOfThePlace>Turku</rdaGr3:nameOfThePlace>
   <rdaGr3:nameOfThePlace>Åbo</rdaGr3:nameOfThePlace>
</rdf:Description>
</code>

==== Examples ====

  - 215 #0$aChâlon-sur-Saône$5GYMG
  - 215 #1$aTurku$5GYMG \\ 215 #1$aÅbo$5SwSKB


==== Internal Representation ====
<code javascript>
{"data": {"heading": [{
    "part": [
        {"entry": "Entry element ($a)"},
        {"nonsort": "Non-sorting part of name ($e)"},
        {"addition": "Addition to the name ($r)"}
    ],
    "usedBy": ["Institution Code ($5)"],
    "prc": 1
}]}}
</code>

==== Change History ====
  * //18.07.2017//: Subfield $6 will no longer be supported, once the CT has been migrated into its new environment
  * //18.07.2017//: Subfield $7 removed from format description
  * //18.07.2017//: Subfield $c marked as deprecated