GeoTag Conflict Management During Project Import
Conflict Resolution During Project Import
When importing a project that contains GeoTags and their categories, Cyclone REGISTER 360 PLUS compares the imported data with the existing data in the current project.
If differences or potential conflicts are detected, the system automatically applies a set of conflict‑resolution rules to maintain consistent, non‑duplicated data.
Below are the conflict types supported by the system and the logic applied to resolve them.
Categories with the Same ID but Different Names
Issue: The same category (same UID) has a different name in the imported project than in the existing project.
Resolution: The system keeps the version with the latest modification time. The older name is replaced.
Also applies to:
List type categories
List type category values
Free text categories
List Type Categories with Different Value Sets
Issue: A category defined as a list contains different sets of values in both projects.
Resolution: The system merges all unique values into a combined list. If a value exists in both lists but has different UIDs, the value with the latest modification time is kept.
Category Value Priority Conflicts
Issue: The same values exist, but their priorities differ between the current and imported projects.
Resolution: Cyclone REGISTER 360 PLUS keeps the priority order from the most recently modified version.
Overlapping Priorities Between Different Values
Issue: Two different category values share the same priority (for example, both set to Priority 1).
Resolution: The latest modified value keeps the priority. The older value is given a new priority to remove duplication.
Categories with Different IDs but the Same Name
Issue: Two categories have different UIDs but the same name, leading to ambiguity.
Resolution: The system keeps only one category and merges data based on modification time. The imported category is adjusted or merged to prevent duplication.
Also applies to:
List type categories
List type category values
Free text categories
Name Conflict Between a Category and a Field
Issue: A category and a field (Free Text) share the same name.
Resolution: The imported field is automatically renamed by appending - Copy. This ensures all names remain unique. If two fields have the same name, the imported one also receives the - Copy suffix.
Summary of Conflict Resolution Rules
Conflict Type | Applied Rule |
|---|---|
Same category ID, different names | Keep the latest modified category |
Different list values | Merge values; resolve duplicates by modification time |
Priority conflicts | Keep the latest priority ordering |
Overlapping priorities | Keep the priority for the latest modified value; the older one gets reassigned |
Same name, different IDs | Keep one; merge or rename imported |
Category name equals field name | Rename the field by adding the - Copy suffix |