Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

There are 3 levels of configuration. This section describes the import configuration. All import configurations are xml-files located in a subfolder of the Importer installation named ImportConfigs. Every xml-file in this subfolder will be perceived as a configuration file. Only files with xml extension are read. Everything else is ignored. Here is a list of all possible configurations.

...

languagexml

...

The importer service is configured from the MediaManager UI under General settings/Importer.

It is enabled by creating a configuration and enabling that.

To create a new import configuration navigate to the before mentioned path and hit the Create new button in the top right corner, see screnshot

Image Added

From here there are the following configuration options.

Info

The UI will change depending on a few of the selections and the below screenshot highlights as many options as possible.


Image Added


KeyDescriptionData type / descriptionDefault
value 1)In use whenLanguageIdA valid DAM system language ID.IntegerNoneAlways. Required.UploadDirectoryThe hotfolder to watch for input.StringNoneAlways. Required.SheetDirectoryDirectory for metadata sheets. When left empty it defaults to UploadDirectory.StringNoneWhen RunMetadata is true and MetadataParser is CSV or Excel. Optional.ZipContentDirectoryDirectory for zipped content. Zip content will be unpacked to UploadDirectory.StringNondeWhenever set this directory will always be checked first and all content unzipped before reading UploadDirectory.SuccessDirectoryWhere to put files successfully uploaded - including metadata files. Leave empty to simply delete these files.StringEmptyAlways. Optional.FailureDirectoryWhere to put files that failed during upload og metadata processing. Leave empty to simply leave failed in place in which case they will be retried. It is recommended to set this to avoid having the Importer repeatedly try and fail.StringEmptyAlways. Optional.DeleteEmptyDirectoriesWhen true all empty directories below UploadDirectory will be deleted after files and/or metadata have been ingested.BooleanFalseAlways. Optional.RunUploadSet true when in need of asset ingest.BooleanFalseAlways. Optional, but if not set RunMetadata must be true.ComputerNameUploadChunkSizeSize in bytes of chunks when uploading files.Integer / cannot be lower than 1mb26214400 (25mb) 2)When RunUpload is true. Optional.FileNameStampType
value
NameA name that must be unique used to identify the import configurationStringNone
Upload directory

This is the hot folder import path.

If this is running on a virtual machine, this must point to an accessible directory on the web server (e.g. C:\Storage\upload\hotfolder).

If this is running in kubernetes in must be a relative path on the provided sftp server (e.g. /hotfolder)

StringNone
ActiveThis enabled/disabled the import configurationBitFalse
Zip content directoryIf this is specified, then a zip file containing the entire import can be dropped in this directory. The contents is then extracted and put in the specified UploadDirectoryStringNone
Run uploadSpecifies if this configuration is used for upload or metadata import. If false, no files are uploaded and the import configuration is assumed to be metadata importBitTrue
Computer nameAn identification token of the uploading application. This name can be used in automations to identify where the upload is coming from StringNone
ImporterWhen RunUpload is true. Optional.
Archive on replaceSpecifies if the import should do duplicate detection. If yes, duplicates are replaced.BitTrue
Keep metadataIf ArchiveOnReplace is true, this specifies if the metadata should be copied to the new version. If true, the metadata is copiedBitTrue
File name stamp type

How filename is stamped. Example:

  • FileNameOnly: AwesomeMe.jpg
  • FileNameNoExtension: AwesomeMe
  • RelativePath: \GoodStuff\AwesomeMe.jpg (if 
  • AbsolutePath C:\Upload\GoodStuff\AwesomeMe.jpg

Enum:

  • FileNameOnly
  • FileNameNoExtension
(5.2.1+)FileNameStampMetafieldIdId of metafield where filename will be stamped.IntegerNoneWhen RunUpload is true. Optional.LastWriteDelayBeforeUpload

Delay in seconds from a file has last been written to the Importer will upload it. The default is zero and this has been the default behavior for the Importer since the beginning.

Leave this at 0 unless using FTP or perhaps a 3rd party file integration that fails even when TreatZeroByteFilesAsFailed is false.

Integer0When RunUpload is true. Optional.TreatZeroByteFilesAsFailed

How to handle zero-byte failes. True will handle them as failed files. False will ignore and essentially retry again later. It is important to set this false when input is ftp or similar input that allocates a zero-byte file and writes it later.

The default is false and this alters the behavior which before the introduction of this setting always treated zero-byte files as failed. This setting was introduced in the 5.4.0-139 build.

BooleanFalseWhen RunUpload is true. Optional.RunMetadataUpdateSet true when i need of metadata ingest.BooleanFalseAlways. Optional, but if not set RunUpload must be true.MetadataFileNameA fullpath reference to a file containing metadata configuration. See Metadata Configuration.StringNoneWhen RunMetadata is true and metadata is preconfigured (Xml2Metadata).CultureA standard string describing a culture setting. See Culture names and identifiers for supported values.Stringen-USWhen RunMetadata is true and there are any dates or floating points in the metadata input.BulkSizeHow many assets are updated in one bulk.Integer5When RunMetadata is true.MetadataParser

The type of medata input.

  • CSV: when metadata is a CSV sheet.
  • Excel: when metadata is an Excel sheet.
  • Xml2Metadata: when metadata is an xml file.

Enum:

  • CSV
  • Excel
  • Xml2Metadata
NoneWhen RunMetadata is true. Required then and ignored otherwise.ComboSeparatorWhen special character to use as delimiter for values of any combo or tree type.1 special character.;When RunMetadata is true and MetadataParser is any of the sheet types. Optional (but required if your delimiter is different from the default.ComboMatchStyleWhen matching input values against existing tree- or combovalues should the importer user textvalue or optionvalue.

Enum:

  • TextValue
  • Option
TextValueWhen RunMetadata is true this settings will have an effect for every metafield of tree- or combotype. It is possible to specify for specific metafields in which case this setting is ignored.FileNameColumnWhich column in the sheet holds the filename of the file to upload.Integer (1-based index)NoneWhen RunMetadata and RunUpload are both true and input type is any of the sheet types.
  • RelativePath
  • AbsolutePath
RelativePath
When RunUpload is true and FileNameStampMetafieldId is set. Optional.
Stamp FieldSpecifies the metadata string field in which the upload filename is put in. The value is based on FileNameStampType configurationStringFullpath UNC metadata field
Success Action

Specifies what to do with the file on Success. Notice you must specify a destination directory on Move action.

Enum

  • Delete
  • Move
  • Keep
Delete
Failure ActionSpecifies what to do with the file on Failure. Notice you must specify a destination directory on Move action.

Enum

  • Delete
  • Move
  • Keep
Move
Delete Empty DirectoriesIf true, any sub directory that is empty once the import has completed will be deletedBitFalse
last Write Delay before uploadThis specifies for how long the importer should wait before uploading files after the files has been moved to the hot folder. This may need to be increased for sFTP drop folders as that is transported over the internet, rather than an internal file copy on disk.Int0
Treat zero byte files (empty files) as failedThis is related to the above setting. If the file is uploaded before the move to the folder has been completed, then specially FTP servers will create a new file which has zero bytes. This generally should be True.BitTrue
CultureThis controls how datetime and floats are parsed in metadata import as they may depend on the language. If in doubt use InvariantList of LangauagesInvariant
Uploaders user idThis controls which user the import should upload as.Int10000
Combo separatorThis controls which separator is used to separate multi values like combo values.String;
Combo match styleDetermines if the combo is matched on textual value (which is different between languages) or option value (which is the non-language unique identifier).

Enum

  • TextValue
  • OptionValue
TextValue
Match search nameThis configures which API endpoint to use for duplicate detection. This is mainly used to switch between filename matching or assetid matchingList of searchesDamImporterMatchSearch
Match token fallback typeThe default match token is what is configured in File name stamp type, however, this can be used as fallback

Enum:

  • FileNameOnly
  • FileNameNoExtension
  • RelativePath
  • AbsolutePath
Relative path
Metadata import typeThis configures what the input for the metadata should be. Do not import implicitly disabled metadata import for the import configuration (i.e. asset upload only).Enum:
  • Import from sheets
  • Import from xml
  • Do not import
Import from sheets
Sheet typeIf Import from sheets is configured, then this controls the type of the sheet

Enum

  • Excel
  • CSV
Excel
Sheet directoryThe directory in which the sheet is uploaded. Similar to Upload directoryStringNone
MetafieldIdRowWhich row in the sheet holds the metadata configuration (metafield IDs).Integer (
1
0-based index)None
When RunMetadata and RunUpload are both true and input type is any of the sheet types.
DataStartRowWhich row in the sheet does data start. This allows the sheet to contain 1 or more rows in the beginning which are ignored by the Importer.Integer (
1MatchSearchName

When set a search will be executed the purpose of which varies with configuration:

  • RunUpload is true: The search result will be used to determine if an asset must be replaced.
  • RunMetadata is true and RunUpload is false: The search result is used to determine the asset to be metadata updated.
String matching a valid DAM search.None but "DamImporterMatchSearch" comes with the importerAlways if set.
0-based index)None
When RunMetadata and RunUpload are both true and input type is any of the sheet types.
MatchTokenColumnWhich column in the sheet holds the token to use as input for MatchSearchNameInteger (
1MatchTokenTag
0-based index)None
When MatchSearchName is set and MetadataParser is any of the sheet types. Optional.
FileNameColumnWhich
tag
column in the
xml holds the token to use as input for MatchSearchNameStringNoneWhen MatchSearchName is set and MetadataParser is Xml2Metadata. Optional.MatchTokenFallbackTypeWhen MatchTokenColumn / MatchTokenTag are either not set or the value is empty a fallback is made to the filename of the uploaded asset (and thus is only possible when RunUpload is true).

Enum:

  • FileNameOnly
  • FileNameNoExtension (5.2.1+)
  • RelativePath
  • AbsolutePath
RelativePathWhen RunUpload is true, MatchSearchName is set and MatchTokenColumn / MatchTokenTag are unset or the value thereof is empty. Optional unless the default differs from what is needed.MatchBatchSizeHow many match tokens are queried at a time.Integer between 1 and 10010Only in effect when RunUpload is false and RunMetadata is true as in an upload scenario tokens are always quesried one at a time. This setting was introduced in DAM 5.1.1.ArchiveOnReplaceWhether to overwrite (false) or archive (true) an asset when replacing.BooleanFalseWhen RunUpload is true, MatchSearchName  is set. Optional unless the default differs from what is needed.

...

sheet holds the filename of the file to upload.Integer (0-based index)None