User talk:Yurik

Previous discussion was archived at User talk:Yurik/Archive 1 on 2016-06-28.

You mentioned pronunciation recording efforts, just making sure you are aware of this tool: https://github.com/abartov/pronuncify

Maybe you can ask the developer to add support to Wikidata.

Hi Yurik, I think the tool Lexicator should be added to this list:

Wikidata:Tools/Lexicographical data

Hi, thanks a lot for your work with the Russian lexemes!

I saw here https://www.wikidata.org/wiki/User_talk:Uziel302 that you also have an interest in modifying QS to support lexemes. Did you see this https://phabricator.wikimedia.org/T220985 ?

Hi, the Template:Graph:Stacked that you created is broken and does not work anymore with queries. Could you fix it please?

@steak: it is not the graph that's broken, it is the Wikidata query service. Please file a ticket in Phabricator, or find an existing ticket about this. Not much I can do from the graph side :(

Ahh too bad. Whats the problem with the query service?

I've been trying to figure out how visualizations of parliamentary votes and such could be created. One necessary component would be data for the seating plan, where each member of parliament sits, so I started some property proposals at Wikidata:Property proposal/Seating chart properties, for a system where each legislative term would have an associated "seating plan" item, which would include an SVG image with identifiers for each seat, and statements linking each seat to a person.

I don't think we currently have anything that could work with such a system, but does this sound possible to work with long-term? I don't know if there's a better way to store such data, or if there's any existing way to work with SVG's with markers like that.

Every response for this survey can help the Wikimedia Foundation improve your experience on the Wikimedia projects. So far, we have heard from just 29% of Wikimedia contributors. The survey is available in various languages and will take between 20 and 40 minutes to be completed. Take the survey now.

If you have already taken the survey, we are sorry you've received this reminder. We have design the survey to make it impossible to identify which users have taken the survey, so we have to send reminders to everyone. If you wish to opt-out of the next reminder or any other survey, send an email through EmailUser feature to WMF Surveys. You can also send any questions you have to this user email. Learn more about this survey on the project page. This survey is hosted by a third-party service and governed by this Wikimedia Foundation privacy statement. Thanks!

WMF Surveys, 01:39, 13 April 2018 (UTC)

Hello! The Wikimedia Foundation is asking for your feedback in a survey. We want to know how well we are supporting your work on and off wiki, and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation. You have been randomly selected to take this survey as we would like to hear from your Wikimedia community. The survey is available in various languages and will take between 20 and 40 minutes.

Take the survey now!

You can find more information about this survey on the project page and see how your feedback helps the Wikimedia Foundation support editors like you. This survey is hosted by a third-party service and governed by this privacy statement (in English). Please visit our frequently asked questions page to find more information about this survey. If you need additional help, or if you wish to opt-out of future communications about this survey, send an email through the EmailUser feature to WMF Surveys to remove you from the list.

Thank you!

WMF Surveys, 18:57, 29 March 2018 (UTC)

Hi,

Right now, the number are formatted as English number (10,000), is it possible to add a parametter to format as European numbers (10 000) ? (it is important as the comma is already used as decimal separator in Europe so this can be quite confusing).

Cdlt

Hi, The graphs should eventually automatically change formatting based on the Wiki's default number formatting, but that requires some work on the server side -- phab:T100444. There might be a way to hack around it, but it might be very unstable without a good result.

Привет!

А это так задумано, что Q7303643 сделан отдельным от Q2167520? Dr Bug (Vladimir V. Medeyko) 22:36, 26 January 2017 (UTC)

Well done sir! Fixed :)

Running into some problems with Kartographer, specifically to replace OpenStreetMap Relation identifier (P402) where it's referenced in frwiki with the template {{Bases géographiques}}. I've tried making a few maplinks for demonstration purposes in the deletion discussion. Unfortunately the first two had to be fixed in OSM and are taking time to update (more than one object has the Wikidata ID and Kartographer just gets the first one), and Amazon and Aire just aren't rendering for some reason. I've also tried with public transport relations like Q837601 Kam Sheung Road Station (visible on the item with Abbe98's OpenStreetMap script), but because they're mixed between ways and nodes Kartographer refuses to render them.

Is it technically feasible to (a) render all objects in an OSM relation (and its subrelations) automatically regardless of object type or (b) render all objects which have a particular Wikidata ID?

In addition, as far as I'm aware there's no way in Lua or anything to just pull a relation ID from OSM with a Wikidata ID like you can with {{#property:P402}}, which might be a problem for templates which just want to link to the OSM relation. (Not a problem with Kartographer but the WD property.)

(also maplink doesn't work in Flow, might be a minor problem.)

Kartographer should show all items (ways and relations only, not nodes) from OSM with the same Wikidata ID (it uses SQL's UNION). It might not show something if it's a broken polygon. Btw, the coordinates template in ruwiki has recently been updated to use <maplink> instead of geohack, e.g. Salzburg. In short, Kartographer should pick up any relations and ways (not super relations or nodes) as polygons and lines. If not, there is some bug that needs to be fixed. Most likely - in OSM data, but it is possible that it is in the osm2pgsql or some other system. Please file a phab: ticket - I am no longer on the project, so I will not be able to do anything beyond my usual volunteer help.

a) in most cases, both a polygon and a line exists with the same Wikidata ID due to how osm2pgsql converts osm data - that's one of the reasons we have geoshape and geoline. And osm2gpsql ignores super relations (relations of relations). b) this should already be the case

As for Lua, it can only access datasets from commons and wikidata properties for a specific entity - the only two forms of external data available to it. In theory, there could be a bot that copies complex query results into datasets on commons, and articles could use those results, but this might be overly complex.

Okay then. Filed three separate bugs, hope something useful comes out of them.