Hi Niel, Galaxy does not expose filepaths to non-admin users intentionally. For executing a workflow with that particular script, the 'file_id' in question in that example should be an hda, which is what api/history/contents will display for your users as the 'id' for each history item.
-Dannon On Fri, Jan 17, 2014 at 6:12 AM, <neil.burd...@csiro.au> wrote: > Hi Charles, > not a problem. In my previous post I specified the command > line: > > /home/galaxy/milxcloud/scripts/api/display.py <api_key> > http://barium-rbh:9100/extras/api/histories/ebfb8f50c6abde6d/contents/4a56addbcc836c23 > > The <api_key> in your question refers to the api_key of an "admin" user, > however, the history_id (ebfb8f50c6abde6d) refers to a history not "owned" > by the admin user using the unique api_key i.e. another user, hence the > error message > > I hope that answers your question? > > Neil > > ________________________________________ > From: Charles Girardot [charles.girar...@embl.de] > Sent: Friday, January 17, 2014 6:31 PM > To: Burdett, Neil (CCI, Herston - RBWH) > Cc: galaxy-dev@lists.bx.psu.edu > Subject: Re: [galaxy-dev] Can't view file_name in histories via API unless > admin? > > Hi Neil, > > sorry, this is not an answer to your post, I hope you won t mind me > stepping in your thread this way. > Your message kept my attention because of your note: I am surprised by the > error message you report when trying to use an admin API key. > > How does galaxy know the user who is making the call? > > Sorry if I am missing the obvious > > bw > > Charles > > On 17 Jan 2014, at 07:35, <neil.burd...@csiro.au> wrote: > > > Hi, > > it seems that the entry "file_name:" does not appear when running > the command > > > > /home/galaxy/milxcloud/scripts/api/display.py <api_key> > http://barium-rbh:9100/extras/api/histories/ebfb8f50c6abde6d/contents/4a56addbcc836c23 > > > > unless you are stated as as admin user in the "universe_wsgi.ini" > > i.e. > > admin_users = t...@test.com,te...@test.com > > > > is this known? > > > > Is there anyway to get around this as we don't want all users to be > admin, however, they need access to this field. > > > > Note that you can't use an admin's <api_key> as you'll get the error > > "Error in history API at listing dataset: History is not owned by the > current user" > > > > Thanks > > Neil > > ___________________________________________________________ > > 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/ > > > > To search Galaxy mailing lists use the unified search at: > > http://galaxyproject.org/search/mailinglists/ > > > ___________________________________________________________ > 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/ > > To search Galaxy mailing lists use the unified search at: > http://galaxyproject.org/search/mailinglists/ >
___________________________________________________________ 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/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
