Allow archiving histories and workflows

[hexylena]

My users report having "too many histories" to deal with effectively. I feel their pain, and there are histories that I'm not going to reference very often but would like to retain forever.

I'd like to propose an "archive" for histories, it's another state that histories can transition into.

Properties:

• no modifications allowed (unless unarchived) (this need not be done for the initial implementation)
• not displayed by default (in the context of the "old" history menu where you have to click the advanced -> deleted to see deleted histories)

Update (2016-05-16): I've found the same issue with workflows. There are workflows which I should retain for historical reasons, but will never use again (or are broken, but we want to record exactly what was run)

[blankenberg]

To add to this, I'd actually find just a 'locked' attribute to be great to have separately from archived.

This is particularly important for e.g. published histories (especially ones referenced in papers) -- it is a sad day when you accidentally add some cruft to that perfectly created history that you want to share (instead of the copy you made).

[blankenberg]

Instead of just archived, could we create "Groups" for histories, where "Archived" could be a particular group? That way we can organize things even a bit better.

[hexylena]

@blankenberg sorry, missed your replies. A locked attribute would be amazing, I definitely agree w/r/t published histories.

Groups is an interesting thought. What sort of other groups would you envision having?

[hexylena]

Update: added workflows to this list. Same problem. I want them to be locked down and moved to a different area, out of my sight.

[lparsons]

This sounds like a great idea. I fully support it. I'd like to add another suggestion: the ability to delete underlying datasets in a history (to conserve space), but save the tool. Pretty much the same as a deleted dataset, but without deleting the item in the history. It would be great for users to be able to archive (online and offline) certain outputs (counts, fold changes, plots, etc.) but not some of the redundant or big data (raw fastq stored elsewhere, bam files, etc.). Of course, preserving the provenance of those final outputs would be needed.

Not sure if I made this totally clear, so please let me know if further clarification would be helpful or if there is a better place to record this.

[hexylena]

related: #3269

[bimbam23]

Ideas on how to archive data which is old, unused, ...

• add location where to archive data (maybe in galaxy.yml?)
• find out how old datasets are or if they are still used?
• define live time of data when uploading
• change color (gray) if dataset is archived
• make request of archived data if need

[hexylena]

I think I heard some discussion somewhere that an "archive histories" function could also enable moving them to colder, tape storage (for admins that configure it) which would be super fantastic.

[nomadscientist]

This would be brilliant! I have major issues with accidentally modifying histories I previously shared as examples, I'm a big fan of this. Plus presumably this could make them citable as well. i.e. 'made this tool, history is here for its use, cite me for being awesome' or some such.