Workflow Metadata File for Intranet Portal Data Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing enterprise information portal systems face inefficiencies in restoring individual data objects and workflows from archived database files, as the reinstallation of large monolithic databases is time-consuming and inefficient, especially when only a small number of items or lists need to be restored, and workflows are not easily distinguished from other items or lists.

Innovation Solution

A method that involves receiving a request to restore a workflow from an archived database file, retrieving workflow attributes, generating a workflow metadata file with tagged elements, and storing it in a file system to restore the workflow to the intranet portal application, allowing for the restoration of individual data objects and workflows without reinstalling the database system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single monolithic database file is reinstalled to restore data objects, then all data can be recovered, but the restoration process becomes time-consuming and inefficient when only a small number of items need to be restored

Engineering Contradiction:
Improvedata recovery completenessVSAvoidrestoration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the monolithic database file into individual data objects and workflows. Instead of reinstalling the entire database, the system extracts and restores only the specific data objects and workflows needed, dividing the large database into manageable, restoreable units that can be selectively recovered without time loss.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts workflow information and data objects from the archived monolithic database file. By taking out only the necessary workflow attributes and associated data objects, the system enables restoration without reinstalling the entire database, thus reducing restoration time while maintaining data recovery reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

2Loss of information

If workflow information is stored in records within the database, then workflow data is preserved, but workflows become difficult to distinguish from other items or lists

Engineering Contradiction:
Improveworkflow information preservationVSAvoidworkflow identification
Core Design Contradiction:
Loss of informationVSDifficulty of detecting and measuring

Solution Approach 1:

The patent applies local quality by creating a dedicated workflow metadata file with tagged elements that specifically represent workflow attributes. This separate metadata structure allows workflow information to be clearly identified and distinguished from other database records, making workflow detection and measurement straightforward while preserving complete workflow information.

Inventive Principle:
Principle #3Local quality

3Reliability

If the entire database system is reinstalled to restore items, then all data structures are restored, but the process is inefficient when only individual items or lists need to be restored

Engineering Contradiction:
Improvedata structure integrityVSAvoidrestoration efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the database restoration process into individual data object restoration operations. Instead of reinstalling the entire database system, the system restores only the specific data objects and workflows needed, maintaining data structure integrity for restored items while significantly improving restoration efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a workflow metadata file that copies essential workflow attributes from the archived database. This metadata copy contains tagged elements representing workflow conditions and actions, enabling efficient restoration of workflow functionality without copying the entire database system structure.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8818961B1User restoration of workflow objects and elements from an archived database
Publication Date: 2014.08.26 COHESITY INC
  • US8818961B1 patent drawing
  • US8818961B1 patent drawing
  • US8818961B1 patent drawing

AI summary

A system and method for restoring data including a workflow from an archived copy of a database file. The method includes receiving a request to restore a workflow from an archived copy. The workflow comprises attributes describing a sequence of conditions and actions corresponding to an item and comprises a history log. The item may comprise an electronic document and associated context information describing the document in an intranet portal application environment. The associated context information includes an identifier corresponding to the workflow. The method includes retrieving records comprising the workflow attributes from the archived copy. The method further includes generating from the retrieved records a workflow metadata file comprising tagged elements corresponding to the workflow attributes and history log. Then the method stores the workflow metadata file in a file system. The method further includes restoring the workflow to the intranet portal application via the file system.