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": "ResearchArchive",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> 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": {
            "2079": {
                "pageid": 2079,
                "ns": 0,
                "title": "Remote Editing",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "__FORCETOC__\n\n= SSH =\n\nFirst, ssh into VM like normal:\n<pre>\nssh blazerid@cheaha.rc.uab.edu\n</pre>\n\nIf you are trying to edit file on VM, not Cheaha, make sure you have tmux installed on system.\n\n<pre>\n# Ubuntu\nsudo apt install tmux\n\n# CentOS\nsudo yum install tmux\n</pre>\n\nNow, create a tmux session and detach right away.\n\n<pre>\ntmux new\n\n# Ctrl+B then D\n^B d\n</pre>\n\nYou can exit this ssh connection now.\n<pre>\nexit\n</pre>\n\nNow ssh with remote command and special option <code> -t Force pseudo-terminal allocation.</code>\n<pre>\nssh -t blazerid@cheaha.rc.uab.edu \"tmux attach\"\n</pre>\n\nor you can setup in your ssh config(<code>~/.ssh/config</code>):\n<pre>\nHost cheaha\n  HostName cheaha.rc.uab.edu\n  User <username>\n  RequestTTY force\n  RemoteCommand tmux attach\n</pre>\n\nWith the setting you can ssh with:\n<pre>\nssh cheaha\n</pre>\n\nEverytime you finish you editing on remote, either Cheaha or VM, use the detach command:\n<pre>\n# Ctrl+B then D\n^B d\n</pre>\n\n== With tmux Control Mode==\n\nNote: It only works with iTerm2 on MacOS\n\nUse <code>-CC</code> option with tmux\n<pre>\nssh -t blazerid@cheaha.rc.uab.edu \"tmux -CC attach\"\n</pre>\n\nThis will launch a new iTerm2 window contents your tmux session.\nYou can create window and panel with iTerm2 shotcuts.\n\n== [[Visual Studio Code]] ==\nVisual Studio Code has official extensions available to enable and facilitate remote development. Three extensions are available from the Visual Studio marketplace. They support remote development over SSH, in containers, and using Windows Subsystem for Linux (WSL). More detailed information on their use can be found at the documentation. To use the the SSH extension to access files on Cheaha, please follow the instructions in the documentation for installation. Once it is installed, follow these instructions to set up the SSH config file. The following assumes SSH is installed locally, and that a config file exists in the usual location for your operating system. The commands assume you have an open Visual Studio Code window.\n\n# Open the command palette, default hotkey \"Ctrl + Shift + P\".\n# Locate \"Remote-SSH: Connect to Host...\" by typing part of the command at the prompt.\n#: [[File:Remote-editing-vscode-palette.png]]\n# Click the command in the palette prompt.\n# Click \"Configure SSH Hosts...\".\n#: [[File:Remote-editing-vscode-ssh-choices.png]]\n# Choose the location of the existing config file.\n#: [[File:Remote-editing-vscode-ssh-file.png]]\n# In the new editor window that opened, add the following lines then save the file.\n\n<pre>\nHost cheaha\n  HostName cheaha.rc.uab.edu\n  User <username>\n</pre>\n\nThe text <username> should be replaced by the user name you use to access Cheaha. The \"User\" line is not necessary but can save some time.\n\n=== Important Notes on Proper Usage ===\n\n<span style=\"background:#FF0000\">'''IMPORTANT!'''</span>\n\nThe Remote-SSH extension of Visual Studio Code runs on the login node! All subprocesses spawned by Visual Studio Code will also run on the login node by default. As always, we should avoid using computation-heavy processes on the login node. The Visual Studio Code limitation is knonw, and due to the way the extension server code is deployed to Cheaha. [https://github.com/microsoft/vscode-remote-release/issues/1722 Issue #1722] has been opened on the relevant GitHub repository. Please click the thumbs-up emoji on the first post there to increase visibility and priority of the issue.\n\nIt is possible to use the integrated terminal as normal with default hotkey \"Ctrl + `\" (backtick). This terminal behaves like the one on Open OnDemand, or other terminals, and can be used to start jobs as any other terminal.\n\n==== Things to Avoid ====\n\nTo minimize impact of remote development, avoid any of the following, or anything else that spawns a process. This is not a comprehensive list!\n* folders containing many files (>~1000 files)\n* folders containing large files (>100 MB or so)\n* debugging\n* accessing or running code within Jupyter notebooks.\n\n==== Working with Many or Large Files ====\n\nIf you must access a folder with many files or with large files, it is possible to have Visual Studio Code ignore those files or folders using a filter. Open \".vscode/settings.json\" in the open folder and add an object like the following (remember the comma following the previous key-value pair, if any). Each key with the value \"true\" is ignored by Visual Studio Code when indexing or searching files. The keys use typical glob syntax. In the example below the following are excluded:\n\n* any folder containing a subfolder \"datasets\" is ignored, along with all contained subfolders and files.\n* the folder \"ignore_children\" in the root folder along with all contained folders and files.\n* the folder \"node_modules\" in the root folder along with all contained files.\n* the file \"LARGE_DATA.sql\" in the root folder\n\n<pre>\n\"files.watcherExclude\": {\n    \"**/datasets/**/*\": true,\n    \"ignore_children/**/*\": true,\n    \"node_modules/*\": true,\n    \"LARGE_DATA.sql\": true\n}\n</pre>"
                    }
                ]
            },
            "1568": {
                "pageid": 1568,
                "ns": 0,
                "title": "Repository notes",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "{{ResearchNotebook}}\n\n==comparing software==\n* [http://blogs.lib.purdue.edu/rep/2010/02/25/a-comparative-analysis-of-institutional-repository-software/ Purdue analysis]\n* [https://wiki.library.jhu.edu/display/RepoAnalysis/ProjectRepository Johns-Hopkins analysis]\n* [http://www.rsp.ac.uk/software/surveyresults repositories support project]\n* [http://www.dlib.org/dlib/may09/marill/05marill.html NLM analysis]\n\n==ideas and examples of components==\n* policy\n** [http://conservancy.umn.edu/policies.jsp UMN repository] policy, very nice example for other sites\n** [http://www.arl.org/rtl/eresearch/escien/nsf/index.shtml NSF policy] via association of research librarians\n* Examples of submission instructions for online archives\n** http://www.archive.org/about/faqs.php#Uploading_Content\n** http://www.zotero.org/support/commons\n* Notebooks and protocols:\n** [http://openwetware.org/wiki/Main_Page openwetware]\n** [http://www.myexperiment.org/ myExperiment]\n** [http://www.fmrimethods.org/index.php/Main_Page Poldrack's fmri methods]\n* preprints:\n** [http://arxiv.org/ arXiv]\n** [http://precedings.nature.com/about nature precedings]\n* postprints:\n** [http://www.openarchives.org/ Open Archives Initiative ]\n* data archives and supplementary data and code supporting publications datasets:\n** see [[research data repositories]]\n* code:\n** [http://code.google.com/ google code]\n** [http://sourceforge.net/ sourceforge]\n* writing tools:\n** [http://owl.english.purdue.edu/ Purdue OWL]\n\n\n; potential infrastructure grant applications : [http://www.ncrr.nih.gov/research_infrastructure/funding.asp ncrr]\n:: [http://grants.nih.gov/grants/guide/pa-files/PAR-10-082.html PAR-10-082] ?\n:[http://www.nlm.nih.gov/ep/Grants.html#resource nlm]\n:nibib\n\n==dspace==\n;dspace user FAQ : https://wiki.duraspace.org/display/DSPACE/EndUserFaq\n;dspace \"how to\" guide : http://www.dspace.org/images/Training_Materials/dspacehowtoguide.pdf\n;the full documentation for 1.6.2 : http://www.dspace.org/1_6_2Documentation/\n;very nice manual for common tasks, kalamazoo dspace procedures manual : http://dspace.nitle.org/handle/10090/5747\n\nhow to [[get data into dspace]]"
                    }
                ]
            }
        }
    }
}