Dear Edgars2007, since you are an administrator on a wiki from which no user participated in this discussion, I'd like to make sure you are aware of some recent events which may alter what the Wikimedia Foundation lets you do on your wiki: Superprotect.
- Request for comment: Requests for comment/Superprotect rights
- An open letter about its implementation: Letter to Wikimedia Foundation: Superprotect and Media Viewer
Peteforsyth 09:12, 12 September 2014 (UTC)
I am contacting you because you have left feedback about VisualEditor at pages like mw:VisualEditor/Feedback in the past. The Editing team is now asking for your help with VisualEditor. Please tell them what they need to change to make VisualEditor work well for you. The team has a list of top-priority problems, but they also want to hear about small problems. These problems may make editing less fun, take too much of your time, or be as annoying as a paper cut. The Editing team wants to hear about and try to fix these small things, too.
More information (including a translatable list of the questions) is posted on wiki at mw:VisualEditor/Survey 2015. If you have questions, or prefer to respond on-wiki, then please leave a message on the survey's talk page.
Global user page migrationEdit
Hello Edgars2007. I deleted your local user pages on all wikis as you requested via Synchbot, and your global user page is now active. You can see the deletion log on your archive page. :) —Pathoschild 18:49, 28 June 2015 (UTC)
Hi! You voted for the cross-wiki watchlist as an important suggestions in the community wishlist survey last year. I'm pinging editors who showed interest in that task to tell them we have some suggestions for how things could look, if you'd like to glance at them and give us some feedback. You can find them on the project page on Meta. If you'd like to share any comments, you're very welcome to do so on the talk page. /Johan (WMF) (talk) 01:09, 21 May 2016 (UTC)
2016 Community Wishlist SurveyEdit
You’re getting this message because you participated in the 2015 Community Wishlist Survey and we want to make sure you don't miss it this year – or at least can make the conscious choice to ignore if it you want to. The 2015 survey decided what the Community Tech team should work on during 2016. It was also the focus of Wikimedia hackathons and work by other developers. You can see the status of wishes from the 2015 wishlist at 2015 Community Wishlist Survey/Results.
The 2016 Community Wishlist Survey is now open for wishes. You can create proposals until November 20. You will be able to vote on which wishes you think are best or most important between November 28 and December 12. /Johan (WMF) (talk) via MediaWiki message delivery (talk) 11:17, 14 November 2016 (UTC)
Commond deletion bot requirementsEdit
I'm contacting you because you supported the Commons Deletion Bot proposal in the 2017 Community Wishlist. The Wishlist team has finalized the draft specifications for how the bot will work, and are seeking review in confirming or discussing the plans for the bot. If you have some time, please take a look and leave a comment. Thanks, happy editing to you. - Keegan (WMF) (talk) 19:06, 12 April 2018 (UTC)
Can you explain reasons for this block? It is not a vandal – I saw this user fixing attribution of images. More importantly, files in question were on Commons at the time, until Jcb deleted them. Incnis Mrsi (talk) 18:12, 13 April 2018 (UTC)
Commons deletion notification botEdit
You are receiving this message because you supported the Commons deletion notification bot in the 2017 Community Wishlist Survey.
Commons deletion notification bot is ready to be deployed to any Wikimedia wiki that wishes to use it. If your community is interested in the bot, you can leave a request on the project page on meta-wiki. The bot messages are available for translation on translatewiki.net, as part of preparing the bot for release.
The Community Wishlist SurveyEdit
You get this message because you’ve previously participated in the Community Wishlist Survey. I just wanted to let you know that this year’s survey is now open for proposals. You can suggest technical changes until 11 November: Community Wishlist Survey 2019.
You can vote from November 16 to November 30. To keep the number of messages at a reasonable level, I won’t send out a separate reminder to you about that. /Johan (WMF) 11:24, 30 October 2018 (UTC)
The Slovene cultural registry importEdit
Hi, as promised on Facebook, here's some details about the job: here's the API for the Slovene cultural registry information service. It contains data on about 30.000 listed objects, of which we're interested in ~10.000 that are listed as cultural monuments (for now). Infrastructure on Wikidata is already set up, currently we have about 770 objects already entered manually - all the details are on WikiProject Slovenia and the constraint violation report for the main part: the unique identifier EŠD.
What would be needed is as follows: to read all the data tables and pull out the subset by listing type (monument of local/national importance), then import the data for those that aren't already in Wikidata. Use the data to create objects and populate some key properties - country, municipality, settlement, EŠD number, type of object, type of listing. Coordinates should also be included, but this part is more tricky, because spatial data is stored as polygons and I'm not sure if those can be easily converted. For all the objects already in Wikidata, type of listing should be compared and updated where necessary. For all processed fields, "Stated in: Q18375284" should be added as a reference, and for listing type, "start time" should be read from the data tables and added.
Can you take a look and see if you can make sense of the API? The key fields (as far I'm able to tell) are:
- OBCINA (municipality)
- NASELJE (settlement)
- ESD (the EŠD number)
- TIP (type of object)
- IME (name)
- RZGLOBDOBJ (date for "start time" of listing, although I'm not sure it's the right one)
- SHAPE data, if we can use it
- @Yerpo: hi! Well, there are two bad and one good news. I won't let you choose the order, because it matters :D
- (1st bad) well, that API isn't what we (developers) usually understand with API. That is some kind of geographical API
- (1st good) by coincidence I work at cartography company, where are people, who work with geographical data.
- (2nd bad) they couldn't help me in exporting the data into something usable, they saw something like this for the first time :D