MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Steering_Committee",
        "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": {
            "1537": {
                "pageid": 1537,
                "ns": 0,
                "title": "Stage content for ingest",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "To preserve digital content in ADPNet, the content must be [[Stage content for ingest|staged for ingest]]. That means making it available on a web server. The staged content should be accessible to ADPNet [[preservation node]]s; it does ''not'' need to be available to the public web. ''Staging content'' for ADPNet servers to [[harvest]] is the method by which content is ingested into the digital preservation network.\n\n== Procedure ==\n'''''This section is now obsolete (as of April 2022). ADAH uses, and ADPNet strongly recommends, the use of the ADPNet [[Drop Server]] for staging content for preservation. This server is available to all network members. Documentation should be updated soon.'''''\n\nThe best way to stage content currently depends on the details of your local web server setup. Here's how we do it at the [http://archives.alabama.gov/ Alabama Department of Archives and History] as of June 2019:\n\n1. We have a public web server, [http://archives.alabama.gov/ archives.alabama.gov]. There is a subdirectory provided by this web server at [http://archives.alabama.gov/Lockss/ http://archives.alabama.gov/Lockss/] which is set up to be visible only to the IP addresses of LOCKSS preservation nodes on ADPNet. Anyone else who browses to that subdirectory will see an HTTP 403 Forbidden error. (We used IIS's access rules to set up limited access to this directory. If you need help setting up a limited-access subdirectory on your own web server, contact the [[Technical Policy Committee]] for assistance.\n\n2. New content is staged as a subdirectory uploaded to [http://archives.alabama.gov/Lockss/ http://archives.alabama.gov/Lockss/] . We use FTP to create a new subdirectory on the web server, for example [http://archives.alabama.gov/Lockss/WPA-Folder-01 http://archives.alabama.gov/Lockss/WPA-Folder-01], and then transfer preservation copies of all of the content for that Archival Unit to the subdirectory. Files can be any format and can have any name, as long as none of them is called index, index.html, or any other file name with \"index\" before the extension (for example: don't use this technique to stage a file named index.php, index.htm, index.asp, index.cfm, ...).\n\n3. Next, we upload a [[manifest file]] named manifestpage.html to the same subdirectory, which includes a permissions statement and a link to the directory listing (for example [http://archives.alabama.gov/Lockss/WPA-Folder-01 http://archives.alabama.gov/Lockss/WPA-Folder-01]).\n\n4. Once the manifest file is uploaded and the AU is accessible through the web server, the content is now considered staged for ingest.\n\n\n== See also ==\n[[Local Content Staging (ADPNet Model.docx)]]"
                    }
                ]
            },
            "1577": {
                "pageid": 1577,
                "ns": 0,
                "title": "Stage new or updated content for digital preservation",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "'''''You've got:''''' A set of digital files that you want preserved in the [[LOCKSS network]]. You have checked the content to make sure that they are [[appropriate for semi-private preservation]] in LOCKSS. You have exported, copied, or packaged in a location where you are ready to transmit them over the network. These files may be either a new unit of content to preserve, or they may be an update to an existing unit.\n\n'''''Now you need:''''' To '''STAGE''' the content in a secure and convenient location for the ADPNet [[preservation node]]s to [[harvest]] a preservation copy of the content. In ''almost all'' cases, the staging area that you will use is the [[ADPNet drop server]], <code>drop.adpn.org</code>. To stage new or updated content on the drop server, you will upload it to your institution's space on the server using common SFTP file-upload tools like [https://winscp.net/ WinSCP]. \n\n: ''In very unusual cases, the LOCKSS network is also capable of harvesting content that you stage using a special area of a web server, or a web service, that you (i.e., your [[Member (ADPNet)|Member]] institution) runs. If you think it might be the best option, contact the [[TPC]] to explain the situation.''\n\n'''''So here's what you do:'''''\n\n* If you haven't done this before, contact the [[TPC]] to [[HOWTO: Request a staging area on the Drop Server|request a staging area on the drop server for your institution]].\n\n* Once you have your staging area set up to accept new content: [[HOWTO: Package files for staging on the Drop Server|package your files for staging on the drop server]].\n\n* Once your files are packaged into an AU and are ready to be considered as an [[Archival Unit]] (AU) by the LOCKSS daemon: upload your files to the staging area.\n** Use WinSCP (or any other SFTP tool that you like) to upload the whole packaged-up directory to <code>drop.adpn.org</code>, storing it under the <code>drop_au_content_in_here</code> subdirectory of your staging area.\n** If this is a '''NEW''' AU -- a new series of digital content, or a new, discrete addition to an existing series -- make sure that your AU's directory name is ''unique''. If the AU is one part of an ongoing series, you may want to use serial numbers to distinguish them.\n*** For example, say you have a series of AUs called '''\"Digitization Masters Files.\"''' Each AU contains new content in new files, representing the new digital masters files produced over time by your digitization project. To preserve a new AU in this series, you might stage it with a name like <code>Digitization-Masters-File-01305</code>, where <code>01305</code> is a serial number that uniquely identifies this AU and distinguishes it from the earlier and later AUs in the same series.\n** If this is an '''UPDATE''' to an existing AU make sure that your AU's directory name is ''identical'' to the name that you used previously when you ingested the older version of the content, which this version replaces.\n*** For example, say you have a set of database files called '''\"Transcription Metadata\"''' which stores Microsoft Access relational database files containing data tables that record the meta-data entered by staff or volunteers during an ongoing transcription project. The `.accdb` files representing the content of the database persist as a single unit, but over time new records are added to the tables contained in them, which should be reflected in their preservation copy. When you first staged this content, you staged it with a name like <code>Transcription-Metadata-Database</code>. To stage an ''update'' to the content in that AU, you would now stage it under the identical name, <code>Transcription-Metadata-Database</code>, to signal to LOCKSS preservation nodes that this is an updated version of the same AU.\n\n* Notify ADPNet TPC to let us know you\u2019re ready to go ahead with the ingest."
                    }
                ]
            }
        }
    }
}