Skip to content

Import / Export Data

SkatingApp supports multiple import and export functions. This page describes the basic import and export functions and provides example files where appropriate.

Import Skaters

You can import new skaters into SkatingApp by supplying an Excel file with the basic information about the skaters. To access the import function, navigate to File -> Import -> Skaters.
A dialog window will pop up, allowing you to navigate to an Excel file to use.

The Skater Import function expects an Excel file with the following columns:

  • isuid: The official ISU ID issued by the ISU. You can leave this column empty when not dealing with ISU skaters.
  • firstname: (required) The first name of the skater.
  • lastname: (required) The last name of the skater.
  • gender: (required) The gender of the skater. Use 'M' for Male and 'F' for Female. Cyrillic equivalent characters are also allowed.
  • birthdate: The date the skater was born.
  • country: (required) The country of the skater. SkatingApp uses IOC country codes. For a full list, see List of IOC Country Codes.
  • region: The region of the skater. Regional codes are tied to the country.
  • category: The age category of the skater. The age categories must exist within the SkatingApp. They can be managed from the database menu or imported from Excel.
  • club: The club of the skater.
  • teamsponsor: The team/sponsor of the skater.
  • city: The birth city of the skater.

Click here to download an example of the skater Excel file.

Import Age Categories

You can import a list of age categories from Excel. To access this import function, navigate to File -> Import -> Categories.
A dialog window will pop up, allowing you to navigate to an Excel file to use.

The Categories Import function expects an Excel file with the following columns:

  • code: (required) The short code for this age category. For example, this could be M30, B5, etc.
  • name: (required) The name that should be displayed for this age category.
  • minage: The minimum age allowed to participate in this category.
  • maxage: The maximum age allowed to participate in this category.

Click here to download an example of the category Excel file.

Import and Export Transponders

You can transfer the transponder inventory between Excel and the database using File -> Import -> Transponders and File -> Export -> Transponders. The Database -> Transponders window also provides Import and Export buttons. Save or cancel any unsaved changes in that window before importing or exporting.

Excel File Format

Import accepts .xls and .xlsx files and reads the active worksheet saved in the workbook. Select the intended worksheet in Excel and save the workbook before importing. The first row must contain the following required column headers:

ChipCode TransponderId
00123456 073L
AB-987 073R

Download an example transponder Excel file.

  • ChipCode: The code printed or scanned from the transponder, from any brand. It must contain between 1 and 10 characters after removing surrounding spaces. Letter case, punctuation, and leading zeros are preserved. Format this column as Text in Excel before entering codes so Excel preserves leading zeros.
  • TransponderId: The inventory label, consisting of one to three digits followed by L or R. IDs are normalized to three digits and an uppercase side letter; for example, 73L becomes 073L.

Header matching ignores letter case and surrounding spaces, and the two columns may appear in either order. Additional columns, including scan timestamps, are ignored. Scan timestamps are not stored or exported. Transponder IDs do not need to form pairs or a consecutive sequence; missing numbers and sides are allowed.

Import Transponders

Select File -> Import -> Transponders or click Import in Database -> Transponders, then select your Excel file.

SkatingApp validates the whole file before making changes. Missing or duplicate required headers, invalid values, partially filled rows, duplicate normalized transponder IDs, and duplicate chip codes cause the import to be rejected. Duplicate chip codes are checked using the database's comparison rules, which may treat differently cased codes as duplicates. Completely blank rows are skipped, and a file without any transponders is rejected.

Import replaces the entire transponder inventory and clears all transponder assignments in all competitions. Review the confirmation before continuing. Export the current inventory first if you want to keep a copy.

Canceling the confirmation, an invalid file, or a failed import leaves the existing inventory and competition assignments unchanged. The replacement is saved as a single transaction, so a failure rolls back the entire change.

Export Transponders

Select File -> Export -> Transponders or click Export in Database -> Transponders, then choose where to save the .xlsx file.

The export contains the saved database inventory, sorted by transponder ID, with ChipCode followed by TransponderId as the column headers. It uses the same format as the example file and can be imported again. Save any editor changes before exporting if you want those changes included.

Import from Vitesse (speedskatingresults.com)

SkatingApp supports data exports from Vitesse as a source for start lists and competitions. This is done via the JSON export functionality found in Vitesse. To export the participants or start lists in JSON format, select File -> Export -> JSON from the main menu in Vitesse. SkatingApp supports both the Start Lists and the All.. options from the export menu.

Vitesse - Export JSON menu

After saving the JSON files from Vitesse in a folder, you can import them into SkatingApp. Using the main menu, select File -> Vitesse (SSR) -> Import Event File.
Select Import Event File when you export the JSON using the All... export type in Vitesse. If you only export the Start Lists, select Import Start Lists File from the menu in SkatingApp.

Vitesse - Import into SkatingApp

Important Notes

  • If the import function encounters a skater that it can't identify by their Speed Skating Result ID, a new entry will be automatically created.
  • To avoid potential conflicts (double entries of skaters), consider trying this feature on a clean database first.