# US 12,216,715 B2 · System and method for event driven generation of content > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,216,715 B2 - Document ID: US12216715B2 - Status: Granted - Kind: B2 - Application number: 17/982,238 - Filed: 2022-11-07 - Published: 2023-03-09 - Granted: 2025-02-04 - Earliest claimed: 2020-09-14 - Assignees: Open Text Holdings, Inc. - Applicants: Open Text Holdings, Inc. - Inventors: Gowtham Janardhanan; Mohammed Fazil Karni; Preetha Srinivasan - Web page: https://patentgrep.com/patent/US12216715B2 ## CPC - G06F 16/93: Document management systems - G06F 16/128: {Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16)} - G06F 16/1734: {Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs} - G06F 16/188: Virtual file systems - G06F 16/904: Browsing; Visualisation therefor (for navigating the web G06F16/954; browsing optimisation for the web G06F16/957) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Systems and methods for content management that allow external events or data to drive the generation of content are disclosed. Specifically, disclosed embodiments allow events generated from external sources (or data determined from those events, or otherwise determined) to drive the generation of content (or metadata associated with that content) in a content management system. ## Claims ### Claim 1 A system, comprising: a processor; and a non-transitory computer readable medium, storing instructions for: providing an interface to an application of a content management system, the interface for: receiving a first user selection of a first event; initiating real-time generation of a snapshot of a virtual document by sending a snapshot request to a snapshot engine, the snapshot request including a first event identifier for the first event, the snapshot engine configured for: receiving the first event identifier, searching the virtual document using the first event identifier to form the snapshot based on determining a first set of documents associated with the first event identifier, based on metadata of the first set of documents, and responsive to the snapshot request, returning the snapshot that includes the first set of documents; and providing the snapshot to a user. ### Claim 2 (depends on 1) The system of claim 1, wherein the interface is further for: receiving a second user selection of a second event, wherein: the snapshot request includes a second event identifier for the second event, wherein the snapshot engine is further for: receiving the second event identifier, searching the virtual document using the second event identifier to form the snapshot based on determining a second set of documents associated with the first event identifier, based on metadata of the first set of documents, and responsive to the snapshot request, returning the snapshot that includes the first set of documents the second set of documents. ### Claim 3 (depends on 1) The system of claim 1, wherein the interface is further for: initiating a display of a plurality of selectable events and respective documents associated with the selectable events. ### Claim 4 (depends on 3) The system of claim 3, wherein: the plurality of selectable events have been previously tracked and associated with the respective documents by the content management system. ### Claim 5 (depends on 1) The system of claim 1, wherein the snapshot engine is further for: applying a snapshot rule that specifies that only documents of the virtual document that are associated with event data of the first event are to be captured in the snapshot. ### Claim 6 (depends on 1) The system of claim 1, wherein the snapshot engine is further for: forming the snapshot of the virtual document to include versions of documents having the first event identifier in metadata of the versions of the documents. ### Claim 7 (depends on 1) The system of claim 1, wherein: the virtual document includes a first child document comprising a first document of a first document type and a second child document comprising a second document of a second document type, and a schema for a type of the virtual document is maintained by the content management system, wherein the schema defines each type of document that is included in the virtual document. ### Claim 8 A method, comprising: providing an interface to an application of a content management system, the interface for: receiving a first user selection of a first event; initiating real-time generation of a snapshot of a virtual document by sending a snapshot request to a snapshot engine, the snapshot request including a first event identifier for the first event, the snapshot engine configured for: receiving the first event identifier, searching the virtual document using the first event identifier to form the snapshot based on determining a first set of documents associated with the first event identifier, based on metadata of the first set of documents, and responsive to the snapshot request, returning the snapshot that includes the first set of documents; and providing the snapshot to a user. ### Claim 9 (depends on 8) The method of claim 8, wherein the interface is further for: receiving a second user selection of a second event, wherein: the snapshot request includes a second event identifier for the second event, wherein the snapshot engine is further for: receiving the second event identifier, searching the virtual document using the second event identifier to form the snapshot based on determining a second set of documents associated with the first event identifier, based on metadata of the first set of documents, and responsive to the snapshot request, returning the snapshot that includes the first set of documents the second set of documents. ### Claim 10 (depends on 8) The method of claim 8, wherein the interface is further for: initiating a display of a plurality of selectable events and respective documents associated with the selectable events. ### Claim 11 (depends on 10) The method of claim 10, wherein: the plurality of selectable events have been previously tracked and associated with the respective documents by the content management system. ### Claim 12 (depends on 8) The method of claim 8, wherein the snapshot engine is further for: applying a snapshot rule that specifies that only documents of the virtual document that are associated with event data of the first event are to be captured in the snapshot. ### Claim 13 (depends on 8) The method of claim 8, wherein the snapshot engine is further for: forming the snapshot of the virtual document to include versions of documents having the first event identifier in metadata of the versions of the documents. ### Claim 14 (depends on 8) The method of claim 8, wherein: the virtual document includes a first child document comprising a first document of a first document type and a second child document comprising a second document of a second document type, and a schema for a type of the virtual document is maintained by the content management system, wherein the schema defines each type of document that is included in the virtual document. ### Claim 15 A non-transitory computer readable medium, storing instructions for: providing an interface to an application of a content management system, the interface for: receiving a first user selection of a first event; initiating real-time generation of a snapshot of a virtual document by sending a snapshot request to a snapshot engine, the snapshot request including a first event identifier for the first event, the snapshot engine configured for: receiving the first event identifier, searching the virtual document using the first event identifier to form the snapshot based on determining a first set of documents associated with the first event identifier, based on metadata of the first set of documents, and responsive to the snapshot request, returning the snapshot that includes the first set of documents; and providing the snapshot to a user. ### Claim 16 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the interface is further for: receiving a second user selection of a second event, wherein: the snapshot request includes a second event identifier for the second event, wherein the snapshot engine is further for: receiving the second event identifier, searching the virtual document using the second event identifier to form the snapshot based on determining a second set of documents associated with the first event identifier, based on metadata of the first set of documents, and responsive to the snapshot request, returning the snapshot that includes the first set of documents the second set of documents. ### Claim 17 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the interface is further for: initiating a display of a plurality of selectable events and respective documents associated with the selectable events. ### Claim 18 (depends on 17) The non-transitory computer readable medium of claim 17, wherein: the plurality of selectable events have been previously tracked and associated with the respective documents by the content management system. ### Claim 19 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the snapshot engine is further for: applying a snapshot rule that specifies that only documents of the virtual document that are associated with event data of the first event are to be captured in the snapshot. ### Claim 20 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the snapshot engine is further for: forming the snapshot of the virtual document to include versions of documents having the first event identifier in metadata of the versions of the documents.