In 5.9 MatchSearch configuration was removed
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
A MatchSearch in the Import configuration is used to Match assets. It is used in two scenarios:
...
The standard search, delivered with the Importer app, goes by the name DamImporterMatchSearch and it is used as the 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
There must be a searchfield defined with the ID sFilename. The ID is case-sensitive. This is the input field the Importer will use.
The sFilename searchfield must have the valueHandler InList. The Importer searches for 50 search tokens at a time, so this is the only valueHandler that will work.
There must be a valuefield defined with the ID filename, and it must reference the same metafield or table/column as sFilename.
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, it is also important to note that the DAM's read access is still respected, so the user configured for the Importer must have read access to the assets needed.
Any search definition can be used as long as these rules are followed.
About the default DamImporterMatchSearch
The match search delivered with the Importer uses the asset's title metafield to match. This does not meet all customers' requirements, so for some, it is 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:
...