This is an old revision of the document!
The structure of a track can be exported and import. This procedure does not export and import the surveys, but the rounds, fields and other attributes that define a track.
The surveys are expected to exist already at both the source (export) and target (import) locations.
Also the current version does not export “Appointment filters”. If the track uses “Appointment filters” for automatic appointment linking and / or track creation you will have to manually transfer the filters. We expect to solve this in the next version.
To export a track, select the track in “Trackbuilder” ⇒ “Tracks” and choose “Export”.
The first screen allows you to choose which fields and rounds to export. You can also check or uncheck “Organization export”.
Organization export does not export the organisations in the source GemsTracker installation, but just their names. The organisations existing with the same name the import installation will selected as active for the track during import.
If your track export contains surveys, the next screen asks export codes for them. Export codes are special survey codes that are only used for track import and export. They are used because the survey can have a different name at the import location. All other possible identifiers can also change from system to system so we need some method to link a survey on the source system and the target system.
Of course if the target system is the source system you will need to enter these codes only during the export. If both systems are different the importer will have to select which survey to link to which export code. If the name of the survey exists on both systems this will be very straightforward, otherwise the right survey can be chosen from a drop-down list.
Survey export codes are stored at the survey level and one survey can have only one survey export code. If you need to change that code edit the survey in the Track Builder.
After setting the export codes (if any was empty) the download of the track definition starts automatically.
The track definition is stored in a tabbed text file with the extension .track.txt. You can edit this file using any text editor, e.g. Notepad.
The definition files contain four type of lines:
To import a track choose import in the Trackbuilder ⇒ Tracks.