CMIS Import Map - Auto Map

Automatically maps Grooper fields to CMIS properties using name similarity and type compatibility.

Remarks

The AutoMap command provides a rapid way to generate initial import mappings between Grooper fields and CMIS properties for a CMIS Import Map. This command analyzes the available Grooper fields and CMIS properties, then attempts to match them based on name similarity (using Levenshtein distance) and compatible data types.

When to Use

• When setting up a new CMIS Import Map and you want to quickly establish baseline mappings.
• To reduce manual effort and ensure consistent, repeatable mapping logic across similar import scenarios.
• During solution prototyping or when working with large or complex content types.

How It Works

• For each writable Grooper field that is not already mapped, the command searches for the closest matching CMIS property.
• Name similarity is determined using Levenshtein distance, and only matches within a configurable threshold are considered.
• Type compatibility is checked to ensure that the CMIS property can be safely imported into the Grooper field.
• Only unmapped fields are affected; existing mappings are preserved.

Limitations & Best Practices

• Not all fields may be mapped automatically, especially if property names differ significantly or types are incompatible.
• Always review and adjust the generated mappings to ensure they meet your business and import requirements.
• Use AutoMap as a starting point, then refine expressions and handle special cases as needed.

Example Scenario

• You have a Content Type with fields "InvoiceNumber", "InvoiceDate", and "TotalAmount", and a CMIS content type with properties "Invoice_Number", "Invoice_Date", and "Total_Amount".
• Running AutoMap will automatically link these fields to their corresponding CMIS properties, saving time and reducing errors.

See Also

CMIS Import Map