2.0.8 - Fix in the EPMC evidence

Fixed typo where the diseaseFromSourceMappedId field in the EPMC evidence was duplicated.

Small updates in EPMC evidence

Changes in the EPMC disease/target evidence:

• targetFromSource and diseaseFromSource are no longer allowed (only the grounded identifiers are stored).
• pmcIds added to store PubmedCentral identifiers when pmids are not available.

2.0.6 - Updating patterns for fields

To accommodate evidence data better, required string patterns got updated.

• variantId: now the pattern allows mitochondrial chromosomes, and IUPAC ambiguity codes to handle multiallelic variants.
• studyStartDate: now the YYYY-MM-DD format better handled.
• studyStopReason: the field no longer allows having leading and trailing white spaces and new-line, CR characters in the text.

2.0.5 - Providing additional links are now available for COSMIC.

Adding urls to COSMIC, it will allow having links to analysis pages o…

2.0.4 - Beta coefficients for Genetics Portal and other updates

Updates:

• beta is added to Genetics Portal.
• The upper and lower boundaries of the confidence interval are also added.
• The same definitions are applied for the confidence intervals of beta and odds ratio.
• alleleOrigins is no longer an enum to better accommodate EVA evidence.
• diseaseFromSource field is added to Sysbio.
• In reactome and uniprot_variants, functionalConsequenceId has been changed to variantFunctionalConsequenceId

2.0.3 - Updating accepted fields for ChEMBL and IntOGen

No major update in this release. Fixes to accommodate ChEMBL evidence:

• diseaseFromSourceId has been deleted, as the presence of a MeSH ID is always a intermediary mapping step coming from ChEMBL; it is not present in the actual resource.
• targetFromSource has been added to store those cases where the target is a protein complex. If the subunit interacting with the molecule is unknown, all subunits should be listed. If known, the particular subunit will be included.

Minor changes to intOGen after rewriting the parser:

• diseaseFromSourceId has been deleted
• studyId has been deleted

2.0.2 - Supporting multiple pathways

Support for storing multiple pathways is added.

Example:

"pathways": [
    {
        "id": "R-HSA-2894862",
        "name": "Constitutive Signaling by NOTCH1 HD+PEST Domain Mutants"
    },
    {
        "id": "R-HSA-2644606",
        "name": "Constitutive Signaling by NOTCH1 PEST Domain Mutants"
    }
]

2.0.1 - First release of the slimmed-down schema

• From the 2.0.0 pre-release, the opentargets.json has been finalised for all data sources.
• The OT_network_schema.json is added to the master branch

New, streamlined json schema for the Platform rewrite

There are numerous changes in the schema from the previous version.

Changes:

• The schema is structured by data sources instead of data types.
• targetId is removed: targets are mapped by OT pipelines. Instead, providers use targetFromSourceId
• uniqueAssociationFields is removed: evidence uniqueness is defined by OT pipelines.
• diseaseId is removed: diseaseId is now assigned by OT pipelines. Instead providers can use diseaseFromSourceId, diseaseFromSource or diseaseMappedFromSourceId for diseases where the EFO identifier is available.

Please contact us for further information.

1.7.5

Variant schema does not require id or rs_id.

Note that the data pipeline may still need the ids for some data sources. This change does not mean that they can be omitted, only that they are not compulsory.