US20090222741A1 - Collaborative management of activities occurring during the lifecycle of a meeting - Google Patents
Collaborative management of activities occurring during the lifecycle of a meeting Download PDFInfo
- Publication number
- US20090222741A1 US20090222741A1 US12/039,789 US3978908A US2009222741A1 US 20090222741 A1 US20090222741 A1 US 20090222741A1 US 3978908 A US3978908 A US 3978908A US 2009222741 A1 US2009222741 A1 US 2009222741A1
- Authority
- US
- United States
- Prior art keywords
- meeting
- agenda
- user interface
- shared workspace
- notes
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
Definitions
- While current software tools provide a great deal of functionality for scheduling meetings, these tools provide little if any functionality for managing activities that occur during the entire lifecycle of a meeting.
- the lifecycle of a meeting refers to the time prior to the meeting, during the meeting, and after the meeting.
- a user may create a meeting agenda prior to a meeting that identifies one or more topics for the meeting.
- one or more users may take notes on the meeting.
- one or more users may create a summary of the meeting.
- Current software tools provide little if any functionality for managing these activities.
- a collaboration program is described herein that includes functionality for collaborative management of activities occurring during the entire lifecycle of a meeting.
- meeting participants can collaborate on the creation of a meeting agenda prior to the occurrence of a meeting, can independently take and exchange meeting notes during a meeting, and can collaboratively generate a meeting summary following the meeting.
- the meeting agenda, meeting notes, and meeting summaries are synchronized to a shared workspace accessible to each of the meeting participants.
- a collaboration program includes functionality for storing documents and other content in a shared workspace.
- a shared workspace is a local or distributed storage location for storing documents and other content.
- the collaboration program also includes functionality for synchronizing changes made to documents or other content stored within the shared workspace to all of the members of a group.
- the collaboration program includes functionality for collaborative management of activities occurring during the lifecycle of a meeting.
- the collaboration program includes functionality for scheduling a meeting with other users of the collaboration program (referred to herein as “meeting participants”).
- activities occurring prior to the meeting can be collaboratively managed through the use of functionality provided by the collaboration program.
- the collaboration program may provide a user interface and associated functionality for collaboratively creating an agenda for the meeting.
- the agenda may include one or more meeting items, and meeting participants may be permitted to create agenda items, edit agenda items, and delete agenda items.
- a presenter may also be assigned for each agenda item and the agenda items may also be placed in a desired order. Documents or other types of attachments may also be added to the agenda items.
- the agenda Once the agenda has been created, it may be synchronized to a shared workspace, thereby making it available to all of the meeting participants for viewing and modification.
- the collaboration program also provides a user interface and associated functionality for managing activities that occur during a meeting.
- the collaboration program provides functionality for allowing meeting participants to take notes related to the meeting. Functionality may also be provided for adding an agenda for the meeting to the meeting notes. Once the notes have been created, they may also be stored in the shared workspace for access and use by other authorized users of the collaboration program.
- the collaboration program also provides a user interface and associated functionality for managing activities that occur following a meeting.
- the collaboration program provides functionality for creating a summary that includes information that summarizes the meeting.
- the meeting agenda and notes created by any of the meeting participants may be added to the summary.
- Once the summary has been created, it may be stored in the shared workspace for access and use by the meeting participants and other authorized users of the collaboration program that did not participate in the meeting.
- the summary may also be transmitted to other users, including users who are not members of the workspace or who did not participate in the meeting, via e-mail or another communication mechanism.
- FIG. 1 is a network diagram showing aspects of an illustrative operating environment and several software components provided by the embodiments presented herein;
- FIG. 2 is a software architecture diagram showing aspects of a shared workspace utilized in embodiments presented herein;
- FIG. 3 is a flow diagram showing an illustrative routine for the collaborative management of pre-meeting activities according to one embodiment presented herein;
- FIGS. 4A-4B are user interface diagrams showing several illustrative user interfaces provided herein in embodiments for collaboratively creating and managing a meeting agenda;
- FIG. 5 is a flow diagram showing an illustrative routine provided herein in one embodiment for the collaborative management of meeting notes
- FIGS. 6A-6B are user interface diagrams showing several illustrative user interfaces provided herein in embodiments for collaboratively creating and managing meeting notes;
- FIG. 7 is a flow diagram showing an illustrative routine provided herein in one embodiment for the collaborative management of post-meeting activities
- FIGS. 8A-8B are user interface diagrams showing several user interfaces for collaboratively creating and managing meeting summaries in one embodiment presented herein;
- FIG. 9 is a computer architecture diagram showing an illustrative computer hardware and software architecture for a computing system capable of implementing aspects of the embodiments presented herein.
- FIG. 1 shows aspects of a system 100 for facilitating collaboration and communication among members of small groups.
- the system 100 illustrated in FIG. 1 includes several computers 102 A- 102 D that are connected to one another via a network 108 .
- each of the computers 102 A- 102 D may communicate with one another directly through the connections 110 A- 110 F.
- the computers 102 A- 102 D are described herein as being standard desktop computer systems, other types of computer devices may be utilized. For instance, communication appliances and other types of communication devices, including handheld and wireless devices may be utilized.
- the network 108 is described herein as being the Internet, virtually any other type of local area network, wide area network, or wireless network may be utilized to facilitate the communication described herein.
- each of the computers 102 A- 102 D is configured to execute a collaboration program 104 .
- the collaboration program 104 is an executable computer program designed to facilitate collaboration and communication among members of small groups.
- a shared workspace 106 can be created.
- the shared workspace 106 may be utilized to store documents, content, and other information and to share this information among users of the computers 102 A- 102 D.
- a user of the computer 102 A may create the shared workspace 106 through the collaboration program 104 .
- the user of computer 102 A may then invite users of the computers 102 B- 102 D to join the shared workspace 106 .
- Each user that responds to an invitation to become an active member of the shared workspace 106 is sent a copy of the workspace 106 that is installed onto their respective computers 102 B- 102 D.
- all of the data that is transmitted between the computers 102 A- 102 D to synchronize the contents of the shared workspace is encrypted.
- the shared workspace 106 may also be encrypted on the mass storage device of the computers 102 A- 102 D. It should be appreciated that by storing a local copy of the shared workspace on each of the computers 102 A- 102 D, users of the computers 102 A- 102 D are never disconnected from the shared data.
- one of the computers 102 A- 102 D may comprise a portable computer system. In this embodiment, if the portable computer system is taken offline from the network 108 , the shared workspace 106 will remain on the portable computer system for access by the user.
- any modifications to the shared workspace 106 while the portable computer system is offline will be synchronized to the other computers when the portable computer is returned to the online state.
- the collaboration program 104 ensures that the shared workspace 106 stored in each of the computers 102 A- 102 D are continually synchronized so that each member of the shared workspace 106 has access to the same data as the other members.
- the changed data in a shared workspace 106 is transmitted to the other computers by transmitting only the changes to the shared workspace 106 .
- One methodology for transmitting only the changes to a shared workspace is described in U.S. Patent Publication No. US2007/0255787 entitled “Method and Apparatus for Maintaining Consistency of the Shared Space Across Multiple Endpoints in a Peer-to-Peer Collaborative Computer System”, which was filed on Jun. 22, 2007, is assigned to the assignee of the instant patent application, and which is expressly incorporated herein by reference in its entirety.
- any one member of a shared workspace 106 makes a change to the shared workspace 106 , that change is sent to all of the other members. If a member is offline and not connected to the network 108 at the time the change is made, the change is queued and synchronized to other workspace members. When the offline member comes back online, that user's copy of the shared workspace 106 is updated.
- the topology illustrated in FIG. 1 is a peer-to-peer topology, other embodiments may be utilized that include a server computer that assists in the synchronization of the shared workspace 106 between the computers 102 A- 102 D.
- the collaboration program 104 comprises the GROOVE collaboration program from MICROSOFT CORPORATION of Redmond, Wash., other collaboration programs from other vendors may be utilized to implement the concepts and technologies presented herein.
- the collaboration program 104 also includes functionality for enabling geographically distributed individuals and/or cross organizational individuals the ability to participate in the full lifecycle of a meeting.
- the collaboration program 104 provides capabilities for meeting setup, scheduling and preparation, collaboration, creation, distribution, and organization of an agenda for a meeting, capabilities for interfacing real-time desktop sharing tools during a meeting, allowing the multi-participant creation of meeting notes, and functionality for creating a meeting summary and distributing the summary to others. Additional details regarding this functionality will be provided below with respect to FIGS. 2-9 .
- the shared workspace 106 is a local or distributed storage location for storing documents 202 and other content 204 .
- the term document refers to files associated with textual and/or graphics data, such as word processing documents, spreadsheet documents, and the like.
- Content refers to any form of data that can be a part of a shared workspace 106 , including audio data, video data, images, graphics, and so on. It should be understood that the terms content and document may be used interchangeably herein, and that any type of data may be stored within the shared workspace 106 and synchronized among the members of the shared workspace 106 .
- the collaboration program 104 includes functionality for scheduling and holding meetings.
- the collaboration program 104 includes calendaring functionality for scheduling meetings with other users of the collaboration program 104 . This calendaring functionality may be utilized to schedule a meeting at a time when the requested meeting participants are available for such a meeting.
- a meeting entry 206 is created within the shared workspace 106 .
- the meeting entry 206 may include a meeting agenda 208 , meeting notes 210 , and one or more meeting summaries 212 .
- the meeting agenda 208 includes a number of agenda items identifying the speakers and other information about the format of the meeting.
- the meeting notes 210 include text and other information, such as meeting minutes, that relate to the meeting.
- the meeting summary 212 includes a summary of the meeting and is typically generated following the meeting.
- the meeting entry 206 is synchronized to each of the members of the shared workspace 106 .
- the other members of the shared workspace 106 may then utilize the collaboration program 104 to modify the meeting agenda 208 , the meeting notes 210 , or the meeting summary 212 . These subsequent changes are then synchronized to the other members of the shared workspace 106 . Additional details regarding the functionality provided by the collaboration program 104 for creating and managing the meeting agenda 208 , the meeting notes 210 , and the meeting summary 212 are provided below with respect to FIGS. 3-9 .
- FIG. 3 is a flow diagram showing an illustrative routine for the collaborative management of pre-meeting activities according to one embodiment presented herein.
- the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules.
- the routine 300 begins at operation 302 , where the collaboration program 104 is utilized to schedule a meeting.
- the collaboration program 104 provides shared calendaring functionality for scheduling a meeting among members of the shared workspace 106 . Any member of the shared workspace 106 can create a meeting in the calendar provided by the collaboration program 104 .
- a user may be presented with a user interface form allowing entry of the meeting subject, location, date, and time, including time zone information. The user may also be permitted to indicate that the meeting reoccurs on a specified schedule.
- the collaboration program 104 operates in conjunction with a personal information manager program to provide the calendaring functionality described above.
- all members of the shared workspace 106 may be permitted to contribute to the multiple phases of the meeting whether they are online or offline. Details regarding participation by members of the shared workspace 106 in pre-meeting activities are described with respect to FIG. 3 . Activities performed during a meeting are described below with respect to FIG. 5 , and activities occurring following a meeting are described below with respect to FIG. 7 . It should be appreciated that users may contribute meeting data prior to the meeting, during a meeting, and after a meeting both synchronously and asynchronously, and such data is synchronized to other members of the shared workspace 106 .
- routine 300 continues from operation 302 to operation 304 , where the meeting entry 206 is created. Once the meeting entry 206 has been created, the routine 300 continues from operation 304 to operation 306 , where the collaboration program 104 synchronizes the meeting entry 206 to the other members of the shared workspace 106 . It should be appreciated that any member of the shared workspace 106 may modify the meeting entry 206 .
- a meeting agenda provides a schedule for the meeting and may include one or more meeting items that identify a presenter, a topic to be presented, and any associated details. Supporting data in the form of file attachments may also be attached to agenda items. Members of the shared workspace 106 can view and modify the agenda items created by other members and reorder the agenda items to fit into the desired flow of the meeting.
- An illustrative user interface for creating the meeting agenda 208 and the agenda items is discussed below with reference to FIGS. 4A-4B .
- the meeting agenda 208 is synchronized to the other members of the shared workspace 106 at operation 310 .
- the routine 300 then continues to operation 312 where a determination is made as to whether any changes have been made to the meeting agenda 208 . If changes have been made to the meeting agenda 208 , these changes are synchronized to other members of the shared workspace 106 at operation 310 . As discussed above, if any members of the shared workspace 106 are offline, changes to the meeting agenda 208 will be synchronized when they return to an online state. It should be appreciated that changes may also be made to the meeting entry 206 and synchronized to the other members of the workspace. For instance, the subject, location, description, start date, end date, and recurrence information contained in the meeting entry 206 may be modified and synchronized to members of the shared workspace 106 .
- the user interface 400 includes an agenda items pane 402 and an agenda item detail pane 406 .
- the agenda items pane 402 shows a number of agenda items 404 A- 404 C. For each of the agenda items 404 A- 404 C, a meeting topic, the duration that the presenter will spend on the topic, and the name of the presenter are identified.
- the user interface button 408 A may be utilized to create a new agenda item 404 . Additional details regarding the creation of a new agenda item will be provided below with respect to FIG. 4B .
- the user interface control 408 B may be used to edit one of the agenda items 404 A- 404 C
- the user interface control 408 C may be used to delete one of the agenda items 404 A- 404 C
- the user interface controls 408 D- 408 E may be utilized to modify the order of the agenda items 404 A- 404 C.
- the user interface control 408 F may be utilized to mark the agenda items 404 A- 404 C as having been read or unread.
- the agenda item detail pane 406 shows the details for a selected one of the agenda items 404 A- 404 C.
- the agenda item 404 A has been selected thereby, showing details of this agenda item in the agenda item detail pane 406 .
- the agenda item detail pane 406 shows that the presenter is named Jim Smith, the details of the meeting, and any attachments that have been added to the agenda item 404 A.
- documents and other types of content may be added to an agenda item 404 .
- Selection of another one of the agenda items 404 A- 404 C will cause the details for the selected agenda item to be displayed in the agenda item detail pane 406 .
- the user interface shown in FIG. 4A is merely illustrative and that other types of user interfaces, user interfaces controls, and information regarding a meeting agenda 208 and agenda items may be displayed.
- the user interface 450 shown in FIG. 4B includes the fields 410 A- 410 E.
- the field 410 A may be utilize to specify a topic for the new agenda item
- the field 410 B may be utilized to specify the presenter for the new agenda item
- the field 410 C may be utilized to specify the number of minutes that have been allocated to the new agenda item.
- the field 410 D may be utilized to specify details of the agenda item.
- the field 410 E is utilized to identify attachments that have been added to the new agenda item.
- the user interface button 408 G may be utilized to save the new agenda item.
- the user interface button 408 H may be utilized to cancel the creation of the new agenda item.
- the user interface control 4081 may be utilized to add an attachment to the new agenda item.
- an illustrative routine 500 will be described illustrating aspects of the collaboration program 104 for collaboratively managing activities occurring during a meeting.
- the collaboration program 104 may operate in conjunction with an online meeting application to provide real-time desktop sharing among the computers 102 A- 102 D during a meeting.
- Additional functionality that may be provided by the collaboration program 104 during a meeting includes functionality for collaboratively creating meeting notes 210 .
- the routine 500 illustrates one process provided herein for collaboratively creating the meeting notes 210 and synchronizing the meeting notes among the meeting participants.
- the routine 500 begins at operation 502 , where one of the members of the shared workspace creates the meeting notes 210 . It should be appreciated that any or all of the members of the shared workspace 106 may create their own meeting notes, which are then synchronized to the other members of the shared workspace 106 . Once the meeting notes have been created, the routine 500 continues to operation 504 where the meeting notes 210 are synchronized to other members of the shared workspace 106 .
- routine 500 continues to operation 506 , where the collaboration program 104 determines whether there have been any changes to the meeting notes 210 . If the meeting notes have been changed, the routine 500 returns to operation 504 where the updated meeting notes 210 are synchronized to the shared workspace 106 of all of the meeting participants. In this manner, any changes to the meeting notes by one of the members of the shared workspace are synchronized to the other members.
- An illustrative user interface will be described below with reference to FIGS. 6A-6B for creating meeting notes in one embodiment presented herein.
- the illustrative user interface 600 includes a meeting notes pane 602 .
- the meeting notes pane 602 identifies one or more meeting notes items 604 A- 604 B created by the various members of the shared workspace 106 .
- the user interface 600 also includes a meeting notes detail pane 606 which shows the details of a selected one of the meeting notes items 604 A- 604 B.
- the meeting notes item 604 B has been selected, thereby displaying its details in the meeting notes detail pane 606 .
- the user interface 600 also includes a user interface button 608 A for creating new meeting notes, a user interface 608 B for editing an existing set of meeting notes, and a user interface button 608 C for deleting one of the meeting notes. Additional details regarding the creation of new meeting notes will be described below with reference to FIG. 6B .
- FIG. 6B an illustrative user interface 650 provided by the collaboration program 104 will be described for creating new meeting notes.
- the user interface 650 is displayed by the collaboration program 104 in response to the selection of the user interface button 608 A.
- the user interface 650 includes the fields 652 A- 652 B.
- the field 652 A is utilized to specify a title for the meeting notes.
- the field 652 B is utilized to input the actual meeting notes.
- an option may be provided for allowing a user to view the meeting agenda 208 while taking meeting notes. In this manner, a user can reference the agenda as the meeting proceeds and while taking meeting notes.
- An option may also be provided for attaching the meeting agenda 208 to the newly created meeting notes 210 .
- the meeting agenda 208 has been added to the new meeting notes.
- the user interface 650 shown in FIG. 6B may be utilized by a member of the shared workspace 106 to create notes for a meeting during the actual meeting itself. The meeting notes 210 are then synchronized to the other members of the shared workspace 106 . If the user would like to save the meeting notes, they may select the user interface control 654 A. If the user desires to cancel the creation of the new meeting notes, the user may select the user interface control 654 B.
- the collaboration program 104 is operative to provide a user interface and associated functionality for creating a meeting summary 212 .
- the meeting 212 provides information summarizing a meeting and may include the meeting agenda 208 and any meeting notes 210 taken by the meeting participants.
- the routine 700 begins at operation 702 , where a user utilizes the collaboration program 104 to create the meeting summary 212 .
- An illustrative user interface will be provided below with respect to FIGS. 8A-8B for creating the meeting summary 212 .
- the routine 700 continues to operation 704 where the meeting summary 212 is stored in the shared workspace 106 .
- the shared workspace 106 is also synchronized to the members of the shared workspace 106 at operation 704 .
- the routine 700 continues to operation 706 , where the collaboration program 104 determines whether any changes have been made to the meeting summary 212 . If changes are detected, the routine 700 returns to operation 704 where the updated meeting summary is synchronized to the shared workspace 106 of each of the members of the shared workspace 106 .
- the collaboration program 104 also provides functionality for transmitting the meeting summary 212 to individuals that are not members of the shared workspace 106 .
- the collaboration program 104 includes functionality for sending the meeting summary 212 to any user via an electronic mail message. Other methods of communicating the meeting summary 212 to individuals that are not members of the shared workspace may also be utilized.
- the user interface 800 includes a meeting summary pane 802 .
- the meeting summary pane 802 includes one or more meeting summary items 804 that identify the summaries created by the various members of the shared workspace 106 .
- the user interface 800 also shows the meeting summary 212 .
- the meeting summary 212 identifies the title of the meeting, the date of the meeting, the location of the meeting, and the meeting organizer. Other data regarding the meeting may also be included in the meeting summary 212 .
- options may be provided to a user to include the meeting agenda 208 in the meeting summary 212 .
- An option may also be provided to include the meeting notes 210 prepared by one or more of the meeting participants in the meeting summary 212 . Additional details regarding user interfaces for providing this functionality will be described below with respect to FIG. 8B .
- the user interface 800 also includes the user interface buttons 806 A- 806 E.
- the user interface control 806 A may be selected to create a new meeting summary 212
- the user interface control 806 B may be utilized to edit an existing meeting summary 212
- the user interface control 806 C may be utilized to delete an existing meeting summary 212 .
- the user interface button 806 D provides functionality for sending the meeting summary 212 to a user that is not a member of the shared workspace 106 in the manner described above.
- the user interface button 806 E may be used to mark a meeting summary as having been read or unread.
- the user interface 850 is displayed following the selection of the user interface control 806 A shown in FIG. 8A and described above. In response to such a selection, the user interface 850 is displayed.
- the user interface 850 includes user interface controls 854 A- 854 G and a field 852 .
- the field 852 may be utilized to specify a title for the meeting summary 212 .
- the user interface control 854 A will cause the meeting agenda 208 to be included in the meeting summary 212 .
- the user interface controls 854 B- 854 C may be selected to cause either agenda highlights or a detailed agenda, respectively, to be placed within the meeting summary 212 .
- the meeting notes 210 may also be included in the meeting summary 212 through a selection of the user interface control 854 D. Once selected, the user interface controls 854 E- 854 G may also be selected to cause meeting notes 210 prepared by various meeting participants to be included in the meeting summary 212 .
- the collaboration program 104 is configured to generate the meeting summary 212 based on the specified options. If a user has requested that the meeting summary 212 be transmitted to an individual that is not a member of the shared workspace 106 , the collaboration program 104 will cause this to occur.
- the meeting summary 212 is also stored in the shared workspace 106 and synchronized to the other members of the shared workspace.
- the collaboration program 104 allows any member of the shared workspace 106 to create and make modifications to any meeting agenda 208 , meeting notes 210 , or meeting summary 212 . Any changes to these items are synchronized by the collaboration program 104 to all members of the shared workspace 106 .
- a permission model may also be provided in embodiments that allows a manager of the shared workspace 106 to control the manner in which the members of the shared workspace 106 are allowed to create, modify, and delete the meeting agenda 208 , the meeting notes 210 , and the meeting summary 212 . For instance, a manager may specify that members of the shared workspace 106 be allowed only to modify items that they created, or may specify that members of the shared workspace 106 be permitted to modify any of the items described herein.
- This permission model may be applied to any data that can be created and stored in the shared workspace 106 , such as the meeting entry 206 .
- FIG. 9 shows an illustrative computer architecture for a computer 102 capable of executing the software components described herein for collaborative management of activities occurring during the lifecycle of a meeting in the manner presented above.
- the computer architecture shown in FIG. 9 illustrates a conventional desktop, laptop, or server computer and may be utilized to execute any aspects of the software components presented herein described as executing on the computers 102 A- 102 D shown in FIG. 1 and described above.
- the computer architecture shown in FIG. 9 includes a central processing unit 902 (“CPU”), a system memory 908 , including a random access memory 914 (“RAM”) and a read-only memory (“ROM”) 916 , and a system bus 904 that couples the memory to the CPU 902 .
- the computer 102 further includes a mass storage device 910 for storing an operating system 918 , application programs, and other program modules, which are described in greater detail herein.
- the mass storage device 910 is connected to the CPU 902 through a mass storage controller (not shown) connected to the bus 904 .
- the mass storage device 910 and its associated computer-readable media provide non-volatile storage for the computer 102 .
- computer-readable media can be any available computer storage media that can be accessed by the computer 102 .
- computer-readable media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data.
- computer-readable media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer 102 .
- the computer 102 may operate in a networked environment using logical connections to remote computers through a network such as the network 108 .
- the computer 102 may connect to the network 108 through a network interface unit 906 connected to the bus 904 . It should be appreciated that the network interface unit 906 may also be utilized to connect to other types of networks and remote computer systems.
- the computer 102 may also include an input/output controller 912 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown in FIG. 9 ). Similarly, an input/output controller may provide output to a display screen, a printer, or other type of output device (also not shown in FIG. 9 ).
- a number of program modules and data files may be stored in the mass storage device 910 and RAM 914 of the computer 102 , including an operating system 918 suitable for controlling the operation of a networked desktop, laptop, or server computer.
- the mass storage device 910 and RAM 914 may also store one or more program modules.
- the mass storage device 910 and the RAM 914 may store the collaboration program 104 , the shared workspace 106 , the online meeting application 920 , and the personal information manager 922 .
- the collaboration program 104 may utilize features of the online meeting application 920 to enable real-time desktop sharing and may integrate with calendaring features provided by the personal information manager 922 . Details regarding other aspects of the operation of the collaboration program 104 and the shared workspace 106 were described in detail above with respect to FIGS. 1-8B .
- the mass storage device 910 and the RAM 914 may also store other types of program modules.
Abstract
Description
- Many types of software tools exist that allow for the scheduling of meetings. For instance, many personal information manager programs provide calendaring functionality. Through this functionality, a user can create meetings on a calendar, invite other users to the meeting, and schedule time on the calendars of the other users for the meeting. Meeting invitees can accept, decline, or suggest a new time for the meeting.
- While current software tools provide a great deal of functionality for scheduling meetings, these tools provide little if any functionality for managing activities that occur during the entire lifecycle of a meeting. The lifecycle of a meeting refers to the time prior to the meeting, during the meeting, and after the meeting. For instance, using current software tools, a user may create a meeting agenda prior to a meeting that identifies one or more topics for the meeting. During the meeting, one or more users may take notes on the meeting. After the meeting, one or more users may create a summary of the meeting. Current software tools provide little if any functionality for managing these activities.
- Using current software tools, activities that occur during the lifecycle of a meeting are commonly performed independently by each of the meeting participants. This can result in significant duplication of effort by the meeting participants. For instance, two meeting participants may independently create an agenda or a summary for a meeting. Moreover, in order to collaborate on these activities, it is often necessary for the meeting participants to utilize electronic mail (“e-mail”) or another type of communication to transmit documents reflecting the meeting activities. For instance, a meeting participant may create a meeting agenda and e-mail the agenda to the other participants. The other participants may then modify the agenda and e-mail the modifications. This process can lead to large numbers of e-mail messages, to difficulty in incorporating the changes made by each participant, and even to confusion in identifying the most current version of a document. There is also currently no convenient way to store documents reflecting the activities occurring during the lifecycle of a meeting in a common location that is convenient for all meeting participants to access.
- It is with respect to these considerations and others that the disclosure made herein is presented.
- Technologies are described herein for collaborative management of activities occurring during the lifecycle of a meeting. In particular, a collaboration program is described herein that includes functionality for collaborative management of activities occurring during the entire lifecycle of a meeting. For instance, in one embodiment, meeting participants can collaborate on the creation of a meeting agenda prior to the occurrence of a meeting, can independently take and exchange meeting notes during a meeting, and can collaboratively generate a meeting summary following the meeting. Through the use of synchronization functionality provided by the collaboration program, the meeting agenda, meeting notes, and meeting summaries are synchronized to a shared workspace accessible to each of the meeting participants.
- According to one aspect presented herein, a collaboration program is provided that includes functionality for storing documents and other content in a shared workspace. A shared workspace is a local or distributed storage location for storing documents and other content. Through the collaboration program, the documents and other content in a shared workspace are made available to groups of users of the collaboration program for viewing and modification. For instance, a group of users may collectively utilize a shared workspace to collaborate on a project. The collaboration program also includes functionality for synchronizing changes made to documents or other content stored within the shared workspace to all of the members of a group.
- According to other aspects, the collaboration program includes functionality for collaborative management of activities occurring during the lifecycle of a meeting. For instance, in one embodiment, the collaboration program includes functionality for scheduling a meeting with other users of the collaboration program (referred to herein as “meeting participants”). Once a meeting has been scheduled, activities occurring prior to the meeting can be collaboratively managed through the use of functionality provided by the collaboration program. As an example, the collaboration program may provide a user interface and associated functionality for collaboratively creating an agenda for the meeting. The agenda may include one or more meeting items, and meeting participants may be permitted to create agenda items, edit agenda items, and delete agenda items. A presenter may also be assigned for each agenda item and the agenda items may also be placed in a desired order. Documents or other types of attachments may also be added to the agenda items. Once the agenda has been created, it may be synchronized to a shared workspace, thereby making it available to all of the meeting participants for viewing and modification.
- According to other aspects, the collaboration program also provides a user interface and associated functionality for managing activities that occur during a meeting. For instance, in one implementation, the collaboration program provides functionality for allowing meeting participants to take notes related to the meeting. Functionality may also be provided for adding an agenda for the meeting to the meeting notes. Once the notes have been created, they may also be stored in the shared workspace for access and use by other authorized users of the collaboration program.
- According to other aspects, the collaboration program also provides a user interface and associated functionality for managing activities that occur following a meeting. For instance, in one embodiment the collaboration program provides functionality for creating a summary that includes information that summarizes the meeting. The meeting agenda and notes created by any of the meeting participants may be added to the summary. Once the summary has been created, it may be stored in the shared workspace for access and use by the meeting participants and other authorized users of the collaboration program that did not participate in the meeting. The summary may also be transmitted to other users, including users who are not members of the workspace or who did not participate in the meeting, via e-mail or another communication mechanism.
- It should be appreciated that the above-described subject matter may also be implemented as a computer-controlled apparatus, a computer process, a computing system, or as an article of manufacture such as a computer-readable medium. These and various other features will be apparent from a reading of the following Detailed Description and a review of the associated drawings.
- This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended that this Summary be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
-
FIG. 1 is a network diagram showing aspects of an illustrative operating environment and several software components provided by the embodiments presented herein; -
FIG. 2 is a software architecture diagram showing aspects of a shared workspace utilized in embodiments presented herein; -
FIG. 3 is a flow diagram showing an illustrative routine for the collaborative management of pre-meeting activities according to one embodiment presented herein; -
FIGS. 4A-4B are user interface diagrams showing several illustrative user interfaces provided herein in embodiments for collaboratively creating and managing a meeting agenda; -
FIG. 5 is a flow diagram showing an illustrative routine provided herein in one embodiment for the collaborative management of meeting notes; -
FIGS. 6A-6B are user interface diagrams showing several illustrative user interfaces provided herein in embodiments for collaboratively creating and managing meeting notes; -
FIG. 7 is a flow diagram showing an illustrative routine provided herein in one embodiment for the collaborative management of post-meeting activities; -
FIGS. 8A-8B are user interface diagrams showing several user interfaces for collaboratively creating and managing meeting summaries in one embodiment presented herein; and -
FIG. 9 is a computer architecture diagram showing an illustrative computer hardware and software architecture for a computing system capable of implementing aspects of the embodiments presented herein. - Technologies are described herein for collaborative management of activities occurring during the lifecycle of a meeting. While the subject matter described herein is presented in the general context of program modules that execute in conjunction with the execution of an operating system and application programs on a computer system, those skilled in the art will recognize that other implementations may be performed in combination with other types of program modules. Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the subject matter described herein may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
- In the following detailed description, references are made to the accompanying drawings that form a part hereof, and which are shown by way of illustration specific embodiments or examples. Referring now to the drawings, in which like numerals represent like elements through the several figures, aspects of technologies for collaborative management of activities occurring during the lifecycle of a meeting will be described.
- Turning now to
FIG. 1 , details will be provided regarding an illustrative operating environment and several software components provided by the embodiments presented herein. In particular,FIG. 1 shows aspects of asystem 100 for facilitating collaboration and communication among members of small groups. Thesystem 100 illustrated inFIG. 1 includesseveral computers 102A-102D that are connected to one another via anetwork 108. In particular, each of thecomputers 102A-102D may communicate with one another directly through theconnections 110A-110F. It should be appreciated that although thecomputers 102A-102D are described herein as being standard desktop computer systems, other types of computer devices may be utilized. For instance, communication appliances and other types of communication devices, including handheld and wireless devices may be utilized. Similarly, although thenetwork 108 is described herein as being the Internet, virtually any other type of local area network, wide area network, or wireless network may be utilized to facilitate the communication described herein. - As also illustrated in
FIG. 1 , each of thecomputers 102A-102D is configured to execute acollaboration program 104. Thecollaboration program 104 is an executable computer program designed to facilitate collaboration and communication among members of small groups. Through the use of thecollaboration program 104, a sharedworkspace 106 can be created. As will be described in greater detail below, the sharedworkspace 106 may be utilized to store documents, content, and other information and to share this information among users of thecomputers 102A-102D. For instance, a user of thecomputer 102A may create the sharedworkspace 106 through thecollaboration program 104. The user ofcomputer 102A may then invite users of thecomputers 102B-102D to join the sharedworkspace 106. Each user that responds to an invitation to become an active member of the sharedworkspace 106 is sent a copy of theworkspace 106 that is installed onto theirrespective computers 102B-102D. - According to embodiments, all of the data that is transmitted between the
computers 102A-102D to synchronize the contents of the shared workspace is encrypted. The sharedworkspace 106 may also be encrypted on the mass storage device of thecomputers 102A-102D. It should be appreciated that by storing a local copy of the shared workspace on each of thecomputers 102A-102D, users of thecomputers 102A-102D are never disconnected from the shared data. For instance, in one embodiment one of thecomputers 102A-102D may comprise a portable computer system. In this embodiment, if the portable computer system is taken offline from thenetwork 108, the sharedworkspace 106 will remain on the portable computer system for access by the user. Any modifications to the sharedworkspace 106 while the portable computer system is offline will be synchronized to the other computers when the portable computer is returned to the online state. In this manner, thecollaboration program 104 ensures that the sharedworkspace 106 stored in each of thecomputers 102A-102D are continually synchronized so that each member of the sharedworkspace 106 has access to the same data as the other members. - According to embodiments, the changed data in a shared
workspace 106 is transmitted to the other computers by transmitting only the changes to the sharedworkspace 106. One methodology for transmitting only the changes to a shared workspace is described in U.S. Patent Publication No. US2007/0255787 entitled “Method and Apparatus for Maintaining Consistency of the Shared Space Across Multiple Endpoints in a Peer-to-Peer Collaborative Computer System”, which was filed on Jun. 22, 2007, is assigned to the assignee of the instant patent application, and which is expressly incorporated herein by reference in its entirety. - As discussed briefly above, when any one member of a shared
workspace 106 makes a change to the sharedworkspace 106, that change is sent to all of the other members. If a member is offline and not connected to thenetwork 108 at the time the change is made, the change is queued and synchronized to other workspace members. When the offline member comes back online, that user's copy of the sharedworkspace 106 is updated. It should be appreciated that although the topology illustrated inFIG. 1 is a peer-to-peer topology, other embodiments may be utilized that include a server computer that assists in the synchronization of the sharedworkspace 106 between thecomputers 102A-102D. It should also be appreciated that while in one implementation thecollaboration program 104 comprises the GROOVE collaboration program from MICROSOFT CORPORATION of Redmond, Wash., other collaboration programs from other vendors may be utilized to implement the concepts and technologies presented herein. - As will be described in greater detail below, the
collaboration program 104 also includes functionality for enabling geographically distributed individuals and/or cross organizational individuals the ability to participate in the full lifecycle of a meeting. In this regard, thecollaboration program 104 provides capabilities for meeting setup, scheduling and preparation, collaboration, creation, distribution, and organization of an agenda for a meeting, capabilities for interfacing real-time desktop sharing tools during a meeting, allowing the multi-participant creation of meeting notes, and functionality for creating a meeting summary and distributing the summary to others. Additional details regarding this functionality will be provided below with respect toFIGS. 2-9 . - Referring now to
FIG. 2 , additional details regarding the sharedworkspace 106 will be described. As mentioned briefly above, the sharedworkspace 106 is a local or distributed storage location for storingdocuments 202 andother content 204. As used herein, the term document refers to files associated with textual and/or graphics data, such as word processing documents, spreadsheet documents, and the like. Content refers to any form of data that can be a part of a sharedworkspace 106, including audio data, video data, images, graphics, and so on. It should be understood that the terms content and document may be used interchangeably herein, and that any type of data may be stored within the sharedworkspace 106 and synchronized among the members of the sharedworkspace 106. - As also discussed briefly above, the
collaboration program 104 includes functionality for scheduling and holding meetings. In this regard, thecollaboration program 104 includes calendaring functionality for scheduling meetings with other users of thecollaboration program 104. This calendaring functionality may be utilized to schedule a meeting at a time when the requested meeting participants are available for such a meeting. When a meeting is created within thecollaboration program 104, ameeting entry 206 is created within the sharedworkspace 106. As shown inFIG. 2 , themeeting entry 206 may include ameeting agenda 208, meeting notes 210, and one ormore meeting summaries 212. As will be discussed in greater detail below, themeeting agenda 208 includes a number of agenda items identifying the speakers and other information about the format of the meeting. The meeting notes 210 include text and other information, such as meeting minutes, that relate to the meeting. Themeeting summary 212 includes a summary of the meeting and is typically generated following the meeting. - As will be described in greater detail below, when a
meeting entry 206 is created by thecollaboration program 104, themeeting entry 206 is synchronized to each of the members of the sharedworkspace 106. The other members of the sharedworkspace 106 may then utilize thecollaboration program 104 to modify themeeting agenda 208, the meeting notes 210, or themeeting summary 212. These subsequent changes are then synchronized to the other members of the sharedworkspace 106. Additional details regarding the functionality provided by thecollaboration program 104 for creating and managing themeeting agenda 208, the meeting notes 210, and themeeting summary 212 are provided below with respect toFIGS. 3-9 . - Referring now to
FIG. 3 , additional details will be provided regarding the embodiments presented herein for collaborative management of activities occurring during the lifecycle of a meeting. In particular,FIG. 3 is a flow diagram showing an illustrative routine for the collaborative management of pre-meeting activities according to one embodiment presented herein. It should be appreciated that the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof. It should also be appreciated that more or fewer operations may be performed than shown in the FIGURES and described herein. These operations may also be performed in a different order than those described herein. - The routine 300 begins at
operation 302, where thecollaboration program 104 is utilized to schedule a meeting. As discussed above, thecollaboration program 104 provides shared calendaring functionality for scheduling a meeting among members of the sharedworkspace 106. Any member of the sharedworkspace 106 can create a meeting in the calendar provided by thecollaboration program 104. In this regard, a user may be presented with a user interface form allowing entry of the meeting subject, location, date, and time, including time zone information. The user may also be permitted to indicate that the meeting reoccurs on a specified schedule. In one embodiment, thecollaboration program 104 operates in conjunction with a personal information manager program to provide the calendaring functionality described above. - Once the
collaboration program 104 has been utilized to create a meeting, all members of the sharedworkspace 106 may be permitted to contribute to the multiple phases of the meeting whether they are online or offline. Details regarding participation by members of the sharedworkspace 106 in pre-meeting activities are described with respect toFIG. 3 . Activities performed during a meeting are described below with respect toFIG. 5 , and activities occurring following a meeting are described below with respect toFIG. 7 . It should be appreciated that users may contribute meeting data prior to the meeting, during a meeting, and after a meeting both synchronously and asynchronously, and such data is synchronized to other members of the sharedworkspace 106. - Once a meeting has been scheduled, the routine 300 continues from
operation 302 tooperation 304, where themeeting entry 206 is created. Once themeeting entry 206 has been created, the routine 300 continues fromoperation 304 tooperation 306, where thecollaboration program 104 synchronizes themeeting entry 206 to the other members of the sharedworkspace 106. It should be appreciated that any member of the sharedworkspace 106 may modify themeeting entry 206. - From
operation 306, the routine 300 continues tooperation 308 where a user may utilize thecollaboration program 104 to create ameeting agenda 208. As discussed briefly above, a meeting agenda provides a schedule for the meeting and may include one or more meeting items that identify a presenter, a topic to be presented, and any associated details. Supporting data in the form of file attachments may also be attached to agenda items. Members of the sharedworkspace 106 can view and modify the agenda items created by other members and reorder the agenda items to fit into the desired flow of the meeting. An illustrative user interface for creating themeeting agenda 208 and the agenda items is discussed below with reference toFIGS. 4A-4B . - Once the
meeting agenda 208 has been created, themeeting agenda 208 is synchronized to the other members of the sharedworkspace 106 atoperation 310. The routine 300 then continues tooperation 312 where a determination is made as to whether any changes have been made to themeeting agenda 208. If changes have been made to themeeting agenda 208, these changes are synchronized to other members of the sharedworkspace 106 atoperation 310. As discussed above, if any members of the sharedworkspace 106 are offline, changes to themeeting agenda 208 will be synchronized when they return to an online state. It should be appreciated that changes may also be made to themeeting entry 206 and synchronized to the other members of the workspace. For instance, the subject, location, description, start date, end date, and recurrence information contained in themeeting entry 206 may be modified and synchronized to members of the sharedworkspace 106. - Turning now to
FIG. 4A , anillustrative user interface 400 provided by thecollaboration program 104 for creating ameeting agenda 208 will be described. As shown inFIG. 4A , theuser interface 400 includes anagenda items pane 402 and an agendaitem detail pane 406. Theagenda items pane 402 shows a number ofagenda items 404A-404C. For each of theagenda items 404A-404C, a meeting topic, the duration that the presenter will spend on the topic, and the name of the presenter are identified. - The
user interface button 408A may be utilized to create a new agenda item 404. Additional details regarding the creation of a new agenda item will be provided below with respect toFIG. 4B . Theuser interface control 408B may be used to edit one of theagenda items 404A-404C, theuser interface control 408C may be used to delete one of theagenda items 404A-404C, and the user interface controls 408D-408E may be utilized to modify the order of theagenda items 404A-404C. Theuser interface control 408F may be utilized to mark theagenda items 404A-404C as having been read or unread. - The agenda
item detail pane 406 shows the details for a selected one of theagenda items 404A-404C. In the example shown inFIG. 4A , theagenda item 404A has been selected thereby, showing details of this agenda item in the agendaitem detail pane 406. For instance, in the example shown inFIG. 4A , the agendaitem detail pane 406 shows that the presenter is named Jim Smith, the details of the meeting, and any attachments that have been added to theagenda item 404A. As discussed above, documents and other types of content may be added to an agenda item 404. Selection of another one of theagenda items 404A-404C will cause the details for the selected agenda item to be displayed in the agendaitem detail pane 406. It should be appreciated that the user interface shown inFIG. 4A is merely illustrative and that other types of user interfaces, user interfaces controls, and information regarding ameeting agenda 208 and agenda items may be displayed. - Referring now to
FIG. 4B , anillustrative user interface 450 presented by thecollaboration program 104 in response to the selection of theuser interface control 408A shown inFIG. 4A will be described. As discussed briefly above, selection of theuser interface control 408A will cause theuser interface 450 to be displayed for creating a new agenda item 404. Theuser interface 450 shown inFIG. 4B includes thefields 410A-410E. Thefield 410A may be utilize to specify a topic for the new agenda item, thefield 410B may be utilized to specify the presenter for the new agenda item, and thefield 410C may be utilized to specify the number of minutes that have been allocated to the new agenda item. Thefield 410D may be utilized to specify details of the agenda item. Thefield 410E is utilized to identify attachments that have been added to the new agenda item. When a user has completed creation of the new agenda item, theuser interface button 408G may be utilized to save the new agenda item. Alternately, theuser interface button 408H may be utilized to cancel the creation of the new agenda item. Theuser interface control 4081 may be utilized to add an attachment to the new agenda item. - Turning now to
FIG. 5 , anillustrative routine 500 will be described illustrating aspects of thecollaboration program 104 for collaboratively managing activities occurring during a meeting. As discussed above, thecollaboration program 104 may operate in conjunction with an online meeting application to provide real-time desktop sharing among thecomputers 102A-102D during a meeting. Additional functionality that may be provided by thecollaboration program 104 during a meeting includes functionality for collaboratively creating meeting notes 210. The routine 500 illustrates one process provided herein for collaboratively creating the meeting notes 210 and synchronizing the meeting notes among the meeting participants. - The routine 500 begins at
operation 502, where one of the members of the shared workspace creates the meeting notes 210. It should be appreciated that any or all of the members of the sharedworkspace 106 may create their own meeting notes, which are then synchronized to the other members of the sharedworkspace 106. Once the meeting notes have been created, the routine 500 continues tooperation 504 where the meeting notes 210 are synchronized to other members of the sharedworkspace 106. - From
operation 504, the routine 500 continues tooperation 506, where thecollaboration program 104 determines whether there have been any changes to the meeting notes 210. If the meeting notes have been changed, the routine 500 returns tooperation 504 where the updated meeting notes 210 are synchronized to the sharedworkspace 106 of all of the meeting participants. In this manner, any changes to the meeting notes by one of the members of the shared workspace are synchronized to the other members. An illustrative user interface will be described below with reference toFIGS. 6A-6B for creating meeting notes in one embodiment presented herein. - Referring now to
FIG. 6A , anillustrative user interface 600 provided by thecollaboration program 104 for the creating meeting notes 210 will be described. As shown inFIG. 6A , theillustrative user interface 600 includes a meeting notespane 602. The meeting notespane 602 identifies one or more meeting notesitems 604A-604B created by the various members of the sharedworkspace 106. Theuser interface 600 also includes a meeting notesdetail pane 606 which shows the details of a selected one of the meeting notesitems 604A-604B. In the example shown inFIG. 6A , the meeting notesitem 604B has been selected, thereby displaying its details in the meeting notesdetail pane 606. - The
user interface 600 also includes auser interface button 608A for creating new meeting notes, auser interface 608B for editing an existing set of meeting notes, and auser interface button 608C for deleting one of the meeting notes. Additional details regarding the creation of new meeting notes will be described below with reference toFIG. 6B . - Turning now to
FIG. 6B , anillustrative user interface 650 provided by thecollaboration program 104 will be described for creating new meeting notes. As discussed above with reference toFIG. 6A , theuser interface 650 is displayed by thecollaboration program 104 in response to the selection of theuser interface button 608A. As illustrated inFIG. 6B , theuser interface 650 includes thefields 652A-652B. Thefield 652A is utilized to specify a title for the meeting notes. Thefield 652B is utilized to input the actual meeting notes. - It should be appreciated that, according to embodiments, an option may be provided for allowing a user to view the
meeting agenda 208 while taking meeting notes. In this manner, a user can reference the agenda as the meeting proceeds and while taking meeting notes. An option may also be provided for attaching themeeting agenda 208 to the newly created meeting notes 210. In the example shown inFIG. 6B , themeeting agenda 208 has been added to the new meeting notes. It should be appreciated that theuser interface 650 shown inFIG. 6B may be utilized by a member of the sharedworkspace 106 to create notes for a meeting during the actual meeting itself. The meeting notes 210 are then synchronized to the other members of the sharedworkspace 106. If the user would like to save the meeting notes, they may select theuser interface control 654A. If the user desires to cancel the creation of the new meeting notes, the user may select theuser interface control 654B. - Turning now to
FIG. 7 , anillustrative routine 700 will be described illustrating aspects of thecollaboration program 104 for managing post-meeting activities. In particular, according to one implementation, thecollaboration program 104 is operative to provide a user interface and associated functionality for creating ameeting summary 212. As discussed briefly above, themeeting 212 provides information summarizing a meeting and may include themeeting agenda 208 and any meeting notes 210 taken by the meeting participants. - The routine 700 begins at
operation 702, where a user utilizes thecollaboration program 104 to create themeeting summary 212. An illustrative user interface will be provided below with respect toFIGS. 8A-8B for creating themeeting summary 212. Once themeeting summary 212 has been created, the routine 700 continues tooperation 704 where themeeting summary 212 is stored in the sharedworkspace 106. The sharedworkspace 106 is also synchronized to the members of the sharedworkspace 106 atoperation 704. - From
operation 704, the routine 700 continues tooperation 706, where thecollaboration program 104 determines whether any changes have been made to themeeting summary 212. If changes are detected, the routine 700 returns tooperation 704 where the updated meeting summary is synchronized to the sharedworkspace 106 of each of the members of the sharedworkspace 106. It should be appreciated that, according to embodiments, thecollaboration program 104 also provides functionality for transmitting themeeting summary 212 to individuals that are not members of the sharedworkspace 106. For instance, in one implementation, thecollaboration program 104 includes functionality for sending themeeting summary 212 to any user via an electronic mail message. Other methods of communicating themeeting summary 212 to individuals that are not members of the shared workspace may also be utilized. - Referring now to
FIG. 8A , anillustrative user interface 800 provided by thecollaboration program 104 for creating ameeting summary 212 will be described. As shown inFIG. 8A , theuser interface 800 includes a meeting summary pane 802. The meeting summary pane 802 includes one or moremeeting summary items 804 that identify the summaries created by the various members of the sharedworkspace 106. Theuser interface 800 also shows themeeting summary 212. As shown inFIG. 8A , themeeting summary 212 identifies the title of the meeting, the date of the meeting, the location of the meeting, and the meeting organizer. Other data regarding the meeting may also be included in themeeting summary 212. - According to implementations, options may be provided to a user to include the
meeting agenda 208 in themeeting summary 212. An option may also be provided to include the meeting notes 210 prepared by one or more of the meeting participants in themeeting summary 212. Additional details regarding user interfaces for providing this functionality will be described below with respect toFIG. 8B . - As also shown in
FIG. 8A , theuser interface 800 also includes theuser interface buttons 806A-806E. Theuser interface control 806A may be selected to create anew meeting summary 212, theuser interface control 806B may be utilized to edit an existingmeeting summary 212, and theuser interface control 806C may be utilized to delete an existingmeeting summary 212. Theuser interface button 806D provides functionality for sending themeeting summary 212 to a user that is not a member of the sharedworkspace 106 in the manner described above. Theuser interface button 806E may be used to mark a meeting summary as having been read or unread. - Referring now to
FIG. 8B , anillustrative user interface 850 provided by thecollaboration program 104 will be described. Theuser interface 850 is displayed following the selection of theuser interface control 806A shown inFIG. 8A and described above. In response to such a selection, theuser interface 850 is displayed. Theuser interface 850 includes user interface controls 854A-854G and afield 852. Thefield 852 may be utilized to specify a title for themeeting summary 212. When selected, theuser interface control 854A will cause themeeting agenda 208 to be included in themeeting summary 212. The user interface controls 854B-854C may be selected to cause either agenda highlights or a detailed agenda, respectively, to be placed within themeeting summary 212. - According to implementations, the meeting notes 210 may also be included in the
meeting summary 212 through a selection of theuser interface control 854D. Once selected, the user interface controls 854E-854G may also be selected to cause meeting notes 210 prepared by various meeting participants to be included in themeeting summary 212. - Once a user has completed the contents of the
user interface 850, thecollaboration program 104 is configured to generate themeeting summary 212 based on the specified options. If a user has requested that themeeting summary 212 be transmitted to an individual that is not a member of the sharedworkspace 106, thecollaboration program 104 will cause this to occur. Themeeting summary 212 is also stored in the sharedworkspace 106 and synchronized to the other members of the shared workspace. - It should be appreciated that, according to embodiments, the
collaboration program 104 allows any member of the sharedworkspace 106 to create and make modifications to anymeeting agenda 208, meeting notes 210, or meetingsummary 212. Any changes to these items are synchronized by thecollaboration program 104 to all members of the sharedworkspace 106. A permission model may also be provided in embodiments that allows a manager of the sharedworkspace 106 to control the manner in which the members of the sharedworkspace 106 are allowed to create, modify, and delete themeeting agenda 208, the meeting notes 210, and themeeting summary 212. For instance, a manager may specify that members of the sharedworkspace 106 be allowed only to modify items that they created, or may specify that members of the sharedworkspace 106 be permitted to modify any of the items described herein. This permission model may be applied to any data that can be created and stored in the sharedworkspace 106, such as themeeting entry 206. -
FIG. 9 shows an illustrative computer architecture for acomputer 102 capable of executing the software components described herein for collaborative management of activities occurring during the lifecycle of a meeting in the manner presented above. The computer architecture shown inFIG. 9 illustrates a conventional desktop, laptop, or server computer and may be utilized to execute any aspects of the software components presented herein described as executing on thecomputers 102A-102D shown inFIG. 1 and described above. - The computer architecture shown in
FIG. 9 includes a central processing unit 902 (“CPU”), asystem memory 908, including a random access memory 914 (“RAM”) and a read-only memory (“ROM”) 916, and asystem bus 904 that couples the memory to theCPU 902. A basic input/output system containing the basic routines that help to transfer information between elements within thecomputer 102, such as during startup, is stored in theROM 916. Thecomputer 102 further includes amass storage device 910 for storing anoperating system 918, application programs, and other program modules, which are described in greater detail herein. - The
mass storage device 910 is connected to theCPU 902 through a mass storage controller (not shown) connected to thebus 904. Themass storage device 910 and its associated computer-readable media provide non-volatile storage for thecomputer 102. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable media can be any available computer storage media that can be accessed by thecomputer 102. - By way of example, and not limitation, computer-readable media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. For example, computer-readable media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the
computer 102. - According to various embodiments, the
computer 102 may operate in a networked environment using logical connections to remote computers through a network such as thenetwork 108. Thecomputer 102 may connect to thenetwork 108 through anetwork interface unit 906 connected to thebus 904. It should be appreciated that thenetwork interface unit 906 may also be utilized to connect to other types of networks and remote computer systems. Thecomputer 102 may also include an input/output controller 912 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown inFIG. 9 ). Similarly, an input/output controller may provide output to a display screen, a printer, or other type of output device (also not shown inFIG. 9 ). - As mentioned briefly above, a number of program modules and data files may be stored in the
mass storage device 910 andRAM 914 of thecomputer 102, including anoperating system 918 suitable for controlling the operation of a networked desktop, laptop, or server computer. Themass storage device 910 andRAM 914 may also store one or more program modules. In particular, themass storage device 910 and theRAM 914 may store thecollaboration program 104, the sharedworkspace 106, theonline meeting application 920, and thepersonal information manager 922. As discussed briefly above, thecollaboration program 104 may utilize features of theonline meeting application 920 to enable real-time desktop sharing and may integrate with calendaring features provided by thepersonal information manager 922. Details regarding other aspects of the operation of thecollaboration program 104 and the sharedworkspace 106 were described in detail above with respect toFIGS. 1-8B . Themass storage device 910 and theRAM 914 may also store other types of program modules. - Based on the foregoing, it should be appreciated that technologies for collaborative management of activities occurring during the lifecycle of a meeting are provided herein. Although the subject matter presented herein has been described in language specific to computer structural features, methodological acts, and computer readable media, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features, acts, or media described herein. Rather, the specific features, acts and mediums are disclosed as example forms of implementing the claims.
- The subject matter described above is provided by way of illustration only and should not be construed as limiting. Various modifications and changes may be made to the subject matter described herein without following the example embodiments and applications illustrated and described, and without departing from the true spirit and scope of the present invention, which is set forth in the following claims.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/039,789 US9824333B2 (en) | 2008-02-29 | 2008-02-29 | Collaborative management of activities occurring during the lifecycle of a meeting |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/039,789 US9824333B2 (en) | 2008-02-29 | 2008-02-29 | Collaborative management of activities occurring during the lifecycle of a meeting |
Publications (2)
Publication Number | Publication Date |
---|---|
US20090222741A1 true US20090222741A1 (en) | 2009-09-03 |
US9824333B2 US9824333B2 (en) | 2017-11-21 |
Family
ID=41014144
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/039,789 Active 2032-08-23 US9824333B2 (en) | 2008-02-29 | 2008-02-29 | Collaborative management of activities occurring during the lifecycle of a meeting |
Country Status (1)
Country | Link |
---|---|
US (1) | US9824333B2 (en) |
Cited By (55)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080052358A1 (en) * | 1999-05-07 | 2008-02-28 | Agility Management Partners, Inc. | System for performing collaborative tasks |
US20100169435A1 (en) * | 2008-12-31 | 2010-07-01 | O'sullivan Patrick Joseph | System and method for joining a conversation |
US20100235216A1 (en) * | 2009-03-16 | 2010-09-16 | Microsoft Corporation | Integration of pre-meeting and post-meeting experience into a meeting lifecycle |
US20110191672A1 (en) * | 2010-02-02 | 2011-08-04 | Think-Cell Software Gmbh | Method, computer readable storage medium and computer system for efficient agenda drafting, synchronization and display |
GB2477762A (en) * | 2010-02-11 | 2011-08-17 | Thales Holdings Uk Plc | Collaborative working environment with defined subgroup of users. |
US20110231409A1 (en) * | 2010-03-19 | 2011-09-22 | Avaya Inc. | System and method for predicting meeting subjects, logistics, and resources |
US20110307555A1 (en) * | 2008-06-27 | 2011-12-15 | Microsoft Corporation | Synchronization and Collaboration Within Peer-to-Peer and Client/Server Environments |
US20120036451A1 (en) * | 2010-08-09 | 2012-02-09 | Hon Hai Precision Industry Co., Ltd. | Electronic device and method for facilitating recording meeting contents |
US20120054639A1 (en) * | 2010-08-27 | 2012-03-01 | Business Objects Software Limited | Intelligent workspace |
US20120131104A1 (en) * | 1999-05-07 | 2012-05-24 | Virtualagility Inc. | System and method for supporting collaborative activity |
US20120150577A1 (en) * | 2010-12-14 | 2012-06-14 | Microsoft Corporation | Meeting lifecycle management |
US20130007635A1 (en) * | 2011-06-30 | 2013-01-03 | Avaya Inc. | Teleconferencing adjunct and user interface to support temporary topic-based exclusions of specific participants |
US20130191719A1 (en) * | 2012-01-19 | 2013-07-25 | Microsoft Corporation | Notebook driven accumulation of meeting documentation and notations |
US20130332804A1 (en) * | 2012-06-06 | 2013-12-12 | Conrad Delbert Seaman | Methods and devices for data entry |
US20140006500A1 (en) * | 2012-06-29 | 2014-01-02 | Adobe Systems Incorporated | Interactive broadcasting between devices |
US8682973B2 (en) | 2011-10-05 | 2014-03-25 | Microsoft Corporation | Multi-user and multi-device collaboration |
US20140325231A1 (en) * | 2010-03-09 | 2014-10-30 | Lock Box Pty Ltd. | Method and system for sharing encrypted content |
US20150213410A1 (en) * | 2014-01-24 | 2015-07-30 | T Minus 5 Llc | Meeting Management |
US9118612B2 (en) | 2010-12-15 | 2015-08-25 | Microsoft Technology Licensing, Llc | Meeting-specific state indicators |
EP2916495A1 (en) * | 2014-03-04 | 2015-09-09 | Ricoh Company, Ltd. | Information processing system, an information processing apparatus and a medium storing an information processing program |
US9383888B2 (en) | 2010-12-15 | 2016-07-05 | Microsoft Technology Licensing, Llc | Optimized joint document review |
US20160291856A1 (en) * | 2015-04-01 | 2016-10-06 | Dropbox, Inc. | Shared Workspaces with Selective Content Item Synchronization |
US9473449B2 (en) | 2011-02-10 | 2016-10-18 | Jeffrey J. Ausfeld | Multi-platform collaboration appliance |
US9508056B2 (en) | 2012-03-19 | 2016-11-29 | Microsoft Technology Licensing, Llc | Electronic note taking features including blank note triggers |
US9544158B2 (en) | 2011-10-05 | 2017-01-10 | Microsoft Technology Licensing, Llc | Workspace collaboration via a wall-type computing device |
WO2017105972A1 (en) * | 2015-12-16 | 2017-06-22 | Microsoft Technology Licensing, Llc | Creating notes related to communications |
US9705689B1 (en) | 2011-06-16 | 2017-07-11 | Google Inc. | Integrated calendar callback feature for inviting to communication session |
US9720574B2 (en) | 2012-03-19 | 2017-08-01 | Microsoft Technology Licensing, Llc | Personal notes on a calendar item |
EP3186958A4 (en) * | 2014-08-25 | 2017-08-23 | Ricoh Company, Ltd. | Conference management apparatus, document registration method, program, and conference system |
US9864612B2 (en) | 2010-12-23 | 2018-01-09 | Microsoft Technology Licensing, Llc | Techniques to customize a user interface for different displays |
US9883003B2 (en) | 2015-03-09 | 2018-01-30 | Microsoft Technology Licensing, Llc | Meeting room device cache clearing |
US9922201B2 (en) | 2015-04-01 | 2018-03-20 | Dropbox, Inc. | Nested namespaces for selective content sharing |
US9996241B2 (en) | 2011-10-11 | 2018-06-12 | Microsoft Technology Licensing, Llc | Interactive visualization of multiple software functionality content items |
US10032135B2 (en) | 2012-03-19 | 2018-07-24 | Microsoft Technology Licensing, Llc | Modern calendar system including free form input electronic calendar surface |
US10049104B2 (en) * | 2016-11-04 | 2018-08-14 | International Business Machines Corporation | Message modifier responsive to meeting location availability |
US20180276192A1 (en) * | 2016-08-29 | 2018-09-27 | International Business Machines Corporation | System, method and computer program product for creating a summarization from recorded audio of meetings |
US10127524B2 (en) | 2009-05-26 | 2018-11-13 | Microsoft Technology Licensing, Llc | Shared collaboration canvas |
US10140198B1 (en) * | 2012-10-30 | 2018-11-27 | Google Llc | Networked desktop environment |
US10198485B2 (en) | 2011-10-13 | 2019-02-05 | Microsoft Technology Licensing, Llc | Authoring of data visualizations and maps |
US10423301B2 (en) | 2008-08-11 | 2019-09-24 | Microsoft Technology Licensing, Llc | Sections of a presentation having user-definable properties |
US20190387033A1 (en) * | 2018-06-19 | 2019-12-19 | Ricoh Company, Ltd. | Information processing apparatus, information processing system, and method of remote information sharing |
US10629189B2 (en) | 2013-03-15 | 2020-04-21 | International Business Machines Corporation | Automatic note taking within a virtual meeting |
US10685038B2 (en) | 2015-10-29 | 2020-06-16 | Dropbox Inc. | Synchronization protocol for multi-premises hosting of digital content items |
US10691718B2 (en) | 2015-10-29 | 2020-06-23 | Dropbox, Inc. | Synchronization protocol for multi-premises hosting of digital content items |
US10819559B2 (en) | 2016-01-29 | 2020-10-27 | Dropbox, Inc. | Apparent cloud access for hosted content items |
US10915584B2 (en) * | 2015-09-22 | 2021-02-09 | Dropbox, Inc. | Event-related document generation |
US10963430B2 (en) | 2015-04-01 | 2021-03-30 | Dropbox, Inc. | Shared workspaces with selective content item synchronization |
CN112651715A (en) * | 2020-12-29 | 2021-04-13 | 太极计算机股份有限公司 | Cross-organization business collaborative flow map construction method, device and equipment |
US20210367802A1 (en) * | 2020-05-21 | 2021-11-25 | HUDDL Inc. | Meeting summary generation |
US11290531B2 (en) | 2019-12-04 | 2022-03-29 | Dropbox, Inc. | Immediate cloud content item creation from local file system interface |
US11303463B1 (en) * | 2017-12-22 | 2022-04-12 | Veeva Systems Inc. | System and method for event management |
US11429943B1 (en) * | 2017-12-22 | 2022-08-30 | Veeva Systems Inc. | System and method for event management |
US11429932B1 (en) * | 2017-12-22 | 2022-08-30 | Veeva Systems Inc. | System and method for event management |
US20230156052A1 (en) * | 2021-11-15 | 2023-05-18 | Lemon Inc. | Methods and systems for facilitating communication in a collaborative work environment |
CN116542643A (en) * | 2022-05-27 | 2023-08-04 | 北京兆维电子(集团)有限责任公司 | Conference processing method and system and conference system |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9723035B1 (en) * | 2013-04-08 | 2017-08-01 | Amazon Technologies, Inc. | Real-time meeting attendance reporting |
US10803189B2 (en) * | 2016-08-31 | 2020-10-13 | Microsoft Technology Licensing, Llc | Location-based access control of secured resources |
US11271978B2 (en) | 2019-09-23 | 2022-03-08 | International Business Machines Corporation | Personalized meeting summaries |
US11606399B2 (en) * | 2021-01-21 | 2023-03-14 | Dell Products L.P. | System and method for meeting preparation and user content management using heterogeneous cloud service providers |
US11228627B1 (en) | 2021-03-19 | 2022-01-18 | Microsoft Technology Licensing, Llc | Updating user-specific application instances based on collaborative object activity |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5317683A (en) * | 1990-09-10 | 1994-05-31 | International Business Machines Corporation | Method and apparatus for automated meeting agenda generation in a data processing system |
US20050027800A1 (en) * | 2003-07-28 | 2005-02-03 | International Business Machines Corporation | Agenda-driven meetings |
US20050125246A1 (en) * | 2003-12-09 | 2005-06-09 | International Business Machines Corporation | Participant tool to support online meetings |
US20050131714A1 (en) * | 2003-12-10 | 2005-06-16 | Braunstein Anne R. | Method, system and program product for hierarchically managing a meeting |
US20060224430A1 (en) * | 2005-04-05 | 2006-10-05 | Cisco Technology, Inc. | Agenda based meeting management system, interface and method |
US20070011233A1 (en) * | 2005-07-06 | 2007-01-11 | Microsoft Corporation | Meetings near me |
US20070033091A1 (en) * | 2005-08-08 | 2007-02-08 | Ravikumar Frederick R | Method And System For Managing A Meeting |
US20080162244A1 (en) * | 2006-12-29 | 2008-07-03 | Tolga Oral | System and method for reordering meeting agenda items prior to the occurrence of the meeting based upon partial participation by the meeting participants |
US20090204465A1 (en) * | 2008-02-08 | 2009-08-13 | Santosh Pradhan | Process and system for facilitating communication and intergrating communication with the project management activities in a collaborative environment |
US20090234721A1 (en) * | 2007-12-21 | 2009-09-17 | Bigelow David H | Persistent collaborative on-line meeting space |
-
2008
- 2008-02-29 US US12/039,789 patent/US9824333B2/en active Active
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5317683A (en) * | 1990-09-10 | 1994-05-31 | International Business Machines Corporation | Method and apparatus for automated meeting agenda generation in a data processing system |
US20050027800A1 (en) * | 2003-07-28 | 2005-02-03 | International Business Machines Corporation | Agenda-driven meetings |
US20050125246A1 (en) * | 2003-12-09 | 2005-06-09 | International Business Machines Corporation | Participant tool to support online meetings |
US20050131714A1 (en) * | 2003-12-10 | 2005-06-16 | Braunstein Anne R. | Method, system and program product for hierarchically managing a meeting |
US20060224430A1 (en) * | 2005-04-05 | 2006-10-05 | Cisco Technology, Inc. | Agenda based meeting management system, interface and method |
US20070011233A1 (en) * | 2005-07-06 | 2007-01-11 | Microsoft Corporation | Meetings near me |
US20070033091A1 (en) * | 2005-08-08 | 2007-02-08 | Ravikumar Frederick R | Method And System For Managing A Meeting |
US20080162244A1 (en) * | 2006-12-29 | 2008-07-03 | Tolga Oral | System and method for reordering meeting agenda items prior to the occurrence of the meeting based upon partial participation by the meeting participants |
US7974871B2 (en) * | 2006-12-29 | 2011-07-05 | International Business Machines Corporation | System and method for reordering meeting agenda items prior to the occurrence of the meeting based upon partial participation by the meeting participants |
US20090234721A1 (en) * | 2007-12-21 | 2009-09-17 | Bigelow David H | Persistent collaborative on-line meeting space |
US20090204465A1 (en) * | 2008-02-08 | 2009-08-13 | Santosh Pradhan | Process and system for facilitating communication and intergrating communication with the project management activities in a collaborative environment |
Cited By (102)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120131104A1 (en) * | 1999-05-07 | 2012-05-24 | Virtualagility Inc. | System and method for supporting collaborative activity |
US8095594B2 (en) * | 1999-05-07 | 2012-01-10 | VirtualAgility, Inc. | System for performing collaborative tasks |
US20080052358A1 (en) * | 1999-05-07 | 2008-02-28 | Agility Management Partners, Inc. | System for performing collaborative tasks |
US8458258B2 (en) * | 1999-05-07 | 2013-06-04 | Virtualagility Inc. | System and method for supporting collaborative activity |
US20120311044A1 (en) * | 1999-05-07 | 2012-12-06 | Virtualagility Inc. | System and Method for Supporting Collaborative Activity |
US9311625B2 (en) * | 1999-05-07 | 2016-04-12 | Virtualagility Inc. | System and method for supporting collaborative activity |
US8275836B2 (en) * | 1999-05-07 | 2012-09-25 | Virtualagility Inc. | System and method for supporting collaborative activity |
US20140026072A1 (en) * | 1999-05-07 | 2014-01-23 | Virtualagility Inc. | System and Method for Supporting Collaborative Activity |
US8719222B2 (en) * | 2008-06-27 | 2014-05-06 | Microsoft Corporation | Synchronization and collaboration within peer-to-peer and client/server environments |
US20110307555A1 (en) * | 2008-06-27 | 2011-12-15 | Microsoft Corporation | Synchronization and Collaboration Within Peer-to-Peer and Client/Server Environments |
US10423301B2 (en) | 2008-08-11 | 2019-09-24 | Microsoft Technology Licensing, Llc | Sections of a presentation having user-definable properties |
US20100169435A1 (en) * | 2008-12-31 | 2010-07-01 | O'sullivan Patrick Joseph | System and method for joining a conversation |
US8650255B2 (en) * | 2008-12-31 | 2014-02-11 | International Business Machines Corporation | System and method for joining a conversation |
US20100235216A1 (en) * | 2009-03-16 | 2010-09-16 | Microsoft Corporation | Integration of pre-meeting and post-meeting experience into a meeting lifecycle |
WO2010107621A3 (en) * | 2009-03-16 | 2011-01-13 | Microsoft Corporation | Integration of pre-meeting and post-meeting experience into a meeting lifecycle |
US10699244B2 (en) | 2009-05-26 | 2020-06-30 | Microsoft Technology Licensing, Llc | Shared collaboration canvas |
US10127524B2 (en) | 2009-05-26 | 2018-11-13 | Microsoft Technology Licensing, Llc | Shared collaboration canvas |
US10331761B2 (en) * | 2010-02-02 | 2019-06-25 | Think-Cell Software Gmbh | Method, computer readable storage medium and computer system for efficient agenda drafting, synchronization and display |
US20110191672A1 (en) * | 2010-02-02 | 2011-08-04 | Think-Cell Software Gmbh | Method, computer readable storage medium and computer system for efficient agenda drafting, synchronization and display |
GB2477762A (en) * | 2010-02-11 | 2011-08-17 | Thales Holdings Uk Plc | Collaborative working environment with defined subgroup of users. |
US10432394B2 (en) * | 2010-03-09 | 2019-10-01 | Kl Data Security Pty Ltd | Method and system for sharing encrypted content |
US20140325231A1 (en) * | 2010-03-09 | 2014-10-30 | Lock Box Pty Ltd. | Method and system for sharing encrypted content |
US8489615B2 (en) * | 2010-03-19 | 2013-07-16 | Avaya, Inc. | System and method for predicting meeting subjects, logistics, and resources |
US9143460B2 (en) * | 2010-03-19 | 2015-09-22 | Avaya Inc. | System and method for predicting meeting subjects, logistics, and resources |
US20160005005A1 (en) * | 2010-03-19 | 2016-01-07 | Avaya Inc. | System and Method for Predicting Meeting Subjects, Logistics, and Resources |
US20130304924A1 (en) * | 2010-03-19 | 2013-11-14 | Avaya Inc. | System and Method for Predicting Meeting Subjects, Logistics, and Resources |
US20110231409A1 (en) * | 2010-03-19 | 2011-09-22 | Avaya Inc. | System and method for predicting meeting subjects, logistics, and resources |
US20120036451A1 (en) * | 2010-08-09 | 2012-02-09 | Hon Hai Precision Industry Co., Ltd. | Electronic device and method for facilitating recording meeting contents |
US9026921B2 (en) * | 2010-08-27 | 2015-05-05 | Business Objects Software Limited | Intelligent workspace |
CN102375858A (en) * | 2010-08-27 | 2012-03-14 | 商业对象软件有限公司 | Intelligent working space |
US20120054639A1 (en) * | 2010-08-27 | 2012-03-01 | Business Objects Software Limited | Intelligent workspace |
US20120150577A1 (en) * | 2010-12-14 | 2012-06-14 | Microsoft Corporation | Meeting lifecycle management |
US9383888B2 (en) | 2010-12-15 | 2016-07-05 | Microsoft Technology Licensing, Llc | Optimized joint document review |
US9118612B2 (en) | 2010-12-15 | 2015-08-25 | Microsoft Technology Licensing, Llc | Meeting-specific state indicators |
US11675471B2 (en) | 2010-12-15 | 2023-06-13 | Microsoft Technology Licensing, Llc | Optimized joint document review |
US9864612B2 (en) | 2010-12-23 | 2018-01-09 | Microsoft Technology Licensing, Llc | Techniques to customize a user interface for different displays |
US9473449B2 (en) | 2011-02-10 | 2016-10-18 | Jeffrey J. Ausfeld | Multi-platform collaboration appliance |
US9824335B1 (en) * | 2011-06-16 | 2017-11-21 | Google Inc. | Integrated calendar and conference application for document management |
US9705689B1 (en) | 2011-06-16 | 2017-07-11 | Google Inc. | Integrated calendar callback feature for inviting to communication session |
US20130007635A1 (en) * | 2011-06-30 | 2013-01-03 | Avaya Inc. | Teleconferencing adjunct and user interface to support temporary topic-based exclusions of specific participants |
US10033774B2 (en) | 2011-10-05 | 2018-07-24 | Microsoft Technology Licensing, Llc | Multi-user and multi-device collaboration |
US8682973B2 (en) | 2011-10-05 | 2014-03-25 | Microsoft Corporation | Multi-user and multi-device collaboration |
US9544158B2 (en) | 2011-10-05 | 2017-01-10 | Microsoft Technology Licensing, Llc | Workspace collaboration via a wall-type computing device |
US9996241B2 (en) | 2011-10-11 | 2018-06-12 | Microsoft Technology Licensing, Llc | Interactive visualization of multiple software functionality content items |
US10198485B2 (en) | 2011-10-13 | 2019-02-05 | Microsoft Technology Licensing, Llc | Authoring of data visualizations and maps |
US11023482B2 (en) | 2011-10-13 | 2021-06-01 | Microsoft Technology Licensing, Llc | Authoring of data visualizations and maps |
CN104067303A (en) * | 2012-01-19 | 2014-09-24 | 微软公司 | Notebook driven accumulation of meeting documentation and notations |
WO2013109511A1 (en) | 2012-01-19 | 2013-07-25 | Microsoft Corporation | Notebook driven accumulation of meeting documentation and notations |
EP2805294A4 (en) * | 2012-01-19 | 2015-08-19 | Microsoft Technology Licensing Llc | Notebook driven accumulation of meeting documentation and notations |
US9449303B2 (en) * | 2012-01-19 | 2016-09-20 | Microsoft Technology Licensing, Llc | Notebook driven accumulation of meeting documentation and notations |
US20130191719A1 (en) * | 2012-01-19 | 2013-07-25 | Microsoft Corporation | Notebook driven accumulation of meeting documentation and notations |
JP2015510175A (en) * | 2012-01-19 | 2015-04-02 | マイクロソフト コーポレーション | Notebook-driven accumulation of meeting documents and meeting notes |
US9720574B2 (en) | 2012-03-19 | 2017-08-01 | Microsoft Technology Licensing, Llc | Personal notes on a calendar item |
US10032135B2 (en) | 2012-03-19 | 2018-07-24 | Microsoft Technology Licensing, Llc | Modern calendar system including free form input electronic calendar surface |
US9508056B2 (en) | 2012-03-19 | 2016-11-29 | Microsoft Technology Licensing, Llc | Electronic note taking features including blank note triggers |
US10732802B2 (en) | 2012-03-19 | 2020-08-04 | Microsoft Technology Licensing, Llc | Personal notes on a calendar item |
US10872316B2 (en) | 2012-03-19 | 2020-12-22 | Microsoft Technology Licensing, Llc | Modern calendar system including free form input electronic calendar surface |
US20130332804A1 (en) * | 2012-06-06 | 2013-12-12 | Conrad Delbert Seaman | Methods and devices for data entry |
US20140006500A1 (en) * | 2012-06-29 | 2014-01-02 | Adobe Systems Incorporated | Interactive broadcasting between devices |
US9973554B2 (en) * | 2012-06-29 | 2018-05-15 | Adobe Systems Incorporated | Interactive broadcasting between devices |
US10140198B1 (en) * | 2012-10-30 | 2018-11-27 | Google Llc | Networked desktop environment |
US10629189B2 (en) | 2013-03-15 | 2020-04-21 | International Business Machines Corporation | Automatic note taking within a virtual meeting |
US10629188B2 (en) | 2013-03-15 | 2020-04-21 | International Business Machines Corporation | Automatic note taking within a virtual meeting |
US20150213410A1 (en) * | 2014-01-24 | 2015-07-30 | T Minus 5 Llc | Meeting Management |
US20150213411A1 (en) * | 2014-01-24 | 2015-07-30 | T Minus 5 Llc | Collaborative Meeting Planning |
EP2916495A1 (en) * | 2014-03-04 | 2015-09-09 | Ricoh Company, Ltd. | Information processing system, an information processing apparatus and a medium storing an information processing program |
EP3186958A4 (en) * | 2014-08-25 | 2017-08-23 | Ricoh Company, Ltd. | Conference management apparatus, document registration method, program, and conference system |
US10979598B2 (en) | 2014-08-25 | 2021-04-13 | Ricoh Company, Ltd. | Conference management apparatus, document registration method, program, and conference system |
US9883003B2 (en) | 2015-03-09 | 2018-01-30 | Microsoft Technology Licensing, Llc | Meeting room device cache clearing |
US9922201B2 (en) | 2015-04-01 | 2018-03-20 | Dropbox, Inc. | Nested namespaces for selective content sharing |
US10001913B2 (en) * | 2015-04-01 | 2018-06-19 | Dropbox, Inc. | Shared workspaces with selective content item synchronization |
US20160291856A1 (en) * | 2015-04-01 | 2016-10-06 | Dropbox, Inc. | Shared Workspaces with Selective Content Item Synchronization |
US11580241B2 (en) | 2015-04-01 | 2023-02-14 | Dropbox, Inc. | Nested namespaces for selective content sharing |
US10963430B2 (en) | 2015-04-01 | 2021-03-30 | Dropbox, Inc. | Shared workspaces with selective content item synchronization |
US10699025B2 (en) | 2015-04-01 | 2020-06-30 | Dropbox, Inc. | Nested namespaces for selective content sharing |
US10915584B2 (en) * | 2015-09-22 | 2021-02-09 | Dropbox, Inc. | Event-related document generation |
US11144573B2 (en) | 2015-10-29 | 2021-10-12 | Dropbox, Inc. | Synchronization protocol for multi-premises hosting of digital content items |
US10740350B2 (en) | 2015-10-29 | 2020-08-11 | Dropbox, Inc. | Peer-to-peer synchronization protocol for multi-premises hosting of digital content items |
US10691718B2 (en) | 2015-10-29 | 2020-06-23 | Dropbox, Inc. | Synchronization protocol for multi-premises hosting of digital content items |
US10685038B2 (en) | 2015-10-29 | 2020-06-16 | Dropbox Inc. | Synchronization protocol for multi-premises hosting of digital content items |
US9984057B2 (en) | 2015-12-16 | 2018-05-29 | Microsoft Technology Licensing, Llc | Creating notes related to communications |
WO2017105972A1 (en) * | 2015-12-16 | 2017-06-22 | Microsoft Technology Licensing, Llc | Creating notes related to communications |
US10819559B2 (en) | 2016-01-29 | 2020-10-27 | Dropbox, Inc. | Apparent cloud access for hosted content items |
US11288443B2 (en) | 2016-08-29 | 2022-03-29 | International Business Machines Corporation | Summarization method for recorded audio |
US20180276192A1 (en) * | 2016-08-29 | 2018-09-27 | International Business Machines Corporation | System, method and computer program product for creating a summarization from recorded audio of meetings |
US10592599B2 (en) * | 2016-08-29 | 2020-03-17 | International Business Machines Corporation | System, method and computer program product for creating a summarization from recorded audio of meetings |
US20220012413A1 (en) * | 2016-08-29 | 2022-01-13 | International Business Machines Corporation | Summarization method for recorded audio |
US10049104B2 (en) * | 2016-11-04 | 2018-08-14 | International Business Machines Corporation | Message modifier responsive to meeting location availability |
US10740569B2 (en) | 2016-11-04 | 2020-08-11 | International Business Machines Corporation | Message modifier responsive to meeting location availability |
US11429932B1 (en) * | 2017-12-22 | 2022-08-30 | Veeva Systems Inc. | System and method for event management |
US11303463B1 (en) * | 2017-12-22 | 2022-04-12 | Veeva Systems Inc. | System and method for event management |
US11429943B1 (en) * | 2017-12-22 | 2022-08-30 | Veeva Systems Inc. | System and method for event management |
US11245733B2 (en) * | 2018-06-19 | 2022-02-08 | Ricoh Company, Ltd. | Information processing apparatus, information processing system, and method of remote information sharing |
US20190387033A1 (en) * | 2018-06-19 | 2019-12-19 | Ricoh Company, Ltd. | Information processing apparatus, information processing system, and method of remote information sharing |
US11290531B2 (en) | 2019-12-04 | 2022-03-29 | Dropbox, Inc. | Immediate cloud content item creation from local file system interface |
US11416831B2 (en) | 2020-05-21 | 2022-08-16 | HUDDL Inc. | Dynamic video layout in video conference meeting |
US20210367802A1 (en) * | 2020-05-21 | 2021-11-25 | HUDDL Inc. | Meeting summary generation |
US11488116B2 (en) | 2020-05-21 | 2022-11-01 | HUDDL Inc. | Dynamically generated news feed |
US11537998B2 (en) | 2020-05-21 | 2022-12-27 | HUDDL Inc. | Capturing meeting snippets |
CN112651715A (en) * | 2020-12-29 | 2021-04-13 | 太极计算机股份有限公司 | Cross-organization business collaborative flow map construction method, device and equipment |
US20230156052A1 (en) * | 2021-11-15 | 2023-05-18 | Lemon Inc. | Methods and systems for facilitating communication in a collaborative work environment |
CN116542643A (en) * | 2022-05-27 | 2023-08-04 | 北京兆维电子(集团)有限责任公司 | Conference processing method and system and conference system |
Also Published As
Publication number | Publication date |
---|---|
US9824333B2 (en) | 2017-11-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9824333B2 (en) | Collaborative management of activities occurring during the lifecycle of a meeting | |
US9715476B2 (en) | Collaborative authoring with scratchpad functionality | |
US10389769B2 (en) | Integrated real time collaboration experiences with online workspace | |
US20190026269A1 (en) | Systems and methods for providing access to data and searchable attributes in a collaboration place | |
US7840543B2 (en) | Method for sharing groups of objects | |
US9165290B2 (en) | Sharing notes in online meetings | |
AU2010226162B2 (en) | Integration of pre-meeting and post-meeting experience into a meeting lifecycle | |
US8239234B2 (en) | Freeform communication in calendaring system | |
US8484292B2 (en) | System and methods for managing co-editing of a document by a plurality of users in a collaboration place | |
US11836679B2 (en) | Object for pre- to post-meeting collaboration | |
JP2009520274A (en) | Electronic provisioning of schedulable calendars | |
US7877356B1 (en) | Retaining intermediate states of shared groups of objects and notification of changes to shared groups of objects | |
JP2000181956A (en) | Information managing and sharing system | |
US11562331B1 (en) | Scheduling a subsequent meeting related to a previous meeting | |
US20230155851A1 (en) | Auto-Generated Object For Impromptu Collaboration | |
Busbach et al. | Support for meetings using the EuroCoOp Task Manager | |
US11962427B2 (en) | Auto-generated object for impromptu collaboration | |
WO2022175678A1 (en) | Messaging and calendaring method and system | |
KR20210147585A (en) | Apparatus and method of providing communication tool | |
Rohall et al. | LiveDeck: Extending Presentations to Support Collaborations | |
Broadwater | Implementing the modern office environment: some experience with Windows for Workgroups and Groupware. |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHAW, DONNA SUE;KLABISH, GREGORY SCOTT;SLAPIKOFF, GAIL ELAINE;REEL/FRAME:020579/0482 Effective date: 20080227 |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034542/0001 Effective date: 20141014 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |