Abstract: In general, embodiments of the technology relate to a method and system for implementing external content type (ECT) object types in a content management system (CMS). More specifically, embodiments of the technology relate to augmenting the object model with a new class of object type—an external content type (ECT) object type. The ECT object types are a class of object types that are used to manage object (referred to as managed external objects) that are located in external data systems.

Abstract: Systems and methods for data reporting using a data aggregator and a data retrieval tool such as a file intelligence service. The data aggregator stores two sets of data reporting tables and designates a first one of the sets of tables as an active set and the second one of the sets as a non-active set. The active set of tables stores data corresponding to a most recently successfully completed search. The non-active set stores data retrieved by the data retrieval tool from disparate data sources according to current search. The data in the active set of tables is immediately available for use in requested reports. When the data aggregator completes the current search, it designates the non-active set of tables as the active set so that the data therein becomes available for use in requested reports.

Abstract: In general, embodiments of the technology relate to a method and system for implementing external content type (ECT) object types in a content management system (CMS). More specifically, embodiments of the technology relate to augmenting the object model with a new class of object type—an external content type (ECT) object type. The ECT object types are a class of object types that are used to manage object (referred to as managed external objects) that are located in external data systems.

Abstract: Systems and methods for data reporting using a data aggregator and a data retrieval tool such as a file intelligence service. The data aggregator stores two sets of data reporting tables and designates a first one of the sets of tables as an active set and the second one of the sets as a non-active set. The active set of tables stores data corresponding to a most recently successfully completed search. The non-active set stores data retrieved by the data retrieval tool from disparate data sources according to current search. The data in the active set of tables is immediately available for use in requested reports. When the data aggregator completes the current search, it designates the non-active set of tables as the active set so that the data therein becomes available for use in requested reports.

Abstract: A federated compliance management system operating in a cloud computing environment imports a repository-specific retention policy from a source information system operating in an enterprise computing environment and converts, using a policy mapping definition, the repository-specific retention policy into a federated retention policy. The policy mapping definition contains attribute mappings for federated attributes common across a plurality of information systems of disparate types, repository-specific attributes that are specific to an information system, and, where applicable, phase-common attributes that are common for all phases of an information system as well as phase-repository-specific attributes that are configured for a specific phase. The federated retention policy is stored in the cloud computing environment for use by the federated compliance management system, for instance, as a base policy for creating a repository-specific retention policy for a target system.

Abstract: Through a cloud-based centralized user interface, a federated compliance system presents a policy of interest and representations of disparate systems that match the policy of interest to a user. The disparate systems, which operate in a distributed network computing environment, can include cloud-based repositories and off-cloud repositories. The federated compliance system can pull the cloud-based repositories through a cloud orchestrator and the off-cloud repositories through an off-cloud orchestrator over a secure tunnel. The federated compliance system utilizes user-provided information on the policy of interest to determine various categories of attributes from different repository schemas employed by the disparate systems. A federated retention policy mapper, implemented as a compliance service, maps the attributes to a common schema, creates a federated retention policy, and stores it in a federated space in the distributed network computing environment.

Abstract: A federated compliance management system operating in a cloud computing environment imports a repository-specific retention policy from a source information system operating in an enterprise computing environment and converts, using a policy mapping definition, the repository-specific retention policy into a federated retention policy. The policy mapping definition contains attribute mappings for federated attributes common across a plurality of information systems of disparate types, repository-specific attributes that are specific to an information system, and, where applicable, phase-common attributes that are common for all phases of an information system as well as phase-repository-specific attributes that are configured for a specific phase. The federated retention policy is stored in the cloud computing environment for use by the federated compliance management system, for instance, as a base policy for creating a repository-specific retention policy for a target system.

Abstract: In general, embodiments of the technology relate to a method and system for implementing external content type (ECT) object types in a content management system (CMS). More specifically, embodiments of the technology relate to augmenting the object model with a new class of object type - an external content type (ECT) object type. The ECT object types are a class of object types that are used to manage object (referred to as managed external objects) that are located in external data systems.

Abstract: In general, embodiments of the technology relate to a method and system for using micro objects to manage content. More specifically, embodiments of the technology relate to using micro objects to change and/or extend the functionality of the content management system such that the manner in which actions are applied to objects varies based the context of the request that specified an action to be performed on an object.

Abstract: In general, embodiments of the technology relate to a method and system for implementing external content type (ECT) object types in a content management system (CMS). More specifically, embodiments of the technology relate to augmenting the object model with a new class of object type—an external content type (ECT) object type. The ECT object types are a class of object types that are used to manage object (referred to as managed external objects) that are located in external data systems.

Abstract: Through a cloud-based centralized user interface, a federated compliance system presents a policy of interest and representations of disparate systems that match the policy of interest to a user. The disparate systems, which operate in a distributed network computing environment, can include cloud-based repositories and off-cloud repositories. The federated compliance system can pull the cloud-based repositories through a cloud orchestrator and the off-cloud repositories through an off-cloud orchestrator over a secure tunnel. The federated compliance system utilizes user-provided information on the policy of interest to determine various categories of attributes from different repository schemas employed by the disparate systems. A federated retention policy mapper, implemented as a compliance service, maps the attributes to a common schema, creates a federated retention policy, and stores it in a federated space in the distributed network computing environment.

Abstract: In general, embodiments of the technology relate to a method and system for implementing a dynamic content type (DCT) in a content management system. More specifically, embodiments of the technology relate to using a DCT in order to change and/or extend the functionality of the content management system.

Abstract: In general, embodiments of the technology relate to a method and system for implementing a dynamic content type (DCT) in a content management system. More specifically, embodiments of the technology relate to using a DCT in order to change and/or extend the functionality of the content management system.

Abstract: Systems and methods for data reporting using a data aggregator and a data retrieval tool such as a file intelligence service. The data aggregator stores two sets of data reporting tables and designates a first one of the sets of tables as an active set and the second one of the sets as a non-active set. The active set of tables stores data corresponding to a most recently successfully completed search. The non-active set stores data retrieved by the data retrieval tool from disparate data sources according to current search. The data in the active set of tables is immediately available for use in requested reports. When the data aggregator completes the current search, it designates the non-active set of tables as the active set so that the data therein becomes available for use in requested reports.

Abstract: In general, embodiments of the technology relate to a method and system for using micro objects to manage content. More specifically, embodiments of the technology relate to using micro objects to change and/or extend the functionality of the content management system such that the manner in which actions are applied to objects varies based the context of the request that specified an action to be performed on an object.

Abstract: In general, embodiments of the technology relate to a method and system for using micro objects to manage content. More specifically, embodiments of the technology relate to using micro objects to change and/or extend the functionality of the content management system such that the manner in which actions are applied to objects varies based the context of the request that specified an action to be performed on an object.

Abstract: Through a cloud-based centralized user interface, a federated compliance system presents a policy of interest and representations of disparate systems that match the policy of interest to a user. The disparate systems, which operate in a distributed network computing environment, can include cloud-based repositories and off-cloud repositories. The federated compliance system can pull the cloud-based repositories through a cloud orchestrator and the off-cloud repositories through an off-cloud orchestrator over a secure tunnel. The federated compliance system utilizes user-provided information on the policy of interest to determine various categories of attributes from different repository schemas employed by the disparate systems. A federated retention policy mapper, implemented as a compliance service, maps the attributes to a common schema, creates a federated retention policy, and stores it in a federated space in the distributed network computing environment.

Abstract: Superseding a prior version of a document, to which prior version a retention policy or other requirement has been applied, is disclosed. In some embodiments, an attribute of a retention policy indicates whether a document to which the retention policy has been applied is to be superseded by a subsequently created and/or saved version of the document. In some embodiments, the attribute is set by a logic or process configured to apply the retention policy to the document. If the retention policy indicates that supersede is enabled, in various embodiments when a subsequent version is created and/or saved, the prior version is promoted to the final phase of the retention policy that has been applied to it and automatically “qualified” for disposition as indicated in the final phase of the retention policy, without regard to intervening requirements, processes, phases, approvals, retention, waiting, or other periods, etc.

Abstract: Superseding a prior version of a document, to which prior version a retention policy or other requirement has been applied, is disclosed. In some embodiments, an attribute of a retention policy indicates whether a document to which the retention policy has been applied is to be superseded by a subsequently created and/or saved version of the document. In some embodiments, the attribute is set by a logic or process configured to apply the retention policy to the document. If the retention policy indicates that supersede is enabled, in various embodiments when a subsequent version is created and/or saved, the prior version is promoted to the final phase of the retention policy that has been applied to it and automatically “qualified” for disposition as indicated in the final phase of the retention policy, without regard to intervening requirements, processes, phases, approvals, retention, waiting, or other periods, etc.

Abstract: In general, embodiments of the technology relate to a method and system for implementing external content type (ECT) object types in a content management system (CMS). More specifically, embodiments of the technology relate to augmenting the object model with a new class of object type—an external content type (ECT) object type. The ECT object types are a class of object types that are used to manage object (referred to as managed external objects) that are located in external data systems.