Team:LCG-UNAM-Mexico/Description
From 2009.igem.org
(Difference between revisions)
EnriquePaz (Talk | contribs) (→Delivery) |
|||
Line 30: | Line 30: | ||
=='''Delivery'''== | =='''Delivery'''== | ||
- | ===''' | + | ==='''Background'''=== |
- | + | *P2-P4 bacteriophages | |
+ | *P4 genome structure | ||
+ | *P4 sid mutation | ||
+ | *Cos sites | ||
+ | Bacteriophage P2 and P4 are double stranded DNA enterobacteria virus. Phage P4 is a satellite phage because it is dependent on the machinery of P2. Sometimes, it is called a "parasite phage", since it takes over the elements of P2 and leaves its "host phage" practically neutralized. About 100 P4 are produced for each P2 particle **** Esto dependeria de la cepa no ¿?? ***** . There are several interesting features of the P4 genome, including transactivation zones (the genes that respond to the presence of P2 along with P4 and vice versa) that function in domination of the late P2 genes. Important elements of this kind are gene P4 delta and P2 ogr, which work synergistically together in activating P2 genes. Given these interesting properties, P4 has been exhaustively studied. | ||
- | + | We can divide P4 genome into two main regions: the essential and non-essential region. The essential region contains operons intended for replication and hijacking of P2, and the non-essential region contains accessory genes for special situations as lambda infections, as well as the integrase and attachment site. Removing the latter two would result in a permanent plasmid-state P4 with a unique multicopy replication system. | |
+ | As P4 thoroughly depends on P2 for capsid, tail and lysis functions, the difference in size between both genomes (+- 33kb for P2 whereas +-11kb for P4) came up to attention. P4 protein sid is able to scaffold a smaller capsid with the same structural proteins as P2. A sid mutant was found that made P4 pack its genome inside bigger-sized capsids, which can hold up to 1, 2 or 3 copies of its genome. The extra genome copies could be “something eles”, it means P4 can transport over 20 kbs of extra foreign DNA if atached to its genome. | ||
- | + | Another important point is that the signal for the encapsidation is located in the “cos” sites. It means that you only need this region, (about 20 pb, but you increase the efficence of transduction with a region of more that 100 pb), to encapsidate a double DNA strand without regarding of the sequence in adition to the cos sites. | |
- | + | ==='''Main objective and relevance'''=== | |
+ | This part of the project consists in a system for transduction of synthetic constructions. | ||
- | The | + | The system starts with a modified bacteriophage P4 genome. This viral vector will be modified to be compatible with iGEM standard for biobrick assembly. Also, because the remotion of non-essential regio non its genome and the use of a natural mutant of this phage P4sid1, the capsid will be able to suport up to 25 kbs of synthetic DNA. Another remarkable characteristic that we expect in our system according to litterature, is the ability to function in an inusual host range than includes E.Coli, Klebsiella, Serratia and Rhizobium. |
+ | Second part of the system is the production under our regulation of these P4 bacteriophages with the synthetic constructions. The idea is to create an E. Coli as a productor strain of this phages that becomes production of P4 only under a stimulus. So you only will need to transform this strain with the viral vector + your construction and the production of the P4 phages may become only when an activation of two main regulators in the system. | ||
- | + | In conclusion we propose a complete, standardized and controllable system for production of P4 bacteriophages than can carry over 25 kbs of synthetic DNA and can transduce an inusual host range of bacteria. Another interesting point is that the relation between bacteria and their bacteriophages is quite rich and dynamic so hacking this system to now control it has been really entertaining. | |
+ | As you can imagin it mean san important and powerfull tool in Synthetic Biology with a great potencial for expansions and applications. | ||
- | |||
+ | ==='''P4 Modifications'''=== | ||
+ | |||
+ | The main objectives of modifing P4 genome are: | ||
+ | |||
+ | *Standardize P4 by removing forbiden restriction sites (EcoRI, XbaI, SspeI, PstI). | ||
+ | *Add preffix and suffix so you can clone biobricks like in any other standard plasmid. | ||
+ | *Remove the integrase from the genome so P4 will be maintained as a plasmid in the bacteria host. | ||
+ | *Remotion of the non-essential region. Together the use of P4sid1 variant means the ability to carry about 25 kbs of *synthetic DNA. | ||
+ | *Adding an antibiotic resistance. | ||
+ | *Adding transcripcional terminators bordering the cloning region. | ||
+ | *Adding sequences for primering with universal primers. | ||
+ | |||
+ | The main goal is the construction of a new vector for iGEM with the peculiarity of being part of a system for transduction of biobricks and synthetic devices in bacteria. | ||
+ | |||
+ | |||
+ | ==='''P4sid1-standardized production'''=== | ||
+ | |||
+ | We thought of a way to overproduce our viral particles without being forced to infect with P2 or getting P2 particles as a byproduct. The solution planned was to construct an E. coli strain containing all the useful genes for P4 in P2 (capsid, tail and lysis operons). In addition to these genes, the helper would also contain the main P2 transactivators (cox and ogr) under a lac operator. This way, after we transform the helper cell with our desired P4 plasmid, we would decide when to promote lysis of the helper bacteria and P4 stock production by adding IPTG. Now we have our biobrick assembled inside ready-to-use phages that can deliver their genome to wildtype bacteria. | ||
+ | |||
+ | We also have biobricked the cos sites of P4. This biobrick should be coloned in any vector with your construction. If you transform the productor strain of P4 with this vector then you infect with P4 you will have as a result some P4 phages and some of your vectors with the P4cos sites inside a capsid. It means you can encapsidate up to 33 kbs with this system. Until your production is not pure you can add a marker in the plasmid like an antibiotic resistance so after infection you select the colonies with the plasmid and not the natural P4. | ||
+ | |||
+ | ==='''P4 infection – transduction – delivery'''=== | ||
+ | |||
+ | The process of infection requires a protocol to increase efficence. The protocol we have used are: | ||
+ | |||
+ | * | ||
+ | * | ||
+ | * | ||
+ | |||
+ | For transduction, an important characteristic of P4 bacteriophage is its unusual range of infection. In litterature is reported that this unusal range includes Klebsiella, E. Coli, Serratia and Rhizobium. | ||
+ | |||
+ | |||
+ | ==='''Applications'''=== | ||
+ | |||
+ | Applications and extensions are many. Two of them we propose for this year are: | ||
+ | |||
+ | 1) A defense system agains another phages for E. Coli delivered by P4phage. | ||
+ | The idea we love is the hacking of one system that is harmful (if you are a bacteria), and use it then for your own protection agains similar systems. | ||
+ | |||
+ | 2) Refinated phage therapy. | ||
+ | In adition of protection of bacteria we propose this system for protecting humans. This by creating an important tool for a refinated phage teraphy were you not only kill bacterias with phages *** but you insert a program inside the pathogen. Its an advantage in cases were you need extra control, in time for example or a program to degrade toxins befote killing the pathogen so toxins are not Spreads in the organism avoiding an increased immune response. | ||
+ | |||
+ | As a first step in this area we have adapted the kamikazee system to detect phatogens instead of phages. The paghes to detect is EHEC, by detecting its molecule for quorum sensing, the kamikazee construction will kill quickly this cell. | ||
+ | |||
+ | 3) Storage of information. | ||
+ | We like the analogy of this modifiedP4 with an USB *** memoria, wehere you can strorage information or a complete program and then just plug it in another machine that will read the information or execute the program. We are sure it is a fascinating concept with many applications. | ||
+ | |||
+ | 4) … | ||
+ | |||
+ | <br> | ||
=='''Delivery'''== | =='''Delivery'''== |
Revision as of 11:53, 20 October 2009