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
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
I want to get a list that "user" is *"patroller" and "blocked"*
my query:
https://en.wikipedia.org/w/api.php?rawcontinue&action=query&list=allusers&
*augroup=patroller&aurights=block*&aulimit=50&auprop=blockinfo
but the api *returns users that is not blocked?*
aurights=block is not working probably?
is it bug on api or am i use wrong?
Hi,
Preface: I understand very little about how ResourceLoader works.
I was trying to use the mw.Api module to do some API calls, following the
general example of the documentation:
*var api = new mw.Api();*
*api.get( {*
* action: 'query',*
* meta: 'userinfo'*
* } ).done ( function ( data ) {*
* console.log( data );*
* } );*
However, I was getting an error in the JS console:
*TypeError: undefined is not a constructor (evaluating 'new mw.Api()')*
For our dev server and on my local instance of MediaWiki (on a Mac),
$wgResourceLoaderDebug is set to *true* so we can debug our individual JS
files. For kicks, I set this value to *false *in my page URL (e.g. "
http://mywiki/index.php/MyPage?*debug=false*"), allowing ResourceLoader to
do its magic - the error went away, giving me the data I wanted. When I
flipped it back to *true*, the error returned.
Is this known behavior, a bug? Or could I have some other strange
configuration which is causing this problem?
Thanks,
--
Jason Ji
jason.y.ji(a)gmail.com
Hello, I am very new to the Wikimedia API, and have only just started
working with it.
I am writing code to access a Wikipedia page via the API, retrieve the text
with prop=extracts, retrieve wikitext via prop=revisions, and retrieve 7
links of some importance, for each of which I query the page image
(pageimages) and it's url (imageinfo),
I am preforming these requests sequentially in accordance with the
description given in the API docs.
I have found that requests, especially the first two for the raw text and
wikitext are taking much longer than expected to conclude. Retrieving plain
text takes around 700 milliseconds, and for wikitext around 800-900 millis.
Some of the problem is related to the response size probably, but querying
for image name and then url which both return a singe result also takes
around 600 milliseconds.
This means that my code is taking around 8-9 seconds to finish running and
that is quite too long. I will be uniting requests with multiple titles,
however I wanted to know if there is any other possible solution.
Thanks!
Hello all,
I am happy to announce the beta release of the Wikimedia REST Content API
at
https://rest.wikimedia.org/
Each domain has its own API documentation, which is auto-generated from
Swagger API specs. For example, here is the link for the English Wikipedia:
https://rest.wikimedia.org/en.wikipedia.org/v1/?doc
At present, this API provides convenient and low-latency access to article
HTML, page metadata and content conversions between HTML and wikitext.
After extensive testing we are confident that these endpoints are ready for
production use, but have marked them as 'unstable' until we have also
validated this with production users. You can start writing applications
that depend on it now, if you aren't afraid of possible minor changes
before transitioning to 'stable' status. For the definition of the terms
‘stable’ and ‘unstable’ see https://www.mediawiki.org/wiki/API_versioning .
While general and not specific to VisualEditor, the selection of endpoints
reflects this release's focus on speeding up VisualEditor. By storing
private Parsoid round-trip information separately, we were able to reduce
the HTML size by about 40%. This in turn reduces network transfer and
processing times, which will make loading and saving with VisualEditor
faster. We are also switching from a cache to actual storage, which will
eliminate slow VisualEditor loads caused by cache misses. Other users of
Parsoid HTML like Flow, HTML dumps, the OCG PDF renderer or Content
translation will benefit similarly.
But, we are not done yet. In the medium term, we plan to further reduce the
HTML size by separating out all read-write metadata. This should allow us
to use Parsoid HTML with its semantic markup
<https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec> directly for
both views and editing without increasing the HTML size over the current
output. Combined with performance work in VisualEditor, this has the
potential to make switching to visual editing instantaneous and free of any
scrolling.
We are also investigating a sub-page-level edit API for micro-contributions
and very fast VisualEditor saves. HTML saves don't necessarily have to wait
for the page to re-render from wikitext, which means that we can
potentially make them faster than wikitext saves. For this to work we'll
need to minimize network transfer and processing time on both client and
server.
More generally, this API is intended to be the beginning of a multi-purpose
content API. Its implementation (RESTBase
<http://www.mediawiki.org/wiki/RESTBase>) is driven by a declarative
Swagger API specification, which helps to make it straightforward to extend
the API with new entry points. The same API spec is also used to
auto-generate the aforementioned sandbox environment, complete with handy
"try it" buttons. So, please give it a try and let us know what you think!
This API is currently unmetered; we recommend that users not perform more
than 200 requests per second and may implement limitations if necessary.
I also want to use this opportunity to thank all contributors who made this
possible:
- Marko Obrovac, Eric Evans, James Douglas and Hardik Juneja on the
Services team worked hard to build RESTBase, and to make it as extensible
and clean as it is now.
- Filippo Giunchedi, Alex Kosiaris, Andrew Otto, Faidon Liambotis, Rob
Halsell and Mark Bergsma helped to procure and set up the Cassandra storage
cluster backing this API.
- The Parsoid team with Subbu Sastry, Arlo Breault, C. Scott Ananian and
Marc Ordinas i Llopis is solving the extremely difficult task of converting
between wikitext and HTML, and built a new API that lets us retrieve and
pass in metadata separately.
- On the MediaWiki core team, Brad Jorsch quickly created a minimal
authorization API that will let us support private wikis, and Aaron Schulz,
Alex Monk and Ori Livneh built and extended the VirtualRestService that
lets VisualEditor and MediaWiki in general easily access external services.
We welcome your feedback here: https://www.mediawiki.org/wiki/Talk:RESTBase
- and in Phabricator
<https://phabricator.wikimedia.org/maniphest/task/create/?projects=RESTBase&…:>
.
Sincerely --
Gabriel Wicke
Principal Software Engineer, Wikimedia Foundation
发件人: shiyue zhang [mailto:byryuer@gmail.com]
发送时间: 2015年3月10日 22:04
收件人: mediawiki-api(a)lists.wikimedia.org
主题: why I can't see deleted revision information?
Hello,
I’m a new user of Wikipedia. My username is Yuer3677.
I’m a senior student in BUPT China, since I am working on my graduating
thesis, which is related to Wikipedia, I really need to get the deleted
revision information.
I try to use action=“query” and list=” deletedrevs”, but the result is
<?xml version="1.0"?>
<api servedby="mw1192">
<error code="drvpermissiondenied" info="You don’t have permission to view
deleted revision information" xml:space="preserve">See https://en.wikipedia.
org/w/api.php for API usage</error>
</api>
So, I want to know why I can’t view the deleted revision information?
Since I really need the data to do my research, what can I do to get the
information?
Please help me. Thanks a lot!