ComPath Resources 
This repository contains the different resources derived or generated using ComPath. Among these resources, there are Jupyter notebooks outlining possible analyses that can be made using ComPath plugins as well as the results of the curation effort (‘mappings’ folder) where we generated pathway mappings between three of the major pathway databases (see below).
Citation
If you use ComPath in your work, please cite:
Domingo-Fernández, D., et al. (2018). ComPath: An ecosystem for exploring, analyzing, and curating mappings across pathway databases. bioRxiv 353235.
Installation

Easiest
Download the latest stable code from PyPI with:
python3 -m pip install compath_resources
Get the Latest
Download the most recent code from GitHub with:
python3 -m pip install git+https://github.com/ComPath/resources.git@master
Curation (Pathway Mappings)
The aim of this exercise was to generate mapping files across pathway databases in order to establish relationships between similar pathways in three of the major pathway databases:
We recommend to download the mappings directly from the ComPath website since the pathways in WikiPathways are not stable and might have been changed. However, the mapping file distributed by the website contains stable identifiers from all resources.
Mapping Between Pathway Databases
A total of 3 mapping files are stored in this package, one for each pairwise comparison:
It is important to mention that even more mappings are stored in the database thanks to the ComPath inference system. For example, when a KEGG to WikiPathways pathway is assigned as equivalent to a Reactome pathway, ComPath uses the Reactome hierarchy to infer new hierarchical mappings and map the super/sub pathways of the Reactome pathway to this corresponding equivalent pathway.
Curation Team
The curation exercise was conducted under inter-curator agreement in a team formed by:
Carlos Bobis-Álvarez
Josep Marín-Llaó
Mapping Types
We have distinguished between two types of relationships between pathways (mappings): “equivalentTo” and “isPartOf”.
equivalentTo. An undirected relationship denoting both pathways refer to the same biological process. The requirements for this relationship are:
Scope: both pathways represent the same biological pathway information.
Similarity: both pathways must share at minimum of one overlapping gene.
Context: both pathways should take place in the same context (e.g., cell line, physiology)
isPartOf. A directed relationship denoting the hierarchical relationship between the pathway 1 (child) and 2 (parent). The requirements are:
Subset: The subject (pathway 1) is a subset of pathway 2 (e.g., Reactome pathway hierarchy).
Similarity: same as above
Context: same as above
Metadata
Release files for compath-resources 0.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| compath_resources-0.0.7.tar.gz | 85.9 kB | Without provenance | Details |
Release files / compath_resources-0.0.7.tar.gz
| Download URL | compath_resources-0.0.7.tar.gz |
|---|---|
| Size | 85.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0fd067bc3e082aa0dd8f6fb95e1bafd8e784665360de0ae6dc68982b55a8c514
|
|
BLAKE2b-256 checksum How to use checksums |
6b1c85c75e7c02c0769fcc2d3d2b479452c96c7ad598c0ac7a24ecd87676a677
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.23.0 CPython/3.6.5
|
Security for compath-resources 0.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.