Users want an easy way to know child/parent pathways

[IgorRodchenkov]

Although it's possible to get such information using current PC2 web services (by chaining /search and /traverse queries) programmatically*(), we could also generate in the downloads a simple pathway-parents.txt** file:

pathway   direct_parent_pathways    parent_pathways

and a pathway-children.txt file

pathway   direct_child_pathways    child_pathways

where the first column would have "displayName"(URI), and the second and third ones - lists of "displayName1"(URI1);"displayName2"(URI2);...

The name (displayName) should be the same one which is also used in our extended SIF and GSEA .gmt files.

I would only use BioPAX Pathway.pathwayComponent property and the corresponding inverse "property" for this (i.e., would not infer child/parent pathway relationships from pathwayOrder and controller/controlled BioPAX properties).

*()** PS: To get parent pathway of a pathway / all pathway by name or URI one could try (better with our cpath-client, or any other way, programmatically, i.e., not via a browser):

1. search for all Pathways, or, e.g., - by (exact) name (collect all the hits, not just the first results page; you can see the URIs of all parent pathways per hit right there; you can request JSON format by using /search.json?... in the query);
2. get displayName(s) of direct parent pathways;
3. get displayName(s) of all parent pathways;

(Can also use "name" if you want instead of displayName - some pathways have several names)

[IgorRodchenkov]

Seems, generating only a pathway-children.txt file (pathway, direct_child_pathways, all_child_pathways) file is enough.