History accessible by many users

Question: History accessible by many users

4.2 years ago by

dgygax • 50

United States

dgygax • 50 wrote:

Hi,

I am an admin for a local instance of galaxy. The local instance of galaxy is on a server that many different lab members all have access to. Is it possible to make a group for the lab members/users so that they will all have access to the same group of histories.

Here is an example:

There are two users, A and B. User A logs on to their own account and creates a history entitle 'Set84', works on the history and then logs out at the end of the day. User A does not click on the gear icon on the top right of galaxy and share the 'Set84' history with any other users. The next morning user B log on to their own account. I want user B to be able to click on the gear icon on the top right of galaxy and then go to saved histories and see the 'Set84' history that user A was working on.

Basically I want all the users to be working together on the same group of histories.

Is there any way to make this possible with the current installation of galaxy?

histories history sharing publishing permissions • 971 views

ADD COMMENT • link •

modified 4.2 years ago by Jennifer Hillman Jackson ♦ 25k • written 4.2 years ago by dgygax • 50

4.2 years ago by

Martin Čech ♦♦ 4.9k

United States

Martin Čech ♦♦ 4.9k wrote:

I believe that currently this is not possible, unless they share the same account. To make it work would require nontrivial implementation effort (locking histories/concurrent access). However there might be other ways to achieve same behavior, maybe somone else will help you.

ADD COMMENT • link written 4.2 years ago by Martin Čech ♦♦ 4.9k

4.2 years ago by

Jennifer Hillman Jackson ♦ 25k

United States

Jennifer Hillman Jackson ♦ 25k wrote:

Hello,

As far as I know, individual histories must be specifically shared or published to grant other users access. And histories cannot be modified or included in the same version between accounts - these must be imported to begin work. There are global permissions and group that can be set up and used by the administrator of the instance, and the impersonate function would permit a user with an admin-level account to access any users account (directly, as that user), but these are not really the same thing.

Depending on who is on your server (just your group?) - asking all users to publish by default would permit all others to access histories. Data will need to be managed carefully (unsharing and permenently deleting histories that no longer represent the most current results).

You could have users all or in part share a single account, on your own server. The most important factor with this type of usage is to ensure that only one person is actively logged in and using the account at a time. We do this here within our own team on various shared instances for training and other administration accounts as needed. Careful coordination is required for successful usage this way.

Sharing accounts is not recommended for public users of the Main Galaxy Instance, especially if users also maintain their own separate account, as this will quickly be picked up by the account duplication tracking processes and all associated accounts deleted without prior notice (resulting in data loss). Following the terms for "one account per user" is very important. But on your own server, you can set your own administrative policies.

Hopefully one of these options will work out for you, Jen, Galaxy team

ADD COMMENT • link written 4.2 years ago by Jennifer Hillman Jackson ♦ 25k

4.2 years ago by

dgygax • 50

United States

dgygax • 50 wrote:

Thank you, all the information has been very helpful. For now we will have all the lab members share a single account, and as you advise we will be careful monitoring the data and ensuring that only one user is logged on at a time. Thanks again for all the help.

ADD COMMENT • link written 4.2 years ago by dgygax • 50

Please log in to add an answer.

Similar posts • Search »