Shortcuts: WD:PC, WD:CHAT, WD:?

Wikidata:Project chat

From Wikidata
Jump to navigation Jump to search

Wikidata project chat
A place to discuss any and all aspects of Wikidata: the project itself, policy and proposals, individual data items, technical issues, etc.

Please use {{Q}} or {{P}} the first time you mention an item or property, respectively.
Other places to find help

On this page, old discussions are archived after 7 days. An overview of all archives can be found at this page's archive index. The current archive is located at 2022/03.

Proposed config change: remove changetags right from users[edit]

Hi everyone! I’d like to propose a change to the wiki configuration related to change tags.

Background: MediaWiki has two rights related to change tags: applychangetags allows users to add tags (like OpenRefine [3.5] or Wikidata User Interface) to their own edits and actions as they perform them, while changetags lets users add and remove tags after the fact, on their own edits and actions as well as others’. (A third right, managechangetags, controls who is allowed to create and delete change tags, and is limited to administrators.) By default, MediaWiki assigns both rights to all users; any registered user can add or remove arbitrary user-defined tags on anyone’s edits and actions. (Such tag changes are logged at Special:Log/tag.) Exempt from this are software-defined tags, which cannot be added or removed manually; this includes all the OAuth tags. So, for example, because OpenRefine [3.5] is a user-defined tag while quickstatements [2.0] is a software-defined tag, anyone can add the OpenRefine tag to a QuickStatements edit, but it’s not possible to remove the QuickStatements tag. You can probably imagine that this can result in confusion, and I personally find it weird that MediaWiki lets any registered user do this by default.

Proposal: Remove the changetags right (but not the applychangetags right!) from all users, and instead add it to other, more limited groups – maybe confirmed/autoconfirmed users, maybe even more limited than that. Some Wikimedia wikis have already made similar changes, namely Wikimedia Commons (T134196) and Meta (T283625), as well as English (T97013), French (T98629), Croatian (T270996), Russian (T136187), and Turkish Wikipedia (T264508).

Open questions:

  • Special:Log/tag is currently mostly populated by WE-Framework gadget – apparently this gadget (sometimes?) tags its edits after making them. This might break due to the config change, but looking at the source code, I think this might not actually be needed anymore – the extra action: 'tag' probably dates back to when the action: 'wbeditentity' API that actually made the edit had no tags parameter yet (it was added in T229917), and when the tags parameter was added to WEF’s action: 'wbeditentity' call, the separate action: 'tag' call wasn’t removed. @Vlsergey: can you check / confirm this, and maybe remove the call that is hopefully no longer needed?
    • Update: I’ve submitted a pull request to remove the unneeded (I think) API call.
      • Update: This was merged and deployed.
  • Which group(s) should the right be limited to? Autoconfirmed/confirmed users, i.e. most people? Admins and bots, like on the other wikis where it was removed from users? Something in between, like rollbackers?
    • Update: So far, it looks like we’re going for admins only (without bots).

If the community agrees on this change, and the open questions are resolved, the next step would be to open a Phabricator task – see meta:Requesting wiki configuration changes.

Thoughts? :) Lucas Werkmeister (talk) 13:25, 28 February 2022 (UTC)[reply]

 Support I think rollbackers (and approved bots?) might be the right group here for this. Maybe this should be an RFC though? ArthurPSmith (talk) 17:58, 28 February 2022 (UTC)[reply]
I don't think an RFC is necessary unless people object to it. It can be easily changed again if necessary. - Nikki (talk) 19:11, 28 February 2022 (UTC)[reply]
 Support Agree with above. Sjoerd de Bruin (talk) 19:07, 28 February 2022 (UTC)[reply]
 Support It sounds reasonable to me. - Nikki (talk) 19:15, 28 February 2022 (UTC)[reply]
  •  Oppose the added value of this request seems somewhat limited and the impact on improving data quality on Wikidata close to nil.
    Given that the developers are already much challenged with a backlog of handling requests from the community from 2019/2020/2021, it's better not to add more to the queue.
    There are other requests with clearly added-value and where the community has already invested much time and efforts in the analysis of the needs and the planning of the improvements. --- Jura 08:08, 1 March 2022 (UTC)[reply]
    This is a trivial change to the config, nothing Wikidata developers would have to deal with. --Matěj Suchánek (talk) 08:45, 1 March 2022 (UTC)[reply]
    • It still needs to be done by developers and takes up time they could be using to handle other requests. --- Jura 08:47, 1 March 2022 (UTC)[reply]
      Wiki configuration changes of this kind can be implemented by volunteers and deployed during a backport window. Matěj is right, your concern for the developers is not warranted in this case. --Lucas Werkmeister (talk) 09:10, 1 March 2022 (UTC)[reply]
      Unfortunately volunteers can't deploy anything of Wikimedia websites. Isn't it? --- Jura 09:28, 1 March 2022 (UTC)[reply]
They can propose changes to be deployed, including during the regular backport windows (explained at the link I provided above), which take place every Monday to Thursday, as Matěj mentions below. --Lucas Werkmeister (talk) 18:56, 1 March 2022 (UTC)[reply]
    • Sorry, but this is silly. Are you suggesting the configuration should not be changed even if communities request that, because (it is claimed that) it takes (some) developers' time? So we will first wait for the major stuff to be done and then we can deal with this trivial request? Do you know that there is reserved time specifically for this kind of requests every Mon-Thu? --Matěj Suchánek (talk) 09:36, 1 March 2022 (UTC)[reply]
      It's just not a priority.
      At least we seem to agree that it requires Wikimedia Foundation developers to handle them.
      Also, as a change to Wikidata org, it would probably also require Wikidata product management to look into it, review and approve it.
      We have other configuration changes that are lingering as neither have time to deal with them. So we don't really want them to work on requests that only have limited or no added value and almost nil impact on improving data quality on Wikidata. --- Jura 09:45, 1 March 2022 (UTC)[reply]
it requires Wikimedia Foundation developers to handle them. The need for such changes is well known, and there is an established and well-functioning procedure for handling them. Note that changing user rights is specifically mentioned as one of the types of requests at meta:Requesting wiki configuration changes.
it would probably also require Wikidata product management to look into it, review and approve it. I’ve already had a brief discussion with Lydia about this change, and she’s okay with it if the community decides it.
We have other configuration changes that are lingering That’s not a valid reason for opposing this request, in my opinion. But if you tell me which other simple configuration changes you have in mind, I can take a look at them.
--Lucas Werkmeister (talk) 18:56, 1 March 2022 (UTC)[reply]
  •  Support I regularly have to come back and clean up tags added by new users [1]. --Matěj Suchánek (talk) 08:45, 1 March 2022 (UTC)[reply]
  •  Support, but please do not bundle this with any existing custom purpose group such as rollback as this would make things more difficult to govern. So, the three options in my opinion are: (1) bundle with autoconfirmed (i.e. make it available to all trusted users), or (2) bundle with admin (make it available by request), or (3) make a new custom group for this where users can request access based on some policy to be written. —MisterSynergy (talk) 10:46, 1 March 2022 (UTC)[reply]
I would lean towards (2) for now (so far it doesn’t sound like there is a need for (1)). (3) is a good option for the future if we need it, but I don’t think we need to start with it. --Lucas Werkmeister (talk) 18:56, 1 March 2022 (UTC)[reply]
  •  Support per MisterSynergy. --Mirer (talk) 13:02, 1 March 2022 (UTC)[reply]
  • the effort of arguing about this seems larger than just implementing it. BrokenSegue (talk) 22:41, 1 March 2022 (UTC)[reply]
  •  Support per Matěj Suchánek. --Epìdosis 11:19, 6 March 2022 (UTC)[reply]
  • I’ve submitted a pull request to WE-Framework; if that gets merged soon, I think we have enough consensus here to go ahead with the change. --Lucas Werkmeister (talk) 20:11, 9 March 2022 (UTC)[reply]
The WE-Framework change was merged and deployed. I found another gadget in Special:Log/tag that adds tags separately, Infobox export gadget, but it turns out that only old versions of the gadget do this. I’ve left a notice about this at Help talk:Infobox export gadget § Stop tagging edits after they were made; in the meantime, since the old gadget versions are only used comparatively rarely (if you look at the recent changes, you’ll see way more InfoboxExport-tagged edits with no corresponding log entry, coming from wikis that use the latest version), I think we can still go ahead with this change. --Lucas Werkmeister (talk) 13:18, 13 March 2022 (UTC)[reply]
  • I’ve just submitted T303682 to request this config change. Unless an admin tells me otherwise, I think we have enough consensus here to deploy the config change, and I’ll try to get it deployed soon. --Lucas Werkmeister (talk) 13:18, 13 March 2022 (UTC)[reply]
    Scheduled for deployment next Monday. (I’m mainly just mentioning it here to prevent the thread from being archived before the change is done.) Lucas Werkmeister (talk) 17:24, 19 March 2022 (UTC)[reply]
    @Lucas Werkmeister: actually will this change break the commons android app? Reading the discussion at [2] suggests they are using the `action=tag` method to change tags after creation. I can't seem to find the source to see if they ever fixed this. BrokenSegue (talk) 23:51, 19 March 2022 (UTC)[reply]
    Actually upon further investigation it looks like the commons app water later changed to do the right thing [3]. Was fixed in 2020. BrokenSegue (talk) 00:14, 20 March 2022 (UTC)[reply]

Universal Code of Conduct Enforcement guidelines ratification voting open from 7 to 21 March 2022[edit]

You can find this message translated into additional languages on Meta-wiki.

Hello everyone,

The ratification voting process for the revised enforcement guidelines of the Universal Code of Conduct (UCoC) is now open! Voting commenced on SecurePoll on 7 March 2022 and will conclude on 21 March 2022. Please read more on the voter information and eligibility details.

The Universal Code of Conduct (UCoC) provides a baseline of acceptable behavior for the entire movement. The revised enforcement guidelines were published 24 January 2022 as a proposed way to apply the policy across the movement. You can read more about the UCoC project.

You can also comment on Meta-wiki talk pages in any language. You may also contact the team by email: ucocproject(_AT_)wikimedia.org

Sincerely,

Movement Strategy and Governance

Wikimedia Foundation --YKo (WMF) (talk) 04:23, 7 March 2022 (UTC)[reply]

As a gentle reminder, the voting period is about halfway through, and will be closing about 7 days from now. YKo (WMF) (talk) 06:33, 14 March 2022 (UTC)[reply]

Moving P2190 - C-SPAN Person ID forward from string to numeric IDs, what are the next steps?[edit]

It seems there is general consensus on the talk page for C-SPAN person ID (P2190) to move from string to numeric IDs and C-SPAN organization ID (P4725) already uses numeric form. I'm sitting on the resolved string to numeric matches (TSV) to make the move quick once the mechanism to switch is clarified. Would deprecating the existing property string value and adding the numeric as the new property numeric value the preferred approach? Is an existing bot or tool to deprecate the old values and add new ones or should quick statements be used? Please chime in on the property talk page to clarify a process for changing the Identifiers. Wolfgang8741 (talk) 16:41, 7 March 2022 (UTC)[reply]

Using templates in talk page headers breaks navigation from history and watchlist pages. --Tagishsimon (talk) 16:57, 7 March 2022 (UTC)[reply]
Fixed, and thank you for the information though no warning is issued to users. This seems more a technical limitation than an issue users should need to avoid. The template could be converted to static string on save with the template value to avoid the issue for those unaware. Now that knowledge has been shared with me... I'll avoid templates in headers. Wolfgang8741 (talk) 19:01, 7 March 2022 (UTC)[reply]

Haven't heard anything further on the property talk page, I'm uploading the matched numeric IDs to P2190. Once the two Quick statement batches are complete (mentioned on the property talk page), what is the suggested way to deprecate all the string IDs for the property? I haven't deprecated at scale before. Wolfgang8741 (talk) 15:01, 14 March 2022 (UTC)[reply]

Request for property creation review[edit]

I am not sure if this is the right place to ask, let me know if I should take this request elsewhere. The properties our institution proposed seems ready for creation, I am wondering if a property creator can kindly spare some time look it over and see if there are any problems and perhaps help with the property creation? Any help is greatly appreciated.

Here are the links to the property: [[4]] [[5]] [[6]]

Hsuaniwu (talk) 02:24, 11 March 2022 (UTC)[reply]

I think there is just a backlog of items to create Category:Properties_ready_for_creation. Since it's a lot of work for the property creators, I think it's worth to wait a little longer, and it will happen. --Newt713 (talk) 08:36, 13 March 2022 (UTC)[reply]
Totally understandable and thanks for the clarification Hsuaniwu (talk) 01:46, 14 March 2022 (UTC)[reply]
What is your institution? It's undisclosed on your user page. SilentSpike (talk) 10:02, 13 March 2022 (UTC)[reply]
I have added institution to my page, sorry still not too familiar with how everything works yet Hsuaniwu (talk) 01:52, 14 March 2022 (UTC)[reply]
Ah thank you, no apology needed, was just curious since you mentioned "our institution". For reference, with regard to whether disclosure is required: my understanding is that the Wikimedia terms of service only require disclosure of any paid editing (usually done on userpage) where local wiki policy does not say otherwise (which is the case on Wikidata). However, generally it's probably good practice to disclose affiliations whether paid or unpaid anyway. SilentSpike (talk) 23:02, 15 March 2022 (UTC)[reply]

Number of Ukrainian refugees via Wikidata?[edit]

Hello, I would like to learn how to use Wikidata for the numbers of Ukrainian refugees by country. I started a conversation here. Would you like to help me? Ziko (talk) 11:35, 12 March 2022 (UTC)[reply]

I'll reiterate what I have written elsewhere here too. I would like us to get into the habit of storing the latest data point on Wikidata and all older ones in the Data namespace on Wikimedia Commons. The way we have for instance population (P1082) in countries and municipalities is a bit arbitrary regarding how granular data we store and not very nice when handling the items. Also, items like COVID-19 pandemic in the United States (Q83873577) where we have number of deaths (P1120) with daily updates quickly becomes unwieldy. For population, we have tabular population (P4179) but really, we should have some generic qualifier to point to a data file on commons for a property so that we don't need to create specific "tabular X" properties for all these kinds of properties (a substantial number of properties can have large amounts of time bound data). Ainali (talk) 11:06, 13 March 2022 (UTC)[reply]
Thanks for your insight, Ainali! Would you like to start on Commons and show us how it works? Ziko (talk) 15:40, 15 March 2022 (UTC)[reply]
@Ziko One earlier conversation regarding the topic of refugees in general. https://www.wikidata.org/wiki/Wikidata:Project_chat/Archive/2017/02#refugee. There are many conversations, I can post to your talk page if you like if I find any other previous conversations...maybe best if I find some previous conversation that lead to more insight into the matter. Maskingself (talk) 12:01, 18 March 2022 (UTC)[reply]
No, I think I got it wrong. That conversation is about adding that a specific individual was a refugee. I'll continue the searching. Maskingself (talk) 12:25, 18 March 2022 (UTC)[reply]

API[edit]

Is there an api-version of this question? Testkonto 42 (talk) 14:28, 13 March 2022 (UTC)[reply]

Yes, but while you could use the API, it's more common (as well as flexible) to use SPARQL to search for things.
MWAPI: https://www.wikidata.org/w/api.php?action=query&format=json&list=search&srsearch=haswbstatement%3AP5736%3D1497
SPARQL: https://query.wikidata.org/#SELECT%20%3Fitem%20%3FitemLabel%20WHERE%20%7B%0A%20%20%3Fitem%20wdt%3AP5736%20%221497%22%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%7D Infrastruktur (talk) 15:34, 13 March 2022 (UTC)[reply]
Takk, Infrastruktur! In this specific case, I think the first version fits my need better than the latter! Testkonto 42 (talk) 19:44, 13 March 2022 (UTC)[reply]

Queries for metadata of the presentations of Wikidata Data Reuse Days 2022[edit]

As Wikidata Data Reuse Days 2022 is coming, I decided to create a Wikidata item for each presentation and structure the information that is presented in the description of each presentation in this page in Wikidata.

Now, we can query its data as shown in the queries below. The queries that I liked the most are Graph of all talks, edges are created through "follows", "followed by", "main subject" and "speaker" and Tree view of the subjects grouped by instance of and sorted by most discussed classes (thanks to this query I knew that an instance of W3C Recommendation (Q2661442) was one of the subjects of one of the presentations).

Queries

Additional information

I also planned to add the following properties to the items of the presentations, but I didn't have more time to add them.

Next steps

Once the recordings are uploaded to Commons. I think each presentation can be linked to the video at Commons by using the property video (P10) at Commons.

According to the description of some the presentations (see this one, the recordings are going to be uploaded to Wikimedia Deutschland’s Youtube channel, but if help is needed to upload them to Commons, let me know since I can help uploading them and also linking them to their corresponding Wikidata items of each of the presentations.

Rdrg109 (talk) 20:15, 13 March 2022 (UTC)[reply]

@Rdrg109 Given the recent discussions about the notability of Wikimedians, this endeavour could very well be perceived as an open provocation to parts of the community. I for one am very unhappy about a lot of new items that seem to fail WD:N. --Emu (talk) 21:08, 13 March 2022 (UTC)[reply]
I second the concerns. What if this task wasn't done for navel-gazing Wikimedia purposes, but by a SEO operative trying to increase information on their company? Every board member, press release, product, meeting and event given a Q-ID ("Joe Schmo", "hiring of Joe Schmo", "promotion of Joe Schmo", "2019 third-quarter sales presentation by Joe Schmo", "2022 Toyota Sale-a-Thon event at the Ogden Car Barn in Utah", etc. ad nauseum)? I think there would be significant pushback if such an operation were discovered, even if well-intentioned. -Animalparty (talk) 21:12, 14 March 2022 (UTC)[reply]

Scraping Javascript Databases[edit]

Is there a way to scrape a database like the Indian NGO Darpan (ngodarpan.gov.in), where every entry is only opened by javascript:void(0); with no extra URL per entry? I guess not, but perhaps you know a workaround? Newt713 (talk) 21:13, 13 March 2022 (UTC)[reply]

That javascript reads data from their API and displays it in the browser. You can investigate the requests with your browser's dev tools—e.g. Firefox or Chrome—and try to make similar requests to the API (be gentle, go slow). As long as there is no cookie stuff in the way, you will probably receive JSON objects so that you do not need to scrape anything from an HTML page. —MisterSynergy (talk) 21:25, 13 March 2022 (UTC)[reply]
Thanks. But it looks like there is a server generated one time identifier I can't get around. --Newt713 (talk) 07:09, 14 March 2022 (UTC)[reply]
@Newt713: I might be able to help, I've done scraping, but the website seems to be down. Germartin1 (talk) 07:24, 14 March 2022 (UTC)[reply]

You first need to retrieve a csrf token in a separate get request, in order to request the payload with a post request. There is also a session cookie required. Here is a very simply demo Python script which works for me:

MisterSynergy (talk) 08:39, 14 March 2022 (UTC)[reply]

Thank you. On a single entry it works, and good to know this is possible. But I'm not at that level of scripting :) But Germartin1 found a set on GitHub I'm working with now. All the best --Newt713 (talk) 17:53, 14 March 2022 (UTC)[reply]

List of victims of the 2022 Russian invasion of Ukraine (Q110999040)[edit]

Here is a SPARQL-powered list of victims of the 2022 Russian invasion of Ukraine (Q110999040) : https://w.wiki/4wtu

Louperivois (talk) 04:02, 14 March 2022 (UTC)[reply]

Deleting of GND redirects – Right or wrong?[edit]

In the request for comment Handling of stored IDs after they've been deleted or redirected in the external database a consensus emerges that identifiers that are given a bad rank should also be kept. As the administrator Emu states here, the problem with the data object is that it is too general. As a result, it cannot be applied directly to more precise cases, so that the deletion of GND redirects, such as here, here and here, is considered okay by the administrators, because both users die with themselves Kolja21 and Epìdosis speak out for such deletions. I, on the other hand, am against such deletions and would like to know what the community thinks here. --Gymnicus (talk) 09:07, 14 March 2022 (UTC)[reply]

Symbol note.svg Info More context: Wikidata:Administrators'_noticeboard#Please_make_a_decision --Emu (talk) 09:44, 14 March 2022 (UTC)[reply]
@Emu: To be honest, I see no reason for this link now. I asked the question quite neutrally here, so that this is more of an opportunity for voting. But if you consider this linking is necessary, then so be it. --Gymnicus (talk) 09:57, 14 March 2022 (UTC)[reply]
Gymnicus is blocked for "Removing content from pages". He wants to prove that he was treated unfair. We had a long discussion where I explained to him that there are cases in which the deleting of a wrong or outdated identifier (after correcting the given source like Commons, Wikipedia or Wikisource) makes sense. Otherwise we would need to check the wrong ID again and again.
--Kolja21 (talk) 13:25, 14 March 2022 (UTC)[reply]
The “long discussion” was about one or two comments where he explained to me that without the deletions the maintenance work would collapse. He does exactly the same thing here in the comment. Only point here is that the problem isn't coming from the GND redirects, but from the bot creating the maintenance pages. Because the KrBot2 cannot recognize ranks, which leads to incorrect messages on the maintenance pages. If this breaks the maintenance work, then you should change the bot's script so that it recognizes the ranks. Then there will be no more false reports. I would like to end my comment with a statement from MisterSynergy (source) about Tn's, which are also a thorn in Kolja21's side: “Eigentlich gehören sie nicht hier her, aber mit missbilligtem Rang stören sie formell nicht – allerdings verstehen das nicht notwendigerweise alle Datennutzer.” (english: “They don't really belong here, but with deprecated rank they don't formally lower - though not necessarily all data users understand that.”) --Gymnicus (talk) 18:22, 14 March 2022 (UTC)[reply]
Data users like VIAF and others. And again: It's not only a problem for VIAF and bots. We need to check the IDs and the source given. We need to fix the errors here and in Commons, Wikipedia and Wikisource. It's a multi-stage maintenance procedure you have no idea of since you never participated in maintenance work. All you do is trolling around. --Kolja21 (talk) 18:37, 14 March 2022 (UTC)[reply]
MisterSynergy also gave you a tip (source), which referred directly to Wikisource, on the subject of Wikimedia Commons, Wikipedia and Wikisource: “Es ist leider nicht einfach möglich das Wikidata-seitig zu evaluieren, es müsste in Wikisource passieren.” (english: “Unfortunately, it is not easy to evaluate this on the Wikidata side, it would have to be done in Wikisource.”) – The solution on the Wikipedia, Wikisource and perhaps also Wikimedia Commons side are GND matching categories, like the category Category:GND different on Wikidata (Q55746867) which is already included in the German-language Wikipedia. Such a category can recognize the ranks, which can be seen, for example, in the data objects Wikipedia (Q52) and New York City (Q60). Although both data objects have several statements about the identifier, the German-language articles for the two data objects are not listed in the category Kategorie:Wikipedia:GND in Wikipedia weicht von GND in Wikidata ab because the category only compares the GND identifiers with the best ranking. This means, for example, for the German-language article Josef Goldschmidt (Bankier), which is listed in the said category: If in the associated data object Josef Goldschmidt (Q89200255) the statement Josef Goldschmidt (Q89200255) GND ID (P227) 1174026251 is placed on the deprecated rank and the qualifier reason for deprecated rank (P2241) redirect (Q45403344) is added. Then the German-language article falls out of the category because then only the GND identifier 1066746923, which has the normal rank and is contained in the German-language Wikipedia article, is checked. Finally, it remains to be said: If you use the entire spectrum of maintenance options, then you do not need to delete GND redirects. --Gymnicus (talk) 08:42, 15 March 2022 (UTC)[reply]

Wiki Loves Folklore 2022 ends tomorrow[edit]

Wiki Loves Folklore Logo.svg

International photographic contest Wiki Loves Folklore 2022 ends on 15th March 2022 23:59:59 UTC. This is the last chance of the year to upload images about local folk culture, festival, cuisine, costume, folklore etc on Wikimedia Commons. Watch out our social media handles for regular updates and declaration of Winners.

(Facebook , Twitter , Instagram)

The writing competition Feminism and Folklore will run till 31st of March 2022 23:59:59 UTC. Write about your local folk tradition, women, folk festivals, folk dances, folk music, folk activities, folk games, folk cuisine, folk wear, folklore, and tradition, including ballads, folktales, fairy tales, legends, traditional song and dance, folk plays, games, seasonal events, calendar customs, folk arts, folk religion, mythology etc. on your local Wikipedia. Check if your local Wikipedia is participating

A special competition called Wiki Loves Falles is organised in Spain and the world during 15th March 2022 till 15th April 2022 to document local folk culture and Falles in Valencia, Spain. Learn more about it on Catalan Wikipedia project page.

We look forward for your immense co-operation.

Thanks Wiki Loves Folklore international Team MediaWiki message delivery (talk) 14:40, 14 March 2022 (UTC)[reply]

Wikidata weekly summary #511[edit]

Updating a URL formatter[edit]

I have just updated the URL formatter for Royal Museums Greenwich artwork ID (P9131) to one which now works.

Could somebody remind me how to get all usages on Wikidata and Commons to update? Jheald (talk) 17:36, 14 March 2022 (UTC)[reply]

@Jheald: Seems to be a PyWiki thing here from Mr. G: https://github.com/generalist/wikidata-misc but note 24 hour assertion at Property_talk:P1630#Formatter_URL_cached --Tagishsimon (talk) 18:36, 14 March 2022 (UTC)[reply]
Thanks @Tagishsimon:, that looks exactly the thing. Any idea if/when usages on Commons (eg through template c:Template:Artwork) will update as well ? Jheald (talk) 18:49, 14 March 2022 (UTC)[reply]
@Jheald: Sadly, no. Nothing obviously useful at https://commons.wikimedia.org/wiki/Commons:Tools --Tagishsimon (talk) 21:16, 14 March 2022 (UTC)[reply]
@Jheald, Tagishsimon: I just tested purging a Commons page using the ID (File:Jan Porcellis - Dutch Vessels in a Strong Breeze.jpg) and it didn't seem to pick up the new one, so I would uneducatedly-guess "after a day the URL formatter cache expires, and then they'll start updating when the Commons page cache is updated" - which is to say whenever the Commons page is edited or otherwise purged. I have no idea if the normal job queue would do this but I guess not. Andrew Gray (talk) 21:25, 14 March 2022 (UTC)[reply]
(ec) @Tagishsimon, Andrew Gray: As you say, let's not panic, but wait and see the effect of updating wikidata first. AFAIK, the {{Artwork}} template tends to be pretty responsive when it comes to ordinary content changes on Wikidata, so it's quite possible it may just all work. Otherwise User:Jarekt may have some ideas. Jheald (talk) 21:27, 14 March 2022 (UTC)[reply]
Jheald This update did require manual change in the code. Thanks for alerting me. --Jarekt (talk) 02:18, 15 March 2022 (UTC)[reply]

Edits from Microsoft's Open Data Team[edit]

Hello, I work with Microsoft's Open Data Team. Our goal is to maintain and improve data accuracy for Bing Maps. We import Wikidata and occasionally when tracking down issues with map data we find the problem is sourced from Wikidata. Currently we don't have a mechanism for addressing these issues at the source.

Our Team would like to establish a pipeline where maps issues we find that are sourced from Wikidata result in edits/updates to those relevant Wikidata features. To establish this pipeline the Open Data Team would like to express interest in joining the Wikidata community as editors. This would entail training up 5-10 people on Wikidata policy regarding editing and sourcing edits. The resources available in the Help section will be instrumental in this training. Our interests are in transparency and in data accuracy.

I wanted to reach out to the community before we start editing to raise awareness around our interest in performing organized edits to Wikidata. I want to create a discussion here to field any concerns or questions.  – The preceding unsigned comment was added by Open Data Team (talk • contribs) at 21:58‎, 14 March 2022 (UTC).

Sounds v.promising. Welcome to wikidata. There's a great deal wrong with WD geodata, so lots to do. tbh, for me, the best pipeline is you fixing issues that need fixing, with good references and appropriate use of statement rank (e.g. to deprecate erroneous but referenced data, or to prefer a more accurate statement). Let us know what help you need. --Tagishsimon (talk) 22:32, 14 March 2022 (UTC)[reply]
Definitely sounds great. Personally, I've been looking at trying to bridge the microsoft and wikidata knowledge graphs through the Bing entity ID (P9885) property. We currently maintain mappings from wikidata to the google knowledge graph (see Google Knowledge Graph ID (P2671)). Unfortunately the Bing APIs are too slow/expensive for us to maintain the mapping to Bing (iirc would cost me thousands of dollars). It'd be cool if you could provide some support there. But in general sounds like an exciting effort and I hope we can be supportive of it. Might be wise to read this page on paid editing and the terms of use on disclosure to make sure you don't run afoul of the rules. BrokenSegue (talk) 00:32, 15 March 2022 (UTC)[reply]
There's also Help:Usernames and accounts ... WD is quite lassaiz faire, but your username might fall foul of en.wikipedia's rules, which in a nutshell says "The username should represent one person; do not use your organisation's name". --Tagishsimon (talk) 04:11, 15 March 2022 (UTC)[reply]
@Tagishsimon: Wikidata's policies are quite explicitely written to allow organizations to have accounts. While the username wouldn't be allowed in Wikipedia it's fine for Wikidata.
That said, it would still be preferred that if you train 5-10 people to edit Wikidata that everyone of those creates their own account and note that the person is working on the Microsoft's Open Data Team on their userpage. ChristianKl❫ 20:03, 19 March 2022 (UTC)[reply]

Updates of maps in the Wikidata pages[edit]

In the Wikidata page of Häagen-Dazs (Q1143333), can you remove the obsolete map File:Häagen-DazsMap.png, because the company left the Russian market? The updated SVG map has already been put there. The obsolete PNG map is superfluous.

In the Wikidata page of Domino's Pizza (Q839466), can you remove the obsolete map File:Domino's pizza world map.PNG and replace it with the updated map File:Domino's world map.svg, because the company left the Russian market?

31.200.20.40 12:00, 15 March 2022 (UTC)[reply]

Everything has already been done in relation to data object Häagen-Dazs (Q1143333). It is not necessary to delete the map which you call “obsolete”, because here in Wikidata statements that are no longer up-to-date are also retained. The statement regarding the no longer valid map was also marked with the qualifier end time (P582) 2022. --Gymnicus (talk) 12:08, 15 March 2022 (UTC)[reply]
the Häagen Dazs map is wrong : it excludes Canada, and is dated 2012 !! see File:Häagen-Dazs_Map.svg Hsarrazin (talk) 12:56, 15 March 2022 (UTC)[reply]
I will ask the original uploader, who is active, to make the corrections and update the SVG map. Since the file name does not have a fixed date and is thus not static, it can be updated. 31.200.20.40 15:38, 15 March 2022 (UTC)[reply]
Regarding data object Domino's Pizza (Q839466), the updated card should be added with preferred rank. In addition, the no longer up-to-date card should be supplemented with the qualifier end time (P582) 2022. --Gymnicus (talk) 12:10, 15 March 2022 (UTC)[reply]
Can you do the same in the Wikidata page of Domino's Pizza (Q839466)? 31.200.20.40 12:16, 15 March 2022 (UTC)[reply]

How to merge M. L. J. Abercrombie (Q6712823) with Minnie Abercrombie (Q15994255) - both same person[edit]

I've tried using the Merge gadget to merge Q6712823 into Q15994255. They are both about the same person, just different aspects of her career. The final version should be Minnie Abercrombie (Q15994255) because there are a number of Wikipedia pages (different languages) with this name. I got an error message when I tried the merge: A conflict detected on enwiki: Q6712823 with enwiki:M. L. J. Abercrombie, Q15994255 with enwiki:Minnie Abercrombie

I tried both ticked and un-ticked answers to the statement: Always merge into the older entity (uncheck to merge into the "Merge with" entity)

How to merge the, please?--MerielGJones (talk) 12:50, 15 March 2022 (UTC)[reply]

OK, the merge has now been done by @Epìdosis:, so no problem now. Thanks. --MerielGJones (talk) 12:57, 15 March 2022 (UTC)[reply]

United World Wrestling ID[edit]

Hi there, I have a question regarding United World Wrestling ID (P2727). It appears that United World Wrestling (UWW) changed their website and the latest data is now located at a different location. For example, for Irina Rîngaci (Q106603858) the latest data (which includes 2022 data) is here and the old location of the data is here (does not include 2022 data). This URL is also used in the Wikidata property and that now points to what appears to be a database with stale data. I think UWW updated their website because this page now uses the new location and not the old location anymore. Is there a process for updating United World Wrestling ID (P2727) to use the URL which points to the new location, or is there anything else I should know if I were to make changes to that property? Thanks, Simeon (talk) 22:52, 15 March 2022 (UTC)[reply]

@Simeon: I updated the formatter URL (P1630) to point at the URL you listed above. BrokenSegue (talk) 22:58, 15 March 2022 (UTC)[reply]
Thanks! Should there perhaps also be corresponding changes to URL match pattern (P8966) and source website for the property (P1896)? In articles (on en.wiki at least) the external link now points to the new location so thanks for helping with that! Simeon (talk) 23:08, 15 March 2022 (UTC)[reply]
Yes, those should be updated in a similar manner. BrokenSegue (talk) 00:55, 16 March 2022 (UTC)[reply]
Ok, that makes sense. I have updated both accordingly with "preferred rank". Simeon (talk) 12:00, 16 March 2022 (UTC)[reply]

Leadership Development Working Group: Apply to join! (14 March to 10 April 2022)[edit]

You can find this message translated into additional languages on Meta-wiki.

Hello everyone,

Thank you to everyone who participated in the feedback period for the Leadership Development Working Group initiative. A summary of the feedback can be found on Meta-wiki. This feedback will be shared with the working group to inform their work. The application period to join the Working Group is now open and will close on April 10, 2022. Please review the information about the working group, share with community members who might be interested, and apply if you are interested.

Thank you,

From the Community Development team
--YKo (WMF) (talk) 05:36, 16 March 2022 (UTC)[reply]

Gatehouse Gazetteer covers more than just Wales[edit]

Gatehouse Gazetteer (Q59259501) refers to a gazetteer for castles etc in Wales, but Gatehouse Gazetteer place ID (P4141) more correctly indicates that it covers England, Wales, Isle of Man, Channel Islands etc, and includes the country name in the data entry. Should Gatehouse Gazetteer (Q59259501) be changed to indicate the broader scope, as there is not currently an English equivalent?

I have a dataset with the name/url mapping for all 5000 entries of Gatehouse, I could import it if given help, as I'm new to Wikidata. Vicarage (talk) 10:32, 16 March 2022 (UTC)[reply]

Renamed and added extra juristictions. Vicarage (talk) 09:15, 17 March 2022 (UTC)[reply]

Modelling Toys and Toy Lines[edit]

On my discussion page Trade pointed out that there are items conflating fictional characters and toy lines/brands/toys (esp. dolls) (link to Discussion: Dolls vs. fictional characters). We decided to split items into one item for the doll and one item for the fictional character. In the case of Barbie (Q167447) we now have Barbie (Q167447) for the brand and the newly created item Barbara Millicent Roberts (Q111242136) for the Barbie character but now there appear some other issues. I will take Barbie as an example, but I think these questions also concern other doll lines (like He-Man (Q550404)/Masters of the Universe (Q519710)).

  1. I think there still exists a conflation of concepts at Barbie (Q167447), namely between doll brand and Barbie doll type (model?). Do we need a third item for Barbie, having one item for Barbie as a brand, one item for Barbie as a doll model (besides Francie (Q5479798), Ken (Q737939), Skipper (Q1995127)) and one item for Barbie as a fictional character? Oh, and we also have Barbie (Q98148278) for the Media Franchise.
  2. How to link Barbara Millicent Roberts (Q111242136) and Barbie (Q167447) (as a doll model)?
  3. How to link individual Barbie doll models (e.g. Francie (Q5479798), Ken (Q737939), Skipper (Q1995127)) to the brand? Is brand (P1716) appropriate here? e.g. Francie (Q5479798) brand (P1716) Barbie (Q167447) (brand)
  4. How to link toy brand and toy line (e.g. Barbie (Q167447) and The Marvelous World of Shani (Q107675961)? Is brand (P1716) appropriate here? e.g. The Marvelous World of Shani (Q107675961) brand (P1716) Barbie (Q167447) (brand) (In this case I would remove the subclass of (P279) statement). Some sidenote: according to the English Wikipedia article en:The Marvelous World of Shani Shani dolls are only retroactively considered Barbie dolls. In this case - should The Marvelous World of Shani (Q107675961) be considered of the Barbie brand?
  5. How to link individual Barbie doll models to the toy line (e.g. Shani to The Marvelous World of Shani (Q107675961)). Should we use brand (P1716), too?

I'm not familiar with modelling of products, so thanks for every input. - Valentina.Anitnelav (talk) 10:58, 16 March 2022 (UTC)[reply]

Thanks for raising this!
For 1/ a third item seems reasonable
but that begs the question, do we need to also split Ken (Q737939) in two?
For 2/ how about Barbara Millicent Roberts (Q111242136) based on (P144) Barbie (Q167447) ?
For 5/, not sure about brand (P1716), how about part of the series (P179)?
Jean-Fred (talk) 14:07, 16 March 2022 (UTC)[reply]
"but that begs the question, do we need to also split Ken (Q737939) in two?" - Yes, in the current approach we also need to split Ken (Q737939) in two (one item for the puppet model and one item for the character)
I like the idea to use part of the series (P179) to link to lines like The Marvelous World of Shani (Q107675961). I still have to think about using based on (P144) for 2) but it might work. - Valentina.Anitnelav (talk) 09:29, 17 March 2022 (UTC)[reply]

Barbara Millicent Roberts (Q109225717) is a thing now, courtesy to @Arlo Barnes, Valentina.Anitnelav, Jean-Frédéric:. Barbie the Doll have official biography published but Mattel while her appereance in media vary from work to work so it makes sense to consider the character group to be a seperate entity. --Trade (talk) 22:31, 16 March 2022 (UTC)[reply]

I made the 'Millicent' entity in order to improve Tefillin Barbie (Q16205089) (although then I became unsure how best to do so due to issues similar to the ones raised here). Since it's a kitbash, it depicts a variant of the Barbie character, but can't properly be said to be part of the Barbie line or brand but is said by the artist to be based on "Halloween Hip Barbie 2006", which is (do we think individual releases like that should have dedicated items?). I'm not too familiar with this particular fashion doll line despite it being the most famous one, so I'll leave questions of proper ontology to those who do; but right now I'll note that the two Rogers entities need more work to distinguish them, as they come off somewhat as duplicates. Arlo Barnes (talk) 23:43, 16 March 2022 (UTC)[reply]

Do you think we should merge the two items? @Arlo Barnes:--Trade (talk) 01:13, 17 March 2022 (UTC)[reply]
That seems best to me; if a distinction becomes important later, a new item can always be created. Arlo Barnes (talk) 01:40, 17 March 2022 (UTC)[reply]

@Infovarius: --Trade (talk) 16:29, 17 March 2022 (UTC)[reply]

What do you think about this? subclass of (P279) Barbie Doll (Q97593385) may be a bit redundant here as it already follows from instance of (P31) doll or action figure model (Q111282474) and brand (P1716) Barbie (Q167447) (I think).
  • I split all the Barbie dolls I could find into an item for the character and one item for the doll model, linked using based on (P144) as proposed by Jean-Fred above (see Barbara Millicent Roberts (Q109225717) and Barbie (Q111282564) as an example). Now, Barbie doll items still raise a couple of constraint violations as they are using properties meant for (fictional) persons (e.g. gender, personal relationships). I'm thinking about just deleting all this information from the doll models after transferring it to the character items so Barbara Millicent Roberts (Q109225717) would have sex or gender (P21) female (Q6581072), but Barbie (Q111282564) (doll model) no gender information at all. But then the information would be missing that it is a doll presented with female characteristics and that it is also marketed as female (even though in the end people can imagine whatever gender or relationships they want when playing with these dolls). - Valentina.Anitnelav (talk) 11:15, 18 March 2022 (UTC)[reply]
Hm, maybe 'has quality'='gendered expression (Q15404978) 'of' 'female'? Arlo Barnes (talk) 06:00, 19 March 2022 (UTC)[reply]
I like 'has quality'='gendered expression (Q15404978) but I'm not sure about using 'of' as a qualifier here. Maybe somebody can think of a better one? - Valentina.Anitnelav (talk) 13:30, 19 March 2022 (UTC)[reply]

Another aspect of dolls is the moulding, with different individual doll models often sharing a mould. However, I'm uncertain where this info could be sourced from, and if it's actually useful to record in Wikidata. Arlo Barnes (talk) 06:00, 19 March 2022 (UTC)[reply]

How difficult it is to link to commons[edit]

János Piry Cirjék (Q1236709)

I have tried to link it to Commons (exactly the same name), I don't know what's wrong. It's bl... difficult to do that. --Io Herodotus (talk) 13:28, 16 March 2022 (UTC)[reply]

@Io Herodotus: Because you don't have to add “János Piry Cirjék” but “Category:János Piry Cirjék”. There is no gallery named “János Piry Cirjék” for him, but only a category named “Category:János Piry Cirjék”. --Gymnicus (talk) 13:47, 16 March 2022 (UTC)[reply]
If I add "category", the word category appears twice!
As I said, it's difficult Io Herodotus
(talk) 13:58, 16 March 2022 (UTC)[reply]

✓ Done thank you. --Io Herodotus (talk) 15:21, 16 March 2022 (UTC)[reply]

Fort Nelson, both a museum and a fort[edit]

Fort Nelson, Hampshire (Q5471742) is a military museum in Hampshire, the latest use of Fort Nelson, Hampshire (Q17650048). Is there really merit in having 2 entries, with mapping clashes when I try to add wikipedia and other external pages, or should the former be given instances of fort and museum, and the latter deleted?

What is the policy for re-use of old buildings under the original name? Vicarage (talk) 13:44, 16 March 2022 (UTC)[reply]

Having two distinct items for building and institution is better, especially when you start to add properties like inception date, founded by, etc. Ayack (talk) 15:30, 16 March 2022 (UTC)[reply]
Should the editor reject adding the same Wikipedia page to both articles then? Why does it insist on a one-to-one mapping when the Wikipedia page says "after a long career as a military building, its now a museum"
Forts are often built and rebuilt on the same site, so would most usefully have the inception of each phase in its life, whether it be fortification, prison, then museum. Indeed I see I can add inception as a qualifier for the museum and fort properties of Fort Nelson, Hampshire (Q5471742)Vicarage (talk) 16:37, 16 March 2022 (UTC)[reply]
Wikidata is more granular than Wikipedia. Combining building/structure and organization (museum) into one item is not a good idea. The changing use of the building over the course of time can be recorded using has use (P366) and relevant qualifiers.Jklamo (talk) 09:07, 18 March 2022 (UTC)[reply]
Thanks. I'll keep updating the 2 items to reflect this and explore the issues that develop. Vicarage (talk) 11:53, 18 March 2022 (UTC)[reply]

languages spoken, written or signed (P1412) is *not* an identifier[edit]

At the moment we have the following (incorrect) chain:

languages spoken, written or signed (P1412)
instance of (P31) = Wikidata property to indicate a language (Q18616084)
subclass of (P279) = Wikidata property for an identifier (Q19847637)

How best to fix this? P1412 should not be coming up in lists of identfiers. Jheald (talk) 15:05, 16 March 2022 (UTC)[reply]

I would remove the P279, there is only one identifier in the list. The rest are general properties. Sjoerd de Bruin (talk) 15:07, 16 March 2022 (UTC)[reply]
@Sjoerddebruin: Thanks! Jheald (talk) 17:03, 16 March 2022 (UTC)[reply]

Easily build useful websites with data from Wikidata and across the web[edit]

Wikidata has a ton of useful data about a wide variety of concepts. To really make that data shine you often want to present it in a way that is purpose-built for a domain or type of data, like a directory of video games or actors. We built a tool to make it easier to build such presentations, even for non-programmers, only using HTML and without any additional programming.

If you are intersted in learning how to build cool presentations of data from Wikidata and other sources of data on the web, please let us know when you are available by filling out this form.

Tarfahalrashed (talk) 19:51, 16 March 2022 (UTC)[reply]

Item to be deleted[edit]

Stanislaus Vasilevskis (Q111270184) has been created by mistake. The item already exists under (Q17593896). Sorry I don't know where to find the information to delete it. --Io Herodotus (talk) 04:56, 17 March 2022 (UTC)[reply]

@Io Herodotus: The easiest would be to merge both items. There is a HowTo an Help:Merge and a nice Tool in your Settings -> Gadgets. If there are any problems, do not hesitate to ask again. But since duplicates are quite common it's good, to be able to do it by yourself. --Newt713 (talk) 11:41, 17 March 2022 (UTC)[reply]
✓ Done Pas de problème. Déjà fait. --Kolja21 (talk) 13:48, 17 March 2022 (UTC)[reply]
I don't understand why we can't ask a "speedy deletion" like on wikipedia. --Io Herodotus (talk) 03:06, 18 March 2022 (UTC)[reply]
Our normal deletion process basically is the equivalent of enwiki's speedy. it's pretty light weight already. BrokenSegue (talk) 03:11, 18 March 2022 (UTC)[reply]

Overcoming language barriers for notice of changes to related projects expressed in Template:ExternalUse[edit]

The recent process of changing the identifier for C-SPAN person ID (P2190) from a string to a numeric ID which functionally in creating the URL is backwards compatible, but I've identified multiple users of templates for the property now added to Template:ExternalUse on P2190. The text for this template suggests notifying other projects (and in this case applicable affected templates), but there isn't documentation of how to overcome the language barrier to notify projects across multiple language Wikis and projects. As further integration of Wikidata grows this will be further compounded. Are there 1. existing mechanisms that could be added to notify all projects listed in the template:ExternalUse that would also enable translation or some standard templates to notify of a "discussion on the property" "deprecation of parameter" "merge of templates" or other events that warrants notification, discussion, and faciliates coordination? Wolfgang8741 (talk) 15:17, 17 March 2022 (UTC)[reply]

Oneway only for a train station[edit]

Hello, I wonder how to model the fact that Gulleråsen (Q11973210) collects passengers only in one way, not the other way. Any idea? Bouzinac💬✒️💛 08:21, 18 March 2022 (UTC)[reply]

Maybe about adjacent station (P197). If it only shows one adjacent station in one direction, then that shows you can only board in one direction. --Gymnicus (talk) 08:32, 18 March 2022 (UTC)[reply]
That's problematical, defining P197, wrongly, as being valid only if passengers can board at this station to alight at the adjacent station. In the situation in which passengers can only alight at this station, the adjacent station still exists as an adjacent station. I did, briefly, think about qualifiers for P197 statements, but again that seems wrong b/c the issue is with this station, not the adjacent station. --Tagishsimon (talk) 08:41, 18 March 2022 (UTC)[reply]
@Tagishsimon: That you can only get in or out is a different case. In the example of Bouzinac the point is that the traffic line only goes in one direction and not in both, at least that's how I understand it and that's how it is represented in the data object Gulleråsen (Q11973210) with the Qualifikator has quality (P1552) one-way traffic (Q786886). This can be represented using the property adjacent station (P197). --Gymnicus (talk) 09:47, 18 March 2022 (UTC)[reply]
Hmm. I wonder. Half tempted to agree, half not. We'd be using P197 on Station1 to point to Station2 b/c passengers can board at 1 and alight at 2. We'd omit a P197 from Station1 on Station2 b/c passengers cannot board at 2 and alight at 1. Station1 remains adjacent to Station2. The Station2 record now has no indicator on it of the adjacent station from which passengers can arrive. It would seem to be a 'where can I go to when boarding'-centric approach which disregards the 'from where might I have come when alighting'-centric approach. One station is adjacent from the perspective of boarding. The other station is adjacent from the perspective of alighting. --Tagishsimon (talk) 09:57, 18 March 2022 (UTC)[reply]

I asked the question because, according to that map and to OSM trains go both ways but only stop/pick passengers in the direction of Frogneseteren. Hence, this actual template would give the current result :

North / westbound Gulleråsen South / eastbound
Vettakollen
towards Frognerseteren
Oslo Metro 1.svg Oslo Metro Line 1 Gråkammen

and the general Oslo map would render as such Map of Oslo Metro (query)

Do you guys know of other subways which serve passengers only in one way ? --Bouzinac💬✒️💛 10:12, 18 March 2022 (UTC)[reply]

@Bouzinac: So directly I can't think of any other example in relation to subways. On the other hand, I know from my own experience that something like this definitely exists in tram and bus transport. In addition, I also came up with a kind of line management that provokes such cases. These are ring lines (circle route (Q145179)). It is usually the case that the clockwise line has a different name than the anti-clockwise line. Examples of this are the S41 and S42 in the Berlin S-Bahn network or line 63 or 61 of the Budapest tram. The Glasgow Subway is also a ring line. On the outer ring track, orange is used to drive clockwise, while on the inner ring track, gray is used to drive counter-clockwise. --Gymnicus (talk) 11:10, 18 March 2022 (UTC)[reply]
Circular lines are OK and as far as I know, their model looks OK, see for instance Map of Glasgow Subway (query). Besides, there are many specific/peculiar subways, as is the case for New York and Séoul, a nightmare to model. For that station X, train may go to Y or Z depending on the time/the day. A solution was to model specific services, such as in
North / westbound Porte des Postes South / eastbound
CHU - Centre Oscar-Lambret
towards CHU - Eurasanté
Symbole Lille 1.svg Lille Metro line 1 Wazemmes
towards Quatre Cantons - Grand Stade (métro de Lille Métropole)
Montebello (métro de Lille Métropole)
towards Saint-Philibert (métro de Lille Métropole)
Symbole Lille 2.svg Lille Metro line 2 Porte d'Arras (métro de Lille Métropole)
towards CH Dron (métro de Lille Métropole)
Montebello (métro de Lille Métropole)
towards Lomme - Lambersart
Symbole Lille 2.svg Q110395973 Porte d'Arras (métro de Lille Métropole)
towards Roubaix - Grand-Place (métro de Lille Métropole)
but still New York and Séoul's subway model are unsatisfiying, actually. Bouzinac💬✒️💛 11:42, 18 March 2022 (UTC)[reply]
@Bouzinac: Well, I knew from the start that the Glasgow Subway map would look good. There could have been an error in the template {{Adjacent stations}}. However, this is not the case because the outer and inner lanes were not implemented as different lines, despite their different color code, as can be seen, for example, at the stop Buchanan Street subway station (Q3269428). That's why we should rather look at the example of the S-Bahn Berlin (Berlin S-Bahn (Q99654)), because there you can't represent lines S41 and S42 as one line. That's why the template {{Adjacent stations}} gets certain difficulties as you can see at the example of the train station Berlin Westhafen station (Q465972):
North / westbound Berlin Westhafen station South / eastbound
Berlin Beusselstraße station
(terminus)
via Berlin-Gesundbrunnen station
Berlin S41.svg S41
terminus
Berlin S42.svg S42
terminus
Berlin-Wedding station
towards Berlin Beusselstraße station
via Berlin Südkreuz station
I don't know if that's the right representation. Because that's how it looks, at least to me, as if line S41 starts and ends in the station Buchanan Street subway station (Q3269428) just like line S42. But that would also be the same for all other stations on these lines. What I'm saying is that the template has a few weaknesses. --Gymnicus (talk) 12:59, 18 March 2022 (UTC)[reply]
Yes, that template is really fit and should be fit for only subway stations, not railways stations as they are really more complicated to model : eg other pb with services departing station X to Y or Z depending on the train mission that are typically rare in subways which mostly go always A to B to C without jumpings, as in most RER Paris lines and probably other suburbans trains. I've tried to correct data on Bahnhof Berlin Westhafen(Q465972). --Bouzinac💬✒️💛 14:21, 18 March 2022 (UTC)[reply]

What should be fixed in Lexeme:L4127?[edit]

The Lexical category of Lexeme:L4127 is Q1084. I expected it to be displayed as 'noun', like in Lexeme:L6191. However, in Lexeme:L4127, it is displayed as 'Verb', which is confusing. What should be fixed? Intolerable situation (talk) 12:55, 18 March 2022 (UTC)[reply]

@Intolerable situation: For me, the lexeme hit (L4127) is also a noun and is also displayed as such. --Gymnicus (talk) 13:01, 18 March 2022 (UTC)[reply]
@Gymnicus: Then why is its lexical category displayed as 'Verb' (yet links to Q1084) to me? Intolerable situation (talk) 13:19, 18 March 2022 (UTC)[reply]
@Gymnicus: Oh, it is now displayed as 'noun'. Sorry. Intolerable situation (talk) 13:20, 18 March 2022 (UTC)[reply]
@Intolerable situation: All good that happens. You might have had both hit (L4126) and hit (L4127) open and then looked at the wrong one and wondered. --Gymnicus (talk) 13:24, 18 March 2022 (UTC)[reply]

field of work (P101)[edit]

There is a significant structural issue with field of work (P101): it is intended to be an inverse/reciprocal property and yet it does not function as one. Its property constraint classes are fundamentally flawed, because the current list suggests an ultimately open set of people, places, and things. It is extremely useful to indicate the academic discipline(s) of a scholarly work. Grouping by disciplines allows bibliographic data in wikidata to be more easily compared to library purchasing activity, book jobbers/vendors, and classification systems such as LC.

However, the property field of work (P101) is confusingly flipped with Works in this Field, a (proposed?) inverse property which exists as a data item but not a property. Works in the Field should appear on Agent (e.g., instance of = human) items, and Field of Work should appear on the Patient (e.g., instance of = journal article) items.

There is also the genre (P136) property that needs to be related to academic discipline, so that the scholarly output of faculties of creative writing, fine arts and performing arts are also accessible through academic discipline.

Academic Discipline is a distinct and broader property than subject. It tends to correspond with academic departments, programs, and the foci of academic societies. Disciplines are likely to be found as descendants of knowledge (Q9081), science (Q336), or scholarly method (Q17079481).  – The preceding unsigned comment was added by Joeeasterly (talk • contribs) at 18:14, March 18, 2022 (UTC).

yeah works shouldn't have field of work (P101). A work doesn't do work so it doesn't have a field of work. Shold use main subject or something. BrokenSegue (talk) 17:49, 18 March 2022 (UTC)[reply]

Mathematical Notation in Aliasses or Labels[edit]

How is it possible in Wikidata to enter special characters to items. I tried to add new Items through using arXIV to QuickStatements and in these there are sometimes special characters. I usually try to add not yet such ones, when I do not trust the Label as proposed. Now I have not looked good enough before. An example is the item Spatially-resolved, substrate-induced rectification in C₆₀ bilayers on copper (Q111286372). There the 60 in C60 should look like C60. When I copy it it did not work. Is there a Wikitext editor extension for Wikidata items or is only plain text allowed. I have seen it in some items in alliases with a lower stepped number at other combinations.--Hogü-456 (talk) 19:44, 18 March 2022 (UTC)[reply]

I don't think any formatting is supported in labels and descriptions. This means you are restricted to what is allowed in plain Unicode, and there is a couple of explicit alphanumeric super- and subscript letters available. For instance you could type subscript 60 as U+2086 and U+2080 which will render as ₆₀. That said, I'd encourage not getting too creative in the label fields, there are some properties that allow Latex, such as defining formula (P2534) that is a better place for things that need a certain formatting, there's likely one for chemical formulas as well. Infrastruktur (talk) 00:06, 19 March 2022 (UTC)[reply]
Yes, approximate in plaintext as best you can in the label field (or if infeasible, put in something like [formula excised] in the title where the unacceptable bit is), duplicate that as a statement with title (P1476), and as a qualifier to that use title in LaTeX (P6835). I mocked it up for you (Hogü-456) in the example you gave, and you can also look at the property description for more examples (edit them without making changes / saving to see the LaTeX source). Arlo Barnes (talk) 06:10, 19 March 2022 (UTC)[reply]
Wikidata allows no formatting but does allow all of unicode. C₆₀ would be unicode way to express it. ChristianKl❫ 21:00, 19 March 2022 (UTC)[reply]

What is the opposite concept of alternative fuel vehicle (Q8449254)?[edit]

I am only able to find a wikidata entry for alternative fuel vehicle, but unable to find wikidata entry for a concept for internal combustion engine vehicles or fossil fuel vehicles or vehicles with conventional energy. Given they are much more dominant, wikidata entry on such vehicle should already exists but I am unable to locate such entry, only able to find entity for vehicles of individual types of fossil fuels. Anyone able to locate what is the entry for conventional fossil fuel powered internal combustion engine vehicles? C933103 (talk) 09:30, 19 March 2022 (UTC)[reply]

  • There are many areas in Wikidata were we have items because there are Wikipedia articles about the corresponding topic. Here it seems that while there's an article for "internal combustion engine" and the more specialized "Internal combustion locomotive" there's no article for "Internal combustion vehicle". In a case like this it makes sense to search a bit for an item but if you don't find an item, you can create a new item. I did it here with internal combustion vehicle (Q111294455) and then linked internal combustion locomotive (Q104830132) with it. ChristianKl❫ 14:40, 19 March 2022 (UTC)[reply]
  • Not everything has a well defined "opposite". ChristianKl made an item for internal combustion vehicle (Q111294455) but that's still not really the opposite of alternative fuel vehicle (Q8449254). BrokenSegue (talk) 17:16, 19 March 2022 (UTC)[reply]
  • You can model this as
    ⟨ internal combustion engine vehicle ⟩ disjoint union of (P2738) View with SQID ⟨ list values as qualifiers (Q23766486)  View with Reasonator View with SQID ⟩
    of (P642) View with SQID ⟨ conventional fuel vehicle ⟩
    of (P642) View with SQID ⟨ alternative fuel vehicle ⟩
    or something like that. Add values if there is other cases such as hybrid vehicles. This means « an internal combustion engine is either an conventional fuel one or an alternative fuel one. That way, you can add other values and don’t have to use the ill defined notion of « opposite ».

The question : If we have a parallel hierarchy of engine, like

⟨ internal combustion engine ⟩ disjoint union of (P2738) View with SQID ⟨ list values as qualifiers (Q23766486)  View with Reasonator View with SQID ⟩
of (P642) View with SQID ⟨ conventional fuel combustion engine ⟩
of (P642) View with SQID ⟨ alternative fuel combustion engine ⟩

maybe we don’t need to repeat it ? isn’t it a bit redundant ? author  TomT0m / talk page 17:43, 19 March 2022 (UTC)[reply]

    • I think such a statement should only added if you go through the subclasses of vehicle has no instance_of statements vehicle (Q42889) and find that the relationship really holds for all the items we have. Currently, I do think that there are rockets that don't have an internal combustion engine but that do use a patrolium based fuel and are thus no alternative fuel vehicles. There are also vehicles like bicyles that don't run on any fuel. ChristianKl❫ 19:54, 19 March 2022 (UTC)[reply]


  • Wait, are biofuel powered vehicles considered alternative fuel vehicles? The "alternative fuel vehicle (Q8449254): vehicle that runs on a fuel other than petroleum fuels" description is also rather ill defined, as I believe most people consider battery electric vehicles to be alternative fuel vehicle (Q8449254) even when they take they are charged with eccentricities 100& generated by fossil fuels?C933103 (talk) 21:27, 19 March 2022 (UTC)[reply]

Join the Community Resilience and Sustainability Conversation Hour with Maggie Dennis[edit]

You can find this message translated into additional languages on Meta-wiki.

The Community Resilience and Sustainability team at the Wikimedia Foundation is hosting a conversation hour led by its Vice President Maggie Dennis.

Topics within scope for this call include Movement Strategy, Board Governance, Trust and Safety, the Universal Code of Conduct, Community Development, and Human Rights. Come with your questions and feedback, and let's talk! You can also send us your questions in advance.

The meeting will be on 24 March 2022 at 15:00 UTC (check your local time).

You can read details on Meta-wiki.--YKo (WMF) (talk) 09:48, 19 March 2022 (UTC)[reply]

Electric appliance (Q20076681)[edit]

Electric appliance (Q20076681) currently gets used as superclass for washing machine (Q124441). It's unclear to me how it differs from major appliance (Q12269769) and Electric appliance (Q20076681). Can someone who knows either Russian or Ukranian (where the item currently has labels) add an English label? ChristianKl❫ 20:06, 19 March 2022 (UTC)[reply]

I tried electric appliance, though I am not 100% sure this is a good translation. Ymblanter (talk) 20:13, 19 March 2022 (UTC)[reply]
@Ymblanter: What's the difference with electrical appliance (Q2425052)?ChristianKl❫ 23:06, 19 March 2022 (UTC)[reply]

Cause of death on a death certificate usually lists multiple morbitities[edit]

See: Sophia Weber (Q63973123) and File:Sophia Weber (1815-1891) death certificate.pdf where a death certificate lists two major causes and a contributing cause. Modern certificates have the same layout. I can switch dementia to "medical condition", and other ideas to resolve the error messages. --RAN (talk) 21:30, 19 March 2022 (UTC)[reply]

  • The suggestion to remove the single value constraint was made multiple times on the talk page without anyone arguing for keeping it. I just removed it. ChristianKl❫ 23:09, 19 March 2022 (UTC)[reply]

Manfredi[edit]

The item Manfredi (Q52746351) refers to 3 brothers.

The brothers Eustachio (1674-1739), Gabriele (1681-1761) and Eraclito (1682-1759) Manfredi were professors at the University of Bologna, of astronomy, mathematics and medicine-cum-geometry. Eustachio was the author of the famous Istituzioni astronomiche, published as the second volume of his works. The reference is "http://www.minorplanetcenter.net/db_search/show_object?object_id=13225"

Question: Should we have 3 items ?

If there is only one item, it is impossible to complete some datas, like birth, death etc.

--Io Herodotus (talk) 02:48, 20 March 2022 (UTC)[reply]

Simple editor for Linux/python/command line ecosystem[edit]

I want to make a series of simple edits from the Linux command line, but all the suggested tools lead me down rabbitholes of npm, docker or mass copies of data between systems. Is there a tool with the simple syntax

wikidata Q5470717 P3134 "2225973"

Which would add a statement without caveats, as I might do in the web page. I use python, but would much rather have a command line tool, than have to code up a function call. Obviously I'd have to log in and get some token stored. Vicarage (talk) 09:28, 20 March 2022 (UTC)[reply]

@Vicarage: Wikibase-cli is rather good. --Tagishsimon (talk) 12:58, 20 March 2022 (UTC)[reply]

Why was my data deleted?[edit]

Why was my data deleted?

Presuming any items you created (not "my data") have been deleted, that would likely be because they did not meet WD:N or else lacked statements and/or references which would have allowed WD:N to be evaluated - an issue we see with the item you created, Q111305489. --Tagishsimon (talk) 12:55, 20 March 2022 (UTC)[reply]