Biological Parts Submitted

From our library of gene constructs shown above, we have selected twelve parts to submit to the Registry of Standard Biological Parts. The twelve that were submitted are tabulated below, and are also labelled on the diagram above. These parts all contain a TEF1 promoter, YFP gene downstream, and a variable number of repressor binding sites (x1, x3) in the 5' UTR region. There are six difference repressor binding site sequences--three that are 16 nucleotides long, and three that are 20 nucleotides long--which can be targeted with our library of repressor constructs (TALEs and sgRNA-dCas9) shown in the diagram. These repressor constructs were not submitted. Click on the part number below to see the documentation on the Registry.

Data For Our Favorite New Parts

1. [http://parts.igem.org/wiki/index.php?title=Part:BBa_K1204013 Main Page] -

Reporter with 1x16A Repressor Binding Sequence, BBa_K1204013 : short description

1. [http://parts.igem.org/wiki/index.php?title=Part:BBa_K1204014 Main Page] -

Reporter with 3x16A Repressor Binding Sequence, BBa_K1204014 ?? : short description

1. [http://parts.igem.org/wiki/index.php?title=Part:BBa_K1204016 Main Page] -

Reporter with 1x20A Repressor Binding Sequence, BBa_K1204016 ?? : short description

<groupparts>iGEM013 Duke</groupparts>

Sample Data Page

An important aspect of the iGEM competition is the use and creation of standard biological parts. Each team will make new parts during iGEM and will place them in the [http://partsregistry.org Registry of Standard Biological Parts]. The iGEM software provides an easy way to present the parts your team has created . The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox. Note that if you want to document a part you need to document it on the [http://partsregistry.org Registry], not on your team wiki.

Remember that the goal of proper part documentation is to describe and define a part such that it can be used without a need to refer to the primary literature. The next iGEM team 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.