Hash-Based Duplicate File Identification for CMS Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content management systems face inefficiencies in identifying and managing duplicate files across multiple repositories, leading to excessive storage costs, resource utilization, and prolonged search and retrieval times due to the lack of effective duplicate detection and primary duplicate identification.

Innovation Solution

A system utilizing a hash-based approach to identify and tag duplicate files, with the ability to designate a primary duplicate based on various criteria, and implement links to reduce storage redundancy and enhance migration efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If files are stored across multiple repositories without duplicate detection, then file accessibility and storage flexibility are improved, but storage space consumption increases and resource utilization worsens

Engineering Contradiction:
Improvefile accessibilityVSAvoidstorage space consumption
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system performs preliminary hash calculation and duplicate detection before file migration to the content management system. By computing hashes of files during the migration process and comparing them against existing files in the destination repository, the system identifies duplicates upfront and excludes them from migration, preventing wasted storage space on redundant files.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the content management system provides information about existing files and their hashes back to the migration process. This feedback allows the system to intelligently determine which files need to be migrated and which are duplicates, optimizing storage space utilization while maintaining file accessibility.

Inventive Principle:
Principle #23Feedback

2Reliability

If all duplicate files are migrated to the new repository, then complete data migration is achieved, but migration time and processing resources increase

Engineering Contradiction:
Improvedata migration completenessVSAvoidmigration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary hash calculation and duplicate identification during the migration process itself. By computing hashes of source files and comparing them against the destination repository's file hashes before actual migration occurs, the system identifies duplicates in advance and excludes them from the migration process, significantly reducing migration time while ensuring complete data migration for non-duplicate files.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system extracts and separates duplicate files from the migration process. By identifying duplicates through hash comparison and excluding them from migration, the system takes only the necessary non-duplicate files for migration, reducing processing time and resources while maintaining data completeness through proper linking to existing duplicates in the destination repository.

Inventive Principle:
Principle #2Taking out (Extraction)

3Device complexity

If duplicate files are not identified, then simple file storage is maintained, but search and retrieval operations become slower due to processing redundant files

Engineering Contradiction:
Improvestorage system simplicityVSAvoidsearch and retrieval speed
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The system performs preliminary hash calculation for all files during migration and stores these hashes in the content management system's metadata. This preliminary action enables fast duplicate detection and identification during subsequent search and retrieval operations, as the system can quickly compare hashes rather than processing all file contents, significantly improving search and retrieval speed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces hash values as an intermediary mechanism between files and search operations. Hash values serve as mediators that enable efficient comparison and identification of duplicates without requiring processing of actual file contents during search operations, thus improving productivity while maintaining relatively simple storage architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Measurement precision

If manual identification of primary duplicates is performed, then accuracy can be controlled, but processing time and labor requirements increase

Engineering Contradiction:
Improveprimary duplicate identification accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs self-service duplicate identification through automated hash-based comparison. By automatically calculating hashes of all files, comparing them against existing files in the destination repository, and identifying duplicates without human intervention, the system achieves both speed and accuracy in primary duplicate identification, eliminating manual processing time and labor requirements.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12561287B2Duplicate file management for content management systems and for migration to such systems
Publication Date: 2026.02.24 SHINYDOCS
  • US12561287B2 patent drawing
  • US12561287B2 patent drawing
  • US12561287B2 patent drawing

AI summary

In large installations of document management systems, files are often duplicated. Users may place their own copies of files in convenient locations, or for other reasons files may be unintentionally duplicated. Duplication of files causes many problems for systems reliant on document management, chiefly because the additional (identical) files accept extra storage space, and must be handled like all other files, which results in greater network and resource utilization (with a concomitant increase in processing, search and retrieval times). A tool to standardize the identification of duplicate files (based on their binary contents), as well as the identification of a primary duplicate (the original file) across multiple repositories in a manner that minimizes the time for identification is disclosed.