User talk:Pamputt

Welcome to Wikidata, Pamputt!

Wikidata is a free knowledge base that you can edit! It can be read and edited by humans and machines alike and you can go to any item page now and add to this ever-growing database!

Need some help getting started? Here are some pages you can familiarize yourself with:

Introduction – An introduction to the project.
Wikidata tours – Interactive tutorials to show you how Wikidata works.
Community portal – The portal for community members.
User options – including the 'Babel' extension, to set your language preferences.
Contents – The main help page for editing and using the site.
Project chat – Discussions about the project.
Tools – A collection of user-developed tools to allow for easier completion of some tasks.

Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date.

If you have any questions, don't hesitate to ask on Project chat. If you want to try out editing, you can use the sandbox to try. Once again, welcome, and I hope you quickly feel comfortable here, and become an active editor for Wikidata.

Best regards! Ajraddatz (Talk) 14:35, 6 February 2013 (UTC)[reply]

^{all subpages T · m:special:CentralAuth}

Autopatrolled

Hello, Pamputt! I am just letting you know that I have added the autopatroller flag to your account, as you are a trusted user on Wikidata. If you have any questions or concerns, please don't hesitate to contact me or leave a message at the project chat. Thanks, Vogone talk 17:48, 22 March 2013 (UTC)[reply]

Hello Vogone, thanks for the status. Pamputt (talk) 23:20, 22 March 2013 (UTC)[reply]

Majuscule dans les libellés

Bonjour Gloumouth1, j'ai vu que tu avais remplacé la majuscule de « Station » par une minucusle (« station »). J'avais cru comprendre qu'il fallait mettre des majuscules ; je veux dire par là que c'est actuellement la très grand majorité des items sur Wikidata et j'utilise systématiquement une majuscule lorsque je renseigne ce champ. Est ce qu'il y a une décision, une règle qui spécifie d'utiliser une minuscule ? Pamputt (talk) 08:13, 7 April 2013 (UTC)[reply]

Bonsoir. Voici 2 pages qui vous seront utiles :

Salutations,

--Gloumouth1 (talk) 21:11, 7 April 2013 (UTC)[reply]

Merci. Il faut donc utiliser des minuscules (sauf pour les noms propres) Pamputt (talk) 05:44, 8 April 2013 (UTC)[reply]

Comment sourcer

Hello, merci d'apporter des sources sur wikidata. Pour sourcer avec un livre, il faut créer 2 éléments au minimum si il existe plusieurs éditions du livre, comme c'est le cas de ton livre. L'élément que tu as créé correspond à l'oeuvre et les données qui sont disponibles dans cet élément sont communs à toutes les versions et éditions de l'oeuvre. Mais cet élément n'est pas utilisé comme source dans la section référence: il faut un autre élément qui contienne les données spécifiques d'une édition comme l'éditeur, la date de publication, le lieu de publication ou l'ISBN. J'ai créé cet élément Nobel Prize Women in Science (Q15043316) et les différentes propriétés qui y sont liées. je te laisse le soin de compléter les données manquantes et si tu as d'autres questions n'hésites pas à me contacter. Snipre (talk) 21:24, 4 October 2013 (UTC)[reply]

Merci beaucoup pour ton aide. C'est vrai que c'est un peu obscur comme fonctionnement au début mais bon, ça va s'améliorer avec le temps. J'ai ajouté 2/3 informations dans l'objet d'édition. Par contre, je n'ai pas compris à quoi servait, fondamentalement, l'objet d'édition ? L'objet oeuvre Q15043031 ne contient pas de lien avec Q15043316 ; c'est uniquement l'éition qui est lié au livre (ce qui se comprend) mais du coup je ne comprends pas l'intérêt de séparer les deux. Pamputt (talk) 21:51, 4 October 2013 (UTC)[reply]

PS : merci pour la correction de l'ISBN Pamputt (talk) 21:52, 4 October 2013 (UTC)[reply]

Pourquoi créer un élément pour chaque édition et un élément pour une oeuvre: si on veut donner des données très précises comme l'éditeur ou la date de publication, on ne peut pas avoir un seul élément en cas de plusieurs éditions d'une même oeuvre, car tout serait mélangé dans un seul élément. Et la raison d'un élément pour l'oeuvre se trouve du côté de wikipedia qui souvent a un article pour l'oeuvre, mais pas pour les éditions. Il faut au moins un lien entre l'élément oeuvre et l'élément édition pour pouvoir réunir toutes les édition d'une oeuvre si on veut faire une telle recherche, comme pour lister toutes les éditions sur la page wikipédia de l'oeuvre. En espérant t'avoir renseigné. Snipre (talk) 22:07, 4 October 2013 (UTC)[reply]

Property:P133

Bonjour,

Votre interprétation est correcte, sauf que l'utilisation de P361 est transitoires, comme c'est visible dans Wikidata talk:Languages task force#Relating languages.

De plus, je viens de passer sur toutes les fiches utilisant P133, donc il faut juste vérifier que je n'ai pas commis ou laissé d'erreur. Visite fortuitement prolongée (talk) 21:46, 1 November 2013 (UTC)[reply]

Actuellement j'utilise Wikidata:Database reports/Constraint violations/P133. Visite fortuitement prolongée (talk) 14:53, 4 January 2014 (UTC)[reply]

Merci bien pour cette page, ça permet de vérifier qu'on a pas fait d'erreur (ce qui n'était pas le cas ...). Pamputt (talk) 19:50, 4 January 2014 (UTC)[reply]

Merci pour votre classement des langues sames.

Sac-Fox-Kickapoo (Q15551956) doublonne Sac-Fox-Kickapoo (Q12953709). Visite fortuitement prolongée (talk) 13:16, 5 January 2014 (UTC)[reply]

Merci pour le doublon. J'avais pas fait gaffe. J'ai demandé la fusion. Et de rien pour les langues sames. On va réussir à faire quelque chose de bien tous les deux :D Pamputt (talk) 13:20, 5 January 2014 (UTC)[reply]

« l'utilisation de P361 est transitoires » →‎ Cf. cette recherche de solution définitive. Visite fortuitement prolongée (talk) 20:19, 23 May 2015 (UTC)[reply]

Congratulations, Dear Administrator!

Pamputt, congratulations! You now have the rights of administrator on Wikidata. Please take a moment to read the Wikidata:Administrators page and watchlist related pages (in particular Wikidata:Project chat, Wikidata:Requests for comment, and Wikidata:Administrators' noticeboard), before launching yourself into page deletions, page protections, account blockings, or modifications of protected pages.

Please feel free to join us on IRC: #wikidata-admin @ irc.freenode.net. If you need access, you can flag someone down at @ irc.freenode.net. You may find Wikidata:Guide to Adminship to be useful reading. You may also want to consider adding yourself to meta:Template:Wikidata/Ambassadors, and to any similar page on your home wiki if one exists. (Check Wikipedia:Wikidata/Wikidatans (Q14964498).)

Please also add/update the languages you speak to your listing at Wikidata:List of administrators. You may also like to add your username to this list if you would not like that items you delete at RfD get marked as deleted automatically. Again, welcome to the admin corps!

-- Bene* ^t_a^l_k 19:26, 4 March 2014 (UTC)[reply]

Accepte svp mes felicitations à cause d'election l'administrateur.--Ymblanter (talk) 19:27, 4 March 2014 (UTC)[reply]

Merci beaucoup. Au boulot maintenant :P Pamputt (talk) 19:49, 4 March 2014 (UTC)[reply]

Deletion of Q15895728

Hello. I'd like to know why you deleted Q15895728. Whenever I find an item/category pair that exists on Wikipedia and only had one of the pair on Wikidata, I create the missing item and link the two with topic's main category (P910) and category's main topic (P301). In this case, I tried to pair human-geographic territorial entity (Q15642541) on Wikidata with w:en:Category:Humangeographic territorial entities on Wikipedia. Am I doing something wrong? --Arctic.gnome (talk) 19:11, 6 March 2014 (UTC)[reply]

@Arctic.gnome: Hello, I deleted it because no Wikipedia page were linked to this item. Category:Human-geographic territorial entities (Q15895728) is gone back. I added the Wikipedia page that you mentionned. Sorry to do not check enough before the deletion. Pamputt (talk) 20:08, 6 March 2014 (UTC)[reply]

more tools

Hi Pamputt! You may add some help tools to user:Pamputt/common.js or (if you use the vector skin) to user:Pamputt/vector.js . Please see User:Rotsaert8000 (in Esperanto), Wikidata:Tools, and Wikidata:Tools/User scripts for candidates you may add. On the user:i18n-page you will see all WD gadget links. It takes time to see what fits most of your interests. Good luck! Please feel free to use the Wikidata Sandbox item: Wikidata Sandbox (Q4115189)   for your first steps adding some statements ^{see Wikidata:List of properties}. If you want to notify a user you may use {{ping|foo bar}} at any place on this wiki. Regards gangLeri לערי ריינהארט (talk) 22:58, 26 May 2014 (UTC)[reply]

Physics WikiProject

New userbox (also translatable) is at Wikidata:Userboxes --Tobias1984 (talk) 12:29, 13 August 2014 (UTC)[reply]

2015-01 fusions

Bonjour, Vous écrivez dans votre page utilisateur « Fusionner les articles de langues de Wikipédia en piémontais avec les items déjà existants (voir ici et chercher « lenga ») ». Une autre méthode pour trouver des éléments (traitant de langues) à fusionner, c'est de chercher (dans toutes les langues de Wikipédia) les articles incluant Template:Infobox language (Q7217946) et non liés à d'autres articles par Wikidata, par exemple Q17634729 et Q11732421. Visite fortuitement prolongée (talk) 21:37, 3 January 2015 (UTC)[reply]

Bonjour Visite fortuitement prolongée et merci du conseil. Cependant je n'ai pas tout compris ; comment fais-tu (pratiquement) pour repérer les articles de toutes les Wikipédias qui utilisent « Infobox langue » ? Il y a un outil pour ça ? Et merci pour Māori (Q17634729) et Maridjabin (Q11732421), je les ai fusionné. Pamputt (talk) 10:23, 4 January 2015 (UTC)[reply]

Soit les trouver manuellement, soit demander à un logiciel informatique de les trouver. Visite fortuitement prolongée (talk) 20:44, 4 January 2015 (UTC)[reply]

Il faudrait aussi fusionner Q3319353 et Q3217488. Visite fortuitement prolongée (talk) 21:37, 5 January 2015 (UTC)[reply]

@Visite fortuitement prolongée:

Done J'ai plutôt déplacé le lien thaï dans Moken (Q18648701) tandis que j'ai mis l'article anglais dans Moken (Q3217488) Pamputt (talk) 22:16, 5 January 2015 (UTC)[reply]

D'accord. Visite fortuitement prolongée (talk) 22:50, 5 January 2015 (UTC)[reply]

Pourriez vous fusionner Q17190181 et Q18325198 ? Visite fortuitement prolongée (talk) 21:49, 6 January 2015 (UTC)[reply]

Done Pamputt (talk) 16:50, 7 January 2015 (UTC)[reply]

Merci. Visite fortuitement prolongée (talk) 21:12, 7 January 2015 (UTC)[reply]

Q6291555 et Q18329653 ? Visite fortuitement prolongée (talk) 21:21, 22 February 2015 (UTC)[reply]

Done Merci pour le signalement. Pamputt (talk) 22:11, 22 February 2015 (UTC)[reply]

Q8825980 et Q9592403, Q8638934 et Q18173912, Q8520466 et Q17477225, Q9833633 et Q17303766. Visite fortuitement prolongée (talk) 21:28, 27 February 2015 (UTC)[reply]

Done Merci Pamputt (talk) 06:49, 28 February 2015 (UTC)[reply]

Q417827 et Q16775060 ? Visite fortuitement prolongée (talk) 21:52, 3 March 2015 (UTC)[reply]

Done

Vu Wikidata:Database reports/Constraint violations/P305#Conflicts with, pourquoi des fiches (item) wikidata de langues sont fusionnées avec des fiches (item) wikidata de page d'homonymie ? Comment est-ce possible ? Visite fortuitement prolongée (talk) 21:52, 3 March 2015 (UTC)[reply]

@Visite fortuitement prolongée: Cela provient d'une fusion, par exemple pour Lou language (Q3260104), l'ajout de la désignation « page d'homonymie » a été fait lors de la fusion avec l'élément Lou language (Q6685832). Et cet élément contenait initialement uniquement un lien vers la page d'homonymie en:Lou language. J'imagine qu'on peut trouver la même explication pour Dari (Q178440). Le cas de European French (Q3083218) est plus compliqué dans la mesure où les articles français et anglais réfèrent à la même chose mais les deux articles ne sont pas traiter de la même façon : le français traite le sujet comme un article à part entière tandis que l'anglais comme une page d'homonymie. Pamputt (talk) 22:08, 3 March 2015 (UTC)[reply]

Je sais que cela résulte de fusions. C'est écrit dans ma question. Visite fortuitement prolongée (talk) 21:16, 4 March 2015 (UTC)[reply]

@Visite fortuitement prolongée: bah du coup je ne comprends pas la question. Soit il y a eu une erreur lors de la fusion, soit la page qui a été fusionné contenait déjà plusieurs propriétés instance of (P31). Pamputt (talk) 07:00, 5 March 2015 (UTC)[reply]

Lorsque vous nettoyez une fiche wikidata (telles Q178440 et Q3260104), ne vous limitez pas aux corrections évidentes. Si vous laissez de coté les scories les moins visibles, alors celles-ci risquent de rester ad vitam æternam. Visite fortuitement prolongée (talk) 21:16, 4 March 2015 (UTC)[reply]

Si tu parles des descriptions dans les différentes langues, tu as raison ; j'ai oublié de le faire dans le cas de Dari (Q178440) et Lou language (Q3260104) Pamputt (talk) 07:00, 5 March 2015 (UTC)[reply]

Q1665598 et Q3693453, Q4036548 et Q12486686 ? Visite fortuitement prolongée (talk) 21:01, 7 March 2015 (UTC)[reply]

Done

Pamputt (talk) 21:19, 7 March 2015 (UTC)[reply]

Merci. Visite fortuitement prolongée (talk) 22:10, 7 March 2015 (UTC)[reply]

Je crois qu'il faudrait scinder Category:Collation (Q8387372) : une partie autour de en:Category:Collation (peut-être à rattacher à Q9598150 ?), l'autre autour de fr:Catégorie:Classement alphabétique. Visite fortuitement prolongée (talk) 22:26, 10 March 2015 (UTC)[reply]

@Visite fortuitement prolongée: salut. Dans ce cas précis, ça me semble plus compliqué que les cas précédents. Il faudrait me dire précisément quels liens est ce que tu voudrais mettre dans Category:Collation (Q8387372) et quels autres dans Q9598150. Car la répartition actuelle me parait acceptable. Pamputt (talk) 22:39, 10 March 2015 (UTC)[reply]

chi va piano, va sano Il me semble que c'est une erreur de rattacher en:Category:Collation à fr:Catégorie:Classement alphabétique (situation actuelle dans Category:Collation (Q8387372)), puisque fr:Classement alphabétique est rattaché à en:Alphabetical order, pas à en:Collation. Votre avis ? Visite fortuitement prolongée (talk) 22:51, 10 March 2015 (UTC)[reply]

Autre question, pour faire murir la réflexion : le category's main topic (P301) de la Category:Collation (Q8387372) doit être collation (Q14953108) ou alphabetical order (Q10925) ? Visite fortuitement prolongée (talk) 21:19, 12 March 2015 (UTC)[reply]

Category:Inscriptions (Q6128252) et Category:Epigraphy (Q8948191) sont mélangées, c'est affreux. Je m'en occuperais plus tard. Visite fortuitement prolongée (talk) 21:37, 11 March 2015 (UTC)[reply]

Q7779954 et Q9553530, Q8621861 et Q9553584 ? Visite fortuitement prolongée (talk) 22:00, 11 March 2015 (UTC)[reply]

Q9063271 et Q10248245 ? Visite fortuitement prolongée (talk) 22:43, 11 March 2015 (UTC)[reply]

Q8382216 et Q13349364 ? Visite fortuitement prolongée (talk) 22:49, 11 March 2015 (UTC)[reply]

Salut, je viens de m'occuper de ces derniers éléments. Pour ce qui est de Category:Collation (Q8387372) et Q9598150 ainsi que de Category:Inscriptions (Q6128252) et Category:Epigraphy (Q8948191), je garde ça en tête. J'essaie de faire ça ce weekend. Pamputt (talk) 06:18, 12 March 2015 (UTC)[reply]

Merci. Visite fortuitement prolongée (talk) 21:19, 12 March 2015 (UTC)[reply]

Peut-être Q835866 et Q3250696 ? Visite fortuitement prolongée (talk) 22:55, 12 March 2015 (UTC)[reply]

Q13328624 et Q8582842. Visite fortuitement prolongée (talk) 22:49, 13 March 2015 (UTC)[reply]

Je viens de fusionner Category:Languages of South Sudan (Q13328624) et Category:Languages of South Sudan (Q8582842). En revanche, je ne sais pas quoi penser de languages of China (Q835866) et languages of China (Q3250696). A noter que, si ça t'intéresse, tu peux également effectuer ces fusions. Il faut pour cela activer le gadget Merge dans tes préférences utilisateur. Pamputt (talk) 00:07, 14 March 2015 (UTC)[reply]

Merci pur la fusion. Visite fortuitement prolongée (talk) 21:56, 14 March 2015 (UTC)[reply]

Q12336757 et Q15282934 ? Visite fortuitement prolongée (talk) 21:56, 14 March 2015 (UTC)[reply]

Plusieurs sous-catégories de fr:Catégorie:Consonne et en:Category:Consonants sont liées à des fiches wikidata différentes. Visite fortuitement prolongée (talk) 22:49, 14 March 2015 (UTC)[reply]

Fait pour language regulator (Q12336757) et language regulator (Q15282934). Pour les catégories de consonnes, je pense avoir fait le tour. Dis moi si tu en trouves d'autres. Pamputt (talk) 08:49, 15 March 2015 (UTC)[reply]

Quelle rapidité !

Toutes les sous-catégories de fr:Catégorie:Consonne me semblent liées. Visite fortuitement prolongée (talk) 21:26, 15 March 2015 (UTC)[reply]

Q397628 et Q16032253 ? Visite fortuitement prolongée (talk) 21:26, 15 March 2015 (UTC)[reply]

Q2989658 et Q1434121 ? Visite fortuitement prolongée (talk) 22:28, 15 March 2015 (UTC)[reply]

Done Pamputt (talk) 06:33, 16 March 2015 (UTC)[reply]

Q8583987 et Q13350236, Q13288055 et Q13350237. Visite fortuitement prolongée (talk) 22:56, 18 March 2015 (UTC)[reply]

Done Pamputt (talk) 04:59, 19 March 2015 (UTC)[reply]

Q9803120 et Q13355279, Q6324640 et Q19640579, Q13320702 et Q18193248, Q9063093 et Q7716312. Visite fortuitement prolongée (talk) 22:56, 21 March 2015 (UTC)[reply]

Done Merci Pamputt (talk) 10:47, 22 March 2015 (UTC)[reply]

Q9000363 et Q8583849, Q13328693 et Q10036210. Visite fortuitement prolongée (talk) 22:57, 22 March 2015 (UTC)[reply]

Done Pamputt (talk) 06:12, 23 March 2015 (UTC)[reply]

Merci. Visite fortuitement prolongée (talk) 22:48, 23 March 2015 (UTC)[reply]

Q9498021 et Q9759023. Visite fortuitement prolongée (talk) 22:48, 23 March 2015 (UTC)[reply]

Done Pamputt (talk) 06:54, 24 March 2015 (UTC)[reply]

Merci. Visite fortuitement prolongée (talk) 22:51, 24 March 2015 (UTC)[reply]

Q16395502 et Q5550686. Visite fortuitement prolongée (talk) 22:51, 24 March 2015 (UTC)[reply]

Done je ne pouvais pas fusionné les deux éléments étant donné qu'il y avait un lien vers Wikipédia en espéranto dans les deux éléments. J'ai donc fait un peu de ménage en déplaçant le lien français vers l'élément « principal ». Pamputt (talk) 06:36, 25 March 2015 (UTC)[reply]

Q15974789 et Q18962533, Q9831506 et Q7888829, Q8376614 et Q9662923, Q8555171 et Q13326624. Visite fortuitement prolongée (talk) 22:28, 25 March 2015 (UTC)[reply]

Done Pamputt (talk) 06:08, 26 March 2015 (UTC)[reply]

Merci. Visite fortuitement prolongée (talk) 21:14, 26 March 2015 (UTC)[reply]

Q13582708 et Q347474, Q3406353 et Q17637106 (fusions inachevées de Verdy p. Visite fortuitement prolongée (talk) 21:14, 26 March 2015 (UTC)[reply]

Done Merci d'avoir signalé Pamputt (talk) 21:41, 29 March 2015 (UTC)[reply]

Q392212 et Q19692106. Visite fortuitement prolongée (talk) 20:56, 31 March 2015 (UTC)[reply]

@Visite fortuitement prolongée: pour ce genre de cas, je te conseille vivement d'installer toi-même le gadget pour effectuer les fusions. Car le travail que tu as fait est effectué automatiquement ainsi que la fusion des 2 éléments. Pamputt (talk) 19:19, 1 April 2015 (UTC)[reply]

Q19366793 et Q9611608. Visite fortuitement prolongée (talk) 16:03, 9 May 2015 (UTC)[reply]

Done Pamputt (talk) 11:39, 10 May 2015 (UTC)[reply]

Merci. Visite fortuitement prolongée (talk) 14:26, 10 May 2015 (UTC)[reply]

Q2816466 et Q4636231, Q601271 et Q18618528. Visite fortuitement prolongée (talk) 20:12, 20 May 2015 (UTC)[reply]

Done Pamputt (talk) 22:08, 20 May 2015 (UTC)[reply]

Q3556389 et Q3796822. Visite fortuitement prolongée (talk) 19:17, 23 May 2015 (UTC)[reply]

Q16672015 et Q19862172. Visite fortuitement prolongée (talk) 20:10, 24 May 2015 (UTC)[reply]

Q8757462 et Q13343608. Visite fortuitement prolongée (talk) 19:41, 27 May 2015 (UTC)[reply]

Q7473254 et Q13343315. Visite fortuitement prolongée (talk) 21:53, 29 May 2015 (UTC)[reply]

Q7366787 et Q13343242, Q8919166 et Q13343453, Q16303630 et Q17374806. Visite fortuitement prolongée (talk) 15:14, 30 May 2015 (UTC)[reply]

Done Merci Pamputt (talk) 18:47, 30 May 2015 (UTC)[reply]

Merci à vous aussi :). Visite fortuitement prolongée (talk) 21:56, 30 May 2015 (UTC)[reply]

Q1616181 et Q19979626 (renommage qui a mal fonctionné). Visite fortuitement prolongée (talk) 21:56, 30 May 2015 (UTC)[reply]

Done Pamputt (talk) 07:47, 31 May 2015 (UTC)[reply]

Q294755 et Q12048523. Visite fortuitement prolongée (talk) 19:17, 31 May 2015 (UTC)[reply]

Merci. Visite fortuitement prolongée (talk) 19:28, 31 May 2015 (UTC)[reply]

Q1193453 et Q3556240. Visite fortuitement prolongée (talk) 20:45, 4 June 2015 (UTC)[reply]

Q9590518 et Q7016980. Visite fortuitement prolongée (talk) 21:45, 4 June 2015 (UTC)[reply]

Done Pamputt (talk) 05:52, 5 June 2015 (UTC)[reply]

Q7485996, Q9818385 et Q19360775; Q17046156, Q10216706, Q7670248, Q9502229 et w:fr:Modèle:Utilisateur LibreOffice; Q7696746 et Q10069292. Visite fortuitement prolongée (talk) 13:53, 6 June 2015 (UTC)[reply]

Done je me suis un peu emmêler les pinceaux entre les catégories et les modèles d'utilisateur de LibreOffice mais je crois que c'est bon maintenant. Pamputt (talk) 15:25, 7 June 2015 (UTC)[reply]

C'est ma faute, je n'avais pas vu qu'il y avait des modèles et des catégories. Merci d'avoir fait la distinction. Visite fortuitement prolongée (talk) 16:56, 7 June 2015 (UTC)[reply]

Q15407172 et Q3914924. Visite fortuitement prolongée (talk) 19:58, 7 June 2015 (UTC)[reply]

Q2828964 et Q3399698, Q6373123 et Q13359803. Visite fortuitement prolongée (talk) 20:30, 9 June 2015 (UTC)[reply]

Done Pamputt (talk) 05:58, 10 June 2015 (UTC)[reply]

Q18627581 et Q18969535. Visite fortuitement prolongée (talk) 20:20, 10 June 2015 (UTC)[reply]

Done Pamputt (talk) 20:54, 10 June 2015 (UTC)[reply]

Q4885023 et Q11051704. Visite fortuitement prolongée (talk) 21:50, 10 June 2015 (UTC)[reply]

Il semble que Bembe (Q4885023) et Bembe (Q11051704) ne réfèrent pas à la même langue. EN fait il existe deux codes ISO : bmb et beq. Bref, il faut vérifier les liens pour mettre un peu d'ordre entre les deux items. Pamputt (talk) 05:55, 11 June 2015 (UTC)[reply]

Q11051704 lie w:en:Kibembe qui redirige vers w:en:Bembe language (Ibembe) qui est lié par Q4885023. Il me semble que Q11051704 et Q4885023 correspondent au code ISO 639 bmb (et devraient être fusionnés), tandis que Q3196320 correspond au code ISO 639 beq. Mais il est préférable de vérifier. J'ai demandé à Kwamikagami et Moyogo. Visite fortuitement prolongée (talk) 20:26, 11 June 2015 (UTC)[reply]

Kwamikagami a fait le nettoyage. Bembe (Q11051704) est maintenant vide, il reste à le proposer à la suppression. --Moyogo (talk) 06:48, 12 June 2015 (UTC)[reply]

Q9080204 et Q20152129. Visite fortuitement prolongée (talk) 19:24, 18 June 2015 (UTC)[reply]

Done Pamputt (talk) 05:09, 19 June 2015 (UTC)[reply]

Q2689628 et Q19957291, Q12953709 et Q12714767, Q1440172 et Q15572319. Visite fortuitement prolongée (talk) 20:00, 19 June 2015 (UTC)[reply]

Done Pamputt (talk) 23:04, 21 June 2015 (UTC)[reply]

Oh, c'est rigolo, à présent speech scroll (Q2689628) a plusieurs dizaines de descriptions de Wikimedia disambiguation page (Q4167410), mais n'a plus P31 Q4167410. Visite fortuitement prolongée (talk) 19:26, 22 June 2015 (UTC)[reply]

Q758570 a un problème similaire. Visite fortuitement prolongée (talk) 20:22, 22 June 2015 (UTC)[reply]

Pas sûr d'avoir compris le problème mais ça a peut-être disparu car je ne vois pas ce qui ne va pas actuellement. Pamputt (talk) 05:46, 25 June 2015 (UTC)[reply]

Avez vous compris « a plusieurs dizaines de descriptions » ? Avez vous labelLister ? Visite fortuitement prolongée (talk) 20:30, 25 June 2015 (UTC)[reply]

Q2881675 et Q4853030. Visite fortuitement prolongée (talk) 21:38, 24 June 2015 (UTC)[reply]

Done Pamputt (talk) 05:46, 25 June 2015 (UTC)[reply]

Q13583746 et Q19955907. Visite fortuitement prolongée (talk) 20:30, 25 June 2015 (UTC)[reply]

Q3028668 et Q5279097, Q3515111 et Q7682921. Visite fortuitement prolongée (talk) 21:43, 25 June 2015 (UTC)[reply]

Done Pamputt (talk) 12:09, 27 June 2015 (UTC)[reply]

Merci. Visite fortuitement prolongée (talk) 19:47, 27 June 2015 (UTC)[reply]

Q1427969 et Q20440513 (promis, le mois prochain je crée une nouvelle section). Visite fortuitement prolongée (talk) 19:47, 27 June 2015 (UTC)[reply]

Done Ok pour la nouvelle section

Pamputt (talk) 10:56, 28 June 2015 (UTC)[reply]

Mayday mayday

Bonjour, je viens de traduire (pas terminé) en:Gurgen Askaryan en francais (en passant, un artik qui devrait te plaire). J'ai tout bien fait propre, et passé la serpillière autour, mais il y a des coins que je ne peux pas atteindre : comment je lie l'artic en français à la "fiche" Kikidata que je viens de metrre à jour? Comment faire apparaître sur l'article WP:FR les liens vers les langues plus ou moins exotiques qui figurent sur l'article EN ? Lorsque j'édite celui-ci, les liens n'apparaissent pas ? (Je crois que je vais aller pisser avant de me suicider... Voila, sinon, tu passes quand tu as envie d'une averse de rayon cosmiques ou ot'choz. Tu connais l'adresse ; pour toi, la porte est ouverte. Cordialement, et Hop ! Kikuyu3 (talk) 07:35, 12 February 2015 (UTC)[reply]

@Kikuyu3: salut

On dirait que tu as finalement trouvé comment faire. Normalement sur Wikipédia, tu peux aussi cliquer sur la petite roue qui est présente à la place des liens interwikis et celle-ci ferra apparaitre une boite de dialogue qui te demande d'indiquer la langue et le nom de l'article dans cette langue. Cela aura pour effet de directement ajouter le lien sans passer par Wikidata. Bon ça c'est en principe car la dernière fois que j'ai voulu essayer, ça ne fonctionnait pas. Peut-être que ça a été réparé depuis. Sionon il faut faire comme tu as sans doute fait : aller sur Wikidata et taper le nom de l'article dans la boite de recherche afin de trouver l'élément correspondant. Après ça, il faut ajouter le lien vers l'article français dans la boite qui va bien. Pamputt (talk) 18:11, 12 February 2015 (UTC)[reply]

Salut jeune gredin, et merci, et cordialement, et Hop ! et tout. --Kikuyu3 (talk) 19:46, 21 February 2015 (UTC)[reply]

2015-07 classification

J'ai besoin d'aide dans Wikidata talk:WikiProject Languages‎#2015-05 language classification. Visite fortuitement prolongée (talk) 20:09, 1 July 2015 (UTC)[reply]

2015-07 fusions

Je crois que Q5965401 et Q19367097 devraient être fusionnées. Visite fortuitement prolongée (talk) 19:11, 5 July 2015 (UTC)[reply]

Done Pamputt (talk) 15:34, 6 July 2015 (UTC)[reply]

Q1098467 et Q2635964 et Q3554760 (dont il faut supprimer l'unique Sitelink juste avant la fusion) et Q3804326. Visite fortuitement prolongée (talk) 21:19, 8 July 2015 (UTC)[reply]

@Visite fortuitement prolongée: en fait, je ne peux pas fusionné regional Italian (Q3804326), regional Italian (Q3554760) et regional Italian (Q2635964) dans la mesure où ces trois éléments disposent chacun d'un lien vers it.wiki. Chaque élément ne peut contenir qu'un seul lien vers un wikipédia dans une langue donné. Donc tant que les italophones n'auront pas fusionné leur article, on ne pourra pas le faire ici. Pour le moment, j'ai donc uniquement fusionné regional Italian (Q1098467) avec regional Italian (Q2635964). Pamputt (talk) 05:24, 9 July 2015 (UTC)[reply]

Pour Q2635964, le Sitelink itwiki est hors-sujet. J'aurais du le supprimer hier, mais j'avais oublié. Voilà qui est fait.
Pour Q3554760, le Sitelink itwiki est une redirection pertinente (les deux articles ont été fusionnés), à supprimer juste avant la fusion (comme indiqué ci-dessus). Puisque apparement vous ne pouvez pas faire ça, je viens de supprimer le Sitelink.

Visite fortuitement prolongée (talk) 19:23, 9 July 2015 (UTC)[reply]

Ok, j'ai fini le ménage normalement. Pamputt (talk) 05:22, 10 July 2015 (UTC)[reply]

Il reste Q3804326. Visite fortuitement prolongée (talk) 19:57, 10 July 2015 (UTC)[reply]

Done Pamputt (talk) 07:15, 12 July 2015 (UTC)[reply]

Q5312598 et Q4116103. Visite fortuitement prolongée (talk) 19:23, 9 July 2015 (UTC)[reply]

Done Pamputt (talk) 05:22, 10 July 2015 (UTC)[reply]

Q1299240 et Q3919665. Visite fortuitement prolongée (talk) 19:57, 10 July 2015 (UTC)[reply]

Done Pamputt (talk) 07:15, 12 July 2015 (UTC)[reply]

Q36403 et Q15407194, Q3270727 et Q15407192, Q11001779 et Q16629616, Q35614 et Q15407191, Q3358289 et Q3105505, Q3513567 et Q1478692, Q11128329 et Q16648644, Q2361829 et Q12952652, Q15407181 et Q36560. Visite fortuitement prolongée (talk) 21:50, 13 July 2015 (UTC)[reply]

Done Pamputt (talk) 09:24, 14 July 2015 (UTC)[reply]

Q8494581 et Q10133256, Q15407186 et Q12952830, Q16666077 et Q11008869, Q5996114 et Q15407185, Q7022547 et Q15407184, Q11130292 et Q15407183, Q35923 et Q15407182, ...

Done

... Q11007144 et Q16669810, Q15407179 et Q15632388, Q10961975 et Q15407177, Q3571364 et Q17522640, Q11003439 et Q17522650, Q17522659 et Q11017443, Q7878635 et Q11013088. Visite fortuitement prolongée (talk) 21:48, 14 July 2015 (UTC)[reply]

Done Pamputt (talk) 05:57, 15 July 2015 (UTC)[reply]

Q3914917 et Q3198896. Visite fortuitement prolongée (talk) 21:17, 15 July 2015 (UTC)[reply]

Done Pamputt (talk) 05:14, 16 July 2015 (UTC)[reply]

Q8917557 et Q19889643, Q10873250 et Q9489086, Q9482199 et Q9608261, Q14920129 et Q19330717, Q16807980 et Q19616726, peut-être des transfers à faire entre Q17468049 et Q9136717, Q7364745 et Q9197168, Q13321712 et Q13343259, peut-être Q8915588 et Q13343180 ?? Visite fortuitement prolongée (talk) 21:42, 18 July 2015 (UTC)[reply]

Done, je n'ai rien trouvé à transférer entre Q17468049 et Wikipedia:Orphan (Q9136717) Pamputt (talk) 17:44, 19 July 2015 (UTC)[reply]

Ok, merci. Visite fortuitement prolongée (talk) 18:24, 19 July 2015 (UTC)[reply]

Q8920801 et Q13343164, Q6118193 et Q13343216, Q8916242 et Q13343621. Visite fortuitement prolongée (talk) 20:18, 19 July 2015 (UTC)[reply]

Done Pamputt (talk) 20:41, 20 July 2015 (UTC)[reply]

Q8915062 et Q13343249, Q8919762 et Q13343273. Visite fortuitement prolongée (talk) 21:49, 20 July 2015 (UTC)[reply]

Done Pamputt (talk) 05:49, 21 July 2015 (UTC)[reply]

Q13343201 et Q16807662, Q8389329 et Q13343324, Q13343533 et Q6337347, Q8916840 et Q13343641, Q8917728 et Q13343219. Visite fortuitement prolongée (talk) 21:18, 21 July 2015 (UTC)[reply]

Done Pamputt (talk) 21:21, 21 July 2015 (UTC)[reply]

Q8918762 et Q13343569. Visite fortuitement prolongée (talk) 20:32, 22 July 2015 (UTC)[reply]

Q5299543 et Q7142889, Q5972848 et Q19587411. Visite fortuitement prolongée (talk) 21:38, 22 July 2015 (UTC)[reply]

Done je n'ai pas fusionné languages of Myanmar (Q5299543) et Category:Languages of Myanmar (Q7142889) étant donné que l'un est l'article tandis que l'autre est la catégorie. Pamputt (talk) 05:13, 23 July 2015 (UTC)[reply]

Je me suis trompée, les candidates à la fusion sont Q5299543 et Q17064397. Visite fortuitement prolongée (talk) 20:10, 23 July 2015 (UTC)[reply]

Done Pamputt (talk) 20:13, 23 July 2015 (UTC)[reply]

Q27630 et Q20431319, Q913935 et Q19709334, Q5575236 et Q12953647. Visite fortuitement prolongée (talk) 20:24, 25 July 2015 (UTC)[reply]

Done Pamputt (talk) 13:53, 26 July 2015 (UTC)[reply]

Q5119242 et Q12956636. Visite fortuitement prolongée (talk) 20:08, 30 July 2015 (UTC)[reply]

Q4536500 et Q20792186, Q4536492 et Q20813176, Q1936960 et Q20814919. Visite fortuitement prolongée (talk) 20:09, 13 August 2015 (UTC)[reply]

Q4536485 et Q20824101, Q3832996 et Q20824382. Visite fortuitement prolongée (talk) 21:46, 16 August 2015 (UTC)[reply]

Done Pamputt (talk) 12:27, 17 August 2015 (UTC)[reply]

Q6266718 et Q8826555. Visite fortuitement prolongée (talk) 20:14, 27 September 2015 (UTC)[reply]

Q16735745 et Q20820633 ?? Visite fortuitement prolongée (talk) 20:36, 2 October 2015 (UTC)[reply]

Done Pamputt (talk) 21:32, 2 October 2015 (UTC)[reply]

Q25325 et Q200554, Q1404296 et Q1691819. Visite fortuitement prolongée (talk) 21:22, 7 October 2015 (UTC)[reply]

Impossible de fusionner Belgian Dutch (Q1404296) et Dutch in Belgium (Q1691819) car il y a un lien vers nl.wikipedia dans les deux éléments. Et le lien n'est pas le même ... À éclaircir avant de fusionner. Pamputt (talk) 21:49, 7 October 2015 (UTC)[reply]

Q8113316 et Q13343499. Visite fortuitement prolongée (talk) 20:40, 23 October 2015 (UTC)[reply]

2015-07 questions

Dans Wikidata, il faut combien de temps aux administrateurs pour prendre une décision ? Visite fortuitement prolongée (talk) 20:16, 17 July 2015 (UTC)[reply]

Bonjour Visite fortuitement prolongée, à quelle genre de décision penses-tu ? En règle générale, les administrateurs ne prennent pas de décision autre que protéger une page ou bloquer un utilisateur et dans ce cas, il n'y a pas de délai ; la décision est prise dès qu'un administrateur est disponible. Pamputt (talk) 17:45, 19 July 2015 (UTC)[reply]

Je pense aux sanctions résultant de cette accusation de mauvaise foi, qui date de plus d'un mois. Visite fortuitement prolongée (talk) 18:27, 19 July 2015 (UTC)[reply]

Hmmm, il ne me semble pas avoir vu de requêtes à ce propos sur Wikidata:Administrators' noticeboard mais je peux me tromper. Quoi qu'il en soit, je suis pour laisser couler. Passons à autre chose car je n'ai pas vu d'autres propos de ce genre depuis. Pamputt (talk) 19:54, 19 July 2015 (UTC)[reply]

Vu. Visite fortuitement prolongée (talk) 20:18, 19 July 2015 (UTC)[reply]

Avez vous vu passer les modifications dans le domaine linguistique de TomT0m le 16 ? Visite fortuitement prolongée (talk) 20:18, 19 July 2015 (UTC)[reply]

J'ai regardé rapidement. Parlez-vous de ce genre de modifications ? Si oui alors je pense qu'il faudrait en discuter avant de se lancer dans une guerre d'édition. Je vais contacter Tomtom pour en parler. La première chose à faire est de se mettre d'accod sur une façon de faire, quitte à créer une nouvelle propriété si on n'arrive pas à un consensus avec les propriétés actuelles. Pamputt (talk) 05:20, 20 July 2015 (UTC)[reply]

« Parlez-vous de ce genre de modifications ? » →‎ Oui, par exemple il écrit que « the set of all chinese languages is a subset of the set of all languages » (ce qui est vrai) puis, quelques minutes après, il supprime le triplet Q45961 P279 Q20643070, où Q45961 correspond à l'ensemble des langues chinoise, et Q20643070 correspond à l'ensemble des langues humaines.

Avant ces modifications il y avait la chaine Q9186 P279 Q7033959 P279 Q7850 P279 Q45961, après il y a la chaine Q9186 P31 Q20671151 P279 Q45961, où il n'est plus possible de savoir que Cantonese (Q9186) est un sous-ensemble de Yue Chinese (Q7033959) et de Chinese (Q7850).

Les modifications Special:Diff/231704974 et Special:Diff/231707226 provoquent des « violations de contraintes » : P220, P221, P282, P305, P1098, P37, P103, P364, P407, P1412. Visite fortuitement prolongée (talk) 19:50, 20 July 2015 (UTC)[reply]

« je pense qu'il faudrait en discuter avant de se lancer dans une guerre d'édition » →‎ Vous noterez que je n'ai jusqu'à présent reverté aucune de ces modifications du 16. Visite fortuitement prolongée (talk) 19:50, 20 July 2015 (UTC)[reply]

« si on n'arrive pas à un consensus avec les propriétés actuelles. » →‎ Un consensus a été atteint dans le Projet:Langues (ici, ici et là pour les différentes points concernés par ces modifications du 16). Visite fortuitement prolongée (talk) 19:50, 20 July 2015 (UTC)[reply]

Bon alors on va essayer de régler ce différent au mieux. Je lui ai laissé un message sur sa page de discussion où il semble vouloir éviter une guerre d'édition. Je te remercie donc de ne pas être rentrer là dedans. Maintenant concernant le consensus, les liens que tu m'as donné implique 2 personnes différentes à chaque fois. Du coup la décision d'utiliser instance of (P31) : langue et subclass of (P279) pour gérer la hiérarchie des langues a été prise à 3 ou 4 personnes maximum. C'est pas mal mais il faut comprendre que rien n'a été décidé « officiellement ». Je pense que pour régler l'affaire une fois pour toute, il faudrait préparer un vote qui donne le choix entre les différentes propositions (la proposition qui est la majoritaire actuellement et qui correspond à celle que tu soutiens, la position défendu par TomT0m ainsi qu'éventuellement d'autres). Je n'ai pas le temps de m'en charger pour le moment mais je crois qu'on va devoir passer par là. Pour le cas concret de Mandarin (Q9192), TomT0m est ce que tu accepterais que l'on reviennes à la version de Visite fortuitement prolongée en attendant de préparer un vote ? Comme je te l'ai indiqué sur ta page de discussion (j'avais pas vu que tu parlais français), le plus simple pour le moment est d'avoir quelque chose d'homogène de sorte que si on doit changer quelque chose par bot, ça pourra se faire très facilement. Pamputt (talk) 20:22, 20 July 2015 (UTC)[reply]

Quelles sont les capacités de nuisance de TomT0m ? Quelles sont ses pouvoirs coercitifs ? Peut-il nous empécher d'utiliser P279 autrement que comme lui veut ET nous empécher d'utiliser une autre propriété ? Visiblement il n'est pas parvenu à fusionner parent taxon (P171) (avec P279), mais c'est à ma connaissance la seule propriété de classement spécialisée qui reste. Visite fortuitement prolongée (talk) 19:23, 21 July 2015 (UTC)[reply]

Merci de remédier à ces attaques personnelles. J'aimerais qu'on se concentre sur le fond et la manière de régler ce différent au mieux et la manière dont vous vous y prenez ne me semble clairement pas la plus adéquate. Pamputt (talk) 21:03, 21 July 2015 (UTC)[reply]

Position de TomT0m

Alors ma position est motivée par la définition de sous classe de, qui veut dire en gros sous ensemble de ou type particulier de. Sa définition est donnée à la fois sur la page de la propriété et sur des pages comme help:BMP. À partir de là quand sur une décision communautaire on a décidé de supprimer la propriété famille de langue et d'autres propriétés de typage spécialisé c'était pour harmoniser le système de typage en utilisant instance de et sous classe de parce qu'on a décidé que c'était à la fois suffisant pour le projet et bénéfique d'harmoniser le système de typage sur tout le projet et pas d'avoir 50 propriétés spécialisées pour 42 domaines quand on peut faire la même chose avec 2 propriétés classiques. Mais ... C'est une aberation de les utiliser incorrectement en ne respectant pas leur définition. Donc je comprend que la décision de supprimer famille de langue ne soit pas comprise et acceptée, mais ça rend les choses pires de pas chercher à la comprendre ... Donc non, je suis pas d'accord. Par définition, si chaque langue est une instance de langue, chaque famille en est un sous ensemble et donc une sous classe. Ce n'est pas une question de consensus mais de cohérence avec les choix communautaires. Pour le reste je veux bien ne pas m'opposer mais c'est juste contre productif et mène à des incohérences logiques. Tant que ce sera pas compris on avancera pas. author TomT0m / talk page 22:13, 20 July 2015 (UTC)[reply]

@TomT0m: J'ai créé une sous-section afin d'aérer un peu la discussion. Je ne connaissais pas l'existence de Help:BMP, c'est en effet une bonne base de départ pour des discussions un minimum formalisée. Donc, pour être sûr de bien comprendre ta position, prenons un exemple : French (Q150). Tu écris « si chaque langue est une instance de langue, chaque famille en est un sous ensemble et donc une sous classe », donc French (Q150) instance of (P31) language (Q34770). Si j'ai bien interprété ton propos, qui est également ce que je comprend de Help:BMP, alors on peut passer à la seconde partie (« chaque famille en est un sous ensemble et donc une sous classe »). D'après Help:BMP, on trouve les définitions suivantes pour subclass of (P279) :

toutes les instances de la classe X appartiennent à la classe Y
les instances de X sont également des instances de Y

On a language (Q34770) qui est une sous-classe de languoid (Q17376908) tout comme language family (Q25295) ; language (Q34770) et languoid (Q17376908) sont donc bien des classes. Si on reprend l'exemple de French (Q150) , ça ne me choque pas de lire que French (Q150) appartient à Oïl (Q37351). Autrement dit, si on reprend les définitions de Help:BMP, French (Q150) est une instance de Oïl (Q37351) ou bien French (Q150) appartient à la classe Oïl (Q37351). Du coup, j'ai du loupé quelque chose dans ton raisonnement car sinon on est d'accord.

Quoi qu'il en soit, le but n'est pas de me convaincre - j'essaie juste de comprendre - mais plutôt de trouver une issue à ce différent. Du coup, un vote de la communauté qui s'intéresse à la linguistique et aux langues afin de trancher cette question te parait-il opportun ? Pamputt (talk) 05:48, 21 July 2015 (UTC)[reply]

J'ai du mal avec l'idée de vote pour quelque chose qui relève uniquement de la logique :) Ce serait comme voter pour savoir si une expérience scientifique ou une démonstration mathématiques sont politiquement acceptable ... En fait le soucis ici c'est qu'on a choisi il y a quelque temps une politique de typage avec des propriétés génériques, comme ça se fait habituellement avec d'autres ontologies, en pensant que ce serait bénéfique pour tous le projet de pouvoir utiliser les mêmes concepts et les mêmes templates et mutualiser le travail, plutôt que de se transformer en tour de babel de propriétés spécialisées. Ça demande un effort de compréhension de ce que sont instance of (P31) et subclass of (P279) mais au final tout le monde y gagne à mon avis.

Sinon il y a un truc qui marche pas dans ton raisonnement, mais c'est normal c'est une des difficultés justement : language (Q34770) [...] est une sous-classe de language family (Q25295). Non. OK pour langue sous classe de langoides, mais pas pour famille de langues. En rapide : si langues germaniques ou langues indo-européennes sont des familles de langue, par exemple, alors oui on a bien

⟨ langues germaniques ⟩ subclass of (P279) ⟨ langue ⟩

et

⟨ langues indo-européennes ⟩ subclass of (P279) ⟨ langue ⟩

. Par contre on ne peut pas avoir

⟨ langue ⟩ subclass of (P279) ⟨ famille de langue ⟩

, ça se montre facilement:

Le français est une langue indo européenne. Donc
⟨ français ⟩ instance of (P31) ⟨ langue indo européenne ⟩
marche sans soucis. Après comme langue indo européenne est une sous classe de langue, on en déduit
⟨ français ⟩ instance of (P31) ⟨ langue ⟩
. Jusque là tout va bien. Mais si on recommence avec
⟨ langue ⟩ subclass of (P279) ⟨ famille de langue ⟩
... ça marche plus car on déduit
⟨ français ⟩ instance of (P31) ⟨ famille de langue ⟩
... euh wait, le français n'est pas une famille à lui tout seul, c'est une langue avec sa grammaire, son vocabulaire ... incohérence logique.

J'ai écris Help:Classification pour expliquer comment on traite ce genre de cas, mais c'est pas traduit en français pour l'instant et j'ai pas encore de support communautaire dans WD:RfC pour le faire valider comme page d'aide officielle de la communauté, mais si tu as des commentaires à faire dans l'appel à commentaire qui va bien n'hésite pas :) L'idée c'est que la notion de classe ne suffit pas en soit, il faut monter d'un cran et avoir des classes de classes, ou ensemble d'ensemble pour résoudre ce problème. Si on utilise instance de (nature en français mais cet intitulé n'est pas très heureux en fait)

⟨ langue indo européenne ⟩ instance of (P31) ⟨ famille de langue ⟩

le problème disparait. author TomT0m / talk page 06:46, 21 July 2015 (UTC)[reply]

Il y a un truc qui a bien marché quand j'ai expliqué ça pour le projet subdivision administrative, c'est de faire 3 colonnes

exemple de langues	classes de langues	type de classes
Français, Anglais, Russe ...	Langue indo européenne, langue germanique, dialecte du cantonais,	famille de langue, famille de dialecte d'une langue, famille de langoide

L'idée c'est qu'on a plusieurs niveaux de conceptualisation et qu'on ne peux pas passer d'un niveau de conceptualisation à l'autre n'importe comment : les objets de bases sont les langues et les langoides eux même. On les regroupe en famille, et on passe au niveau 1. Après il y a différent type de familles (c'est vrai pour ce projet particulier mais c'est encore plus vrai pour le projet en entier) et pour savoir lequel on relie des objets de la deuxième colonnes et de la troisième avec instance de, mais jamais avec sous classe de pour éviter de se retrouver avec des paradoxes style le français est une famille de langue. Il y a un principe pour trouver les éléments de la colonne 0, le principe type/jeton : les jetons sont en général les objets ou les évènements du monde réel. Les objets du niveau 1 sont des ensembles d'objets du monde réel ou d'événements. Ça marche relativement mal pour la les langues vu que les objets de bases d'une langue dans ce principe ce sont les écrits ou les paroles qu'on échange, et que le français est une classe de communications dans ce cas ... mais bon on peut tricher un peu et dire que le français c'est la grammaire définie par l'académie française par exemple. Ou décaler le tableau et rajouter une colonne à gauche. Bon, j'en ai encore beaucoup trop dit /o\

A part ça j'ai cru comprendre qu'il y avait une contraire violée dans l'histoire : c'est à elle d'être corrigée en accord avec ces principes généraux qui sont petits à petit digérés par le projet, pas l'inverse ... author TomT0m / talk page 06:46, 21 July 2015 (UTC)[reply]

« <langues germaniques> sous-classe de (P279) miga <langue> » →‎ C'est ça, continuez à nous prendre pour du caca en faisant exprès de ne pas utiliser d'identifiant Wikidata (et je ne parle pas de miga). Visite fortuitement prolongée (talk) 19:23, 21 July 2015 (UTC)[reply]

« <langues indo-européennes> sous-classe de (P279) miga <langue> » →‎ Mais j'en n'ai rien à foutre de « langues indo-européennes » ! Ce qui nous intéresse c'est Indo-European (Q19860) et les autres fiches Wikidata de languoïdes. Visite fortuitement prolongée (talk) 19:23, 21 July 2015 (UTC)[reply]

« langue indo européenne [instance de] famille de langue » →‎ Il faut rire ou il faut pleurer ? Visite fortuitement prolongée (talk) 19:23, 21 July 2015 (UTC)[reply]

« je comprend que la décision de supprimer famille de langue ne soit pas comprise et acceptée » →‎ Encore des propos insultants.

Il faut deviner que par « famille de langue » vous voulez dire « la propriété P133 famille de langue ». Les propos explicites et les identifiants Wikidata, c'est pour les chiens ?
La propriété « P133 famille de langue » n'existe plus, elle a été renommée en « P133 superfamille de langue » (par moi).
Accusation infondée d'incompréhension.
Accusation infondée d'opposition, et alors que Pamputt a voté pour (!).
Pas d'accusation claire ni de mention explicite de Pamputt, Visite fortuitement prolongée ou je ne sais qui, mais utilisation d'allusion (« je comprend que ») et de la voix passive (« ne soit pas comprise et acceptée »).
Qu'est-ce que P133 vient foutre dans cette discussion ?

Visite fortuitement prolongée (talk) 19:23, 21 July 2015 (UTC)[reply]

Toujours rien à dire sur Special:Diff/231707556 ? Visite fortuitement prolongée (talk) 19:23, 21 July 2015 (UTC)[reply]

@Visite fortuitement prolongée: Désolé si je t'ai offensé mais c'est pas du tout mon intention, et je m'en excuse si c'est le cas. Toujours rien à dire sur Special:Diff/231707556 Ben si, Pamputt a parfaitement résumé au dessous, ce n'est pas une sous classe mais une instance ... à peu prêt toutes mes interventions ici ont pour but d'expliquer ça donc je dois vraiment très mal expliquer /o\. author TomT0m / talk page 12:33, 23 July 2015 (UTC)[reply]

« Pamputt a parfaitement résumé au dessous » →‎ Citation ? Visite fortuitement prolongée (talk) 20:20, 23 July 2015 (UTC)[reply]

« ce n'est pas une sous classe mais une instance ... à peu prêt toutes mes interventions ici ont pour but d'expliquer ça donc je dois vraiment très mal expliquer /o\. » →‎ Ce n'est pas comme si vous répétiez depuis un ou deux ans qu'une fiche Wikidata peut être une instance et une sous classe en même temps, ce n'est pas commme si vous et moi en avions discuté il y a deux mois, ce n'est pas comme si j'avais écrit dans votre page de discussion des tableaux que vous auriez qualifiés de « Seems OK to me ». Ah mince, Pamputt va me bannir pour « attaques personnelles » /o\. Adieu. Visite fortuitement prolongée (talk) 20:20, 23 July 2015 (UTC)[reply]

@Visite fortuitement prolongée: Pardon je reformule : une instance de famille de langue en l'occurence ... je répondais sur le diff précis cité. author TomT0m / talk page 13:30, 24 July 2015 (UTC)[reply]

@Visite fortuitement prolongée: je n'ai rien vu d'offensant dans les propos tenus ci-dessus par TomT0m. Merci donc de ne pas réagir au quart de tour et d'envenimer la discussion. J'espère que la discussion pourra rester courtoise et j'essaierai d'y veiller. Pour le fond, je vais y répondre sous peu. Pamputt (talk) 20:59, 21 July 2015 (UTC)[reply]

@TomT0m: ok je comprend le point sur le fait que French (Q150) ne puisse as être stricto sensu une sous-classe de Oïl (Q37351) étant donné que language (Q34770) n'est pas une language family (Q25295) (au contraire des exemples donnés dans Help:BMP). Bon du coup, sur quoi sommes-nous d'accord ?

on attribut pour chaque langue la valeur language (Q34770) pour la propriété instance of (P31)
idem pour les familles de langues qui prennent la valeur language family (Q25295) pour la propriété instance of (P31)

Si on est d'accord avec ça alors il reste à trouver la meilleure manière d'indiquer la hiérarchie entre les langues et les familles de langues. Quelle est ta proposition ? Pamputt (talk) 21:11, 21 July 2015 (UTC)[reply]

Je vais répondre à la deuxième question en premier: la meilleure manière d'indiquer les hiérarchie.

Utiliser subclass of (P279).

⟨ langue germanique ⟩ subclass of (P279) ⟨ langue indo européenne ⟩

veut dire "toute langue germanique est une langue indo Européenne.

Du coup la réponse à la première question : "on attribut pour chaque langue la valeur language (Q34770) pour la propriété instance of (P31)" => C'est inutile. On a

⟨ langue indo européenne ⟩ subclass of (P279) ⟨ langue ⟩

, donc on sait déja que c'est une langue. subclass of (P279) est spécialement faite pour créer des hiérarchies, justement, pardéfinition : toute instance de sous classe est une instance de la classe parente. C'est parfaitement adapté pour ce qui est phylogénie des langues ( http://pagana.wikia.com/wiki/Cat%C3%A9gorie:Arbre_phylog%C3%A9n%C3%A9tique_des_langues_europ%C3%A9ennes ) qui sont à la mode et ou les langues sont classées hiérarchiquement en fonction de leur histoire et des langues qui leurs sont proches.

Je suis pour la parcimonie : on a ce qu'il faut en propriété génériques, on a pas besoin de plus. author TomT0m / talk page 12:16, 23 July 2015 (UTC)[reply]

antiparticle

antiparticle (P2152) --Tobias1984 (talk) 13:15, 4 October 2015 (UTC)[reply]

binding energy

binding energy (P2154) is ready. --Tobias1984 (talk) 13:57, 4 October 2015 (UTC)[reply]

mass excess

mass excess (P2160) is ready. --Tobias1984 (talk) 14:41, 4 October 2015 (UTC)[reply]

Quel modèle ?

Bonjour, Pamputt. J'aimerais créer l'article Nekkour sur Wikipédia. Saurais-tu (sauriez-vous ?) quel modèle d'infobox je peux utiliser pour que des données de https://www.wikidata.org/wiki/Q6989822 y apparaissent ? Cordialement. --Frenchinmorocco (talk) 09:38, 16 October 2015 (UTC)[reply]

Bonjour Frenchinmorocco, l'infobox à utiliser semble être Modèle:Infobox Ville du Maroc. Cela dit, ce modèle ne semble pas encore avoir été mis à jour pour récupéré les informations directement depuis Wikidata. Cela dit, tu peux forcer l'utilisation des données Wikidata en mettant quelque chose du genre {{#property:p856}} comme valeur pour certains paramètres de l'infobox. Bien sûr, il faut remplacer p856 par le numéro de la propriété correspondante. Par exemple il faut utiliser {{#property:p1082}} population (P1082) pour le champ « population ». Pamputt (talk) 05:25, 17 October 2015 (UTC)[reply]

Merci Pamputt pour ces infos. J'espérais qu'il existait une infobox du type Infobox Biographie2. Snif ! Là, cela me semble bien compliqué, mais je vais quand même essayer. Cordialement. --Frenchinmorocco (talk) 07:22, 23 October 2015 (UTC)[reply]

help

Hello there! (It's a little confusing that the message you left on my user page greets me in german language although you don't seem to speak it... :-) )

I sure could use some help figuring out some things here. There seem to be a lot of rough edges in software, tools and other things that are a holdup and can make you stumble.

Here's my current one:

I fail to merge Q5975028 into Q5975028. For one thing, there's no button to find on the page that you can use to initiate a merge or deletion (discussion) or flag as a duplicate – or even just point you to instructions. I'd like to file a bugreport or something if it's not already a known problem and being worked on. If you can tell me about the places for such reports/discussions/... or the situation on this specific problem that would be nice.

Digging in the help pages i found instructions for merging objects but they don't work. Special:MergeItems refuses to merge because it claims that Q5975028 is not empty. I moved what i can and the item seems empty now but the history page still reports a size of 200-and-something bytes. I'd like to understand what is happening...

The merge gadget did the trick now but, still, the questions remain. It is hard to find and not accessible to anonymous contributors, i guess.--Frysch (talk) 10:36, 18 November 2015 (UTC)[reply]

Hi Frysch, indeed my German is really poor. So we will continue in English. I do not know how to reply properly to your question because I do the merge using the gadget you found. Anyway, the place to ask such questions is on Wikidata:Project chat. You could ask there to get some answers. Pamputt (talk) 17:09, 18 November 2015 (UTC)[reply]

2016-02 fusions

Q1851541 et Q6486930, Q5908782 et Q20723424, Q10964305 et Q20818064, Q5972851 et 20819354, Q5908791 et Q20824110, Q5908780 et Q20827435, et les autres items blanchis par Loup Solitaire 81 à transformer en redirections. Visite fortuitement prolongée (talk) 21:07, 9 February 2016 (UTC)[reply]

Done Je viens de m'occuper des éléments que tu m'as indiqué. Je regarderai plus tard s'il y en a d'autres. Merci pour le signalement. Pamputt (talk) 19:35, 10 February 2016 (UTC)[reply]

Q17558136 et Q21694406 ? Visite fortuitement prolongée (talk) 21:12, 27 February 2016 (UTC)[reply]

Q9854845 et Q20064874, Q9472681 et Q10104432. Visite fortuitement prolongée (talk) 21:29, 15 March 2016 (UTC)[reply]

Merci c'est maintenant fusionné. Pamputt (talk) 05:55, 17 March 2016 (UTC)[reply]

Q4921933 et Q17332977, Q3217522 et Q12641781, Q6805227 et Q12636625. Visite fortuitement prolongée (talk) 20:10, 24 March 2016 (UTC)[reply]

Done Pamputt (talk) 12:36, 26 March 2016 (UTC)[reply]

Wikidata:WikiProject Taxonomy

Hi! Looks like that I can not edit a single section anymore since this translation edits. Please fix it. --Succu (talk) 18:15, 2 June 2016 (UTC)[reply]

@Succu: it should be fixed now. Sorry for this inconvenience. Pamputt (talk) 16:40, 3 June 2016 (UTC)[reply]

Thx, but what was the problem? I had no idea how to fix this. --Succu (talk) 17:54, 5 June 2016 (UTC)[reply]

@Succu: I do not know exactly but I think there were too much "translate" tag, specially aroung the section title (equal sign). Yet, not sure because it has worked like that in the past. So it appears that the Translation function of Mediawiki is now able to parse correctly the section title between two "translate" tags. Pamputt (talk) 18:12, 5 June 2016 (UTC)[reply]

OK, thanks. The translation extension is very odd, but really I refuse to try to understand it. :( --Succu (talk) 18:38, 5 June 2016 (UTC)[reply]

RegEx

A site that I think is useful when it comes to RegEx is http://regexr.com. You can test RegEx there and there's a cheatsheet. Mbch331 (talk) 19:42, 20 September 2016 (UTC)[reply]

Thanks Mbch331 Pamputt (talk) 19:47, 20 September 2016 (UTC)[reply]

@Mbch331: I added a regexp on P3188 (P3188). Could you check I did not make any mistake? Thanks in advance. Pamputt (talk) 05:47, 21 September 2016 (UTC)[reply]

I fixed the regex. The minus sign (as used in the id for Marie Curie) was missing and the multiplier (+) was inside the square brackets instead of outside. Mbch331 (talk) 06:28, 21 September 2016 (UTC)[reply]

Unused properties

This is a kind reminder that the following properties were created more than six months ago: mass excess (P2160), binding energy (P2154). As of today, these properties are used on less than five items. As the proposer of these properties you probably want to change the unfortunate situation by adding a few statements to items. --Pasleim (talk) 19:23, 17 January 2017 (UTC)[reply]

@Pasleim: indeed. Maybe that ArthurPSmith could use his bot to fill these values? Pamputt (talk) 18:46, 18 January 2017 (UTC)[reply]

I can look into it but I think I'm pulling everything I can from the source I was using for nuclear data already... Maybe another source is needed for that information? ArthurPSmith (talk) 18:49, 18 January 2017 (UTC)[reply]

@ArthurPSmith: this file from NNDC contains both information. However, it needs a bit of work to parse it. Pamputt (talk) 18:54, 18 January 2017 (UTC)[reply]

Thanks, I'll look into it! Probably will be a couple of weeks before I can get it working... ArthurPSmith (talk) 19:01, 18 January 2017 (UTC)[reply]

Ping

Re this: {{Ping}} don't work for IP addresses. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:57, 18 January 2017 (UTC)[reply]

@Pigsonthewing: thank you. I was not sure. Pamputt (talk) 18:44, 18 January 2017 (UTC)[reply]

Locative

As you added statements about locative to languages, I thought you might want to comment on Wikidata:Property_proposal/locative.
--- Jura 07:10, 5 March 2017 (UTC)[reply]

I just noticed that you used has grammatical mood (P3161) instead of has grammatical case (P2989) for this (e.g. [1]). What's the easiest way to move them over?
--- Jura 07:13, 5 March 2017 (UTC)[reply]

Reverts

Ciao mr(s) Pamputt,

You keep reverting all my changes to FreeBASIC (Q195929) though we're still discussing on the talk-page saying that changes need to be done. Why you do it, are you the big boss here or what? Klaas `Z4␟` V: 19:33, 2 May 2017 (UTC)[reply]

Hi KlaasZ4usV. Sorry if I hurt you with the revert. It was not my intent. I did it only to be consistent with other software pages. Now, I hope that other people will participate to the discussion in order to get more opinion. Pamputt (talk) 19:36, 2 May 2017 (UTC)[reply]

Property talk:P3961

Hi Paumputt,

Please avoid marking talk pages for translations. It can only work for content pages. Otherwise people's comments would need to be translated or marked for translation. You could create a "translatable Help page" instead (see the link just below the property documentation template).
--- Jura 03:59, 23 May 2017 (UTC)[reply]

Hi Jura1! I do not know if there is any consensus or any debate/discussion about this topic. From my point of view there is absolutely no problem to translate only a part of a given page. I marked Property talk:P3961 for translation in order to show that it is possible to do it and that it works fine. Yet, I will consider to follow the example that you gave. Pamputt (talk) 08:21, 25 May 2017 (UTC)[reply]

It's technically feasible, but the extension is to translate content pages. Otherwise, you'd need to mark every comment for translation, just to keep discussions in sync. For localized headers, you could just use templates.
--- Jura 08:34, 25 May 2017 (UTC)[reply]

signalement d'une guerre d'édition sur le féminin de "auteur"

Bonjour

A propos de la féminisation du terme "auteur" (page sur laquelle vous êtes intervenu pour mentionner "auteure") https://www.wikidata.org/w/index.php?title=Q15980158&offset=&limit=500&action=history

Nous avons des éléments pour comparer les usages de ces deux termes dans les communautés scientifiques et universitaires ; des éléments objectifs, fort différents des arguments idéologiques employés par les quelques rares hommes (deux ?) qui essayent d'imposer "autrice", parce qu'ils trouvent "moche" "auteure", le terme privilégié par les auteures… et par leurs collègues.

Sur "Isidore", moteur de recherches en sciences sociales, en date du 29 mai 2017

https://www.rechercheisidore.fr/search

37005 résultats pour "auteure"

et

1644 résultats pour "autrice"

au pluriel

36215 résultats pour "auteures"

et

989 résultats pour "autrices"

Nous obtenons des résultats similaires si nous faisons une recherche sur "google scholar", en limitant les résultats à "langue française" et "écrits après 2000" [pour éviter les formes médiévales et donc anciennes "autrice").

Bien cordialemen

ED --Droit de retrait 03 (talk) 12:59, 29 May 2017 (UTC)[reply]

2017-07 suppressions

Bonjour, et merci pour vos suppressions de Q21010336 et Q21010338. Pourriez vous faire de même avec Q20671151 ? Visite fortuitement prolongée (talk) 20:32, 4 July 2017 (UTC)[reply]

Done Pamputt (talk) 20:52, 4 July 2017 (UTC)[reply]

Merci. Visite fortuitement prolongée (talk) 21:03, 4 July 2017 (UTC)[reply]

https in schema.org (Q5)

I understand your revert in Q5, but it was marked as an error by VladimirAlexiev at https://github.com/schemaorg/schemaorg/issues/280#issuecomment-314409482 . Currently we have 508 schema.org references, all of them are http-based, except for Q5. It is possible to use https, but my point of view that we should do it more uniformly, either http or https everywhere. --Lockal (talk) 13:57, 28 August 2017 (UTC)[reply]

Hi Lockal! I understand your point now. I agree that it should be unified. Vladimir Alexiev, could we consider to move all the references to the https version since it is clearly supported by schema.org? Pamputt (talk) 16:03, 28 August 2017 (UTC)[reply]

@Lockal, Pamputt: The canonic schema URLs use http. If someone produces some RDF data from WD using the schema.org correspondences and those use https, the RDF data would be wrong. It's like if I was to choose to call you Lockals and Pamputts because I like it better --Vladimir Alexiev (talk) 15:51, 2 September 2017 (UTC)[reply]

@Vladimir Alexiev: ok, I was not aware about the "canonical form" of scheme.org. So, as it uses "http", I reverted myseld on human (Q5). Pamputt (talk) 21:14, 2 September 2017 (UTC)[reply]

It's not just a name, it's the difference between a secure and an insecure connection. if there is a https possible, it should always be preferred to the insecure HTTP one. Sänger (talk) 21:19, 2 September 2017 (UTC)[reply]

These "links" are not supposed to be valid in terms of web protocols. Check mw:Wikibase/Indexing/RDF_Dump_Format#Full_list_of_prefixes: all of these links are http, many of them are broken (i.e. wikidata uris redirect to [2]). And actually, it is not as replaceable, as I initially thought: if you replace http with https in this query, it will break. And results will contain http://www.wikidata.org/entity/Qxxx identifiers, which is also not easy to change due to backwards compatibility and federated queries. --Lockal (talk) 16:38, 3 September 2017 (UTC)[reply]

So what's to be done by whom to get rid of the outdated and insecure http-stuff and stick to the right ans secure https? Just change something back to the wrong address without the "s" can't be right. Sänger (talk) 19:43, 3 September 2017 (UTC)[reply]

I guess it should be possible to replace http to https in tripples referring to http://www.wikidata.org, http://www.w3.org, http://creativecommons.org and http://schema.org and reindex blazegraph. Also some query conversion is needed either in WDQS or Blazegraph directly for converting specific http prefixes to https. @Smalyshev (WMF):, your opinion? --Lockal (talk) 08:53, 11 September 2017 (UTC)[reply]

Please note that the URLs are identifiers in RDF. That means http://schema.org and https://schema.org are as different as http://google.com and http://bing.com. This means querying for one would not find the other. Having two kind of IDs for the same thing is a very bad idea. It is much better to have non-ideal ID than to have two different kinds of IDs. Thus, either everything - I mean every schema.org URL in the RDF - is switched to https, or nothing should be. Doing it piecemeal is the worst way possible of doing it. Moreover, since we are talking linked data here, and vocabulary used by many data sets beyond our own, we'd still have issues with using different IDs to mean the same thing, and unless overwhelming majority of data sets uses https, I think we're better to stay with http.

Also note that these URLs are not specifying any fetchable data that you are going to use anytime soon. It is, in vast majority of cases, used as an ID and only as an ID, not as an address to communicate over HTTP(S) with. Thus, changing it to https serves little useful purpose - since nobody is going to read data from this URL, what's the point of changing it? Smalyshev (WMF) (talk) 19:59, 11 September 2017 (UTC)[reply]

Relation between ChEBI ID (P683) and IEDB Epitope ID (P4168)?

I am not sure I understand the relation between ChEBI ID (P683) and IEDB Epitope ID (P4168). Can you please explain? That is, why should they be linked with a related property (P1659)?--Egon Willighagen (talk) 06:55, 30 September 2017 (UTC)[reply]

Hi Egon Willighagen, you should ask to Gstupp since I only copied the information that he filled in the property proposal when I created the property. Pamputt (talk) 09:37, 30 September 2017 (UTC)[reply]

I added the see also because IEDB Epitope IDs for small molecules are cross-referenced by IEDB to ChEBI. Gstupp (talk) 21:36, 2 October 2017 (UTC)[reply]

I ping Egon Willighagen just to be sure he will read your reply. Pamputt (talk) 01:57, 3 October 2017 (UTC)[reply]

Thanks, all clear! --Egon Willighagen (talk) 15:27, 3 October 2017 (UTC)[reply]

Structured Commons newsletter, October 25, 2017

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter. Do inform others who you think will want to be involved in the project!

Community updates

Rama published an article about Structured Commons in Arbido, a Swiss online magazine for archivists, librarians and documentalists: original in French, illustrated and the article translated in English.
We now have a dedicated IRC channel: wikimedia-commons-sd ^webchat

Things to do / input and feedback requests

Join the community focus group!
Translation. Do you want to help out translating messages about Structured Data on Commons from English to your own language? Sign up on the translators page.
The documentation and info pages about Structured Data on Commons have received a thorough update, in order to get them ready for all the upcoming work. Obsolete pages were archived. There are undoubtedly still a lot of omissions and bits that are unclear. You can help by editing boldly, and by leaving feedback and tips on the talk pages.
We have started to list tools, gadgets and bots that might be affected by Structured Commons in order to prepare for a smooth transition to the new situation. You can help by adding alerts about/to specific tools and developers on the dedicated tools page. You can also create Phabricator tasks to help keep track of this. Volunteers and developers interested in helping out with this process are extremely welcome - please sign up!
Help write the next Structured Commons newsletter.

Presentations / Press / Events

Structured Data on Commons was presented at Wikimania 2017 in Montréal for a packed room. First design sketches for search functionality were discussed during a breakout session. Read the Etherpad reports of the presentation and the breakout session.
Katherine Maher, Executive Director of the Wikimedia Foundation, answered questions on Quora. One of her answers, mentioning Structured Data on Commons, was republished on Huffington Post.
Sandra Fauconnier, Amanda Bittaker and Ramsey Isler from the Structured Commons team will be at WikidataCon. Sandra presents Structured Commons there (with a focus on fruitful collaboration between the Wikidata and Commons communities). If you attend the conference, don't hesitate to say hi and have a chat with us! (phabricator task T176858)

Team updates

Two new people have been hired for the Structured Data on Commons team. We are now complete! :-)

Ramsey Isler is the new Product Manager of the Multimedia team.
Pamela Drouin was hired as User Interface Designer. She works at the Multimedia team as well, and her work will focus on the Structured Commons project.

Partners and allies

We are still welcoming (more) staff from GLAMs (Galleries, Libraries, Archives and Museums) to become part of our long-term focus group (phabricator task T174134). You will be kept in the loop of the project, and receive regular small surveys and requests for feedback. Get in touch with Sandra if you're interested - your input in helping to shape this project is highly valued!

Research

Design research is ongoing.

Jonathan Morgan and Niharika Ved have held interviews with various GLAM staff about their batch upload workflows and will finish and report on these in this quarter. (phabricator task T159495)
At this moment, there is also an online survey for GLAM staff, Wikimedians in Residence, and GLAM volunteers who upload media collections to Wikimedia Commons. The results will be used to understand how we can improve this experience. (phabricator task T175188)
Upcoming: interviews with Wikimedia volunteers who curate media on Commons (including tool developers), talking about activities and workflows. (phabricator task T175185)

Development

In Autumn 2017, the Structured Commons development team works on the following major tasks (see also the quarterly goals for the team):

Getting Multi-Content Revisions sufficiently ready, so that the Multimedia and Search Platform teams can start using it to test and prototype things.
Determine metrics and metrics baseline for Commons (phabricator task T174519).
The multimedia team at WMF is gaining expertise in Wikibase, and unblocking further development for Structured Commons, by completing the MediaInfo extension for Wikibase.

Stay up to date!

Follow the Structured Data on Commons project on Phabricator: https://phabricator.wikimedia.org/project/profile/34/
Subscribe to this newsletter to receive it on a talk page of your own choice.
Join the next IRC office hour and ask questions to the team! It takes place on Tuesday 21 November, 18.00 UTC.

Warmly, your community liaison, SandraF (WMF) (talk)

Message sent by MediaWiki message delivery - 14:27, 25 October 2017 (UTC)[reply]

Structured Commons newsletter, December 13, 2017

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter. Do inform others who you think will want to be involved in the project!

Community updates

There was a IRC Office Hour about Structured Commons on November 21. You can read the log here.
Our dedicated IRC channel: wikimedia-commons-sd ^webchat

Things to do / input and feedback requests

NEW: Participate in a survey that helps us prioritize which tools are important for the Wikimedia Commons and Wikidata communities. The survey runs until December 22. Here's some background.
NEW: Help the team decide on better names for 'captions' and 'descriptions'. You can provide input until January 3, 2018.
NEW: Help collect interesting Commons files, to prepare for the data modelling challenges ahead! Continuous input is welcome.
Join the community focus group!
Do you want to translate messages and information about Structured Data on Commons from English to your own language? Sign up on the translators page.

Presentations / Press / Events

Presentation about Structured Commons and Wikidata, at WikimediaCon in Berlin.

Sandra presented the plans for Structured Commons during WikidataCon in Berlin, on October 29. The presentation focused on collaboration between the Wikidata and Commons communities. You can see the full video here.

Partners and allies

We are still welcoming (more) staff from GLAMs (Galleries, Libraries, Archives and Museums) to become part of our long-term focus group (phabricator task T174134). You will be kept in the loop of the project, and receive regular small surveys and requests for feedback. Get in touch with Sandra if you're interested - your input in helping to shape this project is highly valued!

Research

Research findings from interviews and surveys of GLAM project participants are being published to the research page. Check back over the next few weeks as additional details (notes, quotes, charts, blog posts, and slide decks) will be added to or linked from that page.

Development

The Structured Commons team has written and submitted a report about the first nine months of work on the project to its funders, the Alfred P. Sloan Foundation. The 53-page report, published on November 1, is available on Wikimedia Commons.
The team has started working on designs for changes to the upload wizard (T182019).
We started preliminary work to prototype changes for file info pages.
Work on the MediaInfo extension is ongoing (T176012).
The team is continuing its work on baseline metrics on Commons, in order to be able to measure the effectiveness of structured data on Commons. (T174519)
Upcoming: in the first half of 2018, the first prototypes and design sketches for file pages, the UploadWizard, and for search will be published for discussion and feedback!

Stay up to date!

Follow the Structured Data on Commons project on Phabricator: https://phabricator.wikimedia.org/project/profile/34/
Subscribe to this newsletter to receive it on a talk page of your own choice.
Join the next IRC office hour and ask questions to the team! It takes place on Tuesday, February 13, 18.00 UTC in wikimedia-office ^webchat.

Warmly, your community liaison, SandraF (WMF) (talk)

Message sent by MediaWiki message delivery - 16:32, 13 December 2017 (UTC)[reply]

Wikidata:Wiktionary/Ideas of tools

Salut !

As-tu vu la nouvelle page Wikidata:Wiktionary/Ideas of tools ? C'est une bien belle page, et j'trouve la dynamique sympa, même si j'pense qu'on devrait plutôt avoir un coin pour nos idées d'améliorations qui soit propre au Wiktionnaire. Enfin bon, j'ai balisé la page pour traduire l'intro en français et j'ai réalisé ensuite que j'suis pas admin de traduction ici (puisqu'on est sur Wikidata et pas sur Meta), mais que tu l'es ! Est-ce que tu pourrais passer y faire un tour pour activer la traduction, s'il te plais ? Merci d'avance et bonne fin d'année ! Noé (talk) 18:06, 30 December 2017 (UTC)[reply]

Salut Noé Oui j'avais vu cette page au moment où Lea Lacroix (WMDE) en avait parlé mais j'en été resté à la proposition de Lea et je n'avais pas vu les autres. Bref, c'est maintenant prêt pour la traduction. Pamputt (talk) 19:28, 30 December 2017 (UTC)[reply]

Pas seulement prêt, tu as aussi fait toute la traduction ! Merci ! Noé (talk) 21:09, 30 December 2017 (UTC)[reply]

Extra, merci beaucoup pour le boulot :) Lea Lacroix (WMDE) (talk) 17:33, 1 January 2018 (UTC)[reply]

Number of speakers of Northern Sami

Although the date is not precise, I think that the overall number of speakers is an important information and can't be omitted. I have added back the statement you had deleted, with the weighted average of the sampling dates as date and the qualifier "circa", as advised in Help:Dates for inexact dates.

Notification

Bonjour. Je ne sais pas me servir des notifications dans le bistro, alors je vous écris ici aussi: J'ai deux questions:

- Qui doit continuer la préparation que vous avez commencé ? Vous ? ou bien je peux le faire ?

- J'ai vu que vous n'avez pas marqué le code pour traduction. Par conséquent, on se retrouve à ne pas traduire toutes les propriétés et les éléments. J'avais fait le choix de traduire les requêtes aussi, ça me semblait plus facile pour le lecteur. Qu'en pensez-vous ? Vincent la tortue (talk) 13:31, 27 January 2018 (UTC)[reply]

Pour information

Bonjour Pamputt. Pour information, je me suis permis de t'envoyer un courriel. Nomen ad hoc (talk) 12:34, 27 February 2018 (UTC).[reply]

Structured Data on Commons Newsletter - Spring 2018

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter and contribute to the next issue. Do inform others who you think will want to be involved in the project!

Community updates

Our dedicated IRC channel: wikimedia-commons-sd ^webchat
Several Commons community members are working on ways to integrate Wikidata in Wikimedia Commons. While this is not full-fledged structured data yet, this work helps to prepare for future conversion of data, and helps to understand how Wikidata and Commons can work better together.
- Thanks to Jarekt and other contributors, some Commons templates can now be filled via Wikidata: {{Creator}} (Phabricator) and {{Institution}} (Phabricator). Work is ongoing on the {{Artwork}} template (Phabricator).
- Thanks to Mike Peel and others, Wikidata-powered infoboxes can now be added to Commons categories, with the template {{Wikidata Infobox}}. (Example)
- Multichill is working on an experimental workflow to upload images to Commons via Wikidata (and using metadata from Wikidata). See a part of it here.

Things to do / input and feedback requests

Join the community focus group!
Do you want to help out translating messages about Structured Data on Commons from English to your own language? Sign up on the translators page.
Contribute to the next newsletter.

Discussions held

Events

Wikimedia Conference, Berlin, 20-22 April (+ Learning Days 18-19 April): several sessions and workshops around Structured Commons
EuropeanaTech Conference, Rotterdam, 15-16 May: several presentations + a full workshop day on Monday 14 May about Wikidata and Structured Commons
Wikimedia Hackathon, Barcelona, 18-20 May: Structured Commons as a focus area.

Partners and allies

We are still welcoming (more) staff from GLAMs (Galleries, Libraries, Archives and Museums) to become part of our long-term focus group (phabricator task T174134). You will be kept in the loop of the project, and receive regular small surveys and requests for feedback. Get in touch with Sandra if you're interested - your input in helping to shape this project is highly valued!

Research

The research about GLAM contributions to Wikimedia Commons is concluded. A blog post on the Wikimedia blog provides a summary, and you can read the full results on meta.wikimedia.org.

Development

Prototypes will be available for Multilingual Captions soon.

Stay up to date!

Follow the Structured Data on Commons project on Phabricator: https://phabricator.wikimedia.org/project/profile/34/
Subscribe to this newsletter to receive it on a talk page of your own choice.
Join the next IRC office hour and ask questions to the team! The date for next quarter will be announced soon.

-- Keegan (WMF) (talk)

Message sent by MediaWiki message delivery - 19:48, 3 April 2018 (UTC)[reply]

Category:Canela language (Q36154942)

Bonjour,

Pourrais-tu jeter un coup d’œil à cet élément ? Sauf erreur, j'ai l'impression que ta fusion du 4 avril dernier (Special:Diff/661046148) est erronée et que canela et candoshi sont deux langues distinctes (en tout cas, il y a deux valeurs pour endangeredlanguages.com ID (P2192) différentes) et que Candoshi-Shapra (Q50934284) aurait dû être fusionné avec Candoshi-Shapra (Q642843) (mais je m'y perds, donc je veux bien ton avis avant de faire des bêtises).

Cdlt, VIGNERON (talk) 16:43, 1 May 2018 (UTC)[reply]

Salut VIGNERON, en effet j'ai fait n'importe quoi. C'était la période où je fusionnais en masse des éléments qui avaient été créés alors qu'ils n'auraient pas dû. Bref, merci de ton attention, c'est maintenant réglé. Pamputt (talk) 17:52, 1 May 2018 (UTC)[reply]

Ok, pas de problème, cela arrive à tout le monde (moi le premier) et c'est pour cela qu'il y a des patrouilleurs pour repérer ce genre d'erreur. Cdlt, VIGNERON (talk) 13:58, 2 May 2018 (UTC)[reply]

Property_talk:P3537#new_structure_of_the_internetsite_http://www.footballdatabase.eu

Salut Pamputt, vu que tu as créé la page property talk:P3537, je m'adresse à toi afin te jeter un coup d'oeil à comment au mieux adeapter Property:P3537 à l anouvelle structure du site internet http://www.footballdatabase.eu merci pour le temps de regarder ceci. Salutations cordiales. Robby (talk) 17:34, 12 June 2018 (UTC)[reply]

Demande de marquer des changements en traduction

Bonjour @Pamputt:,

Francophone aussi. J'ai changé la page wikidata:introduction. Voici les diff. J'aimerai la traduire dans notre bonne vieille langue de Molière. Pouvez-vous marquer les changements pour traduction, svp ?

Merci d'avance.

Cordialement.@Eihel

@Eihel: ça y est c'est fait. J'en ai profité pour retoucher quelques autres endroits. Tu peux maintenant traduire

Pamputt (talk) 22:45, 17 June 2018 (UTC)[reply]

Bonjour (tardif ou matinal) @Pamputt:, _a-y-est. C'est fait. C'est plus rapide qu'avec @Ash Crow: qui est dans les admins traduction. Cela fait depuis le 26 mai que j'attends qui me fasse les changements en traduction. Merci beaucoup. --Eihel (talk) 01:01, 18 June 2018 (UTC)[reply]

@Eihel: merci pour la traduction. Pour le reste, chacun a ses priorités et ses contraintes donc si une demande n'aboutit pas avec quelqu'un, on peut essayer avec quelqu'un d'autres (ce que tu as fait), c'est comme ça qu'on avance

Pamputt (talk) 08:05, 18 June 2018 (UTC)[reply]

Structured Data on Commons Newsletter - Summer 2018

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter and contribute to the next issue. Do inform others who you think will want to be involved in the project!

Community updates

Our dedicated IRC channel: wikimedia-commons-sd ^webchat
Since our last newsletter, the Structured Data team has moved into designing and building prototypes for various features. The use of multilingual captions in the UploadWizard and on the file page has been researched, designed, discussed, and built out for use. Behind the scenes, back-end work on search is taking place and designs are being drawn up for the front-end. There will soon be specifications published for the use of the first Wikidata property on Commons, "Depicts," and a prototype is to be released to go along with that.

Things to do / input and feedback requests

A workshop on what Wikidata properties Commons will need. This workshop will be open for the entire month of July 2018 at minimum.

Join the community focus group!
Do you want to help out translating messages about Structured Data on Commons from English to your own language? Sign up on the translators page.
Contribute to the next newsletter.

Discussions held

In late February there was a discussion around how Commons generally sees data being modeled.

The first discussion on copyright and licensing with Commons was held in March. This was a "high level" discussion, there will be a consultation later this summer about the deeper mapping of copyright and licensing in a structured way.
In April there was an exercise for GLAM partners in metadata and ontology mapping.
A discussion about the design for Multilingual Captions on the file page took place in May. You can still review the designs and leave feedback.
There was an IRC office hour in June to discuss progress so far and future plans.

Wikimania 2018

Three sessions about Structured Commons are officially scheduled for Wikimania 2018 - Cape Town, South Africa - July 2018.
- Wikimedia Commons and GLAM needs around the world (Friday 20 July, 10:30 local time)
- Structured Data on Wikimedia Commons and knowledge equity (Friday 20 July, 14:00 local time)
- Design challenge workshop: How can multilingual structured metadata bring knowledge equity to Commons? (Friday 20 July, 14:30 local time)
Structured Data on Commons is also a focus area during the Wikimania 2018 Hackathon. We will, among other things, do 'live' modelling of Wikidata properties for Commons - an offline spin-off of the community consultation taking place on wiki.

Partners and allies

We are still welcoming (more) staff from GLAMs (Galleries, Libraries, Archives and Museums) to become part of our long-term focus group (phabricator task T174134). You will be kept in the loop of the project, and receive regular small surveys and requests for feedback. Get in touch with Sandra if you're interested - your input in helping to shape this project is highly valued!
Structured Data on Commons was presented to GLAM audiences during EuropeanaTech 2018 in Rotterdam (15 May 2018) and at the Deutsche Digitale Bibliothek Forum in Berlin (4 June 2018).

Research

Two research projects about Wikimedia Commons are currently ongoing, or in the process of being finished:

Research:Curation workflows on Wikimedia Commons—a project that seeks to understand the current workflows of Commons contributors who curate media (categorize it, delete it, link to it from other projects, etc.).
Research:Technical needs of external re-users of Commons media—soliciting feedback from individuals and organizations that re-use Commons content outside of Wikimedia projects, in order to understand their current painpoints and unmet needs.

Development

Prototypes will be available for Depicts soon.

Stay up to date!

Follow the Structured Data on Commons project on Phabricator: https://phabricator.wikimedia.org/project/profile/34/
Subscribe to this newsletter to receive it on a talk page of your own choice.
Join the next IRC office hour and ask questions to the team! The date for next quarter will be announced soon.

-- Keegan (WMF) (talk)

Message sent by MediaWiki message delivery - 21:07, 6 July 2018 (UTC)[reply]

Structured Data Newsletter - Research link fix

Greetings,

The newsletter omitted two interwiki prefixes, breaking the links on non-meta wikis as you might see above. Here are the correct links:

m:Research:Curation workflows on Wikimedia Commons—a project that seeks to understand the current workflows of Commons contributors who curate media (categorize it, delete it, link to it from other projects, etc.).
m:Research:Technical needs of external re-users of Commons media—soliciting feedback from individuals and organizations that re-use Commons content outside of Wikimedia projects, in order to understand their current painpoints and unmet needs.

My apologies, I hope you find the corrected links helpful.

- Keegan (WMF) (talk) 21:21, 6 July 2018 (UTC)[reply]

Q_50339681

https://www.wikidata.org/wiki/Wikidata:Vandalism#What_isn't_vandalism?

It get mainly edits from some ip that tries to re-write history. Several attempts were made to discuss this (mainly in relation to property), but that didn't really help. J_u_r_a 10:11, 8 July 2018 (UTC)

✓ Done Semi-protected for one month. Pamputt (talk) 12:00, 8 July 2018 (UTC)

this is a false statement as history will show no discussion, you should look at the edits before reacting.

www dot wikidata dot org/wiki/Talk:Q50339681
www dot wikidata dot org/wiki/Property_talk:P1483
www dot wikidata dot org/wiki/User_talk:50.254.21.213

50.254.21.213 12:48, 18 July 2018 (UTC)[reply]

it is a war, he is reverting everybody, https://www.wikidata.org/w/index.php?title=Property:P1483&action=history and you are in the middle of it,

https://www.wikidata.org/wiki/Wikidata:Administrators%27_noticeboard#код_kulturnoe-nasledie.ru_-_Property:P1483

50.254.21.213 01:30, 27 July 2018 (UTC)[reply]

.

Hi. The problem is that now I can not edit this page. Can you give me permission to review automatic edits? I have a rollback permission in the Hebrew Wiki. דגש חזק (talk) 11:33, 23 July 2018 (UTC)[reply]

Hi דגש חזק, you are now confirmed user. Usually, you can ask such request here. Pamputt (talk) 11:41, 23 July 2018 (UTC)[reply]

thank. דגש חזק (talk) 11:42, 23 July 2018 (UTC)[reply]

Wikidata Benalla

Voir mon intervention sur la page de discussion. Pour la photo je ne suis pas sûr que ce soit la bonne personne, elle ne ressemble pas aux images télévisées.--Markov (talk) 18:49, 23 July 2018 (UTC)[reply]

Ok merci pour le message. Pamputt (talk) 20:09, 23 July 2018 (UTC)[reply]

sources to reconstructed words

I agree with you that reconstructed words should have sources and in Polish Wiktionary we too base on the assumption that all informations should be verificable like in French wiktionary. We have principle in Polish Wiktionary wikt:pl:Wikisłownik:Weryfikowalność which starts with words: "The basic criterion for placing content in Wiktionary is verifiability." I want to add sources to all lexemes from https://www.wikidata.org/w/index.php?title=Special%3AWhatLinksHere&target=Q747537&namespace=146 . How do you propose to describe these sources? Should I add source to instance of (P31)=reconstructed word (Q55074511) (like this) or do it with some other property? KaMan (talk) 07:03, 5 October 2018 (UTC)[reply]

Hi KaMan I have no clear idea about the best way how to do that. That's said, the way you choose looks good. The other way would be to use described by source (P1343) as a statement for the Lexeme. Pamputt (talk) 16:39, 30 October 2018 (UTC)[reply]

Nommé en référence à

Ca me gène toujours quand on met un « nommé en référence à » pas du tout en qualificatif d’une déclaration « nom ». Les trucs peuvent tout à fait avoir plusieurs noms et on n’indique pas de cette manière à quel nom appartient la référence. Un référence de nommage, au contraire, est nécessairement liée à un nom donné … author TomT0m / talk page 13:06, 30 October 2018 (UTC)[reply]

OK je vois le truc, on est supposé grouper les noms en qualificatif https://www.wikidata.org/wiki/Q16483#P138 avec un qualificatif dont j’avais manqué la création. ça fait sens si les noms dans de nombreuses langues partagent la mềme référence, ca évite d’avoir

⟨ élément1 ⟩ nom Search ⟨ nom en fr ⟩
nommée en référence a Search ⟨ élem2 ⟩

⟨ élément1 ⟩ nom Search ⟨ nom en en ⟩
nommée en référence a Search ⟨ élem2 ⟩

⟨ élément1 ⟩ nom Search ⟨ nom en de ⟩
nommée en référence a Search ⟨ élem2 ⟩

… Moué il y a du pour et du contre, c’est peut-être mieux comme ça dans certains cas. Après comme les noms sont des mots, faudrait peut-être mieux mettre tout ça dans des lexeme à terme.

Celà dit le "fr" de linuxfr est clairement une référence à la langue française, pourquoi l’avoir supprimé ? author TomT0m / talk page 13:36, 30 October 2018 (UTC)[reply]

Salut TomT0m c'est en effet la façon de faire que j'avais retenue. Après c'est vrai que ça prête à débat. Pour le « français », ça disparu au passage ; c'est une erreur qui est maintenant corrigée. Pamputt (talk) 16:26, 30 October 2018 (UTC)[reply]

Use of translation admin tools in controversial cases

Please refrain from acting as admin in cases where you seek to advance your own editorial POV. This even in cases where you don't actively contribute to the project. --- Jura 09:13, 25 November 2018 (UTC)[reply]

@Jura1: On va continuer en français. Explique-moi clairement ce qui est controversé dans ce diff ? Pamputt (talk) 09:14, 25 November 2018 (UTC)[reply]

It's the previous edit that is problematic. By marking it for translation, non-translation admins can't change the generally available version. --- Jura 09:18, 25 November 2018 (UTC)[reply]

@Jura1: Qu'est ce qui est problématique précisément ? Tous les utilisateurs peuvent revenir à n'importe quelle version depuis l'historique de la langue principale (en anglais). Pamputt (talk) 09:21, 25 November 2018 (UTC)[reply]

The version you marked for translation gets dispatched to other languages and reverting the English version isn't changing this. Please ensure you don't act as admin when attempting to further your own editorial POV even for fields you don't actively contribute to. --- Jura 09:26, 25 November 2018 (UTC)[reply]

Jura1 stop trolling please. What I added to Wikidata:Lexicographical_data/Notability was reflecting the result of the vote (as KaMan writes below). If you do not think so, explain clearly why. As a translation admin, I simply marked the new version for translation. If this new version is not consensual, explain why and we will be able to come back to an older version (when I marked the version for translation, I did not expect anyone to object). Pamputt (talk) 09:31, 25 November 2018 (UTC)[reply]

Ok. In that case, you could have marked the previous version for translation and shouldn't have reverted my edit. Please refrain from accusing people of trolling when they disagree with your editorial POV. I find this conduct highly inappropriate. --- Jura 09:51, 25 November 2018 (UTC)[reply]

@Jura1: I asked you several times to explain me what is wrong with my version and you did not reply ; you just say that I use my translation admin right for bad withtout explaining why (this is what I consider as a troll). So, to be constructive, tell me exactly which version looks fine for you, so that I can mark it for translation. Pamputt (talk) 09:58, 25 November 2018 (UTC)[reply]

I just noticed that the addition you made was on Nov 13, not today. Sorry about that. I don't think the discussion you mentioned was about graphemes. If we can't agree on a revision of that may reflect today's consensus, we have to restore a version before. --- Jura 10:12, 25 November 2018 (UTC)[reply]

@Jura1: The initial vote was about phoneme but Shlomo points that graphemes are exactly the sam during the vote. You did not oppose during the vote. Do you have any argument to oppose that graphemes should also be exluced from Lexeme namespace? I hope we will not need another vote. Pamputt (talk) 10:21, 25 November 2018 (UTC)[reply]

My questions in the discussion haven't been answered, so as far as I'm concerned, the topic hasn't been resolved. I think most linguists think they are different. Maybe they are the same at Wiktionary or in some country where votes work that way. --- Jura 10:26, 25 November 2018 (UTC)[reply]

Sorry Jura1 but could you tell me which questions you are talking about? Pamputt (talk) 10:34, 25 November 2018 (UTC)[reply]

FYI, I opened a discussion about this topic here. I am sorry but I do not manage to discuss with you. it seems you want to be right against everyone on your own so I do not see any other option. Pamputt (talk) 10:49, 25 November 2018 (UTC) @Jura1: I do actively contribute to the project and I find Pamputt actions correct. KaMan (talk) 09:22, 25 November 2018 (UTC)[reply]

protect

Hello.

Where are the protection of pages being attacked? thanks, דגש חזק - Talk 09:17, 25 November 2018 (UTC)[reply]

Hi דגש חזק, what are you talkink about? Which pages do you want to protect? Pamputt (talk) 09:18, 25 November 2018 (UTC)[reply]

I'm talking about Q185318. but, I also want to know where to seek protection From the administrators. thanks, דגש חזק - Talk 09:27, 25 November 2018 (UTC)[reply]

@דגש חזק: I protected Mount Carmel (Q185318) for 6 months. For knowing which pages are protected, we can see the protect logs and also Special:ProtectedPages. Is it what you are looking for? Pamputt (talk) 09:35, 25 November 2018 (UTC)[reply]

No. I look for the page, where I can ask the administrators to protect a page. (If I do not want to approach you, but rather a general place for such requests). thanks, דגש חזק - Talk 11:00, 25 November 2018 (UTC)[reply]

@דגש חזק: sorry for the misunderstanding. You can ask for such requests here. Pamputt (talk) 12:50, 25 November 2018 (UTC)[reply]

Thanks. If I've been here, can you give me (or comment there) permission to rollback? (I asked for the page, and no one responded). thanks, דגש חזק - Talk 12:55, 25 November 2018 (UTC)[reply]

@דגש חזק: I cannot find the discussion you are talking about (where you "asked for the page"). Pamputt (talk) 18:00, 25 November 2018 (UTC)[reply]

Wikidata:Requests_for_permissions/Other_rights thanks, דגש חזק - Talk 19:30, 25 November 2018 (UTC)[reply]

@דגש חזק:

Done I just gave you the rollback right. Pamputt (talk) 19:56, 25 November 2018 (UTC)[reply]

Like thanks, דגש חזק - Talk 20:02, 25 November 2018 (UTC)[reply]

regex WIGOS

Bonjour Pamputt,

Je suis en train de travailler sur un projet pour ajouter toutes les stations météorologiques d'Environnement Canada sur Wikidata. Parmi les informations disponibles pour certaines stations, il y a WIGOS station ID (P4136). Par exemple pour la station Isachsen (Q3155098), l'identifiant WIGOS est int.wmo.wigos-0-20000-0-71074. Or, le regex pour cet idenfiant donne une erreur. Il n'y a pas seulement les stations canadiennes qui sont problématiques, celle de Blue Hill Meteorological Observatory (Q1803017) (int.wmo.wigos-0-20000-0-74492) donne aussi une erreur. Pourtant, on constate que ces identifiants ont bien un format semblable.

Les quelques stations qui ont cette identifiant ont aussi un format semblable:

int.wmo.wigos-0-20000-0-94980
int.wmo.wigos-0-20000-0-74492
int.wmo.wigos-0-20000-0-71798
int.wmo.wigos-0-20000-0-71074
int.wmo.wigos-0-20000-0-68994
int.wmo.wigos-0-20000-0-68906
int.wmo.wigos-0-20000-0-45005
int.wmo.wigos-0-20000-0-16226
int.wmo.wigos-0-20000-0-16149
int.wmo.wigos-0-20000-0-11121

Requête pour voir ces identifiants:

SELECT ?item ?itemLabel ?identifiant_WIGOS_de_station WHERE {
  ?item wdt:P31 wd:Q190107.
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
  OPTIONAL { ?item wdt:P4136 ?identifiant_WIGOS_de_station. }
}

Try it!

Serait-il possible de revoir le regex pour que cela corresponde bien à ce format, et ainsi faire disparaître les erreurs?

Merci, Dirac (talk) 16:42, 6 December 2018 (UTC)[reply]

Structured Data on Commons Newsletter - Fall 2018 edition

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter. Do inform others who you think will want to be involved in the project!

Community updates

Multilingual Captions, the first feature release for Structured Data, is coming in January of 2019
- Be on the lookout for the beta testing announcement
- Help using captions has been set up, if you'd like to go ahead and see the workflow
Two IRC office hours were held since the last newsletter
- Log for 4 October
- Log for 1 November
Our dedicated IRC channel: wikimedia-commons-sd ^webchat

Things to do / input and feedback requests

Current:

Since the last newsletter:

Review a prototype for searching structured Commons (October 2018)
"Good coverage" for depicts tagging (Sept. 2018)
Review and discuss mockups for displaying the new metadata section of the file page (18 September - 9 October 2018)
Depicts statements draft requirements (14 August - 31 August 2018)
Identify Wikidata properties that Commons will need (26 June - 14 August 2018)

Presentations / Press / Events

Presentation by Keegan on the first features to be released for Structured Data, presented at Wikiconference North America, Columbus, Ohio, October 2018.
Sandra presented a project update at the GLAM-Wiki conference in Tel Aviv, Israel, November 2018, as part of an update and panel discussion.
Structured Data on Commons was the subject of a keynote presentation by Sandra (see slides) at the Baltic Audiovisual Archives Council conference in Tallinn, Estonia, November 2018.

Partners and allies

The info portal on Structured Commons now includes a section on GLAM (Galleries, Libraries, Archives and Museums).
We are currently planning the first GLAM pilot projects that will use structured data on Wikimedia Commons. One project has already started: the Swedish Heritage Board researches and develops a prototype tool to provide improved metadata (translations, data additions...) from Wikimedia Commons back to the source institution. Read the project brief.
The documentation for batch uploads of files to Wikimedia Commons will be improved in 2019, as part of preparing for Structured Data on Wikimedia Commons. To prepare, the GLAM team at the Wikimedia Foundation wants to understand better which types of documentation you already use, and how you like to learn new GLAM-Wiki skills and knowledge. Fill in a short survey to provide input!

Stay up to date!

Follow the Structured Data on Commons project on Phabricator: https://phabricator.wikimedia.org/project/profile/34/
Subscribe to this newsletter to receive it on a talk page of your own choice.

-- Keegan (WMF) (talk)

Message sent by MediaWiki message delivery - 17:58, 7 December 2018 (UTC)[reply]

Captions in January

The previous message from today says captions will be released in November in the text. January is the correct month. My apologies for the potential confusion. -- Keegan (WMF) (talk) 20:43, 7 January 2019 (UTC)[reply]

Structured Data - file captions coming this week (January 2019)

My apologies if this is a duplicate message for you, it is being sent to multiple lists which you may be signed up for.

Hi all, following up on last month's announcement...

Multilingual file captions will be released this week, on either Wednesday, 9 January or Thursday, 10 January 2019. Captions are a feature to add short, translatable descriptions to files. Here's some links you might want to look follow before the release, if you haven't already:

Read over the help page for using captions - I wrote the page on mediawiki.org because captions are available for any MediaWiki user, feel free to host/modify a copy of the page here on Commons.
Test out using captions on Beta Commons.
Leave feedback about the test on the captions test talk page, if you have anything you'd like to say prior to release.

Additionally, there will be an IRC office hour on Thursday, 10 January with the Structured Data team to talk about file captions, as well as anything else the community may be interested in. Date/time conversion, as well as a link to join, are on Meta.

Thanks for your time, I look forward to seeing those who can make it to the IRC office hour on Thursday. -- Keegan (WMF) (talk) 21:09, 7 January 2019 (UTC)[reply]

Fusion

Merci à vous ! Pourriez-vous encore procéder à la fusion de Société d'étude des sciences naturelles de Nîmes (Q46730069) et Société d'étude des sciences naturelles de Nîmes (Q59770658), qui portent sur une même organisation ?

Bien cordialement, 109.9.71.223 15:54, 24 January 2019 (UTC)[reply]

Done Pamputt (talk) 15:59, 24 January 2019 (UTC)[reply]

Property Creator

Hi @Pamputt:, Thanks for your support. I've completed a week as Property Creator rights holder. Please be requested to verify and set to indefinite Property Creator rights. Regards, ZI Jony ^(Talk) 12:31, 4 April 2019 (UTC)[reply]

Hi ZI Jony I just gave you the property creator right for indefinite time. Thanks for helping in property creation. Pamputt (talk) 18:14, 5 April 2019 (UTC)[reply]

Thanks a lot for your Trust and support. Regards, ZI Jony ^(Talk) 04:45, 6 April 2019 (UTC)[reply]

Langues ninziques

Bonjour

Je suis en train de créer l'article sur wp.fr. C'est toi qui a ajouté ce libellé [3], quelle source as-tu pour cette orthographe plutôt que langues ninzic ou langues ninzics (je n'ai rien trouvé de mon côté)

Merci de me notifier. Cordialement, Şÿℵדαχ₮ɘɼɾ๏ʁ 10:34, 17 April 2019 (UTC)

Salut SyntaxTerror il n'y a en effet aucune attestation pour "langues ninziques". A noter qu'il n'y a pas non plus d'attestations pour "langues ninzic" (ou "langues ninzics"). Cette famille ne regroupant que des langues parlées au Nigeria, pays anglophone, il y a peu de chance qu'on trouve une attestation en français dans un avenir proche. Le "-ique" est une francisation "standard" de l'anglais "-ic". Voir par exemple Algic (Q721612). C'est pour ça que je me suis permis de mettre ce libellé "francisé". Pamputt (talk) 11:07, 17 April 2019 (UTC)[reply]

Merci de ta réponse rapide. Je me tâtais aussi sur le choix du nom, je n'ai plus à le faire (et je peux reporter la faute sur toi si jamais j'ai des ennuis :P). Cordialement, Şÿℵדαχ₮ɘɼɾ๏ʁ 11:12, 17 April 2019 (UTC)

It was time...

Thank you for everything !

I borrow this image from Ckoerner (CC BY-SA 4.0) to thank you for the hard work that has been going on for the past 11 years. Rotate it as you like. I will put one on Wiktionary in 9 years. --Eihel (talk) 17:26, 23 June 2019 (UTC)[reply]

Horrible Message on my user talk

Hi Pamputt can you please look into this comment Topic:V2ewmxwvz3k3dyiw~JJBullet~ {Talk} 13:54, 27 June 2019 (UTC)[reply]

I removed it. Pamputt (talk) 13:59, 27 June 2019 (UTC)[reply]

thanks pamputt~JJBullet~ {Talk} 08:09, 1 July 2019 (UTC)[reply]

Wiki Science Competition 2019

Hi, we are organizing the 2019 edition of WSC, if you are interested let me know. Maybe this year we will invest less energy on country whose chapter is not interested but we are expecting much better results in countries were local organizers are active. Let me know if you are interested to join.

Also, we are creating a new User group that acts as a global coordination project on meta for scientific subjects. See m:Science Wiki User Group. It will take some months to shape it but we are very motivated. Specifically, one of the main target of the group are people with an academic degree and/or who are involved in scientific research in real life, we want to reach out to the scientific community through that way. Please join us, especially if you have a sufficient knowledge of English or of meta since we are still building it (we will translate the page in the future when its identity is stable). Every comment is welcome (see the talk page). One of the topic of this UG is to provide an official support also for WSC in the future.--Alexmar983 (talk) 14:52, 29 June 2019 (UTC)[reply]

Wikidata:Lexicographical data/Documentation/Languages/br

Bonjour,

Tout d'abord, je suis preneur de tout remarque sur la page Wikidata:Lexicographical data/Documentation/Languages/br qui est encore plutôt à l'état de brouillon (bien avancé mais loin d'être parfait), je viens justement de lancer une discussion sur Wikidata talk:Lexicographical data/Documentation/Languages.

Ensuite, je veux bien quelques éclaircissements sur le fonctionnement de la balise translate que je ne connais pas vraiment bien. Notamment est-il possible de marquer certains passages comme à ne pas traduire et laisser tel quel ? typiquement, la Databox est automatiquement traduite dans la langue de l'interface et les requêtes en bas de page sont en SPARQL donc pas à traduire non plus. En bonus, vu que c'est encore un brouillon est-il possible de la dé-marquer comme à traduire le temps que le contenu soit stabilisé ?

Cdlt, VIGNERON (talk) 14:32, 1 July 2019 (UTC)[reply]

Salut VIGNERON, je vais essayer de jeter un oeil à Wikidata:Lexicographical data/Documentation/Languages/br. Concernant les balises translate, le logiciel Mediawiki va créer des chaines à traduire pour tout ce qui se trouve entre <translate> et </translate>, donc si tu ne veux pas qu'un passage soit traduit, tu ne le met pas à l'intérieur de ces balises. Autre point, Mediawiki crée un nouveau bloc de texte à traduire dès qu'il détecte un double saut de ligne. C'est pour ça qu'il est intéressant de mettre une ligne blanche avant et après un titre de section. Pour démarquer un texte, j'avoue que je ne sais pas trop comment faire ça simplement ; il faudrait retirer toutes les balises « translate » plus tous les numéros qui sont commentés, donc le mieux c'est de laisser comme ça pour le moment. Pamputt (talk) 15:57, 1 July 2019 (UTC)[reply]

When someone asks to shoot

you just do it?

"I protected Property talk:P6878 because Jura1 asked for the protection"

Or is there a chance you would apply general rules for shooting? 89.14.41.70 19:51, 5 July 2019 (UTC)[reply]

Indeed. Pamputt (talk) 21:44, 5 July 2019 (UTC)[reply]

Translation

This talk page appears on the translation work list. I can only guess that the "nowiki" didn't work for the "translate" tags in "Wikidata:Lexicographical data/Documentation/Languages/br" section above. Presumably a mistake, can you have a look to see if it can be removed. Perhaps the nowiki tag can contain only the < or replace it with < Thanks! Jagulin (talk) 09:36, 28 July 2019 (UTC)[reply]

@Jagulin: I replace < with < to fix this issue. Thanks for reporting. Pamputt (talk) 14:58, 28 July 2019 (UTC)[reply]

Petit rappel

Merci pour vos essais de création de nouveaux éléments. Petit rappel: c'est mieux de toujours rajouter de déclarations sur éléments et ne pas les laisser vide.

D'ailleurs, merci de ne pas supprimer du contenu rajouté par d'autres contributeur et de suivre les standards établis pour certains éléments.. Si ce n'est pas accompagné par d'autres contributions, ceci peut donner une très mauvaise impression du projet, surtout quand c'est fait par des administrateurs. --- Jura 12:36, 13 August 2019 (UTC)[reply]

@Jura1: merci d'être plus explicite car je ne comprends absolument pas de quoi vous parlez. Pamputt (talk) 13:08, 13 August 2019 (UTC)[reply]

Maybe it's clearer if I write it in English:

Thanks you for attempts at creating new items. Short reminder: It's always better to add statements when creating items rather than leaving them empty.

BTW, do not delete content added by other contributors and attempt to follow standards established for items .. If you do not contribute otherwise, this can give a bad impression of the project, especially when it's done by an administrator.

That last part is obviously my personal opinion.

If you are unsure how to identify items you created that essentially are empty, try: [4] --- Jura 14:41, 13 August 2019 (UTC)[reply]

Ce n'est toujours pas clair. J'imagine qu'il s'agit uniquement d'une provocation et je n'y répondrai donc pas. En attendant, vu que vous semblez avoir du temps à perdre, pourriez-vous consacrer quelques minutes pour répondre à mon message ? Pamputt (talk) 14:46, 13 August 2019 (UTC)[reply]

I need your help - Peter Ware Higgs (Q192112)

I'm not good at editing, I just want to contribute, can you help me?

Hola!!! Pamputt thanks for blocking the site . the discussion arises from the religion of Peter higgs.

Peter has been an atheist since 2013: interview conducted by Kenneth Macdonald & BBC Scotland - Source Link

The statements of higgs are confirmed by: The Daily Telegraph - Source Link

You can confirm that the interview is real, University of Edinburgh confirms that this interview is real Source Link - “17 April 2013 BBC TV Scotland shows the Ken MacDonald documentary 'Peter Higgs: Particle Man' on BBC Scotland. It was repeated later on the BBC News Channel.”

The interview has been shared by pages such as: Freedom From Religion Foundation - Source Link

The interview has been shared by pages such as: The Scotsman - Source Link

I can continue to put the necessary sources, but there is not a single statement by Peter Higgs where he says he is an "agnostic person"

The user without IP registration - 181.188.170.150 -Not partial - Does not provide sources – The preceding unsigned comment was added by Audcsias (talk • contribs) at 13 août 2019 à 18:17‎ (UTC).

Hello Audcsias. I copy all you message above on Talk:Q192112 in order to keep track of it easily. Let see whether other contributors react. Pamputt (talk) 16:28, 13 August 2019 (UTC)[reply]

thanks pamputt I have added a few more sources~Audcsias|~ |{Talk} 04:10, 13 august 2019 (UTC)

User doing vandalism in tickets of atheistic people

Hi Pamputt, excuse me who is again posting on your talk!

The user formerly in the discussion of Peter Higgs, is a girl from a discussion group on Facebook, is a person "anti atheists" is not a partial person, only comes to Wikipedia to change sources and annoy the work of other people, is doing the same thing again in the entry of "William James Sidis Q313603" I will not fall into his game again, but as you can see the ip "181.188.170.124" of Bolivia changes data again without providing sources of changes, this user corresponds to the same user of the discussion of Peter higgs "181.188.170.150".

~Audcsias|~ |{Talk}

Hi Audcsias, thank you for the information. I reverted the IP modification since it is not consistant with what is stated in the reference you added. I will watch this page now. Pamputt (talk) 05:23, 22 August 2019 (UTC)[reply]

Hi Pamputt a cordial greeting! Only step to report that user behavior continues.

--ॐ Audcsias talk 13:48, 27 August 2019 (UTC)[reply]

Hi Audcsias I reverted and semi-protected the page for one month. I hope it will be enough. Pamputt (talk) 18:26, 27 August 2019 (UTC)[reply]

Structured Data - blogs posted in Wikimedia Space

There are two separate blog entries for Structured Data on Commons posted to Wikimedia Space that are of interest:

Working with Structured Data on Commons: A Status Report, by Lucas Werkmeister, discusses some ways that editors can work with structured data. Topics include tools that have been written or modified for structured data, in addition to future plans for tools and querying services.
Structured Data on Commons - A Blog Series, written by me, is a five-part posting that covers the basics of the software and features that were built to make structured data happen. The series is meant to be friendly to those who may have some knowledge of Commons, but may not know much about the structured data project.

I hope these are informative and useful, comments and questions are welcome. All the blogs offer a comment feature, and you can log in with your Wikimedia account using oAuth. I look forward to seeing some posts over there. -- Keegan (WMF) (talk) 21:33, 23 September 2019 (UTC)[reply]

Suppression d'un item

Bonjour Pamputt, j'ai adressé une demande de suppression de la page que j'ai créée Q74168053, la personne concernée estime que c'est une atteinte à sa vie privée, or cette page n'a guère d'intérêt en soi (pas de lien Wikipédia), donc je soutiens cette demande de suppression. Merci de voir ce que tu peux faire, bonne journée, --Pierrette13 (talk) 10:26, 17 November 2019 (UTC)[reply]

Done Pamputt (talk) 10:29, 17 November 2019 (UTC)[reply]

Merci !!!! Bonne journée et à la prochaine çà ou là, c'était sympa de te voir en live, --Pierrette13 (talk) 10:47, 17 November 2019 (UTC)[reply]

Suppression

Bonsoir Pamputt,

pourrais-tu STP effectuer cette suppression ? Comme personne ne s'en est encore occupé, je crains que la section ne soit archivée avant qu'on ait pu y donner suite.

Merci à toi,

Nomen ad hoc (talk) 19:52, 26 December 2019 (UTC).[reply]

C'est fait. Pamputt (talk) 20:34, 26 December 2019 (UTC)[reply]

Doublon

Bonjour. Vous avez créé un doublon, Fanny Torros (Q86447949), de Fanny Torros (Q27879557). Son nom était Torras, pas Torros. Sapphorain (talk) 10:08, 27 February 2020 (UTC)[reply]

Effectivement, je viens de fusionner les deux éléments. Merci de ta vigileance. Pamputt (talk) 12:10, 27 February 2020 (UTC)[reply]

Galère sur ResearchGate auteur

Coucou Pamputt, je galère pour ajouter des identifiants RG auteurs. Notamment sur la fiche WD de Dominique Ottavi. Est-ce qu'il y a une façon particulière de faire ? J'espère que tu vas bien, merci de ta réponse, absolument pas pressée, --Pierrette13 (talk) 12:49, 28 March 2020 (UTC)[reply]

Salut Pierrette13, je viens d'ajouter l'identifiant ResearchGate. Pour trouver les identifiants, il suffit d'utiliser leur moteur de recherche, non ? Pamputt (talk) 13:11, 28 March 2020 (UTC)[reply]

Merci de ta réponse, en fait, j'avais regardé l'identifiant que tu avais mis pour Evelyne Mesclier (P6023), j'ai mis le même pour Laurence Gavarini (P6023) mais pour Dominique Ottavi, tu as utilisé P2038 et P6023 ne marche pas... Bon ça n'a pas bcp d'importance, bonne fin de journée et merci, --Pierrette13 (talk) 13:39, 28 March 2020 (UTC)[reply]

Ah ok, la différence entre ResearchGate profile ID (P2038) et ResearchGate contributions ID (P6023), c'est que le premier est utilisé lorsque le chercheur ou la chercheuse a créé son profil sur ResearchGate tandis que le second est un numéro automatique attribué par RG lorsque la personne n'a pas de profil sur la plateforme. Pamputt (talk) 14:06, 28 March 2020 (UTC)[reply]

Question

Can I ask you a question? --- Jura 06:40, 5 May 2020 (UTC)[reply]

@Jura1: Si c'est au sujet de Hsarrazzin et du topic sur le bistro francophone, non ! J'aimerais qu'on passe à autre chose. Pamputt (talk) 06:43, 5 May 2020 (UTC)[reply]

Sure. It's just about your admin action/decision: can you add an explanation in plain English on the noticeboard? People might not look at your revert and consider the topic on the noticeboard still open and wonder why participants didn't respond given some of the comments. --- Jura 07:09, 5 May 2020 (UTC)[reply]

@Jura1: je pense que mon dernier commentaire (celui qui apparait actuellement) se suffit à lui-même et que le sujet se fermera tout seul d'ici 1 jour ou deux (si personne ne remet une pièce dans la machine). Je ne pense donc pas qu'il faille que j'écrive quoi que ce soit. Pamputt (talk) 07:34, 5 May 2020 (UTC)[reply]

If I didn't understand it, it's not unlikely that others will loose it in translation as well. There is a standard way of closing discussions on the noticeboard: why not apply that? --- Jura 08:01, 5 May 2020 (UTC)[reply]

Nouvelle propriété

Salut. Est-ce que je peux avoir Wikidata:Property proposal/Arkansas Register of Historic Places ID ? Je demande juste l'initiation en deux clics. Je m'occupe de tout le reste si tu veux. Thierry Caro (talk) 08:58, 21 May 2020 (UTC)[reply]

Pas de soucis, c'est fait

Pamputt (talk) 09:03, 21 May 2020 (UTC)[reply]

OK. Merci. La propriété est complétée et entièrement déployée, désormais. Comme j'ai d'autres propositions en attente, je me permets de t'en demander une autre, à tout hasard. Wikidata:Property proposal/MACRIS ID par exemple. Vois si tu peux. Thierry Caro (talk) 11:16, 21 May 2020 (UTC)[reply]

Nickel pour Arkansas Register of Historic Places ID (P8232). Je viens de créer MACRIS ID (P8239). Pamputt (talk) 11:19, 21 May 2020 (UTC)[reply]

Merci beaucoup. Thierry Caro (talk) 11:36, 21 May 2020 (UTC)[reply]

Crois-tu que je peux avoir Wikidata:Property proposal/MDAH's HRI ID et Wikidata:Property proposal/RI National Register Search ID de la même façon ? Ensuite je n'aurai plus rien en attente et je ne t'embêterai plus. Thierry Caro (talk) 09:40, 22 May 2020 (UTC)[reply]

Aucun soucis. C'est fait MDAH's HRI ID (P8249) et RI National Register Search ID (P8250) Pamputt (talk) 09:45, 22 May 2020 (UTC)[reply]

Merci beaucoup. Je vais m'en occuper de suite. Thierry Caro (talk) 09:48, 22 May 2020 (UTC)[reply]

Isabelle Méjean

Bonjour Pamputt, je n'ai pas vu pendant un long moment que tu remplissais cette notice hier. Je ne suis pas sûre qu'elle soit admissible sur WP, j'attends de voir si quelqu'un lit l'article du Monde et se lance, bonne journée, --Pierrette13 (talk) 06:07, 25 May 2020 (UTC)[reply]

Thanks for closing property discussion

Wikidata:Property proposal/funder

Thank you. Blue Rasberry (talk) 17:25, 9 June 2020 (UTC)[reply]

Thanks for creating Odeon ID

Malheureusement, it is malfunctioning ((
No link, just plain text. - Coagulans (talk) 06:16, 18 June 2020 (UTC)[reply]

@Coagulans: it seems there is an issue with the new properties; it takes several hours before the links are "enabled". To me, links are working at least on the property page itself. Pamputt (talk) 11:04, 18 June 2020 (UTC)[reply]

Yes, activated, many thanks )) - Coagulans (talk) 18:38, 18 June 2020 (UTC)[reply]

Gramophone composer ID (P8386)

Bonjour Pamputt,

Vous avez dû vous apercevoir de mon manège sur cette propriété nouvellement créée par vous. En fait,

mon format de RegEx n'était pas pris en compte (PCRE pourtant, il me semble), je l'ai modifié et il ne provoque plus d'erreur.
les identifiants ne comportent pas de lien. J'ai déjà aperçu ce phénomène récemment sur P8357. Il suffisait de refaire P1630 (Formatter URL), mais là, le problème persiste. J'aimerais essayer en recommençant de zéro.

À+ —Eihel (talk) 19:10, 27 June 2020 (UTC)[reply]

Salut Eihel, concernant les liens, le problème existe depuis 2-3 semaines (peut-être plus). Au bout de 24-48h, les liens finissent par s'activer « tout seul ». Donc, je pense que d'ici lundi, ça devrait fonctionner (voir Property_talk:P8373#An_error_with_Formatter_URL ou le message juste au-dessus par exemple). Pamputt (talk) 19:30, 27 June 2020 (UTC)[reply]

Academic appointment property P8413 needs to allow series ordinal qualifier

Hi Pamputt. Thanks for your help with approving the Academic appointment property. I have started using it, but noticed that there is a qualifier constraint that only allows start time and end time. That is a problem because one of the key uses of this property is to use the series ordinal qualifier property distinguish between primary academic appointments and secondary academic appointments. This was mentioned by me in the beginning of the property proposal.

For example, Suzana Herculano-Houzel has a primary appointment in the Psychology department, and a secondary appointment in the Biological Sciences department (see reference URL). But when I use series ordinal to make those qualifications, the qualifiers are flagged as violating a constraint.

If you could add series ordinal qualifier property as an allowed qualifier constraint, that would be great and allow us to use the property as intended.

Thanks! Baskaufs (talk) 22:12, 18 July 2020 (UTC)[reply]

@Baskaufs:. I've just added this property as allowed qualifier. No need to ask next time, you can do it by yourself :D. Pamputt (talk) 00:15, 19 July 2020 (UTC)[reply]

Thank you so much for your help and advice! Baskaufs (talk) 11:31, 19 July 2020 (UTC)[reply]

Two proposals

Hi @Pamputt: I am hoping that both of these might be accepted: Wikidata:Property proposal/Australian Weed ID and Wikidata:Property proposal/QLD Biota ID (to be renamed Queensland Biota ID)... Is there any thing more that needs to be done. MargaretRDonald (talk) 07:48, 20 July 2020 (UTC)[reply]

@MargaretRDonald: I marked both proposals as ready. I will create them later today if no one did before. Pamputt (talk) 07:50, 20 July 2020 (UTC)[reply]

@Pamputt:. Thanks so much. However, I edited Abutilon auritum (Q15353368) to add its Queensland Biota ID (18081) but the ID failed to link. (Hoping you can help with this too.) Regards, MargaretRDonald (talk) 22:33, 20 July 2020 (UTC)[reply]

Also edited Emex australis (Q642344) to add its Australian Weed ID. (Emex~australis). It too, failed to link. Cheers, MargaretRDonald (talk) 22:45, 20 July 2020 (UTC)[reply]

@MargaretRDonald: from several weeks already, external links are not enabled directly after property creation. Yet, they become active after 24-48 hours. For example, it is currently working for Emex australis (Q642344) :) Pamputt (talk) 05:54, 21 July 2020 (UTC)[reply]

Thanks for the explanation. MargaretRDonald (talk) 06:37, 21 July 2020 (UTC)[reply]

Property constraint change on P8181

Hi @Pamputt:, last week you changed the property constraint on SNCF Station ID (P8181) from [A-Z]{5} to (BE|FR|NL)[A-Z]{3}. Those ids however exist for several other European countries too, so this looks a bit too restrictive to me. How should I proceed there, try to compile a complete list of countries with those codes, or go back to the previous constraint? Or am I missing something regarding those codes that would actually restrict them to BE/FR/NL? Thank you! Volker.krause (talk)

Hi Volker.krause I have updated the regex so that it takes into account all the possible countries (or at least all the ones for which the property has been used for one train station). I think we should update the list of country codes in the regex to control that there is not country outside Europe. Pamputt (talk) 15:57, 24 July 2020 (UTC)[reply]

Thanks, that works :) Volker.krause (talk) 16:11, 24 July 2020 (UTC)[reply]

IP 137.101.89.177 (Angelmunoz50)

Please can you help me with this situation Vandalism IP 137.101.89.177 that I reported yesterday on the Administrators News Board? These edits affect the content shown in infobox in other wikis, and interfere with the work of various editors (reverting, checking, verifying sources and posting notices to the IP) is impossible given the activity of the vandal. I would appreciate. --Ytha67 (talk) 13:43, 15 August 2020 (UTC)[reply]

Globally blocked as said on the Administrators News Board. Sorry for the delay. Pamputt (talk) 09:18, 16 August 2020 (UTC)[reply]

Premature creation

Hi Pamputt,

thanks for your help with property creations. It's good to have your help given the backlog. However, it seems to me that this was created somewhat prematurely: The discussion was still ongoing and consensus doesn't seem to be that clear.

One person merely supported creation despite "I don't know anything about this site"". This is especially problematic as the proposal didn't include information only added later in the discussion.

If you think this could be speedily deleted, we could continue the discussion. Alternatively, I suppose it would have to go through a regular deletion. --- Jura 08:52, 17 August 2020 (UTC)[reply]

I don't quite understand much of the comments by the proposer, some seems meaningless, based on a misunderstanding of the comment I made, or irrelevant to the discussion of the proposal. In any case, not particularly helpful to built a consensus for its creation. Do you understand their last comment? --- Jura 09:00, 17 August 2020 (UTC)[reply]

Hi Jura1! From what I have observed, you are the only one who is firmly opposed to the creation of this property; 9of99 supported your argument but did not intervene after the explanations given by Eihel, so I deduce (perhaps incorrectly) that he is not very opposed to this creation. So that's 5 supports, one of which is debatable, against one single clear opposition.

I therefore considered that there was a clear majority in favour of creation. So for the moment, let's see how your request for suppression evolves. Pamputt (talk) 11:17, 17 August 2020 (UTC)[reply]

How do you know? As the discussion was cut off, we can't really know. Wikidata consensus building isn't based on mere counts. While it's clear that one user stated they didn't know anything about the property and the proposer had kept them in the dark about the nature of the property.

Did you understand the proposers comment (who obviously supports their own proposal)? --- Jura 12:54, 17 August 2020 (UTC)[reply]

ERIC Thesaurus ID links not working correctly

Hi,

Thank you for creating the ERIC Thesaurus ID property. I discovered that the links from identifiers that have the + character are not working properly. For example the link for Attention+Span gets converted to https://eric.ed.gov/?ti=Attention%2BSpan That link doesn't work, whereas https://eric.ed.gov/?ti=Attention+Span does work fine. It seems that the + is the only problem. In the example with parentheses, only the plus gets changed: https://eric.ed.gov/?ti=Accessibility%2B(for%2BDisabled)

Is there a way to fix this so that the links from Wikidata to ERIC will work?

Thanks.

--- Adam Schiff

Hi UWashPrincipalCataloger I replaced the "+" by a "blank" (see on attention span (Q4115119)) and it seems to do the job. ERIC replaces "+" by "%2B" while it replaces " " by "+". Strange... Pamputt (talk) 21:50, 19 August 2020 (UTC)[reply]

BTW, I copied this message on the talk page so that we can keep memory about this "issue". Pamputt (talk) 21:52, 19 August 2020 (UTC)[reply]

Brilliant, thank you!! UWashPrincipalCataloger (talk) 18:53, 20 August 2020 (UTC)[reply]

New Deal

Salut. Est-ce que tu serais disponible pour initier en deux-trois clics Wikidata:Property proposal/The Living New Deal ID ? Je peux m'occuper de remplir la propriété des déclarations nécessaires ensuite. Thierry Caro (talk) 17:24, 28 August 2020 (UTC)[reply]

Voila c'est fait :D Bon courage. Pamputt (talk) 17:27, 28 August 2020 (UTC)[reply]

Merci bien ! Thierry Caro (talk) 18:11, 28 August 2020 (UTC)[reply]

Salut. Je suis preneur de Wikidata:Property proposal/Wisconsin Historical Society NRHP ID brute si tu as un petit temps. Thierry Caro (talk) 21:43, 5 September 2020 (UTC)[reply]

Merci bien. Je vais déployer les identifiants maintenant. Thierry Caro (talk) 11:54, 6 September 2020 (UTC)[reply]

Propriétés

Bonjour Pamputt, j'ai vu que tu as créé récemment plusieurs propriétés qui étaient restées en souffrance pendant ce mois d'août. Penses-tu pouvoir lancer également la création de Wikidata:Property proposal/NYARC Discovery ID ? Elle est à l'état "prêt" depuis deux bonnes semaines, et je ne pense pas qu'elle pose problème. Je pourrai compléter les déclarations si nécessaire, une fois que tu l'auras créée. Merci par avance. --Nono314 (talk) 20:17, 2 September 2020 (UTC)[reply]

@Nono314: je suis peu relie a Internet jusau'a la fin de la semaine donc je m'occuperai de cette creation dimanche si personne ne l'a fait d'ici la. Si tu es impatient, peut-etre que Thierry Caro pourra s'en charger. Pamputt (talk) 21:13, 2 September 2020 (UTC)[reply]

@Nono314:

Done as NYARC Discovery ID (P8574). Thierry Caro (talk) 02:33, 3 September 2020 (UTC)[reply]

Merci à tous les deux et bon wikibreak à toi Pamputt ! --Nono314 (talk) 07:04, 3 September 2020 (UTC)[reply]

Creation

Hi Pamputt. Would you mind creating Wikidata:Property proposal/opening hours (v.3)? It's been sitting in the queue for a while. Thanks! NMaia (talk) 01:07, 21 September 2020 (UTC)[reply]

@NMaia: no problem. It is done :D : opening time (P8626), closing time (P8627) Pamputt (talk) 05:41, 21 September 2020 (UTC)[reply]

LC Children's Subject Headings constraint violation

Thank you for creating the new LC Children's Subject Headings property.

When I added the ID sj96004824 to the Arthropoda item Q1360, I got this violation:

format constraint

The value for Library of Congress Children's Subject Headings ID (sj96004824) should match the regex sj\d{10}

--Adam Schiff (talk) 18:58, 25 September 2020 (UTC)[reply]

Done UWashPrincipalCataloger —Eihel (talk) 22:21, 25 September 2020 (UTC)[reply]

PhotoLondon ID

Thanks for creating photoLondon ID (P8657). However, the values seem to be displayed only as text strings, not external links (the ID for Lallie Charles (Q37449978) should link to this page for instance). Is this normal for new properties (i.e. a lag before external links become active), or some bug with the syntax? Could you investigate? Thanks, -Animalparty (talk) 16:58, 27 September 2020 (UTC)[reply]

@Animalparty: yeah this is "normal" for new property. Links should be active in 48 hour maximum. Pamputt (talk) 17:02, 27 September 2020 (UTC)[reply]

Ah, I see, thanks again! -Animalparty (talk) 17:03, 27 September 2020 (UTC)[reply]

Biographical Dictionary of Fourierism ID (P8686)

Please can you help me with this property? The property is not creating URLs to the relevant webpage, e.g. see Desirée Gay (Q3045216). Thanks MSGJ (talk) 19:18, 5 October 2020 (UTC)[reply]

@MSGJ: actually there is kind of dealy. The links should enable in 24-48 hours. Pamputt (talk) 19:45, 5 October 2020 (UTC)[reply]

Involved admin

Hi Pamputt,

What's your view on contributors acting as admins in discussions they are involved in? --- Jura 10:41, 23 October 2020 (UTC)[reply]

Dipole moment

[5] It does not seem to be a proper qualifier (maybe in the source?) — could you provide an example? There are many physical quantities that are measured in different conditions etc. but that is the first time I see 'date' as a qualifier rather than source-property. Wostr (talk) 16:53, 30 October 2020 (UTC)[reply]

@Wostr: Actually I mimic what I did with mean lifetime (P2645) on neutron. So not sure it is the good way but it quite convenient to create plot such as this one. Feel free to do as what seem to you the best. Pamputt (talk) 19:10, 30 October 2020 (UTC)[reply]

In this case IMO this 'date' should be included in the source (BTW right now this "source" tells nothing, it's just a journal with a page, no year, no title of the article, no volume, issue etc.) and that statement should have a preferred rank with most recent value (Q71533355). I can't do anything about it as I don't know the source of the value. Wostr (talk) 21:09, 30 October 2020 (UTC)[reply]

@Wostr: The "date" is already included in the source. See for example Review of Particle Physics (Q98479256). All the information you mention are present (are should be present) in the item of the journal article. I really do not think they shuld appear on neutron (Q2348)because we would duplicate many time the same information (and so if something has to be fixed, we just need to fix it once and not many times). Pamputt (talk) 21:30, 30 October 2020 (UTC)[reply]

MediaWiki and numerical identifiers

Where do you wish we should decide about this?--Trade (talk) 13:22, 1 December 2020 (UTC)[reply]

@Trade: I do not know whether there is good place to discuss that but currently there is here. It points to other past and on going discussions related to this "issue". Feel free to give your opinion. Pamputt (talk) 13:55, 1 December 2020 (UTC)[reply]

Need your help

I recently created my first property Gab username (P8919), but I don't know why he can't automatically generate a link, can you tell me? (｀・ω・´) (talk) 13:41, 5 December 2020 (UTC)[reply]

@-akko: actually there is a kind of cache for all newly created properties. So links should enable automatically in 24-48 hours. Nothing to do for now. Pamputt (talk) 13:43, 5 December 2020 (UTC)[reply]

Thank you. Also, is there a script for creating properties? Manual creation took me about half an hour. (｀・ω・´) (talk) 13:46, 5 December 2020 (UTC)[reply]

@-akko: so there is not really a script. It goes faster with the time when you have more experience. Also, you can use User:Matěj Suchánek/moveClaim.js that allow to copy a statement with value to another property (or item). To use it, add this line "mw.loader.load( '//www.wikidata.org/w/index.php?title=User:Mat%C4%9Bj_Such%C3%A1nek/moveClaim.js&action=raw&ctype=text/javascript' ); // User:Matěj Suchánek/moveClaim.js" in your Common.js. Then you just need to find a property rather similar to the one you are creating and copy some statements to the newly created property; it is highly efficient for the constrains. Pamputt (talk) 13:52, 5 December 2020 (UTC)[reply]

Thank you. Now I have enabled this tool (｀・ω・´) (talk) 14:13, 5 December 2020 (UTC)[reply]

I think Pintoch wrote a script to create properties. I haven't tried it myself, but for external-id ones it might work well. I generally use the approach outlined by Pamputt.

WikibaseJS-cli can also create properties, but one needs to learn how to use it first (and install it). facial hair (P8852) worked fairly well. --- Jura 15:17, 5 December 2020 (UTC)[reply]

Suite de Literary Encyclopedia pour les propriétés de type ext-id

Bonjour Pamputt,
Autant vous dire que le pourquoi du comment m'échappe encore !? Pour la forme, je vous livre qques constatat° empiriques qui n'ont pas été faites sur le Wikidata en prod évidemment :

Les liens peuvent fonctionner dès la protection (donc avant la déprotecti°)
La manip ne fonctionne pas à chaque coup, mais mes qques tests m'indiquent que les liens sont actifs la plupart du temps.
Un changement de protection (augmentation du degré ou de durée) peut rendre les liens actifs s'ils ne l'ont pas été lors d'une première tentative de protection. D'autres tentatives de protection-déprotection peuvent aussi rendre les liens actifs.
Un changement de formatter URL (P1630) (de https://www.SLDomain.TLD/a/$1 à https://www.SLDomain.TLD/autre/$1 par exemple), puis une protection-déprotection peut faire pointer les liens d'ID vers l'ancienne adresse (https://www.SLDomain.TLD/a/l_identifiant dans l'exemple). Une purge du cache avant ou après la protect° n'y change rien. D'autres manip rendent les liens d'ID vers les bonnes adresses.
Je donne mon avis même si je ne suis pas admin : ce bidouillage me fait peur et cette manip devrait être réservée pour des cas impérieux (de par son inconstance).

Au plaisir. —Eihel (talk) 07:44, 2 January 2021 (UTC)[reply]

supprimer les éléments créés par Heil )))AdolfHitIer(((

Bonjour, Heil )))AdolfHitIer((( a créé 3 éléments racistes (cf. la liste de ses contributions [ici). J'ai supprimé les textes mais les éléments restent avec le texte de modif raciste. Amicalement, --Olivier Tanguy (talk) 22:38, 7 January 2021 (UTC)[reply]

Salut Olivier Tanguy normalement, j'ai fait le ménage dans ses créations et modifications. Ca devrait donc être bon maintenant. Pamputt (talk) 22:39, 7 January 2021 (UTC)[reply]

CollectieGelderland-creator-ID

Hi Pamputt, we have now an external link for our external identifier for https://www.wikidata.org/wiki/Wikidata:Property_proposal/CollectieGelderland-creator-ID You asked me to ping when ready. Could you create this property for us? With kind regards --Hannolans (talk) 10:57, 15 February 2021 (UTC)[reply]

Done Pamputt (talk) 13:14, 15 February 2021 (UTC)[reply]

Traduction de propriétés

Salut,

Que penses-tu des traductions de libellés en français des propriétés subject lexeme form (P5830) et subject sense (P6072) (cf. Special:Diff/770404170 et Special:Diff/972024532).

Je me questionne sur la traduction de "demonstrates"@en par "concerne"@fr mais j'avoue ne pas forcément avoir de meilleure idée... (peut-être en inversant en « forme concernée » ?)

Cdlt, VIGNERON (talk) 15:04, 16 February 2021 (UTC)[reply]

Salut VIGNERON, c'est vrai que « concerne la forme/le sens » sonne bizarre. Pas d'opposition pour utilisée « forme/sens concerné(e) » à la place. Ça sonne moins alambiqué. Pamputt (talk) 19:31, 16 February 2021 (UTC)[reply]

Done VIGNERON (talk) 13:13, 20 February 2021 (UTC)[reply]

JAANUS ID (P9080)

Bonjour, j'ai remis votre RegEx avec ma touche perso, ça avait l'air d'être mieux ? Cordialement. —Eihel (talk) 06:22, 3 March 2021 (UTC)[reply]

@Eihel: En fait non, la capture ne semble pas être prise en charge par Wikidata. Donc ça ne fonctionne malheureusement pas. Pamputt (talk) 06:53, 3 March 2021 (UTC)[reply]

Okki. Remis comme avant, merci pour l'info ;) —Eihel (talk) 07:03, 3 March 2021 (UTC)[reply]

Incompréhension sur une modification

Bonjour,

Je n'ai pas très bien compris cette modification dans laquelle le nom d'espace dans ma signature est modifié. Il s'agirait d'une simple erreur certainement ? En tout cas, je serais intéressé de savoir si quelque chose m'a échappé dans la syntaxe.

Bonne continuation ! Cdlt — Baidax ^💬 09:10, 22 March 2021 (UTC)[reply]

Bonjour Baidax ah oui c'est intéressant. Aucune idée de ce qui a pu me conduire à faire ce copier-coller malheureux... Bonne continuations. Pamputt (talk) 10:18, 22 March 2021 (UTC)[reply]

Pas de souci dans ce cas, cela arrive. Bonne journée !

— Baidax ^💬 10:20, 22 March 2021 (UTC)[reply]

identifiant Storiaememoriadibologna (P9331)

Bonjour Pamputt,

par rapport à l'identifiant Storiaememoriadibologna (P9331) j'ai déniché un souci, probablement dû à l'expression régulière (contrainte de format), voir Q106034679. Je ne saurais pas résoudre le problème, j'espère bien que vous pourrez faire les corrections nécessaires. Cordialement--Patafisik (talk) 12:56, 22 March 2021 (UTC)[reply]

Bonjour Patafisik, j'ai changé l'identifiant pour qu'il convienne à l'expression régulière. En fait, bien que "palazzo-bonora-2951-luogo" soit présent dans le titre de la page, "2951-luogo" suffit pour envoyer sur cette page. C'est ce format qu'il faut privilégier et c'est ce que vérifie l'expression régulière. Pamputt (talk) 14:03, 22 March 2021 (UTC)[reply]

Merci, je comprends mieux maintenant comment ça marche. Bonne journée.--Patafisik (talk) 14:06, 22 March 2021 (UTC)[reply]

Property applies if regular expression matches (P8460)

Tracked in Phabricator
Task T150939
Open

Tracked in Phabricator
Task T240884
Open

Hello Pamputt, I see that you have created "applies if regular expression matches" Property to format external urls. I cannot see a working example of this property. It seems to me that this qualifier is ignored and wikidata always takes the first formatter url though the ID regexp does not match it. Can Property "applies if regular expression matches" be broken? Why for example IMDB ID ( https://www.wikidata.org/wiki/Property:P345 ) uses a special redirect site to format urls? Thank you! --Sokirko (talk) 18:23, 29 March 2021 (UTC)[reply]

Hello Sokirko

,
It's confusing, but the problem is known and this property is not being used at this time, at least not as it was intended to work. The developers have been on this issue for a while now (at the time it was about a RegEx training issue by contributors). However, this property is often used with the qualifier syntax clarification (P2916), which gives useful informations to contributors (Example on HURDAT ID (P502): syntax clarification (P2916)Can only link to list for year <2005). These additional links may be used outside of WD, but they are just informational. The problem will be fixed one day and this property may be useful at this time, because WD only accepts a single formatter URL (P1630) using single-best-value constraint (Q52060874). You can see the reason for this constraint using constraint clarification (P6607): If there are multiple values for URL formatter without preferred one, Wikibase software is unable to reliably determine default formatter for UI. Before, there were multiple IMDb IDs that were put together (person, title, etc.), but only one URL now works with a preferred rank. For changing URLs, an external URL formatter is used. To sum up, we can say that everything is "abnormally normal", nothing is broken. Best regards. —Eihel (talk) 00:19, 30 March 2021 (UTC)[reply]

UNITER Award person ID (P9581) and P9582 (P9582) created at the same

Hi,

It looks like we both decided to create the same property at the same time: UNITER Award person ID (P9581) and P9582 (P9582). How do we delete one of them? UWashPrincipalCataloger (talk) 08:01, 16 May 2021 (UTC)[reply]

Obviously the one that doesn't match what was proposed: compare "UNITER artist ID" (P9582)" with Wikidata:Property proposal/UNITER Award person ID
This also explains why the duplicate happened. --- Jura 08:15, 16 May 2021 (UTC)[reply]

Indeed UWashPrincipalCataloger I have no time to take care of this for now but we need to delete one of these properties for sure (I will do it tonight if not done before). Pamputt (talk) 08:58, 16 May 2021 (UTC)[reply]

Can't they be merged into one? - Coagulans (talk) 09:24, 16 May 2021 (UTC)[reply]

I think you can move the statements 1-by-1 and the tool should avoid most duplication. --- Jura 09:49, 16 May 2021 (UTC)[reply]

@UWashPrincipalCataloger, Jura1: thank you for the transfer of the statements into UNITER Award person ID (P9581). I've deleted P9582 (P9582) Pamputt (talk) 18:03, 16 May 2021 (UTC)[reply]

OrophinBot

Salut! I wonder if you have a time to look at Wikidata:Requests for permissions/Bot/OrophinBot, it has been a week now. Merci! Bennylin (talk) 10:13, 26 June 2021 (UTC)[reply]

Regex for Scenic Washington scenic drives and road trips ID (P9755)

Hi Pamputt,

Thank you for creating Scenic Washington scenic drives and road trips ID (P9755). I noticed that you revised the regex that we had in our proposal. But now I am seeing a format constraint violation: can you figure out why I'm getting a format constraint violation for property Scenic Washington scenic drives and road trips ID (P9755) on Bellingham (Q430267)?:

"The value for Scenic Washington scenic drives and road trips ID (poi/bellingham) should match the regex (poi\/)?[a-z]+(-[a-z]+)+."
It appears that lack of a hyphen in this identifier is causing the violation? Can you revise the regex so it works for identifiers like this one? Thank you. UWashPrincipalCataloger (talk) 15:13, 22 July 2021 (UTC)[reply]

@UWashPrincipalCataloger:

Done I was not sure whether there are identifiers withtout hyphen so I forced to have at least one. But there are, so I changed the regex accordingly. Pamputt (talk) 16:06, 22 July 2021 (UTC)[reply]

@Pamputt: Thank you! UWashPrincipalCataloger (talk) 16:11, 22 July 2021 (UTC)[reply]

@Pamputt: I'm still getting the constraint violation on Bellingham (Q430267), Anacortes (Q483595) and Westport (Q1007612). Does it take time for a regex change to take effect? UWashPrincipalCataloger (talk) 18:16, 22 July 2021 (UTC)[reply]
@UWashPrincipalCataloger: hmmm, actually I just see that I did not change the regex (probably not saved wehn I thought I did it). So it should work soon now. Pamputt (talk) 18:57, 22 July 2021 (UTC)[reply]
No more warnings! Thanks, and I see what you changed (+ to *). I don't know regex as well as you, but I can see now how that makes a difference. Thanks again! UWashPrincipalCataloger (talk) 19:54, 22 July 2021 (UTC)[reply]

Rafiki Eoax

Azul, despite your warning, Rafiki Eoax broke through [6] and blanked his talk page [7]. --Buxlifa (talk) 17:23, 29 July 2021 (UTC)[reply]

@Buxlifa: pour le moment je l'ai bloqué 3 mois juste sur la page Kabylia (Q46178) Pamputt (talk) 17:44, 29 July 2021 (UTC)[reply]

Proposition de propriété

Salut,

Je voulais t'en parler ce week-end et puis j'ai oublié, pourrais-tu jeter un coup d’œil et me dire ce que tu penses de cette proposition de propriété : Wikidata:Property proposal/Overnia ?

Cdlt, VIGNERON en résidence (talk) 07:10, 30 August 2021 (UTC)[reply]

Salut VIGNERON en résidence c'est tout bon, je ne vois pas de problème. Au milieu de la semaine, je créerai la propriété si il n'y a pas d'opposition ou de discussion. Pamputt (talk) 07:15, 30 August 2021 (UTC)[reply]

@VIGNERON en résidence: je viens de créer Overnia ID (P9845) (je suis en train d'ajouter les déclarations à la propriété). Bon courage pour le boulot :) Pamputt (talk) 08:16, 2 September 2021 (UTC)[reply]

Merci beaucoup ! (@Pierre Tribhou: pour info). Par contre, le lien automatique vers le site Overnia n'est pas généré, manquerait-il une propriété ? (pourtant, cela se base uniquement sur formatter URL (P1630) de mémoire, non ?) ou bien est-ce un simple problème de cache ? Cdlt, VIGNERON en résidence (talk) 11:11, 2 September 2021 (UTC)[reply]

@VIGNERON en résidence: oui c'est un problème de cache (ou quelque chose d'équivalent). D'expérience ce sera actif dans moins de 48h (24h si tu es chanceux). Pamputt (talk) 14:44, 2 September 2021 (UTC)[reply]

Propriété/créateur

Bonjour Pamputt. Sur https://www.wikidata.org/w/index.php?title=Q29245178&diff=1468458664&oldid=1468447998, tu as entré unknown value qui ressort valeur inconnue en français. J'ai beau essayer de faire pareil sur l'élément Q29245328, rien à faire, ça ne marche pas. Peux-tu m'expliquer comment procéder ? Merci d'avance. Cordialement. Père Igor (talk) 18:35, 4 November 2021 (UTC)[reply]

Bonjour Père Igor, pas de soucis

. Pour cela, il faut cliquer sur les petits rectangles à gauche de là où tu saisis l'élément Q. En cliquant dessus, tu verra apparaitre une liste déroulante où tu pourras choisir « valeur inconnue » ou « aucune valeur ». POur des explications plus complètes, voir Help:Statements/fr#Aucune_valeur_ou_valeur_inconnue. Pamputt (talk) 19:39, 4 November 2021 (UTC)[reply]

Property for potentially problematic content

Hi Pamputt,

Can you explain how the open questions about a property for problematic content at Wikidata:Property proposal/Offshore leaks database ID had been addressed? I assume you assessed the discussion and didn't merely count the number of templates used by participants. Feel free to explain this in your closure there or here. --- Jura 09:25, 23 November 2021 (UTC)[reply]

P10136

Bonsoir, on a eu le même réflexe au même moment de compléter la prop ;) —Eihel (talk) 22:56, 12 December 2021 (UTC)[reply]

Ah bah, oui ça arrive. Plus on s'en rend compte rapidement, moins il y a de ménage à faire. Merci de l'avoir vu car moi, j'étais passé à côté

Et merci aussi pour ta notification au créateur de cette propriété. Pamputt (talk) 06:40, 13 December 2021 (UTC)[reply]

P10221

I am still working on creating this, but it is more complicated than it seemed. The proposal really only covered one list, the Representative List of the Intangible Cultural Heritage of Humanity (Q110319947). UWashPrincipalCataloger (talk) 00:11, 31 December 2021 (UTC)[reply]

I proposed a solution to include all the lists on the poperty proposal page. Tell me if this is ok? Pamputt (talk) 08:13, 31 December 2021 (UTC)[reply]

P10222 format constraint

Hi Pamputt, the format constraint that you changed on P10222 does not work for all of the examples. The identifier added to Banksy (Q133600) is banksy-83467f and it is getting a constraint violation. The id kaws-c7a86e on KAWS (Q3194367) is also getting a constraint violation. Why not keep the regex simpler anyway? It was [a-z]+[-a-z0-9]+ in the proposal. UWashPrincipalCataloger (talk) 16:18, 31 December 2021 (UTC)[reply]

@UWashPrincipalCataloger: I fixed the regex. Usually it is better to write a regex that is not too wide so that one can detect invalid identifier. Sorry for the noise. Pamputt (talk) 17:46, 31 December 2021 (UTC)[reply]

Thank you! Happy New Year. UWashPrincipalCataloger (talk) 21:44, 31 December 2021 (UTC)[reply]

New properties

		The Wikidata Barnstar
		Thank you for creating the numismatic properties! Stratocaster47 (talk) 08:05, 1 January 2022 (UTC)[reply]

Hello!

I made some changes to Numista ID (P10205). Before, the ID's had to be preceded by "banknote", "piece", or "exonumia", which was a bit cumbersome. Now we've made some changes on the Numista website, so these keywords are no longer necessary and the IDs are simply the digits. Therefore, I've changed the formatter URLs a few days ago, but the links still don't seem to work. Could you possibly check if I did something wrong, please?

Best regards Stratocaster47 (talk) 16:18, 4 February 2022 (UTC)[reply]

Hi Stratocaster47, what you did looks fine. So it is likely a problem of cache. New links should be enabled in the next hours/days. Pamputt (talk) 17:17, 4 February 2022 (UTC)[reply]

How we will see unregistered users

Hi!

You get this message because you are an admin on a Wikimedia wiki.

When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.

Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.

If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.

We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.

Thank you. /Johan (WMF)

18:20, 4 January 2022 (UTC)

Property proposal on Offizielle Deutsche Charts album ID

Dear Pamputt,

in my opinion the Property proposal is finished and the Property can be created. We also have discussed the equivalent Property proposal for songs here.

Greetings Bigbossfarin (talk) 15:52, 9 January 2022 (UTC)[reply]

Hi Bigbossfarin, I marked the property as ready for creation. Pamputt (talk) 16:10, 9 January 2022 (UTC)[reply]

Wikisimpsons ID

I do find it quite jarring how some MediaWiki identifiers use URL slugs and other use Page ID's --Trade (talk) 01:03, 24 January 2022 (UTC)[reply]

@Trade: all the last created properties related to MediaWiki use the PageID that's why I ask systematically. The PageID identifier has more advantages than the text ID but is a bit more complicated to find so I make sure I have the agreement of the supporters of the creation of a property. Pamputt (talk) 05:08, 24 January 2022 (UTC)[reply]

Deleted property

Greetings! You said "No need to remove everything. When you delete a property (or an item), all statements are automatically deleted." This does not seem to be the case? I deleted P4883 (P4883) but the deleted property is still showing on the items. Do I need to be more patient? I have requested a bot to remove these claims. — Martin (MSGJ · talk) 12:27, 31 January 2022 (UTC)[reply]

Hi MSGJ. Oh I misunderstood what you were asking. I thought you were talking about the statements of the property itself. Now I understand, you were talking about statement using this property on the items. So the answer is definitely no. Such statements are not deleted automatically. Usually, before deleting a property, we checked that the property is not used anymore on any item. That's said, we can still remove the statements after the property deletion and depending on the number of statements, it is worth asking bot help. Pamputt (talk) 12:37, 31 January 2022 (UTC)[reply]

Thanks for your answer above. I now have another :) If two properties are to be merged, is it possible to redirect one to the other, like we do items? Or does one property need to be deleted and all statements migrated? Regards — Martin (MSGJ · talk) 12:23, 14 February 2022 (UTC)[reply]

Hi MSGJ thank you very much for your work on properties for deletion. To answer your question, as far as I know, it is not possible to merge properties. So the answer is to migrate all statements before/after deleting. What is your case? Pamputt (talk) 12:48, 14 February 2022 (UTC)[reply]

Thanks, yes I think you are right — Martin (MSGJ · talk) 21:09, 15 February 2022 (UTC)[reply]

Wikidata:Property proposal/original catalog description

Hi Pamputt,

Is there any chance you could take a look at closing Wikidata:Property proposal/original catalog description? Other than the one oppose, there seems to be mostly support, and no additional comments in over a month now. It would be great to be able to add these statements soon. Thanks! Dominic (talk) 22:42, 7 February 2022 (UTC)[reply]

Hi Dominic I created the property. There were no discussion since more than one month so I guess it is ok. Pamputt (talk) 17:58, 12 February 2022 (UTC)[reply]

Link property

Hi! Do you know why external link doesn't work in this new property? https://www.wikidata.org/wiki/Q110199683#P10357 Thanks! --Davidpar (talk) 12:45, 12 February 2022 (UTC)[reply]

Hi Davidpar. It is a known situation. I am not sure about the technical reason but after each property creation, it takes 24-48 hours before the links become enabled. So it should be the same also for TV3 video ID (P10357) Pamputt (talk) 17:13, 12 February 2022 (UTC)[reply]

Ah, I didn't know that it is common for each property creation. I have to be patient. Thanks! --Davidpar (talk) 19:07, 12 February 2022 (UTC)[reply]

P8990

Hi, when I followed a link I got to a different person, did as well in all the Wikidata property example(s), since you created it I thought you might know how to fix it. TherasTaneel (talk) 14:28, 13 February 2022 (UTC)[reply]

I have started a discussion on the property talk page. I do not know any way how to fix that easily. Pamputt (talk) 16:41, 13 February 2022 (UTC)[reply]

Recent created properties

How would you say my work of creating properties is going so far? --Trade (talk) 23:31, 13 February 2022 (UTC)[reply]

Mnemosine ID

Thank you very much for creating the property Mnemosine ID (P10373). A cordial greeting, --PePeEfe (talk) 11:08, 19 February 2022 (UTC)[reply]

Wikidata:Property proposal/TASS Encyclopedia ID, Wikidata:Property proposal/Chuvash Encyclopedia ID

Hi, Pamputt! I have corrected the comments of the participants in the discussion in both proposed properties. Could you tell me what should be completed for subsequent approval? MasterRus21thCentury (talk) 16:53, 19 February 2022 (UTC)[reply]

Hi MasterRus21thCentury, basically, just need to get some support after the splitting of the property. There is not yet for both property proposals. Pamputt (talk) 17:06, 19 February 2022 (UTC)[reply]

In principle, you can call on a few experienced Wikidata contributors who have had action with similar properties. They just can express their opinion about them and then make further decisions on them. MasterRus21thCentury (talk) 17:11, 19 February 2022 (UTC)[reply]

Requested creation

Hi Pamputt, I appreciate your hard work so far in creating properties. If you don't mind, could you create reddoorz_hotel_ID and skyscanner_hotel_ID as I'm trying to import the values soon. Germartin1 (talk) 15:53, 12 March 2022 (UTC)[reply]

Reminder to participate in the Ratification vote of UCoC Enforcement guideline

This message has been sent because you are administrator in this project. If you voted, Thank you and please ignore this message 🙂

Hello Pamputt,

The Ratification vote of Universal Code of Conduct Enforcement Guidelinein currently taking place until March 21. If you didn't vote yet, please take a few minutes to participate the ratification vote! Your voice is important.

Best, —YKo (WMF) via MediaWiki message delivery (talk) 04:44, 15 March 2022 (UTC)[reply]

Special:Diff/725284578

What did you mean? It, probably, doesn’t make sense. Maybe you meant subclass of (P279)language isolate (Q33648) or linguistic typology (P4132)isolating language (Q7423311)? 217.117.125.83 13:05, 18 September 2022 (UTC)[reply]

Hi, I did not remember why I used linguistic typology (P4132). Anyway, I now use instance of (P31). Pamputt (talk) 05:51, 19 September 2022 (UTC)[reply]

P5654

Ultimately I think it's retired ID and we don't delete them (they just use archived versions) but in this case looks like database has been moved. I don't know. Eurohunter (talk) 20:43, 5 November 2022 (UTC)[reply]

existed so archived version schould be added. Eurohunter (talk) 18:04, 7 November 2022 (UTC)[reply]

As you said, the database has been moved and the page content is strictly the same so I do not know exactly what to do. Let us see what the other contributors think. Pamputt (talk) 19:23, 7 November 2022 (UTC)[reply]

If you are sure page content is the same then it mean it was moved from France Musique to Radio France so in this case we could merge them under Radio France. Eurohunter (talk) 15:37, 8 November 2022 (UTC)[reply]

The content is the same except that the Radio France may be up to date, for example is someone attended to a radio show that occured after the migration. And we also need to be sure all identifiers have been migrated to Radio France. Pamputt (talk) 15:57, 8 November 2022 (UTC)[reply]

BIBSYS ID

Do you know how to find ID using https://authority.bibsys.no? Eurohunter (talk) 18:39, 7 November 2022 (UTC)[reply]

@Eurohunter not really. The only way I am aware is using VIAF. Pamputt (talk) 19:22, 7 November 2022 (UTC)[reply]

France Culture ID/ Radio France ID

Hi Pamputt, Please note: when replacing France Culture ID, by Radio France ID on Wikidata, the link does not show on 'External Links' section on French Wikipedia articles (it has to be added manually). Whereas France Culture ID does show, and is of valuable interest. Cheers. JoSloane (talk) 11:59, 2 December 2022 (UTC)[reply]

Bonjour JoSloane. En fait il faudrait ajouter l'identifiant Radio France person ID (P10780) à w:fr:Modèle:Bases. Il faut lancer la discussion sur frwikipedia. Pamputt (talk) 12:26, 2 December 2022 (UTC)[reply]

Oui, c'est ça tout à fait, mais moi, je ne sais pas faire. Cheers.--JoSloane (talk) 12:30, 2 December 2022 (UTC)[reply]

@JoSloane J'ai démarré la discussion ici. N'hésite pas à commenter/améliorer la formulation. Pamputt (talk) 12:44, 2 December 2022 (UTC)[reply]

Muziekencyclopedie ID

Hello Pamputt, some time ago you created the 'Muziekencyclopedie ID' property (P9589). For example Q106730227 (Ernesto van Dal) is using it with the ID "Ernesto+Van+Dal". When I click on that ID the + in the ID is URL encoded replaced by %2B. As a result of that replacement I don't see the page about him but a site search result. If I replace the %2B in the URL to a space, I will see the correct page on the Muziekencyclopedie website. Replacing the + in the ID to a space is right now no option because every character to the right of that space is automatically removed. Is there a way to avoid the URL encoding? And if not, can the space be added to the allowed characters in the ID? Robotje (talk) 12:28, 4 February 2023 (UTC)[reply]

Hello Robotje, I have modified the constrain so that it accepts space (and not "+"). Tell me if this is good for you now. Pamputt (talk) 13:23, 4 February 2023 (UTC)[reply]

Wow, big improvement! Thanks. Only problem left over is that most of the more than 1000 Q-items using it, still have the + sign. Do you have a bot to correct them? Robotje (talk) 13:33, 4 February 2023 (UTC)[reply]

Unfortunately no, I have no bot to do that for now. You may ask on Wikidata:Bot requests. Pamputt (talk) 13:49, 4 February 2023 (UTC)[reply]

My request there was approved and all the relevant Q-items were corrected. - Robotje (talk) 21:56, 4 February 2023 (UTC)[reply]

Please check the lexemes that were created with Gabrabot

https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Bot/Gabrabot#Gabrabot Mtanti (talk) 16:26, 26 February 2023 (UTC)[reply]

Supression of data about JFColosimo

Hello, just wanted to let you know that I deleted a lot of data from the JF Colosimo Wikidata because most of it was [original research|WP:OR] and was used for a promotional presentation of the subject of the page. We are talking about that here right now.

Cordially, AgisdeSparte (talk) 07:54, 30 June 2023 (UTC)[reply]

PamputtBot

Hi, Pamputt, The last edit by your bot PamputtBot dates from January 20th, 2018. I would propose to remove its bot flag due to inactivity. Do you oppose to that? Of course you can always reapply for a bot flag, once you would want to reactivate it. --Lymantria (talk) 12:18, 13 February 2024 (UTC)[reply]

@Lymantria, you are right, it is better to remove the bot flag for now. You can do it :) Pamputt (talk) 10:53, 1 March 2024 (UTC)[reply]

Restore

Hello. Could you restore Q51758893 and Q51757952, so I could extend them? Eurohunter (talk) 21:36, 24 February 2024 (UTC)[reply]

What do you think? ~~

@Eurohunter: you should ask to Lymantria who has deleted those items. Pamputt (talk) 09:37, 3 March 2024 (UTC)[reply]

@Eurohunter: can you give indication what you like to add in order to make the items fulfill notability criteria? Q51758893 was lacking any form of source, while the sources of Q51757952 were quite thin. I need substantially more to restore. --Lymantria (talk) 12:55, 3 March 2024 (UTC)[reply]

@Lymantria: Hello. First, I would need to know what is there, otherwise it is hard to say if it's already there or not yet. For now I have at least one ID and reference to add. Eurohunter (talk) 18:40, 3 March 2024 (UTC)[reply]

I won't restore without more clarity. Q51758893 was lacking any source, so there is nothing to know there. Q51757952 was source by an interview at YouTube you had and by [8]. --Lymantria (talk) 21:07, 3 March 2024 (UTC)[reply]

New property for deletion

Hello, I wanted to inform you that I've just nominated for deletion the property:P8409 that you created. Horcrux (talk) 14:49, 16 May 2024 (UTC)[reply]

Inactivity

Hi Pamputt, Just to let you know: at this moment your admin action count over the last 6 months is 0 logged actions. That means that you are about to loose your adminship at July 1st due to inactivity, unless you perform at least 5 admin actions before that date. Kind regards, Lymantria (talk) 13:53, 26 June 2024 (UTC)[reply]

Hi Lymantria, thank you for letting me know. I'm actually on wikislow at the moment. I think it's best to give up my admin tools for the time being. If I resume an active activity that requires admin tools, I'll be able to reapply at that point. I let you remove my admin right ;-) Pamputt (talk) 14:17, 26 June 2024 (UTC)[reply]

Okay, thank you for your service! --Lymantria (talk) 14:39, 26 June 2024 (UTC)[reply]

Property:P9590

Hi! I'm notifying you that I have made a request for deletion of North Carolina session law (P9590), which was created by you. I argue that a more general property, law identifier (P8550) should be used instead. Samoasambia ✎ 19:07, 10 October 2024 (UTC)[reply]

Additions to the UNESCO ICH elements

Hi @Pamputt!

I am in the process of importing all new ICH element on UNESCO lists. I saw you have done work on some of the elements, and I would like to give a heads-up and hope I will not break any of your work. The project is on my OpenRefine at the moment, and I can try to share it online in some way if you wish.

I am proposing some changes to the best practices that I have recorded in m:Wiki_Loves_Living_Heritage/How_to_import_an_inventory. These are

I try to keep in mind multilinguality for the reuse of the data and arrange language-specific data (original title and the source page) where it's connected to both the insciption and the language. The best place for these is in the source statements. (I think)
Some already inscribed elements have now been re-inscribed, usually with more countries joining. Their old IDs have been deprecated and new oned added instead. We must put the UNESCO ICH ID (P10221) in a place where it is connected to the inscription on the list, start date and now additionally the end date. For this reason I think the best place is in the main intangible cultural heritage status (P3259) statement. When a new inscription overrides the old one, we will add end date to the old one and make another intangible cultural heritage status (P3259) with different start date. We should probably still keep the separate main statement for UNESCO ICH ID (P10221).

If you are interested, please join the (rather inactive, but useful) Wiki Loves Living Heritage Telegram group. Susanna Ånäs (Susannaanas) (talk) 17:05, 11 December 2024 (UTC)[reply]

Hi, what you said looks fine to me, so go ahead. I have no time for now but I could check what you will do later ;-) Pamputt (talk) 16:29, 15 December 2024 (UTC)[reply]