Difference between revisions of "Team:Arizona State/Collaborations"

Line 8: Line 8:
  
 
<h2>2017 Austin LASA iGEM (Austin_UTexas_LASA) Collaboration with ASU iGEM</h2>
 
<h2>2017 Austin LASA iGEM (Austin_UTexas_LASA) Collaboration with ASU iGEM</h2>
 +
<p>October 1st: Neha from LASA Austin contacts the ASU iGEM team searching for a collaboration regarding cloning vectors</p>
 +
<p>October 2nd: ASU iGEM responds offering assistance in developing a cloning strategy for them</p>
 +
<p>October 2nd: LASA iGEM responds with more information regarding the assistance needed to assemble multiple genes onto a single plasmid using a one-step cloning scheme.</p>
 +
<p>October 2nd: ASU iGEM responds by agreeing to help design a strategy for cloning, and asks for more information regarding sequences and genes.</p>
 +
<p>October 5th: LASA iGEM emails ASU iGEM with two plasmid sequences, their current strategy, cloning issues, and what they are trying to assemble.</p>
  
<p>October 1st: Neha from LASA Austin contacts the ASU iGEM team searching for a collaboration regarding cloning vectors </p>
+
<p><a href="https://benchling.com/s/seq-DOUQcR4Jeyh4FsbQznoQ"> Sequence 1</a></p>
  
<p>October 2nd: ASU iGEM responds offering assistance in developing a cloning strategy for them</p>
+
<p><a href=" https://benchling.com/s/seq-SSx0zkHaEAs5TEtHO1yM"> Sequence 2</a></p>
  
<p>October 2nd: LASA iGEM responds with more information regarding the assistance needed to assemble multiple genes onto a single plasmid using a one-step cloning scheme. </p>
 
  
<p>October 2nd: ASU iGEM responds by agreeing to help design a strategy for cloning, and asks for more information regarding sequences and genes. </p>
+
<p>October 6th: ASU iGEM responds asking for preferences regarding the cloning, such as exact parts to include, and order of the two cloned genes.</p>
 +
<p>October 7th: LASA iGEM responds answering the questions asked previously</p>
 +
<p>October 9th: ASU iGEM sends benchling pages corresponding to primers needed for cloning, along with sequences generated, vector to use, and an explanation of strategy. ASU iGEM offered to send the backbone vector needed for the cloning.</p>
  
<p>October 5th: LASA iGEM emails ASU iGEM with two plasmid sequences, their current strategy, cloning issues, and what they are trying to assemble.</p>
+
<p><a href=" : https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-PKKDynto-pcp-forward/edit"> PCP.Forward </a></p>
 +
 
 +
<p><a href=" https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-IwbIRC8m-pcp-reverse/edit"> PCP.Reverse </a></p>
 +
 
 +
 
 +
<p><a href=" https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-sFeSbWuc-vcp-forward/edit"> VCP.Forward </a></p>
 +
 
 +
<p><a href=" https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-9tiEWZUc-vcp-reverse/edit"> VCP.Reverse </a></p>
  
<P>Sequence 1<a href="https://benchling.com/s/seq-DOUQcR4Jeyh4FsbQznoQ"></p>
+
<p><a href=" https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-tTaQbXGT-pcp-pcr-product/edit"> PCP PCR Product </a></p>
  
<p>Sequence 2 <a href="https://benchling.com/s/seq-SSx0zkHaEAs5TEtHO1yM"></p>
 
  
<p>October 6th: ASU iGEM responds asking for preferences regarding the cloning, such as exact parts to include, and order of the two cloned genes. </p>
+
<p><a href="https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-mFU1Bm9f-vcp-pcr-product/edit"> VCP PCR Product </a></p>
  
<p>October 7th: LASA iGEM responds answering the questions asked previously </p>
 
  
<p>October 9th: ASU iGEM sends benchling pages corresponding to primers needed for cloning, along with sequences generated, vector to use, and an explanation of strategy. ASU iGEM offered to send the backbone vector needed for the cloning. </p>
 
  
<p>PCP.Forward <a href= "https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-PKKDynto-pcp-forward/edit"> </p>
+
<p><a href="https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-L3nEdQ4Z-pet28vcp-pcp/edit"> pET28(VCP-PCP) </a></p>
  
<p> PCP.Reverse <a href= "https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-IwbIRC8m-pcp-reverse/edit"> </p>
 
  
<p>VCP.Forward <a href= "https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-sFeSbWuc-vcp-forward/edit"></p>
 
  
<p> VCP.Reverse <a href= "https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-9tiEWZUc-vcp-reverse/edit"></p>
+
<p><a href="https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-rgoQvXbf-pet28/edit"> pET28 vector </a></p>
  
<p> PCP PCR Product: <a href= "https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-tTaQbXGT-pcp-pcr-product/edit" >  </p>
 
<p>VCP PCR Product: <a href= "https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-mFU1Bm9f-vcp-pcr-product/edit" ></p>
 
  
<p> pET28 vector <a href="https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-rgoQvXbf-pet28/edit"></a> </p>
 
  
<p> pET28(VCP-PCP) <a href= "https://benchling.com/stekel/f/CT3KZ6fN-austin_utexas_lasa/seq-L3nEdQ4Z-pet28vcp-pcp/edit"> </p>
+
<p>October 10th: LASA iGEM responds by asking for the vector to be sent, and acknowledging the strategy as viable in their lab with needed reagents.</p>
 +
<p>October 11th: ASU iGEM mails pET28 vector to LASA iGEM needed for cloning</p>
  
<p>October 10th: LASA iGEM responds by asking for the vector to be sent, and acknowledging the strategy as viable in their lab with needed reagents.
+
<p>October 16th: LASA iGEM received pET28 vector</p>
October 11th: ASU iGEM mails pET28 vector to LASA iGEM needed for cloning </p>
+
  
<p>October 16th: LASA iGEM received pET28 vector </p>
+
<p>October XX: Cloning results?</p>
  
<p>October XX: Cloning results? </p>
 
  
 
</div>
 
</div>

Revision as of 23:53, 27 October 2017