# Understanding genetic\_association datasourceId in 25.06.0

**URL:** <https://community.opentargets.org/t/understanding-genetic-association-datasourceid-in-25-06-0/1851>\
**Category:** General\
**Tags:** datadownloads, genetics-portal\
**Created:** [10 July 2025 14:03 UTC](https://community.opentargets.org/t/understanding-genetic-association-datasourceid-in-25-06-0/1851 "2025-07-10T14:03:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![gatla](https://dub1.discourse-cdn.com/flex017/user_avatar/community.opentargets.org/gatla/32/812_2.png) [@gatla](https://community.opentargets.org/u/gatla)\
**Post date:** [10 July 2025 14:03 UTC](https://community.opentargets.org/t/understanding-genetic-association-datasourceid-in-25-06-0/1851/1 "2025-07-10T14:03:56Z")

</div>

Hi All, I am just wondering what does it meant by _‘gwas\_credible\_sets’_ under _datasourceId_ ? Is it the L2G ML model score or specifically coloc evidence ?

`gene2phenotype, gene_burden, genomics_england, gwas_credible_sets, eva, clingen, orphanet, uniprot_literature, uniprot_variants`

---

<div class="post-metadata">

**Author:** ![ochoa](https://dub1.discourse-cdn.com/flex017/user_avatar/community.opentargets.org/ochoa/32/189_2.png) [@ochoa](https://community.opentargets.org/u/ochoa)\
**Post date:** [10 July 2025 14:49 UTC](https://community.opentargets.org/t/understanding-genetic-association-datasourceid-in-25-06-0/1851/2 "2025-07-10T14:49:01Z")

</div>

I suspect you refer to the value in `associationsByDatasourceDirect` or `associationsByDatasourceIndirect` datasets. In both cases, this value is the association score resulting from aggregating all evidence for the same Target-Disease pair. In the platform website, it corresponds to the blue cells in the associations page. More details [here](https://platform-docs.opentargets.org/associations)

If you are looking after L2G evidence score, you will need to look at the [evidence dataset](https://platform.opentargets.org/downloads/evidence/schema), which will have one single row per credible set-gene pair. You will want to restrict to `gwas_credible_sets` as `sourceId` and use the `score` column to find any L2G prediction above 0.05.

---

<div class="post-metadata">

**Author:** ![gatla](https://dub1.discourse-cdn.com/flex017/user_avatar/community.opentargets.org/gatla/32/812_2.png) [@gatla](https://community.opentargets.org/u/gatla)\
**Post date:** [10 July 2025 14:59 UTC](https://community.opentargets.org/t/understanding-genetic-association-datasourceid-in-25-06-0/1851/3 "2025-07-10T14:59:31Z")

</div>

Thanks for the swift reply David @ochoa. I am looking at _association\_by\_datasource\_direct_ and I am particularly interested in `datatypeID==genetic_asscoation` . I am just wondering if it is a aggregated score of all evidences, why does it still lists `gene2phenotype, gene_burden, genomics_england, eva, clingen, orphanet, uniprot_literature, uniprot_variants` in addition to **gwas\_credible\_sets**? Did _gwas\_credible\_sets_ replaced _ot\_genetics\_portal_ score from previous versions ?

---

<div class="post-metadata">

**Author:** ![ochoa](https://dub1.discourse-cdn.com/flex017/user_avatar/community.opentargets.org/ochoa/32/189_2.png) [@ochoa](https://community.opentargets.org/u/ochoa)\
**Post date:** [11 July 2025 09:28 UTC](https://community.opentargets.org/t/understanding-genetic-association-datasourceid-in-25-06-0/1851/4 "2025-07-11T09:28:52Z")

</div>

The `association_by_datasource_direct` would contain:

- `association` - refers to target-disease aggregated scores derived from evidence
- `by_datasource` - specifies the evidence is aggregated at the datasource-level (e.g. `gene_burden`, `gene2phenotype`, etc.)
- `direct` - implies there is no aggregation of evidence using the ontology structure. Every evidence needs to be for the exact same target and disease and not descendants in the ontology.

You can find 6 different association datasets with different combinations of the above in the `Downloads` page. If instead you are looking for the aggregation of evidence in all genetic data sources you are probably more interested in the `association_by_datatype_direct` which would aggregate all genetic evidence from all sources (e.g. gene2phenotype, genomics\_england, etc.) into a single score by target-disease pair. As a result, the schema of this dataset will not have `datasourceId` on it:

 ![Screenshot 2025-07-11 at 10.28.22](https://europe1.discourse-cdn.com/flex017/uploads/opentargets/original/1X/669f9216d0b8b931c583ad46628d145d5aeabad0.png)

---

<div class="post-metadata">

**Author:** ![gatla](https://dub1.discourse-cdn.com/flex017/user_avatar/community.opentargets.org/gatla/32/812_2.png) [@gatla](https://community.opentargets.org/u/gatla)\
**Post date:** [11 July 2025 13:09 UTC](https://community.opentargets.org/t/understanding-genetic-association-datasourceid-in-25-06-0/1851/5 "2025-07-11T13:09:01Z")

</div>

Thansk David. Super useful. What does **gwas\_credible\_sets** refer to in association\_by\_datasource\_direct ? Is it coloc evidence or L2G model score ? Attaching an example

 ![Screenshot 2025-07-11 at 14.04.12](https://europe1.discourse-cdn.com/flex017/uploads/opentargets/original/1X/6f3647bdf2d09c24d5b5ecaf8db522799bc78815.png)

---

<div class="post-metadata">

**Author:** ![ochoa](https://dub1.discourse-cdn.com/flex017/user_avatar/community.opentargets.org/ochoa/32/189_2.png) [@ochoa](https://community.opentargets.org/u/ochoa)\
**Post date:** [11 July 2025 13:48 UTC](https://community.opentargets.org/t/understanding-genetic-association-datasourceid-in-25-06-0/1851/6 "2025-07-11T13:48:41Z")

</div>

The highlighted value corresponds to the heatmap cell for GWAS associations:

 ![Screenshot 2025-07-11 at 14.45.20](https://europe1.discourse-cdn.com/flex017/uploads/opentargets/original/1X/bdec5ee7ba790a911ccbc47c571c8a40ba9b6260.png)

This is the result of aggregating all the L2Gs for all gwas credible sets pointing to that gene (content of the table when clicking on the blue dot). That data is available is the evidence dataset as described in my first comment
