Add statement regarding Google Drive #49
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
clarify unreliable storage location for research products
Member
|
@egrace479 did you leave the PR in draft status because you were still going to add, change, or review something, or is this by accident, and it is actually ready for review? |
Member
Author
It was more that I thought you may have more suggestions/notes about things to change, as in a discussion. I set it as ready for review, as that really isn't so different. |
hlapp
approved these changes
Jan 26, 2026
Member
hlapp
left a comment
hlapp
left a comment
There was a problem hiding this comment.
See minor suggested change inline. Otherwise LGTM!
Co-authored-by: Hilmar Lapp <hlapp@drycafe.net>
egrace479
added a commit
to Imageomics/Imageomics-guide
that referenced
this pull request
Jan 27, 2026
Pull from Collab Guide [PR 49](Imageomics/Collaborative-distributed-science-guide#49) * Add statement regarding Google Drive clarify unreliable storage location for research products * Include provenance tracking considerations Co-authored-by: Hilmar Lapp <hlapp@drycafe.net> --------- Co-authored-by: Hilmar Lapp <hlapp@drycafe.net>
egrace479
added a commit
to ABC-Center/ABC-guide
that referenced
this pull request
Jan 27, 2026
Pull from Collab Guide [PR 49](Imageomics/Collaborative-distributed-science-guide#49) * Add statement regarding Google Drive clarify unreliable storage location for research products * Include provenance tracking considerations Co-authored-by: Hilmar Lapp <hlapp@drycafe.net> --------- Co-authored-by: Hilmar Lapp <hlapp@drycafe.net>
egrace479
added a commit
to Imageomics/Imageomics-guide
that referenced
this pull request
Jan 28, 2026
Pull from Collab Guide [PR 49](Imageomics/Collaborative-distributed-science-guide#49) * Add statement regarding Google Drive clarify unreliable storage location for research products * Include provenance tracking considerations Co-authored-by: Hilmar Lapp <hlapp@drycafe.net> --------- Co-authored-by: Hilmar Lapp <hlapp@drycafe.net>
egrace479
added a commit
to ABC-Center/ABC-guide
that referenced
this pull request
Jan 28, 2026
Pull from Collab Guide [PR 49](Imageomics/Collaborative-distributed-science-guide#49) * Add statement regarding Google Drive clarify unreliable storage location for research products * Include provenance tracking considerations Co-authored-by: Hilmar Lapp <hlapp@drycafe.net> --------- Co-authored-by: Hilmar Lapp <hlapp@drycafe.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Specifically, we want to clarify that Google Drive is an unreliable storage location for research products. This is due to issues with version control and ease of loss (e.g., if someone's account becomes inactive and the files will disappear, but the folders remain and there's no indication of when that happened nor clear option for recovery).
I did also add a statement about maintaining specifically in a version controlled repo. OSC technically isn't unless git is initialized, though deleted data can be recovered within a reasonable time.