Part:BBa_K3265032

gp460-egfp (Phage201-phi2-1 protein fusion to egfp)

This is a phage protein of unknown function but co-localizes with the transcription machinery of the phage after compartment formation.

Background and Biology

Jumbo ϕKZ-like phages have been the object of many studies in the recent years. This is manly because of the fact that they are bacteriophages of the very lethal, opportunistic and multi antibiotic resistant bacteria Pseudomonas aeruginosa. The phages themselves not being harmfull to humans where considered in phage therapies for illneses that range from the serious lung infections to the less serious "swimmers ear".

During the rave of ϕKZ-like phage discovery and characterization, a new member of the genus was discovered : 201 phi2-1. This virus, although it infects a non pathogenic member of the Pseudomonas family (Pseudomonas Chlororaphis),it still garnered quite a bit of interest from the scientific community.

This interest was based on the fact that when pseudomonas chlororaphis is infected by the 201 phi2-1, a certain amount of the infected population starts showing a nucleus like structure approximately 40min psi (post infection). This nucleus like structure was then identified to be a compartment made by the virus to protect its self from the bacterias natural defences. Crisper cas9 enzymes were shown to have no effect against viral dna when it was in the compartement (insert relevant papers). The compartment was also shown to functionally separate transcription and translation, which forced researchers to belive that this compartment had a way to let transcripts out and let newly translated proteins in. Viral capsids after translation and self assembly are somehow docked onto the outer layer of said compartement, soon after packed with viral protein and dna.

Characterization

Part overview with snapviewer

Sequence and Features

Assembly Compatibility:

• 10
  COMPATIBLE WITH RFC[10]
• 12
  COMPATIBLE WITH RFC[12]
• 21
  INCOMPATIBLE WITH RFC[21]

  Illegal BamHI site found at 1658
  
• 23
  COMPATIBLE WITH RFC[23]
• 25
  INCOMPATIBLE WITH RFC[25]

  Illegal AgeI site found at 2652
  
• 1000
  COMPATIBLE WITH RFC[1000]