MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Resources",
        "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": {
            "27": {
                "pageid": 27,
                "ns": 0,
                "title": "Recombac",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "\n\n=== A library of BAC-GFP reporter recombinants for gene network analysis ===\n\nIn order to identify the cis-regulatory modules that control gene expression during development, we have undertaken the construction of BAC GFP recombinants that contain the intact upstream, downstream and intronic genomic DNA surrounding a particular gene, e.g. the complete cis-regulatory system. These reporters are able to recapitulate the endogenous gene expression with temporal and spatial specificity when microinjected into fertilized sea urchin eggs. We use homologous recombination to target a cassette containing the GFP coding sequence to the start of transcription. A short description of the method is posted here. The references from which these methods derive are listed below.\n\nFrom BAC libraries at the Sea Urchin Genome Resource, recombinants have been constructed from four sea urchins, S. purparatus, S. fransciscanus, L variegatus and A. punctulata as well as the sea star A. miniata. Since the Davidson Laboratory is interested in the regulatory domains that control expression of transcription factors and signaling molecules involved in endomesoderm specification, we have first prepared recombinants for several genes that operate in that gene regulatory network, including the transcription factors Bra, Eve, FoxA, GataC, GataE, GCM, Tbr and Krox, as well as differentiation genes endo16 and sm50 and signaling genes Delta and Wnt8 [[BAC_Table|(see Table)]]. For many of these the expression patterns have been verified against their endogenous counterparts.\n\nThese BAC clones are available by request. We will also entertain requests to make additional constructs as time permits. For new preparations, you will need to find the BAC by computer or by screening our libraries. In order to prepare a new recombinant BAC we will need the ID of the BAC clone from our libraries, the sequence of the gene it contains and evidence that you know the position of the gene in the BAC. Please inquire of those below if you have questions. This is a bit complicated to explain here.\n\n[mailto:wlijun@caltech.edu Lijun Wang]<br />\n[mailto:acameron@caltech.edu Dr. Andy Cameron]\n\n'''References'''\n\nYu D, Ellis HM, Lee EC, Jenkins NA, Copeland NG, Court DL. 2000. An efficient recombination system for chromosome engineering in Escherichia coli. Proc Natl Acad Sci U S A. 97:5978-83.\n\nE-Chiang Lee, Daiguan Yu, J. Martinez de Velasco, Lino Tessarollo, Deborah A. Swing, Donald L. Court, Nancy A. Jenkins, and Neal G. Copeland. 2001. A Highly Efficient Escherichia coli-Based Chromosome Engineering System Adapted for Recombinogenic Targeting and Subcloning of BAC DNA. Genomics 73, 56-65."
                    }
                ]
            },
            "101": {
                "pageid": 101,
                "ns": 0,
                "title": "Reporting bugs",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "=Reporting a bug in Echinobase=\nIf you find a bug in Echinobase, we would really like to know!\nHowever, it is very important that we can find your bug so that we can fix it. \n\n'''To help us find your bug, please fill out form below, and e-mail it to us at [mailto:echinobase@andrew.cmu.edu  echinobase@andrew.cmu.edu].'''\n<div class=\"toccolours mw-collapsible mw-collapsed\">\nEchinobase Bug Report\n<div class=\"mw-collapsible-content\">Date of bug- MM/DD/YYYY\napproximate time at which the bug occurred: HH:MM:SS\n\nReporter:[your name]\nURL at which the bug occurred:[Give the urls from the pages where you first felt that something was wrong]\n\n1. What is the problem?\n[A brief, one sentence explanation of the bug]\n\n2. What were you trying to do?\n[A brief explanation of what you were trying to do when the bug occurred]\n\n3. Please give a step-by-step summary of the actions you took from the time you decided to perform the action in question 2 to the time you experienced the bug in question 1. If you were searching for something or changing the properties of something (i.e. changing a user's address), please include the exact text you entered (as far as you can remember).\n\n4. On a scale of 1 to 6, how will this bug impact your ability to use the website? [Put your answer HERE]\n[1= not at all] \n[4= Working around this bug requires significant changes in how I use Echinobase]\n[6= While this bug exists, I cannot use Echinobase to do what I need to do]</div>\n</div>\n\nBelow you can find an example pre-filled bug report.\n<div class=\"toccolours mw-collapsible mw-collapsed\">\nEchinobase Bug Report\n<div class=\"mw-collapsible-content\">\nDate of bug- 04/11/2020\napproximate time at which the bug occurred: 15:34:29\n\nReporter:John Smith\nURL at which the bug occurred:http://www.echinobase.org/gene/searchGene.do?method=search&searchIn=0&searchValue=XPax-8&searchType=0\n\n1. What is the problem?\nI cannot search for genes with synonyms.\n\n2. What were you trying to do?\nI was trying to search for \"pax2\" with its synonym, \"EPax-2\"\n\n3. Please give a step-by-step summary of the actions you took from the time you decided to perform the action in question 2 to the time you experienced the bug in question 1.If you were searching for something or changing the properties of something (i.e. changing a user's address), please include the exact text you entered (as far as you can remember).\n \n 1. I started at www.echinobase.org.\n 2. I entered \"EPax-2\" in the search box.\n 3. I received no results.\n \n4. On a scale of 1 to 6, how will this bug impact your ability to use the website? 4\n\n[1= not at all] \n[4= Working around this bug requires significant changes in how I use Echinobase]\n[6= While this bug exists, I cannot use Echinobase to do what I need to do]\n\n\n</div>\n</div>\n\n\n\nAn explanation of how to fill out each of the fields and why they are helpful, is below.\n\n==Date and Time==\nThese fields are necessary when someone reports a bug that we cannot find the cause of. We can check Echinobase's error logs at that date and time to see if any errors occurred which might tell us more about the bug. \n\nThe seconds of the time field need only be approximations. \n\n== 1. What is the Problem?==\nPlease provide a very short (1-2 sentence) summary of the problem.\n\n== 2. What were you trying to do?==\nThis field gives us some context as to what you were attempting to do. It helps us determine which page you were on and pages you were likely to have been on before that. \n\n== 3. Step-by-step Summary==\nWrite out, as well as you can remember, each and every step you took from the moment you decided to do the action in number 2 to the moment the bug from number 1 occurred.\n\n===Why is this summary important?===\nSome bugs may be crucial to Echinobase running correctly, but may only occur after a user has performed a very specific sequence of steps. The more specific you are about the steps you took (exactly which search box you used, where you reached an image edit page from, etc.)the easier it will be for us to isolate your bug.\n\nAn extreme example (unrelated to Echinobase) of how specific a bug report may need to be in order to isolate a bug can be found [http://computingcases.org/case_materials/therac/supporting_docs/therac_resources/produce_malfuction_54.html here]. Each and every step from that bug report would need to be performed correctly in order to generate that bug.\n\nThat being said, we understand your time is valuable and very few bugs actually require a report in the above level of detail. Just tell us which buttons you pushed and which pages you navigated to and if we need more information, we will e-mail you. :-)\n\n==4. The Scale From 1 to 6==\nUnfortunately we cannot get to every bug as soon as it is submitted. Some bugs need to wait in our bug queue before we can fix them. To help us prioritize the ordering of these bugs in the queue, we would like to know how inconvenient these bugs are for you. The scale is summarized in the bug report above; however, a more detailed scale summary can be found below.\n\n#= The problem does not affect my ability to use the website.\n#= I can easily work around the problem.\n#= I can work around the problem.\n#= I can work around the problem with some difficulty.\n#= It is very difficult to work around the problem.\n#= I cannot work around the problem.\n\n----"
                    }
                ]
            }
        }
    }
}