...

The standard search, delievered with the Importer app, goes by the name DamImporterMatchSearch and it is used as default way to perform matching logic. It is entirely up to the Importer user whether to use this search or their own as long as it conforms to a couple of rules as described here.

Rules for the MatchSearch

1. There must be a searchfield defined with the ID sFilename. The ID is case sensitive. This is the input field that will be used be the Importer.
2. The sFilename searchfield must have the valueHandler InList. The Importer searches for 50 searchtokens at a time so this is the only valueHandler that will work.
3. There must be a valuefield defined with the ID filename and it must reference the same metafield or table/column as sFilename.
4. The valuefield "assetId" must be present and refer to "asset.assetid" and the Id must be "assetId". It is case sensitive so if this is changed to ie. "assetid" nothing will ever be matched.

While not a rule for the search definition as such, it is also important to note the DAMs read access is in place so the user configured for the Importer must have read access to the assets needed for the Importer.

As long as these rules are followed any search definition can be used.

About the default DamImporterMatchSearch

The match search delivered with the Importer uses the assets Title to match. This does not meet all customers requirement in which case it is be necessary to either change the existing one or create a new search definition.

How to define a new search for use with the Importer

First navigate to the ConfigManager and the DAM node:

...