MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Releases_and_Patching",
        "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": {
            "414": {
                "pageid": 414,
                "ns": 0,
                "title": "Realising Good Control Over Output with Confluence",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "==Formatting General Output==\nIn the Space Admin area of Confluence go to the ''Scroll Wiki PDF Exporter: Template''\n* ''Name'' Must be unique\n* ''Page Layout''\n** ''Different first page''\n** ''Different even and odd pages''\n** Straightforward editing of page size, margins, padding, header and footer\n*** Margins are defined by\n**** (4) Top, Right, Bottom then Left\n**** (2) Top and bottom or\n**** (1) All\n*** Padding is defined by\n**** (4) Top, Right, Bottom then Left\n**** (2) Top and bottom, then Sides (right and left) or\n**** (1) All\n* ''Static Pages''\n** ''Title Page'' Allows you to edit content using HTML tags. (e.g. inserting <img src=\"openpetra_logo_final_white_text.png\"/>)\n* ''Content Formatting'' Allows editing of the overall CSS applied to the PDF export, e.g. to center text and images on the title page and make all chapters begin on the right side of the page:\n <nowiki>\n.titlepage {\n  text-align: center;\n}\n\nh1.heading {\n    page-break-before: right;\n}</nowiki>\n: Use this area to modify what tables look like when exported, if not using the table macro [[#Tables|see below]]\n: Other style sheeting explanations found in the [http://www.k15t.com/display/PDF/Content+Formatting Scroll Wiki Documentation]\n: [http://www.k15t.com/download/attachments/21430295/common-contentstyle.css?version=1&modificationDate=1316422055000 Example Default Style Sheet]\n* ''Fonts'' Presumably upload custom fonts if referenced in CSS file\n* ''Resources'' Needs upload of image files included in Static Pages\n\n==Formatting Specific Content==\n===Highlighting of Sections===\nConfluence macros that have predefined tags associated with them that show up nicely in PDF export (able to be manipulated with Style Sheets following DocBook export)\n* Info\n* Note\n* Tip\n* Warning\n* Panel (possible to use, for just a box around text)\n\n===Hyperlinks===\nUse Scroll Wiki PDF export Linking options so that you can:\n* Add page numbers to internal links\n* Add URL to external links, and\n* Disable links to this Confluence system (which keeps non-exported page links from being converted to absolute links)\n'''Do NOT use monospacing on the text you are using as a link''' the link will not be exported, and the monospaced text will be smashed up against itself.\n\n===Tables===\nThere are also multiple ways to make tables:\n* The Table insert drop-down, inserts a table (with the ability to highlight rows or columns using the built-in editing GUI)\n* Wiki-markup, e.g.\n <nowiki>\n||table heading||more table heading||\n|table cell|another cell|\n|another|and another|</nowiki>\n: produces:\n{| class=\"wikitable\" border=\"1\"\n|-\n! table heading\n! more table heading\n|-\n| table cell\n| another cell\n|-\n| another\n| and another\n|}\n* Using the [https://www.adaptavist.com/display/AtlassianConfluence/table+macro table macro], use syntax similar to HTML (see website for example)\n** This gives us the ability to remove borders by setting the border=0 or using the \"frame\" and \"rules\" options.\n** It seems like the \"class\" parameter could be used to set a particular table to a specific CSS class, that could then be defined itself as having particular borders, or not through the style sheet instead of modifying the style sheet for all normally inserted tables to give them no lines or something.\n\n===Images===\n====Importing====\nAttachments option from edit screen allows particular pages to have specific images and keeps track of all images ever included on that page. (You can use it to upload an image then insert it in the page with wiki-markup.)\n\nTo insert an image choose one of the following:\n* Use Insert > Image (will make the title and name of the image its uploaded file-name)\n* Use wiki-markup (e.g. <code>!example.gif!</code> so that the name of the image is not used as a caption when exporting\n====Exporting====\nThe default Insert > Image option of adding an image to a page makes file-name of the image show up as a caption below the image when it is exported (including the file-extension of .gif, .png, .jpg, etc.)\n\nTo remedy this, use wiki-markup when inserting an image and include <code>|title=\"\"</code> so it looks like <code>!example.gif|title=\"\"!</code>\n\n===Drop-down Expandable Text===\nCheck to see if this is something that might work when exported to DocBook, because it is automatically expanded in PDF and looks very ugly. Is there a way to find out what tag is being used here?\n\n===CSS Classes===\nUse the [https://www.adaptavist.com/display/AtlassianConfluence/div+macro div macro] and [https://www.adaptavist.com/display/AtlassianConfluence/span+macro span macro] to define content as particular class for use with CSS.\n\nThis can also be used for the button effect when exporting to DocBook, not sure about PDF, but presumably if we find the right way to reference it in the right CSS document."
                    }
                ]
            },
            "328": {
                "pageid": 328,
                "ns": 0,
                "title": "Reallocation Tests",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "=== The Test Idea ===\n\nThe idea of the test is of getting test data by some test accountings in petra. \n\nLet us assume the following situation as the sum of the accountings of a year. Here we only have the following account codes\n\n# The account code for the bank = 6200\n# The account code for the gift = 0200\n# The account code for the expense 4100\n\nAnd the following cost centres:\n\n# 4300 (=Standard CC for ledger 43)\n# 4301\n# 4302\n# 4303\n\nThen we account some gifts: (Notatation is Cost centre code: account code and the direction is credit account to debit account. \n\n# 4301:0200 -> 4301:6200 - 100 Euro\n# 4302:0200 -> 4302:6200 - 200 Euro\n# 4303:0200 -> 4303:6200 - 300 Euro\n\nand some expenses:\n\n# 4301:6200 -> 4301:4100 - 150 Euro\n# 4302:6200 -> 4302:4100 - 150 Euro\n# 4303:6200 -> 4303:4100 - 200 Euro\n\n\n=== Reference data from Petra ===\n\n\n==== GLM-Screenshoots before the Reallocation is done ====\n\nIn petra I've the ledger 37 \"UK National Office\" and in open Petra I've 47 - \"German\". So I've to chose an other account numer for 0200 and the best choice is 0900. Furthermore in petra the glm-table hold more data than in open petra. So in petra we have three filtered screenshoots. \n\n[[File:Reallocation-petra-0900-before.JPG]]\n\n[[File:Reallocation-petra-4100-before.JPG]]\n\n[[File:Reallocation-petra-6200-before.JPG]]\n\nAnd in Openpetra we have one screen shoot. \n\n[[File:Reallocation-before.JPG]]\n\n==== GLM-Screenshoots after the Reallocation is done ====\n\n[[File:Reallocation-petra-0900-after.JPG]]\n\n[[File:Reallocation-petra-4100-after.JPG]]\n\n[[File:Reallocation-petra-6200-after.JPG]]\n\nThe account 9700 hold some other petra test results too. The correct value is 100. \n\n[[File:Reallocation-petra-9700-after.JPG]]\n\n==== Informal Comments on the test results ====\n\nInside the petra routines there are two main routine parts, the reallocation and the close-glm-routine. The petra screenshoot shows the result of both operation(s) and the openpetra screenshoots only shows the reallocation part. Actually I've used the TCommonAccountingTool either to create the test data accountings (code followed) and to create the reallocation accountings which is a little bit more complex. \n\nTCommonAccountingTool is a system which directly acts to the web connector routines SaveGLbatchtTDS and PostGLBatch and this only in the last command \"CloseSaveAndPost\" but without using the webconnector routines directly to avoid RequireModulePermission conflicts. \n\n<pre>TCommonAccountingTool commonAccountingTool =\n  new TCommonAccountingTool(intLedgerNumber, \"NUNIT\");\ncommonAccountingTool.AddBaseCurrencyJournal();\ncommonAccountingTool.JournalDescription = \"Test Data accounts\";\nstring strAccountGift = \"0200\";\nstring strAccountBank = \"6200\";\nstring strAccountExpense = \"4100\";\n\n// Accounting of some gifts ...\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountBank, \"4301\", \"Gift Example\", \"Debit\", CommonAccountingConstants.IS_DEBIT, 100);\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountBank, \"4302\", \"Gift Example\", \"Debit\", CommonAccountingConstants.IS_DEBIT, 200);\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountBank, \"4303\", \"Gift Example\", \"Debit\", CommonAccountingConstants.IS_DEBIT, 300);\n\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountGift, \"4301\", \"Gift Example\", \"Credit\", CommonAccountingConstants.IS_CREDIT, 100);\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountGift, \"4302\", \"Gift Example\", \"Credit\", CommonAccountingConstants.IS_CREDIT, 200);\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountGift, \"4303\", \"Gift Example\", \"Credit\", CommonAccountingConstants.IS_CREDIT, 300);\n\n\n// Accounting of some expenses ...\n\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountExpense, \"4301\", \"Expense Example\", \"Debit\", CommonAccountingConstants.IS_DEBIT, 150);\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountExpense, \"4302\", \"Expense Example\", \"Debit\", CommonAccountingConstants.IS_DEBIT, 150);\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountExpense, \"4303\", \"Expense Example\", \"Debit\", CommonAccountingConstants.IS_DEBIT, 200);\n\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountBank, \"4301\", \"Expense Example\", \"Credit\", CommonAccountingConstants.IS_CREDIT, 150);\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountBank, \"4302\", \"Expense Example\", \"Credit\", CommonAccountingConstants.IS_CREDIT, 150);\ncommonAccountingTool.AddBaseCurrencyTransaction(\n  strAccountBank, \"4303\", \"Expense Example\", \"Credit\", CommonAccountingConstants.IS_CREDIT, 200);\n\ncommonAccountingTool.CloseSaveAndPost();</pre>\n\n==== Formal Test Rules ====\n\nSo let us define the following reallocation rules\n\n# a_ledger_number_i and a_year_i are fixed values. \n# For each pair of a_account_code_c and a_cost_centre_code_c a new glm-record shall be created. \n# If the account is of the type Income or Expense, the a_ytd_actual_base_n of both glm records are 0 and a_closing_period_actual_base_n of the ealier year holds the last value. \n# The glm-record of a bank account - account of the type Assert - only shall be copied\n# The example has used 9700 a fund balance account. This account - type equity - is used to account against it all accounts of type income and expense.\n\n=== Test cases ===\n\nAnd now you can compare to the results in openpetra\n\na) after a reallocation\n\n[[File:Reallocation-after.JPG]]\n\nb) after an additional move of the glm-info into the next year has been done\n\n[[File:Glm-new-year-after.JPG]]\n\nThe first operation is only used for accounts of type income and expense and the glm-move shall be used for all accounts."
                    }
                ]
            }
        }
    }
}