Wikidata:Property proposal/Tüik number

From Wikidata
Jump to navigation Jump to search

TÜİK ID

[edit]

Originally proposed at Wikidata:Property proposal/Place

   Not done
DescriptionIdentifier for populated places in Turkey, in the TÜİK database
Data typeString
Allowed values\d+
Example 1Bilecik Province (Q46763) → 11
Example 2Bayraklı (Q812591) → 2056
Example 3Çiçekli (Q8002268) → 176975
Sourcehttp://www.tuik.gov.tr/, xlsx dump
Planned useWikidatification of populated places in Turkey
See alsoYerelNet village ID (P2123), the same for villages
Single-value constraintyes

Motivation

[edit]

Turkish Statistical Institute (TÜİK) is the Turkish government agency responsible for producing official statistics on demographics data related to Turkey. It would be beneficial for Wikidata users to have an identifier pointing to populated places in Turkey, regarding population data. --Superyetkin (talk) 14:06, 1 May 2022 (UTC)[reply]

Discussion

[edit]
✓ Done --Superyetkin (talk) 12:43, 3 May 2022 (UTC)[reply]
There are no two different characteristics of settlements in Turkey. A place is either a village or a neighborhood. There is no village named "Kabasakal" (Q6653955) in Çukurova district. There is only a neighborhood called "Kabasakal". The Turkish Statistical Institute announces the population values of the "Kabasakal" neighborhood every year. Tuik ID-Wikidata ID pairings are made by checking one by one. As in the example on the right, one-to-one control is made over the excel list.--Sadrettin (talk) 17:44, 23 May 2022 (UTC)[reply]
The status of a place can change over time, and Wikidata keeps historical statistics and identifiers, and statistics are available from when it was. It's less of an issue if current status and identifier have "preferred" rank and start dates, and former status and identifier have end dates, but that isn't guaranteed to happen, and would only be possible if the identifiers were available at the same time as the status change. Queries would be easier with separate identifiers, and another reason to create separate properties is that if links become available that use these identifiers, they would probably require a different formatter URL (P1630) for each type. Q3604202 (talk) 23:37, 31 May 2022 (UTC)[reply]
Each settlement has only 1 attribute and 1 number. --Sadrettin (talk) 17:39, 25 May 2022 (UTC)[reply]
@Sadrettin: That's not the issue. The issue is that two (or up to five or six) Wikidata items will have the same number, if there is only the one property. That breaks the basic logic of external identifiers to identify things. ArthurPSmith (talk) 17:55, 26 May 2022 (UTC)[reply]
I am okay with the string data type. Thanks. --Superyetkin (talk) 15:08, 6 June 2022 (UTC)[reply]
User:ArthurPSmith I don't get it. At any point in time one Wikidata item matches one Tüik number. Over time things change like mergers and split up so multiple id's will be on one item and multiple items will have the same id, of course all qualified with start and end time. Isn't that how a lot of external identifiers work? What I just described also applies to for example CBS municipality code (P382). How is this different? Multichill (talk) 15:20, 6 June 2022 (UTC)[reply]
@Multichill: No, one number can correspond to up to 6 WIkidata items at the same time - see the example stated above by Q3604202 "For example 2056 in the example is the identifier for Bayraklı (Q812591), but also refers to Esendere (Q1367550), Kutuören (Q6448671) and Aydoğdu (Q4830384), depending on whether it is the district of Turkey (Q1147395), municipality (Q2460358), mahalle (Q17051044) or town municipality of Turkey (Q815324)/village in Turkey (Q1529096)" - ArthurPSmith (talk) 15:36, 6 June 2022 (UTC)[reply]
I'm okay 👍Like Jelican9 (talk) 17:08, 6 June 2022 (UTC)[reply]
String datatype is ok, this proposal can be marked as ready. --Tinker Bell 20:21, 6 June 2022 (UTC)[reply]
 Strong oppose Can someone explain why this should be a single property? It appears to be a set of identifiers, the spreadsheet even separates them into separate sheets. Combining them into a single property for the sake of it and using the string type because it's no longer representing an identifier does not seem like the right way to store the data. - Nikki (talk) 11:35, 18 June 2022 (UTC)[reply]