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 <ja...@jamestaylor.org> wrote: > On Mon, Nov 12, 2012 at 9:43 AM, John Chilton <chil...@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: > > http://lists.bx.psu.edu/ ___________________________________________________________ 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: http://lists.bx.psu.edu/
