Difference between revisions of "Team:IISER Kolkata/Parts"

(Prototype team page)
 
 
(19 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
{{IISER_Kolkata}}
 
 
<html>
 
<html>
 +
  
 +
<link rel="stylesheet" href="https://2019.igem.org/wiki/index.php?title=Team:IISER_Kolkata/.css&action=raw&ctype=text/css"/>
 +
<link rel="stylesheet" href="https://2019.igem.org/wiki/index.php?title=Team:IISER_Kolkata/common.css&action=raw&ctype=text/css"/>
  
−
<div class="column full_size">
+
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.1.1/jquery.min.js"></script>
−
<h1>Parts</h1>
+
<script src="https://2019.igem.org/wiki/index.php?title=Team:IISER_Kolkata/.js&action=raw&ctype=text/javascript" defer></script>
−
<p>Each team will make new parts during iGEM and will add them to the Registry of Standard Biological Parts. The iGEM provides an easy way to present the parts your team has created. The <code>&lt;groupparts&gt;</code> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.</p>
+
<script src="https://2019.igem.org/wiki/index.php?title=Team:IISER_Kolkata/common.js&action=raw&ctype=text/javascript" defer></script>
−
<p>Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without needing to refer to the primary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for users who wish to know more.</p>
+
−
</div>
+
−
 
+
−
<div class="column full_size">
+
−
<div class="highlight decoration_background">
+
−
<h3>Note</h3>
+
−
<p>Note that parts must be well documented on each part's <a href="http://parts.igem.org/Main_Page">Main Page on the Registry</a>. This documentation includes all of the characterization data for your parts. <b>The part's data MUST be on the part's Main Page on the Registry for your team to be eligible for medals and special prizes pertaining to parts.</b> <br><br>
+
−
This page serves to <i>showcase</i> the parts you have made and should include links to the Registry pages for your parts. Future teams and other users and are much more likely to find parts by looking in the Registry than by looking at your team wiki.</p>
+
−
</div>
+
−
</div>
+
−
 
+
−
<div class="clear extra_space"></div>
+
−
<div class="line_divider"></div>
+
−
<div class="clear extra_space"></div>
+
−
 
+
−
 
+
−
 
+
−
 
+
−
 
+
−
<div class="column two_thirds_size">
+
−
<div class="highlight decoration_B_full">
+
−
 
+
−
<h3>Adding parts to the registry</h3>
+
−
<p>You can add parts to the Registry at our <a href="http://parts.igem.org/Add_a_Part_to_the_Registry">Add a Part to the Registry</a> link.</p>
+
−
 
+
−
<p>We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The sooner you put up your parts, the better you will remember all the details about your parts. Documentation includes the characterization data of your parts.</p>
+
−
<div class="button_link">
+
−
<a href="http://parts.igem.org/Add_a_Part_to_the_Registry">
+
−
ADD PARTS
+
−
</a>
+
−
</div>
+
−
 
+
−
</div>
+
−
</div>
+
−
 
+
−
 
+
−
 
+
−
<div class="column third_size">
+
−
<div class="highlight decoration_A_full">
+
−
<h3>Inspiration</h3>
+
−
<p>We have a created  a <a href="http://parts.igem.org/Well_Documented_Parts">collection of well documented parts</a> that can help you get started.</p>
+
−
 
+
−
<p> You can also take a look at how other teams have documented their parts in their wiki:</p>
+
−
<ul>
+
−
<li><a href="https://2014.igem.org/Team:MIT/Parts"> 2014 MIT </a></li>
+
−
<li><a href="https://2014.igem.org/Team:Heidelberg/Parts"> 2014 Heidelberg</a></li>
+
−
<li><a href="https://2014.igem.org/Team:Tokyo_Tech/Parts">2014 Tokyo Tech</a></li>
+
−
</ul>
+
−
</div>
+
−
</div>
+
−
 
+
−
 
+
−
<div class="clear extra_space"></div>
+
−
 
+
−
 
+
−
 
+
−
 
+
−
<div class="column full_size">
+
−
 
+
−
<h3>What information do I need to start putting my parts on the Registry?</h3>
+
−
<p>The information needed to initially create a part on the Registry is:</p>
+
−
<ul>
+
−
<li>Part Name</li>
+
−
<li>Part type</li>
+
−
<li>Creator</li>
+
−
<li>Sequence</li>
+
−
<li>Short Description (60 characters on what the DNA does)</li>
+
−
<li>Long Description (Longer description of what the DNA does)</li>
+
−
<li>Design considerations</li>
+
−
</ul>
+
−
 
+
−
<p>
+
−
We encourage you to put up <em>much more</em> information as you gather it over the summer. If you have images, plots, characterization data and other information, you must also put it up on the part page. </p>
+
−
 
+
−
</div>
+
−
 
+
−
 
+
−
<div class="clear extra_space"></div>
+
−
<div class="line_divider"></div>
+
−
<div class="clear extra_space"></div>
+
−
 
+
−
<div class="column full_size">
+
−
<h3>Part Table </h3>
+
−
 
+
−
<p>Please include a table of all the parts your team has made during your project on this page. Remember part characterization and measurement data must go on your team part pages on the Registry. </p>
+
−
 
+
−
</html>
+
−
<groupparts>iGEM19 IISER_Kolkata</groupparts>
+
−
<html>
+
−
</div>
+
  
 +
<style>
 +
div#butcont {
 +
align-self: center;
 +
display: flex;
 +
flex-wrap: wrap;
 +
flex-direction: row;
 +
justify-content: center;
 +
}
 +
div.butdiv {
 +
background-color: #74ed46;
 +
        box-shadow: 0vmax 0vmax 0.5vmax 0.1vmax #333333;
 +
height: auto;
 +
width: auto;
 +
cursor: pointer;
 +
margin: 2vmax;
 +
padding: 1vmax;
 +
        -webkit-transition: 0.2s linear;
 +
        -moz-transition: 0.2s linear;
 +
        -o-transition: 0.2s linear;
 +
        transition: 0.2s linear;
 +
}
 +
div.butdiv a {
 +
text-decoration: none;
 +
}
 +
div.butdiv h4 {
 +
    font-size: 1.8vmax;
 +
    line-height: 1.4;
 +
    font-weight: normal;
 +
color: black;
 +
font-family: mohave;
 +
margin: 0 !important;
 +
padding: 0 !important;
 +
        -webkit-transition: 0.2s linear;
 +
        -moz-transition: 0.2s linear;
 +
        -o-transition: 0.2s linear;
 +
        transition: 0.2s linear;
 +
}
 +
div.butdiv:hover {
 +
background-color: black;
 +
}
 +
div.butdiv:hover h4 {
 +
color: #74ed46;
 +
}
 +
/*mobile mode*/
 +
@media screen and (orientation: portrait) {
 +
div.butdiv h4 {
 +
    font-size: 2.8vmax;
 +
}
 +
}
 +
</style>
 +
 +
<nav id="navbar">
 +
<div id="mobdiv">
 +
<div id="logo"><a href="https://2019.igem.org/Team:IISER_Kolkata"><img src="https://static.igem.org/mediawiki/2019/0/0c/T--IISER_Kolkata--unleash.png"/></a></div>
 +
<div id="menuicon">
 +
<span id="bar1"></span>
 +
<span id="bar2"></span>
 +
<span id="bar3"></span>
 +
</div>
 +
</div>
 +
<ul>
 +
<li id="homeMenu"><div><a href="https://2019.igem.org/Team:IISER_Kolkata">Home</a></div></li>
 +
<li id="teamMenu"><div><a href="">Team</a></div>
 +
<ul class="dropdown">
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Team">Members</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Guides">Guides</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Collaborations">Collaborations</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Attributions">Attributions</a></div></li>
 +
</ul>
 +
</li>
 +
<li id="projectMenu"><div><a href="">Project</a></div>
 +
<ul class="dropdown">
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Description">Description</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Design">Design</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Experiments">Experiments</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Notebook">Notebook</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Contribution">Contribution</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Results">Results</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Model">Model</a></div></li>
 +
</ul>
 +
</li>
 +
<li id="partsMenu"><div><a href="">Parts</a></div>
 +
<ul class="dropdown">
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Parts">Overview</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Basic_Part">Basic</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Composite_Part">Composite</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Part_Collection">Collection</a></div></li>
 +
</ul>
 +
</li>
 +
<li id="safetyMenu"><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Safety">Safety</a></div></li>
 +
<li id="humanityMenu"><div><a href="">Humanity</a></div>
 +
<ul class="dropdown">
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Practices_Overview">Overview</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Human_Practices">Integrated&nbsp;HP</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Public_Engagement">Engagement</a></div></li>
 +
<li><div><a href="https://2019.igem.org/Team:IISER_Kolkata/Social_Studies">Social</a></div></li>
 +
</ul>
 +
</li>
 +
</ul>
 +
</nav>
 +
           
 +
                <div id="container">
 +
<h1 class="heading">Parts Overview</h1>
  
 +
<section class="sec white">
 +
<p>The Biobrick parts we designed are helpful in detecting a particular range of nitric oxide concentration inside the macrophages. When the macrophage is infected with any parasite or pathogen, nitric oxide acts as a signaling molecule to trigger the immune response. We are exploiting this unique ability of the macrophage to identify the infected macrophages.</p>
 +
<p>Our Biobrick is active only in certain range of concentration and are turned off outside this range.</p>
 +
<p>The other set of Biobrick consists of iron chelators that we have proposed to use inside the macrophage to chelate the labile iron. As iron is an important micronutrient for most pathogens and parasites to maintain their physiological functions, by chelating the iron, we can suppress the pathogen infectivity, reducing their pathogenicity, and  controlling the spread of the pathogen to different parts of the body as well as combat the pathogen at early stages of infection.</p>
 +
<p>In toto our designed biobrick can produce the iron chelator by sensing the surrounding nitric oxide concentration. This Biobrick can be used in both detection and therapeutics of pathogenic diseases.</p>
 +
<div id="butcont">
 +
<div class="butdiv"><a href="https://2019.igem.org/Team:IISER_Kolkata/Basic_Part"><h4>Basic parts</h4></a></div>
 +
<div class="butdiv"><a href="https://2019.igem.org/Team:IISER_Kolkata/Composite_Part"><h4>Composite parts</h4></a></div>
 +
<div class="butdiv"><a href="https://2019.igem.org/Team:IISER_Kolkata/Part_Collection"><h4>Parts collection</h4></a></div>
 +
</div>
 +
</section>                       
 +
                </div>
  
  
 
</html>
 
</html>

Latest revision as of 02:21, 22 October 2019

Parts Overview

The Biobrick parts we designed are helpful in detecting a particular range of nitric oxide concentration inside the macrophages. When the macrophage is infected with any parasite or pathogen, nitric oxide acts as a signaling molecule to trigger the immune response. We are exploiting this unique ability of the macrophage to identify the infected macrophages.

Our Biobrick is active only in certain range of concentration and are turned off outside this range.

The other set of Biobrick consists of iron chelators that we have proposed to use inside the macrophage to chelate the labile iron. As iron is an important micronutrient for most pathogens and parasites to maintain their physiological functions, by chelating the iron, we can suppress the pathogen infectivity, reducing their pathogenicity, and controlling the spread of the pathogen to different parts of the body as well as combat the pathogen at early stages of infection.

In toto our designed biobrick can produce the iron chelator by sensing the surrounding nitric oxide concentration. This Biobrick can be used in both detection and therapeutics of pathogenic diseases.