ECM File Check-in via Embedded Location Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The check-in process in enterprise content management systems is cumbersome, requiring users to manually navigate file hierarchies and upload updated files, which is inefficient, especially when files are moved or shared among users.

Innovation Solution

Storing metadata identifying the file's location in the ECM content repository within the file itself during the check-out process, allowing the ECM system to automatically identify and update the file upon check-in, reducing the need for manual location specification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual check-in process is used where users navigate file hierarchies and upload files through web interface, then file location identification can be achieved, but the check-in process becomes time-consuming and inefficient

Engineering Contradiction:
Improvecheck-in process simplicityVSAvoidcheck-in time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system embeds metadata containing file location information into the file itself during the check-out process. This preliminary action ensures that when the user checks in the file (even from a different location or after moving it), the ECM system can automatically retrieve the original file location from the embedded metadata without requiring the user to manually navigate through file hierarchies or specify the location again.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If file tracker application is used to track checked-out document status, then finding document location is facilitated, but the system fails when user moves the document to another location

Engineering Contradiction:
Improvedocument location trackingVSAvoidcheck-in reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

Instead of relying on external tracking applications that monitor file locations, the system creates a self-contained copy of the essential location information by embedding metadata directly into the file itself. This ensures that the location information travels with the file regardless of where the user moves it, making the check-in process reliable even when the file is transferred to different locations or shared with other users.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If deep folder hierarchies are used for file organization, then file management capability is improved, but the check-in process requires more manual steps and navigation

Engineering Contradiction:
Improvefile organization capabilityVSAvoidcheck-in process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system extracts the essential location information from the complex folder hierarchy structure and embeds it as metadata within the file itself. This allows the ECM system to understand file locations without requiring users to navigate through deep folder hierarchies during check-in. The metadata contains sufficient information to identify the original file location, effectively removing the complexity of hierarchical navigation from the user's check-in process while preserving the organizational structure's adaptability.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10002135B2Simplifying the check-in of checked-out files in an ECM system
Publication Date: 2018.06.19 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10002135B2 patent drawing
  • US10002135B2 patent drawing
  • US10002135B2 patent drawing

AI summary

Techniques are disclosed for managing a file stored in an enterprise content management (ECM) repository. In response to a check-out request from a client machine for a file stored in the ECM repository, a management application for an ECM system identifies ECM-related metadata associated with the file. The management application stores the ECM-related metadata into the file (or an associated file) prior to sending the file to the client. At check-in for the file, the management application identifies the location of the corresponding file in the ECM repository using the metadata previously stored in the file sent to the client.