Basic Card Import (CSV) - SG Import Utility

 

 

This topic covers the basic steps to import new cards/cardholders from a CSV Conversion File into a blank SysGal database by using the SG Import Utility.

 

N

See System Galaxy User Guide for more about data formats and import capabilities not covered in this QRS.

 

 

i

See prerequisites and stipulations on the back page for creating the CSV Source Data Conversion File *.

 

 

M

Before you execute an import, perform a database backup of SysGal databases to preserve any programming.

 

 

Create the Conversion File

  1. Obtain a Source Data Conversion File (.CSV format) from the end-user’s existing system or DBA.

Ý

(recommended) the Conversion File should have a valid header row to prevent dropping data.

Example of a CSV conversion file in comma-delimited format.

  

 

  1. Copy the Data Conversion File (CSV) into an appropriate folder location*.

Ý

(recommended) Create a folder where you will have access when you start the import – such as C:\\GCS\System Galaxy\SG-Import\SG_Import.csv   – or other local/network folder. 

 

 

 

Create the ODBC Data Source for the Conversion File

This describes how to define an Import ODBC DSN Name and attach the appropriate Microsoft driver.

 

  1. Browse to/Open the ODBC Data Source Administrator (32bit required).
    (You can find it by typing Administrative Tools into the search field on Windows Taskbar. )

  2. Select the System DSN tab and click the Add button to open the Create New Data Source dialog.
    (you should see your SysGal ODBC DSN’s already listed.)

 

  1. Select (highlight) the “Microsoft Text Driver (*.txt *.csv)” in the list-view.

 

  1. Click the Finish button. (This will open the ODBC Text Setup dialog).

  2. Type a Name and Description, uncheck ‘Use Current Directory’ and click the [Select Directory...] button.

     

  3. Select the directory where the Conversion File is stored and click OK button to save the path.
    (the     Conversion File should appear in the list-view on the left side when you choose the folder.)

 

 

  1. When you return to the ODBC Text Setup screen, the new directory path will display.

 

  1. Click the OK button to exit the ODBC Text Setup screen.

 

  1. You should see the SG_Import ODBC Data Source listed with the Microsoft Text-Treiber driver attached.  Click OK button to exit.

 

 

 

 

 

Launch the SG Import Utility and Connect to the SysGal Database.

The Card Import Utility must be connected to the SysGal Data Source before you can import users/cards.

 

  1. Launch the SG Import Utility by double-clicking the SG-Import.exe file
    (located in the     C:\GCS\System Galaxy\Utilities folder)

    1. select File > Connect from the SG Import menu.

    2. select the Machine Data Source tab (you should see the SysGal DSN listed)

    3. Select (highlight) the SysGal DSN name and click OK button (opens SQL Server Login window).

 

 

 

  1. Enter the valid password for the SysGal database login and click OK button.

     

     

     

  2. Now you are logged into the SysGal database and ready to create the Import Card Profile.

 

 

 

Set up the Data Import Profile for the CSV file

These steps visit the basic fields for importing a CSV Conversion File. See the Software User Guide for more.

  1. Open the Import Card Data screen from the menu after you have connected to the SysGal database

    1. Select File > Edit Profile from the menu to open the Import Card Data screen.

    2. Import from Data Source droplist: choose the name of your Import ODBC Data Source.

    3. Select Table to Import From droplist: select your Data Conversion File.

  2. Magnifying Glass button: click this to display a preview the first few rows of the selected file.

  3. Specify Card Format droplist: select the type of card format – such as ‘26-Bit Wiegand’.

  4. Data Mapping Listview: shows two columns (i.e. System Galaxy Columns and Import Source Columns).Be careful to map columns correctly. Incorrect mapping can cause total or partial failure to import.

    1. In the System Galaxy Column: click on the Column_Name that you want to map. 
      (An empty droplist will appear in the Import Source Column).

       

    2. In the Import Source Column: choose a corresponding column from the Conversion File that you want mapped to the selected System Galaxy column.

      TIP: Press <Tab> keyboard key to escape each droplist without disturbing your selection. This prevents unintentionally changing a setting in the active droplist while you scroll the listview to find the next column.

    3. Continue mapping each import column to the appropriate SG column.

 

  1. Click Import Now button.

  2. When prompted enter a File Name for the Import profile.

  3. Click SAVE button to execute the import procedure.
    (    the Log File will display the import results, including how many successful transactions, as well as how many cardholders and cards were inserted into the SysGal database.)

  4. You can sign-in to System Galaxy and view the cardholders appear in the Cardholder screen with all data present that you imported.

 

Import Prerequisites for the CSV file

These requirements are based on using a comma-delimited CSV conversion file for importing new users in a new System Galaxy database that has minimal programming. Contact authorized technical support as needed.

 

  1. System Galaxy has a 14-day grace period to import Cards and Cardholders before license registration.

  2. You need a valid login to the SysGal database to connect the Import Utility.

  3. The Card Import Utility will not import records that have duplicate card codes, or unique id’s.

  4. Any individual columns that contain invalid data (out of range, etc.) might not be imported during the Card Import Process, even if the primary data is imported and a cardholder or card is created; thereby leaving the offending field unset in System Galaxy. Results will be in the import Log File.

  5. The conversion file must obey valid, SQL-compliant formatting …

    • Must include a header row

    • Column_Names must be SQL-compliant

      • cannot not include spaces or special/reserved characters (quotes, tics, hyphens, etc.).

    • Must use the correct formatting for data-types and value separators – such as integers, dates, or date/time. A solidus (/) is not a valid date separator in SQL.

      • YYYY-MM-DD (no spaces; use hypens for date separators; no tics or quotes;)

      • YYYY-MM-DD hh:mm:ss (use hypens for date separators; use colons for time separators; one space between the date and time; no tics or quotes;)