Fix for determining the list of all repository dependency dictionaries when installing a repository into Galaxy that has a deep dependency hierarchy.
Fix to 197878e: properly namespace def and use in grid_async
History, structured: wrap copied HDA's in info about library/history they were copied from
D'oh: fix to ef8ef4ff2e15
Fix for setting environment paths when using setup_virutalenv.
History: allow admin to use display_structured w/ id, add display_structured link in history/view, allow switching to a history from history/view
History options: have 'Purge deleted datasets' update the user disk size
Fix sample tracking functional tests.
More refactoring of tools API test case.
Record history content type with output of history contents API.

Downstream in dataset collections branch this isn't just dataset, including this will allow clients to distinguish between different kinds of content.
Refactor backbone models to allow different kinds of history contents.

In particular, add a new backbone parent model (HistoryContent) refactored out of HistoryDatasetAssociation. This makes room for a forth coming HistoryDatasetCollectionAssociation model that will be emitted from the history contents API.

There are likely better ways to share common functionality between a dataset and a dataset collection contents - more JS savy developers should feel free to refactor into smaller mixins for instance. For now HistoryContent is just composed of the overlap in functionality between dataset and collection representations downstream and is an quick and dirty way to share said functionality.
Refactor backbone views to allow different kinds of history contents.

This makes room for a forth coming HistoryDatasetCollectionAssociation model that will be emitted from the history contents API. Same comment as previous changeset applies - this is a potentially crude way to share duplicated functionality and a better design would be most welcome.
Rename historyPanel.refershHdas to refreshContents.
Add simple module verions of validation stuff in base controller.

For reuse outside of controllers (i.e. in dataset collections). Objections to refactoring base controller stuff to use this?
Extract base class from DataToolParameter to be shared with DataCollectionToolParameter.
Dataset collections - models - basics.

Mapping, model definition, database migration, and model unit tests to support database collections.
Dataset collections - models - mapping to allow HDCA to hide HDAs under it.

Should help keep the history panel in check initially hopefully.
Dataset collections - models - add history.active_contents.

Get all active datasets and collections ordered together by hid. Used downstream for instance when extracting workflows from histories.
Dataset collections - models - history copying.

Copy history dataset collection associations when histories copied.
Dataset collections - infrastructure glue.

Add an API and service layer for dataset collections.