The present invention generally relates to notification regarding posts in an ongoing digital conversation in a collaborative environment.
Instant messaging (IM) and collaboration applications provide real-time text communication, often called “posts” or “chats”, between two or more participants, thereby supporting a “digital conversation” between the participants over a communications network, such as, for example, the Internet. Such applications often support maintaining the continuity of an ongoing digital conversation between its participants by saving the communications as they are sent as a conversation's “history”. Some or all of the digital conversation's history may be presented or made accessible to the participants when accessing a given conversation, typically, in reverse chronological order as per the time each post was contributed to the digital conversation.
The present invention will be understood and appreciated more fully from the following detailed description, taken in conjunction with the drawings in which:
A method for providing a notification of a conversation post in a digital conversation is implemented on a computing device and includes: presenting at least one conversation post from the digital conversation on a display screen of the computing device, detecting selection of the at least one conversation post for the notification, enabling selection of at least one receiving conversation participant to receive the notification, and sending the notification to the at least one receiving conversation participant.
A method for presenting notifications for conversation posts in a digital conversation is implemented on a computing device and includes: receiving at least an indication of at least one user-initiated notification for a conversation post in the digital conversation, presenting the at least an indication on a display screen of the computing device, receiving a selection of the at least one user-initiated notification, opening the digital conversation, and displaying at least the conversation post.
It will be appreciated that digital conversations may be asynchronous. Although conversation posts may be provided in real-time or near real-time, conversation participants may often not access or read a given conversation post until sometime later. As collaboration applications, such as, for example, Cisco Spark, may support the participation of hundreds (or even more) participants in a given group conversation, the volume of conversation posts over time may render it difficult or impractical for some of the conversation participants to read each conversation post in the group conversation. Accordingly, if a given conversation post was intended to be addressed to a specific conversation participant within the context of the group conversation, it's possible that the specific conversation participant may not actually read the given conversation post.
In accordance with embodiments described herein, digital conversation applications may be implemented with functionality to facilitate one conversation participant notifying one or more other conversation participants regarding a specific conversation post that may be presumed to be of interest to the conversation participant thusly notified. Reference is now made to
Display 100 depicts an exemplary ongoing digital conversation and comprises conversation posts 110A-E, which have been contributed by participants of the digital conversation. In accordance with an exemplary embodiment described herein, the user of display 100 may wish to notify one or more of the other conversation participant about conversation post 110D, i.e., to bring conversation post 110D to the attention of one or more of the other conversation participants. To do so, the user, may select conversation post 100D. As depicted in
Reference is now made to
Reference is now made to
It will be appreciated that a collaboration application such as that depicted in the exemplary embodiments of
Display 301 may also comprise notification indicator 320. As depicted, notification indicator 320 appears displayed next to selectable conversation name 310B (i.e., CLOUD MEDIA GROUP). In accordance with embodiments described herein, notification indicator 320 may indicate that there is a notification waiting for the user in the associated conversation (i.e., the CLOUD MEDIA GROUP conversation). As depicted, notification indicator 320 comprises a “plus-one” in a circle, thereby indicating that there is one notification for the user in the associated conversation. It will be appreciated that notification indicator 320 may comprise other numbers to indicate multiple notifications in a conversation. Similarly, display 301 may comprise more than one notification indicator 320, where each notification indicator 320 may be associated with a different conversation.
Reference is now made to
In accordance with some embodiments described herein, the icon representing the collaboration application may be modified to indicate to the user that one or more notifications have been received. For example, a number may be superimposed on the application icon (e.g., as presented on a desktop or home page, depending on the device), similar to notification indicator 320. In accordance with some embodiments, the priority of the associated notification(s) may be indicated by a background color or shading. For example a heat map may be defined to reflect a gradual progression from low to high priority, e.g., green may indicate low priority, whereas red may indicate high priority. It will be appreciated that depending on the implementation, other colors may be used. It will also be appreciated that background colors and/or shading may be used in a similar manner to indicate priority notification indicator 320.
Reference is now made to
Reference is now also made to
It will be appreciated by one of skill in the art that computing device 500 comprises hardware and software components that may provide at least the functionality of the embodiments described herein. For example, computing device 500 may comprise at least processor 510, I/O module 420, display screen 530, and collaboration client application 540. I/O module 520 may be implemented as a transceiver or similar means suitable for transmitting and receiving data between computing device 500 and another device. Such data may be, for example, conversation posts 110 (
Collaboration client application 540 may be any suitable application implemented in software and/or hardware that may be operative to facilitate a user's ongoing participation in a digital conversation as described hereinabove. For example, collaboration client application 540 may be implemented as Cisco Spark®. It will, however, be appreciated that collaboration 540 may be implemented as any suitable IM, collaboration, and/or social network application that supports ongoing digital conversations between multiple participants, such as, for example, Jabber®, WhatsApp®, or Facebook®.
It will be appreciated that computing device 500 may comprise more than one processor 510. For example, one such processor 510 may be a special purpose processor operative to execute collaboration client application 540. Collaboration client application 540 comprises notification module 545. Notification module 545 may be implemented in software and/or hardware and may be employed as necessary by collaboration client application 540 to input, modify, delete and/or present notifications for digital conversation communications transmitted/received by collaboration client application 540, typically via I/O module 520. It will be appreciated by one of ordinary skill in the art that some or all of the functionality of notification module 545 may be implemented on a collaboration server (not shown) that may be configured to facilitate collaborative communications between collaboration applications 540 on different computing devices 500. For example, the collaboration server may store some or all of the digital conversation history displayed in displays 100 and/or 400 as described hereinabove. The collaboration server may also perform indexing of the digital conversation and associated notifications in order to provide notifications and/or associated participation posts for display by collaboration client application 540 and/or notification module 545.
Reference is now also made to
Collaboration client application 540 displays (step 610) a group conversation with conversation posts 110 such as depicted in
In response to the detection of such user input, notification module 545 may display (step 630) conversation participant selection window 200 as per the embodiment of
Collaboration client application 540 may then employ I/O module 520 to send (step 650) the notification details (i.e., the selected conversation post 110, the selected group members, and/or priority) to the selected group members.
In accordance with some embodiments described herein, process 600 may be implemented to facilitate the annotation of a given notification. For example, process 600 may support user input of a text message to be provided along with the notification. Alternatively or in addition, process 600 may support recording of a voice message and/or the recording/uploading of a video clip to be provided along with the notification.
Reference is now also made to
Collaboration client application 540 displays (step 710) an indication of one or more notifications. For example, collaboration client application may add an indication to its associated application icon, as described hereinabove. Alternatively or in addition, an indication may be added to display 301 as per
Notification module 545 may receive selection (step 720) of the associated conversation to display. Such selection may be input, for example, as a UI gesture, textual input, etc., and may be performed as described with respect to
Collaboration client application 540 displays (step 740) the noted conversation post, for example, conversation post 110D′ as per the embodiment of
As discussed hereinabove, process 600 may support the provision of an annotation along with the notification. For example, a text message, voice message, and/or video clip may be provided along with the notification. It will be appreciated that process 700 may be implemented to facilitate the presentation of such an annotation to a viewing participant of the digital conversation.
It will also be appreciated that there may be more than one notification associated with a given conversation. Accordingly, collaboration client application 540 may also be operative to navigate within the conversation in order to display additional noted conversation posts. In accordance with some embodiments described herein, the user may access a table of such noted conversation posts, similar in structure to that of table 302, and select from among the noted conversation posts in the table in order to navigate within a given conversation. Furthermore, in accordance with some embodiments described herein, in the event that a conversation has multiple noted conversation posts where the priorities are not all the same, the priority indication (e.g., background color or shading) may be defined to default to indicate either the highest, lowest, or average priority.
It will be appreciated that some collaboration applications may autonomously notify conversation participants when a new conversation post is added to a digital conversation. However, the embodiments described herein support user initiated notification of specific conversation posts, even if the specific conversation posts have been previously presented to the participants of the digital conversation, i.e., the application had already sent out a new conversation post notification at some point in the past.
It is appreciated that software components of the present invention may, if desired, be implemented in ROM (read only memory) form. The software components may, generally, be implemented in hardware, if desired, using conventional techniques. It is further appreciated that the software components may be instantiated, for example: as a computer program product or on a tangible medium. In some cases, it may be possible to instantiate the software components as a signal interpretable by an appropriate computer, although such an instantiation may be excluded in certain embodiments of the present invention.
It is appreciated that various features of the invention which are, for clarity, described in the contexts of separate embodiments may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment may also be provided separately or in any suitable subcombination.
It will be appreciated by persons skilled in the art that the present invention is not limited by what has been particularly shown and described hereinabove. Rather the scope of the invention is defined by the appended claims and equivalents thereof: