Wikidata

Wikidata:Contact the development team/Archive/2020/05

< Wikidata:Contact the development team‎ | Archive‎ | 2020

Some trouble with Q59188718

Hi. I can’t add data already within a day. Never faced this, error indication appears: 

A page "https://ru.wikipedia.org/wiki/%D0%9F%D0%BE%D1%81%D0%BB%D0%B0%D0%BD%D0%BD%D0%B8%D0%BA%D0%B8_%D0%B2%D0%B5%D1%87%D0%BD%D0%BE%D1%81%D1%82%D0%B8" could not be found on "ruwiki".

- Gerarus (talk) 17:48, 4 May 2020 (UTC)

  • The problem has already been resolved by another participant. Thanks him!
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Gerarus (talk) 18:27, 4 May 2020 (UTC)

Disparition of nsk in the Monolongual text

Hi, I asked for adding Naskapi (Q1704302) in the Monolingual text[1] and it was added this week [2] but now it's disapered I and can not add it to Rivière Châteauguay (Q20055120). :( Do you know why it's disapered? --Fralambert (talk) 16:14, 3 May 2020 (UTC)

@Fralambert: this is probably because the MediaWiki+Wikibase software version deployed to Wikidata was rolled back due to unrelated issues. The language code should reappear soon (possibly today, almost certainly before the end of the week). --Lucas Werkmeister (WMDE) (talk) 09:45, 4 May 2020 (UTC)
@Lucas Werkmeister (WMDE): It works again [3]. \o/ --Fralambert (talk) 23:41, 4 May 2020 (UTC)
Hehe, just barely in time for “possibly today” by the looks of that timestamp :) --Lucas Werkmeister (WMDE) (talk) 09:19, 5 May 2020 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Lucas Werkmeister (WMDE) (talk) 09:19, 5 May 2020 (UTC)

PetScan problem: 504 Gateway Time-out

Tracked in Phabricator
Task T251567

The tool PetScan (http://petscan.wmflabs.org/), which is very useful for creating new wikidata objects for unconnected items or adding statements to existing objects, returns a 504 Gateway Time-out since 8th of April. It has been working again inbetween severall times, but failed again every time after a short period. Also see

Is it possible to check/restart, ... this tool? Thanks a lot! --M2k~dewiki (talk) 10:33, 30 April 2020 (UTC)

The related ticket: phab:T251567. --M2k~dewiki (talk) 20:09, 30 April 2020 (UTC)
Is it still happening? It seems that Magnus proceeded to a big rewrite of Petscan, but the new version should work now. Lea Lacroix (WMDE) (talk) 09:37, 4 May 2020 (UTC)

Importing dataset to political election results

Hi,

I am trying to import a dataset to the 2019 Austrian Legislative Election. I was wondering if you could provide me with some information on how to import a dataset correctly to a Wikidata page.

Thanks, Miklos

Hello @Borisz96:, I believe this documentation page could help you: Wikidata:Data Import Guide. If you have more questions, feel free to ask. Lea Lacroix (WMDE) (talk) 10:11, 4 May 2020 (UTC)
@Borisz96: You can also consult Wikidata:WikiProject elections for how to organize data for elections and ask any election related questions at the WikiProject's talk page. --Dipsacus fullonum (talk) 13:03, 4 May 2020 (UTC)

Abnormal counting in edit history

Tracked in Phabricator
Task T41189

The edit history (and my watchlist) says that the IP removed 21 bytes even though it is not true and the description was expanded. Is it okay? Bencemac (talk) 17:19, 7 May 2020 (UTC)

This is most likely due to invisible changes in the internal serialization of the page, see Help:FAQ § Editing, number 13. --Lucas Werkmeister (WMDE) (talk) 09:48, 11 May 2020 (UTC)
Thanks, then it can be archived. Bencemac (talk) 08:27, 2 June 2020 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Bencemac (talk) 08:27, 2 June 2020 (UTC)

Follow-up on Wikidata:Project_chat#Major_issue

The above has a bug listed, but that bug is closed as "resolved". The thread still has open questions (ideally addressed by devs, I think). Some of the remaining things may be:

  • identify duplicates
  • merge duplicates
  • restore lost sitelinks on query server of already merge duplicates

Maybe some others. Is there bug where we can read about the follow up? --- Jura 07:03, 17 April 2020 (UTC)

For now, there is this ticket. What exactly could be provided by the development team to help the community identify and merge duplicates? Lea Lacroix (WMDE) (talk) 14:06, 17 April 2020 (UTC)
The development team could merge them directly .. --- Jura 17:18, 20 April 2020 (UTC)
The development team is not going to merge the duplicates, as this is content matter and the community should have the final word on it. However, we should be able to provide a list of items that are very likely duplicates, so people can check them and merge if needed. I'm not sure yet how much time we will need to generate such a list. I'll keep you posted. Lea Lacroix (WMDE) (talk) 16:15, 21 April 2020 (UTC)
Hello @Jura1: I shared the list you asked for here. I hope this helps. Lea Lacroix (WMDE) (talk) 12:38, 12 May 2020 (UTC)
I was actually looking for the thing to be resolved, but it seems that it was done since (@Peter James:). Thanks to all of you. The list seems to highlight other periods of similar incidents. --- Jura 13:24, 12 May 2020 (UTC)

Infobox parameter / wikidata property mapping

Hi, after a discussion on the project chat in french I’ve got a question. In this discussion someone asks if we have tools for importing datas of an existing wikidata page on its (maybe new) wikidata item. We’ve got stuffs like "harvest template", who uses a mapping of template parameters to import datas on wikidata items from the templates on their page but the user has to enter himself which Wikidata property corresponds to which parameter, as far as I understand. This is ok for batch import but it’s fastidious if it’s just a one time thing, such as creating an item thanks to the "duplicity" tool, which creates items for pages which lacks one in a wiki.

We also have tools like « craddle », who can create forms for a type of items but it ignores the template parameters.

So I wondered how we could get the better of both world, and this implies to store which property corresponds to which template parameter. Two (good imho) options comes to my mind: store the wikidata property in Templatedatas, which documents the usage of templates in a structured way and is used by the Visual editor to suggest paremeters and so for users when they edits an article, which could be cool and not to hard, so that external tools could reuse the json templatedata mappings for tasks such as importing datas from an article which use this template into Wikidata guessing the properties.

But it occured to me that one thing you develop currently could use exactly the same informations : the Wikidata bridge … so I ask here : will, and if yes how does the bridge will store and use such mappings ? templatedatas ? If not, will the mappings will be editable by community and usable by external tool ? Could the bridge allow to import informations from Wikipedia in an « harvestemplate »-like way ? author  TomT0m / talk page 18:25, 8 May 2020 (UTC)

Hello @TomT0m:, thanks for your message. Storing the mapping between infobox fields and Wikidata properties sounds interesting. I don't have a strong opinion about this, as the Wikidata team is not in charge of Templatedata.
However, I can answer about the Bridge. For now, the Bridge extension is not connected to the Visual Editor, so it doesn't store any information in Templatedata. The extension doesn't store any data at all: the mapping field<>property will be made in the Lua modules and the code of the infoboxes on Wikipedias. So it will be entirely configurable by the communities.
The main goal of the Bridge is not to import data from Wikipedia in Wikidata, but to edit existing values that are stored in Wikidata from Wikipedia. Especially in the first versions of the extension, it will not be possible to add new values, only to update existing ones. So I'm not sure that the Bridge is the best tool to do imports from Wikipedia.
I hope this answers your questions! Lea Lacroix (WMDE) (talk) 11:33, 14 May 2020 (UTC)
I understand, but I can’t help to think that defining the mapping in the module, but also in the documentation, and maybe in external tools (or a property on Wikidata, there is a proposal for this) is a duplication of information and is inefficient. The risk is that the information is never really up to date outside of the infobox for example, or never extracted from there, which make it more difficult to exploit for everyone, even if de facto present. I understand this is not a goal of the bridge, but could you consider ways to be able to share this informations from the modules to the external world ? author  TomT0m / talk page 12:06, 14 May 2020 (UTC)
From discussing around it seems that it’s possible to generate the templatedata from a template : (for example in commons : https://commons.wikimedia.org/wiki/Template:TemplateBox ) so the mappings could be generated from the datas of the lua module, which is good news. author  TomT0m / talk page 17:21, 15 May 2020 (UTC)

dispatch lag

Tracked in Phabricator
Task T252952

here suggested there're some issue on dispatch lag.--GZWDer (talk) 11:07, 16 May 2020 (UTC)

Can we prevent bots from creating new items when a certain amount of maxlag is reached?

For Wikidata it's more important that issues in existing items can be fixed then that new items get created. Jura opened [[4]] on the project chat about it. Currently, it seems that the throttling doesn't distinguish between normal edits and new item creation and it likely should. ChristianKl ❪✉❫ 08:22, 21 May 2020 (UTC)

Thanks for your suggestion! We're going to look at it and see if we can include it as part of the maxlag improvements. Lea Lacroix (WMDE) (talk) 15:46, 25 May 2020 (UTC)

Moved without leaving a redirect at Wikipedia, sitelink remained on Wikidata (26 May)

Can you check why this is still happening? See Wikidata:Requests_for_deletions#Q69802076 for a sample. --- Jura 12:38, 26 May 2020 (UTC)

Some CSS for Vector has been simplified

Hello!

I'd like to make a double-check about a change that was announced in Tech/News/2020/21.

Over-qualified CSS selectors have been changed. div#p-personal, div#p-navigation, div#p-interaction, div#p-tb, div#p-lang, div#p-namespaces or div#p-variants are now all removed of the div qualifier, as in for example it is #p-personal, #p-navigation …. This is so the skins can use HTML5 elements. If your gadgets or user styles used them you will have to update them. This only impacts the Vector skin.

On this wiki, this impacted or still impacts the following pages:

How to proceed now? Just visit all these pages and remove div before these CSS selectors if it hasn't been removed so far.

Thank you! SGrabarczuk (WMF) (talk) 12:34, 25 May 2020 (UTC)

Pinging Ch1902, though he hasn’t been active here since 2013, so it probably doesn’t matter very much. --Lucas Werkmeister (WMDE) (talk) 15:11, 25 May 2020 (UTC)
Changed :-) /Ch1902 (talk) 12:30, 27 May 2020 (UTC)

SPARQL/Mwapi/entity use (May 28)

Tracked in Phabricator
Task T254334

Please see Wikidata:Request_a_query#Mwapi_usage for the initial question/attempt to solve.

The idea is to be able to count (mainspace) pages that use a given entity in a SPARQL query by using the mwapi, similar to what w:Special:EntityUsage/Q42.

@Dipsacus fullonum: identified the relevant api call, but it's not entirely clear why it fails (phab:T196962#6153291).

Supposedly, it's less a problem with query server/sparql than the api. Accordingly, I raise this here than on the subpage.

How could this be done? --- Jura 04:35, 28 May 2020 (UTC)

I wonder if I should open a new case on phabricator for the API RuntimeException. I speculate that it is related to phab:T196962 but I don't know for sure, and nobody answered my question about it at T196962.
But Jura's request can also be met if you open the Mediawiki API Query Service to include API list calls (action=query and list= ). There are many different API list calls, and several of them could probably be interesting to users of WDQS. I suppose that can be done with a small addition to https://github.com/wikimedia/wikidata-query-deploy/blob/master/mwservices.json. --Dipsacus fullonum (talk) 07:49, 28 May 2020 (UTC)

Conversion to external-id (May 16)

Tracked in Phabricator
Task T253722

Here six IDs are considered good for conversion, no objection in the last days. Could you have a look? Thanks, --Epìdosis 21:05, 16 May 2020 (UTC)

Hi! The IDs mentioned on this page seem to have been added a while ago. How can we make sure that the decision got community support? I wouldn't want to ask my colleagues to convert them, and then get complaints because it was not discussed among the community.

@Epìdosis: Could you give me a list of exactly what IDs are ready to be converted, and from what format to which? Ideally on a Phabricator task, but it could also be here. It would help me a lot to have a clear vision of what is ready to be done. Thanks! Lea Lacroix (WMDE) (talk) 07:07, 19 May 2020 (UTC)

@Lea Lacroix (WMDE): The following, from string to external-id:
If you desire, I can open a thread in the talk of each property. Thank you very much, --Epìdosis 07:19, 19 May 2020 (UTC)
Thanks! Yes, I think it would be good. Maybe something like "we're about to convert the property, if you disagree feel free to leave a message". And then in one week, if no one complained, we move forward? Lea Lacroix (WMDE) (talk) 07:27, 19 May 2020 (UTC)
@Lea Lacroix (WMDE):, OK, threads opened. Let's wait a week :) --Epìdosis 07:54, 19 May 2020 (UTC)
@Epìdosis: Any relevant discussion or counter-argument happened? If not, I'll move forward with the ticket. Lea Lacroix (WMDE) (talk) 12:54, 26 May 2020 (UTC)
@Lea Lacroix (WMDE): No objection. You can move not only the four above, but also Dewey Decimal Classification (P1036), Library of Congress Classification (P1149) and Universal Decimal Classification (P1190), since consensus emerged for this solution in Wikidata:Property proposal/Library classifications' IDs for topics. Write me here if there is any problem. Bye, --Epìdosis 13:02, 26 May 2020 (UTC)
Perfect, thanks a lot for checking! I created the related ticket and will make sure that we integrate it in our next development sprints. Lea Lacroix (WMDE) (talk) 07:39, 27 May 2020 (UTC)
Conversion for these properties is now done. Lea Lacroix (WMDE) (talk) 10:38, 8 June 2020 (UTC)

Posted here 16 May 2020, started in Phabricator 27 May 2020, marked resolved in Phabricator 6 June 2020, reported as done here 8 June 2020. MrProperLawAndOrder (talk) 16:39, 9 June 2020 (UTC)

This section was archived on a request by: --- Jura 08:45, 28 June 2020 (UTC)

Query server result view: flipped table (26 May)

 

How can I activate the above view explicitly? It is supposed to be active when the results are lengthy compared to the screen, but it doesn't always happen.

Sample query: [5]

I had left a note about it at Wikidata:Request_a_query#Result_view_table_(flipped). --- Jura 13:11, 26 May 2020 (UTC)

Hello,
Unfortunately, this view is not something that can be explicitly configured in the Query Service. It is part of the library used for the mobile display of the query results, and it's not related to the size of the results, only the size of the screen (562px or less).
We could imagine adding it as a type of view, like the graphs, maps, etc. but it would require a certain amount of work, because it is not configured as such at the moment. Lea Lacroix (WMDE) (talk) 10:03, 27 May 2020 (UTC)
Actually, setting it to 562px could work, but I don't see this happen consistently nor does it only happen with that size. How could I make sure it happens?
The idea is to display a record (several flipped columns) and a link to quickstatement to merge or add a statement, similar to the links in the rightmost column at Wikidata:Database reports/identical birth and death dates/1.
An alternative could be to allow to define a (short) link text for URI (I think there was a request for that), but there may be other reasons why we don't want to allow that. --- Jura 04:45, 28 May 2020 (UTC)
  • A simple workaround could be to use "imagegrid" with some random image [6]. Too bad QuickStatements currently doesn't work for such links.
    To insert this in your list of possible developments, do you need more information? --- Jura 09:01, 5 June 2020 (UTC)
This section was archived on a request by: --- Jura 08:45, 28 June 2020 (UTC)

dispatch lag (May 27)

Tracked in Phabricator
Task T253746

Currently have some issue.--GZWDer (talk) 10:09, 27 May 2020 (UTC)

This has gotten worse the last week, with only a short relief today morning. maxlag<5 for less than 30% of the time. Can someone explain? --SCIdude (talk) 16:05, 7 June 2020 (UTC)
Today maxlag<5 for even less than 20% of the time. --SCIdude (talk) 14:32, 15 June 2020 (UTC)
This section was archived on a request by: --- Jura 08:46, 28 June 2020 (UTC)
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Contact_the_development_team/Archive/2020/05&oldid=1220888268"