Wikidata:Property proposal/Authority control
Property proposal: | Generic | Authority control | Person | Organization |
Creative work | Place | Sports | Sister projects | |
Transportation | Natural science | Lexeme |
See alsoEdit
- Wikidata:Property proposal/Pending – properties which have been approved but which are on hold waiting for the appropriate datatype to be made available
- Wikidata:Properties for deletion – proposals for the deletion of properties
- Wikidata:External identifiers – statements to add when creating properties for external IDs
- Wikidata:Lexicographical data – information and discussion about lexicographic data on Wikidata
This page is for the proposal of new properties.
Before proposing a property
Creating the property
|
On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2022/05. |
EncyclopediaEdit
Millattashlar IDEdit
MotivationEdit
The Tatar encyclopedia "Millattashlar", opened in September 2009 on the MediaWiki engine, is a project about the life and work of Tatars in Russia and the world. Among the articles of the encyclopedia, one can find states located on the territory of modern Tatarstan, Tatars in the regions of Russia, etc. MasterRus21thCentury (talk) 18:13, 14 January 2022 (UTC)
DiscussionEdit
- Notified participants of WikiProject Russia — MasterRus21thCentury (talk) 18:13, 14 January 2022 (UTC)
- I suggest to use page IDs, as it is usually done for MediaWiki websites, e.g. http://www.millattashlar.ru/index.php?curid=136 for the last example. The first example is to be fixed. Besides these things, --Epìdosis 18:19, 14 January 2022 (UTC)
- Do you know why has the table of content at Wikidata:Property_proposal/Authority_control stopped working at exactly this property? Any problems with a template here? RShigapov (talk) 13:05, 19 January 2022 (UTC)
- Answer: Yes, there are problems, because Wikidata administrators and creators of properties are not in a hurry to do this. This is due to the fact that there are quite different points of view on the proposed properties in Wikidata, and discussions on some of them have not been closed since the beginning of 2020. Although, in theory, you can create additional thematic pages. MasterRus21thCentury (talk) 13:12, 19 January 2022 (UTC)
- Support, an important property for Russia.--Arbnos (talk) 23:37, 21 January 2022 (UTC)
- It is wikisite, which has no edits in the last month and is more or less supported by one person, http://www.millattashlar.ru/index.php/Служебная:Вклад/Камиль_Бакиров. Most of the articles are either low-quality, or, as http://www.millattashlar.ru/index.php/Графика, look like copyright violations from Tatar Encyclopaedia (Q2574338) (I cannot check it). @MasterRus21thCentury, RShigapov, Arbnos: can you explain why this website is good? Wikisaurus (talk) 21:37, 26 January 2022 (UTC)
- Good points! Indeed, the maintainer cites Tatar Encyclopaedia (Q2574338) very often, it seems it's his main source of data. I see the requirements of attribution and providing the hyperlink at http://www.ite.antat.ru/articles/index.shtml: "При использовании материалов сайта обязательно указывать ссылку "Институт Татарской энциклопедии и регионоведения АН РТ", а при размещении в интернете - также гиперссылку на сайт: www.ite.antat.ru". It would make more sense to create a separate property for Tatar Encyclopaedia (Q2574338) of the datatype external-ID with the formatter URL http://www.ite.antat.ru/articles/1$ instead of this property proposal. RShigapov (talk) 08:22, 27 January 2022 (UTC)
- That is creation of property is expedient in the given situation? MasterRus21thCentury (talk) 08:46, 27 January 2022 (UTC)
- No, the original source of data at http://www.ite.antat.ru/articles should be preferred, I think. RShigapov (talk) 09:36, 27 January 2022 (UTC)
- That is creation of property is expedient in the given situation? MasterRus21thCentury (talk) 08:46, 27 January 2022 (UTC)
- Good points! Indeed, the maintainer cites Tatar Encyclopaedia (Q2574338) very often, it seems it's his main source of data. I see the requirements of attribution and providing the hyperlink at http://www.ite.antat.ru/articles/index.shtml: "При использовании материалов сайта обязательно указывать ссылку "Институт Татарской энциклопедии и регионоведения АН РТ", а при размещении в интернете - также гиперссылку на сайт: www.ite.antat.ru". It would make more sense to create a separate property for Tatar Encyclopaedia (Q2574338) of the datatype external-ID with the formatter URL http://www.ite.antat.ru/articles/1$ instead of this property proposal. RShigapov (talk) 08:22, 27 January 2022 (UTC)
- Notified participants of WikiProject Authority control —MasterRus21thCentury (talk) 06:05, 14 April 2022 (UTC)
- The example Nizhnekamsk Hydroelectric Station (Q12133686) does not appears to fit within the proposed domain of human (Q5), organization (Q43229), or human settlement (Q486972). C933103 (talk) 16:31, 15 April 2022 (UTC)
- Great Russian Encyclopedia Online ID (P2924) - Would you like to look at an example of properties for universal encyclopedias? MasterRus21thCentury (talk) 16:32, 15 April 2022 (UTC)
Yarkipedia IDEdit
Description | идентификатор статьи в проекте "Яркипедия" (ru) – (Please translate this into English.) |
---|---|
Represents | Yarkipedia (Q110970882) |
Data type | External identifier |
Domain | human (Q5), occurrence (Q1190554), organization (Q43229) |
Example 1 | NPO Saturn (Q1961355) → 26/saturn |
Example 2 | Northern Railway (Q1946844) → 27/severnaya-zheleznaya-doroga |
Example 3 | Yaroslavl revolt (Q5671376) → 11/iyulskij-1918-g-myatezh-v-yaroslavle |
Example 4 | Anatoly Lisitsyn (Q840698) → 126/lisicyn-anatolij-ivanovich |
Source | https://yarwiki.ru |
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]. |
Planned use | for usage in stated in (P248) and for Template:Authority control (Q3907614) |
Number of IDs in source | unknown |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://yarwiki.ru/article/$1 |
Robot and gadget jobs | Yes, it would be great to have a separate mix'n'match catalog. |
See also | Penza Encyclopedia ID (P10036), Irkipedia ID (P10154) |
Wikidata project | Russia |
MotivationEdit
Yarkipedia is an online encyclopedia dedicated to the Yaroslavl region. The project was launched in 2016 on the occasion of the 80th anniversary of the formation of the region, and since then it has a significant number of collections on the history of the region from the time of Ancient Russia to the current 2022. Users of the site also have the right to suggest the editors of the online encyclopedia topics and articles that they would like to see.MasterRus21thCentury (talk) 18:52, 20 February 2022 (UTC)
DiscussionEdit
- Notified participants of WikiProject Russia —MasterRus21thCentury (talk) 18:56, 20 February 2022 (UTC)
- Notified participants of WikiProject Authority control —MasterRus21thCentury (talk) 05:59, 11 March 2022 (UTC)
- Support, an important property for Russia.--Arbnos (talk) 20:06, 23 April 2022 (UTC)
LibraryEdit
NLI topic idEdit
Description | National Library of Israel topic id |
---|---|
Represents | National Library of Israel (Q188915) |
Data type | External identifier |
Template parameter | need to be created in he.wiki |
Domain | human (Q5) and many more (structural class of chemical compounds (Q47154513), class of chemical substances by use (Q100434640) liberty (Q2979)...) |
Allowed values | [1-9]\d* |
Example 1 | Tracy Hickman (Q353137) → value 987007311677105171 |
Example 2 | predation (Q170430) → value 987007533805805171 |
Example 3 | Moses Shapira (Q1246291) → value 987007268051305171 |
Example 4 | academic freedom (Q414706) → value 987007292823905171 |
Source | https://www.nli.org.il/he |
Planned use | already have a list of 26,000 items. to be added using OpenRefine |
Formatter URL | https://www.nli.org.il/he/a-topic/$1 * https://www.nli.org.il/he/a-topic/$1 (Hebrew) * https://www.nli.org.il/en/a-topic/$1 (English) |
Wikidata project | Wikidata:WikiProject National Library of Israel |
MotivationEdit
National Library of Israel (Q188915) id's for topic pages. The first 26k items to be added using OpenRefine tool. The topic pages are pages that gathering all the items (media books etc.) about the topic in the National Library of Israel. Geagea (talk) 14:19, 2 February 2022 (UTC)
DiscussionEdit
Withdrawn per User talk:Epìdosis#Wikidata:Property proposal. Geagea (talk) 14:50, 10 February 2022 (UTC)
- After discussion with Epì - User talk:Epìdosis#Wikidata:Property proposal, I decided to bring the issue to community discussion. When I created this proposal I mentioned the NLI topic id as the extention of the link. for example https://www.nli.org.il/he/a-topic/$1. this $1 nuber is the same as National Library of Israel J9U ID (P8189). In a matter of a fact the correct id of NLI topic is the name. I believe that the web link is just for comfortability. The staff of the National worked on unique naming. The NLI topic have 3 labels Hebrew, English and Arabic. It may have only one of the languages or two or three of them. for example: Beit Guvrin (Q830798) have three names:
- Hebrew: https://www.nli.org.il/he/a-topic/987007547547605171
- English: https://www.nli.org.il/en/a-topic/987007547547605171
- Arabic: https://www.nli.org.il/ar/a-topic/987007547547605171
- But Paul Otlet (Q1868) have only English: https://www.nli.org.il/en/a-topic/987007281064705171.
- So we have three options:
- 1) creating new property (the needs some modifications)
- 2) using two values of National Library of Israel J9U ID (P8189), one of them with qualifier applies to part (P518) NLI topic (Q110943955)
- 3) use only one value of National Library of Israel J9U ID (P8189), specifying in the reference that the titles apply only to NLI topic (Q110943955) as it is now .
- I personally ok with options 1 or 2 as the two id's are not identical even though the web link contains the same number. I would appreciate your advice. Geagea (talk) 12:10, 18 February 2022 (UTC)
- I would personally support option 3. Notified participants of WikiProject Authority control. --Epìdosis 20:32, 18 February 2022 (UTC)
- Notified participants of WikiProject Data Quality. --Epìdosis 20:33, 18 February 2022 (UTC)
- Support —MasterRus21thCentury (talk) 20:34, 18 February 2022 (UTC)
- @MasterRus21thCentury: To which of the three solutions listed above by Geagea? Creating a new property, using the same ID as P8189, would be solution 1). Thanks, --Epìdosis 08:30, 19 February 2022 (UTC)
Notified participants of WikiProject Authority control, The actual question is what should be considered as id. only web id or not necessarily. In this case the real id is unique name in Hebrew. English and/or Arabic.
The web link contains the same id as National Library of Israel J9U ID (P8189) with different link format:
- P8189 link: http://uli.nli.org.il/F/?func=find-b&local_base=NLX10&find_code=UID&request=987007547547605171
- NLI topic link: https://www.nli.org.il/he/a-topic/987007547547605171
The question is which way is preferred to handle this:
A. to create new property.
B. to use the P8189 and create two entries like I have dne her.
C. to use only one enery just like it is now.
So in cases like this does Wikidata id.=web id. or might be differ web id. and other id. Your thoughts on the issue are welcome. Geagea (talk) 09:21, 28 February 2022 (UTC)
- I think using P8189 is generaly enough, and wil do the job. The only problem is places. Unlike LOC which has only one top tier item for and place, NLI has two if a place is both a geographical entity and an author. The will make a 110 item for a place as an author and a seperate 151 item for the place as a subject. DGtal (talk) 22:44, 9 May 2022 (UTC)
LawEdit
RegisterEdit
identifier in a register in GermanyEdit
Description | identifier in a register located in Germany |
---|---|
Data type | External identifier |
Domain | various items represented in various German registers |
Example 1 | BASF (Q9401) → 6000 |
Example 2 | National Research Data Infrastructure (Q61658497) → 703016 |
Example 3 | Air Berlin (Q156829) → 23373 |
Example 4 | ISC Mannheim (Q1654576) → 700478 |
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]. |
Planned use | First, adding them to German companies with qualifiers "type of register" and "XJustiz registration court ID" |
Number of IDs in source | more than 5 millions only for German companies, but only 20-30 thousands of them have items at Wikidata. So the plan is adding those 20-30 thousands values of "identifier in a register" with qualifiers "type of register" and "XJustiz registration court ID" |
Wikidata project | Wikidata:WikiProject_Authority_control |
MotivationEdit
The same motivation as for Wikidata:Property_proposal/type_of_register:
Germany has many registers. Every register has its own register type which is standardized at https://www.xrepository.de/details/urn:xoev-de:xjustiz:codeliste:gds.registerzeichen. To avoid creating many properties for various German registers and for items they represent, we could create just two properties "type of register in Germany" and "identifier in a German register". Then we could add IDs of German companies from German trade register (Handelsregister) using the property "identifier in a register" with qualifiers "type of register" and "XJustiz registration court ID". Notified participants of WikiProject Authority control RShigapov (talk) 09:22, 20 January 2022 (UTC)
DiscussionEdit
- Comment I'd rather continue as outlined at Wikidata_talk:WikiProject_Companies/Archive_2#Missing_identifier_properties, i.e. propose to create specific identifier properties or use one of the existing catalog code (P528) or described at URL (P973). --- Jura 09:38, 22 January 2022 (UTC)
- I've answered at Wikidata:Property_proposal/type_of_register. Let's discuss this issue for both properties there. RShigapov (talk) 10:58, 22 January 2022 (UTC)
- Support, Notified participants of WikiProject Germany —MasterRus21thCentury (talk) 06:25, 13 March 2022 (UTC)
register in GermanyEdit
Description | register located in Germany |
---|---|
Data type | Item |
Domain | items with instance of Registration court (Q2138576) (for modelling the German companies) and possibly other classes for other registers |
Example 1 | BASF (Q9401) → Local Court Ludwigshafen (Q480859) |
Example 2 | National Research Data Infrastructure (Q61658497) → Local Court Mannheim (Q480871) |
Example 3 | Air Berlin (Q156829) → Local Court Charlottenburg (Q480608) |
Example 4 | ISC Mannheim (Q1654576) → Local Court Mannheim (Q480871) |
Planned use | First, adding them as qualifiers to German companies together with the properties "identifier in a register in Germany" and "type of a register in Germany" |
Wikidata project | Wikidata:WikiProject_Authority_control |
MotivationEdit
This property should be used together with Wikidata:Property_proposal/type_of_register as qualifiers to a statement with Wikidata:Property proposal/identifier in a register. I've described examples with the same identifiers (and different registers and types of registers) in the discussion at Wikidata:Property_proposal/type_of_register:
- Maas Beteiligungsgesellschaft mbH is registered at "register in Germany" Local Court Hamburg (Q480732) with the "type of a register in Germany" Section B of the Commercial Register (Q110609503) and "identifier in a register in Germany" 47394.
- MIA.Ticket & Merch OHG is registered at Local Court Charlottenburg (Q480608) with Section A of the Commercial Register (Q110609501) and 47394.
- Fanfarenzug Tilleda e.V. is registered at Local Court Stendal (Q15783176) with register of associations (Q110619518) and 47394
As mentioned in the discussion at Wikidata:Property_proposal/type_of_register, these properties are not limited to registers related to organizations. See all types of registers at https://www.xrepository.de/api/xrepository/urn:xoev-de:xjustiz:codeliste:gds.registerzeichen_3.1/download/GDS.Registerzeichen_3.1.md. RShigapov (talk)
DiscussionEdit
- Support, Notified participants of WikiProject Germany —MasterRus21thCentury (talk) 06:24, 13 March 2022 (UTC)
- Support, an important property for Germany.--Arbnos (talk) 20:20, 23 April 2022 (UTC)
Authority controlEdit
- See also wikidata:property proposal/Pending for approved items awaiting the deployment of currently unavailable datatypes
- Already approved properties: list
FactGrid property IDEdit
Description | identifier for a property in FactGrid |
---|---|
Represents | FactGrid (Q90405608) |
Data type | External identifier |
Domain | item |
Example 1 | instance of (P31) → P2 |
Example 2 | VD 18 ID (P6135) → P370 |
Example 3 | sex or gender (P21) → P154 |
Source | https://database.factgrid.de/wiki/Main_Page |
Planned use | Syncing through collaboration |
Formatter URL | https://database.factgrid.de/wiki/Property:$1 |
MotivationEdit
See Wikidata:Property proposal/FactGrid item ID#Motivation --Adam Harangozó (talk) 14:23, 13 April 2020 (UTC)
DiscussionEdit
- Comment I believe there is a plan to allow wikibases to directly query Wikidata properties in the near future, not quite sure how this relates, have you looked into this? ArthurPSmith (talk) 18:20, 13 April 2020 (UTC)
- Not yet but I will now, thank you! Adam Harangozó (talk) 14:24, 14 April 2020 (UTC)
- It came up in the recent Wikidata office hours on telegram, I'm not sure it's been documented elsewhere. Here's the relevant quote that I caught:
"We started working on Federated Properties: this MVP will make it possible to configure your new Wikibase to remotely access Wikidata’s properties to make local statements, instead of creating your own properties from scratch. Any updates the community makes to Wikidata properties will be reflected automatically in Wikibases with this feature enabled! As an MVP, this is a minimal version of what will eventually be a full-fledged feature We will use it to learn as much as we can about federation between wikibases, and between wikibases and Wikidata!"
- ArthurPSmith (talk) 18:23, 14 April 2020 (UTC)
- @Adam Harangozó:So is there still a need for this property, or should this discussion be closed? --Kristbaum (talk) 23:27, 22 February 2021 (UTC)
- @Kristbaum: I believe it's still needed as FactGrid is already using it's own properties and ontology different from Wikidata's. --Adam Harangozó (talk) 20:00, 16 March 2021 (UTC)
- Support After some thinking, I do see the value of this proposal. --Emu (talk) 10:32, 29 March 2021 (UTC)
- Oppose store it in FactGrid or use exact-match. --- Jura 08:08, 2 April 2021 (UTC)
- Support since we already have the Item Id, might as well have the property id Germartin1 (talk) 22:10, 22 December 2021 (UTC)
- Comment Interconnecting Wikibase instances is obviously an important topic. Property federation may resolve this for connecting smaller Wikibases to Wikidata (though a month ago it was still alpha: you could have either Wikidata props or your own, but not both). But this proposal concerns the other direction... I think Wikidata must know that the link concerns another Wikibase, eg to be able to construct federated SPARQL queries (so @Jura1:'s proposal to use the generic "exactMatch" is not good enough). @Adam Harangozó: I think we need two generic props for this (and therefore to refactor "FactGrid item id"):
- "Corresponding Wikibase item" with qualifier "of" specifying the particular Wikibase
- "Corresponding Wikibase property" with qualifier "of" specifying the particular Wikibase --Vladimir Alexiev (talk) 15:32, 1 January 2022 (UTC)
Ethereum token addressEdit
Description | unique address for a token on the Ethereum blockchain |
---|---|
Data type | External identifier |
Example 1 | Tether (Q47528658) → 0xdac17f958d2ee523a2206206994597c13d831ec7 |
Example 2 | SHIBA INU (Q106853490) →0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce |
Example 3 | Basic Attention Token (Q53039605)→0x0d8775f648430679a709e98d2b0cb6250d2887ef |
Example 4 | Maker (Q57305725) → 0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2 |
Number of IDs in source | 422,950+ |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://etherscan.io/token/$1 |
See also | Wikidata:Property proposal/cryptocurrency address |
MotivationEdit
This external identifier can be used to represent any token on the Ethereum (Q16783523) blockchain. Lewis Hulbert (talk) 09:26, 22 June 2021 (UTC)
DiscussionEdit
- See Wikidata:Property proposal/cryptocurrency address--GZWDer (talk) 10:25, 22 June 2021 (UTC)
- Thanks, added that to the see also in the template. However, the responses to that proposal aren't all relevant to this proposal. This is the address for a token rather than an individual or organisation's address to receive payment, the name of the token can be verified through multiple blockchain explorers which makes the abuse potential much lower than an unverifiable payment address. Lewis Hulbert (talk) 10:43, 22 June 2021 (UTC)
- Comment I agree the possibility of abuse is much smaller here. There may be some motivation for somebody to enter the wrong token to direct people to the wrong crypto-asset potentially and and then try to sell them the wrong asset? But that seems like a very remote possibility to what we had before, actual accounts where people could send money. Another question: does this also allow linking to NFT and auctions on Foundation? Can we for example use this to link to Everydays: the First 5000 Days (Q105947532) or are these different tokens? We should, as long as they are based on Etherium, correct? --Hannes Röst (talk) 15:45, 23 June 2021 (UTC)
- For example the 0x3b3ee1931dc30c1957379fac9aba94d1c48a5405?a=41258 token is linked to this transaction which was the result of this this auction on Foundation for the patent disclosure forms of Crispr-Cas9. So we can say that 0x3b3ee1931dc30c1957379fac9aba94d1c48a5405?a=41258 represents the asset (in this case the patent forms)? But it seems that in addition to the token which just represents Foundation, there is also an ID (41258) associated with the asset, should we also represent this and how? --Hannes Röst (talk) 15:53, 23 June 2021 (UTC)
- Support Germartin1 (talk) 14:49, 30 April 2022 (UTC)
BelTA dossier IDEdit
MotivationEdit
BelTA is the state news agency of Belarus. By analogy with its Russian counterparts TASS and RIA Novosti, the site has a "Dossier" section, which contains background information about Belarusian personalities, individual structures, as well as organizations and events.MasterRus21thCentury (talk) 19:50, 11 February 2022 (UTC)
DiscussionEdit
- Notified participants of WikiProject Authority control —MasterRus21thCentury (talk) 20:13, 11 February 2022 (UTC)
- Support --Хомелка (talk) 09:24, 17 February 2022 (UTC)
- Support, an important property for Belarus.--Arbnos (talk) 20:26, 23 April 2022 (UTC)
HiSCoD idEdit
Description | identifier for a riot or other event in the Historical Social Conflict Database |
---|---|
Represents | revolt (Q6107280) |
Data type | External identifier |
Example 1 | émeute à Veckring le 16 février 1746(Q111395986) ==> HISCOD_JN_7476 ==> JN_7476 |
Example 2 | émeute à Warcq le 14 octobre 1781(Q111395995) ==> HISCOD_JN_7768 ==> JN_7768 |
Example 3 | émeute à Caussade le 14 septembre 1761(Q111396004) ==> HISCOD_JN_3561 ==> JN_3561 |
Example 4 | émeute à Cahors le 13 juillet 1780(Q111396011) ==> HISCOD_JN_1804 ==> JN_1804 |
Example 5 | émeute de 1812(Q3588236) → EMPH_0855 |
Planned use | Préparation d'une future importation de la base de données HiSCoD |
Formatter URL | https://pdnprod.unicaen.fr/hiscod/ead.html?id=HISCOD&c=HISCOD_$1 |
Wikidata project | WikiProject France (Q10816832) |
MotivationEdit
Préparation d'une future importation de la base de données HiSCoD : bdd sur des révoltes dans l'histoire française (paysans, chouans, etc).
. Bouzinac 💬●✒️●💛 10:27, 16 February 2022 (UTC)
DiscussionEdit
Notified participants of WikiProject France
- @Bouzinac: Hi - your examples, like 'HISCOD_JN_7476' should be wikidata items associated with that identifier, the identifier is then the value of the property for that item. Identifiers identify items. ArthurPSmith (talk) 18:52, 16 February 2022 (UTC)
- Sure, but when there is no items, how to handle that pb Bouzinac 💬●✒️●💛 20:44, 16 February 2022 (UTC)Try it!
SELECT ?revolte ?revolteLabel ?date WHERE {SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } ?revolte (wdt:P31/(wdt:P279*)) wd:Q49773. ?revolte wdt:P585|wdt:P580 ?date. filter (year(?date) in(1788,1789) ).}
- I would be in favor of this proposal if @Bouzinac: can fix the proposal and add Wikidata items as suggested by ArthurPSmith. --Hannes Röst (talk) 15:38, 28 March 2022 (UTC)
- @Bouzinac, Hannes Röst: Thanks for the further detail here. Are you sure there aren't any previously existing Wikidata items that would be covered? These seem like events that should have at least some of them covered in Wikipedias. I've added an English description and created a formatter URL. I trimmed off the HISCOD_JN_ prefix as that seems to be common, but perhaps not? I notice that on the pages themselves the ID listed doesn't have the "HISCOD_" prefix, for example just showing "JN_7476". ArthurPSmith (talk) 17:41, 28 March 2022 (UTC)
- I agree it would be great if there were some unrests for which we already have items. --Hannes Röst (talk) 18:13, 28 March 2022 (UTC)
- Hello, please note the Hiscod unrest are very modest for most of them. Just found out that émeute de 1812(Q3588236) which could have been related to https://www.unicaen.fr/hiscod/ead.html?id=HISCOD&c=HISCOD_EMPH_0855&qid=sdx_q17 just saying Bouzinac 💬●✒️●💛 18:20, 28 March 2022 (UTC)
- I agree it would be great if there were some unrests for which we already have items. --Hannes Röst (talk) 18:13, 28 March 2022 (UTC)
- Support Looks good to me if you guys are happy with it! ArthurPSmith (talk) 17:56, 29 March 2022 (UTC)
Bhshakosha pp.Edit
Description | identifier for page number in the digitized version of the Purnnachandra Ordia Bhashakosha hosted by the Digital Dictionaries of South Asia |
---|---|
Represents | Pūrṇṇachandra Orḍiā bhāshākosha (Q106803982) |
Data type | URL |
Domain | Odia (Q33810) |
Allowed values | [0-9] |
Example 1 | ନହକା (L648210) → 4173 |
Example 2 | ପତଳା (L648211) → 4551 |
Example 3 | ମୋଟା (L648212) → 6724 |
Example 4 | ଗୋରା (L648213) → 2332 |
Source | https://dsal.uchicago.edu/dictionaries/praharaj/ |
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]. |
Formatter URL | https://dsal.uchicago.edu/cgi-bin/app/praharaj_query.py?page=/$1 |
MotivationEdit
(Purnnachandra Ordia Bhashakosha is a 1931-1941 lexicon and arguably the oldest and most comprehensive lexicographic work in the Odia language. Two civil society organizations—Srujanika which originally collected the fragile volumes, scanned and digitized it, and the University of Chicago under the Library of Congress-supported DSAL project—have created a stable version for lookup. While the lexicon helped in the past to expand the Odia Wiktionary, it is now helpful for the creation of lexemes and citations. The examples above do contain the page number but a dedicated property would be helpful for a clickable URL as a citation.) Psubhashish (talk) 11:34, 14 March 2022 (UTC)
DiscussionEdit
- Support (as proposer) Psubhashish (talk) 11:34, 14 March 2022 (UTC)
- Comment You've selected URL datatype, which is probably appropriate as this is an identifier for a page, not for a particular lexeme, right? ArthurPSmith (talk) 18:20, 14 March 2022 (UTC)
- @ArthurPSmith: so, the URL is for a page in the original printed version of the book which DSAL has retained. It also makes sense from a lexicographical standpoint as one can see a few other lemmas that are related to the searched one. Is that an issue though? --Psubhashish (talk) 13:52, 17 March 2022 (UTC)
- Weak oppose on account of such a link not being specific to a particular lexeme (the issue Arthur described). Mahir256 (talk) 02:28, 21 March 2022 (UTC)
National Historical Museums of Sweden object IDEdit
Description | authority identification for an object in the collections of the National Historical Museums of Sweden |
---|---|
Data type | External identifier |
Allowed values | [0-9A-Z]{8}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{12} |
Example 1 | Streiff (Q10681657) → https://samlingar.shm.se/object/A4B754D2-5CB6-4FA1-997A-970250E32044 |
Example 2 | Mosjömadonnan (Q10589526) → https://samlingar.shm.se/object/7C505995-EBF5-4106-BBEE-17F52BB3EA83 |
Example 3 | Reliquary of St. Elizabeth (Q26253636) → https://samlingar.shm.se/object/8BA2743C-5065-438B-9FAA-D854606DB716 |
Source | https://samlingar.shm.se |
Planned use | Matching and creating items in the collection that are depicted on Wikimedia Commons |
Number of IDs in source | 1 300 000 |
Expected completeness | no label (Q21873886 (always incomplete)) |
Formatter URL | https://samlingar.shm.se/object/$1 |
See also | Nationalmuseum Sweden artwork ID (P2539) |
Single-value constraint | yes |
Distinct-values constraint | yes |
MotivationEdit
Needed to be able to matching and creating items on Wikidata that are objects in the collection of NHM and that are depicted in images on Wikimedia Commons, for example. / LinneaKarlberg (talk) 12:58, 7 April 2022 (UTC)
DiscussionEdit
- Support Azad Karimi (talk) 13:56, 7 April 2022 (UTC)
- Support LinneaKarlberg (talk) 13:05, 7 April 2022 (UTC)
- Support Eva L Vedin (talk) 13:08, 7 April 2022 (UTC)
- Support Elinor Rajka (talk) 19:13, 7 April 2022 (UTC)
- Support Azad Karimi (talk) 13:56, 7 April 2022 (UTC)
- Comment @LinneaKarlberg:, @Eva L Vedin:, @Elinor Rajka:, @Azad Karimi: coordinating support votes with ones colleagues is not helpful, the property proposal process is in place for a reason. Abbe98 (talk) 22:34, 7 April 2022 (UTC)
- Sorry, we did not know. LinneaKarlberg (talk) 07:19, 8 April 2022 (UTC)
- Comment Considering that National Historical Museums of Sweden agent ID (P9495) exists and that other properties from SHM are likely to be proposed in the future(places, events, heritage sites, ect) maybe there should only be one property? As far as I'm aware the UUIDs are unique across the various types and even if that wouldn't be the case one could include the type prefix in the id. Abbe98 (talk) 22:40, 7 April 2022 (UTC)
- @Abbe98: Sure, that would probably work. Do you have an example of another external identifier that includes several different types so I can check how it works? Is it possible then to change the name and details of P9495? LinneaKarlberg (talk) 07:22, 8 April 2022 (UTC)
- Europeana entity (P7704) would be one example. I would imagine migrating/generalizing National Historical Museums of Sweden agent ID (P9495) by: 1. updating the formatter URL 2. adding the agent prefix to existing values 3. updating the label/description of the property Abbe98 (talk) 10:08, 8 April 2022 (UTC)
- @Abbe98: Sure, that would probably work. Do you have an example of another external identifier that includes several different types so I can check how it works? Is it possible then to change the name and details of P9495? LinneaKarlberg (talk) 07:22, 8 April 2022 (UTC)
- Oppose Per the discussion above, I would suggest generalizing National Historical Museums of Sweden agent ID (P9495) rather than creating a new property for each type. I cave created a section on the discussion page. Abbe98 (talk) 10:20, 8 April 2022 (UTC)
- Hello Abbe98 , It would then be necessary to differentiate "agents" from "object". How would you like to do? (incorporate it into the identifier as a general property? or use an external URL formatter?) We can also consider that each property will be dedicated to the type (less errors with dedicated constraints). It would be necessary to recontact those who have already voted, as well as the voters of the other property, to find out if your idea appeals to them, but with more information. I don't see a URL leading directly to the correct page without using the type (with only the UUID). Example:
type:UUID
. Cordially. —Eihel (talk) 03:47, 13 April 2022 (UTC)- Hi! I would imagine we would use one of the seven possible prefixes like agent/<UUID> and object/<UUID>. We could also use a generic resolver but there isn't an official one so I think such a solution is less optimal. Abbe98 (talk) 06:48, 13 April 2022 (UTC)
- @Abbe98: @Eihel: @LinneaKarlberg: We just had a discussion about this with the Wikidata team at the National Historical Museums of Sweden. Our conclusion is that this property should not be created, and Abbe98's solution (using prefixes) is better. This will include us (WMSE is supporting the museum in their Wikidata work) generalizing National Historical Museums of Sweden agent ID (P9495) and removing
/person/
from the formatter URL and then adding the person prefix to all the existing uses of the property. --Alicia Fagerving (WMSE) (talk) 12:10, 21 April 2022 (UTC)- @Alicia Fagerving (WMSE) I have pinged all the people who voted on National Historical Museums of Sweden agent ID (P9495). I think we should leave it over the weekend at least but then if there are no one oposing this I can migrate it early next week. Abbe98 (talk) 12:32, 21 April 2022 (UTC)
- We at NHM are all on board with this approach instead of several Properties. LinneaKarlberg (talk) 08:09, 29 April 2022 (UTC)
- Sounds like an excellent idea. Many thanks Abbe98 . /André Costa (WMSE) (talk) 08:51, 24 May 2022 (UTC)
- We at NHM are all on board with this approach instead of several Properties. LinneaKarlberg (talk) 08:09, 29 April 2022 (UTC)
- @Alicia Fagerving (WMSE) I have pinged all the people who voted on National Historical Museums of Sweden agent ID (P9495). I think we should leave it over the weekend at least but then if there are no one oposing this I can migrate it early next week. Abbe98 (talk) 12:32, 21 April 2022 (UTC)
- @Abbe98: @Eihel: @LinneaKarlberg: We just had a discussion about this with the Wikidata team at the National Historical Museums of Sweden. Our conclusion is that this property should not be created, and Abbe98's solution (using prefixes) is better. This will include us (WMSE is supporting the museum in their Wikidata work) generalizing National Historical Museums of Sweden agent ID (P9495) and removing
- Hi! I would imagine we would use one of the seven possible prefixes like agent/<UUID> and object/<UUID>. We could also use a generic resolver but there isn't an official one so I think such a solution is less optimal. Abbe98 (talk) 06:48, 13 April 2022 (UTC)
- Hello Abbe98 , It would then be necessary to differentiate "agents" from "object". How would you like to do? (incorporate it into the identifier as a general property? or use an external URL formatter?) We can also consider that each property will be dedicated to the type (less errors with dedicated constraints). It would be necessary to recontact those who have already voted, as well as the voters of the other property, to find out if your idea appeals to them, but with more information. I don't see a URL leading directly to the correct page without using the type (with only the UUID). Example:
techradar review IDEdit
Description | techradar review ID for a product |
---|---|
Data type | External identifier |
Example 1 | IPhone 11 (Q67214165) → iphone-11-review |
Example 2 | DJI Pocket 2 (Q110996843)→ dji-pocket-2 |
Example 3 | MISSING |
MotivationEdit
(Add your motivation for this property here.) Germartin1 (talk) 13:27, 17 April 2022 (UTC)
DiscussionEdit
- Comment Hmm, do we have any other id's like this which are just links to reviews of the item? This seems a little dubious to me. What's wrong with described by source (P1343) for this sort of link? ArthurPSmith (talk) 15:36, 18 April 2022 (UTC)
- Yes for example DxOMark ID (P5906) Germartin1 (talk) 15:06, 30 April 2022 (UTC)
Databank Beschermheiligen anno 1959 IDEdit
Description | Database of patron saints in the Netherlands and Flanders, listing the different saints, the towns where they are venerated, and the reasons for which they are invoked. The database is based on a survey conducted in 1959 by the Meertens Institute. The Wikidata property would consist in the unique ID of the saint as used by the database. |
---|---|
Data type | String |
Domain | property |
Allowed values | [0-9]{0,2} |
Allowed units | human (Q5) narrative entity (Q21070598) group of humans (Q16334295) title of Virgin Mary (Q1509831) Christian holy day (Q60075825) |
Example 1 | Saint Gerlach (Q2513383) → 45 |
Example 2 | Martyrs of Gorkum (Q1909286) → 90 |
Example 3 | Holy Wounds (Q3390934) → 154 |
Example 4 | Our Lady of Sorrows (Q1196075) → 80 |
Source | https://www.meertens.knaw.nl/beschermheiligen/ |
Planned use | To be added as a property for the various saints in question. Especially for local saints, the information provided can be a good addition to what is mentioned in more international sources. |
Number of IDs in source | 207 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://www.meertens.knaw.nl/beschermheiligen/heilige/$1 |
Robot and gadget jobs | No major jobs expected. Adding can be done manually. |
MotivatieEdit
This is a complete database, based on a survey conducted in 1959. It provides important information on where these (often fairly local) saints were venerated and what problems they were invoked for. As far as I know, this is a pretty unique source. Given that the saints all have a unique number and that the database is hosted by the Meertens Institute (a sub-section of the w:en:Dutch Royal Netherlands Academy of Arts and Sciences, the resource can be expected to be stable. Wikibelgiaan (talk) 16:03, 22 April 2022 (UTC)
DiscussionEdit
National Archives of Sweden persistent identifierEdit
Description | Persistent identifier for objects in the National Archives of Sweden main archival database. |
---|---|
Data type | External identifier |
Allowed values | Base62-encoded UUID |
Example 1 | No 2. Elbing. (Q111517198) → eYHMeAFOm4sNVmxKK3M5L2 |
Example 2 | No 3. Elbing (Q111517379) → 0zDW3BS0Gw9Haap2yUVspE |
Example 3 | No 4. Danzigk wir es Eltere und newer werck (Q111519390) → zmQwWNi2ag9DQGJxnSVmD0 |
Formatter URL | https://sok.riksarkivet.se/arkiv/$1 |
See also | Swedish National Archive Reference Code (P5324) |
Single-value constraint | yes |
Distinct-values constraint | yes |
MotivationEdit
Wikidata-objekt med denna egenskapen kan också ha Nationell Arkivdatabas Referenskod (P5324), men den persistenta identifieraren är enklare att använda för att skapa webbsides-URLer och länkad data-URIer. Nils Weinander (Riksarkivet Sverige) (talk) 13:28, 28 April 2022 (UTC)
DiscussionEdit
- Comment Hi - could you fix your examples to look more like other property proposals (should look like: item → id) ? Also it would be useful to have formatter URL and some of the other template parameters filled out if possible. ArthurPSmith (talk) 14:21, 29 April 2022 (UTC)
- Thanks for the feedback! This is my first property proposal so I am very unsure of how to do things. I have reformatted the examples, added URL format and a see also reference. Nils Weinander (Riksarkivet Sverige) (talk) 08:22, 2 May 2022 (UTC)
- Support Ok, looks good to me now! ArthurPSmith (talk) 15:48, 9 May 2022 (UTC)
- Support Jneubert (talk) 05:53, 10 May 2022 (UTC)
- Comment are the above examples also the canonical URIs? Considering that the RA has quite a lot of identifiers, could there be a less generic name/description? "primary database" doesn't say much to the average user. Abbe98 (talk) 21:18, 11 May 2022 (UTC)
TÜİK IDEdit
Description | Identifier for populated places in Turkey, in the TÜİK database |
---|---|
Data type | External identifier |
Allowed values | \d+ |
Example 1 | Bilecik Province (Q46763) → 11 |
Example 2 | Bayraklı (Q812591) → 2056 |
Example 3 | Çiçekli (Q8002268) → 176975 |
Source | http://www.tuik.gov.tr/, xlsx dump |
Planned use | Wikidatification of populated places in Turkey |
See also | YerelNet village ID (P2123), the same for villages |
Single-value constraint | yes |
MotivationEdit
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)
DiscussionEdit
- @Superyetkin: this request is incomplete. Please fill out the full template and add examples. Multichill (talk) 15:31, 1 May 2022 (UTC)
- Examples are available in the source file. Thanks. --Superyetkin (talk) 15:59, 1 May 2022 (UTC)
- @Superyetkin: If you don't bother to fill out the template, we won't bother creating the property and just close it as incomplete. Please put in some effort. Multichill (talk) 16:01, 1 May 2022 (UTC)
- Examples are available in the source file. Thanks. --Superyetkin (talk) 15:59, 1 May 2022 (UTC)
- Oppose in the absence of examples for those of us who are not tr-N. Mahir256 (talk) 19:31, 1 May 2022 (UTC)
- @Superyetkin: You should provide real examples. Examples must link to any Wikidata subject (in this case, items). The xlsx you provide doesn't have links to Wikidata items, and it is written in Turkish, a lot of us are unable to understand that language in order to vote. --Tinker Bell ★ ♥ 05:05, 2 May 2022 (UTC)
- Done --Superyetkin (talk) 12:43, 3 May 2022 (UTC)
- Support --Tinker Bell ★ ♥ 08:15, 4 May 2022 (UTC)
- Oppose this proposal - it would require five separate identifiers, as they are only unique within each type of administrative unit. 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) with that identifier (the other type is province of Turkey (Q48336), but the numbers don't reach 2056). Also as town municipality of Turkey (Q815324) is a type of municipality (Q2460358), some places have more than one, for example Esendere (Q1367550) has 2056 as a municipality (Q2460358), and 15377 as a town municipality of Turkey (Q815324)/village in Turkey (Q1529096) (and it looks like the districts of a metropolitan municipality in Turkey (Q2716259) have both of these in addition to one for the district) If approved, there is also the issue of different statistics for "ilçe" and "ilçe merkezi" - we currently have combined items for many of these. Q3604202 (talk) 21:31, 4 May 2022 (UTC)
- Support There are 18217 villages, 32131 neighborhoods, 1366 municipalities, 981 districts in Turkey, and the en:Turkish Statistical Institute (TUIK) announces the population data for these settlements on 1 February every year. It is very difficult to manually enter the population value of more than 50 thousand settlements into wikidata every year and repeat it every year. If we match the TUIK ID number with the Wikidata item number, a bot can easily import the population data from an excel list into wikidata. --Sadrettin (talk) 16:24, 8 May 2022 (UTC)
- There would have to be a way to distinguish between different units with the same ID - for example searching for the instance of mahalle (Q17051044) with value "2" would probably find Q6653955, when it refers to Q97229878 for that unit type. If every item has the correct P31, an item could be updated from village in Turkey (Q1529096) to mahalle (Q17051044) without updating the ID (perhaps because it isn't known yet) and population would be added to the wrong item. Q3604202 (talk) 12:02, 21 May 2022 (UTC)
- 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)
- Support The concerns are irrelevant. It'll be beneficial for tr.wikipedia. There are many villages, neighborhoods and municipalities in Turkey. Therefore if we don't use it, we'll be exposed to a huge workload which discourage people to update these articles.--Sabri76 (talk) 21:35, 8 May 2022 (UTC)
- Support Vikipolimer (talk) 18:52, 18 May 2022 (UTC)
- Support I think it will be useful for en.wikipedia ×Elvorixtalk 17:08, 20 May 2022 (UTC)
- Comment @Sabri76: Can you explain why "the concerns are irrelevant"? It seems to me that Q3604202's comment above clearly shows that this as proposed is not an external ID, since the same identifier number can refer to two or more different entities. Separate properties should be proposed for each administrative level. Since "neighborhoods" are the most numerous according to Sadrettin's statistics, we could start with that, and make this proposal "Tüik number for a neighborhood" for example. ArthurPSmith (talk) 16:18, 23 May 2022 (UTC)
- Support --Jelican9 (talk) 06:43, 24 May 2022 (UTC)
- Support per reason -- Maurice Flesier (talk) 16:51, 24 May 2022 (UTC)
- Strong oppose Unless this limited to one settlement type and different id's are proposed for the others. This will not work as an external id within Wikidata if the same number can be assigned to multiple entities. ArthurPSmith (talk) 13:37, 25 May 2022 (UTC)
- Each settlement has only 1 attribute and 1 number. --Sadrettin (talk) 17:39, 25 May 2022 (UTC)
- @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)
- Each settlement has only 1 attribute and 1 number. --Sadrettin (talk) 17:39, 25 May 2022 (UTC)
Italian Chamber of Deputies Government IDEdit
Description | Identifier of Italian governments from the Italian Chamber of Deputies |
---|---|
Represents | Government of Italy (Q3773971) |
Data type | External identifier |
Domain | Government of Italy (Q3773971) |
Allowed values | \d+ |
Example 1 | Gentiloni Cabinet (Q27998924) → 122 |
Example 2 | Letta Cabinet (Q12080459) → 82 |
Example 3 | Renzi Cabinet (Q15772498) → 102 |
Source | http://dati.camera.it |
Planned use | Map all Italian post-war governments to dati.camera.it |
Number of IDs in source | 67 |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | http://dati.camera.it/ocd/governo.rdf/g$1 |
See also | Italian Chamber of Deputies dati ID (P1341) |
Applicable "stated in"-value | dati.camera.it (Q106874642) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | WikiProject Politics (Q5492483) |
MotivationEdit
This is one of multiple useful identifiers at the Chamber of Deputies linked data platform. It's similar to Italian Chamber of Deputies dati ID (P1341) but as the URL structure for deputies and governments differ I thought it best to create distinct identifiers for them. The identifier can be used to query additional connections between e.g. deputies, governments, parliamentary groups etc. Popperipopp (talk) 14:35, 9 May 2022 (UTC)
DiscussionEdit
- Support, Notified participants of WikiProject Italy —MasterRus21thCentury (talk) 05:52, 14 May 2022 (UTC)
- Support --Fausta Samaritani (talk) 06:52, 14 May 2022 (UTC)
- Support --FeltriaUrbsPicta (msg) 07:56, 14 May 2022 (UTC)
- Support --Luca.favorido (talk) 08:08, 14 May 2022 (UTC)
- Support --Galessandroni (talk) 10:49, 14 May 2022 (UTC)
- Support--Parma1983 (talk) 11:41, 14 May 2022 (UTC)
- Support --Susanna Giaccai (talk) 13:05, 14 May 2022 (UTC)
- Support--Alexmar983 (talk) 13:54, 14 May 2022 (UTC)
- Support --Camelia (talk) 15:19, 14 May 2022 (UTC)
- Support --AttoRenato (talk) 16:11, 14 May 2022 (UTC)
- Strong support --Luckyz (talk) 19:36, 14 May 2022 (UTC)
- Support --Sentruper (talk) 08:06, 15 May 2022 (UTC)
PM20 ware IDEdit
Description | identifier for a wares category in the 20th Century Press Archives' wares category system |
---|---|
Represents | mostly some kind of tangible good (Q1485500) |
Data type | External identifier |
Domain | 20th Century Press Archives (Q36948990) |
Allowed values | \d{6} |
Example 1 | coal (Q24489) → 143120 |
Example 2 | trailer (Q216146) → 141974 |
Example 3 | Ananas comosus (Q1493) → 141970 |
Source | https://pm20.zbw.eu |
Planned use | Create links in order to make the folders of the commodities/wares archives of PM20 accessible |
Number of IDs in source | c. 270 active categories |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | http://zbw.eu/beta/pm20voc/ip/$1 |
MotivationEdit
The Wikidata:WikiProject 20th Century Press Archives aims at linking all folders of the collection to Wikidata. After the folders of the persons, company and subject archives have been linked, next step is creating the metadata for the folders of the PM20 wares archives. (Currently, the external-id link redirects to a Skosmos page - will be replaced by a list of all folders about this ware in different countries). --Jneubert (talk) 05:40, 10 May 2022 (UTC)
Notified participants of WikiProject Authority control
DiscussionEdit
- Support. YULdigitalpreservation (talk) 16:42, 11 May 2022 (UTC)
JBIS horse IDEdit
Description | identifier for the horse in Japan Bloodstock Information System (JBIS) |
---|---|
Represents | Japan Bloodstock Information System (Q111961534) |
Data type | External identifier |
Domain | horse (Q726) |
Example 1 | Gold Ship (Q4309285) → Gold Ship(JPN) |
Example 2 | Orfevre (Q7101712) → Orfevre(JPN) |
Example 3 | Special Week (Q11312941) → Special Week(JPN) |
Example 4 | Silence Suzuka (Q7514393) → Silence Suzuka(JPN) |
Source | https://www.jbis.jp/ |
Planned use | for usage in stated in stated in (P248) and for linking all horses to JBIS database |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.jbis.jp/horse/$1 |
Applicable "stated in"-value | Japan Bloodstock Information System (Q111961534) |
Wikidata project | Wikidata:WikiProject_Equines |
MotivationEdit
JBIS is the largest database of horse racing in Japan that provides access to pedigree, race record, and sales information on Japanese Horses. This database is operated by Japan Bloodhorse Breeders' Association (JBBA). The database is also available to the general public, making it a unique source of detailed information on Japanese racing and breeding.Titanboo (talk) 04:39, 11 May 2022 (UTC)
DiscussionEdit
- Support--Momiji-Penguin (talk) 19:16, 12 May 2022 (UTC)
- Support JBIS is a very extensive database for horse, especially Japanese horses. Fexpr (talk) 08:12, 13 May 2022 (UTC)
- Support RXerself (talk) 08:49, 13 May 2022 (UTC)
- Support 本日晴天 (talk) 09:24, 13 May 2022 (UTC)
- Support Akbar Soepadhi (talk) 09:54, 13 May 2022 (UTC)
- Support Rkrifat (talk) 10:20, 13 May 2022 (UTC)
- Support VIGNERON (talk) 12:03, 13 May 2022 (UTC)
- Support Marchellangelina 06:41, 19 May 2022 (UTC)
- Support LilyanAgustine (talk) 14:52, 19 May 2022 (UTC)
Italian Chamber of Deputies parliamentary group IDEdit
Description | identifier for a parliamentary group of the Italian Chamber of Deputies |
---|---|
Represents | parliamentary group (Q848197) |
Data type | External identifier |
Domain | Q848197 |
Example 1 | Civics and Innovators (Q27534787) → 1613 |
Example 2 | Mixed group of Italy's 17th Legislature (Q20010077) → 1589 |
Example 3 | Noi con l'Italia - Scelta Civica per l'Italia - MAIE (Q111738297) → 2670 |
Source | http://dati.camera.it |
Planned use | Map all Italian post-war parliamentary groups to dati.camera.it |
Number of IDs in source | 228 |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | http://dati.camera.it/ocd/gruppoParlamentare.rdf/gr$1 |
See also | Italian Chamber of Deputies dati ID (P1341) |
Applicable "stated in"-value | dati.camera.it (Q106874642) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | WikiProject Politics (Q5492483) |
MotivationEdit
This is one of multiple useful identifiers at the Chamber of Deputies linked data platform. It's similar to Italian Chamber of Deputies dati ID (P1341) but as the URL structure for deputies and parliamentary groups differ I thought it best to create distinct identifiers for them. The identifier can be used to query additional connections between e.g. deputies, governments, parliamentary groups etc. See also the above proposal on government identifiers from the same source. Popperipopp (talk) 07:40, 12 May 2022 (UTC)
DiscussionEdit
- Support, Notified participants of WikiProject Italy —MasterRus21thCentury (talk) 10:11, 16 May 2022 (UTC)
- Support --Epìdosis 10:12, 16 May 2022 (UTC)
- Support --Horcrux (talk) 10:13, 16 May 2022 (UTC)
- Support --FeltriaUrbsPicta (msg) 10:34, 16 May 2022 (UTC)
- Support --Fausta Samaritani (talk) 11:05, 16 May 2022 (UTC)
- Support--Parma1983 (talk) 11:19, 16 May 2022 (UTC)
- Support --Camelia (talk) 11:29, 16 May 2022 (UTC)
- Support -Galessandroni (talk) 12:43, 16 May 2022 (UTC)
- Support --Sentruper (talk) 21:15, 16 May 2022 (UTC)
- Support --Carlobia (talk) 10:54, 18 May 2022 (UTC)
Moscow Cultural Heritage IDEdit
Description | идентификатор культурного наследия в базе данных Москомнаследия (ru) – (Please translate this into English.) |
---|---|
Represents | Department of Cultural Heritage of Moscow (Q4158545) |
Data type | External identifier |
Template parameter | Q22849211 |
Domain | cultural heritage site in Russia (Q8346700) in Moscow (Q649) |
Example 1 | Biblioteka Imeni Lenina (Q586295) → 7657409 |
Example 2 | Lubyanka Building (Q646334) → 2954636 |
Example 3 | Solovetsky Stone (Q4427945) → 7683116 |
Source | https://data.mos.ru/opendata/530 |
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]. |
Number of IDs in source | 8329 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://data.mos.ru/opendata/530/row/$1 |
Robot and gadget jobs | import from ru.wikipedia |
See also | kulturnoe-nasledie.ru ID (P1483), EGROKN ID (P5381) |
Applicable "stated in"-value | Department of Cultural Heritage of Moscow (Q4158545) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | Russia, Cultural heritage |
MotivationEdit
The Russian capital has its own database of cultural heritage, distinct from the national one. Most of Moscow's cultural heritage sites on this list are not included in the general list of Russia's cultural heritage, as stated in the Wikipedia databases. MasterRus21thCentury (talk) 06:57, 14 May 2022 (UTC)
DiscussionEdit
- Notified participants of WikiProject Russia —MasterRus21thCentury (talk) 16:50, 14 May 2022 (UTC)
- - Kareyac (talk) 07:19, 21 May 2022 (UTC)
- Question: вы за или против? MasterRus21thCentury (talk) 08:47, 21 May 2022 (UTC)
ORKG IDEdit
Description | Open Research Knowledge Graph (ORKG) ID |
---|---|
Data type | External identifier |
Domain | item |
Example 1 | Open Research Knowledge Graph: Towards Machine Actionability in Scholarly Communication (Q61605356) → R1020 |
Example 2 | Situational Knowledge Representation for Traffic Observed by a Pavement Vibration Sensor Network (Q58464280) → R6758 |
Example 3 | Transmission potential of COVID-19 in Iran (Q88976415) → R44759 |
Source | https://www.orkg.org/ |
Planned use | link scholarly article items in Wikidata to their corresponding ORKG entries. Later, it is possible to link other entities as well (venues, research fields, research problems, authors etc.) |
Number of IDs in source | 10100 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://www.orkg.org/orkg/resource/$1 |
See also | Semantic Scholar paper ID (P4011) Google Scholar paper ID (P4028) arXiv ID (P818) DBLP publication ID (P8978) |
Applicable "stated in"-value | Open Research Knowledge Graph (Q108127463) |
MotivationEdit
The Open Research Knowledge Graph provides machine-readable descriptions of scholarly articles. By linking Wikidata scholarly article entries to ORKG entries, additional scholarly knowledge can be fetched for such articles. Unlike other scholarly article repositories (see the related properties), ORKG focuses on the actual knowledge presented in the article (i.e. research contribution) and not on merely article metadata. Allard123 (talk) 11:38, 16 May 2022 (UTC)
DiscussionEdit
- Support Looks useful to me! ArthurPSmith (talk) 19:41, 23 May 2022 (UTC)
- Support --Jneubert (talk) 18:36, 27 May 2022 (UTC)
Lithuania Minor encyclopedia IDEdit
Description | article identifier in the online version of Lithuania Minor encyclopedia |
---|---|
Represents | no label (Q12664914) |
Data type | External identifier |
Allowed values | [a-z0-9-]+ |
Example 1 | Agluonėnai (Q10719384) → agluonenai |
Example 2 | Medal for the Liberation of Klaipėda (Q4287177) → klaipedos-krasto-atvadavimo-medalis |
Example 3 | Martynas Jankus (Q3917296) → martynas-jankus |
Example 4 | Kaliningrad (Q1829) → karaliaucius |
Source | https://www.mle.lt/ |
Planned use | ru:Template:ВС |
Number of IDs in source | 12000 |
Expected completeness | eventually complete |
Formatter URL | https://www.mle.lt/straipsniai/$1 |
Applicable "stated in"-value | no label (Q12664914) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | WikiProject Lithuania (Q11037150), WikiProject Russia (Q10803886) |
MotivationEdit
The encyclopedia about the history of Lithuania Minor has become officially available online in 2020. It may be useful for articles about the history of Lithuania and the Kaliningrad region. —putnik 12:21, 22 May 2022 (UTC)
DiscussionEdit
- Notified participants of WikiProject Russia. —putnik 12:23, 22 May 2022 (UTC)
- Support —MasterRus21thCentury (talk) 12:39, 22 May 2022 (UTC)
- Sure, it is a good addition. Андрей Романенко (talk) 19:39, 22 May 2022 (UTC)
BRUZZ topic IDEdit
Description | identifier for a topic on the BRUZZ website |
---|---|
Represents | BRUZZ (Q23934497) |
Data type | External identifier |
Domain | all |
Example 1 | Karl Vanlouwe (Q1859093) → karl-vanlouwe |
Example 2 | particulates (Q498957) → fijn-stof-0 |
Example 3 | 2016 Brussels bombings (Q23365300) → aanslagen-22-maart-2016 |
Example 4 | Anheuser-Busch InBev (Q128738) → ab-inbev |
Source | https://www.bruzz.be/ |
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]. |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.bruzz.be/tag/$1 |
See also | Property proposal/BRUZZ place ID |
MotivationEdit
Significant and reputable news source mainly in Dutch
DiscussionEdit
BRUZZ place IDEdit
Description | identifier for a place on the BRUZZ website |
---|---|
Represents | BRUZZ (Q23934497) |
Data type | External identifier |
Domain | all |
Example 1 | Anderlecht (Q12886) → anderlecht |
Example 2 | Brussels-Capital Region (Q240) → brussel |
Example 3 | City of Brussels (Q239) → brussel-stad |
Example 4 | Neder-Over-Heembeek (Q2645721) → neder-over-heembeek |
Source | https://www.bruzz.be/ |
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]. |
Number of IDs in source | 23 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://www.bruzz.be/gemeente/$1 |
See also | Property_proposal/Authority_control#BRUZZ_topic_ID |
MotivationEdit
It has organizes each article according to the location.
DiscussionEdit
Plex GUIDEdit
Description | identifier for media item on Plex |
---|---|
Data type | External identifier |
Domain | film (Q11424) television program (Q15416) |
Allowed values | plex://(episode|movie|season|show)/[a-f0-9]{24} |
Example 1 | Casino Royale (Q151904) → plex://movie/5d7768686f4521001eaa5cac |
Example 2 | Hannibal (Q888841) → plex://show/5d9c08544eefaa001f5daa50 |
Example 3 | Hannibal, season 1 (Q15991276) → plex://season/5d9c09bd3c3f87001f361344 |
Example 4 | Apéritif (Q30612280) → plex://episode/5d9c11154eefaa001f6364e0 |
Source | https://www.plex.tv |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://wikidata-externalid-url.toolforge.org/index.php?url=https%3A%2F%2Fapp.plex.tv%2Fdesktop%2F%23%21%2Fprovider%2Ftv.plex.provider.metadata%2Fdetails%3Fkey%3D%2Flibrary%2Fmetadata%2F%251&exp=%28%5Ba-f0-9%5D%2B%29%24&id=$1 |
Single-value constraint | yes |
Distinct-values constraint | yes |
MotivationEdit
The Plex (Q7204887) media system provides public GUIDs for movies and TV shows on it's public catalog on plex.tv. The canonical format of the GUID is a URI of the form plex://movie/5d7768686f4521001eaa5cac
. These may identify movies/films and tv shows/seasons/episodes. Other types of media may be supported in the future. It'd be exciting to have these IDs associated on Wikidata items to enable cross referencing of other properties such as IMDb ID (P345) or TMDb movie ID (P4947).
DiscussionEdit
Scottish Highland Bridges IDEdit
Description | Identifier for a bridge or other structure on the Scottish Highland Bridges website |
---|---|
Represents | bridge (Q12280) |
Data type | External identifier |
Domain | bridge (Q12280) |
Allowed values | ([01]\d_[AX\d][\dA]|[AHMNPSW][12]\d{3}|HL[\dX]\d\d) |
Example 1 | Lovat Bridge (Q17568543) → 09_01 |
Example 2 | Holme Bridge (Q17826757) → HL169 |
Example 3 | Culloden Viaduct (Q11838929) → 04_01 |
Example 4 | Kessock Bridge (Q1739833) → 02_01 |
Source | https://www.kweimar.de/SCMap.html |
Planned use | match to existing items, identify bridges without items |
Number of IDs in source | 776 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://www.kweimar.de/Bilder_XML.php?ket=$1 |
See also | Historic Scotland ID (P709), Canmore ID (P718), Highland Historic Environment Record ID (P7304), Aberdeenshire HER ID (P7694) |
Applicable "stated in"-value | Scottish Highland Bridges website (Q112147377) |
Single-value constraint | yes |
Distinct-values constraint | yes |
MotivationEdit
The Scottish Highland Bridges website is a database by Wolfgang Krüger containing information, classifications, and photographs of bridges in the Scottish Highlands. The site typically has multiple photographs for each bridge (click on the first picture for slideshow).
The site systematically links back to Historic Scotland ID (P709), Canmore ID (P718), Highland Historic Environment Record ID (P7304), and Aberdeenshire HER ID (P7694) IDs, which should make it possible to match a large proportion of entries to corresponding Wikidata items directly. There are also forward links to the site from Highland Historic Environment Record ID (P7304) entries.
The photographs and the information make this a valuable additional resource for Wikidata items to be linked to. The site may also identify some additional bridges that do not have Historic Scotland or Canmore IDs, that it would be useful to create items for.
As well as Scottish bridges, the site also has sections in the same style relating to the works of Thomas Telford (Q380875), and to bridges in Thuringia. However, these have slightly different URLs, so (if desired) it would make sense to have separate properties for those parts of the site. Jheald (talk) 17:20, 27 May 2022 (UTC)
DiscussionEdit
- Proposed. Jheald (talk) 17:54, 27 May 2022 (UTC)
- Support. Seems a well curated site. Both sites will benefit from a WD ID. (Also notable that Canmore links to www.kweimar.de but not yet to Wikidata, e.g. [1]) --Tagishsimon (talk) 18:30, 27 May 2022 (UTC)
- Support --Jneubert (talk) 18:32, 27 May 2022 (UTC)