...
It is recommended to specify names of persons/entities both in a text element and separately using URIs from authority files. If both current and historical place names are recorded, these should be documented in separate data elements or otherwise identified.
CARE: Knowledge gaps in the object's history should always be disclosed (e.g. by stating “not documented” or “not known to us” in the data elements “Person/entity”, “Date”, “Location”). Uncertainties or attributions that originate, for example, from the surviving collection entry documentation should be contextualized in a separate data element “Event description” (in LIDO: <lido:eventDescriptionSet>/<descriptiveNoteValue>). References to the location of collection items from colonial contexts often originate from historical records or documents. As the names and political affiliations of places have changed, it is often not possible to reconstruct which place it is today. In this case, the assignment of URIs from standard vocabularies should not imply any supposed accuracy. Instead, the historical name (in its literal form) should be published via a text data field (in LIDO: <lido:namePlaceSet>/<lido:appellationValue>). Under certain circumstances, places of origin should not be published at all, e. g. to protect artefacts from looting or plants from illegal collection.
...
Pleiades (for historical place names)
Examples
URI | Preferred name |
---|---|
http://vocab.getty.edu/tgn/7006464 | Prague |
https://sws.geonames.org/2928376/ | Eutritzsch |
https://d-nb.info/gnd/4005728-8 | Berlin |
https://sws.geonames.org/2855745/ | Paderborn |
https://d-nb.info/gnd/4007955-7 | Brandenburg |
http://www.wikidata.org/entity/Q142 | France |
https://pleiades.stoa.org/places/668331 | Palmyra |
http://www.wikidata.org/entity/Q20135 | Grand Duchy of Hesse |
https://d-nb.info/gnd/2015221-8 | Karl-Marx-Stadt |
Kloster Eberbach [eng.: Eberbach Abbey] | |
https://pleiades.stoa.org/places/216788 | Deultum |
Expression in LIDO (v1.0 und v1.1)
...
Comparison with relevant standards and database models
Standard | Element name | Text/URI | Repeatable | Obligation level | Comment |
---|---|---|---|---|---|
German Digital Library: Metadata requirements for data provision | (No match) | Not applicable | Not applicable | Not applicable | |
Text and/or URI | Yes | Conditionally mandatory if sub-elements exist. | |||
DFG Basic Data Record | Text and/or URI | Not specified | Recommended | ||
DFG Practical Guidelines on Digitisation: LIDO core metadata | Place where event took place <eventPlace> | Text and/or URI | Yes | Mandatory, if available | The DFG Practical Guidelines on Digitisation also recommend georeferencing using <place> / <gml>. |
Europeana Data Model (EDM) | Text | No | Not mandatory | ||
EODEM application profile | (No match) | Not applicable | Not applicable | Not mandatory | |
digiCULT | Herstellungsort/Fundort/Gebrauchsort etc. (eventPlace) [eng.: Place of production/discovery/use] | Text (controlled vocabulary) and URI | Yes | Recommended | |
museum-digital | Where? | Text (controlled vocabulary) and URI | Yes | Recommended |
ID data element
mds0012