New

Detecting duplicated objects before importing objects with Content Importer

We need a feature in Content Importer that confirms whether to overwrite existing objects when duplicate objects—those with the same GUID, version, or language—are found in the repository.

The usage scenario of Content Importer in our company is as follows:

We mainly use the Content Importer to import image objects. Multiple staff members from different organizations collaborate to edit a single manual. A unique image management number is assigned by our proprietary system, and this number is used as the GUID for each image object. As an operational rule, image management numbers must be assigned before importing images to prevent unintended overwriting. Of course, image objects need to be overwritten when corrections or engineering changes occur.

The issue we face is that image objects are sometimes overwritten accidentally when someone imports images without assigning image management numbers, or when they mistakenly import images using existing numbers. If Content Importer could detect duplicate objects and request confirmation before overwriting them, we could prevent these accidental overwrites. It would be even more convenient if Content Importer could list the GUIDs and object names of all duplicated objects.

Currently, however, we rely on a proprietary tool built with ISHRemote to verify the existence of duplicate objects. This requires us to maintain the tool with every Tridion Docs version upgrade and results in cumbersome operations.