Field mappings
Mapping of CSV fields with CORE fields.
Fields present in the CSV load file, but not defined here are added to the XML without any change.
If you use the Create New Data Source Wizard, the Type column is filled automatically.
Fields as found in the load file. You can map a CSV field to multiple CORE fields.
- field names as used in load file
field<number>, if the load file has no header.
- None
This column contains internal field names or temporary field names, for which no field exists yet. For standard file crawls that use a CSV reference file, a string that does not match a field name may be required.
- None
Perl expression for altering a field’s content when transferred from a load file.
- None
The type defines the handling and content of a field.
-
- Attachment ID
- This type marks the ID of an attachment and can only be used once.
You won’t get attachment relations when you do not define this ID. If you use
Concordance format, the
begattachfield is assigned this type.
-
- Attachment ID range end
- This type marks the last ID of an attachment and can only be used
once. You must define the document type (rm_doctype) manually using the rules
when this ID is not defined. f you use Concordance format, the
endattachfield is assigned this type.
-
- Date
- This type marks a date field.
- The datasource crawler recognizes these fields as date fields and, for instance, adds a time zone if it is not provided by the CSV file.
-
- Date (day) and Date (time)
- Concatenates date and time strings from separate CSV fields if both are mapped to the same document model date field.
- The datasource crawler recognizes these fields as date fields and, for instance, adds a time zone if it is not provided by the CSV file.
-
- File
- This type marks fields that contain a file path.
-
- File (content only)
- This type marks a field that contains the file path to a plain text file.
-
- File for byte length
- Type that marks the field that contains the names of the files from which the file size is calculated.
-
- File for MIME type detection
- This type marks the field that contains file names that are used for MIME type detection.
-
- ID
- This type must be defined exactly one time. It marks a mapping for the CSV document key.
Note: The CSV document key field can be mapped to fields of another type, too.
-
- ID range end
- This field contains the last ID of the document and can only be
defined once. If Concordance files are loaded, the
endbatesfield is assigned this type.
-
- Image storage location
- Marks the field that contains the file path to images. This can be used if you have no OPTICON file, but the load file contains references to images. A CSV field with this type does not need to be mapped to a document model field. In the Mapped to column, the name of the CSV field is repeated. The Image storage location type is sufficient to treat image references correctly after publishing. It is used to configure the storage handler of the index engine for Axcelerate 5, which is for loaded images.
-
- Native file
- Marks the field with the reference to the native file.
-
- Native storage location
- Marks the field that contains the file path to the folder where native files are stored.
-
- Text
- This type is used for all fields that do not need any special treatment.
-
- URI
- Marks the field that contains the URI.
-
- Ignore
- Fields of this type are filtered. Their content is not added to the XML file, but can still be used in a rule.
- Text
Character that separates multiple values in one field.
- ,
Field Mapping for Standard File Crawls
Alter Field Content with Perl Substitutions