This seems like a nice application of the API:
(1) use a daemon to periodically query Galaxy for user histories and/or
datasets (I think this is possible with the API right now);
(2) create symbolic links to user's datasets, perhaps ordered in subdirectories
based on history.
Best,
J.
On May 1
Thanks for breaking that down for me. We are trying to set up some dev
machines in our environment in a few weeks and I may create a clone of our
production Galaxy mirror and play around with that version to see if I can
get the functionality that I'm looking for. I'll take that idea about
having a
No, this was all an idea I've had for a while, but never did anything about it.
I'm pretty sure the Galaxy developers are not interested in anything this
locally-centric, and I don't blame them. It ought to be something outside the
Galaxy build completely, because Galaxy is meant to be system-
Hi David,
Actually that is an interesting idea to use a daemon to move the files into
associated user directories. Is that something that Galaxy Dev is
working/can work on, or was that just a suggestion? I'm not opposed to
doing any dev work of my own, but I don't really know Python that well and
How about if there were a completely separate daemon that monitored the galaxy
database periodically to determine what datasets belong to which user(s). Then
it would move the actual dataset to an area owned by the user and group
accessible to galaxy, replacing the dataset with a symlink. This
Hello,
Please forgive the length of this proposition as I try to explain my
reasoning behind this. Let me say first of all that I understand that
Galaxy is not meant to be everything to everyone and that requests for
features may not suit everyone who uses Galaxy. That being said I have an
idea or
