Difference between revisions of "Team:NUS Singapore-A/shadow/Improve"

Line 18: Line 18:
  
  
 +
<body>
 
<div class="inner-border" style="border-top: none;"><div class="all-wrapper">
 
<div class="inner-border" style="border-top: none;"><div class="all-wrapper">
  
 
   <img src="https://static.igem.org/mediawiki/2018/0/0c/T--NUS_Singapore-A--Parts_header_C.png" class="modelling-header">
 
   <img src="https://static.igem.org/mediawiki/2018/0/0c/T--NUS_Singapore-A--Parts_header_C.png" class="modelling-header">
<groupparts>iGEM18 NUS_Singapore-A</groupparts>
+
 
 
   <h1>OVERVIEW</h1>
 
   <h1>OVERVIEW</h1>
 
   <div class="row">
 
   <div class="row">
Line 52: Line 53:
 
   <h1>PARTS STUFFS</h1>
 
   <h1>PARTS STUFFS</h1>
 
</div>
 
</div>
 +
 +
 +
</body>
 +
 +
</html>
 +
 +
      <groupparts>iGEM18 NUS_Singapore-A</groupparts>
 +
 +
 +
<html>
 +
 +
<body>
  
 
<div class="inner-border" style="border-top: none;">
 
<div class="inner-border" style="border-top: none;">
Line 101: Line 114:
  
 
</div>
 
</div>
     
 
 
 
  
 
</body>
 
</body>
 
</html>
 
 
 
 
  
 
<script>
 
<script>

Revision as of 18:29, 12 October 2018

CONNECT WITH US

OVERVIEW

Each team will make new parts during iGEM and will submit them to the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The <groupparts> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox. 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.


Note that parts must be documented on the Registry. This page serves to showcase the parts you have made. 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.

Headers and headers for days


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. Remember, you don't need to send us the DNA sample before you create an entry for a part on the Registry. (However, you do need to send us the DNA sample before the Jamboree. If you don't send us a DNA sample of a part, that part will not be eligible for awards and medal criteria.)ADD PARTS


Adding parts to the registry


You can add parts to the Registry at our Add a Part to the Registry link.





PARTS STUFFS

      <groupparts>iGEM18 NUS_Singapore-A</groupparts>





ALL TITLES IN CAPS

We have a created a collection of well documented parts that can help you get started.

You can also take a look at how other teams have documented their parts in their wiki:

The information needed to initially create a part on the Registry is:

  • Part Name
  • Part type
  • Creator
  • Sequence
  • Short Description (60 characters on what the DNA does)
  • Long Description (Longer description of what the DNA does)
  • Design considerations

We encourage you to put up much more information as you gather it over the summer. If you have images, plots, characterization data and other information, please also put it up on the part page.

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.