Mediawiki-api May 2014

mediawiki-api@lists.wikimedia.org

5 participants
7 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

A question about UPLOAD update
by Liu Chenheng 02 Dec '14

02 Dec '14

Hi, All, I found in some of the UPLOAD update, there is no page id: <rc type="log" ns="6" title="File:Lucian A. Sperta- Nunez.jpg" rcid=" 114549183" pageid="0" revid="0" old_revid="0" user="Azarel63"oldlen="0" newlen="0" timestamp="2014-01-05T11:09:38Z" comment="User created page with UploadWizard" logid="77242320" logtype="upload"logaction="upload" img_sha1=" sf9t03wg27tl73nnde3jzfuxncefux9" img_timestamp="2014-01-05T11:09:36Z"/> <rc type="log" ns="6" title="File:Gingerbread spices (annotated).jpg" rcid=" 114549185" pageid="30485540" revid="0" old_revid="0"user="SKopp" oldlen="0" newlen="0" timestamp="2014-01-05T11:09:37Z" comment="User created page with UploadWizard" logid="77242318"logtype="upload" logaction="upload" img_sha1=" q84abqjr2n4bmn7o6j4uovpl5ufs2gq" img_timestamp="2014-01-05T11:09:37Z"/> The first one has no page id but the second one has. Does anybody can tell me the differences? Thanks, Ethan Liu

4 6

Changes in API action=parse&mobileformat=...
by Max Semenik 09 Jun '14

09 Jun '14

Hi, in response to bug 54607 [1], we've changed the semantics of the mobileformat parameter to action=parse == Summary == Previously, it used to accept strings 'html' or 'wml', later just 'html' and modify the structure of output (see below). This was problematic because you needed to retrieve the HTML from output in different ways, depending on whether mobileformat is specified or not. Now, mobileformat is a boolean parameter, that is if there's a 'mobileformat' parameter in request, it will be treated as "the output should be mobile-friendly", regardless of value. And the output structure will be the same. For compatibility with older callers, mobileformat=(html|wml) will be special-cased to return the older structure at least for 6 month from now. These changes will start being rolled out to the WMF sites starting from tomorrow, Tuesday October 24th and this process will be complete by October 31st. == Examples == === Non-mobile parse === api.php?action=parse&format=xml { "parse": { "title": "...", "text": { "*": "foo" } } } api.php?action=parse&format=json <?xml version="1.0"?> <api> <parse title="..." displaytitle="..."> <text xml:space="preserve">foo</text> </parse> </api> === Parse that outputs mobile HTML, old style === api.php?action=parse&format=json&mobileformat=html { "parse": { "title": "API", "text": "foo" } } api.php?action=parse&format=xml&mobileformat=html <?xml version="1.0"?> <api> <parse title="..." text="foo" displaytitle="..."> </parse> </api> === Parse that outputs mobile HTML, new style === api.php?action=parse&format=...&mobileformat Same as for non-mobile parses. == FAQ == Q: I didn't use mobileformat before, does anything change for me? A: No. Q: I use mobileformat=html, will my bot/tool be broken now? A: No, you will have 6 months to switch to new style. Q: I'm only planning to use mobileformat, what should I do? A: Just use the new style. Q: How did this format discrepancy appear in the first place? A: To err is human. ----- [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=54607 -- Best regards, Max Semenik ([[User:MaxSem]])

2 2

how to get a page's wikidata page id?
by Tom Malcolmson 29 May '14

29 May '14

The 'basic info' for every page includes its wikidata page id, e.g. http://en.wikipedia.org/w/index.php?title=Roy_Dowling&action=info But I don't see anyway to retrieve this. I might have thought it would be a property that could be retrieved as part of a query, but I don't see it. Am I missing something or is it not available yet? Thanks, Tom

3 3

[Mediawiki-api-announce] BREAKING CHANGE: action=logevents will no longer allow both letitle and leprefix
by Brad Jorsch (Anomie) 28 May '14

28 May '14

Gerrit change 135283 <https://gerrit.wikimedia.org/r/#/c/135283/> will cause action=logevents to return an error if both the letitle and leprefix parameters are specified. Previously specifying both of these parameters would apply both filters, making leprefix pointless if letitle matches the prefix or returning no results if not. The expected impact of this change is low, as no uses of this parameter combination were logged in the time period checked. If any client is affected by this change, it may simply remove leprefix when letitle is specified. This change will be deployed to WMF wikis with 1.24wmf7, see https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap for the schedule. -- 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 0

[Mediawiki-api-announce] BREAKING CHANGE: action=edit with redirect following will no longer support replacing page text
by Brad Jorsch (Anomie) 20 May '14

20 May '14

Gerrit change 133955 <https://gerrit.wikimedia.org/r/#/c/133955/>, which I plan to merge on Thursday for deployment to WMF wikis with 1.24wmf7<https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap>, will cause the API to report an error when action=edit is used with the "redirect" parameter and none of "appendtext", "prependtext", or "section=new" are used. This will occur regardless of whether the page being edited is actually a redirect. API action=edit has a "redirect" parameter, which will automatically edit the target page if the supplied title is a redirect. The original intention of this feature was to be used in combination with appendtext or section=new for posting notifications to user talk pages without having to first check whether the page is a redirect (see bug 24330<https://bugzilla.wikimedia.org/show_bug.cgi?id=24330>). But as currently implemented it will perform the edit even when replacement page text is supplied, which is extremely prone to error: while reviewing the patch proposing this change, I reviewed several scripts and bots that were logged as submitting API requests with this combination of parameters and every one would make erroneous edits when the target page is a redirect. Clients not using the "redirect" parameter to action=edit or clients that use it in combination with "appendtext", "prependtext", or "section=new" will not be affected by this change. Affected clients have several options for coping with this change, such as: - Stop supplying the "redirect" parameter to action=edit, which will edit the redirect page itself. - When fetching the page content to transform it for the edit, use the "redirect" parameter to action=query and submit the edit to the target page directly (and without using the "redirect" parameter to action=edit) rather than via the redirect title. - Use appendtext, prependtext, or section=new instead of loading the page's wikitext and appending or prepending content on the client side. - Detect the redirect when fetching the page content and treat the unexpected redirect as an error condition. Or handle the error returned by action=edit in whatever manner is appropriate to your script, bot, or tool. See https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap for the deployment schedule. -- 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 0

Aaron Halfaker's new "MediaWiki utilities" library
by Sumana Harihareswara 06 May '14

06 May '14

https://pythonhosted.org/mediawiki-utilities/ "MediaWiki Utilities is an open source (MIT Licensed) library developed by Aaron Halfaker for extracting and processing data from MediaWiki installations, slave databases and xml dumps." It's Python, and requires Python 3 or later. For instance, check out https://pythonhosted.org/mediawiki-utilities/core/api.html . "Session – Constructs an API session with a MediaWiki installation. Contains convenience methods for accessing prop=revisions, list=usercontribs, meta=siteinfo, list=deletedrevs and list=recentchanges." -- Sumana Harihareswara Senior Technical Writer Wikimedia Foundation

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Mediawiki-api May 2014