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": "ReNamer",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "108": {
                "pageid": 108,
                "ns": 0,
                "title": "ReACT (Resource Audit and Comparison Tool)",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "{{Infobox tool\n|purpose=A file audit and comparison tool using Microsoft Excel and VBA.\n|homepage=http://wiki.opf-labs.org/display/SPR/File+management+and+matching+of+tif%2C+htm+and+pdf+files+solution\n|function=File Management, Quality Assurance\n}}\n{{Infobox tool details\n|ohloh_id=Resource Audit and Comparison Tool (ReACT)\n}}\n= Description =\nReACT uses VBA macros within a Microsoft Excel environment to implement automated comparisons of files across folder and directory structures through a simple GUI. The tool was developed in a way that makes it adaptable to discreet differences within archival infrastructures, so that users can specify directories that they wish to compare and search these folders recursively. At the same time ReACT allows users to set matching parameters with the audit process, particularly file type. Once completed the results of the audit are viewed through a series of discrete datasheets which allow for straightforward comparison of files that have been Matched\u2122 or those which are missing or have been mismatched.\n\n= User Experiences =\nMore information about use of this tool on the Archaeology Data Service's blog: http://archaeologydataservice.ac.uk/blog/2012/12/react/#more-168\n\n= Development Activity =\n\n\n\n=== Release and Activity Feed===\n<rss max=7>https://github.com/openplanets/SPRUCE/commits/master.atom</rss>"
                    }
                ]
            },
            "399": {
                "pageid": 399,
                "ns": 0,
                "title": "ReDBox",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "{{Infobox tool\n|purpose=ReDBox and Mint are two complimentary applications designed to create, store, and provide access to research metadata.\n|homepage=http://www.redboxresearchdata.com.au/\n|function=Metadata Processing, Managing Active Research Data\n|content=Research Data\n}}\n{{Infobox tool details\n|ohloh_id=ReDBox\n}}\n= Description =\n[http://www.redboxresearchdata.com.au/ ReDBox] and Mint are two complimentary applications designed to create, store, and provide access to research metadata. RedBox provides workflows and user interfaces for entering and managing research data descriptors, while Mint serves as a name authority and vocabulary system.\n \n====Provider====\nAustralian National Data Service\n \n====Licensing and cost====\n[http://creativecommons.org/licenses/by-nc-sa/3.0/au/ Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Australia License] - free\n \n====Platform and interoperability====\nBoth ReDBox and Mint have been tested on Ubuntu, RedHat, Solaris, and Windows; the site states that the software will function on any &lsquo;modern, general-purpose&rsquo; operating system. The software requires Sun Java JVM 1.6; the project recommends having at least 10Gb of storage space, with at 1Gb of RAM for both pieces.\nThe software is built on the Fascinator Platform. The Jetty server is included with the installations, and all documentation is based on that configuration; other container servers, such as Apache Tomcat, remain untested. The software can integrate with VTLS Vital and Fedora repositories, and also integrates Handle assignment.\n \n====Functional notes====\nReDBox uses a filesystem storage mechanism as its default, under the assumption that actual research data, which often is quite large, will be hosted in a larger repository. The system does allow for the upload of non-metadata files such as supporting licenses and IP statements. It can, however, integrate with Fedora Commons, using Apache Solr to drive the portal interface.\nRedBox attempts to follow Linked Data principles in its metadata creation, but needs the Mint to make this meaningful to outside repositories and data sources. The Mint can assign Linked Data identifiers to the materials, and can integrate information from external comma-separated files; this allows, for example, a repository to incorporate HR data to describe the researchers and grants attached to a dataset. The Mint has a number of common standard vocabularies ready to upload.\nThe two applications may be used as individual, separate systems.\n \n====Documentation and user support====\nThe project site offers extensive documentation, including a user guide, a Developer wiki, and workshop materials. The site also links to an active [https://groups.google.com/forum/?fromgroups#!forum/redbox-repo Forum]. Test sites are available for both [http://redbox-dev.cqu.edu.au/redbox/default/home RedBox]&nbsp;and [http://redbox-dev.cqu.edu.au/mint/rda_parties/home Mint].\n \n====Usability====\nThe software is accessed through a graphical user interface.\n \n====Expertise required====\nInstallation and configuration require solid knowledge of application design and technologies. Users should be thoroughly familiar with the metadata standards &ndash; both disciplinary and preservation-related &ndash; preferred by their organisation.\n \n====Standards compliance====\nThe system adheres to Linked Data principles, and provides an OAI-PMH interface. The Mint can assign Handles.\n \n====Influence and take-up====\nReDBox has among its users Deakin University; Flinders University; James Cook University; Swinburne University of Technology; University of Adelaide; University of Newcastle, Australia; University of Technology Sydney; University of Western Sydney; University of Tasmania; and Research Data Australia.\n\n\n= User Experiences =\n\n\n= Development Activity =\n<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. -->\nVersion 1.6.1 was released in May 2013, and the [https://github.com/redbox-mint GitHub source code repository] shows that development activity is continuing. All development activity is visible on GitHub: http://github.com/redbox-mint/redbox/commits\n \n \n=== Release Feed ===\nBelow the last 3 release feeds:\n<rss max=3>https://github.com/redbox-mint/redbox/releases.atom</rss>\n  \n \n=== Activity Feed ===\nBelow the last 5 commits:\n<rss max=5>https://github.com/redbox-mint/redbox/commits/master.atom</rss>"
                    }
                ]
            }
        }
    }
}