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 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 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: A method and system for writing data, including receiving a request to store a file, where the request has context information. The method further includes generating a metadata portion based on the context information, dividing the file into a plurality of data portions, generating a plurality of blocks where each of the plurality of blocks has the metadata portion and one of the plurality of data portions, and storing the plurality of blocks in a storage array.

Abstract: In general, embodiments of the technology relate to encryption requirements for distributed data archives. More specifically, embodiments of the technology relate to accessing globally distributed data archives by way of local query nodes while providing that encryption rules are enforced.

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: A method and system for requesting a first data, including receiving from a first requestor a first query request to read the first data located in a first geographic location, where the first requestor is located in a second geographic location. The method further includes executing the first query request by a query engine in the first geographic location to obtain a first query result, obtaining a first compliance rule based on at least one of the first geographic location, the second geographic location, generating an exportable result by applying the first compliance rule to the first query result, and transmitting the first exportable result to the first requestor.

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: 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: Polymorphic application of a policy is disclosed. An indication is received that a retention policy is to be applied with respect to an object. A rule is evaluated associated with the retention policy, in light of a circumstance of the object, to determine a manner in which the retention policy is to be configured to behave with respect to the object.

Abstract: Polymorphic application of a policy is disclosed. An indication is received that a retention policy is to be applied with respect to an object. A rule is evaluated associated with the retention policy, in light of a circumstance of the object, to determine a manner in which the retention policy is to be configured to behave with respect to the object.

Abstract: Polymorphic application of a policy is disclosed. An indication is received that a retention policy is to be applied with respect to an object. A rule is evaluated associated with the retention policy, in light of a circumstance of the object, to determine a manner in which the retention policy is to be configured to behave with respect to the object.

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: Techniques allow for applying a retention policy to a composite object. For each composite object type there is a description of the composite object structure and rules that determine how the retention policy is to be applied. A retention application can review the descriptions and rules and, based on the review, apply the appropriate retention policy to each of the objects that make up the composite object.

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: Consistent retention and disposition of managed content and associated metadata is disclosed. An indication that a retention policy is to be applied to a selected item of content comprising a body of managed content is received. The selected item of content and its associated metadata are retained automatically in parallel in accordance with the retention policy.

Abstract: Retention and disposition of stored content associated with multiple stored objects is disclosed. An indication is received that a first stored object associated with an item of content comprising a body of managed content is no longer subject to retention under a retention policy applicable to the first stored object. The item of content is deleted or otherwise disposed of only if the item of content is not associated with a second stored object that is still required or desired to be retained.

Abstract: Resolving retention policy conflicts is disclosed. An indication is received that two or more retention policies apply to an item of content. A merged retention policy that is based at least in part on the respective requirements of the two or more retention policies is generated automatically for the item of content.

Abstract: Consistent retention and disposition of managed content and associated metadata is disclosed. An indication that a retention policy is to be applied to a selected item of content comprising a body of managed content is received. The selected item of content and its associated metadata are retained automatically in parallel in accordance with the retention policy.