Techniques for integrating note-taking and multimedia information

BACKGROUND OF THE INVENTION

0001The present invention relates to a note-taking system, and more particularly to techniques that improve a user's note-taking experience in an environment where information of various types is being recorded.

0002Several techniques have been developed in the past few years for capturing information during a meeting, lecture, or other like presentation. For example, during a presentation, slides (e.g., from a PowerPoint presentation) and video clips may be shown on a projection device while the presenter discusses information related to the slides and/or video clips. Attendees of the meeting may also join in the discussion. The presenter may also write on a whiteboard during the presentation. In such an environment, one or more information capture devices may be provided to record the multimedia information output during the presentation. For example, a video camera may be used to record the slides/video clips presented on the projection device or the actual scene of the presentation. Audio devices such as microphones may be used to capture the audio information spoken by the presenter or the attendees of the meeting. A whiteboard capture device may be used to capture information written on the whiteboard. Various other types of devices may be used to record other types of information output during the presentation.

0003The recorded information captured by the various capture devices is usually stored and can be accessed or consumed by a user after the presentation. For example, a user who could not attend the meeting can access the recorded information and play back the information after the meeting. In this manner, the archived information is available for use subsequent to the meeting.

0004During a presentation attendees of the presentation usually capture information presented during the presentation by taking notes. Although the traditional technique of taking notes has been to use a paper and pencil/pen, an increasing number of users now use computing devices such as laptops, personal digital assistants (PDAs), tablet PCs, etc. to take notes during presentations. However, even with these devices, it is usually quite difficult for the note-taker to capture in his/her notes information of various types (e.g., audio information, slides, video information, etc.) that is output during the presentation. Although, the information during the presentation is being recorded, the recorded information is not available for use by the note-taker until after the presentation has completed. Accordingly, the recorded information cannot be used by the note-taker while the presentation is in progress.

0005Accordingly, there is a need for techniques that improve a user's note taking experience.

0006Publication <nplcit id="ncit0001" npl-type="s"><text>P. CHIU, A. KAPUSKAR, S. REITMEIER, L. WILCOX: "NoteLook: Taking Notes in Meetings with Digital Video and Ink" ACM MULTIMEDIA '99, October 1999, pages 149-158, XP002316508 ORLANDO, FLORIDA, USA</text></nplcit> relates to taking notes in Meetings with digital video and ink. In this respect, NoteLook is a client-server system designed and built to support multimedia note taking in meetings with digital video and ink. It is integrated into a conference room equipped with computer controllable video cameras, video conference camera, and a large display rear video projector. The NoteLook client application runs on wireless pen-based notebook computers. Video channels containing images of the room activity and presentation material are transmitted by the NoteLook servers to the clients, and the images can be interactively and automatically incorporated into the note pages. Users can select channels, snap in large background images and sequences of thumbnails, and write freeform ink notes. A smart video source management component enables the capture of high quality images of the presentation material from a variety of sources. For accessing and browsing the notes and recorded video, NoteLook generates Web pages with links from the images and ink strokes correlated to the video.

0007Publication <nplcit id="ncit0002" npl-type="s"><text>PATRICK CHIU, JOHN S. BORECZKY AND ANDREAS GIRGENSOHN AND DON KIMBER: "LiteMinutes: an Internet-based system for multimedia meeting minutes" PROCEEDINGS OF TENTH WORLD WIDE WEB CONFERENCE, 2 May 2001 XP002316510</text></nplcit> relates to an Intemet-based system for multimedia meeting minutes. In this respect, the Internet provides a highly suitable infrastructure for sharing multimedia meeting records, especially as multimedia technologies become more lightweight and workers more mobile. LiteMinutes is a system that uses both the Web and email for creating, revising, distributing, and accessing multimedia information captured in a meeting. Supported media include text notes taken on wireless laptops, slide images captured from presentations, and video recorded by cameras in the room. At the end of a meeting, text notes are sent by the note taking applet to the server, which formats them in HTML with links from each note item to the captured slide images and video recording. Smart link generation is achieved by capturing contextual metadata such as the on/off state of the media equipment and the room location of the laptop, and inferring whether it makes sense to supply media links to a particular note item.

0008Note takers can easily revise meeting minutes after a meeting by modifying the email message sent to them and mailing it back to the server's email address. Design issues were explored, concerning preferences for email and Web access of meeting minutes, as well as the different timeframes for access. It is also described the integration with a comic book style video summary and visualization system with text captions for browsing the video recording of a meeting.

0009Publication <nplcit id="ncit0003" npl-type="s"><text>TRUONG, K. AND ABOWD, G: "Architectural Support for Building Automated Capture and Access Applications" 20 October 2003 (2003-10-20), XP002316511</text></nplcit> relates to an architectural support for building automated capture and access applications. In this respect, applications that automatically capture some details of a live experience and provide future access to that experience are increasingly common in the ubiquitous computing community. The exploration of this class of applications raises software engineering problems pertaining to proper software structuring and programming abstractions to support the design development and evolution of these systems. The building of a number of capture and access applications, sharing insights on relative successes and failures are explained. These are provided in a toolkit called Infrastructure for Capture and Access (INCA) which supports a distillation of the essential architectural features for this class of applications. It is demonstrated how this toolkit encourages a simplified model for designing, implementing, and evolving such applications - lowering the barrier for building automated capture and access applications and inspiring the construction of a larger variety of applications previously unexplored.

SUMMARY OF THE INVENTION

0010The invention is defined by the subject-matter of the independent claims. The dependent claims are directed to advantageous embodiments.

ADVANTAGES OF THE INVENTION

0011Embodiments of the present invention improve a user's note-taking experience. While taking notes for a presentation, a user can request one or more portions of information recorded during the presentation to be inserted into the user's notes document. User information requests that cannot be immediately processed are stored or cached in the notes document for later processing. These cached requests are processed and the requested information inserted into the user's notes document at a later time.

0012Advantageously, techniques are provided for taking notes in an environment comprising a server configured to respond to requests requesting a portion of stored information, the stored information comprising first information captured by one or more capture devices during a first presentation, and a note-taking device for taking notes during the first presentation in a notes document. A first request is received at the note-taking device during the first presentation to insert a first portion of the first information in a first location in the notes document. A determination is made if the first request can be processed. The first request is stored in the notes document upon determining that the first request cannot be processed.

0013Advantageously, a determination is made, subsequent to storing the first request in the notes document, if the note-taking device can communicate with the server. The first request is processed upon determining that the note-taking device can communicate with the server. Advantageously, the first portion of the first information is inserted in the notes document in the first location.

0014The foregoing, together with other features, embodiments, and advantages of the present invention, will become more apparent when referring to the following specification, claims, and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

0015<ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">Fig. 1</figref> is a simplified block diagram of a system that may incorporate an embodiment of the present invention;</li><li><figref idref="f0002">Fig. 2</figref> is a simplified high-level flowchart depicting a method of processing requests for inserting recorded information in a user's notes document according to an embodiment of the present invention;</li><li><figref idref="f0003">Fig. 3</figref> depicts a list of templates including a template that provides note-taking functionality according to an embodiment of the present invention;</li><li><figref idref="f0003">Fig. 4</figref> depicts a section of a Microsoft Word^™ tool bar showing a menu bar comprising user-selectable options for inserting portions of recorded information into a notes document according to an embodiment of the present invention;</li><li><figref idref="f0004">Fig. 5</figref> depicts a user interface that displays information regarding sessions that the user is authorized to access information from according to an embodiment of the present invention;</li><li><figref idref="f0004">Fig. 6</figref> displays a user interface that allows a user to browse through previously recorded session information when the information is accessible to the user's note-taking device according to an embodiment of the present invention;</li><li><figref idref="f0005">Fig. 7A</figref> depicts a Microsoft Word™ interface 700 that has been configured to provide options for taking notes and that display a notes document with a cached request according to an embodiment of the present invention;</li><li><figref idref="f0006">Fig. 7B</figref> depicts the notes document of <figref idref="f0005">Fig. 7A</figref> wherein the cached information request has been processed according to an embodiment of the present invention; and</li><li><figref idref="f0007">Fig. 8</figref> is a simplified block diagram of a note-taking device 108 that may be used to perform processing according to an embodiment of the present invention.</li></ul>

DETAILED DESCRIPTION OF THE INVENTION

0016In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of the invention. However, it will be apparent that the invention may be practiced without these specific details.

0017<figref idref="f0001">Fig. 1</figref> is a simplified block diagram of a system 100 that may incorporate an embodiment of the present invention. System 100 depicted in <figref idref="f0001">Fig. 1</figref> is merely illustrative of an embodiment incorporating the present invention and does not limit the scope of the invention as recited in the claims. One of ordinary skill in the art would recognize other variations, modifications, and alternatives.

0018As depicted in <figref idref="f0001">Fig. 1</figref>, system 100 includes one or more information capture devices 102 that are configured to capture (or record) information during a presentation. For purposes of this application, a "presentation" is intended to refer to any event or period of time during which information is presented or output Examples of presentations include meetings, lectures, discussions, classes, conferences, speeches, demonstrations, playback of previously recorded information, and the like. A presentation need not be contiguous in time and can be spread out over non-contiguous time periods. For example, a presentation may be spread out over several days and may be interspersed by other events.

0019For purposes of this application, an "information capture device" is intended to refer to any device, system, or apparatus that is configured to capture or record information of one or more types. Various different types or streams of information such as audio information, video information, slides or images, whiteboard information, text information (e.g., user contributed comments), etc. may be output during a presentation and captured by information capture devices 102. Examples of information capture devices 102 include microphones, video cameras, analog or digital photo cameras, scanners, screen capture devices (e.g., a device configured to capture information printed on a whiteboard), presentation recorders, etc. Information capture devices 102 may also be configured to capture temporal information when the information is captured.

0020A presentation recorder is a device that is able to capture information presented during a presentation, for example, by tapping into and capturing streams of information from an information source such as a computer executing a PowerPoint application and displaying slides from a *.ppt file. A presentation recorder may be configured to tap into the video output of the computer and capture keyframes every time a significant difference is detected between displayed video keyframes of the slides. The presentation recorder may also be configured to capture other types of information such as audio information, video information, slides information stream, etc. Time stamps indicating time of capture may also be stored by the presentation recorder. The temporal information indicating when the information was output or captured may be used to synchronize the different types of captured information streams. Examples of presentation recorders include a screen capture software application that allows recording of slides and time elapsed for each slide during a presentation. Examples of presentation recorders are described in <patcit id="pcit0001" dnum="US20010020954A"><text>US 2001/0020954 A</text></patcit> and <patcit id="pcit0002" dnum="US20020056082A"><text>US 2002/0056082 A</text></patcit>.

0021In the embodiment depicted in <figref idref="f0001">Fig. 1</figref>, the information recorded by information capture devices 102 is pushed to server 104 ("presentation server 104") that caches and maintains the recorded information. The information may be pushed to presentation server 104 in a continuous stream or in bursts. The recorded information may include streams of information of various types including slides, images, audio segments, (e.g., MP3 audio segments), video clips or segments, whiteboard information segments, text information, etc.

0022Presentation server 104 may store the information received from information capture devices 102 in a memory location accessible (locally or via a network) to presentation server 104. In one embodiment, presentation server 104 is configured to coordinate access to the stored information. For example, presentation server 104 is configured to respond to requests requesting portions of the recorded information.

0023According to an embodiment of the present invention, the recorded information may be organized into "sessions" 106. For purposes of this application, a "session" is a collection of recorded information. For example, a session may correspond to information streams captured by information capture devices 102 during a certain time period. For example, information recorded during a first presentation (e.g., a meeting between 1:00pm and 2:00pm) may be stored as a first session while information recorded during a second presentation (e.g., a meeting between 3:00pm and 5:00pm) may be stored as another session. A session may also store information recorded over different time periods or different presentations. For example, information captured during a series of lectures may be stored as a single session. Presentation server 104 is configured to control access to the various sessions information.

0024In the embodiment depicted in <figref idref="f0001">Fig. 1</figref>, a user uses a computing device 108 ("note-taking device 108") to take notes. The notes may include text, figures, etc. entered by the user. According to an embodiment of the present invention, the notes may also include portions of recorded information (e.g., multimedia streams or objects). Examples of note-taking device 108 include a personal computer, a portable or laptop computer, a personal digital assistant (PDA), a tablet PC, etc. The user or note-taker may use an application ("composing application 110") 110 executing on note-taking device 108 to take notes in a document 112 ("notes document") created by composing application 110. Examples of composing applications 110 include applications such as Microsoft Word™, Microsoft Excel™, WordPerfect™, text editors (e.g., TextEdit, WinEdit), and the like. Any application that can be used to create or open a document and write information to the document can be classified as a composing application. For example, the user may open a document 112 using Microsoft Word™ executing on note-taking device 108 and take notes in the document. The notes document 112 may be stored on note-taking device 108.

0025According to an embodiment of the present invention, while taking notes during a presentation, a user can specify that portions of information recorded by capture devices 102 during the presentation be incorporated or inserted into the user's notes. The portion may correspond to a slide or other image, an audio segment, a video segment, a text segment (e.g., user contributed text notes), etc. A portion may correspond to a multimedia object included in the information captured by information capture devices 102. For example, the user may request that: a slide being presently shown on a projection device be inserted at a particular location in the user's notes; an audio segment comprising the last 5-minutes of recorded audio information be inserted into the user's notes; a video clip being presently shown be inserted into the user's notes; and the like. Embodiments of the present invention thus enable a user to incorporate information recorded during a presentation or portions thereof into the user's notes while the presentation is proceeding. Recorded information of various types that is captured during the presentation may be incorporated into the user's notes. Details related to how a user can incorporate such information in the user's notes are provided below.

0026Whether or not a user's request to insert information in the notes can be processed generally depends upon whether note-taking device 108 can communicate with presentation server 104 and receive the requested information for presentation server 104. Note-taking device 108 may or may not be communicatively coupled (i.e., can communicate with presentation server 104) to presentation server 104. This on/off nature of the connection between note-taking device 108 and presentation server 104 is indicated by dotted line 114 depicted in <figref idref="f0001">Fig. 1</figref>. For example, note-taking device 108 may be connected or may not be connected to presentation server 104 during (or after) a presentation when the user is taking notes using note-taking device 108. The connection between the note-taking device 108 and the presentation server 104 may be volatile in some situations where it comes and goes (e.g., a weak wireless connection) during a presentation.

0027When note-taking device 108 is connected to presentation server 104, then note-taking device 108 can access information recorded during the presentation by information capture devices 102 and pushed to presentation server 104. Note-taking device 108 may not have access to the captured information when not connected to presentation server 104. According to the teachings of the present invention, the ability of a user to take notes, including specifying portions of the captured information to be inserted in the notes, is not dependent on whether or not note-taking device 108 is communicatively coupled to presentation server 104 (i.e., not dependent on whether note-taking device 108 has access to the captured information or not).

0028According to an embodiment of the present invention, when note-taking device 108 can communicate with presentation server 104, user requests for portions of recorded information to be incorporated into the user's notes are communicated from note-taking device 108 to presentation server 104. Presentation server 104 responds to the requests by sending the request information portions to note-taking device 108. The requested information portions received from the presentation server 104 are then incorporated into the user's notes in locations identified by the user. In this manner, portions of the information being recorded during the presentation can be inserted into the user's notes during the presentation.

0029According to the present invention, when note-taking device 108 cannot communicate with presentation server 104, user requests for portions of recorded information to be incorporated into the user's notes are cached (or stored) in the notes document that the user is composing. Information identifying locations within the notes document where the requested information portions are to be placed may also be cached in the notes document. A visible place holder or marker is placed in the notes document at a location where the requested information is to be inserted The place holder or marker may indicate contextual information (e.g., a slide number from a particular session) regarding the requested information. Accordingly, a user need not have access to the recorded information when the information request is made.

0030Information requests that are cached in the notes document are then processed at a later time. For example, the cached requests may be automatically processed when note-taking device 108 detects that communication with presentation server 104 has been established. Note-taking device 108 may periodically check if communication with the presentation server 104 has been established. The check to determine if communication has been established may be performed upon receiving a signal generated in response to a user action (e.g., user opens the notes document, user explicitly requests a communication check) or in response to an automated signal (e.g., a signal generated by a timer, a signal generated in response to some event related to the notes document).

0031As described above, the information recorded by information capture devices 102 and pushed to presentation server 104 may be stored and organized into sessions. According to an embodiment of the present invention, a user's access to the recorded information is regulated on a per session basis. In this embodiment, a user or note-taker is allowed to request information stored in a session only if the user is authorized to access information from that session. As a result, in this embodiment, a user has to secure authorization for a session before the user request recorded information from the session.

0032In the example depicted in <figref idref="f0001">Fig. 1</figref>, authorization device 116, presentation server 104, and an authorization module 118 executing on note-taking device 108 perform the authorization operations. In this example, a user gains authorization by logging in using authorization module 118 and authorization device 116. Authorization module 118 is independent of composing application 110.

0033According to an example of the present invention, the authorization process is initiated when authorization module 118 communicates login information from the user's note-taking device 108 to authorization device 116 which in turn communicates the information to presentation server 104. The login information may include usemame information, IP address of note-taking device 108, clock information of the note-taking device 108, and other information used for authorization.

0034Presentation server 104 responds by communicating authorization information to authorization device 116 which in turn communicates the information to note-taking device 108. According to an example, the authorization information comprises a session identifier that identifies the session for which authorization is granted for the user. For example, if the user is attending a presentation, the session identifier may identify a session storing information recorded for the presentation that the user is attending. Presentation server 104 may also communicate other information as part of the authorization information such as a login key, the presentation server's host IP address that the note-taking device 108 can use to communicate with the presentation server 104, and other information. Presentation server 104 can be configured to implement several strategies of authorization depending on the access level of a session in a manner similar to those of a file system protection. According to an example, if a session is declared private, only password protected users are authorized to access session information. These password protected user accounts may be created in advance through another process such as conference registration and made known to the user. Alternatively, a login account may be dynamically created if the authorization request is received through an infrared authorization device during the presentation. If a session is declared public, then any authorization request is granted.

0035A user may be also gain authorization to multiple sessions. For example, in addition to the current session storing recorded information for the current presentation that the user is attending, the user may have previously attended three other presentations and gotten authorization to sessions storing recorded information for the three presentations. Different session identifiers may be used to identify different sessions. Presentation server 104 may store a list of authorized session identifiers for each user. The status of the login/authorization process may also be output to the user using note-taking device 108.

0036According to an arrangement of the present invention, infrared (IR) technology may be used to accomplish the authorization process. For example, authorization device 116 may be an IR receiver/transmitter and authorization module 118 may be an IR module configured to communicate with an IR receiver. In one such arrangement, IR module 118 may be configured to automatically start when note-taking device 108 is started (e.g., when a laptop boots up). IR Module 118 is configured to monitor the IR port on note-taking device 108 and send protocol information to an IR authorization device 116 when it comes within range of authorization device. For example, in one embodiment, when a note-taking device 108 comprising an IR module 118 comes within range of an IR authorization device 116, it sends the usemame information, note-taking device's IP address, and clock information to authorization device 116. In return, note-taking device 108 receives a session identifier and other information (e.g., a login key, presentation server's IP address) from authorization device 116. In one embodiment, the IR authorization module 118 is implemented using VC++ (Visual C++) and IR communication is based on IR sockets.

0037As stated above, the status of the login/authorization process may also be output to the user using note-taking device 108. For example, in the case where authorization module 118 is automatically initiated by detecting an IR authorization device 116 in alignment, a message may be displayed on the note-taking device 108 indicating success or failure of the login/authorization process. An audible signal (e.g., a bell sound) may also be used to indicate the status of the login and authorization.

0038Using IR technology, the physical presence/location of the user's note-taking device 108 may initiate the authorization and login process. For example, one or more IR authorization devices 116 may be placed at convenient locations in a conference room. When the conference room is used for a presentation, attendees of the presentation may automatically login and gain access to information recorded for the presentation by bringing their note-taking devices within range of the IR authorization devices 116.

0039As another example, in an environment where a table is used for meetings, IR authorization devices 116 may be placed on the table. When people attending a meeting sit down around the table and start their note-taking devices 108, they are automatically logged in when the IR authorization modules 118 executing on their note-taking devices 108 come within range of the IR authorization devices 116. In this manner, an "intelligent" environment may be created that facilitates recording of information and note-taking according to the teachings of the present invention.

0040Various other technologies besides IR technology may also be used to accomplish the login and authorization process. For example, a web page may be provided for the user to login and gain authorization.

0041<figref idref="f0002">Fig. 2</figref> is a simplified high-level flowchart 200 depicting a method of processing requests for inserting recorded information in a user's notes document according to an embodiment of the present invention. The method depicted in <figref idref="f0002">Fig. 2</figref> may be performed by software modules executed by note-taking device 108, hardware modules of note-taking device 108, or combinations thereof. Flowchart 200 depicted in <figref idref="f0002">Fig. 2</figref> is merely illustrative of an embodiment of the present invention and is not intended to limit the scope of the present invention. Other variations, modifications, and alternatives are also within the scope of the present invention.

0042As depicted in <figref idref="f0002">Fig. 2</figref>, processing is initiated in step 202 upon receiving a request during a presentation to insert into the user's notes a portion of information recorded and stored in a session. The request may identify the type of information requested, for example, a slide or other image, an audio segment, a video segment, a text segment, etc. Multiple types of information (e.g., a slide along with an audio clip) may be requested in a single request. The request may also identify a particular location within the note-takers' notes document where the requested information is to be inserted. The request may include information specifying a session identifier identifying a session from which information is requested. The session identifier may identify a session storing information for the presentation in progress or any other session storing information recorded from a previous presentation to which the user has gained authorization. According to an example of the present invention, each information request received in step 202 is assigned a unique request identifier.

0043The information request in step 202 may be received at any time whether or not note-taking device 108 is communicatively coupled to presentation server 104. Accordingly, the user can request the information while taking notes irrespective of whether the requested information is accessible to note-taking device 108.

0044A note-taker may use various techniques to configure a request. In one embodiment, a user interface may be displayed on note-taking device 108 that allows the user to specify information to be incorporated into the user's notes. The user interface for specifying the information to be inserted may be integrated with the user interface provided by composing application 110 that is used to take the notes. For example, the user interface of a composing application 110 such as Microsoft Word™ may be customized to provide options (e.g., buttons, menus, etc.) that allow a user to configure requests requesting a portion of recorded information to be inserted into the user's notes. One such embodiment is described below in further detail.

0045According to one technique, the information to be inserted into the user's notes may be based upon the time when the user makes the request and the type of information selected by the user. In this embodiment, user-selectable options (e.g., buttons, menus, etc.) may be provided which allow the user to select the type (e.g., slide, audio segment) of recorded information to be incorporated into the user's notes. In this embodiment, the selected information type along with the time when the selection is made and the session identifier form the information request. According to an example of the present invention, the location of the cursor within the notes document when the option is selected indicates the location in the notes document where the requested information is to be placed.

0046For example, a plurality of buttons may be displayed each corresponding to an information type such as slides, audio, video, text, etc. If the user wants to insert the presently displayed slide in the user's notes, the user can move the cursor to a location in the notes document where the slide is to be inserted and then select the "slides" button. This generates an information request requesting that the currently displayed slide (i.e., the slide being displayed when the user selected the "slides" button) be inserted in the cursor location in the user's notes. The user may select other buttons corresponding to the other types of information to configure requests to insert portions of those particular types of information. For example, if the user selects the "audio" button, then a request for audio information is generated. The amount of audio information requested may be based upon the time when the request was made. In one example, a predetermined and user configurable time buffer relative to the time of selection (e.g., 1 minute prior to the time of selection) may be used to identify the amount of audio information to be incorporated. In other examples, the user may be allowed to specify the time length of the audio information to be inserted in the user's notes.

0047According to another technique, a user may specifically identify the information to be incorporated into the user's notes. For example, the user may specify a slide number identifying a slide (which may have been previously displayed during the presentation) to be inserted into the user's notes. Likewise, the user may specify a portion of other types of recorded information (e.g., video clip shown during the first 5 minutes of the presentation, audio information spoken by a particular speaker during the presentation) to incorporated into the user's notes.

0048As described earlier, in some examples of the present invention, a user may be authorized to access information from multiple sessions. For example, in addition to the presently recorded session, the user may also be authorized to access information from other previously recorded sessions. In such examples, the user can configure requests requesting information not only from a session corresponding to the present presentation but also from other sessions. For each request, the user may specify the session (e.g., using a session identifier) from which information is requested.

0049In step 204, it is determined if the information request received in step 202 can be processed. A request can be processed if the requested information is accessible to note-taking device 108. The requested information may be accessible via presentation server 104 or in some situations may be accessible locally (i.e., if the requested information is locally cached on note-taking device 108). A request cannot be processed if the requested information is not accessible.

0050Accordingly, in most situations, whether or not a user's request to insert information in the notes can be processed generally depends upon whether note-taking device 108 can communicate with presentation server 104 and receive the requested information from presentation server 104. In one embodiment, the request can be processed if note-taking device 108 can communicate with presentation server 104. Accordingly, a check is made in step 204 to see if the note-taking device 108 and presentation server 104 can communicate with each other. If it is determined that the note-taking device 108 and presentation server 104 can communicate with each other, then it is deemed that the request can be processed and processing continues with step 206. If it is determined that the note-taking device 108 and presentation server 104 cannot communicate with each, then it is deemed that the request cannot be processed and processing continues with step 214.

0051In certain situations, it may be determined in step 204 that the information request received in step 202 cannot be processed even though the note-taking device 108 and presentation server 104 can communicate with each other. For example, the information requested may not yet be available. In this situation processing continues with step 214.

0052In step 206, an information query is composed based upon the information request. According to an embodiment of the present invention, the information query comprises a session identifier identifying the session from which information is requested, a login key received during authorization, and information identifying the requested information. The query composed in step 206 is then communicated to the presentation server 104 in step 208.

0053Upon receiving a query from a note-taking device 108, presentation server 104 determines if the user is authorized to access the requested information. The query is not processed if the requested information is part of a session which the user is not authorized to access. If the user is authorized, then presentation server 104 determines the requested information and communicates the requested information to the note-taking device that was the source of the information request. Accordingly, in step 210, the note-taking device 108 receives the requested information from presentation server 104. In step 212, the requested information received in step 210 is inserted into the notes document in the user-specified location. This terminates the processing of the request received in step 202.

0054As previously indicated, various different types of recorded information (e.g., slides, images, text, audio information, video information) may be requested and inserted in the user's notes document. According to an embodiment of the present invention, when audio information is inserted in the notes document, a small icon is placed in the notes document where the information is inserted. Clicking on the audio icon automatically opens the inserted audio clip for playback using a preferred player.

0055According to an example of the present invention, the inserted data is actually embedded in the notes document--this is substantially different from hyperlinks that provide links to data. As a result, various operations that can ordinarily be performed on a document can be performed on the notes document. For example, the document can be copied, distributed, etc. In one example, the authorization to access session information is stored separately from the document; thereby allowing distribution of selective data without giving access to the entire session. It should be noted that a user can take notes and include portions of recorded information from different presentations in a single document.

0056If it is determined in step 204 that the request received in step 202 cannot be processed at that time, then in step 214, the request is stored or cached in the notes document for later processing. Multiple unprocessed information requests may be cached in the notes document. In one embodiment, each cached request is stored as a property associated with the notes document. For example, the request may be stored as custom properties of the document (e.g., the "CustomDocumentProperties" associated with a Microsoft Word™ document). Each cached request may be assigned a unique identifier, e.g., "mrRequest#", where # is a unique request identifier. Uniqueness of cached request identifiers in a notes document is preserved. For each cached request, the data type associated with the request, the request time, and other additional information associated with the request may also be stored.

0057Information identifying the location in the notes document where the requested information is to be inserted may also be cached in the notes document in step 216. According to the present invention, a visible mark or cue is placed in the notes document where the information requested by the cached request is to be inserted. The visible mark acts as a reminder to the user that information corresponding to an unprocessed request is to be inserted in that location. The visible mark may also provide information identifying the requested information.

0058The information requests that are cached in the notes document are then processed at a later time, as indicated in step 218. For example, the cached requests may be automatically processed when note-taking device 108 detects that communication with presentation server 104 has been established. In one example, note-taking device 108 may be configured to periodically check communications between note-taking device 108 and presentation server 104 in order to automatically process the cached requests when communication is established.

0059In another example, an attempt to process cached requests may be made by note-taking device 108 responsive to various stimuli. For example, such an attempt may be made upon receiving a signal generated in response to a user action (e.g., user opens the notes document, user explicitly requests a communication check). The signal may also be automatically generated, e.g., a signal generated by a timer on a periodic basis, a signal generated in response to some event related to the notes document. Upon receiving the signal, note-taking device 108 may be configured to check communications between the note-taking device 108 and the presentation server 104 and to process cached requests if communications are possible.

0060When the cached requests are processed in step 218, the processing performed in steps 206, 208, 210, and 212 is performed for the cached requests. After a request is processed, it is removed from the cache.

0061If an error occurs as a result of processing, the request is also removed from the cache and an error message inserted at the location where the requested information would have been inserted. In one embodiment, an error may occur when a user tries to request information from an unauthorized session, or when the user makes a request for a current slide when no presentation is being captured. The errors can be detected in a number of ways. In one embodiment, a process error is detected by note-taking device 108 when receiving an explicit error signal from presentation server 104 as a result of request processing.

Microsoft Word^™ example

0062This section describes an example wherein a Microsoft Word^™ composing application is used to take notes. This example is not intended to limit the scope of the present invention as recited in the claims. The teachings of the present invention can also be used other composing applications.

0063In this example, code modules are provided on the note-taking device 108 that provide the note-taking functionality of the present invention and run inside any standard Microsoft Word^™ package. These code modules and forms, along with other layout and formatting guidelines may be saved and distributed as a Word template file. These modules cause a menu interface to be shown inside Microsoft Word^™ that allows users to configure requests for recorded information. For example, a user can specify a slide, an audio segment, a video clip, etc. to be incorporated into the user's notes during a presentation. The modules provide the functionality needed to support user information requests for inserting portions of recorded information in the user's notes. In one embodiment, the modules that run on note-taking device 108 are implemented using Visual Basic for Applications (VBA).

0064As described above, modules implementing the note-taking functionality according to the teachings of the present invention may be distributed as a Word template file. Any document opened with this template will have the note-taking functionality of the present invention. For example, when a new document is to be opened for taking notes using Microsoft Word^™, the user can select the template that provides the functionality of the present invention to open the document. As depicted in <figref idref="f0003">Fig. 3</figref>, a list 300 of templates may be displayed to the user and the user can select can select a template 302 (the "mrCapture.dot" template) which provides the note-taking functionality according to the teachings of the present invention.

0065When a Microsoft Word^™ document is opened using the "mrCapture.dot" template, a new menu bar providing options for specifying information to be inserted into the notes document are added to the Microsoft Word^™ tool bar. <figref idref="f0003">Fig. 4</figref> depicts a section of a Microsoft Word^™ tool bar showing a menu bar 402 comprising user-selectable options for inserting portions of recorded information into a notes document according to an embodiment of the present invention. In the example depicted in <figref idref="f0003">Fig. 4</figref>, menu bar 402 comprises several buttons and toggles: button ("Insert") 404, button ("Calendar") 406, "Slide" toggle 408, "Audio" toggle 410, and "Video" button 412. The user can select "Slide" toggle 408 to indicate that the presently displayed slide should be inserted in the user's notes document. The position of the cursor within the notes document at the time when "Slides" toggle 408 is clicked indicates the position in the document where the slide is to be inserted. Likewise, the user can set "Audio" toggle 410 to indicate that an audio segment is to be inserted. Users can configure the length of audio clip to be inserted using pull-down menu 414 associated with "Audio" toggle 410. When the user clicks the "Insert" button 404, the specified information will be inserted in the user's notes document at the position of the cursor. It should be apparent that buttons and/or toggles for other types of information may be provided in other examples.

0066As previously described, a user can be authorized to access information from multiple sessions and can incorporate portions of recorded information from these sessions into the user's notes. Selecting ("Calendar") button 406 in <figref idref="f0003">Fig. 4</figref> brings up a dialog box 500 as depicted in <figref idref="f0004">Fig. 5</figref> that displays information regarding the various other sessions from which the user is authorized to access information according to an example. A calendar interface is displayed in <figref idref="f0004">Fig. 5</figref>. The user can select a range of dates from the calendar interface. As shown in <figref idref="f0004">Fig. 5</figref>, the user has selected a range of days including October 6, 2002 to October 11, 2002. A list of sessions 502 that a user is authorized to access within the selected range of days is displayed. Summary information for each session is displayed including the starting time of the recording included in the session, the duration of the session information, and the number of slides included in the session information.

0067While attending and taking notes for a presentation, the user can specify that a portion of recorded information from another presentation, which is stored as another session to which the user is authorized, be inserted into the user's notes. The user can specify the particular session from which information is to be inserted. For example, in <figref idref="f0004">Fig. 5</figref>, the user can select one of the sessions displayed in list 502. The user can then specify the portion of information to be inserted. For example, the user can specify a slide number to be inserted.

0068If the recorded information for user-selected session is accessible to the note-taking device used by the user, then the recorded information from that session may be displayed to the user on the note-taking device 108 and the user can then pick and chose the information to be inserted in the user's notes. The recorded information for the selected session may be stored by presentation server 104 and accessible to note-taking device 108 via server 104. In some examples, the recorded information for sessions which are authorized for the user may be downloaded to the user's note-taking device and cached in the note-taking device's memory. According to an example, the download may be performed when the user logs in and get authorized for accessing information recorded for the present presentation.

0069<figref idref="f0004">Fig. 6</figref> displays a user interface that allows a user to browse through previously recorded session information when the information is accessible to the user's note-taking device according to an example. Once the user has selected a session using the user interface depicted in <figref idref="f0004">Fig. 5</figref>, the user can select "Slide" tab 504 to bring up the user interface displayed in <figref idref="f0004">Fig. 6</figref> which displays slides recorded for the selected session. As shown, recorded slides are displayed in window 602. The user can browse through the slides using slider 604 or step through them one at a time using previous and next buttons 606. Several control buttons 608 are provided for inserting a slide or audio segment into the user's notes. Controls 610 are also provided for playing back the recorded information stored for the session. A slide counter 612 is also displayed.

0070If information for a selected slide is accessible to the note-taking device, either via presentation server 104 or cached on the note-taking device itself, the request for the selected slide is immediately processed and the requested data is inserted into the user's notes document. If the request information is not accessible, then the information request is cached in the notes document, and processed later when the requested information becomes accessible, as described above.

0071As described above, the user interfaces depicted in <figref idref="f0004">Figs. 5 and 6</figref>, and described above allow the user to specify information to be inserted into the user notes from previously recorded sessions which the user is authorized to access. The user interfaces can also be used to view and select information previously displayed during the present presentation that the user is attending and which is stored as part of the current session. For example, using the interface depicted in <figref idref="f0004">Fig. 6</figref>, the user can step back through slides that have already been displayed in the presentation the user is attending and select a slide for insertion in the user's notes. As new slides are displayed during the presentation, slide counter 612 is updated to include the new slides.

0072<figref idref="f0005">Fig. 7A</figref> depicts a Microsoft Word™ interface 700 that has been configured to provide options for taking notes according to an embodiment of the present invention. Interface 700 displays a section 702 of a user's notes document. As shown, a visible marker 704 is displayed in the notes document corresponding to an information request that has not yet been processed and is accordingly stored or cached in the notes document. Visible marker 704 is placed in a location where the information requested by the cached information request is to be inserted. Visible marker 704 provides a context of the requested information such as "[mrRequest1: To be inserted slide4 from 13:09:23 10/1/0/02]". The user may have requested the information to be inserted dialog window 706 (which is similar to the user interface depicted in <figref idref="f0004">Fig. 6</figref> and described above). The information request is stored in the notes document until the request can be processed, i.e., the information requested by the request can be accessed and inserted into the notes document.

0073<figref idref="f0006">Fig. 7B</figref> depicts the notes document of <figref idref="f0005">Fig. 7A</figref> wherein the cached information request has been processed according to an embodiment of the present invention. As shown, a slide 708 corresponding to the cached information request has been inserted into the notes document at the specified location. Visible marker 704 has accordingly been automatically removed and replaced by the requested slide 708. Audio information associated with the inserted slide has also been inserted into the notes document as indicated by icon 710. The user can playback the audio segment by clicking or selecting icon 710.

0074As described above, the code modules that provide the functionality needed to support user information requests for inserting portions of recorded information in the user's notes may be implemented in Visual Basic for Applications (VBA) that is supported as part of the standard Microsoft Office Suite^™. Several code modules may be provided. For example, a "user request module" may be provided that provides the functionality needed to support user information requests such as inserting slides, audio segments, and so on. The "user request module" may interact with different types of objects including a Word document object, a user request object, and a presentation or session object.

0075According to an embodiment of the present invention, the user request object is a class object that handles creation of a user information request (e.g., a request created using the interfaces depicted in <figref idref="f0004">Figs. 5 and 6</figref>), processing the user information request to obtain the requested information and inserting the information in the notes document, caching the request when it cannot be processed, and loading in cached requests during module startup. The session object comprises information about presentations (or sessions) and is configured for formulating a query for the information request, communicating the query to the presentation server 104, receiving requested information from the presentation server 104, managing cached sessions on the note taking device, and processing of login keys. The Word object is part of the Microsoft Office Object Model that is provided for manipulation of document elements.

0076<figref idref="f0007">Fig. 8</figref> is a simplified block diagram of a note-taking device 108 that may be used to perform processing according to an example. As shown in <figref idref="f0007">Fig. 8</figref>, note-taking device 108 includes at least one processor 802, which communicates with a number of peripheral devices via a bus subsystem 804. These peripheral devices may include a storage subsystem 806, comprising a memory subsystem 808 and a file storage subsystem 810, user interface input devices 812, user interface output devices 814, and a network interface subsystem 816. The input and output devices allow user interaction with data processing system 802.

0077Network interface subsystem 816 provides an interface to other computer systems such as presentation server 104 and authorization device 116. The networks may include the Internet, a local area network (LAN), a wide area network (WAN), a wireless network, an intranet, a private network, a public network, a switched network, or any other suitable communication network. Network interface subsystem 816 serves as an interface for receiving data from other sources and for transmitting data to other sources from note-taking device 108. For example, note-taking device 108 may send information requests to presentation server 104 and receive the requested information from presentation server 104 via network interface subsystem 816. Embodiments of network interface subsystem 816 include an Ethernet card, a modem (telephone, satellite, cable, ISDN, etc.), (asynchronous) digital subscriber line (DSL) units, and the like.

0078User interface input devices 812 may include a keyboard, pointing devices such as a mouse, trackball, touchpad, or graphics tablet, a scanner, a barcode scanner, a touchscreen incorporated into the display, audio input devices such as voice recognition systems, microphones, and other types of input devices. In general, use of the term "input device" is intended to include all possible types of devices and ways to input information to note-taking device 108. A user may use user input devices 812 to take notes.

0079User interface output devices 814 may include a display subsystem, a printer, a fax machine, or non-visual displays such as audio output devices. The display subsystem may be a cathode ray tube (CRT), a flat-panel device such as a liquid crystal display (LCD), or a projection device. In general, use of the term "output device" is intended to include all possible types of devices and ways to output information from note-taking device 108.

0080Storage subsystem 806 may be configured to store the basic programming and data constructs and modules that provide the functionality of the present invention. For example, software modules such as authorization module 118 may be stored in storage subsystem 806. These software modules may be executed by processor(s) 802. Storage subsystem 806 may also provide a repository for storing data used in accordance with the present invention. For example, the notes documents, cached sessions information, etc. may be stored in storage subsystem 806. Storage subsystem 806 may comprise memory subsystem 808 and file/disk storage subsystem 810.

0081Memory subsystem 808 may include a number of memories including a main random access memory (RAM) 818 for storage of instructions and data during program execution and a read only memory (ROM) 820 in which fixed instructions are stored. File storage subsystem 810 provides persistent (non-volatile) storage for program and data files, and may include a hard disk drive, a floppy disk drive along with associated removable media, a Compact Disk Read Only Memory (CD-ROM) drive, an optical drive, removable media cartridges, and other like storage media.

0082Bus subsystem 804 provides a mechanism for letting the various components and subsystems of note-taking device 108 communicate with each other as intended. Although bus subsystem 804 is shown schematically as a single bus, alternative examples of the bus subsystem may utilize multiple busses.

0083As previously stated, note-taking device 108 can be of varying types including a personal computer, a portable computer, a laptop, a kiosk, a PDA, a tablet PC, and the like. The description of note-taking device 108 depicted in <figref idref="f0007">Fig. 8</figref> is intended only as a specific example. Many other configurations having more or fewer components than the system depicted in <figref idref="f0007">Fig. 8</figref> are possible.

0084Although specific embodiments of the invention have been described, various modifications, alterations, alternative constructions, and equivalents are also encompassed within the scope of the invention. The described invention is not restricted to operation within certain specific data processing environments, but is free to operate within a plurality of data processing environments. Additionally, although the present invention has been described using a particular series of transactions and steps, it should be apparent to those skilled in the art that the scope of the present invention is not limited to the described series of transactions and steps.

0085Further, while the present invention has been described using a particular combination of hardware and software, it should be recognized that other combinations of hardware and software are also within the scope of the present invention. The present invention may be implemented only in hardware, or only in software, or using combinations thereof.

0086The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that additions, subtractions, deletions, and other modifications and changes may be made.