-
Notifications
You must be signed in to change notification settings - Fork 20
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
Clarification about commercial licenses #87
Comments
Hi, This is a good point, I'll try to implement it. The license parameter currently only makes sure that each record is supported by at least one evidence that fits the chosen licensing requirements. All other columns ( |
Thank you! |
Hello @deeenes and @InesdeSantiago do you have any update related to this ticket?
but the result is the same as if I run this:
Ideally what I would expect is that the sources that cannot be used, wont appear right? Later looking in your nicely and very well commented code I found this function
My suggestions:
(I mean a resource associated with another resource with underscore) this means that the first_resource_name is used by the second_resource_name, and that's the only one to be used for the "Queries" described by the resource_info() object? I understand it is a huge project and not sure if I am big enough to push some changes into it. But I could try, at least with the documentation atm if that helps. |
…rmation to input definitions from controller - saezlab/OmnipathR#87
Hi,
There are a few data sources that seem to have a non-commercial license:
I noticed that these data sources appear in the output table , even when seleting the "commercial" option
I am not sure if Omnipath uses a version of such databases that could be "public", for instance SIGNOR ? but I believe that the resources such as LRdb, PhosphoPoint and others should be considered "commercial".
If this is correct, it possible to update the package to remove them if they are indeed not commercial?
Thank you.
The text was updated successfully, but these errors were encountered: