Difference between revisions of "Team:IIT-Madras/Description"

(Prototype team page)
 
 
(20 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{IIT-Madras}}
+
{{IIT-Madras--Header}}
 
<html>
 
<html>
 +
    <div class="row" style="grid-template-columns: 1fr;">
 +
        <div class="box" style="font-size: 30px; font-family: heads; text-align: center; padding: 40px;  padding-top: 100px; background: #039BE5; color: white;">
 +
            Description
 +
        </div>
 +
    </div>
  
 +
    <div class="row" style="grid-template-columns: 768px; background: #ffffff; justify-content: center;">
 +
        <div class="box mainbox" style="padding: 40px;  color: #161b1f; background: white;">
 +
            <h1>What? Why? How?</h1>
 +
            <h2>What does our database do?</h2>
 +
            An easy access platform with a database of various host organisms and tools to work with them.
 +
            <h2>Why?</h2>
 +
            <br>For a considerable amount of time, it has been known that Escherichia coli is not the omnipotent synthetic biology model organism that it is made out to be. With many context failures and departures from the desired expression once out of the lab, it has become frustrating to work with specialized functions in model organisms.</br>
 +
<br>
 +
When a model organism fails to optimally express a gene isolated from another organism, the next proposed step could be to either try to clone it into another organism or work with the native yet uncharacterized organism. But, working with an uncharacterized organism can have multiple natural hindrances like growth and maintenance conditions. A larger roadblock can be obtaining the protocols, parts, vectors, and even simple things like optimal growth and maintenance conditions.</br>
 +
<br>
 +
Our team faced many of the problems mentioned above while we tried to work with the halo-extremophile, Haloferax volcanii. Hence, we decided to come up with a database that would help ease the transition to working with an organism less worked with.</br>
 +
<br><br>
 +
<h2>How does the database work?</h2>
 +
<br>
 +
The landing page of the database has a drop-down menu and a search bar where the user entered/selected organism is matched with the list of organisms present in the database. This then takes the user to a different page consisting of all important attributes of the organism. At this page, there is an option present to either navigate through all the attributes by scrolling down or by selecting a specific attribute in the list present on the left-hand side.
 +
There is also an option to add a new organism and all details pertaining to it by filling a form that feeds the entered data to the database. The organism is now a new addition to the database and is visible in the drop-down menu.
  
  
<div class="column full_size">
+
           
<h1>Description</h1>
+
        </div>
 
+
    </div>
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
+
 
+
 
+
<h5>What should this page contain?</h5>
+
<ul>
+
<li> A clear and concise description of your project.</li>
+
<li>A detailed explanation of why your team chose to work on this particular project.</li>
+
<li>References and sources to document your research.</li>
+
<li>Use illustrations and other visual resources to explain your project.</li>
+
</ul>
+
 
+
 
+
</div>
+
 
+
<div class="column full_size" >
+
 
+
<h5>Advice on writing your Project Description</h5>
+
 
+
<p>
+
We encourage you to put up a lot of information and content on your wiki, but we also encourage you to include summaries as much as possible. If you think of the sections in your project description as the sections in a publication, you should try to be consist, accurate and unambiguous in your achievements.
+
</p>
+
 
+
<p>
+
Judges like to read your wiki and know exactly what you have achieved. This is how you should think about these sections; from the point of view of the judge evaluating you at the end of the year.
+
</p>
+
 
+
</div>
+
 
+
 
+
<div class="column half_size" >
+
 
+
<h5>References</h5>
+
<p>iGEM teams are encouraged to record references you use during the course of your research. They should be posted somewhere on your wiki so that judges and other visitors can see how you thought about your project and what works inspired you.</p>
+
 
+
</div>
+
 
+
 
+
<div class="column half_size" >
+
<h5>Inspiration</h5>
+
<p>See how other teams have described and presented their projects: </p>
+
 
+
<ul>
+
<li><a href="https://2016.igem.org/Team:Imperial_College/Description">2016 Imperial College</a></li>
+
<li><a href="https://2016.igem.org/Team:Wageningen_UR/Description">2016 Wageningen UR</a></li>
+
<li><a href="https://2014.igem.org/Team:UC_Davis/Project_Overview"> 2014 UC Davis</a></li>
+
<li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">2014 SYSU Software</a></li>
+
</ul>
+
</div>
+
 
+
 
+
 
+
 
</html>
 
</html>
 +
{{IIT-Madras--Footer}}

Latest revision as of 16:34, 31 October 2017

Team IIT-Madras

Description

What? Why? How?

What does our database do?

An easy access platform with a database of various host organisms and tools to work with them.

Why?


For a considerable amount of time, it has been known that Escherichia coli is not the omnipotent synthetic biology model organism that it is made out to be. With many context failures and departures from the desired expression once out of the lab, it has become frustrating to work with specialized functions in model organisms.

When a model organism fails to optimally express a gene isolated from another organism, the next proposed step could be to either try to clone it into another organism or work with the native yet uncharacterized organism. But, working with an uncharacterized organism can have multiple natural hindrances like growth and maintenance conditions. A larger roadblock can be obtaining the protocols, parts, vectors, and even simple things like optimal growth and maintenance conditions.

Our team faced many of the problems mentioned above while we tried to work with the halo-extremophile, Haloferax volcanii. Hence, we decided to come up with a database that would help ease the transition to working with an organism less worked with.


How does the database work?


The landing page of the database has a drop-down menu and a search bar where the user entered/selected organism is matched with the list of organisms present in the database. This then takes the user to a different page consisting of all important attributes of the organism. At this page, there is an option present to either navigate through all the attributes by scrolling down or by selecting a specific attribute in the list present on the left-hand side. There is also an option to add a new organism and all details pertaining to it by filling a form that feeds the entered data to the database. The organism is now a new addition to the database and is visible in the drop-down menu.