Importing Names
Olympus provides a powerful feature to import names from CSV files. (Note: CSV was chosen as the standard, since most data can easily be stored in CSV format. For instance, Excel has a way to save any file as a CSV file).
The Import Names
feature is accessed from the people pane's More...
menu in the toolbar:
This launches an interface like this:
When this dialog opens, it immediately asks to pick a CSV file for import. Select a file from the dialog to proceed. Note that it is also possible at any time to load another CSV file through the Import CSV
button. This will clear the current data from the import workbench and load the chosen file.
Mapping columns
One of the key tasks that needs to be performed when importing names is to map the columns from the CSV file into meaningful data fields in Olympus. When opening a new CSV file, the import tool tries to make a best guess at what the columns in the CSV file might map to. The degree to which the tool guesses correct mappings varies greatly with the source data. When the CSV file has meaningful column names, it will do much better than when they are very generic. Ultimately, it is up to the user to make sure the mappings are correct.
The user can change mappings by clicking on the map indicator in the header of the grid shown in the Data to Import
tab of the dialog:
The list of Olympus fields the tool can map to is continuously extended. Here are the fields available at the time of this writing:
--Ignore Field--
- The source field is completely ignored and not importedCompany Name
- Name of the company the person is associated with.First Name
- First name of the person.Full Name (Search Name)
- Full name of the person (it is up to the user if this name includes the company name or not).Last Name
- Last name of the person.Title
- The person's title.City
- Address city.Country
- Address country. (The import tool will do it's best to map country names to the names stored in Olympus. For instance, it can handleUSA
as well asUnited States
. The names of the country have to be in English however.)Street 1
- Address street line 1.Street 2
- Address street line 2.State/Province
- State of province (for countries where that's applicable).ZIP/Postal Code
- ZIP or postal code.Email
- Email address.Web
- Web address (URL).Phone 1
- Phone number.Phone 2
- Secondary phone number.- Social Media:
Blog Address
- The URL of the person's blog.Facebook
- The Facebook ID of the person.Google ID
- The Google ID of the person.GitHub Name
- THe GitHub name of the person.LinkedIn Handle
- Linked in handle or URL.Twitter (X) Handle
- The X handle (formerly “Twitter”) of the person.Wikipedia
- The Wikipedia page of the person.Windows Live ID
- The Windows Live ID (Microsoft ID) of the person.Wordpress
- The Wordpress address of the person.Xing Handle
- The Xing Handle of the person.YouTube Handle
- The YouTube handle of the person.
Source
- Indicates where the names record came from. For instance, if we are importing a list with attendee data from the various conferences, the source column could contain a value such asMicrosoft BUILD
, indicating that we first encountered this person at that event. Note: If this map is set, and the record contains a value, it will override the default source setting chosen for the whole import (see below).Notes (multi-apply)
- The selected column is mapped to the notes field, and the header of the column is applied as a label to the note. For instance, if the header isRevenue
, and the value is$1 million
, the resulting note will beRevenue: $1 million
. Note that this map can be applied to multiple columns, resulting in multiple lines of text put into the note.- Notification Settings
Email Newsletter Opt-In
: Indicates, whether the person opted in for email newsletters. (If mapped, the setting overrides the default (see below). Valid values areTrue
,False
,Yes
,No
,0
,1
).Event News Opt-In
: Indicates, whether the person opted in for event news, such as webinars, training, conferences,… (If mapped, the setting overrides the default (see below). Valid values areTrue
,False
,Yes
,No
,0
,1
).New Content Opt-In
: Indicates, whether people opted in for new content being available (usually subscriber content). (If mapped, the setting overrides the default (see below). Valid values areTrue
,False
,Yes
,No
,0
,1
).Press Release Opt-In
: Indicates, whether the person opted in to receive our press releases. (If mapped, the setting overrides the default (see below). Valid values areTrue
,False
,Yes
,No
,0
,1
).Partner Announcements Opt-In
: Indicates, whether the person opted in to receive announcements we send out on behalf of our partners. (If mapped, the setting overrides the default (see below). Valid values areTrue
,False
,Yes
,No
,0
,1
).
In an ideal import scenario, all source columns will be mapped to an Olympus field. Often it may be beneficial to map otherwise unmappable columns into the Notes
field, which can act as a catch-all bucket.
Note that some fields are required for an import to take place, such as a name and some address information. (The tool will refuse to import if a minimum set of fields has not been mapped).
Import options
The top of the import dialog allows setting a number of general import options that apply to all imported records. They inciude the following:
Duplicates
- Defines how potential duplicates are handled. (A “duplicate” can be a name that we seem to already have in the database, or it could even be duplicates that are in the CSV file we are importing). The following options are available for duplicate handling:Do not check for duplicates and import names regardless
- No duplicate checking logic is applied. Records are imported without any consideration given to whether or not they may represent a name we may already have in the database.Check for duplicates and update existing names with new information
- Applies logic that checks if the record is a likely duplicate (by applying a duplicate rating score). If a high enough score is achieved where we think the record is a definitive duplicate, the existing record is updated with the new information in the CSV record. Note that this can be extremely slow!!!Check for duplicates and do NOT import names that seem to be duplicates
- Applies the same logic as in the prior option, but if duplicates are found, the record is NOT imported and instead put into theIgnored Rows
tab to be dealt with later. Note that this can be extremely slow!!!
Address Verification
- Applies US Postal Service verification of the provided address. Note that this slows things down somewhat, and also, as per the rules of the USPS, can only be applied to a small number of reords. Otherwise, this option is disabled.Max Rows to Import
- This setting can be used to limit how many records will be imported the next time theImport
button is pressed.Simulation
- When this option is set, the import is only simulated and no name records are actually added to the system. This is useful to “give it a try and see what happens”, especially when options such as duplicate checking are enabled.
Default values
This section defines default settings that are applied to imported records (these can be overridden by individually mapped columns. See above).
Source
- Indicates where the entire list came from. This setting defaults to the name of the CSV file being imported, but it can (and probably should) be changed to something more meaningful. Note that this setting can be overridden on a record-by-record basis, if a mapped source column exists (see above).Email Newsletters
- Indicates, whether the email newsletter opt-in flag is set to true or false by default.Event Information
- Indicates, whether the event notification opt-in flag is set to true or false by default.Press Releases
- Indicates, whether the press release opt-in flag is set to true or false by default.Content Notitication
- Indicates, whether the new content notification opt-in flag is set to true or false by default.Partner Announcements
- Indicates, whether the partner announcements opt-in flag is set to true or false by default.
Data Tabs
The import workbench features five different tabs for data. They can be used to move data around, work with successful or failed imports, put certain records aside for the time being, and so on. With that, the tool is not just a one-shot tool, but provides the ability to work with data.
Note that every tab provides a way to export the data shown in the tab to a CSV file. This is useful to then work with the exported data, perhaps clean it uo more, and then use it for another import run later.
Data To Import
This tab shows the main data that will be imported. New data can be loaded using the Import CSV
button (this removes all prior data).
It is also possible to select one or more records from the list (by clicking, CTRL
-clicking, or by selection with the arrow keys in combination with SHIFT
or CTRL
, or by pressing CTRL-A
to select everything, as well as other standard Windows key combinations) and then selecting Exclude Selected Rows
to remove rows from the next import run. The excluded rows will be moved to the Excluded Data
tab (see below).
This tab is also useful to map columns from the source into fields in Olympus (see above).
Whenever you are ready to import, click Import
to let the import algorithm run. Note that depending on the data size and the selected options, an import run can take a while. It may be useful to limit the number of records and perform the import in multiple batches. Note that rows that exceeded the import limit remain in this tab and subsequent import operations can be triggered later. Or, the remaining records could be saved into another CSV file and dealt with later.
Excluded Data
This tab holds import data that was excluded frm the main data import tab. These records are not considered for import. They can however be saved into a separate CSV file, allowign to return to the excluded records later. Also, this tab allows moving selected records back to the import tab.
Imported
This tab shows records that have been successfully imported. Usually, these records do not need further attention.
It is possible to double-click any of the reords in this view and open the imported name in Olympus. (This does NOT work when the import run was only simulated).
Note that simulated import runs also move the “imported” records to this tab, even though they weren't really imported or saved away. This is still useful, since it provides information about how many records have actually been imported. However, to run a real import run later, the user should select all records in this tab (hit
CTRL-A
for instance, to select all rows) and move them back to the import tab.
Ignored Rows
This tab holds all the rows that were not imported because they would have been considered duplicates. (This only applies if a duplicate checking option was selected - see above). It is often useful to then save these records to a CSV file, investinage the matter further, perform some cleanup tasks, and perhaps use the new CSV file later for another import run.
Import failed
This tab holds all rows that failed to import for any reason other than being ignored duplicates. It is generally also useful to save these rows into a CSV file and investigate further what the cause of the error was.