/cite-encode

name: cite-encode
description: Generate proper ENCODE citations for publications, grants, and presentations. Use when the user needs to cite ENCODE data, create bibliography entries, write acknowledgment sections, or ensure compliance with ENCODE data use policy.

Cite ENCODE Data Properly

When to Use

• User wants to generate proper citations for ENCODE data, tools, and consortium papers
• User asks about "citing ENCODE", "BibTeX", "references", "bibliography", or "data citation"
• User needs to create a Key Resources Table (STAR Methods) for Cell-family journals
• User wants to export citations in BibTeX, RIS, or other reference manager formats
• Example queries: "cite the ENCODE experiments I used", "generate BibTeX for my tracked experiments", "how do I cite ENCODE in my paper?"

Help the user generate correct citations for ENCODE data following official guidelines. This is the definitive guide to citing ENCODE data in manuscripts, grants, presentations, and supplementary materials.

ENCODE Citation Requirements

ENCODE data use policy requires citing data in publications. Data is freely available with **no embargo** -- unrestricted use upon release. However, proper attribution is both a scientific obligation and a practical necessity: reviewers will check that you have cited data sources correctly, and incomplete citations are a common reason for revision requests.

Step 0: Assess Publication Trust Before Citing

Before citing any study, check its scientific integrity using the **publication-trust** skill. This step catches:

• Formally retracted papers still in circulation
• Key findings contradicted by independent groups
• Expressions of concern from journal editors
• Authors with patterns of problematic publications

If a study scores Trust Level 1 (Compromised) or 2 (Reliability concerns), flag it prominently in the citation list and note the issue. A compromised citation undermines the entire analysis built on it.

# For each paper you plan to cite:
# 1. Get metadata: get_article_metadata(pmids=["PMID"])
# 2. Check retractions: search_articles(query="PMID[PMID] AND Retracted Publication[pt]")
# 3. Check contradictions: search for citing articles with refutation language
# See publication-trust skill for full workflow

Step 1: Identify What to Cite

Determine what the user needs to cite:

Individual Experiments

For specific experiments used in analysis: 1. Track the experiment: `encode_track_experiment(accession="ENCSR...")` 2. Get associated publications: `encode_get_citations(accession="ENCSR...")` 3. The experiment's own publications should be cited

The ENCODE Project Itself

When referencing ENCODE as a data source, cite the consortium papers:

**ENCODE Phase 3 (2020)**:

• ENCODE Project Consortium et al. "Expanded encyclopaedias of DNA elements in the human and mouse genomes." Nature 583, 699-710 (2020). PMID: 32728249. DOI: 10.1038/s41586-020-2493-4

**ENCODE Phase 2 (2012)**:

• ENCODE Project Consortium. "An integrated encyclopedia of DNA elements in the human genome." Nature 489, 57-74 (2012). PMID: 22955616. DOI: 10.1038/nature11247

**Original ENCODE (2007)**:

• ENCODE Project Consortium. "Identification and analysis of functional elements in 1% of the human genome by the ENCODE pilot project." Nature 447, 799-816 (2007). PMID: 17571346. DOI: 10.1038/nature05874

Specific Data Standards

When your methods rely on ENCODE standards:

• ChIP-seq guidelines: Landt et al. "ChIP-seq guidelines and practices of the ENCODE and modENCODE consortia." Genome Res 22, 1813-1831 (2012). PMID: 22955991. DOI: 10.1101/gr.136184.111
• ENCODE uniform pipelines: Hitz et al. "The ENCODE Uniform Analysis Pipelines." Nucleic Acids Res 51, D1014-D1024 (2023). DOI: 10.1093/nar/gkac1067
• ENCODE Blacklist: Amemiya et al. "The ENCODE Blacklist: Identification of Problematic Regions of the Genome." Sci Rep 9, 9354 (2019). DOI: 10.1038/s41598-019-45839-z

Step 2: Export Citations

Use `encode_get_citations` with appropriate format:

• `export_format="bibtex"` -- For LaTeX, Overleaf, BibDesk
• `export_format="ris"` -- For Endnote, Zotero, Mendeley, Papers
• `export_format="json"` -- For programmatic use

For all tracked experiments:

encode_get_citations(export_format="bibtex")

For a specific experiment:

encode_get_citations(accession="ENCSR133RZO", export_format="bibtex")

Step 3: Generate Data Availability Statement

For the Data Availability section of a publication:

Template: > "[Assay type] data for [biosample] were obtained from the ENCODE Project (https://www.encodeproject.org). Experiment accessions: [list ENCSR accessions]. All ENCODE data are freely available under unrestricted use policy."

Use `encode_export_data(format="csv")` to generate a supplementary table listing all experiments used, with columns for accession, assay, biosample, target, lab, and date released.

Step 4: Write Acknowledgments

Template: > "This work used data generated by the ENCODE Consortium (encodeproject.org). The ENCODE Project is funded by the National Human Genome Research Institute (NHGRI)."

If using data from specific labs, consider acknowledging them: > "We thank [Lab Name] for generating the [assay type] data used in this study (ENCODE accession [ENCSR...])."

Step 5: Cross-Reference with Literature

Use `encode_get_references` to find all linked PMIDs and DOIs for tracked experiments. These can be:

• Passed to PubMed tools for full metadata
• Used to find related articles
• Included in the bibliography

Step 6: Supplementary Materials

For reproducibility, include in supplements: 1. Full experiment accession list: `encode_export_data(format="tsv")` 2. File accessions used: list specific ENCFF accessions 3. Pipeline versions and parameters 4. Quality metrics for each experiment used 5. Any derived files with provenance: `encode_get_provenance`

---

Walkthrough: End-to-End From Analysis to Submitted Manuscript

This walkthrough co