There are times when you’ll want to add person information and/or pictures into KeepnTrack from outside sources such as your central district or facility database; a process called "importing". The Imports interface places everything you need to quickly find, modify, and run an import of patron, item, and transaction command information.
The first step in performing an import is picking the correct import type. The Categories pane on the left-hand side of the window is where you choose the import whose settings appear in the Import Selection pane on the right.
Allows you to upload and integrate person information from simple text documents or data files.
Upload a ZIP file containing person pictures. When importing, KeepnTrack will attempt to match image filenames with Student ID, Person ID, or Staff ID. Image files should be 186 x 240px and must be in the JPEG, GIF, PNG, or BMP format.
KeepnTrack has the ability to import new (or update existing) Person record information from a record database stored on an FTP server.
The larger, right-side of the Import interface is dedicated to the selected import type and contains all of the import's configurable settings and options. The information that appears in this pane relates directly to the import type selected from the Categories pane. It contains all of the configurable settings and options essential to how your import is performed. For example, if you select Automatic Import from the Categories pane, the results here will adjust accordingly.
Before going further, it helps to understand some basic concepts about computerized records. In order to exchange information between different programs (or even between different computer systems), one needs the information in a format that many different programs can understand. The standard, called ASCII, is widely used to exchange information between different programs and operating systems. Sometimes an ASCII file is called a text file (.txt) because all it contains is textual information.
ASCII files contain two types of characters: standard visible characters such as numbers and letters of the alphabet, and special control characters used for special purposes to control the display or interpret information in the file. If you have computerized data, you may be familiar with the <tab> and <return> control characters that are used to make text more legible.
When dealing with computerized information systems, you often hear the terms field, record, and file. A field is the smallest unit of information stored. An example of a field is a person's last name. A record is a related group of fields. Many records of the same type saved together are called a file. For example, in a file of names, a record consists of the fields “First Name” and “Last Name”. A more complex file may include records with other fields such as “Phone Number” and “Address”. In other words, records contain fields filled with information, and files contain many records.
Most database, spreadsheet, and word-processing programs support files in a tab-delimited format, which KeepnTrack is capable of importing.
A very common method of exchanging record information between programs is the tab-delimited ASCII file. Using tab-delimited import files, you can transfer information about people stored in other computer systems. For example, a school can use this capability to transfer student information from the school administration computer system into KeepnTrack.
In the tab-delimited format, fields are separated by the <tab> control character and the end of the record contains the <return> control character.
Bill <tab> Jones <return>
Smith <tab> John T.<return>
My First Name <tab> My Last Name <return>
KeepnTrack’s Tab-Delimited Import File Format
In KeepnTrack, we've enhanced the tab-delimited format by adding special information on the first line of the file, used to interpret data in the file. This first line is called a header because it's at the head (or beginning) of the file. The header allows programs to figure out where the data in the file belongs. KeepnTrack’s headers look like this:
The ###*PT01 doesn't mean anything, but is a rather unusual character combination, unlikely to be found at the beginning of most files. If KeepnTrack discovers ###*PT01 at the beginning of a file, it assumes that the file is in a familiar format, and will update the database accordingly.
The Field Codes (shown above) don't have any special meaning other than acting as unique identifiers for each of the fields that can be imported or exported, and identifiers are surrounded by slashes. A complete list of KeepnTrack field codes can be found in Import Field Mapping.
Although a file header is optional, KeepnTrack presumes that every import file has one. However, KeepnTrack only knows how to process headers in the format stated above. If one is present, KeepnTrack will automatically analyze, sort, and relay the import information to the proper data fields. If there is no header, KeepnTrack displays a Field Mapping dialog, which allows you to manually order the data being imported.
Some fields allow multiple lines of information (such as first and middle name). Any <return> located in a field is converted into the ‘\’ character on export and on import, the ‘\’ character is restored to a <return>. Generally, you don't need to know about this; however, if you were to examine an exported file, you'd see these characters. Also, if you wanted to add a <return> into a file that is getting imported, you can use the ‘\’ character to make it happen.
Be aware that newly imported people must be associated with a facility; this is currently done using 1027 in the import file header. If a person belongs to multiple facilities, repeat 1027 in the header and then use <tab> to separate the facility IDs (e.g. StudentID#<tab>FacilityID01<tab>FacilityID02<tab>FacilityID03...) in the person record.