This repo will not not be updated anymore, please see from now on.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
example files

This repo will not not be updated anymore, please see from now on


An algorithm to identify authorship and editor interactions in Wiki revisioned content.

(also check out our API: )

Installation Requirements

WikiWho has been tested on Mac OS X and Debian GNU/Linux, running on Python 2.7. (A python3 version can be found in this branch: It has however not been extensively tested yet - stick to the master for now if you want reliability)

WikiWho utilizes the Wikimedia Utilities library to process the revisioned content extracted from Wikipedia. These functions can be downloaded from the Wikimedia Utilities repository (under the MIT license) at the following link:


(Note: is the original script, giving just provenance information. can provide the exact same authorship/provenance data, plus interactions, but might run slower due to the overhead of interaction calculation. We didn't test that yet.)

Expected data:

  • the full revision history of one or a given set of wiki articles (basically everything that wikimedia utilities can process). It is here expected to be .xml, could also be .json, etc. if you parse it correctly.

  • you can get xml for single articles here, although this is only recommended for testing purposes. Or (more reliable, but only 50 revisions at a time) at the official API: example call (note that you will have to use rvcontinue to get all revisions). Finally, the full history dump can be downloaded at the WM dumps page. Note that the dump is quite big for enwiki, i.e. not recommended just for testing. Use wm utilities to read the compressed files.

How to run:



-i [source_file_name.xml] (complete history dump XML of one article)

-o [a | r] --> what type of output to produce --> a = authorship for all tokens of a revision | r = interactions for every revision with each other revision in the past. I.e., this will list you all revisions and for each type of interaction we defined (delete, undelete, reintro, ..) the revisions that were target of that interaction and the number of tokens that interaction included. We will soon provide code that will spit put a more aggregated version of this as an editor-editor network. Yet, from the output available right now, you can already construct such a network yourself by summing up the positive and/or negative interactions between two editors over the whole revision history or a part of it.

-r [<revid> | all] --> what revision to show. revID or "all" for -o a, revID only for -o r


  • example A:

python -i Randomarticle.xml -o a -r 5

gives authorship for all tokens of revision 5 (has to be an actual revision id) of Randomarticle

  • example B:

python -i Randomarticle.xml -o r -r 5

gives the edit interactions produced at every revision to other revisions, up to revision number 5 (has to be an actual revision id) of Randomarticle

  • "Finger_Lakes3" dummy article example:


python -i Finger_Lakes3_dummy.xml -o a -r 27  

the xml file can be found in the "example files" folder. 27 is the last revision, you can also run it for all others. check the Finger_Lakes3_explained.xlsx in the same folder to get an explanation of the results. you can also try the -o r argument, the results are also displayed in the xlsx


  • Fabian Floeck: fabian.floeck[.]
  • Maribel Acosta: maribel.acosta[.]


This work is licensed under the MIT license.