Default Criteria for Handling File and Inventory Comparisons During the Import

The following information describes the default criteria used for handling file and inventory comparisons during an import. You can modify this criteria as needed by reconfiguring import options, as described in the next section, Available Import Options to Configure Import Behavior.

•

Only those files whose complete files paths match in both the import data file and the scanned target codebase can be associated with inventory in the target project. See Option for Creating New File Associations in Target Inventory for more information.

•

Only those files whose MD5s and complete paths match in both the import data file and the scanned target codebase are processed when marking files as reviewed in the target project. See Option for Marking Target Codebase Files as Reviewed for more information.

•

Only those inventory items in the import data file whose associated files match file paths in the target codebase are created in the target project (if these inventory items do not already exist in the target project). See Option to Create Empty Inventory for more information. (The import REST interface uses this behavior as the default; the Web UI might use different default behavior based on project settings.)

•

When an inventory item in the import data file is an exact match to an inventory item in the target project, any notes content defined for the inventory item in the import data file overwrites the notes content defined in the target inventory item. See Options for Handling Inventory Notes and Custom Fields for more information.

The default import logic is configurable, as described in the next section.