modMine (Nucleic Acids Research, 2011) is a database paper from the modENCODE Data Coordination Center describing an InterMine-based data warehouse that makes the NHGRI modENCODE consortium's genomic data for D. melanogaster and C. elegans searchable, integrated, and programmatically accessible. The central claim is that metadata-rich integration β not just raw data hosting β enables researchers to pinpoint relevant experiments among thousands and run fine-grained queries linking modENCODE results with model-organism resources .
modMine is built on the InterMine data warehousing system, chosen for scalability, flexible querying, list tools, user workspaces, and RESTful APIs. Data flow: producer labs β DCC vetting β Chado database (chadoxml transfer) β modMine integration of ~70 external sources (XML, FASTA, GFF3, key-value formats; 1 MB to 50 GB per source; processing 50 s to ~18 h). Full builds take ~1 week on a 4Γ dual-core 3.0 GHz AMD Opteron, 32 GB RAM server; the PostgreSQL database is 325 GB pre-indexing and ~1 TB post-indexing . Metadata capture uses BIR-TAB drawing on MIAME, MINSEQE, and MIBBI standards; controlled vocabularies (Sequence Ontology, MGED Ontology, model-database gene names, stock center strains, DGRC cell lines) enable the fine-grained search that is the paper's key innovation.
| Feature | Reported evidence |
|---|---|
| Metadata experiment search | Query 'chip-chip AND ctcf AND 0-12' returns two CTCF ChIP-chip experiments (0β12 h embryos) |
| Template searches | 1666 ChIP-bound regions upstream of 540 C. elegans TF genes (GO:0003700) found via 12 L2 ChIP-seq submissions |
| List analysis | Interactive expression heatmaps (CanvasXpress), GO/publication/protein-domain enrichment |
| Region search | Extract features from user-defined chromosomal spans; replication-origin vs random-region comparison example |
| Programmatic access | RESTful web services; Perl/Python/Ruby/Java/JS client libraries; automatic code generation; Galaxy export |
| Interactive networks | Cytoscape Web versions of integrative-paper regulatory figures with XML/SIF export |
External data integrated include WormBase/FlyBase annotations, GO, phenotypes, RNAi screens, Reactome pathways, PubMed mappings, IntAct/BioGRID interactions, UniProt/InterPro protein data, and TreeFam orthology β enabling cross-resource queries the raw modENCODE data alone could not support .
Strengths: (1) Metadata discipline (MIAME/MINSEQE/BIR-TAB) is genuinely load-bearing β the fine-grained search described depends on it, and the DCC vetting pipeline is documented in a companion paper . (2) Dual biologist/bioinformatician interfaces with real code generation lower barriers. (3) Archived releases (e.g. release-17) and planned Amazon EC2 deployment support long-term reproducibility.
Limitations and blind spots: (1) Source conflicts are resolved by field-specific priority rules β reasonable but unvalidated; no error rate on integrated annotations is reported. (2) A 9-month embargo delays independent verification of new data. (3) No usage statistics, performance benchmarks, or query-latency numbers are given beyond build times. (4) Downstream data-quality issues in modENCODE itself are not addressed: a systematic modENCODE comparison showed ChIP-seq vs ChIP-chip cross-platform correlation of only ~0.41 despite intra-platform reproducibility of ~0.82β0.85, with input DNA variability substantially affecting peak calls . modMine makes such heterogeneous data searchable but does not quantify or flag cross-technology discordance to users. (5) The paper predates current FAIR/DOIs-for-every-dataset norms; persistence relies on institutional commitment, though the EC2 plan mitigates this.
modMine seeded the InterMine ecosystem (RatMine, YeastMine, TargetMine, interMOD interoperability) described in the paper, and InterMine remains active infrastructure. The claims are falsifiable: if template/list queries failed to reproduce known upstream binding regions or if integration priority rules introduced systematic misannotation detectable by independent curation, the usefulness claim would fail. The paper's own forward-looking limitations (search result rearrangement, GFF3 region input, interMOD cross-database browsing) define its honest boundary at publication. One hidden assumption deserves scrutiny: that controlled-vocabulary metadata quality is uniform across 11 primary projects β the paper asserts it but provides no inter-lab consistency audit. Confidence in the core architecture claims is high (strong primary evidence, explicit infrastructure details); confidence in unaddressed data-quality messaging is a moderate concern, not a refutation.
Know what changed, what holds up, and what remains uncertain. Every Friday. No ads.