Acceptable format for Logikcull Database Upload

The database volume must be compressed with a .zip extension. If it is password-protected, the password must be removed prior to uploading. If it has multiple parts (e.g. .zip, .z01, .z02, etc.), the partitioned zips must be fully extracted, combined into a single volume, and compressed into a single .zip file first.

Directory structure typically includes the following folders within a top-level volume folder:

DATA

Contains the required metadata load file (DAT or CSV) and an image load file (OPT or LFP). Logikcull accepts the following encoding formats for these load files:

  • UTF8
  • UTF16
  • ISO-8859-1 (Latin 1 - also sometimes referred to as Western European) 

IMAGES

Supported formats:

  • Single page black and white TIFF and color JPEG 
  • Multi-page black and white TIFF
  • Multi-page PDF (black and white, or color)

NATIVES

Native path must be provided in the DAT file

TEXT

Text path must be provided in the DAT file

Load File Structure

  • The sort order between the metadata load file and the image load file must be aligned.
  • Metadata load file must have a header row with unique/clear field names so that they can be mapped properly.

Metadata load files must be in delimited text format, but you can choose which delimiters to use in the load file. Metadata load file makes use of three (3) main delimiters:

  • Column/Field delimiter: Denotes the separation between column/fields
  • Quote/Text Qualifier: Used to separate actual field data from the delimiters around it (especially useful when your field delimiter is a common character, such as a comma)
  • Newline: Code to denote a newline within the data encompassed by your quote delimiter (most often seen in extracted text fields or other long text fields)

We recommend these characters as delimiters, by default:

  • Column (separates load file columns) – ASCII 020 (¶)
  • Quote (marks the beginning and end of each load file field) – ASCII 254 (þ)
  • Newline (marks the end of a line in any extracted or long text field) – ASCII 174 (®)

Metadata load file must include at least the “Begin Doc” field. You can provide any additional fields in the load file. Fields that cannot be mapped to Logikcull directly can be imported in as new fields, or not imported at all.

Date and time fields in the metadata load file are preferably separate fields, and should be formatted as follows:

Date formats:

Date

mm/dd/yyyy

mm-dd-yyyy

yyyy-mm-dd

yyyymmdd

Time formats

 (along with a valid date that lines up with the Date-Time formats below):

Time

hh:mm:ss [AM|PM]
hh:mm [AM|PM]
hh:mm:ss
hh:mm

Date-time formats:

12/31/2019 1:13:30 PM
12/31/2019 1:13 PM
12/31/2019 1 13 30 PM
12/31/2019 1 13 PM
12-31-2019 1:30 PM
12-31-2019 13:13:30
12-31-2019 13:13
2019-12-31 13:13:30
2019-12-31 13:13
20191231 131330
20191231 1313
2019-12-31T13:13:30-06:00
2019-12-31T13:13:30Z

Months (mm), days (dd), and hours (hh) may all be denoted by a single digit.
If the time is in military format, the AM/PM indicator is not required.

Fields available for direct mapping in a Production Upload

(*) “Family ID”, “Begin Family” and “End Family”, or “Begin Attach” and “End Attach” fields are utilized to establish a family relationship. This can only be accomplished during the initial upload, so include these fields, if applicable. Example of supported metadata information for family members shown below.

(†) “Native File Link” and “Text File Link” in the metadata load file, and the Image File Link in the image load file must be in the relative format.

Metadata load file must include at least the “Begin Doc” field. You can provide any additional fields in the load file. Fields that cannot be mapped to Logikcull directly can be imported in as new fields, or not imported at all.

Did this answer your question?