Difference between revisions of "Team:SUNY Oneonta/Parts"

(Prototype team page)
 
Line 1: Line 1:
{{IGEM_TopBar}}
+
<!-- # TODO: #6 Fix table caption font--><!-- # TODO: #7 Fix citations links font size--><html lang="en"><head><meta charset="utf-8"/><meta content="width=device-width,initial-scale=1" name="viewport"/><title>Parts | iGEM SUNY_Oneonta</title><script src="https://2020.igem.org/common/MathJax-2.5-latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script><link href="https://2021.igem.org/Template:SUNY_Oneonta/css/contentCSS?action=raw&amp;ctype=text/css" rel="stylesheet"/></head><body><!-- # TODO: #6 Fix table caption font--><!-- # TODO: #7 Fix citations links font size--><nav class="navbar navbar-expand-xl fixed-top"><div class="container d-flex justify-content-between"><a class="navbar-brand d-lg-inline-block" href="https://2021.igem.org/Team:SUNY_Oneonta"><h1>SNflaPs</h1></a><button aria-controls="navbarNav" aria-expanded="false" aria-label="Toggle navigation" class="navbar-toggler" data-target="#navbarNav" data-toggle="collapse" type="button"><span class="navbar-toggler-icon"></span></button><div class="collapse navbar-collapse" id="navbarNav"><ul class="navbar-nav ml-auto"><li class="nav-item dropdown"><a aria-expanded="false" aria-haspopup="true" class="nav-link dropdown-toggle" data-toggle="dropdown" href="#" id="navbarProject InspirationDropdown" role="button">Project Inspiration</a><div aria-labelledby="navbarProject InspirationDropdown" class="dropdown-menu"><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Abstract">Abstract</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Description">Description</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Inspiration">Inspiration</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/https:/video.igem.org/w/h4vrbSMacEdgkw4C3SN6hy">Promotional Video</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/#">Presentation</a></div></li><li class="nav-item dropdown"><a aria-expanded="false" aria-haspopup="true" class="nav-link dropdown-toggle" data-toggle="dropdown" href="#" id="navbarProjectDropdown" role="button">Project</a><div aria-labelledby="navbarProjectDropdown" class="dropdown-menu"><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Overview">Overview</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Sample_Prep">Sample Preparation</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Detection">Detection</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Model">Modeling</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Hardware">Hardware/Software</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/RPA">RPA</a></div></li><li class="nav-item dropdown"><a aria-expanded="false" aria-haspopup="true" class="nav-link dropdown-toggle" data-toggle="dropdown" href="#" id="navbarJudgingDropdown" role="button">Judging</a><div aria-labelledby="navbarJudgingDropdown" class="dropdown-menu"><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Part_Collection">Parts</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Implementation">Implementation</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Engineering">Engineering</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Contribution">Contributions</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Judging">Judging Confirmation</a></div></li><li class="nav-item dropdown"><a aria-expanded="false" aria-haspopup="true" class="nav-link dropdown-toggle" data-toggle="dropdown" href="#" id="navbarHuman PracticesDropdown" role="button">Human Practices</a><div aria-labelledby="navbarHuman PracticesDropdown" class="dropdown-menu"><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Engaging_Stakeholders">Engaging Stakeholders</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Collaborations">Collaborations</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Outreach">Educational Outreach</a></div></li><li class="nav-item dropdown"><a aria-expanded="false" aria-haspopup="true" class="nav-link dropdown-toggle" data-toggle="dropdown" href="#" id="navbarTeamDropdown" role="button">Team</a><div aria-labelledby="navbarTeamDropdown" class="dropdown-menu"><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Team">Team</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Attributions">Attributions</a></div></li><li class="nav-item dropdown"><a aria-expanded="false" aria-haspopup="true" class="nav-link dropdown-toggle" data-toggle="dropdown" href="#" id="navbarLab NotebookDropdown" role="button">Lab Notebook</a><div aria-labelledby="navbarLab NotebookDropdown" class="dropdown-menu"><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Protocols">Protocols</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Daily_Log">Daily Log</a><a class="dropdown-item" href="https://2021.igem.org/Team:SUNY_Oneonta/Safety">Safety</a></div></li></ul></div><div class="d-flex" id="themeSwitchWrapper"><i class="far fa-sun"></i><div id="themeSwitch"><label class="switch" for="themeSwitchInput"><input id="themeSwitchInput" type="checkbox"/><span class="slider round"></span></label></div><i class="far fa-moon"></i></div></div></nav><header class="d-flex justify-content-center align-items-center"><div class="container"><h1>Parts</h1><p class="lead pl-1"></p><hr class="my-4"/></div></header><main><div class="container"><div class="row"><div class="sidebar col-lg-3"><div class="nav" id="contents"><h5>Contents</h5><ul></ul></div></div><div class="content col-lg-9"><article><h1>Preparing New Targets</h1><h2>Expanding on the Ca2LF Concept to Develop SNflaPs</h2><p>In the project Ca2LF, we developed the Flappase assay to detect a single nucleotide polymorphism (SNP) in one gene, the beta-casein gene. The detection of the SNP would only tell us what version of the beta-casein allele is present, A1 or A2. For this year’s project we wanted to expand the usefulness of our genetic testing system. We decided to expand our system to be used to characterize the genetic profile of a cow on a variety of different traits so that farmers could make informed decisions regarding a variety of advantageous and deleterious traits when breeding their cows.</p><h1>Identifying potential target genes</h1><p>We began by interviewing two experts in cattle genetics and breeding, Dr.’s Dechow and Huson. During this interview, we learned about some genetic conditions that are not desirable in cattle, such as diseases, conditions that negatively impact fertility, and physical traits (for example, being horned) that farms routinely attempt to breed out of their herds. We also learned about genetic traits that are advantageous and routinely selected for by farmers when breeding, including genes involved in promoting fertility, milk production, and milk composition. We compiled a list of these genes and researched their different alleles (Table 1).</p><p><strong>TABLE 1 HERE</strong></p><p>Another important piece of feedback we received from the interviews with Drs Dechow and Huson is that most alleles are created by multiple SNPs, or larger changes to the gene, such as insertions, deletions, inversions, or duplications. So, to be useful, our SNflaPs genetic testing system needs to detect multiple types of polymorphisms. We decided to focus our efforts on selecting a few genes, each of which has a different type of polymorphism, to serve as proof of concept that the Flappase-based detection system can discriminate between these alleles.</p><p><strong>Table 2. Genes selected for proof-of-concept testing of the Flappase assay for detecting polymorphisms.</strong> The genes selected for each contain different polymorphisms, or multiple SNPs found in close, medium, or far proximity to each other.</p><p><strong>TABLE 2 HERE</strong></p><p>When deciding which genes to use for testing the detection system we used the following criteria:</p><ol><li>The length of any polymorphism should be less than 5,000 bp.</li><li>If multiple SNPs are to be detected, the distance between these should be enough to fit both the oligos, as well as accommodate the Flappase protein that is approx. 22 nucleotides and 75 Angstroms apart (See modeling page).</li><li>For initial testing, any gene selected should be of sufficient length to be synthesized for the creation of positive control DNAs.</li></ol><p>Based on these characteristics, we decided to begin by pursuing LRP4 and APOB as model genes.</p><h1>Designing and cloning new targets and oligos for use with the Flappase system</h1><h2>New Target #1- LRP4</h2><p>The <em>LRP4</em> gene encodes for LDL receptor related protein 4 (3). Two well-characterized allelic variants of this gene have been identified, the normal (wildtype) version, and a syndactylous version. Inheritance of the syndactylous version leads to congenital syndactyly. This condition, also known as mulefoot, refers to the fusion or non-division of the two developed digits of the bovine foot (4).</p><div class="image"><img alt="Sequence variation between the normal and syndactyl alleles of LRP4. The two versions differ by two SNPs, where nucleotides CG are substituted by AT at positions 4863 and 4864." src="https://static.igem.org/mediawiki/2021/b/b2/T--SUNY_Oneonta--img--NT-01.png" style="width: 85%"/><p>Figure 3: Sequence variation between the normal and syndactyl alleles of LRP4. The two versions differ by two SNPs, where nucleotides CG are substituted by AT at positions 4863 and 4864.</p></div><h1>Parts Registry</h1></article></div></div></div></main><footer><div class="container"><p>Email: <a href="mailto:igem@oneonta.edu">iGEM@oneonta.edu</a> | <a href="https://suny.oneonta.edu/igem">suny.oneonta.edu/iGEM</a></p></div></footer><script src="https://2021.igem.org/Template:SUNY_Oneonta/content-bundleJS?action=raw&amp;ctype=text/javascript"></script></body></html>
{{SUNY_Oneonta}}
+
<html>
+
 
+
 
+
<div class="column full_size">
+
<h1>Parts</h1>
+
<p>Each team will make new parts during iGEM and will add them to the Registry of Standard Biological Parts. 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>
+
<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 Main Page on the <a href="http://parts.igem.org/Main_Page">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 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 full_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 adding and documenting their parts on the Registry as soon as they can. Once you add your parts to the Registry, you can continue to add documentation to them throughout the iGEM season (up until the Registry freeze). This will allow you to remember all the details about your parts and store their history in the wiki. 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: Basic Parts</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 the following examples for Basic Parts on the Registry:</p>
+
<ul>
+
<li><a href="http://parts.igem.org/Part:BBa_K3114006">2019 Calgary </a></li>
+
<li><a href="http://parts.igem.org/Part:BBa_K3027000">2019 GO Paris Saclay</a></li>
+
<li><a href="http://parts.igem.org/Part:BBa_K3187028">2019 TU Darmstadt</a></li>
+
<li><a href="http://parts.igem.org/Part:BBa_K3552000">2020 Links China</a></li>
+
<li><a href="http://parts.igem.org/Part:BBa_K3558000">2020 UNSW Australia</a></li>
+
<li><a href="http://parts.igem.org/Part:BBa_K3338002">2020 Hannover</a></li>
+
</ul>
+
</div>
+
</div>
+
 
+
<div class="column third_size">
+
<div class="highlight decoration_A_full">
+
<h3>Inspiration: Composite Parts</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 the following examples for Composite Parts on the Registry:</p>
+
<ul>
+
<li><a href="http://parts.igem.org/Part:BBa_K3198007">2019 NUS Singapore </a></li>
+
<li><a href="http://parts.igem.org/Part:BBa_K2932003">2019 Mingdao</a></li>
+
<li><a href="http://parts.igem.org/Part:BBa_K2980009">2019 Tsinghua</a></li>
+
 
+
<li><a href="http://parts.igem.org/Part:BBa_K3407022">2020 TUDelft</a></li>
+
<li><a href="http://parts.igem.org/Part:BBa_K3380500">2020 Edinburgh</a></li>
+
<li><a href="http://parts.igem.org/Part:BBa_K3512042">2020 BITSPilani Goa India</a></li>
+
</ul>
+
</div>
+
</div>
+
 
+
 
+
 
+
<div class="column third_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>iGEM20 SUNY_Oneonta</groupparts>
+
<html>
+
</div>
+
 
+
 
+
 
+
 
+
</html>
+

Revision as of 02:44, 18 October 2021

Parts | iGEM SUNY_Oneonta

Parts


Preparing New Targets

Expanding on the Ca2LF Concept to Develop SNflaPs

In the project Ca2LF, we developed the Flappase assay to detect a single nucleotide polymorphism (SNP) in one gene, the beta-casein gene. The detection of the SNP would only tell us what version of the beta-casein allele is present, A1 or A2. For this year’s project we wanted to expand the usefulness of our genetic testing system. We decided to expand our system to be used to characterize the genetic profile of a cow on a variety of different traits so that farmers could make informed decisions regarding a variety of advantageous and deleterious traits when breeding their cows.

Identifying potential target genes

We began by interviewing two experts in cattle genetics and breeding, Dr.’s Dechow and Huson. During this interview, we learned about some genetic conditions that are not desirable in cattle, such as diseases, conditions that negatively impact fertility, and physical traits (for example, being horned) that farms routinely attempt to breed out of their herds. We also learned about genetic traits that are advantageous and routinely selected for by farmers when breeding, including genes involved in promoting fertility, milk production, and milk composition. We compiled a list of these genes and researched their different alleles (Table 1).

TABLE 1 HERE

Another important piece of feedback we received from the interviews with Drs Dechow and Huson is that most alleles are created by multiple SNPs, or larger changes to the gene, such as insertions, deletions, inversions, or duplications. So, to be useful, our SNflaPs genetic testing system needs to detect multiple types of polymorphisms. We decided to focus our efforts on selecting a few genes, each of which has a different type of polymorphism, to serve as proof of concept that the Flappase-based detection system can discriminate between these alleles.

Table 2. Genes selected for proof-of-concept testing of the Flappase assay for detecting polymorphisms. The genes selected for each contain different polymorphisms, or multiple SNPs found in close, medium, or far proximity to each other.

TABLE 2 HERE

When deciding which genes to use for testing the detection system we used the following criteria:

  1. The length of any polymorphism should be less than 5,000 bp.
  2. If multiple SNPs are to be detected, the distance between these should be enough to fit both the oligos, as well as accommodate the Flappase protein that is approx. 22 nucleotides and 75 Angstroms apart (See modeling page).
  3. For initial testing, any gene selected should be of sufficient length to be synthesized for the creation of positive control DNAs.

Based on these characteristics, we decided to begin by pursuing LRP4 and APOB as model genes.

Designing and cloning new targets and oligos for use with the Flappase system

New Target #1- LRP4

The LRP4 gene encodes for LDL receptor related protein 4 (3). Two well-characterized allelic variants of this gene have been identified, the normal (wildtype) version, and a syndactylous version. Inheritance of the syndactylous version leads to congenital syndactyly. This condition, also known as mulefoot, refers to the fusion or non-division of the two developed digits of the bovine foot (4).

Sequence variation between the normal and syndactyl alleles of LRP4. The two versions differ by two SNPs, where nucleotides CG are substituted by AT at positions 4863 and 4864.

Figure 3: Sequence variation between the normal and syndactyl alleles of LRP4. The two versions differ by two SNPs, where nucleotides CG are substituted by AT at positions 4863 and 4864.

Parts Registry