Versions Compared

Version Old Version 6 New Version 7
Changes made by

damian.hickey

damian.hickey

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
stylenone

Introduction

...

This will walk you through the complete process of merging document nodes in Orthogramic, from understanding different merge types and their appropriate applications. Whether you're consolidating complementary information, updating outdated content, or replacing redundant data, Orthogramic's intelligent merge functionality provides a structured approach to maintaining the integrity of your business domain data.

By following the straightforward merge process outlined in this guide, you'll be able to make informed decisions about how different pieces of information should interact, ensuring your organization maintains a cohesive and accurate knowledge base that evolves alongside your business needs.

Nodes to be merged

Nodes to be merged are coloured as below.

...

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.

...