-
Notifications
You must be signed in to change notification settings - Fork 3
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
Consider re-use of OLS source code #2
Comments
Looking at the software requirements of OLS it seems that it might be unfeasible to integrate. The only use case I would see for it would be maybe if people don't want to use Angular when integrating the annotator, then jQuery is vanilla enough to use, but that would mean a separate annotator written in jQuery only. |
Understood - of course I hope it gets in bio.tools soon. The big benefit though is we'll struggle (never?) get a tree browser that comes close to being as good as OLS ... Jupp spent ages on it - this bit would be good to re-use if poss. Just food for thought ... |
I think for now, what we can do is point each term to OLS, as a separate link in the annotator information panel, where all the term info is displayed. |
OLS have done a great job at browsing EDAM:
https://www.ebi.ac.uk/ols/ontologies/edam
And their source code (for the full-fledged web application) is available under open license:
https://www.ebi.ac.uk/ols/docs/installation-guide
So I think this has to be under consideration for future development of edamToolAnnotator.
We can park the issue for now, but one for the future.
cc @hansioan @hmenager
The text was updated successfully, but these errors were encountered: