Difference between revisions of "Team:DTU-Denmark/Software"

 
(2 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
     <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
 
     <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
 
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
 
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
   
 
   
 
    <link href="/Team:DTU-Denmark/loadphpcss?action=raw&ctype=text/css" rel="stylesheet">
 
    <link href="/Team:DTU-Denmark/bootstrapcss?action=raw&ctype=text/css" rel="stylesheet">
 
    <link href="/Team:DTU-Denmark/font-awesomecss?action=raw&ctype=text/css" rel="stylesheet">
 
    <link href="/Team:DTU-Denmark/wikicss?action=raw&ctype=text/css" rel="stylesheet">
 
    <link href="/Team:DTU-Denmark/timelinecss?action=raw&ctype=text/css" rel="stylesheet">
 
    <link href="/Team:DTU-Denmark/menufixcss?action=raw&ctype=text/css" rel="stylesheet">
 
  
   
+
      <link rel=stylesheet href="/Team:DTU-Denmark/loadphpcss?action=raw&ctype=text/css">
 +
      <link rel=stylesheet href="/Team:DTU-Denmark/bootstrapcss?action=raw&ctype=text/css">
 +
      <link rel=stylesheet href="/Team:DTU-Denmark/font-awesomecss?action=raw&ctype=text/css">
 +
      <link rel=stylesheet href="/Team:DTU-Denmark/wikicss?action=raw&ctype=text/css">
 +
      <link rel=stylesheet href="/Team:DTU-Denmark/timelinecss?action=raw&ctype=text/css">
 +
      <link rel=stylesheet href="/Team:DTU-Denmark/menufixcss?action=raw&ctype=text/css">
 +
 
 
     <script type="text/javascript" src="/Team:DTU-Denmark/jqueryjs?action=raw&ctype=text/javascript"></script>
 
     <script type="text/javascript" src="/Team:DTU-Denmark/jqueryjs?action=raw&ctype=text/javascript"></script>
 
     <script type="text/javascript" src="/Team:DTU-Denmark/bootstrapjs?action=raw&ctype=text/javascript"></script>
 
     <script type="text/javascript" src="/Team:DTU-Denmark/bootstrapjs?action=raw&ctype=text/javascript"></script>
 
     <script type="text/javascript" src="/Team:DTU-Denmark/jqueryeasingjs?action=raw&ctype=text/javascript"></script>
 
     <script type="text/javascript" src="/Team:DTU-Denmark/jqueryeasingjs?action=raw&ctype=text/javascript"></script>
 
     <script type="text/javascript" src="/Team:DTU-Denmark/wikijs?action=raw&ctype=text/javascript"></script>
 
     <script type="text/javascript" src="/Team:DTU-Denmark/wikijs?action=raw&ctype=text/javascript"></script>
 +
 
     <!-- MathJax (LaTeX for the web) -->
 
     <!-- MathJax (LaTeX for the web) -->
 
     <script src="https://2015.igem.org/common/MathJax-2.5-latest/MathJax.js?config=TeX-AMS-MML_SVG"></script>
 
     <script src="https://2015.igem.org/common/MathJax-2.5-latest/MathJax.js?config=TeX-AMS-MML_SVG"></script>
    <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
 
    <!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
 
    <!--[if lt IE 9]>
 
      <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
 
      <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
 
    <![endif]-->
 
 
      
 
      
 
   </head>
 
   </head>
Line 44: Line 37:
 
             <i class="fa fa-bars"></i>
 
             <i class="fa fa-bars"></i>
 
           </button>
 
           </button>
           <a class="navbar-brand navimg" href="#"><img src="/wiki/images/b/b7/DTU-Denmark_dtulogo.png"></a>
+
           <a class="navbar-brand navimg" href="#"><img src="https://static.igem.org/mediawiki/2015/b/b7/DTU-Denmark_dtulogo.png"></a>
 
         </div>
 
         </div>
 
         <!-- Collect the nav links, forms, and other content for toggling -->
 
         <!-- Collect the nav links, forms, and other content for toggling -->
 
         <div class="collapse navbar-collapse" id="nav-collapse">
 
         <div class="collapse navbar-collapse" id="nav-collapse">
 
           <ul class="nav navbar-nav">
 
           <ul class="nav navbar-nav">
<li >
+
                <li >
<a href="/Team:DTU-Denmark"
+
                <a href="/Team:DTU-Denmark"
  >Home
+
                  >Home
                                          </a></li>
+
                  </a></li>
<li  
+
                <li  
+
               
 
                      
 
                      
                 
+
               
 
                      
 
                      
                 
+
               
  >
+
                >
<a href=""
+
                <a href=""
  class="dropdown-toggle"
+
                  class="dropdown-toggle"
  data-toggle="dropdown"
+
                  data-toggle="dropdown"
  role="button"
+
                  role="button"
  aria-expanded="false">Team and Attributions
+
                  aria-expanded="false">Team and Attributions
                                          <span class="caret"></span></a><ul class="dropdown-menu" role="menu">
+
                  <span class="caret"></span></a><ul class="dropdown-menu" role="menu">
<li >
+
                <li >
<a href="/Team:DTU-Denmark/Team"
+
                <a href="/Team:DTU-Denmark/Team"
  >Team
+
                  >Team
                                          </a></li>
+
                  </a></li>
<li >
+
                <li >
<a href="/Team:DTU-Denmark/Attributions"
+
                <a href="/Team:DTU-Denmark/Attributions"
  >Attributions
+
                  >Attributions
                                          </a></li></ul></li>
+
                  </a></li></ul></li>
<li  
+
                <li  
+
               
 
                      
 
                      
                 
+
               
 
                      
 
                      
                 
+
               
 
                      
 
                      
                 
+
               
 
                      
 
                      
                 
+
               
 
                      
 
                      
                 
+
               
 
                      
 
                      
                 
+
               
 
                      
 
                      
                 
+
               
 +
                >
 +
                <a href=""
 +
                  class="dropdown-toggle"
 +
                  data-toggle="dropdown"
 +
                  role="button"
 +
                  aria-expanded="false">Project
 +
                  <span class="caret"></span></a><ul class="dropdown-menu" role="menu">
 +
                <li >
 +
                <a href="/Team:DTU-Denmark/Project/Overview"
 +
                  >Overview
 +
                  </a></li>
 +
                <li >
 +
                <a href="/Team:DTU-Denmark/Project/Background"
 +
                  >Background
 +
                  </a></li>
 +
                <li >
 +
                <a href="/Team:DTU-Denmark/Project/MAGE"
 +
                  >MAGE subtilis
 +
                  </a></li>
 +
                <li >
 +
                <a href="/Team:DTU-Denmark/Project/Tyrocidine"
 +
                  >Tyrocidine
 +
                  </a></li>
 +
                <li >
 +
                <a href="/Team:DTU-Denmark/Project/Chip"
 +
                  >Lab-on-a-disc
 +
                  </a></li>
 +
                <li >
 +
                <a href="/Team:DTU-Denmark/Project/Inteins"
 +
                  >Inteins
 +
                  </a></li>
 +
                <li >
 +
                <a href="/Team:DTU-Denmark/Project/Detection"
 +
                  >Detection of NRP
 +
                  </a></li></ul></li>
 +
                <li >
 +
                <a href="/Team:DTU-Denmark/Practices"
 +
                  >Human Practices
 +
                  </a></li>
 +
                <li
 +
               
 
                      
 
                      
                 
+
               
 
                      
 
                      
                 
+
               
  >
+
                >
<a href=""
+
                <a href=""
  class="dropdown-toggle"
+
                  class="dropdown-toggle"
  data-toggle="dropdown"
+
                  data-toggle="dropdown"
  role="button"
+
                  role="button"
  aria-expanded="false">Project
+
                  aria-expanded="false">Parts Collection
                                          <span class="caret"></span></a><ul class="dropdown-menu" role="menu">
+
                  <span class="caret"></span></a><ul class="dropdown-menu" role="menu">
<li >
+
                <li >
<a href="/Team:DTU-Denmark/Project/Overview"
+
                <a href="/Team:DTU-Denmark/Parts"
  >Overview
+
                  >Parts
                                          </a></li>
+
                  </a></li>
<li >
+
                <li >
<a href="/Team:DTU-Denmark/Project/Background"
+
                <a href="/Team:DTU-Denmark/Description"
  >Background
+
                  >Characterisation of xylR
                                          </a></li>
+
                  </a></li></ul></li>
<li >
+
                <li >
<a href="/Team:DTU-Denmark/Project/MAGE"
+
                <a href="/Team:DTU-Denmark/Journal"
  >MAGE Subtilis
+
                  >Journal
                                          </a></li>
+
                  </a></li>
<li >
+
                <li class="active">
<a href="/Team:DTU-Denmark/Project/Surfactin"
+
                <a href="/Team:DTU-Denmark/Software"
  >Surfactin
+
                  >Software
                                          </a></li>
+
                  </a></li>
<li >
+
                <li  
<a href="/Team:DTU-Denmark/Project/Tyrocidine"
+
               
  >Tyrocidine
+
                                          </a></li>
+
<li >
+
<a href="/Team:DTU-Denmark/Project/Chip"
+
  >Lab-on-a-disc
+
                                          </a></li>
+
<li >
+
<a href="/Team:DTU-Denmark/Project/Intein"
+
  >Inteins
+
                                          </a></li>
+
<li >
+
<a href="/Team:DTU-Denmark/Project/Detection"
+
  >Detection of NRP
+
                                          </a></li>
+
<li >
+
<a href="/Team:DTU-Denmark/Project/POC_MAGE"
+
  >Proof of concept of MAGE in B. subtilis
+
                                          </a></li></ul></li>
+
<li >
+
<a href="/Team:DTU-Denmark/Practices"
+
  >Human Practices
+
                                          </a></li>
+
<li  
+
+
 
                      
 
                      
                 
+
               
 
                      
 
                      
                 
+
               
  >
+
<a href=""
+
  class="dropdown-toggle"
+
  data-toggle="dropdown"
+
  role="button"
+
  aria-expanded="false">Partss
+
                                          <span class="caret"></span></a><ul class="dropdown-menu" role="menu">
+
<li >
+
<a href="/Team:DTU-Denmark/Parts"
+
  >Parts
+
                                          </a></li>
+
<li >
+
<a href="/Team:DTU-Denmark/Description"
+
  >Characterization of xylR
+
                                          </a></li></ul></li>
+
<li >
+
<a href="/Team:DTU-Denmark/Journal"
+
  >Journal
+
                                          </a></li>
+
<li class="active">
+
<a href="/Team:DTU-Denmark/Software"
+
  >Software
+
                                          </a></li>
+
<li
+
+
 
                      
 
                      
                 
+
               
                   
+
                >
                 
+
                <a href=""
                   
+
                  class="dropdown-toggle"
                 
+
                  data-toggle="dropdown"
  >
+
                  role="button"
<a href=""
+
                  aria-expanded="false">Achievements
  class="dropdown-toggle"
+
                  <span class="caret"></span></a><ul class="dropdown-menu" role="menu">
  data-toggle="dropdown"
+
                <li >
  role="button"
+
                <a href="/Team:DTU-Denmark/Achievements"
  aria-expanded="false">Achievements
+
                  >Key Achievements
                                          <span class="caret"></span></a><ul class="dropdown-menu" role="menu">
+
                  </a></li>
<li >
+
                <li >
<a href="/Team:DTU-Denmark/Achievements"
+
                <a href="/Team:DTU-Denmark/Collaborations"
  >Overview of Achievements
+
                  >Collaborations
                                          </a></li>
+
                  </a></li>
<li >
+
                <li >
<a href="/Team:DTU-Denmark/Collaborations"
+
                <a href="/Team:DTU-Denmark/Judging_Form"
  >Collaborations
+
                  >Judging Form
                                          </a></li>
+
                  </a></li></ul></li>
<li >
+
<a href="/Team:DTU-Denmark/Judging%20Form"
+
  >Judging Form
+
                                          </a></li></ul></li>
+
 
             <li class="hidden-xs">
 
             <li class="hidden-xs">
 
               <a href="http://facebook.com/dtubiobuilders" data-toggle="tooltip" data-placement="bottom" title="Follow us on Facebook">
 
               <a href="http://facebook.com/dtubiobuilders" data-toggle="tooltip" data-placement="bottom" title="Follow us on Facebook">
Line 211: Line 192:
 
             <li class="hidden-lg">
 
             <li class="hidden-lg">
 
               <a href="https://igem.org" target="_blank" class="navimg">
 
               <a href="https://igem.org" target="_blank" class="navimg">
                 <img src="/wiki/images/a/af/DTU-Denmark_igemlogo.png">
+
                 <img src="https://static.igem.org/mediawiki/2015/a/af/DTU-Denmark_igemlogo.png">
 
               </a>
 
               </a>
 
             </li>
 
             </li>
Line 218: Line 199:
 
       </div>
 
       </div>
 
     </nav>
 
     </nav>
    <nav class="navbar navbar-default extrabar hidden-xs hidden" data-spy="affix">
+
 
      <div class="container-fluid" id="scrollspy">
+
 
        <ul class="nav navbar-nav">
+
<nav class="navbar navbar-default extrabar hidden-xs hidden" data-spy="affix">
          <li><a class="page-scroll" href="#The-Wiki-Wizard">The Wiki Wizard</a></li><li><a class="page-scroll" href="#NOD-Nrps-Oligo-Designer">NOD Nrps Oligo Designer</a></li>
+
  <div class="container-fluid" id="scrollspy">
        </ul>
+
    <ul class="nav navbar-nav">
      </div>
+
      <li><a class="page-scroll" href="#TheWikiWizard">The Wiki Wizard</a></li><li><a class="page-scroll" href="#NODNrpsOligoDesigner">NOD Nrps Oligo Designer</a></li>
    </nav>
+
    </ul>
    <div class="jumbotron hero bg-hero">
+
  </div>
 +
</nav>
 +
 
 +
 
 +
<div class="jumbotron hero" style="background-image: url(https://static.igem.org/mediawiki/2015/0/0b/DTU-Denmark_hero.jpg)">
 
       <div class="igem-logo visible-lg">
 
       <div class="igem-logo visible-lg">
 
         <a href="https://igem.org" target="_blank">
 
         <a href="https://igem.org" target="_blank">
           <img src="/wiki/images/a/af/DTU-Denmark_igemlogo.png">
+
           <img src="https://static.igem.org/mediawiki/2015/a/af/DTU-Denmark_igemlogo.png">
 
         </a>
 
         </a>
 
       </div>
 
       </div>
Line 235: Line 220:
 
           <div class="col-md-12">
 
           <div class="col-md-12">
 
              
 
              
            <h3><br></h3>
+
<h3><br></h3>
            <h1>Software</h1>
+
<h1>Software</h1>
           
+
 
 
             <hr/>
 
             <hr/>
 +
           
 +
           
 
             <ul class="list-inline hidden-xs hidden-sm">
 
             <ul class="list-inline hidden-xs hidden-sm">
 
                
 
                
 
               <li>
 
               <li>
                 <a id="The-Wiki-Wizard-submenu" class="btn btn-default btn-transparent btn-lg page-scroll" href="#The-Wiki-Wizard">The Wiki Wizard</a>
+
                 <a id="TheWikiWizard-submenu" class="btn btn-default btn-transparent btn-lg page-scroll" href="#TheWikiWizard">The Wiki Wizard</a>
 
               </li>
 
               </li>
 
                
 
                
 
               <li>
 
               <li>
                 <a id="NOD-Nrps-Oligo-Designer-submenu" class="btn btn-default btn-transparent btn-lg page-scroll" href="#NOD-Nrps-Oligo-Designer">NOD Nrps Oligo Designer</a>
+
                 <a id="NODNrpsOligoDesigner-submenu" class="btn btn-default btn-transparent btn-lg page-scroll" href="#NODNrpsOligoDesigner">NOD Nrps Oligo Designer</a>
 
               </li>
 
               </li>
 
                
 
                
Line 253: Line 240:
 
                
 
                
 
               <li>
 
               <li>
                 <a id="The-Wiki-Wizard-submenu" class="page-scroll" href="#The-Wiki-Wizard">The Wiki Wizard</a>
+
                 <a id="TheWikiWizard-submenu" class="page-scroll" href="#TheWikiWizard">The Wiki Wizard</a>
 
               </li>
 
               </li>
 
                
 
                
 
               <li>
 
               <li>
                 <a id="NOD-Nrps-Oligo-Designer-submenu" class="page-scroll" href="#NOD-Nrps-Oligo-Designer">NOD Nrps Oligo Designer</a>
+
                 <a id="NODNrpsOligoDesigner-submenu" class="page-scroll" href="#NODNrpsOligoDesigner">NOD Nrps Oligo Designer</a>
 
               </li>
 
               </li>
 
                
 
                
 
             </ul>
 
             </ul>
 +
           
 +
           
 
           </div>
 
           </div>
 
         </div>
 
         </div>
 +
       
 
         <div class="row">
 
         <div class="row">
 
           <div class="col-md-12">
 
           <div class="col-md-12">
 
             Scroll down for more<br>
 
             Scroll down for more<br>
             <a href="#The-Wiki-Wizard" class="btn btn-circle btn-transparent page-scroll">
+
             <a href="#TheWikiWizard" class="btn btn-circle btn-transparent page-scroll">
 
               <i class="fa fa-angle-double-down"></i>
 
               <i class="fa fa-angle-double-down"></i>
 
             </a>
 
             </a>
 
           </div>
 
           </div>
 
         </div>
 
         </div>
 +
       
 
       </div>
 
       </div>
 
     </div>
 
     </div>
 
      
 
      
+
   
 
+
       
<div id="The-Wiki-Wizard">
+
<div id="TheWikiWizard">
 
   <div class="container">
 
   <div class="container">
 +
 
 
     <div class="row col-md-12">
 
     <div class="row col-md-12">
 
       <h1>
 
       <h1>
 
         The Wiki Wizard
 
         The Wiki Wizard
 
       </h1>
 
       </h1>
     
+
       
     
+
 
      <div id="carousel-wiki-wizard" class="carousel slide" data-ride="carousel">
+
 
 +
<div id="carousel-wiki-wizard" class="carousel slide" data-ride="carousel">
 
   <!-- Indicators -->
 
   <!-- Indicators -->
 
   <ol class="carousel-indicators">
 
   <ol class="carousel-indicators">
Line 304: Line 297:
 
      
 
      
 
     <div class="item active">
 
     <div class="item active">
       <img class="img-responsive center-block" src="/wiki/images/b/b4/DTU-Denmark_wizard_screenshot2.png">
+
       <img class="img-responsive center-block" src="https://static.igem.org/mediawiki/2015/b/b4/DTU-Denmark_wizard_screenshot2.png">
 
       <div class="carousel-caption">
 
       <div class="carousel-caption">
 
         Word like editing with CKEDITOR
 
         Word like editing with CKEDITOR
Line 311: Line 304:
 
      
 
      
 
     <div class="item">
 
     <div class="item">
       <img class="img-responsive center-block" src="/wiki/images/7/7e/DTU-Denmark_wizard_screenshot3.png">
+
       <img class="img-responsive center-block" src="https://static.igem.org/mediawiki/2015/7/7e/DTU-Denmark_wizard_screenshot3.png">
 
       <div class="carousel-caption">
 
       <div class="carousel-caption">
 
         Manage pages, sections and members easily
 
         Manage pages, sections and members easily
Line 318: Line 311:
 
      
 
      
 
     <div class="item">
 
     <div class="item">
       <img class="img-responsive center-block" src="/wiki/images/c/ce/DTU-Denmark_wizard_screenshot4.png">
+
       <img class="img-responsive center-block" src="https://static.igem.org/mediawiki/2015/c/ce/DTU-Denmark_wizard_screenshot4.png">
 
       <div class="carousel-caption">
 
       <div class="carousel-caption">
 
         Automatically generated reference lists
 
         Automatically generated reference lists
Line 325: Line 318:
 
      
 
      
 
     <div class="item">
 
     <div class="item">
       <img class="img-responsive center-block" src="/wiki/images/7/7c/DTU-Denmark_wizard_screenshot.png">
+
       <img class="img-responsive center-block" src="https://static.igem.org/mediawiki/2015/7/7c/DTU-Denmark_wizard_screenshot.png">
 
       <div class="carousel-caption">
 
       <div class="carousel-caption">
 
         Upload Wiki to iGEM servers
 
         Upload Wiki to iGEM servers
Line 332: Line 325:
 
      
 
      
 
     <div class="item">
 
     <div class="item">
       <img class="img-responsive center-block" src="/wiki/images/b/b9/DTU-Denmark_wizard_screenshot5.png">
+
       <img class="img-responsive center-block" src="https://static.igem.org/mediawiki/2015/b/b9/DTU-Denmark_wizard_screenshot5.png">
 
       <div class="carousel-caption">
 
       <div class="carousel-caption">
 
         Select between different themes
 
         Select between different themes
Line 350: Line 343:
 
   </a>
 
   </a>
 
</div>
 
</div>
      <p>Creating and designing an iGEM wiki can be a difficult and time consuming task. We believe that many teams would benefit from an easier way to create and design, which led us to develop the Wiki Wizard.<br />
 
The Wiki Wizard is a content&nbsp;management system (CMS) that allows the user to create and edit pages easily. It includes functions such as: name spacing pages and files, referene list for a page, and a preview of the wiki that can be seen by clicking on the &rsquo;Team main page&rsquo; link in the menu. Most importantly, the Wiki Wizard allows user to create wiki that are in compliance with the wiki standards specified by iGEM.</p>
 
  
<p>You can find it at <span class="fa fa-github"></span><span style="color:#000000;"></span><a href="http://github.com/dkmva/igem-wiki-wizard">GitHub</a></p>
+
        <p>Creating and designing iGEM wikis can be a difficult and time consuming task. We developed the Wiki Wizard as we believe that teams would benefit from an easier way to create and design their wiki.&nbsp;The Wiki Wizard is a content&nbsp;management system (CMS) that allows the user to create and edit pages easily. It includes functions such as: name spacing pages and files, referene list for a page, and a preview of the wiki that can be seen by clicking on the &rsquo;Team main page&rsquo; link in the menu. Most importantly, the Wiki Wizard allows users to create wikis that are in compliance with the wiki standards specified by iGEM.</p>
 +
 
 +
<p>You can find it and an installation guide here:&nbsp;<span class="fa fa-github"></span><span style="color:#000000;"></span><a href="http://github.com/dkmva/igem-wiki-wizard">GitHub</a></p>
  
 
<h1>Wiki creation</h1>
 
<h1>Wiki creation</h1>
  
<p>With our wiki wizard, you can choose an existing theme, upload a theme made by someone else, or create your own. The tool is based on Flask and it uses the Jinja engine for loading of templates. By default, the Wiki Wizard uses a bootstrap theme and creates pages corresponding to the standard IGEM pages.</p>
+
<p>With our wiki wizard&nbsp;you can choose an existing theme, upload a theme made by someone else, or create your own theme. The tool is based on Flask and it uses the Jinja engine for loading of templates. By default, the Wiki Wizard uses a bootstrap theme and creates pages corresponding to the standard iGEM pages.</p>
  
 
<h2>Content</h2>
 
<h2>Content</h2>
Line 375: Line 368:
 
<h4>Section</h4>
 
<h4>Section</h4>
  
<p>Sections are where the content is stored. These can be edited either in the page editor or separately in the section editor. To make writing easier, the section content is written in a CKEDITOR frame, which allows you to write HTML as you would write a page in Word. This allows user without knowledge of HTML and CSS to generate appealing content. Sections, like pages, can be assigned an image, template, position, and name.</p>
+
<p>Sections are where the content is stored. These can be edited either in the page editor or separately in the section editor. The secition content&nbsp;is written in a CKEDITOR frame, which allows you to write HTML as you would write a page in Word. This makes editing easier and&nbsp;allows users without knowledge of HTML and CSS to generate appealing content. Sections, like pages, can be assigned an image, template, position, and name.</p>
  
 
<ul>
 
<ul>
Line 383: Line 376:
 
<li>T​he name is used for section headers. Themes can use the name to create links to sections.</li>
 
<li>T​he name is used for section headers. Themes can use the name to create links to sections.</li>
 
</ul>
 
</ul>
 
<p>&nbsp;</p>
 
  
 
<h4>Entities</h4>
 
<h4>Entities</h4>
  
<p>Besides keeping track of your pages, the Wiki Wizard can also store your teams members, advisors, sponsors etc as Entities. Section templates can be designed to show (some of) these, thus adding members to your members section can be done with a few clicks. Again these can be edited in a CKEDITOR frame (see above) and have some settings. They are, image, position name, role and link.</p>
+
<p>Besides keeping track of your pages, the Wiki Wizard can also store your teams members, advisors, sponsors, and etc, as &quot;Entities&quot;. Section templates can be designed to show (some of) these, thus adding members to your members section can be done with a few clicks. The entities can be edited in a CKEDITOR frame (see above) and they are associated with some settings. These settings are: image, position name, role, and link.</p>
 
+
<p>Besides keeping track of your pages, the Wiki Wizard can also store your teams members, advisors, sponsors, and etc, as &quot;Entities&quot;. Section templates can be designed to show (some of) these, thus adding members to your members section can be done with a few clicks. The entities can be edited in a CKEDITOR frame (see above) and they are associated with some settings. Thesettings are: image, position name, role, and link.</p>
+
  
 
<ul>
 
<ul>
<li>I​mages are used to for e​.g.​ member section images.</li>
+
<li>I​mages can be used, for example&nbsp;member section images.</li>
 
<li>Position determines the order of entities.</li>
 
<li>Position determines the order of entities.</li>
<li>​Role is used to filter entities; e​.g. By splitting up​ members in team membrrs and advisors.</li>
+
<li>​Role is used to filter entities; e​.g. by splitting up​ members in team members and advisors.</li>
 
<li>​Name is the name of the entity.</li>
 
<li>​Name is the name of the entity.</li>
<li>L​ink can be used to make links to e​.g.​ sponsor websites.</li>
+
<li>L​ink can be used to make links to for example sponsor websites.</li>
 
</ul>
 
</ul>
  
 
<h4>Menu</h4>
 
<h4>Menu</h4>
  
<p>The menu can be used to create a nested menu or add external links to the menu. Each item in the menu can have page, parent, position, name url, and children.</p>
+
<p>The menu can be used to create a nested menu or add external links to the menu. Each item in the menu can have page, parent, position, name url, and children, associated with it.</p>
  
 
<ul>
 
<ul>
<li>​Page is used to make a link to a page.</li>
+
<li>​Page is used to make a link to a&nbsp;page.</li>
<li>​Position determines order.</li>
+
<li>​Position determines the order of menu items.</li>
<li>​Name and url can be used to make external links. These are ignored if page is assigned. ​Parent/Children can be used to create dropdowns. Items associated witt a parent, will be listed under the parent, and children are the items listed under the current item. The number of levels of the menu may be limited by the selected theme.<br />
+
<li>​Name and url can be used to make external links. These are ignored if page is assigned. ​Parent/Children can be used to create dropdowns. Items associated with&nbsp;a parent&nbsp;will be listed under the parent&nbsp;and children are the items listed under the current item. The number of levels of the menu may be limited by the selected theme.</li>
&nbsp;</li>
+
 
</ul>
 
</ul>
  
Line 417: Line 405:
 
<h4>References</h4>
 
<h4>References</h4>
  
<p>Keeping track of reference order is tedious, bit with the Wiki Wizard, references are ordered automatically. They should have the reference text, and a reference id.</p>
+
<p>Keeping track of reference order is a tedious task, when writing your project pages. In the Wiki Wizard, references are ordered automatically. They should have the reference text, and a reference id.</p>
  
 
<ul>
 
<ul>
<li>T​he &quot;id&quot; is used to insert citations in the content. Similar to LaTeX, they can be inserted witth[-1].</li>
+
<li>T​he &quot;id&quot; is used to insert citations in the content. Similar to LaTeX, they can be inserted with \ cite{ref_id} without spaces.</li>
 
<li>​&quot;Reference text&quot; is the text that will be shown in the reference list.</li>
 
<li>​&quot;Reference text&quot; is the text that will be shown in the reference list.</li>
 
</ul>
 
</ul>
  
<p>These settings can be grabbed automatically by supplying a doi for the reference. The references Will be displayed, when a reference section is added to the page. The default themes include a reference section template.</p>
+
<p>These settings can be grabbed automatically by supplying the&nbsp;doi for the reference. The references will only be displayed, if the reference is used. The default themes include a reference section template which will show the reference list.</p>
 
+
<h2>&nbsp;</h2>
+
  
 
<h2>Files</h2>
 
<h2>Files</h2>
  
<p>Files can be uploaded to the Wiki Wizard under &quot;Files&quot;. The Wiki Wizard automatically rename files to the correct namespacing when uploading the files to the wiki (see below).</p>
+
<p>Files can be uploaded to the Wiki Wizard under &quot;Files&quot;. The Wiki Wizard automatically rename files to the correct namespacing, when the files are later uploaded to the wiki (see below).</p>
 
+
<p>&nbsp;</p>
+
  
 
<h2>Settings</h2>
 
<h2>Settings</h2>
  
<p>The settings tab can be used to select the base url that the wiki should upload to. This year, it is 2015.igem.org, next year it should be 2016.igem.org. This is also the page, where the team name should be entered, so that the Wizard can upload and rename files correctly. The last setting is used to determine whether or not, it should be possible for new users to register on the Wizard. This option should be ticked off, once the desired users have been created. Users can also be created and deleted under the Advanced &shy;&gt; Users tab.</p>
+
<p>The settings tab can be used to select the base url that the wiki should be upload to. This year, it is 2015.igem.org.&nbsp;Next year, it should be 2016.igem.org. This is also the page, where the team name should be entered, so that the Wizard can upload and rename files correctly. The last setting is used to determine whether or not, it should be possible for new users to register on the Wizard. This option should be ticked off, once the desired users have been created. Users can also be created and deleted under the Advanced &shy;&gt; Users tab.</p>
 
+
<h2>&nbsp;</h2>
+
  
 
<h2>Theme</h2>
 
<h2>Theme</h2>
Line 450: Line 432:
 
<h2>Writing themes</h2>
 
<h2>Writing themes</h2>
  
<p>The theme system utilises Flask&shy;Themes2 for theme selection. Additional information on writing themes can be seen&nbsp;<a href="https://flask-themes2.readthedocs.org/en/latest/#writing-templates">here</a>.</p>
+
<p>The theme system utilises Flask&shy;Themes2 for theme selection. Additional information on writing themes can be found&nbsp;<a href="https://flask-themes2.readthedocs.org/en/latest/#writing-templates">here</a>.</p>
  
<p>Themes can be uploaded to the Wiki Wizard as a zip file containing the theme folder. Briefly described, the theme folder contains one file and two folders.</p>
+
<p>Themes can be uploaded to the Wiki Wizard as a zip file containing the theme folder. The theme folder contains one file and two folders.</p>
  
 
<ul>
 
<ul>
Line 460: Line 442:
 
</ul>
 
</ul>
  
<p>Theme templates are stored in the templates folder and static files are put in the static folder, these can be images, javascript, stylesheets, etc. The info.json stores information about the theme, such as author and a description.</p>
+
<p>Theme templates are stored in the templates folder and static files are put in the static folder.&nbsp;These can be images, javascript, stylesheets, etc. The info.json stores information about the theme&nbsp;such as author and a description.</p>
  
 
<h2>Perspectives</h2>
 
<h2>Perspectives</h2>
  
<p>We have several improvements in mind for the Wiki Wizard.</p>
+
<p>We envision that a future Wiki Wizard contains the following improvements:</p>
  
 
<ul>
 
<ul>
<li>We would like to add a graphical menu builder, that can be used to design the main menu using drag and drop.</li>
+
<li>A graphical menu builder&nbsp;that can be used to design the main menu using drag and drop.</li>
<li>We would also like to improve on the collaboration feature and possibly use socketio to keep changes of the fields live.</li>
+
<li>Improvements of the&nbsp;collaboration feature that possibly use socketio to keep changes of the fields live.</li>
<li>Replace the admin feature with inline editing to give a better feel of how the page will look.</li>
+
<li>Replacing&nbsp;the admin feature with inline editing, which would&nbsp;give a better feel of how the page will look.</li>
 
</ul>
 
</ul>
 +
 +
       
  
 
     </div>
 
     </div>
 +
   
 
   </div>
 
   </div>
 
</div>
 
</div>
+
   
+
       
<div id="NOD-Nrps-Oligo-Designer">
+
<div id="NODNrpsOligoDesigner">
 
   <div class="container">
 
   <div class="container">
 +
 
 
     <div class="row col-md-12">
 
     <div class="row col-md-12">
 
       <h1>
 
       <h1>
 
         NOD Nrps Oligo Designer
 
         NOD Nrps Oligo Designer
 
       </h1>
 
       </h1>
      <p>In order to fully utilise high throughput methods, you must be able to do high throughput design.</p>
+
       
 +
        <p>In order to fully utilise high throughput methods, you must be able to do high throughput design.&nbsp;We developed a prototype oligo designer for NRPS library production and screening in python (NOD).</p>
  
<p>We developed a prototype oligo designer for NRPS library production and screening in python (NOD).</p>
+
<p>You can find it and an installation guide here:&nbsp;<span class="fa fa-github"></span><a href="https://github.com/dkmva/nrps-oligo-designer">GitHub</a></p>
 
+
<p>You can find it at <span class="fa fa-github"></span><a href="https://github.com/dkmva/nrps-oligo-designer">GitHub</a></p>
+
  
 
<h2>Usage</h2>
 
<h2>Usage</h2>
  
<p>NOD is a commandline program, that takes a fasta file with one or more dna sequences encoding a NRPS and prints oligos that can be used to alter the specifity of each module. Also shipped with the tool is a simple UI, that can be run instead.</p>
+
<p>NOD is a command line program&nbsp;that takes a fasta file with one or more DNA&nbsp;sequences encoding a NRPS and outputs oligos that can be used to alter the specifity of each module. Also shipped with the tool is a simple UI, that can be run instead.</p>
 
+
<p>&nbsp;</p>
+
  
 
<h2>Requirements</h2>
 
<h2>Requirements</h2>
  
<p>NOD requires a few extra programs. It uses HMMSEARCH of HMMER to identify the adenylation domains and MUSCLE to identify the stachelhaus code, it is written in python and requires BioPython. To run the UI, wxPython must also be installed.</p>
+
<p>NOD requires a few extra programs. It uses HMMSEARCH of HMMER to identify the adenylation domains and MUSCLE to identify the stachelhaus code.&nbsp;It is written in python and requires BioPython. To run the UI, wxPython must also be installed.</p>
 
+
<p>&nbsp;</p>
+
  
 
<h2>Development</h2>
 
<h2>Development</h2>
Line 506: Line 487:
  
 
<p>After identifying the stachelhaus residues, the stachelhaus code is compared to the stachelhaus code of different specificities. By comparing the degenerate sequence of the new stachelhaus code to the sequence of the native code, the changes are scored based on the amount of oligos required to incorporate all changes followed by the number of required mismatches. More than one oligo may be necessary, if changes are too far apart. The oligos are designed to be 90 nucleotides long with homologous ends of atleast 15 nucleotides in each end.</p>
 
<p>After identifying the stachelhaus residues, the stachelhaus code is compared to the stachelhaus code of different specificities. By comparing the degenerate sequence of the new stachelhaus code to the sequence of the native code, the changes are scored based on the amount of oligos required to incorporate all changes followed by the number of required mismatches. More than one oligo may be necessary, if changes are too far apart. The oligos are designed to be 90 nucleotides long with homologous ends of atleast 15 nucleotides in each end.</p>
 
<p>&nbsp;</p>
 
  
 
<h2>Perspectives</h2>
 
<h2>Perspectives</h2>
  
<p>The developed tool is only a prototype and several improvements could be added.</p>
+
<p>The developed tool is only a prototype. We suggest to implement the following improvements:</p>
  
 
<ul>
 
<ul>
<li>Currently the program randomly selects a codon from a degenerate codon if more than have the same required mismatches to incorporate. An improvement to this, could be to score codons according to codon usage.</li>
+
<li>Currently the program randomly selects a codon from a degenerate codon if there are more than one option with the same required mismatches. An improvement to this, could be to score codons according to codon usage.</li>
<li>The oligo folding is not optimised, but this could be added by using ViennaRNA.</li>
+
<li>The oligo folding is not optimized, but this could be added by adding&nbsp;ViennaRNA.</li>
<li>With more data on incorporation efficiencies, it would be possible to calculate the allelic replacement of each oligo set, in order to select the stachelhaus code with highest allelic replacement</li>
+
<li>With more data on incorporation efficiencies, it would be possible to calculate the allelic replacement of each oligo set, in order to select the stachelhaus code with highest allelic replacement.</li>
 
</ul>
 
</ul>
  
 +
       
 
     </div>
 
     </div>
 +
   
 
   </div>
 
   </div>
 
</div>
 
</div>
+
   
     <div class="container">
+
      
 +
<footer class="container">
 
       <div class="row">
 
       <div class="row">
 
         <div class="col-md-2 col-md-offset-2">
 
         <div class="col-md-2 col-md-offset-2">
 
           <a href="http://www.dtu.dk" target="_blank">
 
           <a href="http://www.dtu.dk" target="_blank">
             <img src="/wiki/images/b/b7/DTU-Denmark_dtulogo.png" height="130px">
+
             <img src="https://static.igem.org/mediawiki/2015/b/b7/DTU-Denmark_dtulogo.png" height="130px">
 
           </a>
 
           </a>
 
         </div>
 
         </div>
Line 543: Line 525:
 
         <div class="col-md-2">
 
         <div class="col-md-2">
 
           <a href="https://igem.org" style="float:left" target="_blank">
 
           <a href="https://igem.org" style="float:left" target="_blank">
               <img src="/wiki/images/a/af/DTU-Denmark_igemlogo.png" height="90px">
+
               <img src="https://static.igem.org/mediawiki/2015/a/af/DTU-Denmark_igemlogo.png" height="90px">
 
           </a>
 
           </a>
 
         </div>
 
         </div>
 
       </div>
 
       </div>
     </div>
+
     </footer>
 
     <div class="sponsors">
 
     <div class="sponsors">
       <div class="container-fluid">
+
       <div class="container">
 
         <div class="row">
 
         <div class="row">
 
            
 
            
 
           <div class="sponsorlogo">
 
           <div class="sponsorlogo">
 
             <a href="http://www.lundbeckfonden.com/" target="_blank">
 
             <a href="http://www.lundbeckfonden.com/" target="_blank">
               <img src="/wiki/images/e/e2/DTU-Denmark_Lundbeckfonden.jpg">
+
               <img src="https://static.igem.org/mediawiki/2015/e/e2/DTU-Denmark_Lundbeckfonden.jpg">
 
             </a>
 
             </a>
 
           </div>
 
           </div>
Line 560: Line 542:
 
           <div class="sponsorlogo">
 
           <div class="sponsorlogo">
 
             <a href="http://www.ottomoensted.dk" target="_blank">
 
             <a href="http://www.ottomoensted.dk" target="_blank">
               <img src="/wiki/images/3/35/DTU-Denmark_Ottomoensted.png">
+
               <img src="https://static.igem.org/mediawiki/2015/3/35/DTU-Denmark_Ottomoensted.png">
 
             </a>
 
             </a>
 
           </div>
 
           </div>
Line 566: Line 548:
 
           <div class="sponsorlogo">
 
           <div class="sponsorlogo">
 
             <a href="http://www.novonordiskfonden.dk/en" target="_blank">
 
             <a href="http://www.novonordiskfonden.dk/en" target="_blank">
               <img src="/wiki/images/5/5c/DTU-Denmark_NovoNordiskFonden_logo.png">
+
               <img src="https://static.igem.org/mediawiki/2015/5/5c/DTU-Denmark_NovoNordiskFonden_logo.png">
 
             </a>
 
             </a>
 
           </div>
 
           </div>
Line 572: Line 554:
 
           <div class="sponsorlogo">
 
           <div class="sponsorlogo">
 
             <a href="https://dk.vwr.com/" target="_blank">
 
             <a href="https://dk.vwr.com/" target="_blank">
               <img src="/wiki/images/e/ea/DTU-Denmark_VWR.jpg">
+
               <img src="https://static.igem.org/mediawiki/2015/e/ea/DTU-Denmark_VWR.jpg">
 
             </a>
 
             </a>
 
           </div>
 
           </div>
Line 578: Line 560:
 
           <div class="sponsorlogo">
 
           <div class="sponsorlogo">
 
             <a href="http://frisenette.dk" target="_blank">
 
             <a href="http://frisenette.dk" target="_blank">
               <img src="/wiki/images/c/c8/DTU-Denmark_Frisenette.jpg">
+
               <img src="https://static.igem.org/mediawiki/2015/c/c8/DTU-Denmark_Frisenette.jpg">
 
             </a>
 
             </a>
 
           </div>
 
           </div>
Line 584: Line 566:
 
           <div class="sponsorlogo">
 
           <div class="sponsorlogo">
 
             <a href="http://www.in-vitro.dk/" target="_blank">
 
             <a href="http://www.in-vitro.dk/" target="_blank">
               <img src="/wiki/images/7/7c/DTU-Denmark_In_Vitro.jpg">
+
               <img src="https://static.igem.org/mediawiki/2015/7/7c/DTU-Denmark_In_Vitro.jpg">
 
             </a>
 
             </a>
 
           </div>
 
           </div>
Line 590: Line 572:
 
           <div class="sponsorlogo">
 
           <div class="sponsorlogo">
 
             <a href="https://dk.fishersci.com/dk/" target="_blank">
 
             <a href="https://dk.fishersci.com/dk/" target="_blank">
               <img src="/wiki/images/b/b4/DTU-Denmark_Fisher_Scientific.jpg">
+
               <img src="https://static.igem.org/mediawiki/2015/b/b4/DTU-Denmark_Fisher_Scientific.jpg">
 
             </a>
 
             </a>
 
           </div>
 
           </div>
Line 596: Line 578:
 
           <div class="sponsorlogo">
 
           <div class="sponsorlogo">
 
             <a href="http://us.akg.com/akg-homepage-us.html" target="_blank">
 
             <a href="http://us.akg.com/akg-homepage-us.html" target="_blank">
               <img src="/wiki/images/9/9d/DTU-Denmark_AKG.png">
+
               <img src="https://static.igem.org/mediawiki/2015/9/9d/DTU-Denmark_AKG.png">
 
             </a>
 
             </a>
 
           </div>
 
           </div>
Line 602: Line 584:
 
           <div class="sponsorlogo">
 
           <div class="sponsorlogo">
 
             <a href="http://www.macrogen.com/" target="_blank">
 
             <a href="http://www.macrogen.com/" target="_blank">
               <img src="/wiki/images/1/11/DTU-Denmark_Marcogen.jpg">
+
               <img src="https://static.igem.org/mediawiki/2015/1/11/DTU-Denmark_Marcogen.jpg">
 
             </a>
 
             </a>
 
           </div>
 
           </div>
Line 608: Line 590:
 
           <div class="sponsorlogo">
 
           <div class="sponsorlogo">
 
             <a href="http://www.snapgene.com/" target="_blank">
 
             <a href="http://www.snapgene.com/" target="_blank">
               <img src="/wiki/images/5/58/DTU-Denmark_Snapgene.png">
+
               <img src="https://static.igem.org/mediawiki/2015/5/58/DTU-Denmark_Snapgene.png">
 
             </a>
 
             </a>
 
           </div>
 
           </div>
Line 614: Line 596:
 
           <div class="sponsorlogo">
 
           <div class="sponsorlogo">
 
             <a href="https://www.neb.com/" target="_blank">
 
             <a href="https://www.neb.com/" target="_blank">
               <img src="/wiki/images/e/e0/DTU-Denmark_NEB_logo.png">
+
               <img src="https://static.igem.org/mediawiki/2015/e/e0/DTU-Denmark_NEB_logo.png">
 
             </a>
 
             </a>
 
           </div>
 
           </div>

Latest revision as of 15:15, 9 November 2015

The Wiki Wizard

Creating and designing iGEM wikis can be a difficult and time consuming task. We developed the Wiki Wizard as we believe that teams would benefit from an easier way to create and design their wiki. The Wiki Wizard is a content management system (CMS) that allows the user to create and edit pages easily. It includes functions such as: name spacing pages and files, referene list for a page, and a preview of the wiki that can be seen by clicking on the ’Team main page’ link in the menu. Most importantly, the Wiki Wizard allows users to create wikis that are in compliance with the wiki standards specified by iGEM.

You can find it and an installation guide here: GitHub

Wiki creation

With our wiki wizard you can choose an existing theme, upload a theme made by someone else, or create your own theme. The tool is based on Flask and it uses the Jinja engine for loading of templates. By default, the Wiki Wizard uses a bootstrap theme and creates pages corresponding to the standard iGEM pages.

Content

Page

In the Wiki Wizard, a page is a container for one or more sections in which the page content is written. A page can also be assigned an image, template, position, name, and url.

  • The template determines the overall layout of the page.
  • T​he image is a setting that themes can use for page specific images.
  • Position determines the order of pages in the menu unless the menu is specified in menu (see below).
  • T​he name is shown in the menu, and
  • The URL is the link to the page – e​.g.​ blank for front page, or "Team" for the team page.

Section

Sections are where the content is stored. These can be edited either in the page editor or separately in the section editor. The secition content is written in a CKEDITOR frame, which allows you to write HTML as you would write a page in Word. This makes editing easier and allows users without knowledge of HTML and CSS to generate appealing content. Sections, like pages, can be assigned an image, template, position, and name.

  • T​he image is a setting that themes can use for section specific images.
  • T​he template determines which and how the content is rendered.
  • ​The position determines the order of the sections on a page, and
  • T​he name is used for section headers. Themes can use the name to create links to sections.

Entities

Besides keeping track of your pages, the Wiki Wizard can also store your teams members, advisors, sponsors, and etc, as "Entities". Section templates can be designed to show (some of) these, thus adding members to your members section can be done with a few clicks. The entities can be edited in a CKEDITOR frame (see above) and they are associated with some settings. These settings are: image, position name, role, and link.

  • I​mages can be used, for example member section images.
  • Position determines the order of entities.
  • ​Role is used to filter entities; e​.g. by splitting up​ members in team members and advisors.
  • ​Name is the name of the entity.
  • L​ink can be used to make links to for example sponsor websites.

Menu

The menu can be used to create a nested menu or add external links to the menu. Each item in the menu can have page, parent, position, name url, and children, associated with it.

  • ​Page is used to make a link to a page.
  • ​Position determines the order of menu items.
  • ​Name and url can be used to make external links. These are ignored if page is assigned. ​Parent/Children can be used to create dropdowns. Items associated with a parent will be listed under the parent and children are the items listed under the current item. The number of levels of the menu may be limited by the selected theme.

Timeline

Timeline entries can be used to quickly generate a timeline/journal. These entries have a date, title, and content, which can be edited with a CKEDITOR. The timeline can be inserted in a specific section by selecting a template that shows timeline entries.

References

Keeping track of reference order is a tedious task, when writing your project pages. In the Wiki Wizard, references are ordered automatically. They should have the reference text, and a reference id.

  • T​he "id" is used to insert citations in the content. Similar to LaTeX, they can be inserted with \ cite{ref_id} without spaces.
  • ​"Reference text" is the text that will be shown in the reference list.

These settings can be grabbed automatically by supplying the doi for the reference. The references will only be displayed, if the reference is used. The default themes include a reference section template which will show the reference list.

Files

Files can be uploaded to the Wiki Wizard under "Files". The Wiki Wizard automatically rename files to the correct namespacing, when the files are later uploaded to the wiki (see below).

Settings

The settings tab can be used to select the base url that the wiki should be upload to. This year, it is 2015.igem.org. Next year, it should be 2016.igem.org. This is also the page, where the team name should be entered, so that the Wizard can upload and rename files correctly. The last setting is used to determine whether or not, it should be possible for new users to register on the Wizard. This option should be ticked off, once the desired users have been created. Users can also be created and deleted under the Advanced ­> Users tab.

Theme

This section can be used to edit/upload files for the current theme under theme files. Themes can be selected under "Select Theme".

Wiki Upload

The Wiki Wizard can upload the files and content to the iGEM servers and automatically rename files to the correct namespace. The Wiki Wizard takes care of the upload using the user's login to iGEM.

Writing themes

The theme system utilises Flask­Themes2 for theme selection. Additional information on writing themes can be found here.

Themes can be uploaded to the Wiki Wizard as a zip file containing the theme folder. The theme folder contains one file and two folders.

  • info.json
  • static
  • templates

Theme templates are stored in the templates folder and static files are put in the static folder. These can be images, javascript, stylesheets, etc. The info.json stores information about the theme such as author and a description.

Perspectives

We envision that a future Wiki Wizard contains the following improvements:

  • A graphical menu builder that can be used to design the main menu using drag and drop.
  • Improvements of the collaboration feature that possibly use socketio to keep changes of the fields live.
  • Replacing the admin feature with inline editing, which would give a better feel of how the page will look.

NOD Nrps Oligo Designer

In order to fully utilise high throughput methods, you must be able to do high throughput design. We developed a prototype oligo designer for NRPS library production and screening in python (NOD).

You can find it and an installation guide here: GitHub

Usage

NOD is a command line program that takes a fasta file with one or more DNA sequences encoding a NRPS and outputs oligos that can be used to alter the specifity of each module. Also shipped with the tool is a simple UI, that can be run instead.

Requirements

NOD requires a few extra programs. It uses HMMSEARCH of HMMER to identify the adenylation domains and MUSCLE to identify the stachelhaus code. It is written in python and requires BioPython. To run the UI, wxPython must also be installed.

Development

The code for identification of adenylation domains and stachelhaus is based on antiSMASH, but has been slightly modified in order to not only identify the stachelhaus code, but also keep track on the positions in the unaligned sequence.

After identifying the stachelhaus residues, the stachelhaus code is compared to the stachelhaus code of different specificities. By comparing the degenerate sequence of the new stachelhaus code to the sequence of the native code, the changes are scored based on the amount of oligos required to incorporate all changes followed by the number of required mismatches. More than one oligo may be necessary, if changes are too far apart. The oligos are designed to be 90 nucleotides long with homologous ends of atleast 15 nucleotides in each end.

Perspectives

The developed tool is only a prototype. We suggest to implement the following improvements:

  • Currently the program randomly selects a codon from a degenerate codon if there are more than one option with the same required mismatches. An improvement to this, could be to score codons according to codon usage.
  • The oligo folding is not optimized, but this could be added by adding ViennaRNA.
  • With more data on incorporation efficiencies, it would be possible to calculate the allelic replacement of each oligo set, in order to select the stachelhaus code with highest allelic replacement.
Technical University of Denmark
Department of Systems Biology
Søltofts Plads 221
2800 Kgs. Lyngby
Denmark
P: +45 45 25 25 25
M: dtu-igem-2015@googlegroups.com