Mediawiki-api December 2017

mediawiki-api@lists.wikimedia.org

4 participants
5 discussions

Need to extract abstract of a wikipedia page
by aditya srinivas 23 Nov '23

23 Nov '23

Hello, I am writing a Java program to extract the abstract of the wikipedia page given the title of the wikipedia page. I have done some research and found out that the abstract with be in rvsection=0 So for example if I want the abstract of 'Eiffel Tower" wiki page then I am querying using the api in the following way. http://en.wikipedia.org/w/api.php?action=query&prop=revisions&titles=Eiffel… and parse the XML data which we get and take the wikitext in the tag <rev xml:space="preserve"> which represents the abstract of the wikipedia page. But this wiki text also contains the infobox data which I do not need. I would like to know if there is anyway in which I can remove the infobox data and get only the wikitext related to the page's abstract Or if there is any alternative method by which I can get the abstract of the page directly. Looking forward to your help. Thanks in Advance Aditya Uppu

4 3

[Mediawiki-api-announce] Deprecation of list=allusers 'recenteditcount' result property
by Brad Jorsch (Anomie) 16 Apr '19

16 Apr '19

When list=allusers is used with auactiveusers, a property 'recenteditcount' is returned in the result. In bug 67301[1] it was pointed out that this property is including various other logged actions, and so should really be named something like "recentactions". Gerrit change 130093,[2] merged today, adds the "recentactions" result property. "recenteditcount" is also returned for backwards compatability, but will be removed at some point during the MediaWiki 1.25 development cycle. Any clients using this property should be updated to use the new property name. The new property will be available on WMF wikis with 1.24wmf12, see https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap for the schedule. [1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=67301 [2]: https://gerrit.wikimedia.org/r/#/c/130093/ -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation _______________________________________________ Mediawiki-api-announce mailing list Mediawiki-api-announce(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce

1 1

Fair Use of The MediaWiki API In A Game‏
by Tal Barda 01 Jan '18

01 Jan '18

Hello! I hope this is the correct place to ask this question. My name is Tal, and I'm developing my own version of the Wiki Game <https://en.wikipedia.org/wiki/Wikipedia:Wiki_Game> (or Wiki Race, some may say) for Android devices. There is a great multiplayer version <https://thewikigame.com/>of it for the iPhone and Web, but I think there should be a worthy version to the Android. My version is still in progress, and I put a lot of effort into it, including the gameplay experience (single-player and multiplayer) and the design. _________________________ I'm writing this email because I'd like to consult with some wiki experts about one of the main things which on my mind, and it's my usage of the Mediawiki API. I'd like to launch the game and upload it to the Play Store in a few months, but I can't keep working on it while knowing that I might put my efforts in danger if I will do so, because of unfair usage of the Wiki API. Well, the game is based on generating two random articles: the first article (the starting point) and the target article (the end point) which the user should reach to using only the hyperlinks inside the articles. The thing is, that unlike the currently exist Wiki Game <https://thewikigame.com/> version which is played by many users together at the same time (by joining "game rooms"), or using pre-generated articles, - I'm generating the articles live for each user individually. Each user can play in single-player mode and generate his own pair of articles, his own game, a thing which is gonna keep the game infinite for all of the players. My generator generates two articles before each game and the user has 15 seconds to decide whether he would like to start the game or not. After the 15 seconds are up the generator is generating a new pair of articles. While the time is running, the user may refresh the articles manually and ask to generate a new pair. So why am I worried about my app's usage of the API? Well, not all of the target articles are reachable through the hyperlinks in the mobile version of Wikipedia, because the templates view in the mobile version is very limited and there are articles without references from other articles, and I don't want the users to get stuck. In order to overcome this , and make sure that the target article is actually reachable, I need to make about 5 requests to the REST API each articles generation (one request after another, not together). The algorithm was made after a very long time of research by me, and I think its efficient for the purpose. So, I assume that the average player is gonna play about an hour in a day, so he is gonna refresh his pair about 15 times, which are 75 requests from the API in a given day for a user. Let's say (hopefully and hypothetically) the game goes pretty viral - well, there are gonna be a lot of requests to the API at the same time, and this makes me unsure about my way of action. I don't mind sending my random articles generator code (as long it is not copied :P ) for a review, and work together with somebody to make the game better and fair, and I'm also willing to donate a part of the game incomes (if there will be any) to the Wikimedia Foundation, but there is one thing I'm not gonna do, and it's launching the game before I'm making sure I do a fair use of the API. I know Wikipedia is taking care millions and billions of requests everyday, and still - I can't move on without knowing everything is fine. This information <https://www.mediawiki.org/wiki/API:Etiquette> about the usage limits is not very explicit, and it doesn't put the line between good and bad, and maybe I'm using it badly. I will accept every answer respectfully. Thanks in advance, Tal

3 4

Question about 'Api-User-Agent'
by Nikola I. 07 Dec '17

07 Dec '17

About: xhr.setRequestHeader( 'Api-User-Agent', 'Example/1.0' ); Hi, I'm working on the "Build a Wikipedia Viewer" assignment at freeCodeCamp using CodePen. I wanted to access the API via XMLHttpRequest(), but got: index.html:1 Failed to load https://en.wikipedia.org/w/api.php?action=query&prop=links&format=json&titl… : Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://s.codepen.io' is therefore not allowed access. What would be the correct way to get connected to the API? Thanks in advance, Nikola Irobaliev (freeCodeCamp student) https://codepen.io/aus-fl/pen/WXWabX My experimental code: function loadXMLDoc() { var xhttp = new XMLHttpRequest(); xhttp.open( "GET", " https://en.wikipedia.org/w/api.php?action=query&prop=links&format=json&titl… ", //" https://en.wikipedia.org/w/api.php?action=query&list=search&srsearch=Bulgar… ", //" https://en.wikipedia.org/w/api.php?action=query&list=search&prop=info&inpro… ", true ); xhttp.setRequestHeader( 'Api-User-Agent', 'Build a Wikipedia Viewer at freeCodeCamp ( https://codepen.io/aus-fl/pen/WXWabX; support(a)aus-fl.com)' ); xhttp.send(); xhttp.onreadystatechange = function() { if (this.readyState == 4 && this.status == 200) { var myObj = JSON.parse(this.responseText); document.getElementById("wikidata").innerHTML = this.responseText; //string console.log(JSON.parse(myObj.links[0].title)); } };

2 2

Processing geotags within page created by API
by Jc Barré 04 Dec '17

04 Dec '17

Hi All! First at all, I would like to thank you for your awesome work on the mediawiki code. I'm currenlty working on the ApiEditPage.php of Mediawiki API. Indeed, my aim is to create wiki pages directly from a mobile phone using mediawiki API (1.29) and the GeoData Extension (1.29). Unfortunately, I found out that when inserting a geodata tag ({{#coordinates:xxx}}) in a page using ApiEditPage.php, the coordinates are not saved in the 'geo_tags' database as they should. But they are saved correctly into db when I open the created page in a browser and save it manually. So I tried to find basic solution like adding an equivalent "manual save command" but no luck for the moment. I also tried to replace APIEditBeforeSave by EditFilterMergedContent within the Hooks::run command unsuccessfully. Would you have any idea to perform a correct "manual save command" to force mediawiki to process the geotags written inside the page created by API? Thanks in advance, JC

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Mediawiki-api December 2017