Abstract: Described are techniques for providing a framework having a scanning control for selecting a batch of documents using configuration data and a process control for processing the batch of documents. Under control of the framework, the batch of documents is sent to a plurality of subscribed applications serially, wherein the batch of documents is selected based on a high key value stored in the configuration data, and wherein each of the subscribed applications subscribes with the framework to process a document type, and the stored high key value in the configuration data is updated for use in selecting another batch of documents.

Abstract: Described are techniques for providing a framework having a scanning control for selecting a batch of documents using configuration data and a process control for processing the batch of documents. Under control of the framework, the batch of documents is sent to a plurality of subscribed applications serially, wherein the batch of documents is selected based on a high key value stored in the configuration data, and wherein each of the subscribed applications subscribes with the framework to process a document type, and the stored high key value in the configuration data is updated for use in selecting another batch of documents.

Abstract: The present disclosure relates to maintaining consistency in a content management system. A content management system generally includes a transactional database for storing content metadata and a non-transactional data repository for storing content. According to one embodiment, a content management system generates a set of content identifiers. The content management system receives a request to upload content to the content management system. Upon receiving the request, the content management system associates the content with a content identifier from the set of content identifiers and generates a name for the content from the content identifier. The content management system stores the content, with the generated name, in a non-transactional data repository and persists metadata related to the content in a transactional data store.

Abstract: The present disclosure relates to maintaining consistency in a content management system. A content management system generally includes a transactional database for storing content metadata and a non-transactional data repository for storing content. According to one embodiment, a content management system generates a set of content identifiers. The content management system receives a request to upload content to the content management system. Upon receiving the request, the content management system associates the content with a content identifier from the set of content identifiers and generates a name for the content from the content identifier. The content management system stores the content, with the generated name, in a non-transactional data repository and persists metadata related to the content in a transactional data store.

Abstract: The present disclosure relates to maintaining consistency in a content management system. A content management system generally includes a transactional database for storing content metadata and a non-transactional data repository for storing content. According to one embodiment, a content management system generates a set of content identifiers. The content management system receives a request to upload content to the content management system. Upon receiving the request, the content management system associates the content with a content identifier from the set of content identifiers and generates a name for the content from the content identifier. The content management system stores the content, with the generated name, in a non-transactional data repository and persists metadata related to the content in a transactional data store.

Abstract: The present disclosure relates to maintaining consistency in a content management system. A content management system generally includes a transactional database for storing content metadata and a non-transactional data repository for storing content. According to one embodiment, a content management system generates a set of content identifiers. The content management system receives a request to upload content to the content management system. Upon receiving the request, the content management system associates the content with a content identifier from the set of content identifiers and generates a name for the content from the content identifier. The content management system stores the content, with the generated name, in a non-transactional data repository and persists metadata related to the content in a transactional data store.

Abstract: Described are techniques for providing a framework having a scanning control for selecting a batch of documents using configuration data and a process control for processing the batch of documents. Under control of the framework, the batch of documents is sent to a plurality of subscribed applications serially, wherein the batch of documents is selected based on a high key value stored in the configuration data, and wherein each of the subscribed applications subscribes with the framework to process a document type, and the stored high key value in the configuration data is updated for use in selecting another batch of documents.

Abstract: Described are techniques for providing a framework having a scanning control for selecting a batch of documents using configuration data and a process control for processing the batch of documents. Under control of the framework, the batch of documents is sent to a plurality of subscribed applications serially, wherein the batch of documents is selected based on a high key value stored in the configuration data, and wherein each of the subscribed applications subscribes with the framework to process a document type, and the stored high key value in the configuration data is updated for use in selecting another batch of documents.

Abstract: Methods, apparatus, and articles for creating a document revision history for a document imported into a first Electronic Document Management System (EDMS) from a second EDMS. Metadata and content from the second EDMS is “mirrored” within the first EDMS to create an artificial or mirrored revision history of a document within the first EDMS. Doing so allows users of the first EDMS to access any version of a document and its history, as though the document had always existed on the first EDMS. Content may be stored onto the first EDMS or a reference to the content may be stored instead. Rules may be developed to resolve conflicts between different document versions in the first and second EDMS.

Abstract: A data storage management system comprises a workflow engine, a lifecycle module, and a storage application. The workflow engine is configured to manage a plurality of defined business processes and to execute at least one process step associated with at least one data item. The lifecycle module is configured to detect a change in lifecycle of the at least one data item. The storage application is configured to perform at least one storage action on the data item as a result of the data item reaching a step in a business process, the data item having a change in lifecycle, the data item having a change in metadata, or an event occurring to the data item. Application layer information about data derived from operation of the system allows the system to make more accurate determinations of business value of data and to determine appropriate storage actions to perform on data.

Abstract: Methods, apparatus, and articles for creating a document revision history for a document imported into a first Electronic Document Management System (EDMS) from a second EDMS. Metadata and content from the second EDMS is “mirrored” within the first EDMS to create an artificial or mirrored revision history of a document within the first EDMS. Doing so allows users of the first EDMS to access any version of a document and its history, as though the document had always existed on the first EDMS. Content may be stored onto the first EDMS or a reference to the content may be stored instead. Rules may be developed to resolve conflicts between different document versions in the first and second EDMS.

Abstract: A data storage management system comprises a workflow engine, a lifecycle module, and a storage application. The workflow engine is configured to manage a plurality of defined business processes and to execute at least one process step associated with at least one data item. The lifecycle module is configured to detect a change in lifecycle of the at least one data item. The storage application is configured to perform at least one storage action on the data item as a result of the data item reaching a step in a business process, the data item having a change in lifecycle, the data item having a change in metadata, or an event occurring to the data item. Application layer information about data derived from operation of the system allows the system to make more accurate determinations of business value of data and to determine appropriate storage actions to perform on data.