> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/correlation-engine/managing-my-data-in-correlation-engine/libraries.md). # Public and Domain Libraries Correlation Engine organises all available studies into two main libraries: the **Public Library** and the **Domain Library**. Understanding the distinction between these is important for knowing which data you can query and how your own imported data is shared. *** ## Public Library The **Public Library** (also called the Public Domain Library) contains all studies that have been curated by Illumina and made available to every Correlation Engine user, regardless of subscription level. ### What Is in the Public Library? | Content | Source | | -------------------------- | -------------------------------------------------------------------------- | | Gene expression studies | Gene Expression Omnibus (GEO), Array Express, Stanford Microarray Database | | Cancer genomics | The Cancer Genome Atlas (TCGA), COSMIC | | Chemical perturbation data | L1000 Connectivity Map (LINCS) | | Single-cell studies | CZI CELLxGENE, GEO | | Body Atlas reference sets | GTEx RNA-Seq, Affymetrix normalised arrays, Single Cell RNA-Seq | | GWAS / SNP data | OMIM, Jackson Labs, DrugBank | | Manually curated studies | Illumina curation team from published literature | As of Correlation Engine v2.9.0, the public library contains: | Metric | Count | | -------------------------------- | ------- | | Public studies | 27,566 | | Public biosets | 202,676 | | Single-cell biosets (Body Atlas) | 3,287 | ### Key Properties of Public Studies * **Read-only** — Public studies and their biosets cannot be edited by users. * **Semantic tagging** — All public studies are tagged with disease, tissue, compound, and gene ontology terms, enabling them to appear in categorized atlas results. * **Continuously updated** — New public data is added with each CE release, primarily sourced from newly published GEO series. ### Requesting a Public Study If there is a specific GEO Series (GSE) or published study you would like added to the public library, you can submit a request through **Curated Studies → All Studies → Request a Study** within the CE interface. Provide the GEO Series ID (GSE number) or PubMed ID (PMID) with a link to the publicly available data. *** ## Domain Library The **Domain Library** (also referred to as the "Company Library" or "Enterprise Library" in some contexts) contains studies imported by users within your organisation's Correlation Engine domain. It is the private, organisation-scoped counterpart to the Public Library. ### Who Can See Domain Library Studies? | Scope | Visibility | | -------------------------------------- | --------------------------------------------- | | Studies you imported (personal) | Visible only to you by default | | Studies in a shared group | Visible to group members | | Studies promoted to the Domain Library | Visible to all users in your domain/workgroup | Domain library studies are included in categorized atlas results (Disease Atlas, Body Atlas, etc.) for all users in the domain, giving your organisation's data the same integration as public data. {% hint style="info" %} Promoting a study to the domain-wide library requires special administrator permission. Contact your Correlation Engine administrator or reach out to if you need organisation-wide library access. {% endhint %} ### Domain Library vs. Personal Studies | Feature | Personal Studies | Domain Library | | --------------------------------- | --------------------------------------- | --------------------- | | Visible to | Only you (and shared groups) | All domain users | | Included in atlas categorizations | No (appears in Correlated Studies only) | Yes | | Editable | Yes | No (after promotion) | | API bulk import | No | Yes (Enterprise only) | ### Privacy and Security Correlation Engine provides complete privacy control over your imported data. You can share data selectively by: 1. **Groups** — sharing a study with a specific user-created group. 2. **Domain promotion** — elevating a study to domain-wide visibility (requires admin permission). All data — in transit and at rest — is encrypted. See [About Correlation Engine](/correlation-engine/about/about.md#security) for full security details. *** ## Navigating Between Libraries From the **Studies & Projects** page, use the tab controls to switch between: * **My Studies** — your personal imports. * **Public Domain Library** — all CE public content, browseable by project category (e.g., "TCGA", "GEO by year", "L1000"). * **\[Your Organisation] Library** — domain library studies (visible if your domain has promoted studies). Within the public library projects, studies are organised into named folders corresponding to their data source. None of these can be edited. Use the **All Curated Studies** view in the Curated Studies app to search and filter across all library content. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.bioinsight.illumina.com/correlation-engine/managing-my-data-in-correlation-engine/libraries.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.