geo-connectorlisted

# Search and Cross-Reference NCBI GEO with ENCODE ## When to Use - User wants to find complementary datasets in NCBI GEO to supplement ENCODE data - User asks about "GEO", "Gene Expression Omnibus", "supplementary data", or "find related datasets" - User needs to cross-reference ENCODE experiments with GEO series for additional replicates or conditions - User wants to link ENCODE accessions to GEO/SRA identifiers for data sharing or citation - Example queries: "find GEO datasets for pancreatic islet RNA-seq", "link this ENCODE experiment to GEO", "search GEO for complementary ATAC-seq data" Query the Gene Expression Omnibus programmatically to find complementary datasets, cross-reference ENCODE experiments, and download metadata. ## Scientific Rationale **The question**: "What additional expression or epigenomic datasets exist in GEO that complement my ENCODE analysis?" GEO hosts >200,000 series across all organisms and assay types. Many ENCODE experiments are deposited in GEO as secondary archives (ENCODE Portal is primary). GEO also contains vast amounts of non-ENCODE data — disease cohorts, perturbation experiments, time courses — that complement ENCODE's reference epigenomes. ### GEO ↔ ENCODE Relationship - ENCODE processed data is deposited at GEO as standard GSE submissions - Raw sequencing data goes to SRA (linked from both GEO and ENCODE) - The ENCODE Portal is canonical; GEO is secondary archive - GEO accessions are stored in ENCODE's `dbxrefs` field as `GEO: