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

Please add Galaxy annotations to the "Community usage" #31

Open
2 tasks
matuskalas opened this issue Jul 1, 2018 · 3 comments
Open
2 tasks

Please add Galaxy annotations to the "Community usage" #31

matuskalas opened this issue Jul 1, 2018 · 3 comments

Comments

@matuskalas
Copy link
Member

matuskalas commented Jul 1, 2018

  • Data & format annotations:
    Either from https://test.galaxyproject.org or https://usegalaxy.eu (..org released with datatypes update every 4 months; ..eu has a few more tools than ..org).
    Higher priority (cool to do after I get all these updated in the Galaxy code, and adequate updates are released in EDAM)

  • Operation & topic annotations:
    Would be the best to pull from the main ToolShed. A minimalistic API implemented to do this would probably suffice for this functionality; otherwise would need to pull info from Schema.org|BioSchemas annotation of the generated HTMLs (which is going to be implemented).

@bryan-brancotte
Copy link
Member

Hi @matuskalas
Links to galaxy instanceS is in scope. Do you a a link where I can see data annotated with edam ? I did not found that yet.
Best

@bryan-brancotte
Copy link
Member

We have to decide if there is a source for such information, or close the issue

@bryan-brancotte bryan-brancotte removed this from the outreachy202105-1 milestone Jun 22, 2021
@bryan-brancotte
Copy link
Member

Hi @matuskalas

@HagerDakroury internship is the good occasion to work on this issue, but I (we?) are still blocked with not knowing where to find the galaxy api to get which tool are annotated with edam. Could you provide some pointers to start working on this issue (maybe @hmenager you also have some) ? Or should we simply close this issue ?

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

No branches or pull requests

3 participants