Wikidata:Property proposal/Authority control
Property proposal: | Generic | Authority control | Person | Organization |
Creative work | Place | Sports | Sister projects | |
Transportation | Natural science | Computing | Lexeme |
See also
edit- 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
- Search if the property already exists.
- Search if the property has already been proposed.
- Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically.
- Select the right datatype for the property.
- Read Wikidata:Creating a property proposal for guidelines you should follow when proposing new property.
- Start writing the documentation based on the preload form below by editing the two templates at the top of the page to add proposal details.
Creating the property
- Once consensus is reached, change status=ready on the template, to attract the attention of a property creator.
- Creation can be done 1 week after the creation of the proposal, by a property creator or an administrator.
- See property creation policy.
![]() |
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 2025/05. |
Encyclopedia
editOberpfalzWiki article ID
editDescription | Identifier for articles in OberpfalzWiki, a city wiki for Oberpfalz, Bavaria, Germany. |
---|---|
Represents | Upper Palatinate (Q10555) |
Data type | External identifier |
Allowed values | [^\s]+ |
Example 1 | Alfred Härtl (Q2645200)→Alfred_Härtl |
Example 2 | Hermann Frieser (Q125489352)→Hermann_Frieser |
Example 3 | Eh'häusl (Q835547)→Eh'häusl |
Source | OberpfalzWiki (Q130283034) |
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]. |
Planned use | Linking Wikidata/Wikimedia Commons items (in infoboxes) related to Oberpfalz to their corresponding articles in OberpfalzWiki. |
Number of IDs in source | Approximately 1,700 articles as of May 2025 |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.oberpfalzwiki.de/$1 |
Country | Germany (Q183) |
See also | Stadtwiki Dresden article (P8713), OesterreichWiki ID (P6228), Stadtwiki Karlsruhe ID (P12984), and many more city wikis |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editThe OberpfalzWiki is a community-driven, non-commercial online encyclopedia dedicated to documenting the history and present of Oberpfalz, Bayern. Only established in January 2025, it has already published over 1.700 articles as of May 2025. Some of the articles are related to Wikipedia articles, and for many there are Wikidata entities, so there would be a lot of connections. --Bebbe (talk) 10:44, 13 May 2025 (UTC)
Discussion
edit- Support --[[kgh]] (talk) 21:42, 13 May 2025 (UTC)
- I know, that different Wikis handle this different. I think, that the page names are nicer, see P7140 at Q252648. I know, that the handling is a little bit easier with page IDs, but I hope, that the search engines will like it more, if they get text, which can be read by humans. --Bebbe (talk) Bebbe (talk) 22:00, 13 May 2025 (UTC)
Rhein-Neckar-Wiki-Kennung
editDescription | Identifier for articles in the Rhein-Neckar-Wiki, a regional wiki for the Rhine-Neckar Metropolitan Region, a cross-border area in southwestern Germany spanning parts of Baden-Württemberg, Rhineland-Palatinate, and Hesse. |
---|---|
Represents | Rhein-Neckar-Wiki (Q106165542) |
Data type | External identifier |
Domain | item |
Allowed values | [1-9]\d* |
Example 1 | Heidelberg (Q2966)→1309 |
Example 2 | Heidelberger Bergbahn (Q1594020)→1752 |
Example 3 | Heidelberg Castle (Q327265)→1679 |
Example 4 | Mannheim (Q2119)→6628 |
Example 5 | Ludwigshafen (Q2910)→1518 |
Example 6 | BASF (Q9401)→1566 |
Example 7 | SAP (Q552581)→2405 |
Example 8 | Category:People from Heidelberg (Q8736254)→1730 |
Example 9 | Category:Buildings and structures in Mannheim (Q8322536)→12919 |
Source | rhein-neckar-wiki.de |
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]. |
Planned use | Linking Wikidata and Wikimedia Commons items related to the Rhein-Neckar Region to their corresponding articles in the Rhein-Neckar-Wiki. |
Number of IDs in source | Approximately 12,115 articles and 6,670 photo articles as of May 2025 |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://rhein-neckar-wiki.de/?curid=$1 |
URL match pattern | ^https?:\/\/rhein-neckar-wiki\.de\/\?curid=([1-9]\d*)$ |
Country | Germany (Q183) |
See also | Stadtwiki Dresden article (P8713), OesterreichWiki ID (P6228), Stadtwiki Karlsruhe ID (P12984), Vienna History Wiki ID (P7842), Salzburgwiki ID (P8854) and more city wikis |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | Rhein-Neckar-Wiki (Q106165542) |
Motivation
editen = The Rhein-Neckar-Wiki is a community-driven, non-commercial regional encyclopedia focused on documenting the history, culture, and present-day life of the Rhine-Neckar Metropolitan Region. This cross-border area in southwestern Germany covers parts of the federal states of Baden-Württemberg, Rhineland-Palatinate, and Hesse, including major cities such as Mannheim, Ludwigshafen, and Heidelberg. Linking Wikidata items to Rhein-Neckar-Wiki articles will facilitate access to region-specific knowledge and strengthen the connection between Wikidata and regional knowledge repositories. --Vbachem (talk) 23:35, 11 May 2025 (UTC)
de = Das Rhein-Neckar-Wiki ist ein gemeinschaftlich betriebenes, nicht-kommerzielles Regiowiki, das sich der Dokumentation der Geschichte, Kultur und Gegenwart der Metropolregion Rhein-Neckar widmet. Diese grenzüberschreitende Region in Südwestdeutschland erstreckt sich über Teile der Bundesländer Baden-Württemberg, Rheinland-Pfalz und Hessen und umfasst bedeutende Städte wie Mannheim, Ludwigshafen und Heidelberg. Die Verknüpfung von Wikidata-Elementen mit Artikeln im Rhein-Neckar-Wiki erleichtert den Zugang zu regionalem Wissen und stärkt die Verbindung zwischen Wikidata und regionalen Wissensbeständen.
--Vbachem (talk) 23:35, 11 May 2025 (UTC)
Discussion
edit- Support LGTM. Formatter URL should not point to search results but directly to the page, so: https://rhein-neckar-wiki.de/$1 Infrastruktur (talk) 15:01, 12 May 2025 (UTC)
- Support Yes, though I suggest changing the proposed identifier and URL formatter as per talk page. --[[kgh]] (talk) 16:24, 12 May 2025 (UTC)
- Support Yes, please Fuellel (talk)
- Support makes sense! --Bebbe (talk)
Stadtwiki Meißen ID
editDescription | Identifier for articles in the Stadtwiki Meißen, a city wiki for Meißen, Saxony, Germany. |
---|---|
Represents | Meissen (Q8738) |
Data type | External identifier |
Domain | item |
Allowed values | [1-9]\d* |
Example 1 | Church of Our Lady (Q1451777)→44 |
Example 2 | Siebeneichen (Q1504268)→72 |
Example 3 | Triebisch (Q2452864)→83 |
Source | City Wiki Meißen (Q131285422) |
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]. |
Planned use | Linking Wikidata/Wikimedia Commons items (in infoboxes) related to Meißen to their corresponding articles in Stadtwiki Meißen. |
Number of IDs in source | Approximately 800 articles as of May 2025 |
Expected completeness | always incomplete (Q21873886) |
Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
Formatter URL | https://stadtwiki-meissen.de/?curid=$1 |
Country | Germany (Q183) |
See also | Stadtwiki Dresden article (P8713), OesterreichWiki ID (P6228), Stadtwiki Karlsruhe ID (P12984), and many more city wikis |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editThe Stadtwiki Meißen is a community-driven, non-commercial online encyclopedia dedicated to documenting the history and present of Meißen, Saxony. Only established in March 2024, it has already published over 800 articles as of May 2025. Some of the articles are related to Wikipedia articles, and for many there are Wikidata entities, so there would be a lot of connections. Fuellel (talk) 05:55, 11 May 2025 (UTC)
Discussion
editSupport can't think of any reason, why not. MB-one (talk) 07:52, 11 May 2025 (UTC)
Support - as MB-one. -- Marcus Cyron (talk) 07:58, 11 May 2025 (UTC)
Support Yes, please. --Tkarcher (talk) 08:01, 11 May 2025 (UTC)
Support, sure. DerHexer (talk) 08:57, 11 May 2025 (UTC)
Support Yes. --Vbachem (talk) 16:54, 11 May 2025 (UTC)
Support This wiki is hosted on Mediawiki, so allowed values for the ID is whatever Mediawiki allows for the page titles: https://www.mediawiki.org/wiki/Manual:$wgLegalTitleChars/en . Article count seems to be 790 as of the time of writing: https://stadtwiki-meissen.de/wiki/Spezial:Statistik . Infrastruktur (talk) 16:04, 11 May 2025 (UTC)
- Article count is over 800 now. :) Fuellel (talk) 21:00, 15 May 2025 (UTC)
Support Yes, though I suggest changing the proposed identifier and URL formatter as per talk page. --[[kgh]] (talk) 15:20, 12 May 2025 (UTC)
- As I wrote on the talk page, I changed the proposal to use PageIDs. Fuellel (talk) 19:19, 12 May 2025 (UTC)
- Cool, and thanks a bunch. [[kgh]] (talk) 19:38, 12 May 2025 (UTC)
Encyclopedia of Marxism ID
editMotivation
editThis is a reasonably large database of Marxists, Marxism and related subjects. It should be noted that some subjects have multiple entries in different portions of the resource. The linked Mix'n'match catalogue is devoted to the people in the database, but there are several organisations and periodicals listed in it. Susmuffin (talk) 12:34, 2 February 2025 (UTC)
Discussion
editWikiProject Authority control has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. Susmuffin (talk) 12:34, 2 February 2025 (UTC)
Notified participants of WikiProject Philosophy
Notified participants of WikiProject Sociology
These WikiProjects would also be interested in this potential identifier. Susmuffin (talk) 21:28, 26 February 2025 (UTC)
- Oppose Hi, thank you for this proposition. However, I think these are just web links and not unique identifiers. Therefore it cannot be used with the unique identifier properties. Instead, you may create or complete marixism related items (ex: with dates, definitions, occupation of the people mentionned...) and use the publication mentionned in the website as reference (Published in To the Masses: Proceedings of the Third Congress of the Communist International, 1921 (https://www.haymarketbooks.org/books/897-to-the-masses), pp. 1203-1250. & Or in Toward the United Front: Proceedings of the Fourth Congress of the Communist International, 1922 (https://www.haymarketbooks.org/books/472-toward-the-united-front), pp. 1211-1255.) For social sciences, we have institutionnaly recognized identifiers (ex: thesaurus, encyclopedia IDs) and if you look in the Karl Marx item you will see there are already a lot of them.
- The structure is similar to that of The Peerage person ID (P4638), which has been a property for some time. That property makes use of different sections on an alphabetically ordered set of pages, much like this one would. In terms of its utility as a property related to the social sciences, this one would be related to Marxism specifically. In many cases, there are links to archives of works that are in the public domain and other openly accessible content that is related to the identifiers' subjects. Susmuffin (talk) 17:33, 3 March 2025 (UTC)
- Support Agreed--Trade (talk) 13:11, 22 April 2025 (UTC)
WürzburgWiki ID
editDescription | Identifier for articles in the WürzburgWiki, a city and regional wiki for Würzburg, Franconia, Germany. |
---|---|
Represents | Würzburg (Q2999) and Würzburg (Q10458) |
Data type | External identifier |
Domain | item |
Allowed values | [1-9]\d* |
Example 1 | University of Würzburg (Q161976)→1026 |
Example 2 | Würzburg Residence (Q156316)→1103 |
Example 3 | Johann Balthasar Neumann (Q61349)→888 |
Source | WürzburgWiki (Q28466308) |
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]. |
Planned use | Linking item on Wikidata and Wikimedia Commons items (in infoboxes) related to Würzburg and the surrunding region to their corresponding articles in WürzburgWiki. |
Number of IDs in source | Approximately 30800 articles as of May 2025 |
Expected completeness | always incomplete (Q21873886) |
Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
Formatter URL | https://wuerzburgwiki.de/w/index.php?curid=$1 |
URL match pattern | ^https?:\/\/(?:www\.)?wuerzburgwiki\.de\/([1-9]\d*) |
Country | Germany (Q183) |
See also | OesterreichWiki ID (P6228), Stadtwiki Dresden article (P8713), Vienna History Wiki ID (P7842), Stadtwiki Karlsruhe ID (P12984), and many more city and region wikis |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editThe WürzburgWiki is a community-driven, non-commercial online encyclopedia dedicated to documenting the history and present of Würzburg and the surrunding region. Established in July 2007, it has already published over 30800 articles as of May 2025. Some of the articles are related to Wikipedia articles, and for many there are Wikidata entities, so there would be a lot of connections. --[[kgh]] (talk) 16:01, 12 May 2025 (UTC)
Discussion
editSupport Infrastruktur (talk) 16:43, 12 May 2025 (UTC) Support Yes, please!! --Bebbe (talk)
AW-Wiki ID
editDescription | Identifier for articles in AW-Wiki, a region wiki for the Ahrweiler district and region, Germany. |
---|---|
Represents | Ahrweiler (Q8596) |
Data type | External identifier |
Domain | item |
Allowed values | [1-9]\d* |
Example 1 | Maria Laach Abbey (Q334032)→3745 |
Example 2 | Ahr Valley (Q402908)→5261 |
Example 3 | Andernach Geyser (Q15111605)→3567 |
Source | Q134448312 |
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]. |
Planned use | Linking item on Wikidata and Wikimedia Commons items (in infoboxes) related to the Ahrweiler district and region to their corresponding articles in AW-Wiki. |
Number of IDs in source | Approximately 34000 articles as of May 2025 |
Expected completeness | always incomplete (Q21873886) |
Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
Formatter URL | https://www.aw-wiki.de/index.php?curid=$1 |
URL match pattern | ^https?:\/\/(?:www\.)?aw-wiki\.de\/index\.php\?curid=([1-9]\d*) |
Country | Ahrweiler (Q8596) |
See also | OesterreichWiki ID (P6228), Stadtwiki Dresden article (P8713), Vienna History Wiki ID (P7842), Stadtwiki Karlsruhe ID (P12984), and many more city and region wikis |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editThe AW-Wiki is a community-driven, non-commercial online encyclopedia dedicated to documenting the history and present of the Ahrweiler district and region. Established in August 2007, it has already published over 34000 articles as of May 2025. Some of the articles are related to Wikipedia articles, and for many there are Wikidata entities, so there would be a lot of connections --[[kgh]] (talk) 22:07, 12 May 2025 (UTC)
Discussion
editSupport Yes, please! --Bebbe (talk)
Wetzipedia ID
editDescription | Identifier for articles in Wetzipedia, a city wiki for Wetzikon, Switzerland. |
---|---|
Represents | Wetzikon (Q68305) |
Data type | External identifier |
Domain | item |
Allowed values | [1-9]\d* |
Example 1 | Jakob Messikommer (Q14545364)→137 |
Example 2 | Hedi Lang (Q116380)→559 |
Example 3 | Wetzikon–Meilen tramway (Q2566204)→148 |
Source | Wetzipedia (Q96473741) |
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]. |
Planned use | Linking item on Wikidata and Wikimedia Commons items (in infoboxes) related to Wetzikon to their corresponding articles in Wetzipedia. |
Number of IDs in source | Approximately 23800 articles as of May 2025 |
Expected completeness | always incomplete (Q21873886) |
Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
Formatter URL | https://www.wetzipedia.ch/index.php?curid=$1 |
URL match pattern | ^https?:\/\/(?:www\.)?wetzipedia\.ch\/index\.php\?curid=([1-9]\d*) |
Country | Switzerland (Q39) |
See also | OesterreichWiki ID (P6228), Stadtwiki Dresden article (P8713), Vienna History Wiki ID (P7842), Stadtwiki Karlsruhe ID (P12984), and many more city and region wikis |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editThe Wetzipedia is a non-commercial online encyclopedia dedicated to documenting the history and present of Wetzikon. Established in July 2009, it has already published over 23800 articles as of May 2025. Some of the articles are related to Wikipedia articles, and for a lot of them there are Wikidata entities to estabish connections. --[[kgh]] (talk) 22:09, 12 May 2025 (UTC)
Discussion
editLibrary
editNLI Newspaper Collection ID
editDescription | Identifier for a periodical in the newspapers collections of the of the National Library of Israel |
---|---|
Represents | The National Library Newspaper Collection (Q130459321) |
Data type | External identifier |
Domain | periodical (Q1002697) |
Example 1 | ha-Modiʻa (Q16128641) –> hmd |
Example 2 | Yediʻot ʻIriyat Tel Aviv (Q31197462) –> ytlv |
Example 3 | El Horria (Q16128711) –> llb |
Example 4 | al-Awqāt al-ʻArabīyah (Q113190844) –> awqat |
Example 5 | The Detroit Jewish News (Q7729873) –> detroitjn |
Example 6 | Ha-Karmel (Q12406639) –> hcr |
Example 7 | L'Aurore (Q111169345) –> lauror |
Expected completeness | eventually complete (Q21873974) |
Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
Formatter URL | https://www.nli.org.il/he/newspapers/$1 OR https://www.nli.org.il/ar/newspapers/$1 OR https://www.nli.org.il/en/newspapers/$1 |
See also | Trove newspaper ID (P5603), Chronicling America newspaper ID (P4898), Newspapers.com paper ID (P7259) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editDiscussion
editWikiProject Authority control has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. Regards, ZI Jony (Talk) 05:10, 26 October 2024 (UTC)
- עברית: @לוכסן, לא כל כך הבנתי למה זה ישמש ואיך.Geagea (talk) 17:20, 7 October 2024 (UTC)
- @Geagea: שתי סיבות: א) זה עוזר בזיהוים של פריטי ויקינתונים על עיתונים (לפעמים יש כמה עיתונים בעלי שם דומה וגישה לזה עוזר), ב) בוויקיפדיה העברית, יש כבר קישורים לדף הזה בערכים רבים על עיתונים וכתבי עת. עם נוסיף את זה לוויקינתונים, נוכל ליצור את הקישורים האלה אוטומטית ובקלות וויקיפדיות אחרות יוכלו לנצל את זה גם. לוכסן (talk) 17:40, 7 October 2024 (UTC)
- מזהה עיתון לא מספיק צריך גם תאריך ומזהה כתבה. מזהה עיתון עצמו לא נותן קישור. Geagea (talk) 17:45, 7 October 2024 (UTC)
- @Geagea: מצטער, תן לי לדייק. מטרתי לקשר מהערך על, נגיד, "על המשמר" לאוסף המלא של כל המהדורות הסרוקות של העיתון. אני לא מתכוון להשתמש בזה כדי לקשר למהדורה מסוימת של העיתון בהקשר של הערת שוליים. בערך על המשמר בפרט, כבר יש קישור כזה בראש הפרק "קישורים חיצוניים" (הקישור לעיתונות היהודית ההיסטורית). לוכסן (talk) 18:01, 7 October 2024 (UTC)
- לכל עיתון יש פריט ויקינתונים (אם אין לו אז אפשר ליצור). אפשר לקשר לפריט. הפריט יכול לכלות קישור לאתר הספרייה. לא חושב שצריך בשביל זה מזהה. Geagea (talk) 18:24, 7 October 2024 (UTC)
- @Geagea: מבחינתי, זה לא קישור כלשהו אלא קישור ארכיוני מאוד ספציפי ושימושי (דומה מאוד למאפיינים קיימים דומים מהספרייה הלאומית של אוסטרליה (Trove newspaper ID (P5603)) ומספריית קונגרס (Chronicling America newspaper ID (P4898))), הגם שלוּ היינו מוסיפים קישור לפריט דרך איזה מאפיין (יש לך מאפיין מוצע? periodical archive URL (P7213)? full work available at URL (P953)?), הקישור יכלול ממשק רק בשפה שצוינה בקישור (ערבית, עברית, או אנגלית). אז, אם נרצה לקשר לזה בוויקיפדיה העברית, וירצו להשתמש בזה גם בוויקיפדיה הערבית או האנגלית, יצטרכו להוסיף עוד קישורים, שזה לא אידאלי. אז, בזמן שאיבת הקישור מוויקינתונים, איך נדע איזה קישור לכלול? זה כמובן אפשרי להשתמש במבחין כדי לציין את השפה, אבל אז יהיה צורך שלכל אחד מהמאות פריטים שבאוסף, נצטרך להוסיף שלושה קישורים כמעט זהים. הגם שנראה לי שזה יקשה על כל הוויקיפדיות שישתמשו בזה בעת השאיבה. לעומת זה, מאפיין זה משהו קל מאוד לשימוש. לוכסן (talk) 19:31, 7 October 2024 (UTC)
- לא חושב שיעשו בזה שימוש בוויקיפדיות אבל מאפיין דומה אכן קיים לפי הדוגמאות שהוספת. לא כתבת מה מספר סוגי העיתונים שמופיעים במאגר. אני גם לא מבין מה ההבדל בין " אוסף העיתונות וכתבי העת של הספרייה הלאומית" לבין אתר עיתונות יהודית היסטורית אם יש הבדל בכלל. אני לא מתנגד. אולי אם אפשר יהיה לקבל אקסל של מזהה עיתון עם שמות בשפות השונות ופרטים נוספים אפשר יהיה להריץ אופן ריפיין. Geagea (talk) 20:50, 7 October 2024 (UTC)
- @Geagea: מבחינתי, זה לא קישור כלשהו אלא קישור ארכיוני מאוד ספציפי ושימושי (דומה מאוד למאפיינים קיימים דומים מהספרייה הלאומית של אוסטרליה (Trove newspaper ID (P5603)) ומספריית קונגרס (Chronicling America newspaper ID (P4898))), הגם שלוּ היינו מוסיפים קישור לפריט דרך איזה מאפיין (יש לך מאפיין מוצע? periodical archive URL (P7213)? full work available at URL (P953)?), הקישור יכלול ממשק רק בשפה שצוינה בקישור (ערבית, עברית, או אנגלית). אז, אם נרצה לקשר לזה בוויקיפדיה העברית, וירצו להשתמש בזה גם בוויקיפדיה הערבית או האנגלית, יצטרכו להוסיף עוד קישורים, שזה לא אידאלי. אז, בזמן שאיבת הקישור מוויקינתונים, איך נדע איזה קישור לכלול? זה כמובן אפשרי להשתמש במבחין כדי לציין את השפה, אבל אז יהיה צורך שלכל אחד מהמאות פריטים שבאוסף, נצטרך להוסיף שלושה קישורים כמעט זהים. הגם שנראה לי שזה יקשה על כל הוויקיפדיות שישתמשו בזה בעת השאיבה. לעומת זה, מאפיין זה משהו קל מאוד לשימוש. לוכסן (talk) 19:31, 7 October 2024 (UTC)
- לכל עיתון יש פריט ויקינתונים (אם אין לו אז אפשר ליצור). אפשר לקשר לפריט. הפריט יכול לכלות קישור לאתר הספרייה. לא חושב שצריך בשביל זה מזהה. Geagea (talk) 18:24, 7 October 2024 (UTC)
- @Geagea: מצטער, תן לי לדייק. מטרתי לקשר מהערך על, נגיד, "על המשמר" לאוסף המלא של כל המהדורות הסרוקות של העיתון. אני לא מתכוון להשתמש בזה כדי לקשר למהדורה מסוימת של העיתון בהקשר של הערת שוליים. בערך על המשמר בפרט, כבר יש קישור כזה בראש הפרק "קישורים חיצוניים" (הקישור לעיתונות היהודית ההיסטורית). לוכסן (talk) 18:01, 7 October 2024 (UTC)
- מזהה עיתון לא מספיק צריך גם תאריך ומזהה כתבה. מזהה עיתון עצמו לא נותן קישור. Geagea (talk) 17:45, 7 October 2024 (UTC)
- @Geagea: שתי סיבות: א) זה עוזר בזיהוים של פריטי ויקינתונים על עיתונים (לפעמים יש כמה עיתונים בעלי שם דומה וגישה לזה עוזר), ב) בוויקיפדיה העברית, יש כבר קישורים לדף הזה בערכים רבים על עיתונים וכתבי עת. עם נוסיף את זה לוויקינתונים, נוכל ליצור את הקישורים האלה אוטומטית ובקלות וויקיפדיות אחרות יוכלו לנצל את זה גם. לוכסן (talk) 17:40, 7 October 2024 (UTC)
- Support But I think there can only be one formatter URL that is designated as the preferred one. Otherwise, it wouldn't be possible to know which formatter URL to use for any particular ID. AdamSeattle (talk) 17:25, 2 April 2025 (UTC)
- Support. Geagea (talk) 11:46, 28 April 2025 (UTC)
Fnac person ID
editMotivation
editNotified participants of WikiProject France: I propose to create a new property for the website Fnac (Q676585) which is a sizeable catalog of authors' works and biographical data. --Soufiyouns (talk) 13:32, 4 November 2024 (UTC)
Discussion
edit- Support ArthurPSmith (talk) 21:14, 4 November 2024 (UTC)
- Support - PKM (talk) 22:20, 4 November 2024 (UTC)
- Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:57, 11 November 2024 (UTC)
- Question I don't see how this is related to Fonds national d'art contemporain (Q3075877). www.fnac.com is a site run by Fnac (Q676585), a book/electronics retailer. Samoasambia ✎ 11:56, 13 November 2024 (UTC)
- @Samoasambia: Thank you very much for this very pertinent remark. I have just made the required modification. Regards. Soufiyouns (talk) 08:01, 14 November 2024 (UTC)
- Samoasambia, would you like to give your opinion? Regards, ZI Jony (Talk) 11:34, 14 December 2024 (UTC)
- I'm not sure if we need an authority control property for a book store. The biographical texts seem to be mostly copied from elsewhere, in the case of Agatha Christie it is from evene.lefigaro.fr and Victor Hugo from Wikipedia. Samoasambia ✎ 12:14, 18 December 2024 (UTC)
- @Samoasambia: Thank you very much for this very useful clarification. I also think that this property will enrich Wikidata with its counterpart Amazon author ID (P4862) which is also a book store, and French-speaking authors who are not mentioned in the Amazon (Q3884) database can be found and promoted through the Fnac (Q676585) database. Regards. Soufiyouns (talk) 06:44, 19 December 2024 (UTC)
- I'm not sure if we need an authority control property for a book store. The biographical texts seem to be mostly copied from elsewhere, in the case of Agatha Christie it is from evene.lefigaro.fr and Victor Hugo from Wikipedia. Samoasambia ✎ 12:14, 18 December 2024 (UTC)
- Samoasambia, would you like to give your opinion? Regards, ZI Jony (Talk) 11:34, 14 December 2024 (UTC)
- @Samoasambia: Thank you very much for this very pertinent remark. I have just made the required modification. Regards. Soufiyouns (talk) 08:01, 14 November 2024 (UTC)
eLIBRARY Document Number
editDescription | document identifier at elibrary.ru |
---|---|
Represents | not yet |
Data type | External identifier |
Domain | intellectual work (Q15621286) |
Allowed values | \\w+ |
Example 1 | Q122987597 -> VWFWBP |
Example 2 | Q77668068 -> FUMUIG |
Example 3 | MISSING |
Source | external database (elibrary.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] • [en.wikt] • [fr.wikt]. |
Planned use | somebody will mass import |
Number of IDs in source | ~45mln and growing |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.elibrary.ru/$1 |
See also | elibrary.ru article ID (P11860) |
Applicable "stated in"-value | eLibrary.ru (Q4037789) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editeLIBRARY Document Number (EDN) is an universal identifier for all documents at eLIBRARY.ru. They include academic articles, monographies, proceedings, and books of conference abstracts. At present more than 45 millions items have EDN. In plans all items having DOI will have also EDN, thus this ID will be more complete than DOI (with addition of Russian magazines, which don't have DOI yet). Wikidata should be a hub linking DOI and EDN identifiers. P.S. It's different from (and not replaces) Infovarius (talk) 11:57, 25 February 2025 (UTC)
Discussion
editLUX person ID
editDescription | identifier for a person in the Yale University LUX discovery platform |
---|---|
Represents | LUX (Q133612457) |
Data type | External identifier |
Allowed values | [a-z0-1]{8}-[a-z0-1]{4}-[a-z0-1]{4}-[a-z0-1]{4}-[a-z0-1]{12} |
Example 1 | Eva Strautmann (Q1230142) → bffc05ec-afa5-4a26-979f-c484013c2d4f |
Example 2 | Ernst Mayr (Q5354) → ecbd10ab-bbb0-41dd-86a1-f9f7ab1cbf8c |
Example 3 | Julia Moss Seton (Q112461802) → 67e5c387-ba19-4bbc-b931-215ec1276a14 |
Example 4 | Igor Stravinsky (Q7314) → 5f69b1b6-643e-423f-a4f2-4a67411d2357 |
Example 5 | Srinagarindra, Princess Mother (Q449433) → 05c4bd56-4d3d-4a9d-af92-be912d98dd41 |
Allowed units | human (Q5) |
Source | https://lux.collections.yale.edu/ |
Planned use | adding to newly created lexemes or lexemes being edited or to new items or items being edited |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://lux.collections.yale.edu/view/person/$1 |
Applicable "stated in"-value | LUX (Q133612457) |
Type constraint – instance of | human (Q5) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editYale University's LUX (Q133612457) is a "platform that provides access to millions of records for objects, people, places, concepts, and events represented in Yale’s rich cultural heritage collections." The collections that are brought together are Yale University Library, Yale Center for British Art, Yale Peabody Museum, Yale University Art Gallery, Paul Mellon Centre (UK), Collection of Musical Instruments, Lens Media Lab, Campus Art Collection, and Elizabethan Club of Yale University. Entities include 5,683,846 people and groups, 577,020 places, 13,078,404 works, 17,482,648 objects, 312,240 collections, 158,014 events, and 4,679,830 concepts. AdamSeattle (talk) 23:38, 28 March 2025 (UTC)
Discussion
edit- Support--Trade (talk) 19:15, 30 March 2025 (UTC)
- Support--Emwille (talk) 13:06, 1 April 2025 (UTC)
- Support--Thisismattmiller (talk) 16:41, 1 April 2025 (UTC)
- Support -- Riesengrey (talk) 22:08, 2 April 2025 (UTC)
- Support -- Kkdavis14 (talk) 14:38, 4 April 2025 (UTC)
- Oppose as per Azaroth42 --Vladimir Alexiev (talk) 05:42, 22 April 2025 (UTC)
- Please instead support the proposal for a single LUX identifier property: Wikidata:Property_proposal/Yale_LUX_ID rather than embedding the class name into the property. This would require properties for each of physical object, digital object, image, text, audio, person, group, place, set, concept, and activity. Azaroth42 (talk) 16:37, 4 April 2025 (UTC)
Identifiant d'un(e) auteurice dans le catalogue de la bibliothèque du Saulchoir (fr) – (Please translate this into English.)
editDescription | Saulchoir library author id |
---|---|
Represents | bibliothèque du Saulchoir(2901417) |
Data type | External identifier |
Domain | être humain(5) |
Example 1 | Siméon Vailhé(17000442) → 146148 |
Example 2 | Olivier Clément(2501324) → 38145 |
Example 3 | Hervé Legrand(16266522) → 90114 |
Formatter URL | https://catalogue.bibliothequedusaulchoir.org/cgi-bin/koha/opac-search.pl?q=an:$1 |
Motivation
editDiscussion
editNotified participants of WikiProject France. Maxime 10:20, 3 April 2025 (UTC)
- Notified participants of WikiProject Religions. Maxime 10:20, 3 April 2025 (UTC)
- This is a Koha catalog, but they hid the access to the authority search page. So, please, if you agree, rewrite the proposal, but base it on https://catalogue.bibliothequedusaulchoir.org/cgi-bin/koha/opac-authorities-home.pl?op=do_search&type=opac&authtypecode=NP&operator=contains&value=&marclist=all&and_or=and&excluding=&orderby=HeadingAsc. Anyway, first of all verify the quality of the authority records. Bargioni 🗣 13:50, 3 April 2025 (UTC)
- Seems like a good idea but what should it be called in English?StarTrekker (talk) 12:24, 3 April 2025 (UTC)
- Support, but only on the condition that the authority records are re-verified, as @Bargioni pointed out. — Baidax 💬 11:46, 18 April 2025 (UTC)
National Library of Spain Alma ID (BNE v2.0)
editMotivation
editThe National Library of Spain appears to previously have used the library catalog system Symphony from SirsiDynix which issued a control number that for persons began with the prefix XX and then was followed by 4 to 7 numbers. This number is National Library of Spain SpMaBN ID (BNE v1.0) (P950). Recently, they appear to have moved to a new library catalog system called Alma/Primo from Ex Libris. They posted an announcement regarding a catalog change in January. The new system is using an 18 digit all-digit number. The old number, which formerly was coded as "BNE" in VIAF, is now coded as "SpMaBN". This new 18 digit number is now coded in VIAF as "BNE". See Example 1 VIAF, Example 2 VIAF, Example 3 VIAF. I propose we also include this new control number as we do the old control number. --Chchowmein (talk) 07:04, 10 May 2025 (UTC); edited 05:29, 11 May 2025 (UTC)
Discussion
edit- Comment this seems a good description of the situation (an addition: not only authority records but also subject headings have been converted into Alma, I have added an example); I have just one clarification to ask before supporting: do we have ready a way to massively add the new ID converting the 290k values of old National Library of Spain SpMaBN ID (BNE v1.0) (P950) we have? Doing it consulting VIAF, given the absence of VIAF dumps and the monthly limit of 10k connections to VIAF, is not feasible; so is there a dump of BNE containing all the old and the new IDs? --Epìdosis 08:00, 10 May 2025 (UTC)
- In general, maintaining two IDs at the same time is challenging, so I hesitate creating a new ID in these cases: the conversion seems to be still ongoing, the old ID is the only way to access datos.bne.es and the new ID is the only way to access Alma, but probably in the future it will be possible to access both using one of the two IDs. Considering the instability of the situation, I think we should wait creating this property and try to coordinate with BNE as much as possible to understand if the new Alma ID will become the standard one or, as in the case of NUKAT (NUKAT ID (P1207)), despite the change of ILS the old ID will be kept as the standard and stable one. @Bargioni: is trying to have updates from BNE. Epìdosis 14:07, 14 May 2025 (UTC)
- That seems prudent, I just assumed a new ID would be easiest to facilitate the migration (and prevent edits from mixing in the new number to the old ID). To your question about the BNE dataset, I don't know the answer and was hoping someone else with more familiarity would chime in. But, I mentioned this at WikiProject Authority Control, this authority record download page from BNE provides their latest release as a dataset that begins with three column names:
id|id_symphony|otros_identificadores|
– notably (from a quick skim) it seems all entries have a new 18 digit number in the id column; the occasional entry has the old XX-prefixed code in the second column as" XX#######"
(with a leading space) but this appears rare unfortunately. I'll echo the suggestion we look for a source that has both. Chchowmein (talk) 23:01, 14 May 2025 (UTC)
- That seems prudent, I just assumed a new ID would be easiest to facilitate the migration (and prevent edits from mixing in the new number to the old ID). To your question about the BNE dataset, I don't know the answer and was hoping someone else with more familiarity would chime in. But, I mentioned this at WikiProject Authority Control, this authority record download page from BNE provides their latest release as a dataset that begins with three column names:
- In general, maintaining two IDs at the same time is challenging, so I hesitate creating a new ID in these cases: the conversion seems to be still ongoing, the old ID is the only way to access datos.bne.es and the new ID is the only way to access Alma, but probably in the future it will be possible to access both using one of the two IDs. Considering the instability of the situation, I think we should wait creating this property and try to coordinate with BNE as much as possible to understand if the new Alma ID will become the standard one or, as in the case of NUKAT (NUKAT ID (P1207)), despite the change of ILS the old ID will be kept as the standard and stable one. @Bargioni: is trying to have updates from BNE. Epìdosis 14:07, 14 May 2025 (UTC)
- All but one of the examples is for a person. Are other agents also covered by this? What about genre/form headings in addition to subjects? AdamSeattle (talk) 02:01, 13 May 2025 (UTC)
- In the Authority Search search box dropdown (when English is chosen in the UI) they list: Keyword (all fields), Personal Name, Corporate Name, Meeting Name, Name, Subject, Geographic Term, Genre/Form Term, and Uniform Title. I added the record for science fiction (Q24925) as an example. Chchowmein (talk) 04:32, 13 May 2025 (UTC)
Law
editRegister
editRAN code
editDescription | identifier of elements of the National archaeological register of Moldova |
---|---|
Represents | RAN ID (Q124828245) |
Data type | String |
Domain | Archaeological National Register (Q124828308) |
Allowed values | \d{3,4}(\/\d{3,4})?\.S?\d{1,3} (regex) |
Example 1 | Bălți IRAN ID300.1 |
Example 2 | Zăzuleni Tumulul 1RAN ID6943.2 |
Example 3 | Valul lui Traian de Jos, Sectorul II – Vulcănești, Găvănoasa, Alexanderfeld, Iujnoe, BurlăceniRAN ID1700/9600.S2 |
Source | annex of the applicable Moldovan law (Word document; see archived) |
Planned use | generating the list of archaeological locations of Moldova on Wikidata and then on Wikipedia |
Number of IDs in source | 11,156 |
Expected completeness | eventually complete (Q21873974) |
See also | Wikidata:Property proposal/RAN-ID |
Single-value constraint | yes |
Motivation
editArchaeological National Register (Q124828308) (RAN) is Moldova's recently approved registry of archaeological locations, superseding the sublist of archaeological locations from Q108443136 (on Wikidata the latter are tagged with instance of (P31)former archaeological monument of Moldova (as previously defined in the Registry of state protected monuments) (Q106378344)).
All items in RAN are uniquely identified using an ID. The ID (e.g. 1700/9600.S2
) is comprised of:
- the CUATM unique code (CUATM unique identification code (P13182)) of the city/village the archaeological location is located in – e.g.
1700
(note that if P13182 starts with 0, the first digit is disregarded in RAN)- in some cases, the unique code of another city/village, separated from the first by a forward slash – e.g.
/9600
- in some cases, the unique code of another city/village, separated from the first by a forward slash – e.g.
- a dot –
.
- if item is a so-called "sector", the capital letter S –
S
- if item is a so-called "sector", the capital letter S –
- a simple count that starts at 1, to disambiguate multiple archaeological location in the same city/village – e.g.
2
The name of this ID eventually needs to be properly disambiguated from RAN ID (P2845), a similar kind of identifier from neighboring Romania. Pinging @Strainu who had worked on that ID.
Thanks! Gikü (talk) 17:07, 17 December 2024 (UTC)
Discussion
edit- Notified participants of WikiProject Archaeology. Samoasambia ✎ 04:44, 27 December 2024 (UTC)
- Could the property name include the word Moldovan, else it could be used for other countries. Vicarage (talk) 17:16, 6 January 2025 (UTC)
- Conditional support I do support the creation of the property. But I do suggest changing the name from RAN code to RAN ID (Moldova) or RAN ID (MDA) to disambiguate it from RAN IDs from other countries. Conversely, I suggest changing the name for the existing RAN ID (P2845) to 'RAND ID (ROU)' @Strainu. Mtrognitz (talk) 10:17, 28 January 2025 (UTC)
- Oppose Hello Gikü This seems interesting, but I don't understand something. I do not understand anything about the source: one link does not seem to provide the examples precisely and the second link (archive) seems empty. In this case, how to fill items from an external source to WD? In the examples, the codes must be linked to something, both in a source and in WD; if nothing is linked, this proposition cannot be a property. What is "Bălți I" for example? What is "2897–2904, 2906, 2907, 2910– 2916, 2919–2925"? Where can I see these sectors? What and how are these terms linked? The regex is understandable without adding the term "(regex)", but I do not see how to approve this regex without a complete external list of codes linked to tangible things. I don't want to look for those 11156 IDs, I prefer to see those IDs in front of me. Cordially. —Eihel (talk) 12:37, 10 February 2025 (UTC)
- Hi Eihel, thanks for your input!
- In the provided link to the law, do you see a text all the way at the end "anexa"? If you click on it, does it download a DOCX file for you? That file contains the table of codes; I have converted it in a CSV for myself, intending to prepare for an OpenRefine effort.
- Didn't understand your point about linking... do you mean the items are not available on Wikidata? If so, like I mentioned in the request my plan is to create the items and populate the new property in them from the get-go. If that's not allowed, I can create the items first and then add the property. Gikü (talk) 15:03, 10 February 2025 (UTC)
Social networking service
editMagazine
editHarper's tag
editDescription | Tag in Harper's Magazine (Q1170076). |
---|---|
Data type | External identifier |
Domain | external-id |
Allowed values | [a-zA-Z\-]+ |
Example 1 | United States (Q30)→united-states |
Example 2 | democracy (Q7174)→democracy |
Example 3 | Max Weber (Q9387)→max-weber |
Example 4 | racism (Q8461)→racism |
Example 5 | Protestantism (Q23540)→protestantism |
Example 6 | globalization (Q7181)→globalization |
Example 7 | Donald Trump (Q22686)→donald-trump |
Example 8 | capitalism (Q6206)→capitalism |
Source | https://harpers.org |
Planned use | Adding identifiers to Wikidata items for individuals, publications and events with tags in Harper's Magazine (Q1170076). |
Number of IDs in source | Unknown |
Expected completeness | always incomplete (Q21873886) |
Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
Formatter URL | https://harpers.org/tag/$1/ |
See also | Harper's author ID (P6784) |
Motivation
editHarper's Magazine (Q1170076) is one of the oldest continuously published magazines in the United States. It contains discussions of many different topics that were written by various journalists, writers and intellectuals of note. A property for its tags would compliment the one that relates to its authors. Susmuffin (talk) 20:56, 7 May 2025 (UTC)
Discussion
editWikiProject Authority control has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. This proposal might be of interest to you. Susmuffin (talk) 20:56, 7 May 2025 (UTC)
Authority file
editStorytel author ID
editDescription | identifier of an author or narrator on the Storytel website |
---|---|
Represents | Storytel (Q10681448) |
Data type | External identifier |
Domain | human (Q5) |
Allowed values | [1-9]\d{1,6} |
Example 1 | James Joyce (Q6882) → 4012 |
Example 2 | Charles Dickens (Q5686) → 141 |
Example 3 | Roberto Saviano (Q25163) → 5459 |
Example 4 | Zerocalcare (Q4024265) → 329948 |
Example 5 | Valerio Nicolosi (Q131915333) → 705783 |
Example 6 | Nicolás Reydel (Q29048311) → 394247 |
Example 7 | Francesco Pannofino (Q808664) → 73144 |
Example 8 | Simon Vance (Q66572596) → 139 |
Example 9 | Christopher Gebauer (Q131915418) → 13801 |
Example 10 | Francesco Acquaroli (Q14041613) → 121105 |
Example 11 | Neri Marcorè (Q3338344) → 92920 |
Source | https://www.storytel.com/se/authors, https://www.storytel.com/se/narrators |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.storytel.com/se/authors/-$1 |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | WikiProject Books (Q8487081) |
Motivation
editGood resource for audiobooks. The website uses the same identifier for authors and narrators (example: [1] and [2]). --Horcrux (talk) 19:57, 26 January 2025 (UTC)
Discussion
edit- Question If it's just for the authors, why add the narrators in the sources? —Eihel (talk) 13:27, 10 February 2025 (UTC)
- @Eihel: It's not just for the authors: as said above, "The website uses the same identifier for authors and narrators" ;-) --Horcrux (talk) 14:41, 10 February 2025 (UTC)
- @Horcrux: Ok, but there are narrators who do not have any work of their own, so they have no place in this property proposition. Example: Audrey d'Hulstère has no works by her pen. See example 6 : https://www.storytel.com/authors/-394247 does not work too. Otherwise the property must be renamed, the formatter URL (P1630) and the regex must be replaced. Also, the links do not work without a language indication in the URL. Cordially. —Eihel (talk) 15:38, 10 February 2025 (UTC)
- @Eihel: URL https://www.storytel.com/authors/-394247 works for me (but maybe it's just guessing my language through the IP I'm connecting with), but I have no problem in specifying a language tag in it. For what concerns the label, my initial thought was to use "author" for the label and "narrator" as alias, but maybe it could be a better solution to name the property "Storytel author or narrator ID". Finally, I don't see any problem in having one default formatter URL and a secondary one, as long as the ID is recognized under both the URLs (i.e. it shows the person's name in both cases). --Horcrux (talk) 17:59, 10 February 2025 (UTC)
- and what do you get as URL after the page is displayed, @Horcrux: ? And most importantly, what is the content of the page? —Eihel (talk) 19:26, 10 February 2025 (UTC)
- @Eihel: I'm redirected to https://www.storytel.com/it/authors/nicolas-riedel-394247. I see the name "Nicolas Riedel" (so he's recognized) but no associated work. --Horcrux (talk) 19:37, 10 February 2025 (UTC)
- and what do you get as URL after the page is displayed, @Horcrux: ? And most importantly, what is the content of the page? —Eihel (talk) 19:26, 10 February 2025 (UTC)
- @Eihel: URL https://www.storytel.com/authors/-394247 works for me (but maybe it's just guessing my language through the IP I'm connecting with), but I have no problem in specifying a language tag in it. For what concerns the label, my initial thought was to use "author" for the label and "narrator" as alias, but maybe it could be a better solution to name the property "Storytel author or narrator ID". Finally, I don't see any problem in having one default formatter URL and a secondary one, as long as the ID is recognized under both the URLs (i.e. it shows the person's name in both cases). --Horcrux (talk) 17:59, 10 February 2025 (UTC)
- @Horcrux: Ok, but there are narrators who do not have any work of their own, so they have no place in this property proposition. Example: Audrey d'Hulstère has no works by her pen. See example 6 : https://www.storytel.com/authors/-394247 does not work too. Otherwise the property must be renamed, the formatter URL (P1630) and the regex must be replaced. Also, the links do not work without a language indication in the URL. Cordially. —Eihel (talk) 15:38, 10 February 2025 (UTC)
- @Eihel: It's not just for the authors: as said above, "The website uses the same identifier for authors and narrators" ;-) --Horcrux (talk) 14:41, 10 February 2025 (UTC)
- Strong oppose @Horcrux: There is a cookie that allows you to get to the Italian page (
storytel.com/it/authors
), but the link to the proposal does not exist. When you arrive, you must first choose one of the 26 available countries. Once the country is chosen, the destination URL disappears for the home page. And once again, narrators who are not writers have an empty author page, like those mentioned before (Audrey d'Hulstère or Nicolas Riedel); only the narrator pages are filled, https://www.storytel.com/it/narrators/nicolas-riedel-394247. So, as I said, the link from the source to the narrators is not useful: you have to- change this proposal or
- correct the proposal or
- make another proposal only for the narrators. Cordially. —Eihel (talk) 20:20, 10 February 2025 (UTC)
- @Eihel:
Unfortunately I still can't see the country problem because, I think, accessing the website from Italy I don't have any possibility of changing country/language (I guess for copyright reasons).[I just trued with the "en" tag, which apparently doesn't exist, but other tags (like "in", "es", etc.) work indeed. Anyway, apparently, still I don't see any way of changing country/language without manually editing the URL.] I also tried the private mode or accessing via other browsers, so my problem are not cookies. Anyway, I set all the URLs to English, so I hope we're happy on this side.- Regarding the other point raised: this property stores IDs, not URLs. Having two properties would just be redundant, as the website uses the same ID for both authors and narrators (whether it provides or not useful information in some cases is secondary to me). If you want to add some further metadata, you could suggest using some qualifiers (e.g. applies to people (P6001)). --Horcrux (talk) 09:33, 11 February 2025 (UTC)
- Hello Horcrux I replaced the links with the Swedish language, because the site was created in Sweden. The only English-speaking country is for the Indian page (https://www.storytel.com/in).
- For the second problem, if you don't want to make a second property, fine, the problem is still the same. The best fix would be to include the languages in the URL formatter, because authors and narrators are only in certain languages. So there is only one possibility left, narrators are taken into account:
- en label = Storytel author and narrator ID
- desc en = identifier of an author or narrator on the Storytel site according to the language
- same thing for other languages
- allowed values = (be|br|bg|co|dk|eg|fi|fr|de|id|il|in|is|it|mx|nl|no|pl|sa|sg|kr|es|se|th|tr|ae)\/(authors|narrators)\/[1-9]\d{1,6}
- formatter URL = https://www.storytel.com/$1
- single value constraint = no
- source parameter identical to what is currently there by changing the language
- If a site offers blank pages, Wikidata is not intended to recover bad IDs from poorly made sites. Cordially. —Eihel (talk) 22:31, 12 February 2025 (UTC)
Rekhta Gujarati Author ID
editDescription | identifier for an author, in the Rekhta Gujarati database of literature of the Gujarati language of India |
---|---|
Data type | External identifier |
Domain | human (Q5), publisher (Q2085381) |
Allowed values | [a-z1-9\-]+ |
Example 1 | Anil Joshi (Q2722277) → anil-joshi |
Example 2 | Akha Bhagat (Q2721893) → akho |
Example 3 | Ichharam Desai (Q2724598) → ichchharam-suryaram-desai |
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]. |
Planned use | Adding ID to as many Gujarati writer articles as possible especially on Gujarati Wikipedia and Gujarati Wikisource. Contacting Rekhta Gujarati and requesting them to release their ID list in Public Domain |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://www.rekhtagujarati.org/poets/$1 |
See also | Rekhta author ID (P9459), Rekhta book ID (P10520) |
Motivation
editThey are very limited identifiers to connect writers and books of Indian literature. This ID will help All Indic-language Wikipedia and Gujarati writer articles to connect Rekhta Gujarati IDs. If Rekhta Gujarati agrees and releases their database in PD, we may receive additional information like Biographies and list of works etc to populate on Wikidata.- – The preceding unsigned comment was added by Nizil Shah (talk • contribs) at 03:21, March 26, 2025 (UTC).
Discussion
editOpen Location Code
editDescription | A code representing a location using the Open Location Code system |
---|---|
Represents | Open Location Code (Q23582265) |
Data type | External identifier |
Template parameter | plus_code |
Domain | item, Q618123 |
Allowed values | [23456789CFGHJMPQRVWX]{4,6}\+[23456789CFGHJMPQRVWX]{2,3} |
Example 1 | Berlin (Q64)plus codeF6WR+VC |
Example 2 | Googleplex (Q694178)plus code8FVC9G8F+6W |
Example 3 | Louvre Museum (Q19675)plus codeV86P+C8 |
Source | https://plus.codes |
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]. |
Planned use | Add Plus codes to many buildings in SC, as well as importing Plus Codes for places lacking street addresses (e.g. rural areas) |
Number of IDs in source | global coverage |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://plus.codes/$1 |
Wikidata project | Open Location Code (Q23582265) |
Motivation
editCan be used for many locations without addresses.
Discussion
edit- Oppose per previous proposals Wikidata:Property proposal/Plus codes and Wikidata:Property proposal/Google Plus code. Mahir256 (talk) 18:49, 8 May 2025 (UTC)
- This is pretty much just a coordinate system, identifying an area on Earth, not identifying anything that would have a Wikidata item. The location/business details are just the closest nearby on Google Maps. coordinate location (P625) and related properties would work just fine for the given motivation. -wd-Ryan (Talk/Edits) 17:05, 9 May 2025 (UTC)
CvLAC ID
editDescription | Identifier for a person in the Curriculum Vitae of Latinamerica and the Carribean |
---|---|
Data type | External identifier |
Domain | property |
Example 1 | Manuel Elkin Patarroyo Murillo (Q977933) → 0000267619 |
Example 2 | Ana María Groot (Q21480681) → 0000247065 |
Example 3 | Dolly Montoya Castaño (Q50846002) → 0000067474 |
Source | https://scienti.minciencias.gov.co/ciencia-war/index.jsp |
Expected completeness | always incomplete (Q21873886) |
Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
Formatter URL | https://scienti.minciencias.gov.co/cvlac/visualizador/generarCurriculoCv.do?cod_rh=$1 |
Motivation
editA unique identifier (Q6545185) for human (Q5) with occupation (P106) related to scientist (Q901), researcher (Q1650915) and alike in Latin America and the Caribbean (Q72829598) administred by Ministry of Science, Technology and Innovation (Q4683466). As mentioned in the template, it is a Wikidata property for an identifier that suggests notability (Q62589316). Thanks --Sahaquiel9102 (talk) 18:14, 10 April 2025 (UTC)
Discussion
edit- I assume just the ending number portion of the value is what you are proposing for the ID? Can you fix up the examples? ArthurPSmith (talk) 17:18, 21 April 2025 (UTC)
- Hi @ArthurPSmith:. Thanks for your help. Yes, the ending number portion of the value is what I'm proposing for the ID. I'm sorry, but I don't understand what do you mean with fixing up the examples. I followed some other proposals to fill up the template as I was a lil' confused. I guess for me it is still not clear how to fill up correctly the template, sorry. --Sahaquiel9102 (talk) 05:26, 23 April 2025 (UTC)
- @Sahaquiel9102: I've adjusted them so only the number is showing for the ID now. ArthurPSmith (talk) 20:34, 23 April 2025 (UTC)
Jesuit Online Necrology ID
editDescription | identifier for a Jesuit in the Jesuit Online Necrology |
---|---|
Data type | External identifier |
Example 1 | Clemens Bleses (Q134374811) -> 92456 |
Example 2 | Luis Sodiro (Q3266829) -> 43670 |
Example 3 | Marcel Bouix (Q16775650) -> 29300 |
Formatter URL | https://jesuitonlinenecrology.bc.edu/catalog/$1 |
Motivation
editNotified participants of WikiProject Religions great source for our coverage of Jesuits. --Epìdosis 16:23, 6 May 2025 (UTC)
- + Mix'n'match catalogue ready for upload once the property is created. Epìdosis 17:32, 6 May 2025 (UTC)
Discussion
edit- Support -- Bargioni 🗣 17:32, 6 May 2025 (UTC)
- Support I don't see why not. Amqui (talk) 21:16, 6 May 2025 (UTC)
- Support Seems great.StarTrekker (talk) 12:13, 8 May 2025 (UTC)
- See also wikidata:property proposal/Pending for approved items awaiting the deployment of currently unavailable datatypes
- Already approved properties: list
ConLang Code Registry code
editDescription | 3-letter identifier for language defined in the ConLang Code Registry, using codes reserved for private use in ISO 639-3 |
---|---|
Represents | ConLang Code Registry (Q107713633) |
Data type | String |
Domain | languages |
Example 1 | Black Speech (Q686210) → qbs |
Example 2 | Ithkuil (Q35846) → qit |
Example 3 | Idiom Neutral (Q35847) → qin |
Source | https://www.kreativekorp.com/clcr/ |
Planned use | assign value to relevant languages |
Number of IDs in source | 255 |
Expected completeness | eventually complete (Q21873974) |
Robot and gadget jobs | Not that I know of |
Motivation
editCurrently, many conlangs (constructed languages) that don't have official ISO 639-3 codes have an ISO 639-3 code (P220) value listed anyway, for a code issued by the ConLang Code Registry; they generally take the format Black Speech (Q686210)ISO 639-3 code (P220)qbsqaa
-qtz
as "reserved for private use", which means that anyone can use them for any purpose, and still be compliant with the standard. The fact that the ConLang Code Registry has issued codes in this range does not mean that these conlangs have actually received ISO 639-3 codes, though; it just means that a completely separate organisation has decided to issue codes which just-so-happen to be in ISO 639-3's private use range.
This is obviously intentional, as it allows them to be used as language codes without conflicting with the official ISO standard, but that doesn't mean we should have statements which claim they're actually part of the standard. Simply saying that the code is "issued by the ConLang Code Registry" doesn't make it clear that the ConLang Code Registry is not entitled to issue ISO 639-3 codes, and therefore obscures the fact that the code isn't actually part of the standard in the first place (i.e. that the statement is wrong). Outside of conlang communities, these codes see almost no use, and they may conflict other privately-issued codes used in other communities.
To get around the issue, I'd like to propose a separate property for the ConLang Code Registry, so that these codes can be listed without polluting the data for those who only want information on official ISO 639-3 codes. – The preceding unsigned comment was added by Theknightwho (talk • contribs) at 12:47, August 16, 2024 (UTC).
Discussion
edit- Support This makes sense to me. Are there really 255 of these? ArthurPSmith (talk) 19:24, 16 August 2024 (UTC)
- @ArthurPSmith Yes - 252 active codes and 3 retired ones according to https://www.kreativekorp.com/clcr/. There are 520 codes in the private use range (
qaa
-qtz
), which is the theoretical maximum, and growth is quite uneven, with some years seeing very few codes added (2 added in 2021), while others see many (32 added in 2023). Codes are retired if they're replaced by genuine ISO 639-3 codes. Theknightwho (talk) 21:18, 16 August 2024 (UTC)
- @ArthurPSmith Yes - 252 active codes and 3 retired ones according to https://www.kreativekorp.com/clcr/. There are 520 codes in the private use range (
- Support --Lewis Hulbert (talk) 11:16, 19 August 2024 (UTC)
- Oppose I don't think this would be a good idea.
It's not a coincidence that the ConLang Code Registry (CLCR) codes are in ISO 639-3's private-use range, the whole point is that they are private-use ISO 639-3 codes for use as ISO 639-3 codes.
ISO 639-3 provides the set of private-use codes for people to use how they want, which means that users assign their own meanings. It's true that other places may assign conflicting meanings, but that's why those statements all have a qualifier saying who gives it that meaning. Conflicts shouldn't be a problem either, we can use constraints like single-best-value constraint (Q52060874) and/or add separator (P4155) to the constraint.
The existing statements shouldn't pollute the data if you're using it correctly. The items with private-use codes also have a no value statement set to preferred rank to indicate that they have no official code, and if you're looking at all statements, you need to take ranks and qualifiers into account for the data to be meaningful anyway.
The real issue here is: How should we model usage of private-use codes? This isn't limited to CLCR or even ISO 639-3 (e.g. XK is widely used as the ISO 3166-1 code for Kosovo, Qaag is used by Unicode and CLDR as the ISO 15924 code for Zawgyi, U+F8D0 is the Unicode codepoint normally used for the Klingon letter "a"), so I don't think it makes sense to have a property specifically for CLCR's private-use ISO 639-3 codes. We should have a model we can apply to private-use codes in general instead.
- Nikki (talk) 09:23, 28 August 2024 (UTC)- @Nikki These are not ISO 639 codes, though - these are codes assigned by another body which have been intentionally designed to match up with ISO 639's private use range. It's not a question of qualifying the codes or setting no value as a preferred rank - it's the fact that it is factually wrong to say that they are ISO 639 codes at all, and they shouldn't be listed there at all. Theknightwho (talk) 22:09, 5 September 2024 (UTC)
- @Nikki, any changes in your opinion based on the response? Regards, ZI Jony (Talk) 18:25, 16 September 2024 (UTC)
- @Nikki These are not ISO 639 codes, though - these are codes assigned by another body which have been intentionally designed to match up with ISO 639's private use range. It's not a question of qualifying the codes or setting no value as a preferred rank - it's the fact that it is factually wrong to say that they are ISO 639 codes at all, and they shouldn't be listed there at all. Theknightwho (talk) 22:09, 5 September 2024 (UTC)
- Support - PKM (talk) 23:54, 12 February 2025 (UTC)
- Support -wd-Ryan (Talk/Edits) 17:45, 3 April 2025 (UTC)
- Oppose I think that listing the ConLang codes in the ISO namespace promotes their use and thus interoperability; even though they are not part of the ISO standard. Secondly, if a code is used by ConLang and another organization, we want to know this "conflict", and the best is to see it in the ISO namespace, with qualifiers as shown above --Vladimir Alexiev (talk) 05:48, 22 April 2025 (UTC)
Timenote.info Person ID
editDescription | Identifier for a person profile on the Timenote.info international encyclopedia. |
---|---|
Represents | timenote.info (Q130484179) |
Data type | External identifier |
Template parameter | First, second names, dates of birth and death, etc in en:Template:Infobox person/Wikidata |
Domain | human (Q5), dead human (Q18093576) |
Allowed values | For $1, which is ID = "1-999999999999". For $2, which is a mandatory qualifier language of work or name (P407) of the statement = at this point only supported values are ISO 639-1 of these languages: en, de, lt, lv, fr, pl, he, ua, ee, ru. |
Example 1 | Georgiy Pavlovich Osipov (Q130516824) + language of work or name (P407)=Russian (Q7737) → */ru/person/view?id=11797405 |
Example 2 | Georgiy Pavlovich Osipov (Q130516824) + language of work or name (P407)=English (Q1860) → */en/person/view?id=11797405 |
Example 3 | Q130470636 + language of work or name (P407)=Russian (Q7737) → */ru/person/view?id=11797406 |
Example 4 | Q130470636 + language of work or name (P407)=English (Q1860) → */en/person/view?id=11797406 |
Source | https://timenote.info/ |
Planned use | I plan to add this property to at least 4 Wikidata items that have corresponding profiles on Timenote.info within the next month. |
Number of IDs in source | Unknown |
Expected completeness | always incomplete (Q21873886) |
Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
Formatter URL | https://timenote.info/$2/person/view?id=$1 |
URL match pattern | ^https?:\/\/timenote\.info\/(?:[a-z]{2})\/person\/view\?id=(\d+)$ |
Robot and gadget jobs | While it's possible that bots or gadgets could be developed in the future to import or check data related to this property, that's not a guarantee. It's best not to overpromise functionality that doesn't yet exist. |
See also | BillionGraves grave ID (P10554), Find a Grave memorial ID (P535), genealogics.org person ID (P1819), FamilySearch person ID (P2889), GeneaStar person ID (P8094), Geni.com profile ID (P2600), WikiTree person ID (P2949), The Peerage person ID (P4638) |
Applicable "stated in"-value | timenote.info (Q130484179) |
Type constraint – instance of | human (Q5), dead human (Q18093576) |
Type constraint – subclass of | human (Q5) |
Distinct-values constraint | yes |
Wikidata project | WikiProject Genealogy (Q19817878) |
Proposed by | David Osipov |
Motivation
editTimenote.info is a free, international, multilingual encyclopedia of people, places, and events. It allows anyone to create and contribute information about individuals, including biographical details, family connections, related locations, and associated events. This property links Wikidata items to corresponding person profiles on Timenote.info, facilitating the exchange of information and enhancing the discoverability of biographical data. Because Timenote.info is multilingual, the language of work or name (P407) qualifier is mandatory to specify the language version of the profile. --David Osipov (talk) 14:07, 26 October 2024 (UTC)
Discussion
edit- Comment Do you have any examples that aren't your family members (that you presumably added to the website)? William Graham (talk) 14:31, 26 October 2024 (UTC)
- Comment Sure.
- Yuri Nikulin (Q310873) -> https://timenote.info/ru/person/view?id=151 and https://timenote.info/lv/person/view?id=151
- Joseph Stalin (Q855) -> https://timenote.info/en/person/view?id=26089 , https://timenote.info/de/person/view?id=26089 , https://timenote.info/ua/person/view?id=26089
- Frank Sinatra (Q40912) -> https://timenote.info/en/person/view?id=23988 , https://timenote.info/de/person/view?id=23988 David Osipov (talk) 15:29, 26 October 2024 (UTC)
- Comment Wikidata's UI can't handle a "$2". You may want to make this two (or more?) proposals. ArthurPSmith (talk) 00:39, 27 October 2024 (UTC)
- I guess it would not be really efficient. Where can I file for a feature request? David Osipov (talk) 05:56, 27 October 2024 (UTC)
- Since they are multiple formatters (per language) for same ID, we only need one property. Multiple formatters can be handled like Property:P7704#P1630. GZWDer (talk) 12:03, 27 October 2024 (UTC)
- Oooo, I see, it solves the problem! Should I do anything like adjusting the proposal? Thank you for your input. David Osipov (talk) 12:44, 27 October 2024 (UTC)
- Wait what? We already use "$2" for Fandom articles Trade (talk) 18:00, 20 January 2025 (UTC)
- Since they are multiple formatters (per language) for same ID, we only need one property. Multiple formatters can be handled like Property:P7704#P1630. GZWDer (talk) 12:03, 27 October 2024 (UTC)
- I guess it would not be really efficient. Where can I file for a feature request? David Osipov (talk) 05:56, 27 October 2024 (UTC)
University of Neuchâtel thesis number
editDescription | numeric identifier of a doctoral thesis at University of Neuchâtel, Switzerland. Theses are numbered sequentially since 1910, with #1000 in 1987, #2000 in 2008, #3000 in 2022. |
---|---|
Data type | External identifier |
Domain | doctoral thesis (Q187685) of University of Neuchâtel (Q541548) |
Allowed values | [1-9]\d* |
Example 1 | Q131695534 : 3146 |
Example 2 | Q131697574 : 3000 |
Example 3 | Q131697527 : 2000 |
Example 4 | Q130350124 : 1438 |
Source | unine.ch, Libra (Q117216160) |
Number of IDs in source | 3146 (per end of 2024) |
Country | Switzerland (Q39) |
See also | Theses.fr person ID (P4285), Dialnet thesis ID (P9553), DUMAS thesis ID (P11983), Cerist ID (P12669), theses.cz ID (P8937), RHE doctor ID (P5459), LIBRA Unine ID (P11710) |
Type constraint – instance of | doctoral thesis (Q187685) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editThis number is a good way to identify these theses, independently of the way of publication. Doctoral theses are numbered sequentially across all disciplines since 1910. This is the primary way to identify them. There is no "national" thesis database.
Libra (Q117216160) includes copies of some of the recent ones and provides an identifier for maybe 50% of the authors, but the DOI mentioned there aren't valid. See DOI:10.35662/unine-thesis-1438 for sample #4 above.
A current list of theses is available at unine.ch. – The preceding unsigned comment was added by E2.7182818284590 (talk • contribs) at 16:30, 11 January 2025 (UTC).
Discussion
edit- See my proposal above e 16:32, 11 January 2025 (UTC)
- Comment This property proposal came from a user that has been blocked indefinitely. I will mark this proposal as cancelled if no one wants to adopt it. Samoasambia ✎ 21:40, 29 January 2025 (UTC)
ROAR ID
editDescription | numeric identifier for an entry in the Registry of Open Access Repositories (ROAR) |
---|---|
Represents | Registry of Open Access Repositories (Q861552) |
Data type | External identifier |
Domain | open-access repository (Q7096323) |
Allowed values | [1-9]\d* |
Example 1 | ZHAW digitalcollection (Q131746575): 11577 |
Example 2 | RERO DOC (Q131746648): 8789 |
Example 3 | Serval (Q131742253): 3094 |
Number of IDs in source | >10000 |
Formatter URL | https://roar.eprints.org/$1/ |
See also | OpenDOAR ID (P5332), re3data repository ID (P5874), OpenAlex ID (P10283) |
Applicable "stated in"-value | Registry of Open Access Repositories (Q861552) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editHas some interesting things even it may date a bit and some entries might not be that complete (check the tabs).
This should complete other properties in the field, such as OpenDOAR ID (P5332), or the excellent, but underused re3data repository ID (P5874).
Discussion
edit- See my proposal above e 13:15, 13 January 2025 (UTC)
- Support Sure. ArthurPSmith (talk) 18:27, 13 January 2025 (UTC)
AGORHA UUID
editDescription | item ID in the AGORHA database (INHA) |
---|---|
Data type | External identifier |
Domain | art history (Q50637) |
Allowed values | [0-9A-Z]{8}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{12} |
Example 1 | person Nicolas Poussin (Q41554) https://agorha.inha.fr/ark:/54721/3cf92a4e-d654-464d-a0b1-2fcf704b423a |
Example 2 | institution National Gallery (Q180788) https://agorha.inha.fr/ark:/54721/a2d2d69b-fbcd-417b-adbd-e86495798c53 |
Example 3 | artwork Susannah and the Elders (Q18573218) https://agorha.inha.fr/ark:/54721/0d3acb3e-c350-4461-84a0-8ebef43fb438 |
Example 4 | event Q26833085 https://agorha.inha.fr/ark:/54721/4231f084-fdf9-4dec-b219-6f9546e5c787 |
Source | AGORHA (Q21994367) |
Number of IDs in source | 253 425 (March 6, 2025) |
Expected completeness | expected completeness (Q66364359) |
Formatter URL | https://agorha.inha.fr/ark:/54721/$1 |
See also | AGORHA person/institution ID (P2342), AGORHA work ID (P2344), AGORHA event ID (P2345) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editIn 2021, the AGORHA website had a new version, with a new resource identifier policy. The ancient system was build on domain prefix and ID. Based on this system, 3 properties were created in wikidata : AGORHA person/institution ID (P2342), AGORHA work ID (P2344), AGORHA event ID (P2345). The new system has an unique identifier system (UUID) and this property proposal is to have a unique property in correspondance for all resources items of this database. Shonagon (talk) 00:31, 6 March 2025 (UTC)
Discussion
editNotified participants of WikiProject Visual arts,@Daehan:@Samoasambia:
- Support Shonagon (talk) 00:40, 6 March 2025 (UTC)
- Support — Dcflyer (talk) 13:00, 14 March 2025 (UTC)
- Comment what will happen with the current properties? Do you plan of migrating all the IDs to the new one? --Jahl de Vautban (talk) 08:17, 15 March 2025 (UTC)
- Hello Jahl de Vautban The old properties, corresponding to the previous system, are obsolete and should be indicated as such. Of course, I intend to fill in the new identifier and populate it in wikidata with the new property. It wouldn't be difficult and could be automated. There is currently a redirection system and with CURL commands it is possible to get the new identifier automatically. Best regards Shonagon (talk) 08:24, 21 April 2025 (UTC)
- Support ; I don't think that we should reuse one of the existing property as proposed below. --Jahl de Vautban (talk) 18:07, 1 May 2025 (UTC)
- Hello Jahl de Vautban The old properties, corresponding to the previous system, are obsolete and should be indicated as such. Of course, I intend to fill in the new identifier and populate it in wikidata with the new property. It wouldn't be difficult and could be automated. There is currently a redirection system and with CURL commands it is possible to get the new identifier automatically. Best regards Shonagon (talk) 08:24, 21 April 2025 (UTC)
- Comment I think we could name this as "AGORHA UUID" to differentiate it from the previous properties since the format follows Universally Unique Identifier (Q195284). For example World Rowing rower UUID (P8990) is named like that. Getting the new UUIDs by scraping should be relatively easy. Samoasambia ✎ 08:37, 15 March 2025 (UTC)
- Hello Samoasambia Thanks for the suggestion. UUID as been added. Yes, getting the new UUIDs would be easy. Best regards Shonagon (talk) 08:24, 21 April 2025 (UTC)
- Oppose. Use AGORHA work ID (P2344). Thierry Caro (talk) 21:18, 16 March 2025 (UTC)
- Hello Thierry Caro. As indicated in the name of the property, AGORHA work ID (P2344) is for artworks, not every items. It is not possible to use it for people unless changing the nature of the property. We should not do the same in changing URLs paterns for others properties ; creating a new and unique AGORHA property, corresponding to the new ID INHA policy, is a better choice (no damage to the previousa and historic data ; specific adapted property to the new system). Having a new porperty was already suggested in https://www.wikidata.org/wiki/Property_talk:P2342 and in a previous discusssion of the French pump village (no archive because of Flow). Currently using the AGORHA person/institution ID (P2342) is a mess because the pattern correspond to old IDs, which are not displayed on the websites pages. Some contributors are adding the new ID which can not work or give up to fill them. The issue, which exist since several years, need a solution ; this proposal is to find a clean solution. Best regards Shonagon (talk) 08:24, 21 April 2025 (UTC)
- No. It's uselessly complicated. Just use the property that already exists and works. Thierry Caro (talk) 14:16, 21 April 2025 (UTC)
- No, there is still an issue. This is not the same property for all types of things and the one for artworks. You made alone the changement on the artwork property despite there had been a discussion about the solution, especially about a new property, and what you did doesn't fix the problem for people items. For now there is always an issue and an unique Agohra proprerty should fix it. On the contrary, without tinkering with what already exists, it would be simple, useful and sustainable. Best regards Shonagon (talk) 17:19, 21 April 2025 (UTC)
- No. It's uselessly complicated. Just use the property that already exists and works. Thierry Caro (talk) 14:16, 21 April 2025 (UTC)
- Hello Thierry Caro. As indicated in the name of the property, AGORHA work ID (P2344) is for artworks, not every items. It is not possible to use it for people unless changing the nature of the property. We should not do the same in changing URLs paterns for others properties ; creating a new and unique AGORHA property, corresponding to the new ID INHA policy, is a better choice (no damage to the previousa and historic data ; specific adapted property to the new system). Having a new porperty was already suggested in https://www.wikidata.org/wiki/Property_talk:P2342 and in a previous discusssion of the French pump village (no archive because of Flow). Currently using the AGORHA person/institution ID (P2342) is a mess because the pattern correspond to old IDs, which are not displayed on the websites pages. Some contributors are adding the new ID which can not work or give up to fill them. The issue, which exist since several years, need a solution ; this proposal is to find a clean solution. Best regards Shonagon (talk) 08:24, 21 April 2025 (UTC)
Yale LUX ID
editDescription | identifier for an entity in Yale's LUX cross collection knowledge graph |
---|---|
Data type | External identifier |
Allowed values | ^(object|digital|visual|text|person|group|set|place|concept|event|activity)/([0-9a-f-]+)$ |
Example 1 | Rembrandt (Q5598)LUX IDperson/2107305b-7a4c-4af8-9d02-7a75bb1b2a4e |
Example 2 | paper (Q11472)LUX IDconcept/f9412911-af4c-45c9-86f1-d2dac953dff9 |
Example 3 | Douglas Adams (Q42)LUX IDperson/414e6263-213a-448e-ae18-8efc28d3c663 |
Example 4 | Dort, or Dordrecht: The Dort packet-boat from Rotterdam becalmed (Q22329821)LUX IDobject/047181f4-2fdf-43fd-abbe-f16d7f9edc10 |
Example 5 | Yale University Library (Q2583293)LUX IDgroup/d07b9b86-0a1e-4026-aa4c-8ecba8bbd9c9 |
Example 6 | Mars (Q111)LUX IDplace/a70eb257-9f63-44ec-9e54-8e1d0f47f49d |
Example 7 | 2020 Summer Paralympics (Q14856650)LUX IDactivity/9de9fe2d-8753-4bf8-b772-20eaedc111fc |
Example 8 | World Conference on Women (Q16551855)LUX IDactivity/65cc52ad-6a44-4bae-b243-94eae046d5f8 |
Example 9 | ornamental fern (Q133722383)LUX IDconcept/48ecd3bc-49f2-4e84-a0de-99738b1159b2 |
Example 10 | Lusaka (Q3881)LUX IDplace/8d0cfa1b-85f5-4e18-bda1-4b4e91f8dcfa |
Example 11 | American Society of Plant Biologists (Q4745104)LUX IDgroup/ba2e550f-c1a1-402b-beef-f380c3a887c3 |
Planned use | Will populate with data from LUX in existing Wikidata records |
Number of IDs in source | 42 million |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://lux.collections.yale.edu/data/$1 |
See also | Archives at Yale agent ID (P8902), Yale University Art Gallery ID (P8583), Yale Center for British Art artwork Lido ID (P9789), |
Motivation
editWikidata is a wonderful hub of identifiers for the global knowledge graph. Yale's LUX system (https://lux.collections.yale.edu/) provides enriched data in a standard form for 42 million records, including all of the library, archive and museums at Yale. LUX reconciles with many systems, including wikidata already. We hope that by enabling backlinks from wikidata to LUX, that others will be able to use our CC0 data to improve their own systems.
Azaroth42 (talk) 21:45, 11 March 2025 (UTC)
Discussion
edit- @AdamSeattle, Trade, Emwille, Thisismattmiller, Riesengrey, Kkdavis14: who voted on one of the proposals for more specific IDs and might have an opinion about whether this more general one would be better. Mahir256 (talk) 19:46, 11 April 2025 (UTC)
- I had not noticed this proposal before I started proposing individual properties for each of the LUX classes. I'm not sure whether a single property or separate ones is better. I lean toward separate because they clearly identify the type of entity, but if community consensus is that a single one is better, I'm happy to go along with that. I think this property would be better named as just LUX ID though. AdamSeattle (talk) 19:08, 12 April 2025 (UTC)
- LUX, as with any three letter word, is far from unique, even in the search space. Yale on the other hand are unlikely to make another search system called LUX :)
- As for 1 vs 10, apart from proliferation of properties (a ship that has LONG since sailed here), data management for 10 seems much harder than for 1. Also if entities swap between classes, such as a concept that becomes and event, or a group that is really just a single person. Azaroth42 (talk) 01:02, 8 May 2025 (UTC)
- I had not noticed this proposal before I started proposing individual properties for each of the LUX classes. I'm not sure whether a single property or separate ones is better. I lean toward separate because they clearly identify the type of entity, but if community consensus is that a single one is better, I'm happy to go along with that. I think this property would be better named as just LUX ID though. AdamSeattle (talk) 19:08, 12 April 2025 (UTC)
- Support. "Yale LUX ID" is better because otherwise one would think of Luxembourg. A single prop rather than 10 or so individual props is better --Vladimir Alexiev (talk) 05:44, 22 April 2025 (UTC)
LUX concept ID
editMotivation
editYale University's LUX (Q133612457) is a "platform that provides access to millions of records for objects, people, places, concepts, and events represented in Yale’s rich cultural heritage collections." The collections that are brought together are Yale University Library, Yale Center for British Art, Yale Peabody Museum, Yale University Art Gallery, Paul Mellon Centre (UK), Collection of Musical Instruments, Lens Media Lab, Campus Art Collection, and Elizabethan Club of Yale University. Entities include 5,683,846 people and groups, 577,020 places, 13,078,404 works, 17,482,648 objects, 312,240 collections, 158,014 events, and 4,679,830 concepts. AdamSeattle (talk) 06:42, 30 March 2025 (UTC)
Discussion
edit- Support--Trade (talk) 19:15, 30 March 2025 (UTC)
- Support--Emwille (talk) 13:08, 1 April 2025 (UTC)
- Support--Thisismattmiller (talk) 16:42, 1 April 2025 (UTC)
- Support -- Riesengrey (talk) 22:07, 2 April 2025 (UTC)
- Support -- Kkdavis14 (talk) 14:39, 4 April 2025 (UTC)
- Please instead support the proposal for a single LUX identifier property: Wikidata:Property_proposal/Yale_LUX_ID rather than embedding the class name into the property. This would require properties for each of physical object, digital object, image, text, audio, person, group, place, set, concept, and activity. Azaroth42 (talk) 16:37, 4 April 2025 (UTC)
ISFDB award category ID
editMotivation
editWe need a specific property to link the categories of an award to ISFDB, because the URL pattern is different than the one used for the awards themselves (ISFDB award ID (P11395)). Those specific URLs are already used on several Wikipedias. --Harmonia Amanda (talk) 22:29, 1 April 2025 (UTC)
Discussion
edit- Support, though I’d be inclined to call it “ISFDB award category ID” (which would also match the URL,
award_category.cgi
) --Lucas Werkmeister (talk) 00:21, 2 April 2025 (UTC)- Oh yeah, that sounds better. Harmonia Amanda (talk) 01:35, 2 April 2025 (UTC)
- Support The format string should allow '+' to accommodate https://www.isfdb.org/cgi-bin/award_category.cgi?349+0 which encodes to https://www.isfdb.org/cgi-bin/award_category.cgi?349%2B0. Add Locus Award for Best First Novel (Q2090893) to examples to demonstrate this. Vicarage (talk) 06:29, 2 April 2025 (UTC)
- Support I revised the regex to allow the + and also to allow numbers larger than 999. There are award category IDs like 1000, 1001, etc. I do note that 349 and 349+0 resolve to the same page, so perhaps the + is totally unnecessary. AdamSeattle (talk) 17:47, 2 April 2025 (UTC)
- Thanks! I'm bad with regex and I didn't even see I limited to 999. I would have only discovered it when using the property and getting errors :D. I don't think the "+" is necessary, as far as I see the "+0" or "+1" decides how the page is structured, but the identifier resolves correctly to the correct category without it, so it would actually make more sense to store the IDs without the +. --Harmonia Amanda (talk) 21:11, 2 April 2025 (UTC)
- I agree, so I've revised the regex and changed the example to remove the +0. AdamSeattle (talk) 21:53, 2 April 2025 (UTC)
- Support Makes sense to me, especially given that other identifiers from ISFDB are already present. --Aspensmonster (talk) 19:43, 2 April 2025 (UTC)
- Support --Kdkeller (talk) 21:49, 3 April 2025 (UTC)
- Oppose I can't see these URLs "used in several wikipedias". And there are only 191 elements. Gerwoman (talk) 07:30, 4 April 2025 (UTC)
- If ISFDB award ID (P11395) is wanted, then we need this variant to cope with a different format string. It might be preferable if ISFDB hadn't produced this small subset, but we have no control of that. Vicarage (talk) 08:03, 4 April 2025 (UTC)
IEC 61355 identifier
editDescription | IEC document kind classification code; IEC DCC |
---|---|
Represents | IEC 61355 (Q1275524) |
Data type | External identifier |
Domain | item: standard, document, diagram, chart, list, etc |
Allowed values | D\d{5} |
Example 1 | diagram (Q959962)IEC identifierD00002 |
Example 2 | piping and instrumentation diagram (Q1890459)IEC identifierD00043 |
Example 3 | technical standard (Q317623)IEC identifierD00010 |
Source | https://std.iec.ch/iec61355/iec61355.nsf/$enID?OpenForm |
Number of IDs in source | 232 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://std.iec.ch/iec61355/iec61355.nsf/(sysSymbolEn)/$1?Opendocument |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editImportant classifier for technical documents.
Nominally "DCC" is a more generic classification code as shown at https://en.wikipedia.org/wiki/IEC_61355: eg FB is "Flow diagrams". This DCC is shown eg on the page of piping and instrumentation diagram (Q1890459)Identity numberD00043, but the identity number is the more specific one (to distinguish it from process flow diagram (Q912333) and other flow diagrams).
I think "IEC DCC" is short and memorable, so I'm proposing it as one of the aliases for this prop.
--Vladimir Alexiev (talk) 20:47, 17 April 2025 (UTC)
Discussion
edit- The label should indicate that this is the "identity number" then? ArthurPSmith (talk) 17:10, 21 April 2025 (UTC)
- Let's call the property "IEC 61355 identifier" and use IEC DCC as an alias --Vladimir Alexiev (talk) 05:29, 22 April 2025 (UTC)
- Support Ok, I adjusted the label in the title here. ArthurPSmith (talk) 00:56, 28 April 2025 (UTC)
IEC CDD for electronics
editDescription | IEC CDD for electronics; IEC 61360-4 code |
---|---|
Represents | IEC Common Data Dictionary (Q60740694) |
Data type | External identifier |
Domain | item |
Allowed values | [A-Z]{3}\d{3} |
Example 1 | complex number (Q11567)IEC CDDAAA234 (named as "complex number value") |
Example 2 | impedance (Q179043)IEC CDDAAA236 |
Example 3 | sphere (Q12507)IEC CDDAAA665 |
Example 4 | correspondence address (Q105724547)IEC CDDAAA657 (named as "postal address") |
Example 5 | "material declaration" IEC CDD AAF603, ACA070 |
Source | https://cdd.iec.ch/cdd/iec61360/iec61360.nsf/TreeFrameset?OpenFrameSet |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://cdd.iec.ch/CDD/iec61360/iec61360.nsf/TU0/0112-2---61360_4%23$1 |
See also | https://www.wikidata.org/wiki/Wikidata:Property_proposal/IEC_document_kind_classification_code |
Applicable "stated in"-value | IEC Common Data Dictionary (Q60740694) |
Distinct-values constraint | yes |
Motivation
editIEC CDD is an online database of product characteristics and properties. https://cdd.iec.ch/cdd/iec61360/iec61360.nsf/Welcome?OpenPage includes the following datasets:
- https://cdd.iec.ch/cdd/common/iec61360-7.nsf General items (IEC 61360-7)
- https://cdd.iec.ch/cdd/iec61360/iec61360.nsf Electric/electronic components (IEC 61360-4). See this proposal
- https://cdd.iec.ch/cdd/iec61987/iec61987.nsf Process automation (IEC 61987 series)
- https://cdd.iec.ch/cdd/iec62720/iec62720.nsf Units of measurement (IEC 62720). I will propose this next
- https://cdd.iec.ch/cdd/iec62683/iec62683.nsf Low voltage switchgear (IEC 62683 series)
- https://cdd.iec.ch/cdd/iectc85/iec63213.nsf Measuring equipment for electrical quantities (IEC 63213)
- https://cdd.iec.ch/cdd/iec63508/iec63508.nsf Circuit-breakers for household use (IEC 63508)
- https://cdd.iec.ch/cdd/isoics/isoics.nsf International classification for standards (ISO ICS)
They are all based on International Registration Data Identifier (IRDI), eg 0112/2///61360_4#AAA234 for the first example (or 0112/2///61360_4#AAA234#001 with version number).
We could use a single property "IRDI" but the formatter URLs are different for all standards in the CDD. So we'd need a custom resolver based on the prefix (or rather, the standard id, eg 61360_4 --Vladimir Alexiev (talk), 06:14, April 22, 2025
Discussion
edit- Support I think separate properties are fine. ArthurPSmith (talk) 20:20, 22 April 2025 (UTC)
- Comment Hi @ArthurPSmith: I'm now thinking that it's better to use the whole IRDI. We can use a smarter formatter to redirect per the standard part of the IRDI, and per WD type (for Units vs ListsOfUnitsAllVersions, see Wikidata:Property proposal/IEC CDD units) --Vladimir Alexiev (talk) 06:00, 29 April 2025 (UTC)
IEC CDD units
editDescription | IEC 62720 units of measure code |
---|---|
Represents | IEC Common Data Dictionary (Q60740694) |
Data type | External identifier |
Domain | item |
Allowed values | [A-Z]{3}\d{3} |
Example 1 | kilogram per hour (Q107210138)IEC CDDUAA607 |
Example 2 | kilogram (Q11570)IEC CDDUAA594 |
Example 3 | Momme (Q124685757)IEC CDDUAB598 |
Source | https://cdd.iec.ch/cdd/iec62720/iec62720.nsf/TreeFrameset |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://cdd.iec.ch/cdd/iec62720/iec62720.nsf/Units/0112-2---62720%23$1 |
See also | Wikidata:Property_proposal/IEC_CDD_for_electronics, QUDT unit ID (P2968), QUDT quantity kind ID (P8393) |
Applicable "stated in"-value | IEC Common Data Dictionary (Q60740694) |
Distinct-values constraint | yes |
Motivation
editIEC CDD is an online database of product characteristics, properties, units of measure, etc. In Wikidata:Property_proposal/IEC_CDD_for_electronics I listed all parts of that database (IEC standards). Here I'm proposing a prop for this part:
- https://cdd.iec.ch/cdd/iec62720/iec62720.nsf Units of measurement (IEC 62720)
I don't know why this tree doesn't expand, but there are links between units and unit lists, allowing us to discover more. Also, QUDT has 1215 units, 211 quantityKinds and 4 physical constants with property qudt:iec61360Code, also expressed as link qudt:informativeReference, see https://github.com/qudt/qudt-public-repo/issues/1092.
IEC CDD codes are all International Registration Data Identifier (IRDI), eg 0112/2///62720#UAA607 for the first example (or 0112/2///62720#UAA607#001 with version number).
Unfortunately quantityKinds and physicalConstants use a slightly different prefix (Units vs ListsOfUnitsAllVersions), eg (hover over the URLs):
- mass flow rate (Q1366187) has two IRDI coming from two IEC standards:
- 0112/2///61987#ABT545: lists 31 units (i.e. unit of mass flow rate (Q126978213))
- 0112/2///62720#UAD107: lists 34 units, including the "SI coherent derived unit"
- Avogadro constant (Q6203): 0112/2///62720#UAD015
Perhaps it's best to use a single property "IRDI" for:
- IEC 62720 units,
- IEC 62720 quantityKinds and physicalConstants,
- other IEC standards defining units and quantityKinds,
- other IEC standards covered by IEC CDD
But the formatter URLs are different for all standards in the CDD so we'd need a custom resolver based on the prefix (eg 62720 vs 61987), and even for units vs quantityKinds and physicalConstants (but I don't know how to distinguish them, except by Wikidata item type).
--Vladimir Alexiev (talk) 07:46, 22 April 2025 (UTC)
Discussion
edit- Comment Are you proposing to create a "smart" formatter for these? The current redirector service is "dumb" - it doesn't look up anything in Wikidata for reference, it just relies on what is provided as parameters. ArthurPSmith (talk) 19:23, 29 April 2025 (UTC)
parliament.uk bill ID
editDescription | Identifier for a bill or act on parliament.uk |
---|---|
Data type | External identifier |
Domain | UK legislation |
Allowed values | [1-9]\d* |
Example 1 | House of Lords Reform Bill 2012 (Q5915119) → 1067 |
Example 2 | Animal Welfare (Kept Animals) Bill (Q107366106) → 2880 |
Example 3 | Steel Industry (Special Measures) Act 2025 (Q133860904) → 3961 |
Example 4 | Video Recordings Act 2010 (Q7927867) → 567 |
Source | https://bills.parliament.uk/ |
Number of IDs in source | unknown |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://bills.parliament.uk/bills/$1 |
URL match pattern | ^https?:\/\/bills\.parliament\.uk\/bills\/(\d+) |
See also | parliament.uk member ID (P10428) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editbill.parliament.uk has details of proposed bills and passed acts not covered by legislation.gov.uk ID (P3343). UndefinedRachel (talk)
Discussion
edit- Support Looks like a good reference. ArthurPSmith (talk) 00:50, 28 April 2025 (UTC)
- Support. Very useful. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:09, 28 April 2025 (UTC)
- Comment The lowest identifier I can find is https://bills.parliament.uk/bills/26 (first proposed Febuary 2007). and the earliest are https://bills.parliament.uk/bills/140 (Febuary 2005) and https://bills.parliament.uk/bills/208/stages (November 2004). Is there a way of indicating a cut off point for when the property is valid? If we can find the truly earliest bill on the website, are all bills proposed after that point listed? Secondly, is there an applicable qualifier for stages such as royal assent (Q1070654) or eg "3rd reading in House of Lords" (would likely need to either invent new Q IDs or use series ordinal (P1545)). Tæppa (talk)
- Support Ainali (talk) 07:03, 29 April 2025 (UTC)
- Question: (and I support this proposal regardless of the answer, I am just curious) Is there a way to see the connection between bills in this database and what ends up in legislation.gov.uk-ID? Ainali (talk) 07:06, 29 April 2025 (UTC)
- Yes. a link to the corresponding legislation.gov.uk page is add to the bills.parliament.uk page (and its RSS feed) when a bill becomes law (https://bills.parliament.uk/bills/3961 See "Get file" button). I plan to write a script to extract the details for easy matching. UndefinedRachel (talk) 09:12, 29 April 2025 (UTC)
- Question: (and I support this proposal regardless of the answer, I am just curious) Is there a way to see the connection between bills in this database and what ends up in legislation.gov.uk-ID? Ainali (talk) 07:06, 29 April 2025 (UTC)
Mobility Database ID
editDescription | An identifier for a General Transit Feed Specification feed (Q113379415) in the Mobility Database (Q134286316) |
---|---|
Represents | Mobility Database (Q134286316) |
Data type | External identifier |
Domain | General Transit Feed Specification feed (Q113379415) |
Allowed values | mdb-[1-9]\d+ |
Example 1 | Amtrak General Transit Feed Specification feed (Q113379480) → mdb-11 |
Example 2 | Auckland GTFS Feed (Q134251700) → mdb-1029 |
Example 3 | New South Wales GTFS Feed (Q134268812) → mdb-2449 |
Source | https://mobilitydatabase.org |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://mobilitydatabase.org/feeds/$1 |
Applicable "stated in"-value | Mobility Database (Q134286316) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
editA ID in the Mobility Database (Q134286316), which is a database of General Transit Feed Specification feed (Q113379415) maintained by Mobility Data (Q134286341).
Wikidata already has a property Onestop ID (P11109) for Transitland (Q113379392), which is a database with the same purpose, but a slightly broader scope.
WikiProject Authority control has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead., @عُثمان:, @BrokenSegue:, @Thryduulf:, @PiperMcCorkle: since you were all involved in Wikidata:Property proposal/Onestop ID, and this is basically the same type of database.
--Кайл55 (talk) 15:12, 30 April 2025 (UTC)
Discussion
edit- Support Looks useful. ArthurPSmith (talk) 20:48, 7 May 2025 (UTC)
Private Enterprise Number
editDescription | number assigned by the Internet Assigned Number Authority which uniquely identifies a private enterprise |
---|---|
Represents | Private Enterprise Number (Q7246073) |
Data type | External identifier |
Domain | item, organization (Q43229) |
Example 1 | Hewlett-Packard (Q80978) → 11 |
Example 2 | New York University (Q49210) → 88 |
Example 3 | McDonald’s (Q38076) → 30897 |
Source | https://www.iana.org/assignments/enterprise-numbers/ |
Formatter URL | https://www.iana.org/assignments/enterprise-numbers/?q=$1 |
Motivation
editPrivate Enterprise Numbers, or PENs, are assigned by Internet Assigned Numbers Authority (Q242540) on request from a company or individual. A considerable amount of large corporations have these identifiers and it is important to include here. They are all publicly available and can be used to construct ITU/ISO/IEC object ID (P3743) values under the 1.3.6.1.4.1 node. -wd-Ryan (Talk/Edits) 01:11, 2 May 2025 (UTC)
Discussion
edit- Support I didn't know about this, but it looks like a good reference identifier for organizations. ArthurPSmith (talk) 02:44, 4 May 2025 (UTC)
- Any Wikiprojects that would be interested in this identifier? -wd-Ryan (Talk/Edits) 18:04, 11 May 2025 (UTC)
- Support --Kdkeller (talk) 23:18, 12 May 2025 (UTC) The URL formatter looks like a search query. Is there a direct link for each company?
- I can't find any, but it is important to note that the URL doesn't seem to search the names of companies if you input just a number. So it should only ever return the exact identifier value. -wd-Ryan (Talk/Edits) 00:50, 13 May 2025 (UTC)
Delfi.lv theme ID
editDescription | identifier of a theme in the Delfi.lv database |
---|---|
Data type | External identifier |
Allowed values | [1-9][0-9]+ |
Example 1 | Novak Djokovic (Q5812) → 35402640 |
Example 2 | Baltic Basketball League (Q805695) → 35400606 |
Example 3 | Latvijas Basketbola līga (Q1640536) → 35417134 |
Source | https://www.delfi.lv/ |
Planned use | add to mix'n'match |
Number of IDs in source | 9,287 (at least according to what the Wayback Machine has archived; may be lower or higher) |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.delfi.lv/temas/$1 |
See also | Postimees topic ID (P9937), ERR keyword ID (P13295), Delfi.ee theme ID (P13403) |
Applicable "stated in"-value | Delfi (Q1184119) |
Motivation
editThis is a natural follow-up to the proposal for Delfi.ee theme ID (P13403), with respect to the Latvian version of that site. Mahir256 (talk) 19:21, 14 May 2025 (UTC)
Discussion
edit15min.lt theme ID
editDescription | identifier for a theme in the 15min online Lithuanian news website |
---|---|
Data type | External identifier |
Allowed values | [1-9][0-9]* |
Example 1 | Málaga (Q8851) → 1119 |
Example 2 | Helsinki (Q1757) → 1040 |
Example 3 | Giedrius Titenis (Q2744601) → 926 |
Source | https://www.15min.lt/ |
Planned use | add to mix'n'match |
Number of IDs in source | 22,116 (at least according to what the Wayback Machine has archived; may be higher or lower) |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.15min.lt/tema/_-$1 |
See also | Postimees topic ID (P9937), ERR keyword ID (P13295), Delfi.ee theme ID (P13403) |
Applicable "stated in"-value | 15 min (Q194350) |
Motivation
editThis is a complement to the three proposals for topics on Estonian news websites and the proposal at Wikidata:Property proposal/Delfi.lv theme ID for a Latvian news site; with this all three Baltic countries would have properties that could be attached to a wide variety of items of general interest. Mahir256 (talk) 21:29, 15 May 2025 (UTC)