MediaWiki API result

This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Rights_and_restrictions_administration_from_accession_to_access(Mumma)",
        "continue": "gapcontinue||"
    },
    "query": {
        "pages": {
            "113": {
                "pageid": 113,
                "ns": 0,
                "title": "Reqs, tools, design analysis",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "ARCHIVEMATICA session:\n\nprocessing begins and is dependent on working with a file system (thunar with ubuntu OS) -\npre-ingest has been renamed \u201ctransfer processing\u201d\n\nTransfer Processing\n--next iteration of Archivematica is moving many ingest microservices to the transfer watched directory (tab in dashboard); for instance, integrity checking and/or assignment, quarantine, transfer uuid assignment, package extraction, directory structure log (directory printer?)\n\nNext steps\n-need mockup of rights in transfer stage on the dashboard\n-possible addition of microservice for \u201cindex transfer\u201d\n\nnote: during keyword and pattern matching work \u2013 good to have institution-specific ontologies\n\nIndexing to identify\n-list of pdfs that haven't been ocr'ed\n-list of password protected files\n\nnote: should we move format identification forward so we can use visualization tools to visualize format distribution?\n\nSuggestions for Transfer Processing:\n-viewer (add for files that you can't use ubuntu to view)\n-visualizations: graphs of modification/access/creation times (enable date-based range searches)\n-identify duplicates"
                    }
                ]
            },
            "202": {
                "pageid": 202,
                "ns": 0,
                "title": "Research data",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "= Overarching Research Data Issues =\n#Storage\n#Access\n#Management (& Policy)\n#Discovery\n#Formats\n#Assessment\n#*Use/needs from partners\n#Metadata Schemas\n\n= Questions =\n#What are the real world obstacles to large (any) scale data storage and access?\n#What are researchers' curation obligations?\n\n= Notes =\n# JPL = (NASA Jet Propulsion Laboratory). A large repository for research data.\n# ICPSR = (Inter-university Consortium for Political and Social Research). A large repository for social science research data.\n# JPL / ICPSR provides services such as:\n#*Training\n#*Documentation\n\n= Conclusions =\n#Not every academic institution would be expected to have its own research data management apparatus implemented.\n#There are some large scale (and even domain specific?) research data repositories available in the public/private sphere.\n#On-campus research data solutions are generally for a specific audience - those large enough to collect significant data but yet not reached by JPL/ICPSR type repositories."
                    }
                ]
            }
        }
    }
}