Wikidata:Property proposal/HASC
Hierarchical administrative subdivision codes edit
Originally proposed at Wikidata:Property proposal/Place
| Description | codes to represent names of country subdivisions |
|---|---|
| Represents | Hierarchical Administrative Subdivision Code (Q3013341) |
| Data type | External identifier |
| Domain | administrative territorial entity (Q56061) |
| Example 1 | Bielefeld (Q2112) → DE.NW.BE |
| Example 2 | Coesfeld (Q6210) → DE.NW.CE |
| Example 3 | Emmendingen (Q8193) → DE.BW.EM |
| Source | [1] |
| External links | Use in sister projects: [ar] • [de] • [en] • [es] • [fr] • [he] • [it] • [ja] • [ko] • [nl] • [pl] • [pt] • [ru] • [sv] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt]. |
| Number of IDs in source | 41,000 |
| Expected completeness | eventually complete (Q21873974) |
| See also | Statoids ID (P3175) |
Motivation edit
en:Hierarchical administrative subdivision codes (HASC) are codes to represent names of country subdivisions, such as states, province, regions. It would be very cool to use this in wikidata. Stefan Kühn (talk) 15:55, 10 November 2018 (UTC)
Discussion edit
Comment These are not a recognized standard as far as I can see. How do they compare with ISO 3166-2? (for which we have ISO 3166-2 code (P300). ArthurPSmith (talk) 20:00, 12 November 2018 (UTC)
Answer HASC goes depper then ISO 3166-2. For example Alabama has "US-AL" in ISO 3166-2. For the Chilton County, Alabama there is nothing in ISO. HASC had this: "US.AL.CI". So you get an easy identifier for this county. If you look at Wikidata Q111266 for the identifier, there is nothing so easy like this. The identifiere there are all huge numbers or so. - An other positiv thing about HASC is the 2 letter design. For example ISO 3166-2:AT say "Steiermark"="AT-6". In HASC it is "AT.ST". Easy to use and easy to learn. -- Stefan Kühn (talk) 16:54, 15 November 2018 (UTC)
- Who uses those codes? ChristianKl ❪✉❫ 19:31, 14 November 2018 (UTC)
- Answer I don't know. I used HASC in this project c:Commons:Brück & Sohn for the sorting of all this postcards in counties. Today I use it for some other projects. - I found some other maybe-users: Link1, Link2, very interesting: Link3 (cite: "Due to shortcomings of related de-jure standards a hierarchical set of subdivision codes, called Hierarchical Administrative Subdivision Codes (HASC), has been devised, extending in many cases to secondary administrative divisions.") - Someone insert HASC in Openstreetmap (at the moment only for Tunisia). -- Stefan Kühn (talk) 17:15, 15 November 2018 (UTC)
Not done, no support. Regards, ZI Jony (Talk) 16:47, 8 April 2019 (UTC)
- Comment @ArthurPSmith, ChristianKl, ZI Jony, MisterSynergy, Trivialist: Back to live. Stefan has practical usage for this official systems of hierarchical naming. So it is for us a GLAM argument. User:Stefan Kühn, can you give us a sample use of the codes and how they improve your work please? Regards to all helpers, Conny (talk) 12:05, 30 December 2019 (UTC).
- Answer First I use this to sort my private collection of postcards (over 20.000). I think this is the best method of organization worldwide in the third level (Country, Region, Subregion). It is good to understand and easy to remember. When I start the project c:Commons:Brück & Sohn we also use HASC to sort all 30.000 postcard by regions. All other identifier work with numbers or postcodes and are not easy to remember. For example "DE.SN.DE" First "DE" is for the country Germany/Deutschland, "SN" is the region "Saxony" (equal to ISO 3166-2) and the last "DE" is 1 of 10 subregion of Saxony, is "Dresden" (see: en:Saxony#Administration). Mostly the subregion is generated by the 1 and 3 letter "D"r"E"sden --> DE. Because of the 2-letter-design, you can easy detect errors. Also you can add by your own more two letter for cities in the subregions or city parts. Unfortunately the creator of this HASC is dead. And not all regions are done (For example Canada-Manitoba, but this can be done later. Why we need this? Read this! -- sk (talk) 13:08, 30 December 2019 (UTC)
Support Conny (talk) 19:22, 2 January 2020 (UTC).
@ArthurPSmith, ChristianKl, MisterSynergy, Trivialist: can we accept the proposal? Regards, ZI Jony (Talk) 16:24, 4 April 2020 (UTC)
- @Conny: Sorry I didn't notice your comment earlier. You said "it is for us a GLAM argument" - who is "us" in this context? ArthurPSmith (talk) 18:47, 6 April 2020 (UTC)
- @ArthurPSmith: Wikipedians in Dresden, especially @Stefan Kühn: have some ongoing cooperations with f. e. persondata of museums and archives in the Dresden. The linked archive is an output of a cooperation, at this time 7 % of the 30.568 files are used in 9 Wikipedians and Wikidata. Stefan want as I understand use HASC to detect errors in the dataset and maybe also get in touch with constraint violations to maintain the information of the dataset. Regards, Conny (talk) 20:31, 6 April 2020 (UTC).
- @Conny, Stefan Kühn: Ok I made a couple of modifications to the proposal to bring it a little closer to being ready to create: (1) I changed the datatype to external-id. This is appropriate if these string values are single-valued and unique, that is they correspond to only one place and each place with a HASC has only one such string. Is this correct, and what you want? (2) Your examples should link to actual Wikidata items (and you had the traditional order in the template reversed) - I modified the first example, assuming that that Wikidata item is correct for that value of the id; I'd appreciate if you could verify that and fix the other two examples similarly. ArthurPSmith (talk) 20:53, 6 April 2020 (UTC)
- @ArthurPSmith: Thanks for your change. I fix the wikidata-item and add the other two examples. It is my first proposal at Wikidata. -- sk (talk) 21:04, 6 April 2020 (UTC)
