Koch Lab:Protocols/Unzipping constructs/17mer: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 7: Line 7:
The protocol is naturally sub-divided into three parts, followed by a ligation reaction(s).
The protocol is naturally sub-divided into three parts, followed by a ligation reaction(s).


===Anchoring segment===
===[[/Anchoring segment|Anchoring segment]]===
See [[/Anchoring segment|Anchoring segment page]]


===Adapter duplex===
===[[/Adapter duplex|Adapter duplex]]===
See [[/Adapter duplex|Adapter duplex page]]


===Downstream unzipping segment===
===[[/Downstream unzipping segment|Downstream unzipping segment]]===
See [[/Downstream unzipping segment|Downstream unzipping segment page]]


==Ligation, final product formation==
==Ligation, final product formation==


==Optional End capping==
==Optional End capping==
==Pitfalls==


==Tethering protocol==
==Tethering protocol==

Latest revision as of 23:36, 14 June 2008


This is a specific protocol for creating a DNA construct that will unzip the "17-mer" sequence from plasmid pCP681 from Craig Peterson lab. Steve used this plasmid in his 2002 Biophysical Journal Paper (PMID 12124289). Originally designed to study nucleosome remodeling, this repetitive DNA is also convenient for studying site-specific DNA-binding proteins via unzipping, because multiple binding sites can be probed from a single-tether. The method here is easily adaptable to other DNA unzipping segments, if a few pitfalls are considered. The protocol below is a more detailed version of that provided in Koch et al. 2002.

Individual segments

The protocol is naturally sub-divided into three parts, followed by a ligation reaction(s).

Anchoring segment

See Anchoring segment page

Adapter duplex

See Adapter duplex page

Downstream unzipping segment

See Downstream unzipping segment page

Ligation, final product formation

Optional End capping

Pitfalls

Tethering protocol

See this example protocol.