US20070260619A1 - Enterprise content management network-attached system - Google Patents
Enterprise content management network-attached system Download PDFInfo
- Publication number
- US20070260619A1 US20070260619A1 US11/741,688 US74168807A US2007260619A1 US 20070260619 A1 US20070260619 A1 US 20070260619A1 US 74168807 A US74168807 A US 74168807A US 2007260619 A1 US2007260619 A1 US 2007260619A1
- Authority
- US
- United States
- Prior art keywords
- content
- data
- business process
- management
- storage
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1456—Hardware arrangements for backup
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/289—Object oriented databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1474—Saving, restoring, recovering or retrying in transactions
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/953—Organization of data
- Y10S707/959—Network
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99933—Query processing, i.e. searching
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99953—Recoverability
Definitions
- the present invention relates generally to enterprise content management systems, and, more particularly, to enterprise content management network-attached systems.
- NAS Network Attached Storage
- SAN Storage Area Networks
- Metadata is “data about data”—i.e., data or information about a particular item of data.
- metadata about a document file may be the author, creation time and date, last modified time and date, keywords describing the content of the documents, the file type, the application associated with the file, and access privileges for various users.
- Content management systems create and manage metadata for each item of data or information entered into the system and maintain a database or repository that contains the metadata. Thus, with a content management system users can locate desired information by searching for relevant attributes or keywords in the metadata database. Utilization of metadata also allows organizing, sorting, and selectively presenting data items based on relevant attributes stored in the associated metadata.
- Metadata can be used, however, for much more than organizing, searching, and retrieving information. Since metadata are just another type of data, any information about the content data can be stored in the associated metadata. Stated generally, metadata can contain “intelligence” about the associated item of data. This intelligence can include: applications associated with the data, what operation can be performed on the data, the history of processing on the data, and what processing should be performed next on the data. Thus, metadata can be used to encode the entire life-cycle specifications for the associated content data. Based on such technologies, the capabilities of content management systems can be extended beyond organization and retrieval of information to management of business processes performed on the documents, information, or data. Systems with such capabilities are called Business Process Management (BPM) or Work Flow Management (WFM) systems. The metadata in this context are also called business process data. At present, vendors such as FileNet, IBM, Documentum, and Vignette provide various content management and/or business process management products or services.
- BPM Business Process Management
- WFM Work Flow Management
- fixed content systems One particular area where the content management systems are heavily relied on is so-called “fixed content” systems.
- enterprises are required to maintain data or records that cannot be modified due to the nature of business or government regulatory requirements. Examples include medical records and diagnostic medical images (such as X-ray and MRI images) for healthcare and insurance industry, accounting records and corporate documents for corporations, and security transaction records for brokerage firms or investment banks.
- medical records and diagnostic medical images such as X-ray and MRI images
- accounting records and corporate documents for corporations
- security transaction records for brokerage firms or investment banks.
- X-ray and MRI images For hospitals and healthcare providers, it is important to maintain X-ray and MRI images that cannot be modified due to concerns about accurate diagnosis and keeping accurate medical histories.
- Various government regulations such as Sarbanes-Oxley, HIPAA (Health Insurance Portability and Accountability Act), and SEC Rule 17a-4 require corporations, insurance companies, and securities brokers to maintain records that are guaranteed against modification for an extended period of time.
- an enterprise content management system typically comprises several separate component systems: namely, content server cluster ( 110 ), content data storage ( 112 ), content metadata server cluster ( 120 ), content metadata storage ( 122 ), business process server cluster ( 130 ), and business process data storage ( 132 ).
- An enterprise content management system is typically deployed in a local area network ( 140 ) environment, and accessed from workstations ( 150 ) or personal computers ( 160 ).
- these component systems are usually provided by different vendors, and are installed, maintained, and operated separately.
- the applications or software that provide the content management and business process management functions operate as distinct components separate from the storage systems.
- Content bridges such as VeniceBridge from Venetica
- Content bridges provide tools to integrate disparate systems by mapping and translating dissimilar logical units, data dictionaries, metaphors, and taxonomy into a single, consistent framework.
- content bridges provide useful tools that can improve the quality of system integration, several problems remain. The first is that some inconsistencies across disparate systems simply cannot be resolved. The second, and a more serious problem is that content bridges do not and cannot address the issues of replication and disaster recovery, since content bridges focus only on the conceptual problems of integrating dissimilar semantics of disparate systems.
- replication and disaster recovery must be done separately for each component system.
- existing products and technologies do not provide mechanisms to synchronize replication and recovery with external systems. Thus, currently, system-wide synchronization must be performed manually, and, when the replication and recovery transactions become “out of sync”, the transactions must be reconciled through a manual process. These are difficult and frustrating processes that are also error-prone.
- the present invention addresses the foregoing need by providing an integrated enterprise content management network-attached system that affords a native, unified approach to the entire range of enterprise content management functions from storage management to content and business process management.
- the present invention is an enterprise content management network-attached system, where a storage system is provided with integral, native content management and business process management functions.
- the present invention is an enterprise content management network-attached system with native integration of a content management system, a business process system, and a storage system, comprising: a storage system for storing content data, content metadata, business process data, and computer executable process steps for content management and business process management, wherein the computer executable process steps for content management and business process management include: (1) steps for accessing the content data, the content metadata, and business process data, and (2) steps for processing the content data in accordance with information contained in the content metadata and business process data.
- the present invention also encompasses a native, unified replication system which automatically synchronizes replication of the content data, the content metadata, and the business process data.
- the present invention is a method of providing services in an enterprise content management network-attached system, where the content management and business process management functions are provided as an integral, native extension of a storage system.
- the present invention is a method of providing services in an enterprise content management network-attached system with native integration of a content management system, a business process system, and a storage system, comprising the steps of: (1) providing a storage system for storing content data, content metadata, business process data, and computer executable process steps for content management and business process management; and (2) providing computer executable process steps for content management and business process management including: (i) steps for accessing the content data, the content metadata, and business process data, and (ii) steps for processing the content data in accordance with information contained in the content metadata and business process data.
- the present invention also encompasses a method for providing a native, unified replication system which automatically synchronizes replication of the content data, the content metadata database, and the business process database.
- FIG. 1 illustrates a network environment in which an enterprise content management system is deployed
- FIG. 2 illustrates Enterprise Content Management Network-Attached System deployed in a network environment according to the present invention
- FIG. 3 illustrates the software and hardware components of Enterprise Content Management Network-Attached System according to the present invention
- FIG. 4 illustrates the architecture of the content management subsystem according to the present invention
- FIG. 5 illustrates the architecture of the business process management subsystem according to the present invention
- FIG. 6 illustrates an example of content management according to the present invention
- FIG. 7 illustrates the high-availability and disaster recovery configurations of the existing content management and business process management systems.
- FIG. 8 illustrates the integrated high-availability and disaster recovery configurations according to the present invention.
- the present invention provides an integrated enterprise content management network-attached system, where a storage system is provided with native, integral content management and business process management functions.
- the present invention is an enterprise content management network-attached system with native integration of a content management system, a business process system, and a storage system, comprising: a storage system for storing content data, content metadata, business process data, and computer executable process steps for content management and business process management, wherein the computer executable process steps for content management and business process management include: (1) steps for accessing the content data, the content metadata, and business process data, and (2) steps for processing the content data in accordance with information contained in the content metadata and business process data.
- such enterprise content management system with native integration of a content management system, an optional business process system, and a storage system is defined as Enterprise Content Management Network-Attached System.
- FIG. 2 illustrates Enterprise Content Management Network-Attached System deployed in a network environment according to the present invention.
- Enterprise Content Management Network-Attached System ( 210 ) is an integrated solution that provides the native, unified content data storage, content metadata storage, and business process data storage functions in “a single box”.
- Enterprise Content Management Network-Attached System ( 210 ) is deployed by simply rolling in the “single box” and connecting it to the network ( 140 ) with network connection ( 212 ).
- the content management and business management functions are provided as the integral part of Enterprise Content Management Network-Attached System ( 210 ), not as separate application packages installed and operated separately from the storage system.
- FIG. 3 illustrates the software and hardware components of Enterprise Content Management Network-Attached System according to the present invention.
- Content Management Subsystem ( 310 ) Content Management Subsystem ( 310 ), Business Process Management Subsystem ( 320 ), Storage System ( 330 ), Computing Hardware ( 340 ), and Network Interface Hardware ( 350 ) are integral part of Enterprise Content Management Network-Attached System ( 210 ) which appears as a single system to operators or end-users.
- the native, unified, and integrated system of the present invention eliminates the problems related to installation, configuration, and upgrade of disparate enterprise system components.
- the native, unified approach of the present invention also eliminates or greatly reduces the problems due to inconsistent and/or incompatible semantics across disparate systems from different vendors.
- the present invention also improves the overall performance of the enterprise system by providing tight integration without unnecessary interfaces or translation layers between various components of the system. The result is a more robust, reliable, and efficient enterprise content management system that is easier to deploy, configure, maintain, operate, and use.
- Storage System ( 330 ) can be any storage system known to those skilled in the art, including RAID disk farm, Network Attached Storage (NAS) system, and Storage Area Networks (SAN) system, without departing from the scope of the present invention.
- NAS Network Attached Storage
- SAN Storage Area Networks
- Storage System ( 330 ) can also include a content-addressable storage (CAS) system such as the EMC CenteraTM system.
- CAS content-addressable storage
- Storage System ( 330 ) can include any fixed-content storage solutions known to those skilled in the art, including the Optical Storage and Retrieval systems such as the FileNet OSARTM system and magnetic fixed-content systems such as the EMC CenteraTM system, without departing from the scope of the present invention.
- Computing Hardware ( 340 ) comprises CPUs, memory units, and supporting computing circuits to provide an Enterprise Server class computing capability for Enterprise Content Management Network-Attached System ( 210 ).
- the CPU can be any high-performance CPU known to those skilled in the art, including an Intel CPU, a PowerPC CPU, a MIPS RISC CPU, a SPARC CPU, or a proprietary CPU, without departing from the scope of the present invention.
- Content Management Subsystem ( 310 ) and Business Process Management Subsystem ( 320 ) can communicate with each other over any interprocess communication (IPC) mechanism known to those skilled in the art, including pipes, sockets, messages, and RPC, as well as high level communication mechanisms such as SOAP (Simple Object Access Protocol).
- IPC interprocess communication
- Content Management Subsystem ( 310 ) and Business Process Management Subsystem ( 320 ) communicate with outside systems - for example, workstations ( 150 )—over Network API ( 360 ) software and Network Interface Hardware ( 350 ) connected to network ( 140 ) over network connection ( 212 ), utilizing proprietary or standards based communications protocols including IETF WebDAV (RFC 2518) and IETF DeltaV (RFC 3253).
- FIG. 4 illustrates the architecture of the content management subsystem according to the present invention.
- Content Management Subsystem ( 310 ) comprises Content Management Engine ( 410 ), Content Data ( 420 ), Content Data Database ( 422 ), Content Metadata ( 430 ), and Content Metadata Database ( 440 ).
- Content Data ( 420 ) are stored and accessed through Content Data Database ( 422 ) or File System ( 450 ) of Storage System ( 330 ), and Content Metadata ( 430 ) are stored and managed through Content Metadata Database ( 440 ) which is itself stored on Storage System ( 330 ) through File System ( 450 ).
- Content Management Engine ( 410 ) contains the software logic for providing content management functions.
- Content Management Engine ( 410 ) comprises computer executable process steps stored on Storage System ( 330 ) that access Content Data Database ( 422 ) and Content Metadata Database ( 440 ), and process Content Data ( 420 ) in accordance with Content Metadata ( 430 ) contained in Content Metadata Database ( 440 ).
- Content Management Engine ( 410 ) employs object-oriented (OO) technology.
- a Business Object is a representation of content data and associated content metadata.
- a Business Object is described by a class which specifies the object properties (attributes) and the methods (functions or operations).
- the metadata instances of Business Objects are stored in Content Metadata Database ( 440 ), while the content data for the Business Object instances are stored either in the Content Data Database ( 422 ) or File System ( 450 ).
- the benefit of object-oriented technology is ease of development, management, and use through abstraction, encapsulation, and inheritance.
- FIG. 6 illustrates an example of content management according to the present invention.
- a Business Object for a loan is represented by Loan Object ( 602 ), which is an instance of Loan Class ( 610 ).
- Loan Class ( 610 ) contains Loan ID Attribute ( 612 ), Loan Application Attribute ( 614 ), Loan Policy Attribute ( 616 ), and Customer Attribute ( 618 ).
- Loan Application Attribute ( 614 ) can either point to or contain Loan Application Object ( 620 ), which is an instance of Loan Application Class ( 622 ).
- Loan Application Class ( 622 ) in turn contains Loan Application Content Attribute ( 624 ) and Application Date Attribute ( 626 ).
- Loan Application Content Attribute ( 624 ) points to the content data,
- Loan Application File ( 630 ) which can be a scanned image file of a paper application or an electronic application file.
- loan Policy Attribute ( 616 ) can either point to or contain Loan Policy Object ( 640 ), which is an instance of Loan Application Class ( 642 ).
- Loan Policy Class ( 642 ) in turn contains Policy Content Attribute ( 644 ) and Policy Number Attribute ( 646 ).
- Policy Content Attribute ( 644 ) points to the content data, Policy Document File ( 650 ), which can be an electronic document file of any type or format, including a Word document and a Acrobat document.
- Customer Attribute ( 618 ) pointing to Customer Object ( 660 ), which is an instance of Customer Class ( 662 ).
- Content Management Subsystem ( 310 ) of the present inventions provides services to create, search, find, sort, and manage all documents and information related to a particular loan application. For example, an end-user can search for a loan application by a particular customer by the customer name. Once the search found the match in Content Metadata Database ( 440 ), Content Management Subsystem ( 310 ) automatically provides access to all related information and documents, including Loan Application File ( 630 ) and Policy Document File ( 650 ), by utilizing various related Business Objects illustrated above.
- Content Management Subsystem ( 310 ) retrieves Loan Application File ( 630 ) by: (1) accessing Loan Application Object ( 620 ) by looking up Loan Application Attribute ( 614 ) of Loan Object ( 602 ); and (2) accessing Loan Application File ( 630 ) by looking up Loan Application Content Attribute ( 624 ) of Loan Application Object ( 620 ).
- loan Application File ( 630 ) is accessed by the following chain of references: from Loan Object ( 602 ) to Loan Application Attribute ( 614 ), to Loan Application Object ( 620 ), to Loan Application Content Attribute ( 624 ), and to Loan Application File ( 630 ).
- Content Management Subsystem ( 310 ) retrieves Policy Document File ( 650 ) by a similar chain of references: from Loan Object ( 602 ), to Loan Policy Attribute ( 616 ), to Loan Policy Object ( 640 ), to Policy Content Attribute ( 644 ), and to Policy Document File ( 650 ).
- Content Metadata Database ( 440 ) can be any database known to those skilled in the art, including client-server relational databases, object-oriented databases, and object-relational databases, without departing from the scope of the present invention.
- Content Data ( 420 ), Content Data Database ( 422 ), Content Metadata ( 430 ), and Content Metadata Database ( 440 ) can also include full text indexing so that the entire content can be searched for text content.
- the content management functions can include: capability to reliably maintain arbitrary, user specifiable, relationships between two or more content or metadata objects (to represent a compound document, for instance); capability of versioning of one or more content or metadata objects; capability to search for objects based upon metadata and content attributes, including the capability to query utilizing the XQuery or SQL query methods; capability to specify security access requirements on one or more content or metadata objects; secure authorized and audited access to content and metadata objects; and container objects each of which may contain zero or more container, content, metadata, or other objects. Examples of container objects include containers that represent folders, projects, work cases, and taxonomies.
- the content management functions of the present invention can also include: capability to manually file content or metadata objects in one or more user creatable container; capability to automatically file content or metadata objects into one or more user or automatically creatable containers based on attributes of the object content or metadata or inferences of the object content or metadata; capability to store objects containing references to content stored outside of the storage system; capability to discover what metadata is required for adding new content or allowable on existing content; capability to dynamically update metadata or content without versioning or creating superfluous metadata or content objects; capability to raise events and subscription to those events by programs, scripts or other logic that users can provide to extend the behavior of the content storage system; capability to automatically change security on content or metadata objects based on time or some event; capability to provide reports about the utilization of content, metadata, and other objects including information about the eligibility of objects for replication; capability to import or export some or all of the content, metadata, or other objects stored within a content management system; and capability to pre-configure content management software and storage system capabilities so as to reduce cost of installation and minimize installation and configuration related errors.
- FIG. 5 illustrates the architecture of the business process management subsystem according to the present invention.
- Business Process Management Subsystem ( 320 ) comprises Business Process Management Engine ( 510 ), Business Process Data ( 520 ), and Business Process Data Database ( 530 ).
- Business Process Data ( 520 ) are stored and managed through Business Process Database ( 530 ) which is stored on Storage System ( 330 ) through File System ( 450 ).
- Business Process Management Engine ( 510 ) contains the software logic for providing business process management functions.
- Business Process Management Engine ( 510 ) comprises computer executable process steps stored on Storage System ( 330 ) that access Business Process Data ( 520 ) stored in Business Process Data Database ( 530 ), and process Content Data ( 420 ) and/or Business Process Data ( 520 ) in accordance with Business Process Data ( 520 ) contained in Business Process Data Database ( 530 ).
- Business Process Data Database ( 530 ) can be any network-deployable database known to those skilled in the art, including client-server relational databases, object-oriented databases, and object-relational databases, without departing from the scope of the present invention.
- Enterprise Content Management Network-Attached System ( 210 ) Upon receiving a service request from workstation ( 150 ) or personal computer ( 160 ), Enterprise Content Management Network-Attached System ( 210 ) of the present invention: 1) executes computer executable process codes that comprise Content Management Engine ( 410 ) or Business Process Management Engine ( 510 ) from Enterprise Content Management Network-Attached System ( 210 ); 2) accesses Content Data ( 420 ), Content Metadata Database ( 440 ), and Business Process Data Database ( 530 ); and 3) processes Content Data ( 420 ) in accordance with Content Metadata ( 430 ) contained in Content Metadata Database ( 440 ) and Business Process Data ( 520 ) contained in Business Process Data Database ( 530 ). The results of the processing are notified to or delivered to the requesting client workstation ( 150 ) or personal computer ( 160 ).
- the Enterprise Content Management Network-Attached System of the present invention can be configured with high-availability components and capabilities—that is, with redundant components including the power supply, processor, memory, storage, and network interface controllers, controlled by a single, native high-availability (HA) software implementation that will switch to the backup components if the primary components fail.
- HA high-availability
- the Enterprise Content Management Network-Attached System of the present invention can include: capability to create, update, search, and delete content as part of a transaction initiated by the content management software so as to provide a system that is reliable and robust in the event of component system failures; and capability to create, update, search, and delete content and content metadata and user-definable business process as part of a transaction initiated by the calling application so as to implement a system that is reliable and robust in the event of component failures.
- mission-critical enterprise systems For mission-critical enterprise systems, it is not enough to provide high-availability capability for each of the system components. The entire system could become non-operational or go off-line due to operator error, massive system-wide failures, or natural disasters. Consequently, mission-critical enterprise systems are usually backed up by disaster recovery systems at an off-site facility away from the operation or production deployment site.
- disaster recovery systems a key issue is consistent and reliable replication of relevant data from the operation site (called production site) to disaster recovery site, since the disaster recovery site must contain a current or nearly current set of data for the backup system to be effective.
- production site the operation site
- the disaster recovery site must contain a current or nearly current set of data for the backup system to be effective.
- providing consistent and reliable replication is a difficult and error-prone process.
- FIG. 7 illustrates the high-availability and disaster recovery configurations of typical existing content management and business process management systems.
- content, content metadata, and business process data are replicated separately by different products through disparate processes.
- Content data are replicated from Content Server Cluster ( 110 ) and Content Data Storage ( 112 ) to Content Backup ( 710 ) via replication product A
- content metadata from Content Metadata Server Cluster ( 120 ) and Content Metadata Storage ( 122 ) to Content Metadata Backup ( 720 ) via replication product B
- business process data from Business Process Server Cluster ( 130 ) and Business Process Data Storage ( 132 ) to Business Process Data Backup ( 730 ) via replication product C.
- content, content metadata, and business process data are replicated separately by different mechanisms on different schedules, the replication process can leave the recovery system with inconsistent data.
- Content data items may be there but their metadata are not, or business process data may include references to content item or metadata values that are not yet replicated to the recovery site.
- FIG. 8 illustrates the integrated high-availability and disaster recovery configurations according to the present invention.
- Enterprise Content Management Network-Attached System ( 210 ) is replicated as a single system to Enterprise Content Management Network-Attached System Backup ( 810 ), utilizing a single, unified, native replication facility of the system, providing consistent and logically ordered replication of content, content metadata, and business process data.
- Content Data ( 420 ), Content Metadata ( 430 ), Content Metadata Database ( 440 ), Business Process Data ( 520 ), Business Process Data Database ( 530 ), and File System ( 450 ) of Storage System ( 330 ) are all integral part of Enterprise Content Management Network-Attached System ( 210 ), a single, unified, native replication facility can replicate the entire content of the system more efficiently using a single consistent mechanism, eliminating the need to coordinate replication and synchronize replicated content.
- the single, unified, native replication facility of the present invention can guarantee zero-loss replication across all levels of replication, including the disk I/O level, the file system level, and the transaction level.
- the replication facility of the present invention can guarantee zero-loss replication by not returning from the replication operation—that is, performing a synchronous replication operation—until the disk sector or sectors being replicated has been committed to the recovery site.
- the file system level zero-loss replication is guaranteed by not returning from the replication operation until the entire file has been committed to the recovery site.
- zero-loss replication is guaranteed by committing the transaction at both production and recovery sites—i.e., completing the transaction guarantees that the entire set of files comprising the transaction have been committed to both the production site and the recovery site.
- replication can take place continuously (or in “real-time” ) as the disk sectors, files, or set of files are modified and updated.
- the production system is transparently mirrored to the recovery site in “real-time” with zero-loss guaranteed across all levels of replication, including the disk I/O level, the file system level, and the transaction level.
- Replication operation can also be scheduled to run automatically at a pre-determined time when the impact of backup operation on the overall system performance is minimal. Alternatively, replication can be initiated manually at any given time.
- ECM Network-Attached System keeps a logically ordered record of the data changes since the last replication.
- This record represents the delta between the data as of the last replication and the current state. It could be organized by data change operations at the storage level, the file system level, the transaction level, or any other level that allows tracking the logical order of operations and replicating that order at the recovery site.
- only the difference delta data are replicated to save replication time and reduce impact on the overall system.
- the entire data set can be replicated, although this is usually done only during the initial (or the very first) system replication.
- the data are read from Storage System ( 330 ) in the recorded logical order and transmitted in that same logical order to Enterprise Content Management Network-Attached System Backup ( 810 ) over a network connection.
- Storage System 330
- Content Metadata 430
- Content Metadata Database 440
- Business Process Data 520
- Business Process Data Database 530
- system administrators only need to learn and administer a single technology for replication and a single implementation for high availability. This reduces the likelihood of operator errors that would lead to downtime or failure of the recovery system in a disaster.
- TCO total cost of ownership
Abstract
Techniques describe providing services in an enterprise content management network-attached system, where the enterprise content management functions are provided as an integral part of a storage system. An integrated enterprise content management network-attached system provides a single, unified approach to the entire range of enterprise content management functions from storage management to content and business process management. The result is a robust and reliable complete enterprise content management solution with a lower total cost of ownership than existing products.
Description
- This application is a continuation application of and claims the benefit of “ENTERPRISE CONTENT MANAGEMENT NETWORK ATTACHED SYSTEM”, having application Ser. No. 10/834,100, filed Apr. 29, 2004, the disclosure of which is incorporated herein by reference in its entirety.
- 1. Field of the Invention
- The present invention relates generally to enterprise content management systems, and, more particularly, to enterprise content management network-attached systems.
- 2. Description of the Related Art
- Managing electronic files and data is a fact of life for modern business operations. Businesses are becoming increasingly dependent on various electronic content creation and communication tools—such as the word processors, web applications, emails, image and video applications, and various databases, just to name a few—to conduct their business operations.
- One consequence of this growing dependence on electronic information and communication tools is wildly proliferating digital data. It is not uncommon these days to find several billion bytes (gigabytes) of data on home computers used for personal purposes. In the business world, having several trillion bytes (terabytes) of data is not unusual, and some of the largest enterprises maintain more than petabytes (million billion bytes) of data on a regular basis. Thus, there exist needs among modern enterprises for systems which can store and manage very large amounts of data. At present, such needs are met by various interconnected storage systems such as the Network Attached Storage (NAS) and Storage Area Networks (SAN). The NAS systems are storage systems connected over existing computer network technologies such as the Ethernet or IP networks. The SAN (Storage Area Networks) systems connect storage systems over dedicated Fiber Channel network connections. Currently, vendors such as EMC and Network Appliance offer various NAS and SAN solutions.
- However, being able to store a very large amount of data creates yet another type of problem, as the large quantity of data by its very nature gives rise to the proverbial “needle in the haystack” problem. As the size of the data in the storage grows, the task of finding and retrieving the exact data and information needed for a particular purpose becomes more and more challenging. It is often said that the success of modern enterprises depends on finding the right information for the right person at the right time.
- The problem of finding “a needle in the haystack” is compounded by the existence of dissimilar data types which are managed by different applications with different access and/or search methodologies. Some files are managed through conventional file systems, emails are organized and accessed with email applications, and various databases are managed with their own database application programs. Thus, with conventional tools, it is often necessary to search several places with different applications in order to find the right set of information for a given task. In addition, access privilege and security mechanisms are typically quite different across the various content management tools. These problems make the task of “finding the right information for the right person at the right time” difficult for modern enterprises.
- In order to address these problems, various Enterprise Content Management (ECM) systems have been introduced. A key component of any content management system is metadata. Metadata is “data about data”—i.e., data or information about a particular item of data. For example, metadata about a document file may be the author, creation time and date, last modified time and date, keywords describing the content of the documents, the file type, the application associated with the file, and access privileges for various users. Content management systems create and manage metadata for each item of data or information entered into the system and maintain a database or repository that contains the metadata. Thus, with a content management system users can locate desired information by searching for relevant attributes or keywords in the metadata database. Utilization of metadata also allows organizing, sorting, and selectively presenting data items based on relevant attributes stored in the associated metadata.
- Metadata can be used, however, for much more than organizing, searching, and retrieving information. Since metadata are just another type of data, any information about the content data can be stored in the associated metadata. Stated generally, metadata can contain “intelligence” about the associated item of data. This intelligence can include: applications associated with the data, what operation can be performed on the data, the history of processing on the data, and what processing should be performed next on the data. Thus, metadata can be used to encode the entire life-cycle specifications for the associated content data. Based on such technologies, the capabilities of content management systems can be extended beyond organization and retrieval of information to management of business processes performed on the documents, information, or data. Systems with such capabilities are called Business Process Management (BPM) or Work Flow Management (WFM) systems. The metadata in this context are also called business process data. At present, vendors such as FileNet, IBM, Documentum, and Vignette provide various content management and/or business process management products or services.
- One particular area where the content management systems are heavily relied on is so-called “fixed content” systems. In some business environments, enterprises are required to maintain data or records that cannot be modified due to the nature of business or government regulatory requirements. Examples include medical records and diagnostic medical images (such as X-ray and MRI images) for healthcare and insurance industry, accounting records and corporate documents for corporations, and security transaction records for brokerage firms or investment banks. For hospitals and healthcare providers, it is important to maintain X-ray and MRI images that cannot be modified due to concerns about accurate diagnosis and keeping accurate medical histories. Various government regulations such as Sarbanes-Oxley, HIPAA (Health Insurance Portability and Accountability Act), and SEC Rule 17a-4 require corporations, insurance companies, and securities brokers to maintain records that are guaranteed against modification for an extended period of time. For these types of records and data, the storage and content management problems are particularly acute due to the fact that the size of overall data must inevitably grow since the records cannot be deleted or modified and must be kept for an extended period of time. At present, vendors such as FileNet, EMC, and Network Appliance offer various fixed content storage systems, while FileNet, IBM, and Documentum provide content management solutions for enterprise record management needs and compliance requirements.
- Despite multitudes of existing products and systems, there exist opportunities for improvements among currently available enterprise information management solutions. One of the shortcomings of existing solutions is lack of integration among various components of enterprise content management and storage systems. For example, as shown in
FIG. 1 , an enterprise content management system typically comprises several separate component systems: namely, content server cluster (110), content data storage (112), content metadata server cluster (120), content metadata storage (122), business process server cluster (130), and business process data storage (132). An enterprise content management system is typically deployed in a local area network (140) environment, and accessed from workstations (150) or personal computers (160). With existing solutions, these component systems are usually provided by different vendors, and are installed, maintained, and operated separately. In addition, the applications or software that provide the content management and business process management functions operate as distinct components separate from the storage systems. - Since there is currently no single integrated solution that provides the entire spectrum of process management, content management and storage capabilities, the enterprises must integrate various components of the enterprise information management system manually. Often the various components are provided by different vendors. This lack of integration causes several serious problems.
- The first is difficulties in system administration including installation, configuration, and upgrade management. Since various components of enterprise information management systems are not aware of each other, they must be installed and configured separately. More often than not, the installation and configuration procedures and tools are quite dissimilar from each other, requiring the operators and administrators to learn and remember the dissimilar procedures and methods. Furthermore, since the configuration information for the entire system is not (and cannot be) maintained by any single component, the system-wide configuration data must be maintained manually through a process that is external to the system, rendering the management of system-wide configuration information an error-prone, complex, and difficult process.
- In addition, upgrades of various components of the enterprise system tend to occur in a manner that is completely unrelated to each other, as the components are produced by different companies with entirely unrelated upgrade or product release schedules. This leads to difficult problems of timing upgrades, upgrade synchronization, and system-wide version maintenance and management. In particular, system-wide version information must be maintained, as interaction between different versions of software and/or hardware sometimes can result in unexpected problems which are difficult to track down. However, as was the case for system-wide configuration information, system-wide version information must be maintained external to the system for exactly the same reasons, leading to similar system administration difficulties. Thus, there exists a need in the field for an integrated enterprise content management system with integrated procedures and tools for installation, configuration, upgrade, and version management.
- The second type of problems that arises from mixing and matching components from different vendors is dissimilar and incongruent semantics among various system components. Because information systems deal with intangible objects, the design and architecture of an information system are inherently based on abstract concepts. Thus, the “ontology” of an information system—what it is and what it does—is a direct result of the design principles, conceptual building blocks (“primitives”), and architectural framework employed by the system designers and architects. Naturally, there are competing design principles and paradigms, and designers and architects of information systems do not think alike. As a result, information systems from different design teams, e.g., from different vendors, tend to look and operate quite differently from each other. Thus, mixing and matching components from different vendors quite often involve translating and mapping dissimilar objects and concepts across the system boundaries. For example, most enterprise content storage systems offer primitives for storing content data and associated content metadata. However, the semantics of the primitives may not be entirely consistent with the semantics of the enterprise content management or business process management systems that operate on top of the storage primitive layers. Dissimilar and incongruent semantics across the system boundaries can sometimes lead to fundamental system problems with adverse consequences. Often, system-wide instability can be traced to inherent instability in system integration due to inconsistent and incongruent semantics across the system component boundaries.
- Furthermore, dissimilar and inconsistent semantics can result in difficulties in system administration, as it is difficult to handle several different semantics and conceptual frameworks at the same time. Consistent semantics, conceptual framework, and design paradigms across the system hierarchy are essential and fundamental requirements for a stable and robust enterprise content management system. Thus, there exists a need in the field for an integrated enterprise content management system that presents a unified paradigm across the system hierarchy with unified and consistent semantics and conceptual framework.
- Some enterprises have attempted to address the problem of dissimilar semantics by employing so-called “Content Bridge” technologies. Content bridges, such as VeniceBridge from Venetica, provide tools to integrate disparate systems by mapping and translating dissimilar logical units, data dictionaries, metaphors, and taxonomy into a single, consistent framework. Although content bridges provide useful tools that can improve the quality of system integration, several problems remain. The first is that some inconsistencies across disparate systems simply cannot be resolved. The second, and a more serious problem is that content bridges do not and cannot address the issues of replication and disaster recovery, since content bridges focus only on the conceptual problems of integrating dissimilar semantics of disparate systems.
- For enterprise systems comprising disparate components from different vendors, replication and disaster recovery must be done separately for each component system. However, it is critical that replication and recovery transactions are synchronized across the entire hierarchy of system data layers. From the low-level storage data of NAS and/or SAN storage systems, to the content data, business process data, associated metadata, and the database that maintains the association information, the entire data set must be perfectly synchronized for the system to be operational and replication and recovery be effective. If these subcomponents become “out of sync” from each other, the entire data set may become meaningless, rendering the enterprise system useless. Nevertheless, existing products and technologies do not provide mechanisms to synchronize replication and recovery with external systems. Thus, currently, system-wide synchronization must be performed manually, and, when the replication and recovery transactions become “out of sync”, the transactions must be reconciled through a manual process. These are difficult and frustrating processes that are also error-prone.
- The problem of replication and recovery synchronization is especially acute for “fixed content” systems discussed above. Because the content data in fixed content systems must be guaranteed against changes while the metadata and association database must be dynamic (i.e., modifiable), the entire data set cannot be stored on the same storage system and backed up together by brute force by “imaging” the entire system. Thus, for currently available fixed content systems, synchronization of replication and recovery must be done manually, with all of the accompanying problems described above.
- For enterprise systems, the importance of replication and disaster recovery cannot be over-stated. Because many modern enterprises depend critically on their enterprise information systems, the enterprise content management systems for those organizations must be mission critical, high availability systems. For these systems, system-wide replication and disaster recovery are essential functions in providing high availability capabilities. Even when high availability is not required, replication and disaster recovery are important in order to provide business continuity protection. Replication and disaster recovery are essential functions to ensure reliability and robustness of enterprise systems. Thus, there exists a need in the field for an integrated enterprise content management system that provides synchronized replication and recovery of all of its components including the content management, business process management, and database and content storage management systems.
- Another problem that comes from integrating disparate components from different vendors is performance degradation. Typically, integration is achieved by utilizing vendor-provided interface layers. Alternatively, components may be integrated employing third-party integration tools such as the content bridges described above. In either case, performance degradation is inevitable whenever interface layers are introduced to a system, because the system needs to perform extra steps in order to process data through the interfaces or bridges.
- It can be seen, then, there is a need for an integrated enterprise content management network attached system that provides a unified approach to the entire range of enterprise content management functions from storage management to content and business process management.
- Accordingly, the present invention addresses the foregoing need by providing an integrated enterprise content management network-attached system that affords a native, unified approach to the entire range of enterprise content management functions from storage management to content and business process management.
- According to one aspect of the invention, the present invention is an enterprise content management network-attached system, where a storage system is provided with integral, native content management and business process management functions. According to this aspect of the invention, the present invention is an enterprise content management network-attached system with native integration of a content management system, a business process system, and a storage system, comprising: a storage system for storing content data, content metadata, business process data, and computer executable process steps for content management and business process management, wherein the computer executable process steps for content management and business process management include: (1) steps for accessing the content data, the content metadata, and business process data, and (2) steps for processing the content data in accordance with information contained in the content metadata and business process data.
- The present invention also encompasses a native, unified replication system which automatically synchronizes replication of the content data, the content metadata, and the business process data.
- According to another aspect of the invention, the present invention is a method of providing services in an enterprise content management network-attached system, where the content management and business process management functions are provided as an integral, native extension of a storage system. According to this aspect of the invention, the present invention is a method of providing services in an enterprise content management network-attached system with native integration of a content management system, a business process system, and a storage system, comprising the steps of: (1) providing a storage system for storing content data, content metadata, business process data, and computer executable process steps for content management and business process management; and (2) providing computer executable process steps for content management and business process management including: (i) steps for accessing the content data, the content metadata, and business process data, and (ii) steps for processing the content data in accordance with information contained in the content metadata and business process data.
- The present invention also encompasses a method for providing a native, unified replication system which automatically synchronizes replication of the content data, the content metadata database, and the business process database.
- Other and further objects and advantages of the present invention will be further understood and appreciated by those skilled in the art by reference to the following specification, claims, and drawings.
- Referring now to the drawings in which like reference numbers represent corresponding parts throughout:
-
FIG. 1 illustrates a network environment in which an enterprise content management system is deployed; -
FIG. 2 illustrates Enterprise Content Management Network-Attached System deployed in a network environment according to the present invention; -
FIG. 3 illustrates the software and hardware components of Enterprise Content Management Network-Attached System according to the present invention; -
FIG. 4 illustrates the architecture of the content management subsystem according to the present invention; -
FIG. 5 illustrates the architecture of the business process management subsystem according to the present invention; -
FIG. 6 illustrates an example of content management according to the present invention; -
FIG. 7 illustrates the high-availability and disaster recovery configurations of the existing content management and business process management systems; and -
FIG. 8 illustrates the integrated high-availability and disaster recovery configurations according to the present invention. - The present invention provides an integrated enterprise content management network-attached system, where a storage system is provided with native, integral content management and business process management functions. According to one aspect of the invention, the present invention is an enterprise content management network-attached system with native integration of a content management system, a business process system, and a storage system, comprising: a storage system for storing content data, content metadata, business process data, and computer executable process steps for content management and business process management, wherein the computer executable process steps for content management and business process management include: (1) steps for accessing the content data, the content metadata, and business process data, and (2) steps for processing the content data in accordance with information contained in the content metadata and business process data. According to the present invention, such enterprise content management system with native integration of a content management system, an optional business process system, and a storage system is defined as Enterprise Content Management Network-Attached System.
-
FIG. 2 illustrates Enterprise Content Management Network-Attached System deployed in a network environment according to the present invention. As shown inFIG. 2 , Enterprise Content Management Network-Attached System (210) is an integrated solution that provides the native, unified content data storage, content metadata storage, and business process data storage functions in “a single box”. Enterprise Content Management Network-Attached System (210) is deployed by simply rolling in the “single box” and connecting it to the network (140) with network connection (212). In addition, the content management and business management functions are provided as the integral part of Enterprise Content Management Network-Attached System (210), not as separate application packages installed and operated separately from the storage system. -
FIG. 3 illustrates the software and hardware components of Enterprise Content Management Network-Attached System according to the present invention. As shown inFIG. 3 , Content Management Subsystem (310), Business Process Management Subsystem (320), Storage System (330), Computing Hardware (340), and Network Interface Hardware (350) are integral part of Enterprise Content Management Network-Attached System (210) which appears as a single system to operators or end-users. The native, unified, and integrated system of the present invention eliminates the problems related to installation, configuration, and upgrade of disparate enterprise system components. The native, unified approach of the present invention also eliminates or greatly reduces the problems due to inconsistent and/or incompatible semantics across disparate systems from different vendors. In addition, the present invention also improves the overall performance of the enterprise system by providing tight integration without unnecessary interfaces or translation layers between various components of the system. The result is a more robust, reliable, and efficient enterprise content management system that is easier to deploy, configure, maintain, operate, and use. - Storage System (330) can be any storage system known to those skilled in the art, including RAID disk farm, Network Attached Storage (NAS) system, and Storage Area Networks (SAN) system, without departing from the scope of the present invention. Currently, vendors such as EMC and Network Appliance offer various NAS and SAN solutions. Storage System (330) can also include a content-addressable storage (CAS) system such as the EMC Centera™ system. For fixed-content systems, Storage System (330) can include any fixed-content storage solutions known to those skilled in the art, including the Optical Storage and Retrieval systems such as the FileNet OSAR™ system and magnetic fixed-content systems such as the EMC Centera™ system, without departing from the scope of the present invention.
- Computing Hardware (340) comprises CPUs, memory units, and supporting computing circuits to provide an Enterprise Server class computing capability for Enterprise Content Management Network-Attached System (210). The CPU can be any high-performance CPU known to those skilled in the art, including an Intel CPU, a PowerPC CPU, a MIPS RISC CPU, a SPARC CPU, or a proprietary CPU, without departing from the scope of the present invention. In addition, there can be multiple CPUs for Computing Hardware (340), including scalable and/or multi-processing CPUs.
- Content Management Subsystem (310) and Business Process Management Subsystem (320) can communicate with each other over any interprocess communication (IPC) mechanism known to those skilled in the art, including pipes, sockets, messages, and RPC, as well as high level communication mechanisms such as SOAP (Simple Object Access Protocol). Content Management Subsystem (310) and Business Process Management Subsystem (320) communicate with outside systems - for example, workstations (150)—over Network API (360) software and Network Interface Hardware (350) connected to network (140) over network connection (212), utilizing proprietary or standards based communications protocols including IETF WebDAV (RFC 2518) and IETF DeltaV (RFC 3253).
-
FIG. 4 illustrates the architecture of the content management subsystem according to the present invention. As shown inFIG. 4 , Content Management Subsystem (310) comprises Content Management Engine (410), Content Data (420), Content Data Database (422), Content Metadata (430), and Content Metadata Database (440). Content Data (420) are stored and accessed through Content Data Database (422) or File System (450) of Storage System (330), and Content Metadata (430) are stored and managed through Content Metadata Database (440) which is itself stored on Storage System (330) through File System (450). - Content Management Engine (410) contains the software logic for providing content management functions. Content Management Engine (410) comprises computer executable process steps stored on Storage System (330) that access Content Data Database (422) and Content Metadata Database (440), and process Content Data (420) in accordance with Content Metadata (430) contained in Content Metadata Database (440).
- In the preferred embodiment, Content Management Engine (410) employs object-oriented (OO) technology. Under this approach, a Business Object is a representation of content data and associated content metadata. A Business Object is described by a class which specifies the object properties (attributes) and the methods (functions or operations). The metadata instances of Business Objects are stored in Content Metadata Database (440), while the content data for the Business Object instances are stored either in the Content Data Database (422) or File System (450). The benefit of object-oriented technology is ease of development, management, and use through abstraction, encapsulation, and inheritance.
-
FIG. 6 illustrates an example of content management according to the present invention. As shown inFIG. 6 , a Business Object for a loan is represented by Loan Object (602), which is an instance of Loan Class (610). Loan Class (610) contains Loan ID Attribute (612), Loan Application Attribute (614), Loan Policy Attribute (616), and Customer Attribute (618). Loan Application Attribute (614) can either point to or contain Loan Application Object (620), which is an instance of Loan Application Class (622). Loan Application Class (622) in turn contains Loan Application Content Attribute (624) and Application Date Attribute (626). Loan Application Content Attribute (624) points to the content data, Loan Application File (630), which can be a scanned image file of a paper application or an electronic application file. - As also shown in
FIG. 6 , Loan Policy Attribute (616) can either point to or contain Loan Policy Object (640), which is an instance of Loan Application Class (642). Loan Policy Class (642) in turn contains Policy Content Attribute (644) and Policy Number Attribute (646). Policy Content Attribute (644) points to the content data, Policy Document File (650), which can be an electronic document file of any type or format, including a Word document and a Acrobat document. Also shown inFIG. 6 is Customer Attribute (618) pointing to Customer Object (660), which is an instance of Customer Class (662). - The Business Objects—Loan Object (602), Loan Application Object (620), Loan Policy Object (640), and Customer Object (660)—are stored and managed through Content Metadata Database (440). Thus, Content Management Subsystem (310) of the present inventions provides services to create, search, find, sort, and manage all documents and information related to a particular loan application. For example, an end-user can search for a loan application by a particular customer by the customer name. Once the search found the match in Content Metadata Database (440), Content Management Subsystem (310) automatically provides access to all related information and documents, including Loan Application File (630) and Policy Document File (650), by utilizing various related Business Objects illustrated above. As an example, after the search, the end-user might request access to the loan application file and loan policy document for this type of loan application. In response to this service request, Content Management Subsystem (310) retrieves Loan Application File (630) by: (1) accessing Loan Application Object (620) by looking up Loan Application Attribute (614) of Loan Object (602); and (2) accessing Loan Application File (630) by looking up Loan Application Content Attribute (624) of Loan Application Object (620). Described schematically, Loan Application File (630) is accessed by the following chain of references: from Loan Object (602) to Loan Application Attribute (614), to Loan Application Object (620), to Loan Application Content Attribute (624), and to Loan Application File (630). Content Management Subsystem (310) retrieves Policy Document File (650) by a similar chain of references: from Loan Object (602), to Loan Policy Attribute (616), to Loan Policy Object (640), to Policy Content Attribute (644), and to Policy Document File (650).
- Content Metadata Database (440) can be any database known to those skilled in the art, including client-server relational databases, object-oriented databases, and object-relational databases, without departing from the scope of the present invention.
- Content Data (420), Content Data Database (422), Content Metadata (430), and Content Metadata Database (440) can also include full text indexing so that the entire content can be searched for text content.
- Further details of content management functions are described in “FileNet Content Manager Architecture: An Architecture White Paper” by FileNet Corporation, published in 2003. The content management functions can include: capability to reliably maintain arbitrary, user specifiable, relationships between two or more content or metadata objects (to represent a compound document, for instance); capability of versioning of one or more content or metadata objects; capability to search for objects based upon metadata and content attributes, including the capability to query utilizing the XQuery or SQL query methods; capability to specify security access requirements on one or more content or metadata objects; secure authorized and audited access to content and metadata objects; and container objects each of which may contain zero or more container, content, metadata, or other objects. Examples of container objects include containers that represent folders, projects, work cases, and taxonomies.
- The content management functions of the present invention can also include: capability to manually file content or metadata objects in one or more user creatable container; capability to automatically file content or metadata objects into one or more user or automatically creatable containers based on attributes of the object content or metadata or inferences of the object content or metadata; capability to store objects containing references to content stored outside of the storage system; capability to discover what metadata is required for adding new content or allowable on existing content; capability to dynamically update metadata or content without versioning or creating superfluous metadata or content objects; capability to raise events and subscription to those events by programs, scripts or other logic that users can provide to extend the behavior of the content storage system; capability to automatically change security on content or metadata objects based on time or some event; capability to provide reports about the utilization of content, metadata, and other objects including information about the eligibility of objects for replication; capability to import or export some or all of the content, metadata, or other objects stored within a content management system; and capability to pre-configure content management software and storage system capabilities so as to reduce cost of installation and minimize installation and configuration related errors.
-
FIG. 5 illustrates the architecture of the business process management subsystem according to the present invention. As shown inFIG. 5 , Business Process Management Subsystem (320) comprises Business Process Management Engine (510), Business Process Data (520), and Business Process Data Database (530). Business Process Data (520) are stored and managed through Business Process Database (530) which is stored on Storage System (330) through File System (450). Business Process Management Engine (510) contains the software logic for providing business process management functions. Business Process Management Engine (510) comprises computer executable process steps stored on Storage System (330) that access Business Process Data (520) stored in Business Process Data Database (530), and process Content Data (420) and/or Business Process Data (520) in accordance with Business Process Data (520) contained in Business Process Data Database (530). - Business Process Data Database (530) can be any network-deployable database known to those skilled in the art, including client-server relational databases, object-oriented databases, and object-relational databases, without departing from the scope of the present invention.
- The details of business process management functions are disclosed in U.S. patent application Ser. No. 10/328,072, “System for Enterprise-Wide Work Flow Automation,” by Luen Kimball Poindexter, Glenn R. Seidman, Stephen R. Timm, and Bruce A. Waddington, filed Dec. 23, 2002, U.S. patent application Ser. No. 09/989,833, “System for Enterprise-Wide Work Flow Automation,” by Luen Kimball Poindexter, Glenn R. Seidman, Stephen R. Timm, and Bruce A. Waddington, filed Nov. 19, 2001, and U.S. Pat. No. 6,338,074, “System for Enterprise-Wide Work Flow Automation,” by Luen Kimball Poindexter, Glenn R. Seidman, Stephen R. Timm, and Bruce A. Waddington, filed Jul. 23, 1997, the disclosures thereof are incorporated by reference herein in their entirety.
- In operation, the enterprise content and business process services of the present invention are provided by Enterprise Content Management Network-Attached System (210) and accessed from workstations (150) or personal computers (160) over network (140). Upon receiving a service request from workstation (150) or personal computer (160), Enterprise Content Management Network-Attached System (210) of the present invention: 1) executes computer executable process codes that comprise Content Management Engine (410) or Business Process Management Engine (510) from Enterprise Content Management Network-Attached System (210); 2) accesses Content Data (420), Content Metadata Database (440), and Business Process Data Database (530); and 3) processes Content Data (420) in accordance with Content Metadata (430) contained in Content Metadata Database (440) and Business Process Data (520) contained in Business Process Data Database (530). The results of the processing are notified to or delivered to the requesting client workstation (150) or personal computer (160).
- The Enterprise Content Management Network-Attached System of the present invention can be configured with high-availability components and capabilities—that is, with redundant components including the power supply, processor, memory, storage, and network interface controllers, controlled by a single, native high-availability (HA) software implementation that will switch to the backup components if the primary components fail. In addition, the Enterprise Content Management Network-Attached System of the present invention can include: capability to create, update, search, and delete content as part of a transaction initiated by the content management software so as to provide a system that is reliable and robust in the event of component system failures; and capability to create, update, search, and delete content and content metadata and user-definable business process as part of a transaction initiated by the calling application so as to implement a system that is reliable and robust in the event of component failures.
- For mission-critical enterprise systems, it is not enough to provide high-availability capability for each of the system components. The entire system could become non-operational or go off-line due to operator error, massive system-wide failures, or natural disasters. Consequently, mission-critical enterprise systems are usually backed up by disaster recovery systems at an off-site facility away from the operation or production deployment site. For disaster recovery systems, a key issue is consistent and reliable replication of relevant data from the operation site (called production site) to disaster recovery site, since the disaster recovery site must contain a current or nearly current set of data for the backup system to be effective. For existing enterprise disaster recovery solutions, providing consistent and reliable replication is a difficult and error-prone process.
-
FIG. 7 illustrates the high-availability and disaster recovery configurations of typical existing content management and business process management systems. As shown inFIG. 7 , in the existing products, content, content metadata, and business process data are replicated separately by different products through disparate processes. Content data are replicated from Content Server Cluster (110) and Content Data Storage (112) to Content Backup (710) via replication product A, content metadata from Content Metadata Server Cluster (120) and Content Metadata Storage (122) to Content Metadata Backup (720) via replication product B, and business process data from Business Process Server Cluster (130) and Business Process Data Storage (132) to Business Process Data Backup (730) via replication product C. Because content, content metadata, and business process data are replicated separately by different mechanisms on different schedules, the replication process can leave the recovery system with inconsistent data. Content data items may be there but their metadata are not, or business process data may include references to content item or metadata values that are not yet replicated to the recovery site. - The present invention eliminates the need for synchronization and coordination of replication operations of disparate systems and the related problems by providing a unified, native replication facility from a single storage system.
FIG. 8 illustrates the integrated high-availability and disaster recovery configurations according to the present invention. As shown inFIG. 8 Enterprise Content Management Network-Attached System (210) is replicated as a single system to Enterprise Content Management Network-Attached System Backup (810), utilizing a single, unified, native replication facility of the system, providing consistent and logically ordered replication of content, content metadata, and business process data. Because Content Data (420), Content Metadata (430), Content Metadata Database (440), Business Process Data (520), Business Process Data Database (530), and File System (450) of Storage System (330) are all integral part of Enterprise Content Management Network-Attached System (210), a single, unified, native replication facility can replicate the entire content of the system more efficiently using a single consistent mechanism, eliminating the need to coordinate replication and synchronize replicated content. - Furthermore, the single, unified, native replication facility of the present invention can guarantee zero-loss replication across all levels of replication, including the disk I/O level, the file system level, and the transaction level. At the disk I/O or storage level, the replication facility of the present invention can guarantee zero-loss replication by not returning from the replication operation—that is, performing a synchronous replication operation—until the disk sector or sectors being replicated has been committed to the recovery site. Similarly, at the file system level, zero-loss replication is guaranteed by not returning from the replication operation until the entire file has been committed to the recovery site. Finally, at the transaction level, zero-loss replication is guaranteed by committing the transaction at both production and recovery sites—i.e., completing the transaction guarantees that the entire set of files comprising the transaction have been committed to both the production site and the recovery site.
- In operation, replication can take place continuously (or in “real-time” ) as the disk sectors, files, or set of files are modified and updated. Thus, as the production system content is being changed by enterprise operations, the production system is transparently mirrored to the recovery site in “real-time” with zero-loss guaranteed across all levels of replication, including the disk I/O level, the file system level, and the transaction level.
- Replication operation can also be scheduled to run automatically at a pre-determined time when the impact of backup operation on the overall system performance is minimal. Alternatively, replication can be initiated manually at any given time.
- When replication is not continuous, ECM Network-Attached System (210) keeps a logically ordered record of the data changes since the last replication. This record represents the delta between the data as of the last replication and the current state. It could be organized by data change operations at the storage level, the file system level, the transaction level, or any other level that allows tracking the logical order of operations and replicating that order at the recovery site. Typically, only the difference delta data are replicated to save replication time and reduce impact on the overall system. Alternatively, the entire data set can be replicated, although this is usually done only during the initial (or the very first) system replication. Once the replication system has determined the delta data set, the data are read from Storage System (330) in the recorded logical order and transmitted in that same logical order to Enterprise Content Management Network-Attached System Backup (810) over a network connection. Because the replication of the entire system data set—Content Data (420), Content Metadata (430), Content Metadata Database (440), Business Process Data (520), and Business Process Data Database (530)—is accomplished through one integrated mechanism, the replication is synchronized automatically, and the need for manual accounting of the synchronization of replicated data is eliminated by the present invention.
- Moreover, system administrators only need to learn and administer a single technology for replication and a single implementation for high availability. This reduces the likelihood of operator errors that would lead to downtime or failure of the recovery system in a disaster.
- The advantages of the present invention ultimately result in a complete enterprise content and business process management system with a lower total cost of ownership (TCO) than the systems with a combination of software and storage systems.
- The foregoing description of the preferred embodiment of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention not be limited by this detailed description, but by the claims and the equivalents to the claims appended hereto.
Claims (20)
1. A system, comprising:
an enterprise content management network-attached system with native integration of a content management system, a business process management system, and a storage system,
wherein the storage system is configured to store content data, content metadata, business process data, and computer executable process steps for content management and business process management,
wherein the computer executable process steps for content management and business process management include: (1) steps for accessing the content data, the content metadata, and the business process data, and (2) steps for processing the content data in accordance with information contained in the content metadata and the business process data, wherein the steps for processing include one of creating data and delivering at least one of the content data, the content metadata, and the results from the steps from processing the content data to a requesting computer.
2. The system of claim 1 , further comprising:
a native, unified replication system which automatically synchronizes replication of the content data, the content metadata, and the business process data.
3. The system of claim 1 , wherein the storage system comprises a Storage Area Network (SAN) system.
4. The system of claim 1 , wherein the storage system comprises a Network Attached Storage (NAS) system.
5. The system of claim 1 , wherein the storage system comprises a Content Addressable Storage (CAS) system.
6. The system of claim 1 , wherein the storage system comprises a fixed content storage system.
7. The system of claim 1 , wherein the content data comprises one or more records.
8. The system of claim 1 , wherein the content data comprises one or more emails.
9. The system of claim 1 , wherein the content data comprises one or more files.
10. The system of claim 1 , wherein the content data comprises data in a database.
11. A method of providing services, comprising the steps of:
providing an enterprise content management network-attached system with native integration of a content management system, a business process management system, and a storage system,
providing the storage system for storing content data, content metadata, business process data, and computer executable process steps for content management and business process management, and
providing computer executable process steps for content management and business process management including: (1) steps for accessing the content data, the content metadata, and the business process data, and (2) steps for processing the content data in accordance with information contained in the content metadata and the business process data, wherein the steps for processing include one of creating data and delivering at least one of the content data, the content metadata, and the results from the steps from processing the content data to a requesting computer.
12. The method of claim 11 , further comprising the step of:
providing a native, unified replication system which automatically synchronizes replication of the content data, the content metadata, and the business process data.
13. The method of claim 11 , wherein, in the step of providing a storage system, the storage system comprises a Storage Area Network (SAN) system.
14. The method of claim 11 , wherein, in the step of providing a storage system, the storage system comprises a Network Attached Storage (NAS) system.
15. The method of claim 11 , wherein, in the step of providing a storage system, the storage system comprises a Content Addressable Storage (CAS) system.
16. The method of claim 11 , wherein, in the step of providing a storage system, the storage system comprises a fixed content storage system.
17. The method of claim 11 , wherein the content data comprises one or more records.
18. The method of claim 11 , wherein the content data comprises one or more emails.
19. The method of claim 11 , wherein the content data comprises one or more files.
20. The method of claim 11 , wherein the content data comprises data in a database.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/741,688 US20070260619A1 (en) | 2004-04-29 | 2007-04-27 | Enterprise content management network-attached system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/834,100 US7213022B2 (en) | 2004-04-29 | 2004-04-29 | Enterprise content management network-attached system |
US11/741,688 US20070260619A1 (en) | 2004-04-29 | 2007-04-27 | Enterprise content management network-attached system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/834,100 Continuation US7213022B2 (en) | 2004-04-29 | 2004-04-29 | Enterprise content management network-attached system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070260619A1 true US20070260619A1 (en) | 2007-11-08 |
Family
ID=35188302
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/834,100 Active 2025-05-20 US7213022B2 (en) | 2004-04-29 | 2004-04-29 | Enterprise content management network-attached system |
US11/363,946 Abandoned US20060149735A1 (en) | 2004-04-29 | 2006-03-01 | Automated records management with enforcement of a mandatory minimum retention record |
US11/741,688 Abandoned US20070260619A1 (en) | 2004-04-29 | 2007-04-27 | Enterprise content management network-attached system |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/834,100 Active 2025-05-20 US7213022B2 (en) | 2004-04-29 | 2004-04-29 | Enterprise content management network-attached system |
US11/363,946 Abandoned US20060149735A1 (en) | 2004-04-29 | 2006-03-01 | Automated records management with enforcement of a mandatory minimum retention record |
Country Status (5)
Country | Link |
---|---|
US (3) | US7213022B2 (en) |
EP (1) | EP1741027A2 (en) |
JP (1) | JP2008506161A (en) |
CA (1) | CA2563879A1 (en) |
WO (1) | WO2005111783A2 (en) |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060015555A1 (en) * | 2004-07-15 | 2006-01-19 | Michael Douglass | Storage cluster server network |
US20060085245A1 (en) * | 2004-10-19 | 2006-04-20 | Filenet Corporation | Team collaboration system with business process management and records management |
US20060085374A1 (en) * | 2004-10-15 | 2006-04-20 | Filenet Corporation | Automatic records management based on business process management |
US20060149735A1 (en) * | 2004-04-29 | 2006-07-06 | Filenet Corporation | Automated records management with enforcement of a mandatory minimum retention record |
US20070088736A1 (en) * | 2005-10-19 | 2007-04-19 | Filenet Corporation | Record authentication and approval transcript |
US20070088585A1 (en) * | 2005-10-19 | 2007-04-19 | Filenet Corporation | Capturing the result of an approval process/workflow and declaring it a record |
US20070150445A1 (en) * | 2005-12-23 | 2007-06-28 | Filenet Corporation | Dynamic holds of record dispositions during record management |
US20070239715A1 (en) * | 2006-04-11 | 2007-10-11 | Filenet Corporation | Managing content objects having multiple applicable retention periods |
US20090210461A1 (en) * | 2008-02-14 | 2009-08-20 | Mcchord Austin | Network Attached Storage System and Method |
US20110153515A1 (en) * | 2009-12-17 | 2011-06-23 | Pitzo Joseph J | Distributed capture system for use with a legacy enterprise content management system |
US8037029B2 (en) | 2006-10-10 | 2011-10-11 | International Business Machines Corporation | Automated records management with hold notification and automatic receipts |
US20120110039A1 (en) * | 2009-05-08 | 2012-05-03 | Invizion Pty Ltd | System and Method for Storage and Retrieval of Electronic Documents |
US20120117025A1 (en) * | 2008-02-18 | 2012-05-10 | Microsoft Corporation | Synchronization of Replications for Different Computing Systems |
US20150180707A1 (en) * | 2010-04-23 | 2015-06-25 | Datcard Systems, Inc. | Event notification in interconnected content-addressable storage systems |
US9258144B2 (en) | 2012-02-23 | 2016-02-09 | Infosys Limited | Methods, systems and computer-readable media for integrating a composite MIME message |
US9390089B2 (en) | 2009-12-17 | 2016-07-12 | Wausau Financial Systems, Inc. | Distributed capture system for use with a legacy enterprise content management system |
US10078674B2 (en) | 2010-06-04 | 2018-09-18 | Mcl Systems Limited | Integrated workflow and database transactions |
Families Citing this family (113)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9361243B2 (en) | 1998-07-31 | 2016-06-07 | Kom Networks Inc. | Method and system for providing restricted access to a storage medium |
US7536524B2 (en) * | 1998-07-31 | 2009-05-19 | Kom Networks Inc. | Method and system for providing restricted access to a storage medium |
US8234477B2 (en) | 1998-07-31 | 2012-07-31 | Kom Networks, Inc. | Method and system for providing restricted access to a storage medium |
US20020046061A1 (en) | 2000-02-11 | 2002-04-18 | Wright Kenneth L. | Personal information system |
US7120629B1 (en) * | 2000-05-24 | 2006-10-10 | Reachforce, Inc. | Prospects harvester system for providing contact data about customers of product or service offered by business enterprise extracting text documents selected from newsgroups, discussion forums, mailing lists, querying such data to provide customers who confirm to business profile data |
US7330850B1 (en) | 2000-10-04 | 2008-02-12 | Reachforce, Inc. | Text mining system for web-based business intelligence applied to web site server logs |
US7469306B2 (en) * | 2002-06-28 | 2008-12-23 | Nxp B.V. | Method for communicating with first and second device that includes reference to metadata wherein third device modifies the metadata based on specific operations by first device |
US8868858B2 (en) * | 2006-05-19 | 2014-10-21 | Inmage Systems, Inc. | Method and apparatus of continuous data backup and access using virtual machines |
US8949395B2 (en) | 2004-06-01 | 2015-02-03 | Inmage Systems, Inc. | Systems and methods of event driven recovery management |
US7730012B2 (en) | 2004-06-25 | 2010-06-01 | Apple Inc. | Methods and systems for managing data |
US7437358B2 (en) | 2004-06-25 | 2008-10-14 | Apple Inc. | Methods and systems for managing data |
US7774326B2 (en) | 2004-06-25 | 2010-08-10 | Apple Inc. | Methods and systems for managing data |
US20060004699A1 (en) * | 2004-06-30 | 2006-01-05 | Nokia Corporation | Method and system for managing metadata |
US7627726B2 (en) * | 2004-06-30 | 2009-12-01 | Emc Corporation | Systems and methods for managing content having a retention period on a content addressable storage system |
US7895218B2 (en) * | 2004-11-09 | 2011-02-22 | Veveo, Inc. | Method and system for performing searches for television content using reduced text input |
JP4752260B2 (en) * | 2004-12-13 | 2011-08-17 | 株式会社日立製作所 | Information processing apparatus and information processing method |
JP4774059B2 (en) * | 2005-02-01 | 2011-09-14 | シーメンス カナダ リミテッド | Electrical exhaust gas recirculation valve |
AU2005330533A1 (en) * | 2005-04-14 | 2006-10-19 | Rajesh Kapur | Method for validating system changes by use of a replicated system as a system testbed |
US7646886B2 (en) * | 2005-05-11 | 2010-01-12 | Lockheed Martin Corporation | Closely-spaced multiple targets detection using a regional window as a discriminant function |
US9508077B2 (en) * | 2005-07-29 | 2016-11-29 | At&T Intellectual Property I, L.P. | Podcasting having inserted content distinct from the podcast content |
US7788266B2 (en) | 2005-08-26 | 2010-08-31 | Veveo, Inc. | Method and system for processing ambiguous, multi-term search queries |
US7779011B2 (en) | 2005-08-26 | 2010-08-17 | Veveo, Inc. | Method and system for dynamically processing ambiguous, reduced text search queries and highlighting results thereof |
US7970743B1 (en) | 2005-09-15 | 2011-06-28 | Emc Corporation | Retention and disposition of stored content associated with multiple stored objects |
US7644054B2 (en) * | 2005-11-23 | 2010-01-05 | Veveo, Inc. | System and method for finding desired results by incremental search using an ambiguous keypad with the input containing orthographic and typographic errors |
US7747579B2 (en) | 2005-11-28 | 2010-06-29 | Commvault Systems, Inc. | Metabase for facilitating data classification |
US8930496B2 (en) | 2005-12-19 | 2015-01-06 | Commvault Systems, Inc. | Systems and methods of unified reconstruction in storage systems |
US20200257596A1 (en) | 2005-12-19 | 2020-08-13 | Commvault Systems, Inc. | Systems and methods of unified reconstruction in storage systems |
US7693889B1 (en) * | 2005-12-28 | 2010-04-06 | Emc Corporation | Automated backup and recovery for content repository |
US7574461B1 (en) * | 2005-12-28 | 2009-08-11 | Emc Corporation | Dividing data for multi-thread backup |
US8095542B1 (en) * | 2006-01-03 | 2012-01-10 | Emc Corporation | Methods and apparatus for allowing access to content |
US7958101B1 (en) * | 2006-01-03 | 2011-06-07 | Emc Corporation | Methods and apparatus for mounting a file system |
US8560503B1 (en) * | 2006-01-26 | 2013-10-15 | Netapp, Inc. | Content addressable storage system |
US7734603B1 (en) | 2006-01-26 | 2010-06-08 | Netapp, Inc. | Content addressable storage array element |
US7657526B2 (en) | 2006-03-06 | 2010-02-02 | Veveo, Inc. | Methods and systems for selecting and presenting content based on activity level spikes associated with the content |
US7818300B1 (en) | 2006-03-07 | 2010-10-19 | Emc Corporation | Consistent retention and disposition of managed content and associated metadata |
US7594082B1 (en) | 2006-03-07 | 2009-09-22 | Emc Corporation | Resolving retention policy conflicts |
US7814063B1 (en) * | 2006-03-07 | 2010-10-12 | Emc Corporation | Retention and disposition of components of a complex stored object |
WO2007104100A1 (en) * | 2006-03-14 | 2007-09-20 | Càvea Systems Australia Pty Ltd | Content management |
US8073860B2 (en) | 2006-03-30 | 2011-12-06 | Veveo, Inc. | Method and system for incrementally selecting and providing relevant search engines in response to a user query |
EP2911071A1 (en) | 2006-04-20 | 2015-08-26 | Veveo, Inc. | User interface methods and systems for selecting and presenting content based on user navigation and selection actions associated with the content |
US7613742B2 (en) * | 2006-05-02 | 2009-11-03 | Mypoints.Com Inc. | System and method for providing three-way failover for a transactional database |
US20070285779A1 (en) * | 2006-06-13 | 2007-12-13 | Walker Christopher B | Optical films comprising high refractive index and antireflective coatings |
US7546486B2 (en) * | 2006-08-28 | 2009-06-09 | Bycast Inc. | Scalable distributed object management in a distributed fixed content storage system |
CA3163292A1 (en) * | 2006-09-14 | 2008-03-20 | Veveo, Inc. | Methods and systems for dynamically rearranging search results into hierarchically organized concept clusters |
US7801862B1 (en) | 2006-09-29 | 2010-09-21 | Emc Corporation | Retention of complex objects |
WO2008045690A2 (en) | 2006-10-06 | 2008-04-17 | Veveo, Inc. | Linear character selection display interface for ambiguous text input |
US20080086463A1 (en) * | 2006-10-10 | 2008-04-10 | Filenet Corporation | Leveraging related content objects in a records management system |
EP2108147B1 (en) * | 2006-10-20 | 2017-03-08 | Her Majesty The Queen, In Right Of Canada As Represented By The Minister Of Health Through The Public Health Agency Of Canada | Method and apparatus for software policy management |
CA2667142C (en) * | 2006-10-20 | 2013-01-08 | Her Majesty The Queen, In Right Of Canada As Represented By The Minister Of Health Through The Public Health Agency Of Canada | Method and apparatus for creating a configurable browser-based forms application |
US8078884B2 (en) | 2006-11-13 | 2011-12-13 | Veveo, Inc. | Method of and system for selecting and presenting content based on user identification |
US8646095B2 (en) * | 2006-11-30 | 2014-02-04 | Microsoft Corporation | Personal site privacy policy |
US7836080B2 (en) * | 2006-12-22 | 2010-11-16 | International Business Machines Corporation | Using an access control list rule to generate an access control list for a document included in a file plan |
US7805472B2 (en) * | 2006-12-22 | 2010-09-28 | International Business Machines Corporation | Applying multiple disposition schedules to documents |
US7831576B2 (en) * | 2006-12-22 | 2010-11-09 | International Business Machines Corporation | File plan import and sync over multiple systems |
US7979398B2 (en) * | 2006-12-22 | 2011-07-12 | International Business Machines Corporation | Physical to electronic record content management |
US7784528B2 (en) * | 2006-12-27 | 2010-08-31 | General Electric Company | Heat exchanger system having manifolds structurally integrated with a duct |
US20080172276A1 (en) * | 2007-01-12 | 2008-07-17 | Burton Mary C | Apparatus, system, and method for assessing information technology environment needs |
US20080181107A1 (en) * | 2007-01-30 | 2008-07-31 | Moorthi Jay R | Methods and Apparatus to Map and Transfer Data and Properties Between Content-Addressed Objects and Data Files |
KR101137243B1 (en) * | 2007-04-17 | 2012-04-20 | (주)야긴스텍 | Intelligent ECM system based on the ontology |
US20080294492A1 (en) * | 2007-05-24 | 2008-11-27 | Irina Simpson | Proactively determining potential evidence issues for custodial systems in active litigation |
WO2008148012A1 (en) | 2007-05-25 | 2008-12-04 | Veveo, Inc. | System and method for text disambiguation and context designation in incremental search |
US7870154B2 (en) * | 2007-09-28 | 2011-01-11 | Hitachi, Ltd. | Method and apparatus for NAS/CAS unified storage system |
US9401846B2 (en) * | 2007-10-17 | 2016-07-26 | Dell Products, Lp | Information handling system configuration identification tool and method |
US8572043B2 (en) | 2007-12-20 | 2013-10-29 | International Business Machines Corporation | Method and system for storage of unstructured data for electronic discovery in external data stores |
US8112406B2 (en) | 2007-12-21 | 2012-02-07 | International Business Machines Corporation | Method and apparatus for electronic data discovery |
US8140494B2 (en) | 2008-01-21 | 2012-03-20 | International Business Machines Corporation | Providing collection transparency information to an end user to achieve a guaranteed quality document search and production in electronic data discovery |
US7899850B2 (en) * | 2008-02-22 | 2011-03-01 | Bycast, Inc. | Relational objects for the optimized management of fixed-content storage systems |
US8275720B2 (en) * | 2008-06-12 | 2012-09-25 | International Business Machines Corporation | External scoping sources to determine affected people, systems, and classes of information in legal matters |
US9830563B2 (en) | 2008-06-27 | 2017-11-28 | International Business Machines Corporation | System and method for managing legal obligations for data |
US8489439B2 (en) | 2008-06-30 | 2013-07-16 | International Business Machines Corporation | Forecasting discovery costs based on complex and incomplete facts |
US8484069B2 (en) | 2008-06-30 | 2013-07-09 | International Business Machines Corporation | Forecasting discovery costs based on complex and incomplete facts |
US8327384B2 (en) | 2008-06-30 | 2012-12-04 | International Business Machines Corporation | Event driven disposition |
US8515924B2 (en) * | 2008-06-30 | 2013-08-20 | International Business Machines Corporation | Method and apparatus for handling edge-cases of event-driven disposition |
US8073729B2 (en) | 2008-09-30 | 2011-12-06 | International Business Machines Corporation | Forecasting discovery costs based on interpolation of historic event patterns |
EP2329424B1 (en) | 2008-08-22 | 2016-12-07 | Datcard Systems, Inc. | System and method of encryption for dicom volumes |
US7992037B2 (en) * | 2008-09-11 | 2011-08-02 | Nec Laboratories America, Inc. | Scalable secondary storage systems and methods |
US8204869B2 (en) * | 2008-09-30 | 2012-06-19 | International Business Machines Corporation | Method and apparatus to define and justify policy requirements using a legal reference library |
US8788519B2 (en) | 2008-10-24 | 2014-07-22 | John C. Canessa | System and methods for metadata management in content addressable storage |
US8898267B2 (en) * | 2009-01-19 | 2014-11-25 | Netapp, Inc. | Modifying information lifecycle management rules in a distributed system |
US8261033B1 (en) | 2009-06-04 | 2012-09-04 | Bycast Inc. | Time optimized secure traceable migration of massive quantities of data in a distributed storage system |
US20110040600A1 (en) * | 2009-08-17 | 2011-02-17 | Deidre Paknad | E-discovery decision support |
US9166714B2 (en) | 2009-09-11 | 2015-10-20 | Veveo, Inc. | Method of and system for presenting enriched video viewing analytics |
US8250041B2 (en) | 2009-12-22 | 2012-08-21 | International Business Machines Corporation | Method and apparatus for propagation of file plans from enterprise retention management applications to records management systems |
US8655856B2 (en) | 2009-12-22 | 2014-02-18 | International Business Machines Corporation | Method and apparatus for policy distribution |
US20110191332A1 (en) | 2010-02-04 | 2011-08-04 | Veveo, Inc. | Method of and System for Updating Locally Cached Content Descriptor Information |
US8620724B2 (en) * | 2010-04-20 | 2013-12-31 | Accenture Global Services Limited | Integration framework for enterprise content management systems |
EP2381395A1 (en) * | 2010-04-20 | 2011-10-26 | Accenture Global Services Limited | Integration frame work for enterprise content management systems |
US8112657B2 (en) * | 2010-06-14 | 2012-02-07 | At&T Intellectual Property I, L.P. | Method, computer, and computer program product for hardware mapping |
US8832148B2 (en) | 2010-06-29 | 2014-09-09 | International Business Machines Corporation | Enterprise evidence repository |
US8566903B2 (en) | 2010-06-29 | 2013-10-22 | International Business Machines Corporation | Enterprise evidence repository providing access control to collected artifacts |
US8402359B1 (en) | 2010-06-30 | 2013-03-19 | International Business Machines Corporation | Method and apparatus for managing recent activity navigation in web applications |
US8386533B2 (en) * | 2010-11-30 | 2013-02-26 | Oracle International Corporation | Records management of database tables |
WO2012078898A2 (en) | 2010-12-10 | 2012-06-14 | Datcard Systems, Inc. | Secure portable medical information access systems and methods related thereto |
EP2681677A4 (en) * | 2011-03-03 | 2014-08-20 | Hewlett Packard Development Co | Records management system |
CN102222090B (en) * | 2011-06-02 | 2012-12-05 | 清华大学 | Mass data resource management frame under cloud environment |
CN102571771B (en) * | 2011-12-23 | 2014-06-04 | 华中科技大学 | Safety authentication method of cloud storage system |
US8954436B2 (en) | 2012-01-26 | 2015-02-10 | International Business Machines Corporation | Monitoring content repositories, identifying misclassified content objects, and suggesting reclassification |
US9355120B1 (en) | 2012-03-02 | 2016-05-31 | Netapp, Inc. | Systems and methods for managing files in a content storage system |
US8892523B2 (en) | 2012-06-08 | 2014-11-18 | Commvault Systems, Inc. | Auto summarization of content |
US9092395B2 (en) | 2012-12-20 | 2015-07-28 | International Business Machines Corporation | Provide an appliance like test vehicle for IT disaster recovery |
US9870422B2 (en) | 2013-04-19 | 2018-01-16 | Dropbox, Inc. | Natural language search |
US20150095283A1 (en) * | 2013-09-27 | 2015-04-02 | Microsoft Corporation | Master schema shared across multiple tenants with dynamic update |
CN103763319B (en) * | 2014-01-13 | 2017-01-18 | 华中科技大学 | Method for safely sharing mobile cloud storage light-level data |
US20160026941A1 (en) * | 2014-07-26 | 2016-01-28 | International Business Machines Corporation | Updating and synchronizing existing case instances in response to solution design changes |
US9558078B2 (en) | 2014-10-28 | 2017-01-31 | Microsoft Technology Licensing, Llc | Point in time database restore from storage snapshots |
US20170091256A1 (en) * | 2015-09-29 | 2017-03-30 | Bank Of America Corporation | Record Retention and Deletion |
JP7030707B2 (en) | 2016-08-22 | 2022-03-07 | オラクル・インターナショナル・コーポレイション | Systems and methods for generating metadata-driven external interfaces for application programming interfaces |
US10540516B2 (en) | 2016-10-13 | 2020-01-21 | Commvault Systems, Inc. | Data protection within an unsecured storage environment |
US9858424B1 (en) * | 2017-01-05 | 2018-01-02 | Votiro Cybersec Ltd. | System and method for protecting systems from active content |
US10331889B2 (en) | 2017-01-05 | 2019-06-25 | Votiro Cybersec Ltd. | Providing a fastlane for disarming malicious content in received input content |
US10642886B2 (en) | 2018-02-14 | 2020-05-05 | Commvault Systems, Inc. | Targeted search of backup data using facial recognition |
US11080151B2 (en) | 2018-09-27 | 2021-08-03 | Hewlett Packard Enterprise Development Lp | Restoration of cloud management platform |
US11232113B2 (en) | 2019-03-12 | 2022-01-25 | Sap Se | Metadata-driven data maintenance |
Citations (69)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4608679A (en) * | 1984-07-11 | 1986-08-26 | Filenet Corporation | Optical storage and retrieval device |
US4675856A (en) * | 1984-07-11 | 1987-06-23 | Filenet Corporation | Optical storage and retrieval device |
US4685095A (en) * | 1984-07-11 | 1987-08-04 | Filenet Corporation | Optical storage and retrieval device |
US5144556A (en) * | 1990-06-07 | 1992-09-01 | International Business Machines Corporation | Method and system for retaining access to deleted documents in a data processing system |
US5710921A (en) * | 1994-05-26 | 1998-01-20 | Fuji Xerox Co., Ltd. | Information processing system and work flow management method therefor |
USRE35861E (en) * | 1986-03-12 | 1998-07-28 | Advanced Software, Inc. | Apparatus and method for comparing data groups |
US5813009A (en) * | 1995-07-28 | 1998-09-22 | Univirtual Corp. | Computer based records management system method |
US5940804A (en) * | 1996-12-18 | 1999-08-17 | Turley; William N. | Computer executable workflow resource management system |
US6061679A (en) * | 1997-11-25 | 2000-05-09 | International Business Machines Corporation | Creating and searching a data structure ordered by ranges of key masks associated with the data structure |
US6141754A (en) * | 1997-11-28 | 2000-10-31 | International Business Machines Corporation | Integrated method and system for controlling information access and distribution |
US20010013004A1 (en) * | 1998-11-03 | 2001-08-09 | Jordan Haris | Brand resource management system |
US20010018693A1 (en) * | 1997-08-14 | 2001-08-30 | Ramesh Jain | Video cataloger system with synchronized encoders |
US6314437B1 (en) * | 1997-09-30 | 2001-11-06 | Infraworks Corporation | Method and apparatus for real-time secure file deletion |
US20010039542A1 (en) * | 2000-03-31 | 2001-11-08 | Atsushi Okada | Information processing apparatus and method, and storage medium |
US6338074B1 (en) * | 1997-07-23 | 2002-01-08 | Filenet Corporation | System for enterprise-wide work flow automation |
US6347299B1 (en) * | 1997-07-31 | 2002-02-12 | Ncr Corporation | System for navigation and editing of electronic records through speech and audio |
US20020032689A1 (en) * | 1999-12-15 | 2002-03-14 | Abbott Kenneth H. | Storing and recalling information to augment human memories |
US20020055888A1 (en) * | 1999-05-03 | 2002-05-09 | Sicommnet, Inc. | Internet-based commerce system |
US20020137493A1 (en) * | 2001-03-26 | 2002-09-26 | International Business Machines Corporation | System and method for improved mobile phone functionality |
US6505219B1 (en) * | 1999-01-27 | 2003-01-07 | Xerox Corporation | Process management system wherein process descriptions provide indices to document histories |
US20030046369A1 (en) * | 2000-10-26 | 2003-03-06 | Sim Siew Yong | Method and apparatus for initializing a new node in a network |
US6553365B1 (en) * | 2000-05-02 | 2003-04-22 | Documentum Records Management Inc. | Computer readable electronic records automated classification system |
US20030105738A1 (en) * | 2001-09-27 | 2003-06-05 | Kabushiki Kaisha Onda Techno | Method and system for managing cases |
US6581069B1 (en) * | 2000-06-01 | 2003-06-17 | Ge Medical Technology Services, Inc. | Automated activation and deactivation of operational data logging on medical imaging device |
US20030135559A1 (en) * | 2002-01-16 | 2003-07-17 | Xerox Corporation | Method and system for flexible workflow management |
US20030182380A1 (en) * | 2000-12-01 | 2003-09-25 | Toshiyasu Yabe | Mail system, server and mail transmitting/receiving device |
US20030182332A1 (en) * | 2002-03-21 | 2003-09-25 | International Business Machines Corporation | System and method for designating and deleting expired files |
US20030187878A1 (en) * | 1999-11-16 | 2003-10-02 | Aircraft Technical Publishers | Computer aided maintenance and repair information system for equipment subject to regulatory compliance |
US20030236788A1 (en) * | 2002-06-03 | 2003-12-25 | Nick Kanellos | Life-cycle management engine |
US6690774B1 (en) * | 2001-09-17 | 2004-02-10 | Bellsouth Intellectual Property Corporation | Voice mail witness |
US20040117358A1 (en) * | 2002-03-16 | 2004-06-17 | Von Kaenel Tim A. | Method, system, and program for an improved enterprise spatial system |
US20040128182A1 (en) * | 2002-12-31 | 2004-07-01 | Pepoon Francesca Miller | Methods and structure for insurance industry workflow processing |
US20040168058A1 (en) * | 2003-02-26 | 2004-08-26 | Permabit, Inc., A Massachusetts Corporation | History preservation in a computer storage system |
US20040187140A1 (en) * | 2003-03-21 | 2004-09-23 | Werner Aigner | Application framework |
US20040193740A1 (en) * | 2000-02-14 | 2004-09-30 | Nice Systems Ltd. | Content-based storage management |
US20040230941A1 (en) * | 2003-01-17 | 2004-11-18 | Marin Mike A. | Component integrator |
US20040249871A1 (en) * | 2003-05-22 | 2004-12-09 | Mehdi Bazoon | System and method for automatically removing documents from a knowledge repository |
US20040260769A1 (en) * | 2003-06-18 | 2004-12-23 | Junji Yamamoto | Method and apparatus for distributed cache control and network system |
US20050027696A1 (en) * | 2003-07-29 | 2005-02-03 | Kishore Swaminathan | Rapid knowledge transfer among workers |
US20050044197A1 (en) * | 2003-08-18 | 2005-02-24 | Sun Microsystems.Inc. | Structured methodology and design patterns for web services |
US20050055519A1 (en) * | 2003-09-08 | 2005-03-10 | Stuart Alan L. | Method, system, and program for implementing retention policies to archive records |
US20050076049A1 (en) * | 2003-10-02 | 2005-04-07 | Marwan Qubti | Business workflow database and user system |
US20050080771A1 (en) * | 2003-10-14 | 2005-04-14 | Fish Edmund J. | Search enhancement system with information from a selected source |
US20050154723A1 (en) * | 2003-12-29 | 2005-07-14 | Ping Liang | Advanced search, file system, and intelligent assistant agent |
US20050216448A1 (en) * | 2000-03-30 | 2005-09-29 | Iqbal Talib | Methods and systems for searching an information directory |
US20050222984A1 (en) * | 2004-03-31 | 2005-10-06 | Guenter Radestock | Fast search with very large result set |
US20050222993A1 (en) * | 2001-03-07 | 2005-10-06 | Beacon Information Technology Inc. | Data search system and method for displaying data search results |
US20050246276A1 (en) * | 2001-08-24 | 2005-11-03 | Via Technologies, Inc. | Method for disbursing account payable |
US20060004689A1 (en) * | 2004-06-30 | 2006-01-05 | Venkat Chandrasekaran | Systems and methods for managing content on a content addressable storage system |
US20060047650A1 (en) * | 2004-08-24 | 2006-03-02 | Freeman Thomas M | Trainable record searcher |
US20060085245A1 (en) * | 2004-10-19 | 2006-04-20 | Filenet Corporation | Team collaboration system with business process management and records management |
US20060085374A1 (en) * | 2004-10-15 | 2006-04-20 | Filenet Corporation | Automatic records management based on business process management |
US20060149735A1 (en) * | 2004-04-29 | 2006-07-06 | Filenet Corporation | Automated records management with enforcement of a mandatory minimum retention record |
US7080066B1 (en) * | 2001-08-09 | 2006-07-18 | Ncr Corporation | Systems and methods for refining a decision-making process via executable sequences |
US20060179061A1 (en) * | 2005-02-07 | 2006-08-10 | D Souza Roy P | Multi-dimensional surrogates for data management |
US20060282292A1 (en) * | 2005-05-10 | 2006-12-14 | Healthmark Multimedia, Llc | Healthcare informed consent system and methods |
US7159178B2 (en) * | 2001-02-20 | 2007-01-02 | Communispace Corp. | System for supporting a virtual community |
US20070088715A1 (en) * | 2005-10-05 | 2007-04-19 | Richard Slackman | Statistical methods and apparatus for records management |
US20070088585A1 (en) * | 2005-10-19 | 2007-04-19 | Filenet Corporation | Capturing the result of an approval process/workflow and declaring it a record |
US20070088736A1 (en) * | 2005-10-19 | 2007-04-19 | Filenet Corporation | Record authentication and approval transcript |
US7237184B2 (en) * | 2003-12-18 | 2007-06-26 | Microsoft Corporation | Data property promotion system and method |
US20070150445A1 (en) * | 2005-12-23 | 2007-06-28 | Filenet Corporation | Dynamic holds of record dispositions during record management |
US20070168315A1 (en) * | 2006-01-03 | 2007-07-19 | Eastman Kodak Company | System and method for generating a work of communication with supplemental context |
US20070192423A1 (en) * | 2006-02-04 | 2007-08-16 | Karlson Bruce L | Document reminder system |
US20070239715A1 (en) * | 2006-04-11 | 2007-10-11 | Filenet Corporation | Managing content objects having multiple applicable retention periods |
US20070271517A1 (en) * | 2006-05-19 | 2007-11-22 | Navigant Consulting, Inc. | System and method for providing a web portal for managing litigation activities |
US20070271308A1 (en) * | 2006-05-22 | 2007-11-22 | Iron Mountain Incorporated | Methods and apparatus for managing retention of information assets |
US7428724B2 (en) * | 2004-06-30 | 2008-09-23 | United Technologies Corporation | Interactive interface for engineering standard work |
US7496860B2 (en) * | 2004-06-30 | 2009-02-24 | United Technologies Corporation | Engineering standard work framework method and system |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030046389A1 (en) * | 2001-09-04 | 2003-03-06 | Thieme Laura M. | Method for monitoring a web site's keyword visibility in search engines and directories and resulting traffic from such keyword visibility |
US7043490B2 (en) * | 2002-03-05 | 2006-05-09 | International Business Machines Corporation | Method, system, and program product to support multiple content-management data models |
JP2003316800A (en) * | 2002-04-22 | 2003-11-07 | Maruzen Co Ltd | Contents control device, contents control method and contents control program |
-
2004
- 2004-04-29 US US10/834,100 patent/US7213022B2/en active Active
-
2005
- 2005-04-22 WO PCT/US2005/013588 patent/WO2005111783A2/en not_active Application Discontinuation
- 2005-04-22 EP EP05737497A patent/EP1741027A2/en not_active Withdrawn
- 2005-04-22 JP JP2007510807A patent/JP2008506161A/en active Pending
- 2005-04-22 CA CA002563879A patent/CA2563879A1/en not_active Abandoned
-
2006
- 2006-03-01 US US11/363,946 patent/US20060149735A1/en not_active Abandoned
-
2007
- 2007-04-27 US US11/741,688 patent/US20070260619A1/en not_active Abandoned
Patent Citations (73)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4675856A (en) * | 1984-07-11 | 1987-06-23 | Filenet Corporation | Optical storage and retrieval device |
US4685095A (en) * | 1984-07-11 | 1987-08-04 | Filenet Corporation | Optical storage and retrieval device |
US4608679A (en) * | 1984-07-11 | 1986-08-26 | Filenet Corporation | Optical storage and retrieval device |
USRE35861E (en) * | 1986-03-12 | 1998-07-28 | Advanced Software, Inc. | Apparatus and method for comparing data groups |
US5144556A (en) * | 1990-06-07 | 1992-09-01 | International Business Machines Corporation | Method and system for retaining access to deleted documents in a data processing system |
US5710921A (en) * | 1994-05-26 | 1998-01-20 | Fuji Xerox Co., Ltd. | Information processing system and work flow management method therefor |
US5813009A (en) * | 1995-07-28 | 1998-09-22 | Univirtual Corp. | Computer based records management system method |
US5940804A (en) * | 1996-12-18 | 1999-08-17 | Turley; William N. | Computer executable workflow resource management system |
US20030093458A1 (en) * | 1997-07-23 | 2003-05-15 | Poindexter Luen Kimball | System for enterprise-wide work flow automation |
US6338074B1 (en) * | 1997-07-23 | 2002-01-08 | Filenet Corporation | System for enterprise-wide work flow automation |
US20020059466A1 (en) * | 1997-07-23 | 2002-05-16 | Filenet Corporation | System for enterprise-wide work flow automation |
US7010602B2 (en) * | 1997-07-23 | 2006-03-07 | Filenet Corporation | Multilevel queuing system for distributing tasks in an enterprise-wide work flow automation |
US6347299B1 (en) * | 1997-07-31 | 2002-02-12 | Ncr Corporation | System for navigation and editing of electronic records through speech and audio |
US20010018693A1 (en) * | 1997-08-14 | 2001-08-30 | Ramesh Jain | Video cataloger system with synchronized encoders |
US6314437B1 (en) * | 1997-09-30 | 2001-11-06 | Infraworks Corporation | Method and apparatus for real-time secure file deletion |
US6061679A (en) * | 1997-11-25 | 2000-05-09 | International Business Machines Corporation | Creating and searching a data structure ordered by ranges of key masks associated with the data structure |
US6141754A (en) * | 1997-11-28 | 2000-10-31 | International Business Machines Corporation | Integrated method and system for controlling information access and distribution |
US20010013004A1 (en) * | 1998-11-03 | 2001-08-09 | Jordan Haris | Brand resource management system |
US6505219B1 (en) * | 1999-01-27 | 2003-01-07 | Xerox Corporation | Process management system wherein process descriptions provide indices to document histories |
US20020055888A1 (en) * | 1999-05-03 | 2002-05-09 | Sicommnet, Inc. | Internet-based commerce system |
US20030187878A1 (en) * | 1999-11-16 | 2003-10-02 | Aircraft Technical Publishers | Computer aided maintenance and repair information system for equipment subject to regulatory compliance |
US20020032689A1 (en) * | 1999-12-15 | 2002-03-14 | Abbott Kenneth H. | Storing and recalling information to augment human memories |
US20040193740A1 (en) * | 2000-02-14 | 2004-09-30 | Nice Systems Ltd. | Content-based storage management |
US20050216448A1 (en) * | 2000-03-30 | 2005-09-29 | Iqbal Talib | Methods and systems for searching an information directory |
US20010039542A1 (en) * | 2000-03-31 | 2001-11-08 | Atsushi Okada | Information processing apparatus and method, and storage medium |
US6553365B1 (en) * | 2000-05-02 | 2003-04-22 | Documentum Records Management Inc. | Computer readable electronic records automated classification system |
US6581069B1 (en) * | 2000-06-01 | 2003-06-17 | Ge Medical Technology Services, Inc. | Automated activation and deactivation of operational data logging on medical imaging device |
US20030046369A1 (en) * | 2000-10-26 | 2003-03-06 | Sim Siew Yong | Method and apparatus for initializing a new node in a network |
US20030182380A1 (en) * | 2000-12-01 | 2003-09-25 | Toshiyasu Yabe | Mail system, server and mail transmitting/receiving device |
US7159178B2 (en) * | 2001-02-20 | 2007-01-02 | Communispace Corp. | System for supporting a virtual community |
US20050222993A1 (en) * | 2001-03-07 | 2005-10-06 | Beacon Information Technology Inc. | Data search system and method for displaying data search results |
US20020137493A1 (en) * | 2001-03-26 | 2002-09-26 | International Business Machines Corporation | System and method for improved mobile phone functionality |
US7080066B1 (en) * | 2001-08-09 | 2006-07-18 | Ncr Corporation | Systems and methods for refining a decision-making process via executable sequences |
US20050246276A1 (en) * | 2001-08-24 | 2005-11-03 | Via Technologies, Inc. | Method for disbursing account payable |
US6690774B1 (en) * | 2001-09-17 | 2004-02-10 | Bellsouth Intellectual Property Corporation | Voice mail witness |
US20030105738A1 (en) * | 2001-09-27 | 2003-06-05 | Kabushiki Kaisha Onda Techno | Method and system for managing cases |
US20030135559A1 (en) * | 2002-01-16 | 2003-07-17 | Xerox Corporation | Method and system for flexible workflow management |
US20040117358A1 (en) * | 2002-03-16 | 2004-06-17 | Von Kaenel Tim A. | Method, system, and program for an improved enterprise spatial system |
US20030182332A1 (en) * | 2002-03-21 | 2003-09-25 | International Business Machines Corporation | System and method for designating and deleting expired files |
US20030236788A1 (en) * | 2002-06-03 | 2003-12-25 | Nick Kanellos | Life-cycle management engine |
US20040128182A1 (en) * | 2002-12-31 | 2004-07-01 | Pepoon Francesca Miller | Methods and structure for insurance industry workflow processing |
US20040230941A1 (en) * | 2003-01-17 | 2004-11-18 | Marin Mike A. | Component integrator |
US20040168058A1 (en) * | 2003-02-26 | 2004-08-26 | Permabit, Inc., A Massachusetts Corporation | History preservation in a computer storage system |
US20040187140A1 (en) * | 2003-03-21 | 2004-09-23 | Werner Aigner | Application framework |
US20040249871A1 (en) * | 2003-05-22 | 2004-12-09 | Mehdi Bazoon | System and method for automatically removing documents from a knowledge repository |
US20040260769A1 (en) * | 2003-06-18 | 2004-12-23 | Junji Yamamoto | Method and apparatus for distributed cache control and network system |
US20050027696A1 (en) * | 2003-07-29 | 2005-02-03 | Kishore Swaminathan | Rapid knowledge transfer among workers |
US7321886B2 (en) * | 2003-07-29 | 2008-01-22 | Accenture Global Services Gmbh | Rapid knowledge transfer among workers |
US20050044197A1 (en) * | 2003-08-18 | 2005-02-24 | Sun Microsystems.Inc. | Structured methodology and design patterns for web services |
US20050055519A1 (en) * | 2003-09-08 | 2005-03-10 | Stuart Alan L. | Method, system, and program for implementing retention policies to archive records |
US20050076049A1 (en) * | 2003-10-02 | 2005-04-07 | Marwan Qubti | Business workflow database and user system |
US20050080771A1 (en) * | 2003-10-14 | 2005-04-14 | Fish Edmund J. | Search enhancement system with information from a selected source |
US7237184B2 (en) * | 2003-12-18 | 2007-06-26 | Microsoft Corporation | Data property promotion system and method |
US20050154723A1 (en) * | 2003-12-29 | 2005-07-14 | Ping Liang | Advanced search, file system, and intelligent assistant agent |
US20050222984A1 (en) * | 2004-03-31 | 2005-10-06 | Guenter Radestock | Fast search with very large result set |
US20060149735A1 (en) * | 2004-04-29 | 2006-07-06 | Filenet Corporation | Automated records management with enforcement of a mandatory minimum retention record |
US20060004689A1 (en) * | 2004-06-30 | 2006-01-05 | Venkat Chandrasekaran | Systems and methods for managing content on a content addressable storage system |
US7496860B2 (en) * | 2004-06-30 | 2009-02-24 | United Technologies Corporation | Engineering standard work framework method and system |
US7428724B2 (en) * | 2004-06-30 | 2008-09-23 | United Technologies Corporation | Interactive interface for engineering standard work |
US20060047650A1 (en) * | 2004-08-24 | 2006-03-02 | Freeman Thomas M | Trainable record searcher |
US20060085374A1 (en) * | 2004-10-15 | 2006-04-20 | Filenet Corporation | Automatic records management based on business process management |
US20060085245A1 (en) * | 2004-10-19 | 2006-04-20 | Filenet Corporation | Team collaboration system with business process management and records management |
US20060179061A1 (en) * | 2005-02-07 | 2006-08-10 | D Souza Roy P | Multi-dimensional surrogates for data management |
US20060282292A1 (en) * | 2005-05-10 | 2006-12-14 | Healthmark Multimedia, Llc | Healthcare informed consent system and methods |
US20070088715A1 (en) * | 2005-10-05 | 2007-04-19 | Richard Slackman | Statistical methods and apparatus for records management |
US20070088736A1 (en) * | 2005-10-19 | 2007-04-19 | Filenet Corporation | Record authentication and approval transcript |
US20070088585A1 (en) * | 2005-10-19 | 2007-04-19 | Filenet Corporation | Capturing the result of an approval process/workflow and declaring it a record |
US20070150445A1 (en) * | 2005-12-23 | 2007-06-28 | Filenet Corporation | Dynamic holds of record dispositions during record management |
US20070168315A1 (en) * | 2006-01-03 | 2007-07-19 | Eastman Kodak Company | System and method for generating a work of communication with supplemental context |
US20070192423A1 (en) * | 2006-02-04 | 2007-08-16 | Karlson Bruce L | Document reminder system |
US20070239715A1 (en) * | 2006-04-11 | 2007-10-11 | Filenet Corporation | Managing content objects having multiple applicable retention periods |
US20070271517A1 (en) * | 2006-05-19 | 2007-11-22 | Navigant Consulting, Inc. | System and method for providing a web portal for managing litigation activities |
US20070271308A1 (en) * | 2006-05-22 | 2007-11-22 | Iron Mountain Incorporated | Methods and apparatus for managing retention of information assets |
Cited By (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060149735A1 (en) * | 2004-04-29 | 2006-07-06 | Filenet Corporation | Automated records management with enforcement of a mandatory minimum retention record |
US20060015555A1 (en) * | 2004-07-15 | 2006-01-19 | Michael Douglass | Storage cluster server network |
US20060085374A1 (en) * | 2004-10-15 | 2006-04-20 | Filenet Corporation | Automatic records management based on business process management |
US20060085245A1 (en) * | 2004-10-19 | 2006-04-20 | Filenet Corporation | Team collaboration system with business process management and records management |
US20070088736A1 (en) * | 2005-10-19 | 2007-04-19 | Filenet Corporation | Record authentication and approval transcript |
US20070088585A1 (en) * | 2005-10-19 | 2007-04-19 | Filenet Corporation | Capturing the result of an approval process/workflow and declaring it a record |
US10402756B2 (en) | 2005-10-19 | 2019-09-03 | International Business Machines Corporation | Capturing the result of an approval process/workflow and declaring it a record |
US20070150445A1 (en) * | 2005-12-23 | 2007-06-28 | Filenet Corporation | Dynamic holds of record dispositions during record management |
US7856436B2 (en) | 2005-12-23 | 2010-12-21 | International Business Machines Corporation | Dynamic holds of record dispositions during record management |
US20070239715A1 (en) * | 2006-04-11 | 2007-10-11 | Filenet Corporation | Managing content objects having multiple applicable retention periods |
US8037029B2 (en) | 2006-10-10 | 2011-10-11 | International Business Machines Corporation | Automated records management with hold notification and automatic receipts |
US20090210461A1 (en) * | 2008-02-14 | 2009-08-20 | Mcchord Austin | Network Attached Storage System and Method |
US8983904B2 (en) * | 2008-02-18 | 2015-03-17 | Microsoft Technology Licensing, Llc | Synchronization of replications for different computing systems |
US20120117025A1 (en) * | 2008-02-18 | 2012-05-10 | Microsoft Corporation | Synchronization of Replications for Different Computing Systems |
US20120110039A1 (en) * | 2009-05-08 | 2012-05-03 | Invizion Pty Ltd | System and Method for Storage and Retrieval of Electronic Documents |
US9390089B2 (en) | 2009-12-17 | 2016-07-12 | Wausau Financial Systems, Inc. | Distributed capture system for use with a legacy enterprise content management system |
US9002838B2 (en) | 2009-12-17 | 2015-04-07 | Wausau Financial Systems, Inc. | Distributed capture system for use with a legacy enterprise content management system |
US20110153515A1 (en) * | 2009-12-17 | 2011-06-23 | Pitzo Joseph J | Distributed capture system for use with a legacy enterprise content management system |
US20150180707A1 (en) * | 2010-04-23 | 2015-06-25 | Datcard Systems, Inc. | Event notification in interconnected content-addressable storage systems |
US20170237606A1 (en) * | 2010-04-23 | 2017-08-17 | Datcard Systems, Inc. | Event notification in interconnected content-addressable storage systems |
US20190036764A1 (en) * | 2010-04-23 | 2019-01-31 | Datcard Systems, Inc. | Event notification in interconnected content-addressable storage systems |
US20160036627A1 (en) * | 2010-04-23 | 2016-02-04 | Datcard Systems, Inc. | Event notification in interconnected content-addressable storage systems |
US20200092163A1 (en) * | 2010-04-23 | 2020-03-19 | Datcard Systems, Inc. | Event notification in interconnected content-addressable storage systems |
US20230091925A1 (en) * | 2010-04-23 | 2023-03-23 | Datcard Systems, Inc. | Event notification in interconnected content-addressable storage systems |
US20230376523A1 (en) * | 2010-04-23 | 2023-11-23 | Datcard Systems, Inc. | Event notification in interconnected content-addressable storage systems |
US10078674B2 (en) | 2010-06-04 | 2018-09-18 | Mcl Systems Limited | Integrated workflow and database transactions |
US10565223B2 (en) | 2010-06-04 | 2020-02-18 | Mcl Systems Limited | Integrated workflow and database transactions |
US9258144B2 (en) | 2012-02-23 | 2016-02-09 | Infosys Limited | Methods, systems and computer-readable media for integrating a composite MIME message |
Also Published As
Publication number | Publication date |
---|---|
US20060149735A1 (en) | 2006-07-06 |
CA2563879A1 (en) | 2005-11-24 |
US20050246311A1 (en) | 2005-11-03 |
WO2005111783A2 (en) | 2005-11-24 |
WO2005111783A3 (en) | 2009-04-02 |
JP2008506161A (en) | 2008-02-28 |
US7213022B2 (en) | 2007-05-01 |
EP1741027A2 (en) | 2007-01-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7213022B2 (en) | Enterprise content management network-attached system | |
US10657008B2 (en) | Managing a redundant computerized database using a replicated database cache | |
CN100445998C (en) | Transactional file system | |
JP6448555B2 (en) | Content class for object storage indexing system | |
US9146934B2 (en) | Reduced disk space standby | |
US6665657B1 (en) | Method and system for cross browsing of various multimedia data sources in a searchable repository | |
US6240429B1 (en) | Using attached properties to provide document services | |
US6327594B1 (en) | Methods for shared data management in a pervasive computing environment | |
Bouzeghoub et al. | Database design tools: An expert system approach | |
US8121978B2 (en) | Database system providing improved methods for data replication | |
US20080147704A1 (en) | Systems and methods for propagation of database schema changes | |
US10146827B2 (en) | Object based content management system and method | |
Do et al. | On metadata interoperability in data warehouses | |
US11500738B2 (en) | Tagging application resources for snapshot capability-aware discovery | |
Blaustein et al. | Updating replicated data during communications failures | |
US11436089B2 (en) | Identifying database backup copy chaining | |
US20040059706A1 (en) | System and method for providing concurrent usage and replacement of non-native language codes | |
Stockinger et al. | Data management for grid environments | |
US20210334165A1 (en) | Snapshot capability-aware discovery of tagged application resources | |
Frank et al. | Architecture for mobile control functions in supplier deliveries for distributed integrated ERP modules | |
Hasan et al. | Remembrance: The unbearable sentience of being digital | |
Darmawan et al. | Database Performance Tuning on AIX | |
Kumar et al. | Implementing Shared Data Services (SDS): A Proposed Approach | |
He | A case study on a [sic] implementation of marketing data analysis system | |
Strohm et al. | Oracle Database Concepts, 11g Release 1 (11.1) B28318-05 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FILENET CORPORATION;REEL/FRAME:020166/0855 Effective date: 20070823 Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION,NEW YO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FILENET CORPORATION;REEL/FRAME:020166/0855 Effective date: 20070823 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |