Wikidata

Wikidata:Contact the development team/Archive/2018/07

< Wikidata:Contact the development team‎ | Archive‎ | 2018
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

Future of query server

Just wondering, what's the plan for the future of query server? When I looked at the bug tracking system of the software that is being used some time ago, I had the impression that it stopped being maintained. Besides, it appears that the company was acquired by Amazon some time back, possibly when development stopped. Is there a plan to replace the software or at least start evaluating alternatives?
--- Jura 08:24, 29 June 2018 (UTC)

So far I am not worried but investigating. The software we have works and isn't going away over night. I am in the process of talking to people about alternatives and reaching out to Amazon though to get a better sense of where Blazegraph is going and if we need to make a switch. Back when we decided for Blazegraph we also looked at several alternatives and we can still use a lot of that research. --Lydia Pintscher (WMDE) (talk) 10:14, 29 June 2018 (UTC)
If the bug tracking system consists mainly of customers unanswered calls for help, I find it hard to be convinced by anything contrary corporate communications may say.
Currently, the server works fine and I think WMDE/WMF are doing a great job keeping it running. I think its functioning has become a key factor in Wikidata as a whole. One needs to make sure that this still works a year from now.
Compared to other endpoints, I think the GUI is most helpful, but I suppose this is unrelated to the underlying server software.
Growth of Wikidata continues and even if we don't want to change it now, one needs to bear in mind the time it takes to switch. Given other priorities of Wikidata/WMF and its usual pace, I suppose even if we started to switch to something else today, this could easily take 6 months. Selection of an alternative and preparing for this might easily take another 6 months .. You might have better estimates though.
--- Jura 11:08, 29 June 2018 (UTC)
Hello Jura,
As mentioned above by Lydia, we think that there is nothing pressing us right now. When the time comes we'll make a plan. Lea Lacroix (WMDE) (talk) 12:05, 11 July 2018 (UTC)

Wikidata API not acessible via URL with CONSTRUCT in query

Unfortunately since some point in time in May 2018 it is not longer possible to query the Wikidata API via URL completely.

As far as I can see, the query API is working fine in the context of functionality. So if we for example adding this query, the given results are fine. https://query.wikidata.org/#CONSTRUCT%7B%3Ffilm%20%3Fp%20%3Fo.%7D%20%20WHERE%20%7B%0A%20%20%3Ffilm%20wdt%3AP31%20wd%3AQ11424.%0A%20%20%3Ffilm%20wdt%3AP179%20wd%3AQ2484680.%0A%20%20%3Ffilm%20%3Fp%20%3Fo.%0A%7D

But if we use the respective URL acess, to be able to handle the results in our own application, the data is not accessible anymore. (cf. https://query.wikidata.org/sparql?query=CONSTRUCT%7B%3Ffilm%20%3Fp%20%3Fo.%7D%20%20WHERE%20%7B%0A%20%20%3Ffilm%20wdt%3AP31%20wd%3AQ11424.%0A%20%20%3Ffilm%20wdt%3AP179%20wd%3AQ2484680.%0A%20%20%3Ffilm%20%3Fp%20%3Fo.%0A%7D)

At first I thought it would not work anymore due to changes in the API, but as the query works still in the web interface (cf. first link), and the URL access is also offered at the code section of the web interface with exactly the same link, thus not accessible, I think this bug should be fixed.

Did I miss any information about this URL queriing possibility? Or is it a bug already working on? N0omB (talk) 12:24, 9 July 2018 (UTC)

So for me the URL is not working in the browser, but works fine with CURL. What library do you use in your application? Are there any error messages? Jonas Kress (WMDE) (talk) 10:28, 11 July 2018 (UTC)

LEFT-TO-RIGHT MARK

I'm not sure exactly what sort of normalization is performed on (monolingual) strings, but it appears that we strip certain whitespace from both ends. I found a case of an invisible "left to right mark" character (U+200E) that a user had appended to a string. I think these could usefully be stripped as well.

https://www.wikidata.org/w/index.php?title=Q21877685&diff=prev&oldid=512551790

For the avoidance of doubt, I'm not trying to criticize the user who made this change. I'm sure it was just a copy-and-paste and they had no idea. Cheers, Bovlb (talk) 23:08, 9 July 2018 (UTC)

Thanks for noticing. We are going to investigate about this. Lea Lacroix (WMDE) (talk) 12:06, 11 July 2018 (UTC)

units displayed as QIDs

It seems frequent today, but tends to disappear when one edits items. What happened?
--- Jura 12:53, 12 July 2018 (UTC)

It was a bug that has been fixed, should not occur anymore. Purging the page to refresh the last remaining. If it's still happening despite purging, let us know. Lea Lacroix (WMDE) (talk) 15:08, 12 July 2018 (UTC)

Hard to read titles

Update to the archived discussion Wikidata:Contact the development team/Archive/2018/01#Hard to read titles: don't really know if this is a problem for others; however, it is no longer a problem for me since I bought a new computer. It's a widescreen, so this problem went away for me. Just fyi. Thank you for your input and help!  Paine Ellsworth  put'r there  08:02, 13 July 2018 (UTC)

"20. century" doesn't mean 2000–2099

Is it actually technically possible to fix phab:T95553/phab:T196674? As far as I'm aware this bug is basically like displaying "19.5±.5" for values internally stored as 20.49±.5, so that all of the data entered with a precision of integer is possibly wrong; so this is probably not something that should be lying around unfixed. Jc86035 (talk) 07:29, 17 July 2018 (UTC)

Since it is fairly evident from the age of the Phabricator tasks that no one wants to fix this, I've made a bot request. Jc86035 (talk) 11:48, 17 July 2018 (UTC)

Lexeme numbers made jumps

The following lexemes were apparently created consecutively: głuszec (L7038), tannpirkar (L7042) and niedziela (L7044). What happened? --Njardarlogar (talk) 07:58, 19 July 2018 (UTC)

Probably someone wanted to create the missing ones, but for some reason this was not successful and the L-ID is lost forever. The same happens to Q-IDs, where we omit about one out of three these days (see the black bars in User:MisterSynergy/itemstats). I think the item creation rate limit is to some extent responsible. —MisterSynergy (talk) 08:14, 19 July 2018 (UTC)
Tool Wikidata Lexeme Forms returned to me error messages (sorry don't remeber exact wording) that server is overloaded and cannot create lexemes, but apparently it reserved ids for them. I workarounded it by creating lexemes through Special:NewLexeme and then added forms with tool. KaMan (talk) 08:24, 19 July 2018 (UTC)
@Lucas Werkmeister: can you have a look if it's your tool creating this problem? Lea Lacroix (WMDE) (talk) 12:18, 19 July 2018 (UTC)
Hm, I’m not sure how my tool could have caused this… if the API returned that error, I guess it’s possible, but the tool doesn’t really do anything that special, so I’m not sure how I could prevent it. @KaMan: can you take a screenshot of the error if it happens again? --Lucas Werkmeister (talk) 20:38, 19 July 2018 (UTC)
Ok. KaMan (talk) 06:11, 20 July 2018 (UTC)

Wikibase Repository’s naming convention

Hi, I have a Gamepedia wiki and I would like to use Wikibase to store variables on a namespace (Properties:) and retrieve them in the main namespace. And I’d also a third tab between Article and Discussion. Is there a way to name items pages with its real name instead of Q173 or Qsomething ? Otherwise how do I link a page if the basepagename doesn’t match ?

Thank you --CreativeC (talk) 11:15, 17 July 2018 (UTC)

Interface language bug

Tracked in Phabricator
Task T199983
Was: ‎Language says English but is showing German

My language says English but is showing German. I have tried switching languages and switching back but the issue still exists. Image at https://unsee.cc/1105249c/ Please ping in reply. --Emir of Wikipedia (talk) 18:27, 18 July 2018 (UTC)

Was: Some texts of this property show up in Chinese

It seems to be the only property affected, but for 2022 Harmonized System Code (P5471) some texts show up in what it seems to be Chinese. For instance instead of the header "Data type", "数据类型" appears, also for the string "references" is shown in Chinese. Refreshing the page doesn't solve it. I have opened the page in another browser and the same happens.--Micru (talk) 08:24, 19 July 2018 (UTC)

In this one it also happens (but in Japanese): GlyphWiki ID (P5467).--Micru (talk) 08:30, 19 July 2018 (UTC)

Some of the text in my interface (e.g. "references") has randomly switched to French; others (in the same room at Wikimania) are seeing German. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:34, 19 July 2018 (UTC)

Task filed at phab:T199983. Quiddity (talk) 11:47, 19 July 2018 (UTC)

This has been fixed for now. We're looking into a better fix. --Lydia Pintscher (WMDE) (talk) 09:51, 26 July 2018 (UTC)

schema:about triples without schema:isPartOf on query server

Q23769546 doesn't seem to have schema:isPartOf on query server [1]. The same goes for a few others I added yesterday. --
--- Jura 10:09, 14 July 2018 (UTC)

@Jura1: [2] This query seems to work better. Bovlb (talk) 16:28, 15 July 2018 (UTC)
@Bovlb: I'm not sure, try another item, you will see that you get more triples (e.g. Q21508594). --
--- Jura 17:30, 15 July 2018 (UTC)
@Jura1: [3][4] These two queries both produce five results for me. Bovlb (talk) 17:41, 15 July 2018 (UTC)
Strange, I get 1 triple only for Q23769546.
--- Jura 17:52, 15 July 2018 (UTC)
Hmm. Is query.wikidata.org load-balanced? I have seen BlazeGraph drop an update block occasionally . Bovlb (talk) 18:09, 15 July 2018 (UTC)
There are at least two servers, but it seems I keep getting the wrong one ;)
--- Jura 18:12, 15 July 2018 (UTC)

Technical Advice IRC Meeting

 

We'd like to invite you to the weekly Technical Advice IRC meeting. The Technical Advice IRC Meeting (TAIM) is a weekly support event for volunteer developers. Every Wednesday, two full-time developers are available to help you with all your questions about Mediawiki, gadgets, tools and more! This can be anything from "how to get started" and "who would be the best contact for X" to specific questions on your project.

The Technical Advice IRC meeting is every Wednesday 3-4 pm UTC as well as on every first Wednesday of the month 11-12 pm UTC.

If you already know what you would like to discuss or ask, please add your topic to the next meeting: Technical Advice IRC meeting

Cheers, -- Michael Schönitzer (WMDE) (talk) 14:27, 30 July 2018 (UTC)

Valid URL rejected

I have been unable to add the valid URL:

http://www.qucosa.de/recherche/frontdoor/?tx_slubopus4frontend[id]=2601

to Fusion von Geodaten unterschiedlicher Quellen in Geodateninfrastrukturen am Beispiel von ATKIS und OpenStreetMap (Q55832954) using full work available at URL (P953). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:07, 30 July 2018 (UTC)

I was able to add it as http://www.qucosa.de/recherche/frontdoor/?tx_slubopus4frontend%5Bid%5D=2601 -- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:19, 30 July 2018 (UTC)
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Contact_the_development_team/Archive/2018/07&oldid=726588158"