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

[WIP] Biotools #1891

Draft
wants to merge 11 commits into
base: dev
Choose a base branch
from
Draft

[WIP] Biotools #1891

wants to merge 11 commits into from

Conversation

mr-c
Copy link
Contributor

@mr-c mr-c commented Mar 8, 2016

No description provided.

@bgruening
Copy link
Member

To add a little bit of information here.
This PR aims at updating and tracking the EDAM annotations that we started at the ELIXIR/de.NBI hackathon in January. Ideally we will have an API endpoint that delivers EDAM consumable tool-descriptions so that the ELIXIR registry can poll Galaxy instances to know which tools are installed.

:rtype: string
"""
try:
return "/".join(tool_id.replace('repos', 'view', 1).split('/')[0:-2])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Galaxy versions > 16.01 return a tool_shed_repository entry for toolshed tools that looks like this:

 "tool_shed_repository": {"owner": "devteam", "changeset_revision": "e359ce20fbd9", "name": "fastq_quality_boxplot", "tool_shed": "toolshed.g2.bx.psu.edu"}

This is probably better suited for constructing a link, given that a toolshed may well be reachable at <http://server_url/abc/toolshed>

@mr-c
Copy link
Contributor Author

mr-c commented Mar 8, 2016

Thanks @mvdbeek ; This is just a standing PR for collaborators of @hmenager & friends to assist with their work.

Lets hold off on a detailed review until they are ready :-)

@mvdbeek
Copy link
Member

mvdbeek commented Mar 8, 2016

Sure, this does look really interesting. One thing that I would discuss is the use of tool_id ... it's a bit unfortunate that the same tool_id may not be sufficient to unambiguously identify the origin of a tool. AFAIK we'd need a combo of toolshed/owner/name/changeset_revision.

@mr-c
Copy link
Contributor Author

mr-c commented Mar 8, 2016

@mvdbeek I appreciate the enthusiasm! @hmenager is at a conference today, but I'm sure he'll get back to you about tool_id

edam_format = "format_1915"
edam_data = "data_0006"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

edam_data is duplicated here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nsoranzo feel free to PR against this branch. I can merge it afaik.

'datatypes',
path_prefix='/api',
collection={ 'sniffers': 'GET', 'mapping': 'GET', 'converters': 'GET', 'edam_data': 'GET' },
parent_resources=dict( member_name='datatype', collection_name='datatypes' ) )
Copy link
Member

@nsoranzo nsoranzo May 19, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that instead of invoking again webapp.mapper.resource() here, you should just add 'edam_data': 'GET' at line 303.

else:
return description[0].upper() + description[1:size] + '.'
except IndexError:
raise description
Copy link
Member

@mvdbeek mvdbeek May 19, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will cause a TypeError if description is "".

'dataDescription': data_json['name']
})

def inputs_extract_repeat(repeat_json):
Copy link
Member

@bgruening bgruening May 19, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there not already a function in Galaxy that traverses all params and extracting data-params.
If not this should probably end up in some utils file to be reused by other modules.

@nsoranzo
Copy link
Member

This has been rebased now that #2387 is merged.

@mvdbeek
Copy link
Member

mvdbeek commented May 20, 2016

@galaxybot test this

@mr-c
Copy link
Contributor Author

mr-c commented Jun 23, 2017

@hmenager What's the status of this? Shall we hack on it next week?

@nsoranzo nsoranzo marked this pull request as draft September 17, 2022 07:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants