Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request #48

Open
jaygray0919 opened this issue Jan 28, 2019 · 3 comments
Open

feature request #48

jaygray0919 opened this issue Jan 28, 2019 · 3 comments

Comments

@jaygray0919
Copy link

The reverse switch (-r) takes the query identifier and creates a reverse tree. In other words, the query is on line 1, the superclass is on line 2, etc.
Would it be possible to provide an extra switch that would change the order of the 'reverse' switch? In other words, line 1 would be the root term (e.g. entity) and the tree would be constructed from the root to the query term.
What is the reasoning for this?
In order to see a large class structure, one might run a children (subclass) query from, for example, level 5 in the class tree. That query produces the target result where the 'top' term is the target and the children are listed below.
Now I would like to integrate the subclass results with the superclasses for the search term. But the superclass query result is not in the same form/shape as the subclass query results.
I have to do significant editing to reorder the superclass query to fit with the subclass query.
A switch -rt (reverse top) would allow the simple combination of a superclass query and a subclass query.

Thanks for creating a really useful tool.

@nichtich
Copy link
Owner

could you add a small example of existing items and expected output?

@jaygray0919
Copy link
Author

will do. be back to you over the weekend with simple and more complex examples

@jaygray0919
Copy link
Author

jaygray0919 commented Feb 7, 2019

here is the use case: build complete taxonomy for bos
but starting from the root [biota (Q2382443)] is indiscriminate, even if SPARQL would process the query, and too large.
so the starting point is bos using this query:
Bos (Q237993); parent taxon (P171); wdtaxonomy Q237993 -P P171
which produces the following (abbreviated)

image

then wdtaxonomy Q237993 -P P171 -r produces (abbreviated)
image

But to 'concatenate' (hook-up) the two structures, I need to manually reverse the parent results as follows:
image

so the feature request is to provide a switch that produces (in the formal wdtaxonomy format) a structure like the last image.
that feature would simplify the combination of results from wdtaxonomy parent and wdtaxonomy children into a single structure - from root to nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants