Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Introduction

To be added

Nodes to be merged

Nodes to be merged are coloured as below.

image-20250413-023042.png

Merge process

These are the steps in the merge process.

  • Defining merge source and target: When a mindmap node is dragged onto a node of the same type, the node being dragged is the source and node being dragged onto is the target.

  • Review merge suggestions: The suggested changes to add or remove content will be highlighted. These are based on the merge type and merge weighting. See Merge Types and Merge Weighting below for more details.

  • Manual edits: While its possible to use Orthogramic’s suggestions for the merge, manual edits are highlighted as you make them.

image-20250413-023846.png

  • Confirming the merge: After you select Merge at the bottom of the Insights Panel, you will be required to confirm your merge.

Merge confirmations (2).png

Merge types

When merging a document in Orthogramic, a merge type is automatically selected from three types of merges below based on how the new information should best integrate with existing business architecture domain data. Each merge type ensures that your organization maintains a structured and strategic approach to managing its domain data.

Merge type and description

Use case

Outcome

Additive: This integrates the new document’s data alongside existing domain data without removing or replacing any content. This approach is ideal when the new information provides additional insights or expands on existing knowledge without creating conflicts.

  • When the document contains complementary information that enhances an existing domain without requiring changes to previous data.

  • When multiple perspectives or data sources should be retained for future reference.

The merged document contributes to the domain while keeping all prior data intact.

Overwrite: This merge replaces outdated or redundant domain data with higher-priority content from the new document. This approach is useful when the new document provides more accurate, updated, or authoritative information than what currently exists.

  • When the document contains the latest policy, strategy, or regulatory update that must replace outdated versions.

  • When previous data is no longer relevant or has been superseded by new business decisions.

Older data is removed and replaced by the new document’s content.

Update: This merge selectively integrates new data while preserving historical context where relevant. This approach balances maintaining past records while incorporating necessary updates.

  • When parts of the document contain updates that should be merged with existing data without completely removing prior versions.

  • When historical context is important for tracking changes over time, but certain aspects of the domain require modification.

The merged content reflects updated information while keeping historical dependencies intact.

Merge weighting

The weighting of the source documents the domain data in each node determines the relative importance of attributes and elements when the merge occurs. The history of previous merges is also tracked at the attribute and element level. For example, an overwrite is more likely when merging a highly weighted Source with a lower weighted Target. See https://orthogramic.atlassian.net/wiki/spaces/OUG/pages/48267825/Document+weighting?atlOrigin=eyJpIjoiYmE3MGFhYmU0NjBmNDU5YmE4ZDBmMjVhZDliZGJjYTYiLCJwIjoiYyJ9

  • No labels

© Orthogramic 2024