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, on #wikidata connect and on the mailing list or report bugs on Phabricator. (See the list of open bugs on Phabricator.)

Regarding the accounts of the Wikidata development team, we have decided on the following rules:

  • Wikidata developers can have clearly marked staff accounts (in the form "Fullname (WMDE)"), and these can receive admin and bureaucrat rights.
  • These staff accounts should be used only for development, testing, spam-fighting, and emergencies.
  • The private accounts of staff members do not get admin and bureaucrat rights by default. If staff members desire admin and bureaucrat rights for their private accounts, those should be gained going through the processes developed by the community.
  • Every staff member is free to use their private account just as everyone else, obviously. Especially if they want to work on content in Wikidata, this is the account they should be using, not their staff account.
Symbol future class.svg
Because of the holidays, this page will not be monitored as carefully as usual between December 19th and January 6th. All new unanswered messages will be addressed in January.
Thanks for your patience!
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 2019/12.

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

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


Search doesn't include subtitle field?[edit]

Some titles exceed the title limit (of 250 characters,) but the property subtitle appears to not be limited as such. When splitting too-long titles into title and subtitle, one can convey all the essential info. It would, however, be helpful if searches looked at the subtitle field to find those results. Can you enable this? Trilotat (talk) 21:33, 22 November 2019 (UTC)

Do you have examples? Lea Lacroix (WMDE) (talk) 08:22, 28 November 2019 (UTC)
I think it's any subtitle. --- Jura 20:17, 28 November 2019 (UTC)
Here is the item that got me thinking about this, review of Egypt and Africa. Joyce Tyldesley. Chronicle of the Queens of Egypt from Early Dynastic Times to the Death of Cleopatra (Q58890343). Please search for any phrase in the subtitle to see what I'm describing. Thanks. Trilotat (talk) 15:21, 3 December 2019 (UTC)
Thanks for the example. Indeed, search is not browsing the subtitle and haswbstatement:"P1680=..." doesn't work well in that case.
@DCausse (WMF): Can you maybe give us some insight about what kind of content Special:Search takes in account and how difficult/relevant it would be to include the value of subtitle (P1680)? Lea Lacroix (WMDE) (talk) 16:57, 3 December 2019 (UTC)
The search keyword haswbstatement has been designed to search for codes or IDs (short strings) if we enabled it for P1680 you would have to search for haswbstatement:"P1680=the full subtitle text" which might not be very usable on text. On the other hand the engine will index all "textual" properties meaning that your search query will also search for P1680 without telling it to do so, ranking might not be perfect but if your search query is precise enough you might find it near the top, e.g. 978-0-500-05145-0. Unfortunately you don't have the possibility to filter only on this particular property. DCausse (WMF) (talk) 16:16, 5 December 2019 (UTC)
So, it appears maybe it does search the Subtitle field. Forgive me, but I didn't understand the technical parts of DCausse's reply, but I did another targeted search and found exactly what I was looking for. Strange. Sorry for the distraction. Trilotat (talk) 16:57, 5 December 2019 (UTC)
I don't think the above is/was a great sample. Part of the string was also in the labels, so it wasn't visible that it isn't indexed.
Maybe Special:Search/Snowhite A Christmas Story that doesn't find Q58183681 illustrates it better (at least as of this version of the item. --- Jura 18:47, 5 December 2019 (UTC)
Thanks for the example, indeed something stopped working properly recently and is causing all the textual properties to disappear from the search index (not only subtitle). My first example stopped to work as well and no longer finds review of Egypt and Africa. Joyce Tyldesley. Chronicle of the Queens of Egypt from Early Dynastic Times to the Death of Cleopatra (Q58890343). I filed a task to fix this issue. DCausse (WMF) (talk) 11:43, 10 December 2019 (UTC)
Sorry please scratch my comment above, for some reason I thought that we already indexed all textual properties (work done in phab:T163642) and as pointed out I was confused by my misleading example, I'll re-purpose the task attached to this question to see how we could add this data to the search index. Sorry for the confusion. DCausse (WMF) (talk) 12:33, 10 December 2019 (UTC)

Page for thumbnail[edit]

On Q75803176#P996, when displaying the thumbnail for scanned file on Wikimedia Commons (P996), would it be possible to display the page indicated by the qualifier file page (P7668) instead of the first page? (compare sample above). Ideally, any P7668 on a Commons property displaying images would do that. The default first page isn't necessarily the ideal one. --- Jura 06:22, 4 December 2019 (UTC)

Hello,
After discussing about it with Lydia, our assumption is that this doesn't happen often enough to be worth a specific development for now, as we have plenty of other priorities. If more people disagree and want to support thi, feel free to do it here. Maybe this could be done through a user script. Lea Lacroix (WMDE) (talk) 12:05, 9 December 2019 (UTC)
SELECT *
{
    ?item p:P996 ?st .
    ?st ps:P996 ?scan .
    ?st pq:P304 ?pqvalue .
    FILTER( contains(str(?scan), "djvu") ) 
}

Try it!

Hi Léa.

Thanks for your feedback. Sounds reasonable. People interested might be regular Wikisource+Wikidata contributors: .. @Hsarrazin:

I don't know if this is complicated to put in place or not (a few lines of code or a new module). Maybe you could add it at the right place in the phab-pipeline, so it could be done when (e.g. 2021) some tweaks in these fields are done (image thumbnail display or Wikisource support at Wikidata).

Some 120 pages current statements could use. I think they are mostly by Vieux_têtard (talk ? contribs ? logs). Some with title page number (P4714) sometimes used by myself/Jarekt (talk ? contribs ? logs) could use a similar feature.

Obviously, if we add scanned file on Wikimedia Commons (P996) statements in a more systematic way, this could go into the thousands/ten thousands. Currently, these statements are only marginally useful as the pdf/djvu-page can't easily be identified/clicked. --- Jura 12:30, 9 December 2019 (UTC)

on frwikisource, we systematically record the number for the thumbnail, but there is no easy way to transfer it on wikidata, since the info comes from the Index page, and the link on wikidata is to the Main page of a book.
but, since it is now possible to export data from Commons files, using the built-in QS script in "Book" template[1], more and more of those will be added to wikidata :)

broken Lua's mw.wikibase.entity:getSitelink function[edit]

Any changes today, that might have broken Lua's mw.wikibase.entity:getSitelink function? Today c:Category:Pages with script errors started to fill up with files showing "Lua error in Module:Wikidata_label at line 24: attempt to call method 'getSitelink' (a nil value)" error. I do not think that error was caused by any changes to Lua code on Commons. So perhaps something went broke in mw:Extension:Wikibase Client/Lua. --Jarekt (talk) 04:53, 12 December 2019 (UTC)

Hello @Jarekt:, thanks a lot for reporting! I created a ticket for this issue. Lea Lacroix (WMDE) (talk) 12:05, 12 December 2019 (UTC)

Moved articles no longer auto-updating in WD[edit]

just in case no one has seen it and would like to inform the community of what is currently occurring.  — billinghurst sDrewth 00:46, 16 December 2019 (UTC)

Thanks for letting us know. We'll follow the progress on the ticket, it seems to be monitored by WMF's teams. If the issue happens again, please let me know. Lea Lacroix (WMDE) (talk) 08:17, 17 December 2019 (UTC)

Wikidata:Development plan[edit]

Is it the time to update this page for 2020?--GZWDer (talk) 18:37, 17 December 2019 (UTC)

We're on it, the new roadmap will be published sometime in January. Lea Lacroix (WMDE) (talk) 16:25, 18 December 2019 (UTC)

Wikidata:Database reports/Constraint violations/P225[edit]

Creating a diff like this gives Fataler Ausnahmefehler des Typs ?WMFTimeoutException“ for some month now. Looks like all works fine switching to EN as my UI language as I detected today. --Succu (talk) 21:04, 18 December 2019 (UTC)

P642 label/language problem[edit]

I'm an EN language user. http://www.palabrario.com/wiki/Property:P642 has the En label "of". However when rendered through the P template - de (P642) - or viewed when used as a statement qualifier in, for example, http://www.palabrario.com/wiki/Q56661670#P31 ... it renders as "de". It should render as "of". So that's probably not a good thing. --Tagishsimon (talk) 00:02, 26 December 2019 (UTC)