Overview, Import source file, Overview import source file – Interlogix Topaz Reference Manual User Manual

Page 5

Advertising
background image

1

Overview

The information contained in this manual provides instruction on uploading and converting an
external cardholder database to a Sapphire Pro or Topaz host.

Note: The illustrations included in this document are based on the Sapphire Pro user interface; however the field

references are the same in Sapphire Pro and in Topaz.

Import Source File

This file can be generated as an export file from a database on another computer or network. For
example, human resources has a separate system and uses a stand alone employee database.
Most databases can export some or all data into a comma delimited file. The file should be placed in
a common location where both systems can access it. It should contain only information to be used
in the host (Sapphire Pro or Topaz) system. Other fields cause the file to be rejected. If automatic
rather than manual import is going to be used, the field names used in the export/comma delimited
file must match the field names in the employee descriptor file. It must also follow the formatting
parameters described below. Some of the formatting may require manual manipulation of the file
(such as keypad masking permissions) if an automatic import method is used, it may be better for
these changes to be added manually once the record is in the host system.

Information Needed to Format the Comma Delimited File

Depending on how comprehensive the information in the import file is to be, one or more of the
following documents may not be required.

To prepare the comma delimited file for importing into the host system, the operator needs several
reference documents:

The list of Field Titles that are used in the host system. These are found in the second column
of the

“Employee Table Field Descriptions” on page 5

If Access Groups are a part of a card record, the operator needs the names of Access
Groups as they are used in the source database along with the corresponding Access
Group ID Numbers
that are used in the host database (Sapphire Pro or Topaz).

If the Card Status is to be included in the card record, the operator needs the Sapphire Pro or
Topaz numerical ID numbers, used to identify Card Status, that are equivalent to the ones
used in the source database.

If Security Areas are to be included in the card record, the operator needs the Sapphire Pro
or Topaz numerical ID numbers, used to identify Time Schedules, that are equivalent to the
ones used in the database that is being imported.

If Custom Fields are to be included in the card record, the operator needs a reference guide
that lists these fields and the USERFLD numbers that are used in Sapphire Pro or Topaz to
hold this information.

The more concurrence there is between the fields in the source database and the employee field
descriptors in the host database, the easier it is to import the data into the security system.

Note: If the automatic Import function is enabled, these fields should be exact matches. Otherwise, the.cvs file must be

formatted each time there is an import.

Advertising