Open main menu

Wikidata:WikiProject Historical Place

Historical names and boundaries of placesEdit

Boundaries of administrative entities change over time. Areas are united, split, relocated or terminated. The names of places vary over time and in different languages. They are related to the changes in administrative borders as well as dependent on context, dialect, regime etc.

Tasks
  • Record current best practises
  • Identify challenging questions
  • Create necessary missing properties
  • Create pilot imports

Change over timeEdit

Add the results of discussion here, discuss on the talk page or the Wikidata-wide project chat!

A sequence of items vs. changing properties of one itemEdit

How long does a place remain the same item, and when is a new item required?

Examples of a single persistent itemEdit

Examples of a changing itemEdit

Properties to to connect predecessors, successors, merges and splitsEdit

  • <Add here>

How to link entities hierarchically to historical administrative unitsEdit

Hierarchy over timeEdit

Historical location vs current locationEdit

located in present-day administrative territorial entity (P3842)

View and sort out existing classes for historical administrative division (Q19832712):

Useful classes:

QuestionsEdit

ExamplesEdit

  • In this case the change of the containing country of Oslo has been described with the property country (P17). Here is a related discussion.

<add more>

See alsoEdit

See also properties for #Historical_regions below or merge the topics.

TimeEdit

Properties for timeEdit

Qualifiers for timeEdit

Title ID Data type Description Examples Inverse
start timeP580Point in timestart time: when a statement starts being validJapan <capital> Tokyo
<start time> 1868
-
end timeP582Point in timeend time: when a statement stops being validJapan <capital> Heian-kyō
<end time> 1868
-
earliest dateP1319Point in timeearliest date at which an event could have happened. Use as qualifier for other date propertiesdate of birth of Jesus <earliest date> -
latest dateP1326Point in timelatest possible time that something could have occurred. Use as qualifier for other date propertiesdate of birth of Jesus <latest date> -
point in timeP585Point in timepoint in time: time and date something took place, existed or a statement was trueMalaysia Airlines Flight 17 <point in time> -
valid in periodP1264Itemtime period when a statement is validTübingen <valid in period> standard time-
  • Further fuzziness can be defined using the date property's precision.
  • Examples needed

ToponymsEdit

  • Names in different languages, contexts, administration, script systems
  • Change of names over time and in relation to boundary or administrative changes.
  • Which datatypes and properties are used.

QuestionsEdit

  1. Should place names be modeled as a property of a place or as separate items, either Q-items or L-items for lexical entries?
  2. Are place names in the scope of the Wikidata project. Current guidelines here: Wikidata:Lexicographical data/Notability#Proper Nouns

Properties to use for historical namesEdit

Title ID Data type Description Examples Inverse
official nameP1448Monolingual textofficial name: official name of the subject in its official language(s)Germany <official name> Bundesrepublik Deutschland-
native labelP1705Monolingual textnative label: label for item in its official or original languageMoscow <native label> Москва-

These are based on practices that are used currently in Wikidata.

Qualifiers for the spellingEdit

Title ID Data type Description Examples Inverse
transliterationP2440Stringtransliteration: conversion of text to alternate script (use as a qualifier for monolingual text statements; please use specific property if possible)Property talk:P2440-
ISO 9:1995P2183StringISO 9: the Latin transliteration of Cyrillic text (used as qualifier)Pyotr Ilyich Tchaikovsky <ISO 9:1995> Pëtr Ilʹič Čajkovskij-
Revised Hepburn romanizationP2125StringHepburn romanization: romanized Japanese following the Revised Hepburn romanization systemTokyo <Revised Hepburn romanization> Tōkyō-to-
Georgian national system of romanizationP2126StringGeorgian national system of romanization: no descriptionGeorgian <Georgian national system of romanization> kartuli ena-

Source statementEdit

Title ID Data type Description Examples Inverse
stated inP248Itemto be used in the references field to refer to the information document or database in which a claim is made; for qualifiers use P805Property talk:P248-
reference URLP854URLUniform Resource Locator: should be used for internet URLs as references. Use P4656 for interwiki linksJames Barry <reference URL> http://www.newscientist.com/article/mg19726462.000-histories-the-male-military-surgeon-who-wasnt.html-
quoteP1683Monolingual textcitation: quote supporting the statement claim (to be used in the "reference" field only)Curaçao-
stated asP1932Stringuse as qualifier to indicate how the value was given in the sourceBefore the embers <stated as> Léon Grandet-
  • There are several other generic source statements, such as date, page, chapter etc.

QuestionsEdit

ExampleEdit

Tartu (Q13972)

Properties for placesEdit

  • Select which features are in the scope of this project
  • List the key properties for each type of place feature and how change is expressed
  • Which WikiProjects should be connected with each feature?
  • What external expertise is available?
  • Identify missing properties. Note: Data type geographic shape is pending for the time being.

Generic, authority controlEdit

There are hundreds of identifiers marking geographic places. Here's a list of all Wikidata properties for authority control about places.

Please introduce significant identifiers here:

Title ID Data type Description Examples Inverse
GeoNames IDP1566External identifierGeoNames and Global Geosites: identifier in the GeoNames geographical databasePiton de la Fournaise <GeoNames ID> 935877-
OSM relation IDP402External identifierOpenStreetMap: identifier for a relation in OpenStreetMapBerlin <OSM relation ID> 62422-
Pleiades IDP1584External identifierPleiades: identifier for a place in Pleiades hosted at pleiades.stoa.orgGortyn <Pleiades ID> 589796-
Pleiades IDP1584External identifierPleiades: identifier for a place in Pleiades hosted at pleiades.stoa.orgGortyn <Pleiades ID> 589796-
Trismegistos Geo IDP1958External identifierTrismegistos: identifier of an ancient place on trismegistos.orgUlpia Traiana Sarmizegetusa <Trismegistos Geo ID> 30060-
TGN IDP1667External identifierThesaurus of Geographic Names: identifier in the Getty Thesaurus of Geographic NamesSiena <TGN ID> 7011179-

Place type matchingEdit

Also consider Pleiades place type (proposal). Link to wherever the work will be carried out, Mix'n'Match?

Administrative entitiesEdit

There is a Request for Comments about modelling Countries, subdivisions, and disputed territories

Which features are in the scope of this project

For example country, region, city, village, hamlet

Related WikiProjects


Historical regionsEdit

Title ID Data type Description Examples Inverse
has partP527Itemhas part and consist of: part of this subject; inverse property of "part of" (P361). See also "has parts of the class" (P2670).
using has part to link to present day administrative entities. It may be worth creating items for each point in time when the scope differs.
Occitania <has part> Occitaniapart of

Houses, buildings and monumentsEdit

Which features are in the scope of this project
Key properties for the feature
Missing properties
Related WikiProjects
Expertise, participants

Natural featuresEdit

Which features are in the scope of this project
Key properties for the feature
Missing properties
Related WikiProjects
Expertise, participants

Streets, roadsEdit

Which features are in the scope of this project
Key properties for the feature
Missing properties
Related WikiProjects
Expertise, participants

OtherEdit

PilotsEdit

There are several datasets that are ready to be imported or are already being imported to Wikidata. List them here to make referencing them easier. Note the source and the Wikidata destination. Make remarks about decisions that were needed or need to be solved for the import to happen.

You can also introduce a dataset and ask for community discussion about importing it.

Resources: Historical GazetteersEdit

participantsEdit

The participants listed below can be notified using the following template in discussions:

{{Ping project|Historical Place}}

NavigationEdit