# US 2018/0025027 A1 · Systems and methods for in-place records management and content lifecycle management > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0025027 A1 - Document ID: US20180025027A1 - Status: Published application - Kind: A1 - Application number: 15/722,871 - Filed: 2017-10-02 - Published: 2018-01-25 - Earliest claimed: 2012-07-12 - Assignees: Open Text SA ULC - Applicants: Open Text SA ULC - Inventors: Jody Hupton Palmer - Web page: https://patentgrep.com/patent/US20180025027A1 ## CPC - G06F 16/185: Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof (details of archiving G06F16/11) - G06F 16/25: Integrating or interfacing systems involving database management systems - G06F 16/256: {in federated or virtual databases} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract An in-place information management system having a management application built on a common data model and configured for asynchronous query-based application of policies on content stored in the disparate data storage systems through a query interface which may be part of a set of integration services. The common data model may be configured based on common architectures of the disparate data storage systems. The query interface may be configured for running a query on a data storage system in response to a search request received by the management application from a records manager and for mapping semantically equalivant keys from disparate data storage systems to a key in the common data model. The query may define a set of records to be treated similarly according to corporate policy on content lifecycle and records compliance. ## Claims ### Claim 1 A method, comprising: receiving a search request from a client device, the receiving performed by a management application hosted on a server computer, the management application built on a common data model, the common data model having a common data model format and a set of keys mapped to semantically equivalent keys from disparate backend systems; communicating, by the management application, a query in the common data model format to a query interface executing on the server computer; translating or interpreting, by the query interface utilizing the set of keys in the common data model mapped to the semantically equivalent keys from the disparate backend systems, the query in the common data model format into requests in disparate formats for the disparate backend systems, and wherein the disparate backend systems identify managed content that match criteria, metadata, or a combination thereof in the requests and return identification information for the managed content to the query interface executing on the server computer; translating or interpreting, by the query interface utilizing the set of keys in the common data model mapped to the semantically equivalent keys from the disparate backend systems, the identification information from the disparate backend systems into the common data model format; communicating, by the query interface, the identification information in the common data model format to the management application; and returning, by the management application, the identification information for the managed content to the client device. ### Claim 2 (depends on 1) The method according to claim 1, further comprising: generating, for presentation via a user interface on the client device and utilizing the identification information for the managed content and at least one of the criteria or metadata, a representation of the managed content, the managed content comprising records stored in the disparate backend systems. ### Claim 3 (depends on 2) The method according to claim 2, further comprising: receiving, via the user interface on the client device, an indication that a policy is to be associated with the records stored in the disparate backend systems; and associating the records stored in the disparate backend systems with a classification that complies with the policy to thereby map the policy to the records stored in the disparate backend systems. ### Claim 4 (depends on 3) The method according to claim 3, further comprising: associating the records stored in the disparate backend systems with a schedule, wherein the policy comprises a lifecycle policy, and wherein the schedule defines a lifecycle of the records stored in the disparate backend systems according to the lifecycle policy. ### Claim 5 (depends on 3) The method according to claim 3, wherein the associating is performed dynamically responsive to the search request from the client device or asynchronously after an approval process associated with the policy. ### Claim 6 (depends on 2) The method according to claim 2, further comprising: copying at least a record stored in a backend system of the disparate backend systems into a hold repository, wherein the backend system does not support in-place holds. ### Claim 7 (depends on 1) The method according to claim 1, further comprising: holding a request at the server computer when a backend system of the disparate backend systems is off-line; and asynchronously sending the request to the backend system when the backend system comes back on-line. ### Claim 8 A system, comprising: a server computer having a processor, a non-transitory computer-readable medium, and stored instructions translatable by the processor to implement a management application and a query interface, the management application built on a common data model, the common data model having a common data model format and a set of keys mapped to semantically equivalent keys from disparate backend systems; wherein the management application receives a search request from a client device and communicates a query in the common data model format to the query interface; wherein the query interface translates or interprets, utilizing the set of keys in the common data model mapped to the semantically equivalent keys from the disparate backend systems, the query in the common data model format into requests in disparate formats for the disparate backend systems; wherein the disparate backend systems identify managed content that match criteria, metadata, or a combination thereof in the requests and return identification information for the managed content to the query interface; wherein the query interface translates or interprets, utilizing the set of keys in the common data model mapped to the semantically equivalent keys from the disparate backend systems, the identification information from the disparate backend systems into the common data model format and communicates the identification information in the common data model format to the management application; and wherein the management application returns the identification information for the managed content to the client device. ### Claim 9 (depends on 8) The system of claim 8, wherein the server computer generates, for presentation via a user interface on the client device and utilizing the identification information for the managed content and at least one of the criteria or metadata, a representation of the managed content, the managed content comprising records stored in the disparate backend systems. ### Claim 10 (depends on 9) The system of claim 9, wherein the server computer receives, via the user interface on the client device, an indication that a policy is to be associated with the records stored in the disparate backend systems, and associates the records stored in the disparate backend systems with a classification that complies with the policy to thereby map the policy to the records stored in the disparate backend systems. ### Claim 11 (depends on 10) The system of claim 10, wherein the server computer further associates the records stored in the disparate backend systems with a schedule, wherein the policy comprises a lifecycle policy, and wherein the schedule defines a lifecycle of the records stored in the disparate backend systems according to the lifecycle policy. ### Claim 12 (depends on 10) The system of claim 10, wherein the associating is performed dynamically responsive to the search request from the client device or asynchronously after an approval process associated with the policy. ### Claim 13 (depends on 9) The system of claim 9, wherein the server computer copies at least a record stored in a backend system of the disparate backend systems into a hold repository and wherein the backend system does not support in-place holds. ### Claim 14 (depends on 8) The system of claim 8, wherein the server computer holds a request when a backend system of the disparate backend systems is off-line and asynchronously sends the request to the backend system when the backend system comes back on-line. ### Claim 15 A computer program product comprising a non-transitory computer readable medium storing instructions translatable by a processor of a server computer to implement a management application and a query interface, the management application built on a common data model, the common data model having a common data model format and a set of keys mapped to semantically equivalent keys from disparate backend systems; wherein the management application receives a search request from a client device and communicates a query in the common data model format to the query interface; wherein the query interface translates or interprets, utilizing the set of keys in the common data model mapped to the semantically equivalent keys from the disparate backend systems, the query in the common data model format into requests in disparate formats for the disparate backend systems; wherein the disparate backend systems identify managed content that match criteria, metadata, or a combination thereof in the requests and return identification information for the managed content to the query interface; wherein the query interface translates or interprets, utilizing the set of keys in the common data model mapped to the semantically equivalent keys from the disparate backend systems, the identification information from the disparate backend systems into the common data model format and communicates the identification information in the common data model format to the management application; and wherein the management application returns the identification information for the managed content to the client device. ### Claim 16 (depends on 15) The computer program product of claim 15, wherein the instructions are further translatable by the processor to perform: generating, for presentation via a user interface on the client device and utilizing the identification information for the managed content and at least one of the criteria or metadata, a representation of the managed content, the managed content comprising records stored in the disparate backend systems. ### Claim 17 (depends on 16) The computer program product of claim 16, wherein the instructions are further translatable by the processor to perform: receiving, via the user interface on the client device, an indication that a policy is to be associated with the records stored in the disparate backend systems; and associating the records stored in the disparate backend systems with a classification that complies with the policy to thereby map the policy to the records stored in the disparate backend systems. ### Claim 18 (depends on 16) The computer program product of claim 16, wherein the instructions are further translatable by the processor to perform: associating the records stored in the disparate backend systems with a schedule, wherein the policy comprises a lifecycle policy, and wherein the schedule defines a lifecycle of the records stored in the disparate backend systems according to the lifecycle policy. ### Claim 19 (depends on 17) The computer program product of claim 17, wherein the associating is performed dynamically responsive to the search request from the client device or asynchronously after an approval process associated with the policy. ### Claim 20 (depends on 16) The computer program product of claim 16, wherein the instructions are further translatable by the processor to perform: copying at least a record stored in a backend system of the disparate backend systems into a hold repository and wherein the backend system does not support in-place holds.