Difference between revisions of "Importing Data"

From zFairs Contest Management
(Create Importing Data from Support instructions)
 
Line 1: Line 1:
 
== Importing registrations ==
 
== Importing registrations ==
# Go to '''Staff → Import Data'''
+
== For Registrations ==
# Confirm you are on the correct tab (defaults to participants)
 
  
# Click '''Choose File''' and select your CSV
+
# Go to Staff > Import Data
# Map the columns:
+
# It will take you to this screen:
 +
#: [[File:Import_Data_Screen.png]]
 +
# Make sure the correct tab is open. It defaults to participants, but it's always good to check.
 +
# Then select Choose File. Select the CSV file that you want to load.
 +
# Then you are asked to Map the columns:
 +
#: Each of the columns in your file should show, along with the title you named the column. You then need to select the item from the drop down list that matches the item in the CSV file.
 +
#: Note: All of the entries in your CSV file should match entries in your registration. If you notice that there is a field/column in your file that is NOT in your registration, close the file and DO NOT process. The item will need to be added to the registration in order for the data reports to collect the correct information. Go into your registration and add the item, then retry the import.
 +
#: If you have headers, don't forget to select that the first row are headers, or else it will create a "header" account.
 +
# When you are done mapping, select “process file”, double check to make sure your file looks correct, then click "Load".
  
# Each CSV column should map to the matching registration field via the dropdown
+
=== Some things to take into consideration: ===
 
+
* As long as the First Name, Last Name and Email are the same, any other differences for accounts will be changed if uploading the CSV file multiple times, without creating a duplicate account. This can also cause information to be cleared from existing accounts.
'''Important:''' All CSV columns should match fields in your registration. If a column is not in registration, '''do not process''' — add the field to registration first, then retry. Otherwise data reports will not collect correctly.
+
* When creating TEAM projects, be sure to add an Entry ID column. Then assign any number to the projects with team members receiving the same number.
 
+
* If using multiple entries, add an External Entry ID. ALL PROJECTS should be assigned DIFFERENT numbers. First Name, Last Name and email of the participant should be provided for every project as well. NOTE: multiple entries will create what appear to be duplicate accounts on the people page. Just take note that multiple entries does not mean multiple participants, and the counts will show different numbers.
If the file has headers, select that the first row is headers; otherwise a “header” account may be created.
 
 
 
When mapping is done, select '''Process file''', verify the preview, then click '''Load'''.
 
 
 
== Considerations ==
 
* Matching '''First Name + Last Name + Email''' updates an existing account on re-import (other fields can change or clear). Avoid accidental data wipes.
 
* For '''TEAM''' projects, add an '''Entry ID''' column; teammates share the same number.
 
* For '''multiple entries''' per person, add an '''External Entry ID'''. All projects get '''different''' numbers. Provide First Name, Last Name, and email for every project. Multiple entries can look like duplicate people accounts; counts for entries vs participants will differ.
 
  
 
== Related pages ==
 
== Related pages ==

Revision as of 16:37, 6 August 2026

Importing registrations

For Registrations

  1. Go to Staff > Import Data
  2. It will take you to this screen:
    Import Data Screen.png
  3. Make sure the correct tab is open. It defaults to participants, but it's always good to check.
  4. Then select Choose File. Select the CSV file that you want to load.
  5. Then you are asked to Map the columns:
    Each of the columns in your file should show, along with the title you named the column. You then need to select the item from the drop down list that matches the item in the CSV file.
    Note: All of the entries in your CSV file should match entries in your registration. If you notice that there is a field/column in your file that is NOT in your registration, close the file and DO NOT process. The item will need to be added to the registration in order for the data reports to collect the correct information. Go into your registration and add the item, then retry the import.
    If you have headers, don't forget to select that the first row are headers, or else it will create a "header" account.
  6. When you are done mapping, select “process file”, double check to make sure your file looks correct, then click "Load".

Some things to take into consideration:

  • As long as the First Name, Last Name and Email are the same, any other differences for accounts will be changed if uploading the CSV file multiple times, without creating a duplicate account. This can also cause information to be cleared from existing accounts.
  • When creating TEAM projects, be sure to add an Entry ID column. Then assign any number to the projects with team members receiving the same number.
  • If using multiple entries, add an External Entry ID. ALL PROJECTS should be assigned DIFFERENT numbers. First Name, Last Name and email of the participant should be provided for every project as well. NOTE: multiple entries will create what appear to be duplicate accounts on the people page. Just take note that multiple entries does not mean multiple participants, and the counts will show different numbers.

Related pages



Updated from Support instructions (2026).