Shortcut: WD:DEV

Wikidata:Contact the development team

From Wikidata
Jump to navigation Jump to search

Contact the development team

Wikidata development is ongoing. You can leave notes for the development team here or report bugs on Phabricator. (See the list of open bugs on Phabricator.)

If you have questions or bug reports related to the Wikidata Query Service or search on Wikidata, please add them to this page. If you have suggestions or requests regarding the entity suggester ranking, please see this page.

On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2020/05.

Project
chat

Lexicographical
data

Administrators'
noticeboard

Development
team

Translators'
noticeboard

Request
a query

Requests
for deletions

Requests
for comment

Bot
requests

Requests
for permissions

Property
proposal

Properties
for deletion

Partnerships
and imports

Interwiki
conflicts

Bureaucrats'
noticeboard

Requests
for checkuser

Development plan Usability and usefulness Status updates Development input Contact the development team


Follow-up on Wikidata:Project_chat#Major_issue[edit]

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)

Abnormal counting in edit history[edit]

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)

Infobox parameter / wikidata property mapping[edit]

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[edit]

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

Conversion to external-id (May 16)[edit]

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)

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

For Wikidata it's more important that issues in existing items can be fixed then that new items get created. Jura opened [[1]] 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)

Some CSS for Vector has been simplified[edit]

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)

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

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


Query server result view: flipped table (26 May)[edit]

WDQS - Table Result View - flipped.png

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: [2]

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