Hello! I am trying to connect my Galaxy account directly to Google Drive as a repository in the hopes that it will make uploading multi-GB files faster… I am repeatedly running into the error message attached. Would appreciate any help, as I think this is an issue on the Galaxy side rather than the Google side. Thanks!
Are you still having this problem? If so, let’s try to troubleshoot!
Creating your account through the Google Auth process for account registration is a distinct process from configuring Goggle Drive as a storage location. I mentioning this first since it can be mixed up, but these are unrelated processes. You could even using one Gmail account for registration, and another for Google Drive!
Some more tips about how this works:
- Configure your space following this guide.
-
Set the storage space for your account (or a specific history) to use the new space.
-
The first time a dataset is loaded into a history using the space, it will be written to your new storage location for the first time.
- From here, you will be able to read/write that dataset.
- A copy of a dataset from another history is not enough, since the underlying file still is written to the original storage location. The reference to the file was only copied over, not the file itself.
- This usually means the first step is using the Upload tool to add new data to Galaxy. After, you’ll be able to work with that data in place, even if it is on your Google Drive storage.
-
You can also choose to do things like load the starting data into a history that uses the local storage on the server, then execute a workflow, and set the workflow to write to your Google Drive location.
- Sending the results to a new history will create a new history, where the inputs will be cloned over (still assigned to the original storage) but all new data created by the workflow will be written to the Google Drive storage.
-
For data that is shared between Galaxy and Google Drive, consider not modifying it!
- Let the Galaxy history areas be managed by Galaxy.
- If you want to work with one of those files, create a copy of that data into another location in your Google Drive and work with it there. If you want that updated file to be used in Galaxy, load it again through the Upload tool into a history with the Google Drive storage set (this can be an existing history, including the history where the original version of the file was!).
With this context, problems like your usually mean that the request for an action didn’t have the correct file permissions set. This is usually because the data was modified outside of the Galaxy managed actions (in Google Drive directly) or that Galaxy is being asked to change a file that it was never granted permissions to manage (was not created in Google Drive through Upload/tools).
Questions
- Which public Galaxy server are you working at? URL from the top of the browser window please.
- Did you set up your storage area to use Google Drive? Did you load data into that location? Did you have tools or a workflow write to that location?
- Then explain a bit more about what you were doing. Screenshots can help!
Let’s start there, thanks! 