Topic 8.2.1: Configuring Instances Through a .CSV File

  • Galaxy Dump

  • Object instances and their configuration data can be exported to a comma-delimited format Galaxy dump file (.csv extension).
  • The Galaxy Dump function only dumps instances. Templates cannot be dumped. The .csv file contains the configuration for the checked in versions of the selected objects as well as the checked-out objects of the user who initiates the Galaxy dump. The file contains only those attributes that are unlocked and configuration time-writeable, one column per attribute. Attributes that are locked, calculated or runtime writeable only are not saved to the file. The Galaxy Dump function only dumps instances. Templates cannot be dumped. The .csv file contains the configuration for the checked in versions of the selected objects as well as the checked-out objects of the user who initiates the Galaxy dump. The file contains only those attributes that are unlocked and configuration time-writeable, one column per attribute. Attributes that are locked, calculated or runtime writeable only are not saved to the file. 
  • Galaxy Dump File (.csv) Structure
  • Dumped objects are organized in the resulting .csv file based on the template from which each is derived. A header row per template indicates the instance’s columns’ reference. Comments can be added in the resulting .csv file by adding a line preceded by a semi-colon.
  • Galaxy Load
  • Object instances and their configuration data in an existing Galaxy can be exported to a comma- delimited format Galaxy dump file (.csv extension). A .csv file can be edited in most text editors and spreadsheet programs. Using editing functions like copy and paste, you can create quantities of already-configured objects ready to be imported into your Galaxy.
  • The Galaxy Load Conflict Resolution dialog box is displayed. Use it to resolve conflicts that occur if objects you want to load already exist in the Galaxy. The options are:
    • Replace entire instance if an instance of an object with the same name already exists and you want to replace it entirely with the object in the import file.
    • Only update changed attributes if an instance with the same name already exists and you want to replace only the attributes of the object where the values are different.
    • Skip if an instance with the same name already exists and you want to keep the version already in the Galaxy.
    • Stop Galaxy Load if an instance with the same name already exists and you want to cancel the Galaxy Load.

Last modified: Friday, 10 April 2020, 4:03 PM