Are there any docs or examples about how to add/remove tags from items via the galaxy web-api? Thanks, Kyle Ellrott
Kyle, Tags haven't been implemented in the API yet. This is, of course, planned development for the future. J. On Nov 9, 2012, at 7:56 PM, Kyle Ellrott wrote:
Are there any docs or examples about how to add/remove tags from items via the galaxy web-api?
Thanks, Kyle Ellrott ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
From IRC (weeks ago): (03:15:01 PM) jmchilton: Ideally, what would the API uri for assigning a tag to a histories dataset be? POST to api/tags/<tag_name>/<item_class(e.g. HistoryDatasetAssociation)>/<encoded_id> or POST to api/histories/<history_id>/contents/<dataset_id>/tags/<tag_name> or POST to api/tags/<tag_name>?item_class=HistoryDatasetAssociation&encoded_id=<encoded_id> (03:16:19 PM) jmchilton: And filtering a histories contents by tag, would pull request that implemented api/histories/<history_id>/contents/<dataset_id>?filter_by_tag=<tag_name> be accepted? (03:16:56 PM) jmchilton: How about grabbing the unique tags in a history, what should that API call look like?
I would just like to reiterate my standing offer to implement this if someone from the Galaxy team tells me what they would look like at a high level. -John On Sat, Nov 10, 2012 at 11:50 AM, Jeremy Goecks <jeremy.goecks@emory.edu> wrote:
Kyle,
Tags haven't been implemented in the API yet. This is, of course, planned development for the future.
J.
On Nov 9, 2012, at 7:56 PM, Kyle Ellrott wrote:
Are there any docs or examples about how to add/remove tags from items via the galaxy web-api?
Thanks, Kyle Ellrott ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
Ah, sorry I missed this.
From IRC (weeks ago): (03:15:01 PM) jmchilton: Ideally, what would the API uri for assigning a tag to a histories dataset be? POST to api/tags/<tag_name>/<item_class(e.g. HistoryDatasetAssociation)>/<encoded_id> or POST to api/histories/<history_id>/contents/<dataset_id>/tags/<tag_name> or POST to api/tags/<tag_name>?item_class=HistoryDatasetAssociation&encoded_id=<encoded_id>
Both :) An independent /api/tags controller is desirable so that all items with a particular tag can be found, but adding tag functionality to object-specific controllers would be nice as well. For ease of use, I envision item_class supporting both formal and informal notation (e.g. hda, ldda) and being case insensitive.
(03:16:19 PM) jmchilton: And filtering a histories contents by tag, would pull request that implemented api/histories/<history_id>/contents/<dataset_id>?filter_by_tag=<tag_name> be accepted?
Sure, but why would a dataset ID be needed if filtering a history by tag(s)?
(03:16:56 PM) jmchilton: How about grabbing the unique tags in a history, what should that API call look like?
Maybe this: /api/histories/<history_id>/contents/tags?unique=True (where unique=False returns a list of tags for each HDA, potentially producing duplicate tags)
I would just like to reiterate my standing offer to implement this if someone from the Galaxy team tells me what they would look like at a high level.
Great, looking forward to it. J.
On Mon, Nov 12, 2012 at 9:43 AM, John Chilton <chilton@msi.umn.edu> wrote:
From IRC (weeks ago): (03:15:01 PM) jmchilton: Ideally, what would the API uri for assigning a tag to a histories dataset be? POST to api/tags/<tag_name>/<item_class(e.g. HistoryDatasetAssociation)>/<encoded_id> or POST to api/histories/<history_id>/contents/<dataset_id>/tags/<tag_name> or
I personally prefer this one. Any object that supports tags gets a /tags/...
(03:16:56 PM) jmchilton: How about grabbing the unique tags in a history, what should that API call look like?
Just a GET to .../<entity_id>/tags ?
While we're talking about the tags API, I'd also like to see if we can think about the annotations API. Can it be formulated in the same manner as the proposal for the tags api? Kyle On Mon, Nov 12, 2012 at 7:49 AM, James Taylor <james@jamestaylor.org> wrote:
On Mon, Nov 12, 2012 at 9:43 AM, John Chilton <chilton@msi.umn.edu> wrote:
From IRC (weeks ago): (03:15:01 PM) jmchilton: Ideally, what would the API uri for assigning a tag to a histories dataset be? POST to api/tags/<tag_name>/<item_class(e.g. HistoryDatasetAssociation)>/<encoded_id> or POST to api/histories/<history_id>/contents/<dataset_id>/tags/<tag_name> or
I personally prefer this one. Any object that supports tags gets a /tags/...
(03:16:56 PM) jmchilton: How about grabbing the unique tags in a history, what should that API call look like?
Just a GET to .../<entity_id>/tags ? ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
While we're talking about the tags API, I'd also like to see if we can think about the annotations API. Can it be formulated in the same manner as the proposal for the tags api?
Yes, annotations and tags share the same structure, so it makes sense that the tag API structure can be used for annotations as well. J.
participants (4)
-
James Taylor -
Jeremy Goecks -
John Chilton -
Kyle Ellrott