# US 8,786,597 B2 · Management of a history of a meeting > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,786,597 B2 - Document ID: US8786597B2 - Status: Granted - Kind: B2 - Application number: 12/826,919 - Filed: 2010-06-30 - Published: 2012-01-05 - Granted: 2014-07-22 - Earliest claimed: 2010-06-30 - Assignees: International Business Machines Corporation - Applicants: Yurdaer Nezihi Doganata; Mercan Topkara - Inventors: Yurdaer Nezihi Doganata; Mercan Topkara - Web page: https://patentgrep.com/patent/US8786597B2 ## CPC - G06F 16/9024: {Graphs; Linked lists (G06F16/9027 takes precedence)} - G06Q 10/00: Administration; Management - G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling - G06Q 10/10: Office automation; Time management - G06Q 10/101: Collaborative creation, e.g. joint development of products or services - G06Q 10/103: {Workflow collaboration or project management} - G06T 11/23: using straight lines or curves - G06T 11/26: Drawing of charts or graphs - G06T 15/40: Hidden part removal - G06T 15/405: {using Z-buffer} - G06T 17/20: Finite element generation, e.g. wire-frame surface description, {tesselation} - G06T 19/00: Manipulating three-dimensional [3D] models or images for computer graphics - G06F 16/358: Browsing; Visualisation therefor - G06F 16/38: Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - G06T: IMAGE DATA PROCESSING OR GENERATION, IN GENERAL ## Abstract Provenance techniques are disclosed for managing a history of a meeting. For example, a method for managing a history associated with a meeting comprises the following steps. Data associated with the meeting is collected. Provenance data is generated based on at least a portion of the collected data, wherein the provenance data is indicative of a lineage of one or more data items. A provenance graph is generated that defines a visual representation of the generated provenance data, wherein graph elements comprise one or more nodes and one or more edges between nodes, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. One or more applications are associated with at least one graph element and are selectable to invoke functionality. The generated provenance graph is stored in a repository for use in analyzing the meeting. ## Claims ### Claim 1 A method for managing a history associated with a meeting, comprising the steps of: collecting data associated with the meeting; generating provenance data based on at least a portion of the collected data, wherein the provenance data is indicative of a lineage of one or more data items; generating a provenance graph that defines a visual representation of the generated provenance data, wherein graph elements comprise one or more nodes and one or more edges between nodes, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records; associating one or more applications with at least one graph element, wherein the one or more applications are selectable to invoke functionality; and storing the generated provenance graph in a repository for use in analyzing the meeting, wherein the step of generating the provenance data based on the collected data further comprises mapping the collected data onto a data model dedicated to meeting activities and meeting data, and previously created to represent the meeting, and using the data model to categorize and capture meeting data records, meeting task records and meeting resource records, respectively. ### Claim 2 (depends on 1) The method of claim 1, wherein the step of collecting data associated with the meeting further comprises probing a system within which the meeting is hosted. ### Claim 3 (depends on 1) The method of claim 1, wherein the data model further comprises one or more provenance record types. ### Claim 4 (depends on 3) The method of claim 3, wherein the one or more provenance record types comprise a data record type wherein a data record comprises a representation of an artifact produced or changed during the meeting. ### Claim 5 (depends on 3) The method of claim 3, wherein the one or more provenance record types comprise a task record type wherein a task record comprises a representation of an execution of one particular meeting-related task. ### Claim 6 (depends on 3) The method of claim 3, wherein the one or more provenance record types comprise a meeting record type wherein a meeting record comprises a representation of one instance of the meeting. ### Claim 7 (depends on 3) The method of claim 3, wherein the one or more provenance record types comprise a resource record type wherein a resource record comprises a representation of a person or a resource that is relevant to a selected scope of provenance of the meeting. ### Claim 8 (depends on 3) The method of claim 3, wherein the one or more provenance record types comprise a custom record type wherein a custom record comprises a representation of a domain-specific artifact. ### Claim 9 (depends on 1) The method of claim 1, wherein the step of generating the provenance graph that provides the visual representation of the generated provenance data further comprises accessing one or more previously created rules that define one or more correlations between data items in the collected data which are then used to connect the data items in the provenance graph. ### Claim 10 (depends on 1) The method of claim 1, wherein the step of generating the provenance graph that provides the visual representation of the generated provenance data further comprises identifying at least one control point such that the provenance graph is generated from a perspective of the identified control point. ### Claim 11 (depends on 1) The method of claim 1, further comprising the step of receiving a query directed to the stored provenance graph. ### Claim 12 (depends on 1) The method of claim 1, further comprising the step of analyzing the stored provenance graph to determine a condition associated with the meeting. ### Claim 13 (depends on 1) The method of claim 1, further comprising the step of updating the provenance graph as subsequent data associated with the meeting is collected. ### Claim 14 (depends on 1) The method of claim 1, wherein the meeting comprises a virtual meeting. ### Claim 15 A method for managing a history associated with a meeting, the method comprising: collecting data associated with a meeting, wherein the collected data comprises a plurality of records; mapping at least some of the records, using a data model, to either a resource, task, data or relationship type, wherein the data model is dedicated to meeting activities and meeting data, and was previously created to represent the meeting, and the data model is used to categorize and capture meeting data records, meeting task records, and meeting resource records, respectively; create a graph from the mapped data, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records, and wherein the records are mapped to one of the resource, task or data types; and using the graph to answer a query or to create a visualization of the meeting record. ### Claim 16 (depends on 15) The method of claim 15, wherein the mapping is based on knowledge of the structure of the input meeting record data. ### Claim 17 (depends on 15) The method of claim 15, wherein the mapping is based on recognizing a format that the data is in. ### Claim 18 (depends on 17) The method of claim 17, wherein the format of a record is that of an email, and based on recognizing that format, the mapping of the record is to a resource.