Summary: ATP dependent DNA ligase C terminal region
Pfam includes annotations and additional family information from a range of different sources. These sources can be accessed via the tabs below.
The Pfam group coordinates the annotation of Pfam families in Wikipedia, but we have not yet assigned a Wikipedia article to this family. If you think that a particular Wikipedia article provides good annotation, please let us know.
This tab holds the annotation information that is stored in the Pfam database. As we move to using Wikipedia as our main source of annotation, the contents of this tab will be gradually replaced by the Wikipedia tab.
ATP dependent DNA ligase C terminal region Provide feedback
This region is found in many but not all ATP-dependent DNA ligase enzymes ( EC:220.127.116.11). It is thought to constitute part of the catalytic core of ATP dependent DNA ligase .
Internal database links
|Similarity to PfamA using HHSearch:||DNA_ligase_OB_2 DNA_ligase_C|
This tab holds annotation information from the InterPro database.
InterPro entry IPR012309
DNA ligase (polydeoxyribonucleotide synthase) is the enzyme that joins two DNA fragments by catalysing the formation of an internucleotide ester bond between phosphate and deoxyribose. It is active during DNA replication, DNA repair and DNA recombination. There are two forms of DNA ligase, one requires ATP (EC), the other NAD (EC), the latter being restricted to eubacteria. Eukaryotic, archaebacterial, viral and some eubacterial DNA ligases are ATP-dependent. The first step in the ligation reaction is the formation of a covalent enzyme-AMP complex. The co-factor ATP is cleaved to pyrophosphate and AMP, with the AMP being covalently joined to a highly conserved lysine residue in the active site of the ligase. The activated AMP residue is then transferred to the 5'phosphate of the nick, before the nick is sealed by phosphodiester-bond formation and AMP elimination [PUBMED:1988940,PUBMED:1497311].
Vertebrate cells encode three well-characterised DNA ligases (DNA ligases I, III and IV), all of which are related in structure and sequence. With the exception of the atypically small PBCV-1 viral enzyme, two regions of primary sequence are common to all members of the family. The catalytic region comprises six conserved sequence motifs (I, III, IIIa, IV, V-VI), motif I includes the lysine residue that is adenylated in the first step of the ligation reaction. The function of the second, less well-conserved region is unknown. When folded, each protein comprises of two distinct sub-domains: a large amino-terminal sub-domain ('domain 1') and a smaller carboxy-terminal sub-domain ('domain 2'). The ATP-binding site of the enzyme lies in the cleft between the two sub-domains. Domain 1 consists of two antiparallel beta sheets flanked by alpha helices, whereas domain 2 consists of a five-stranded beta barrel and a single alpha helix, which form the oligonucleotide-binding fold [PUBMED:1437556, PUBMED:11983065].
The mapping between Pfam and Gene Ontology is provided by InterPro. If you use this data please cite InterPro.
|Molecular function||DNA ligase (ATP) activity (GO:0003910)|
|Biological process||DNA repair (GO:0006281)|
|DNA recombination (GO:0006310)|
Below is a listing of the unique domain organisations or architectures in which this domain is found. More...
The graphic that is shown by default represents the longest sequence with a given architecture. Each row contains the following information:
- the number of sequences which exhibit this architecture
a textual description of the architecture, e.g. Gla, EGF x 2, Trypsin.
This example describes an architecture with one
Gladomain, followed by two consecutive
EGFdomains, and finally a single
- a link to the page in the Pfam site showing information about the sequence that the graphic describes
- the UniProt description of the protein sequence
- the number of residues in the sequence
- the Pfam graphic itself.
Note that you can see the family page for a particular domain by clicking on the graphic. You can also choose to see all sequences which have a given architecture by clicking on the Show link in each row.
Finally, because some families can be found in a very large number of architectures, we load only the first fifty architectures by default. If you want to see more architectures, click the button at the bottom of the page to load the next set.
Loading domain graphics...
The OB (oligonucleotide/oligosaccharide binding) was defined by Murzin . The common part of the OB-fold, has a five-stranded beta-sheet coiled to form a closed beta-barrel. This barrel is capped by an alpha-helix located between the third and fourth strands .
The clan contains the following 107 members:BOF BRCA-2_OB1 BRCA-2_OB3 CcmE CDC13_N Cdc13_OB2 CDC24_OB1 CDC24_OB2 CDC24_OB3 CSD CSD2 CusF_Ec CysA_C_terminal DNA_ligase_A_C DNA_ligase_C DNA_ligase_OB DNA_ligase_OB_2 DNA_pol_D_N DUF1344 DUF1449 DUF2110 DUF223 DUF2815 DUF3127 DUF3217 DUF3299 DUF4539 DUF961 EFP eIF-1a eIF-5a Elong-fact-P_C EutN_CcmL EXOSC1 FbpC_C_terminal Fimbrial_PilY2 GlcV_C_terminal Gp138_N gp32 HIN ID MCM_OB mRNA_cap_C MRP-S35 NfeD NigD_N NlpE_C OB_aCoA_assoc OB_Dis3 OB_MalK OB_NTP_bind OB_RNB PCB_OB Phage_DNA_bind Phage_SSB Pol_alpha_B_N POT1 POT1PC Prot_ATP_ID_OB Prot_ATP_OB_N RecG_wedge RecJ_OB RecO_N RecO_N_2 Rep-A_N Rep_fac-A_3 Rep_fac-A_C REPA_OB_2 Rho_RNA_bind Ribosom_S12_S23 Ribosomal_L2 Ribosomal_S17 Ribosomal_S28e Ribosomal_S4e RMI1_C RMI1_N RMI2 RNA_pol_Rbc25 RNA_pol_Rpb8 RNA_pol_RpbG RNase_II_C_S1 RPA43_OB Rrp44_CSD1 Rrp44_S1 RsgA_N RuvA_N S1 S1-like S1_2 SfsA_N SSB ssDBP Stn1 TEBP_beta Ten1 Ten1_2 TOBE TOBE_2 TOBE_3 TPP1 TRAM TRAM_2 tRNA_anti-codon tRNA_anti-like tRNA_anti_2 tRNA_bind TTC5_OB
We store a range of different sequence alignments for families. As well as the seed alignment from which the family is built, we provide the full alignment, generated by searching the sequence database (reference proteomes) using the family HMM. We also generate alignments using four representative proteomes (RP) sets, the UniProtKB sequence database, the NCBI sequence database, and our metagenomics sequence database. More...
There are various ways to view or download the sequence alignments that we store. We provide several sequence viewers and a plain-text Stockholm-format file for download.
We make a range of alignments for each Pfam-A family:
- the curated alignment from which the HMM for the family is built
- the alignment generated by searching the sequence database using the HMM
- Representative Proteomes (RPs) at 15%, 35%, 55% and 75% co-membership thresholds
- alignment generated by searching the UniProtKB sequence database using the family HMM
- alignment generated by searching the NCBI sequence database using the family HMM
- alignment generated by searching the metagenomics sequence database using the family HMM
You can see the alignments as HTML or in three different sequence viewers:
- a Java applet developed at the University of Dundee. You will need Java installed before running jalview
- an HTML page showing the whole alignment.Please note: full Pfam alignments can be very large. These HTML views are extremely large and often cause problems for browsers. Please use either jalview or the Pfam viewer if you have trouble viewing the HTML version
- an HTML-based representation of the alignment, coloured according to the posterior-probability (PP) values from the HMM. As for the standard HTML view, heatmap alignments can also be very large and slow to render.
You can download (or view in your browser) a text representation of a Pfam alignment in various formats:
You can also change the order in which sequences are listed in the alignment, change how insertions are represented, alter the characters that are used to represent gaps in sequences and, finally, choose whether to download the alignment or to view it in your browser directly.
You may find that large alignments cause problems for the viewers and the reformatting tool, so we also provide all alignments in Stockholm format. You can download either the plain text alignment, or a gzipped version of it.
We make a range of alignments for each Pfam-A family. You can see a description of each above. You can view these alignments in various ways but please note that some types of alignment are never generated while others may not be available for all families, most commonly because the alignments are too large to handle.
1Cannot generate PP/Heatmap alignments for seeds; no PP data available
Key: available, not generated, — not available.
Format an alignment
We make all of our alignments available in Stockholm format. You can download them here as raw, plain text files or as gzip-compressed files.
You can also download a FASTA format file containing the full-length sequences for all sequences in the full alignment.
HMM logos is one way of visualising profile HMMs. Logos provide a quick overview of the properties of an HMM in a graphical form. You can see a more detailed description of HMM logos and find out how you can interpret them here. More...
If you find these logos useful in your own work, please consider citing the following article:
This page displays the phylogenetic tree for this family's seed alignment. We use FastTree to calculate neighbour join trees with a local bootstrap based on 100 resamples (shown next to the tree nodes). FastTree calculates approximately-maximum-likelihood phylogenetic trees from our seed alignment.
Note: You can also download the data file for the tree.
Curation and family details
This section shows the detailed information about the Pfam family. You can see the definitions of many of the terms in this section in the glossary and a fuller explanation of the scoring system that we use in the scores section of the help pages.
|Number in seed:||145|
|Number in full:||9664|
|Average length of the domain:||102.90 aa|
|Average identity of full alignment:||26 %|
|Average coverage of the sequence by the domain:||15.46 %|
|HMM build commands:||
build method: hmmbuild -o /dev/null HMM SEED
search method: hmmsearch -Z 45638612 -E 1000 --cpu 4 HMM pfamseq
|Family (HMM) version:||15|
|Download:||download the raw HMM for this family|
Weight segments by...
Change the size of the sunburst
selected sequences to HMM
a FASTA-format file
- 0 sequences
- 0 species
This visualisation provides a simple graphical representation of the distribution of this family across species. You can find the original interactive tree in the More....
This chart is a modified "sunburst" visualisation of the species tree for this family. It shows each node in the tree as a separate arc, arranged radially with the superkingdoms at the centre and the species arrayed around the outermost ring.
How the sunburst is generated
The tree is built by considering the taxonomic lineage of each sequence that has a match to this family. For each node in the resulting tree, we draw an arc in the sunburst. The radius of the arc, its distance from the root node at the centre of the sunburst, shows the taxonomic level ("superkingdom", "kingdom", etc). The length of the arc represents either the number of sequences represented at a given level, or the number of species that are found beneath the node in the tree. The weighting scheme can be changed using the sunburst controls.
In order to reduce the complexity of the representation, we reduce the number of taxonomic levels that we show. We consider only the following eight major taxonomic levels:
Colouring and labels
Segments of the tree are coloured approximately according to their superkingdom. For example, archeal branches are coloured with shades of orange, eukaryotes in shades of purple, etc. The colour assignments are shown under the sunburst controls. Where space allows, the name of the taxonomic level will be written on the arc itself.
As you move your mouse across the sunburst, the current node will be highlighted. In the top section of the controls panel we show a summary of the lineage of the currently highlighed node. If you pause over an arc, a tooltip will be shown, giving the name of the taxonomic level in the title and a summary of the number of sequences and species below that node in the tree.
Anomalies in the taxonomy tree
There are some situations that the sunburst tree cannot easily handle and for which we have work-arounds in place.
Missing taxonomic levels
Some species in the taxonomic tree may not have one or more of the main eight levels that we display. For example, Bos taurus is not assigned an order in the NCBI taxonomic tree. In such cases we mark the omitted level with, for example, "No order", in both the tooltip and the lineage summary.
Unmapped species names
The tree is built by looking at each sequence in the full alignment for the family. We take the name of the species given by UniProt and try to map that to the full taxonomic tree from NCBI. In some cases, the name chosen by UniProt does not map to any node in the NCBI tree, perhaps because the chosen name is listed as a synonym or a misspelling in the NCBI taxonomy.
So that these nodes are not simply omitted from the sunburst tree, we group them together in a separate branch (or segment of the sunburst tree). Since we cannot determine the lineage for these unmapped species, we show all levels between the superkingdom and the species as "uncategorised".
Since we reduce the species tree to only the eight main taxonomic levels, sequences that are mapped to the sub-species level in the tree would not normally be shown. Rather than leave out these species, we map them instead to their parent species. So, for example, for sequences belonging to one of the Vibrio cholerae sub-species in the NCBI taxonomy, we show them instead as belonging to the species Vibrio cholerae.
Too many species/sequences
For large species trees, you may see blank regions in the outer layers of the sunburst. These occur when there are large numbers of arcs to be drawn in a small space. If an arc is less than approximately one pixel wide, it will not be drawn and the space will be left blank. You may still be able to get some information about the species in that region by moving your mouse across the area, but since each arc will be very small, it will be difficult to accurately locate a particular species.
The tree shows the occurrence of this domain across different species. More...
We show the species tree in one of two ways. For smaller trees we try to show an interactive representation, which allows you to select specific nodes in the tree and view them as an alignment or as a set of Pfam domain graphics.
Unfortunately we have found that there are problems viewing the interactive tree when the it becomes larger than a certain limit. Furthermore, we have found that Internet Explorer can become unresponsive when viewing some trees, regardless of their size. We therefore show a text representation of the species tree when the size is above a certain limit or if you are using Internet Explorer to view the site.
If you are using IE you can still load the interactive tree by clicking the "Generate interactive tree" button, but please be aware of the potential problems that the interactive species tree can cause.
For all of the domain matches in a full alignment, we count the number that are found on all sequences in the alignment. This total is shown in the purple box.
We also count the number of unique sequences on which each domain is found, which is shown in green. Note that a domain may appear multiple times on the same sequence, leading to the difference between these two numbers.
Finally, we group sequences from the same organism according to the NCBI code that is assigned by UniProt, allowing us to count the number of distinct sequences on which the domain is found. This value is shown in the pink boxes.
We use the NCBI species tree to group organisms according to their taxonomy and this forms the structure of the displayed tree. Note that in some cases the trees are too large (have too many nodes) to allow us to build an interactive tree, but in most cases you can still view the tree in a plain text, non-interactive representation. Those species which are represented in the seed alignment for this domain are highlighted.
You can use the tree controls to manipulate how the interactive tree is displayed:
- show/hide the summary boxes
- highlight species that are represented in the seed alignment
- expand/collapse the tree or expand it to a given depth
- select a sub-tree or a set of species within the tree and view them graphically or as an alignment
- save a plain text representation of the tree
Please note: for large trees this can take some time. While the tree is loading, you can safely switch away from this tab but if you browse away from the family page entirely, the tree will not be loaded.
There are 3 interactions for this family. More...
We determine these interactions using iPfam, which considers the interactions between residues in three-dimensional protein structures and maps those interactions back to Pfam families. You can find more information about the iPfam algorithm in the journal article that accompanies the website.
For those sequences which have a structure in the Protein DataBank, we use the mapping between UniProt, PDB and Pfam coordinate systems from the PDBe group, to allow us to map Pfam domains onto UniProt sequences and three-dimensional protein structures. The table below shows the structures on which the DNA_ligase_A_C domain has been found. There are 14 instances of this domain found in the PDB. Note that there may be multiple copies of the domain in a single PDB structure, since many structures contain multiple copies of the same protein sequence.
Loading structure mapping...