Embodiments are generally related to data-processing systems and methods. Embodiments also relate in general to the field of computers and similar technologies and in particular to software utilized in this field. In addition, embodiments relate to electronic messaging methods and systems thereof.
Modern computer systems allow for the interchange of data and resources through network environments. Electronic messaging systems, such as e-mail and instant messaging, for example, are widely utilized by individuals and businesses for providing a rapid, low cost means of communication. Certain electronic messaging systems provide a documented record of all communications sent to and from a particular user. While a user can create and send a message independent of any other messages, messages are often part of a message thread.
A message thread is a group of messages that are related to each other, such as when one message is a response to (e.g., a reply to or a forwarding of) another message. Messages in the same message thread typically share various common message data, such as related subjects or common message content. For example, a reply e-mail or voice-mail will often include the contents of the original message as well as additional contents specific to the reply and the subject line of a reply or forwarded e-mail will often include the original subject line along with a relation indicator such as “RE:” or “FW:” respectively.
Many times a group of individuals organized into, for example, a “helpdesk” or support team, may engage in an ongoing conversation with one another by sending e-mail messages related to the topic at hand. In most cases it is expected that each recipient will provide a response to the originator of the message. This can be easily accomplished by selecting a “Reply” function button in the recipient's e-mail application. However, when replies are returned to the originator of a message, the replies are returned individually and are displayed for the originator as separate messages, which are most often separated by other messages that have been transmitter from other parties to the originator.
Various techniques have been employed for organizing and displaying e-mail messages and e-mail threads.
Based on the foregoing it is believed that a need exists for an improved method and system for detecting and consolidating a user's e-mail box and converting e-mail messages associated with a thread into a forum-type list format, as described in greater detail herein.
The following summary is provided to facilitate an understanding of some of the innovative features unique to the present invention and is not intended to be a full description. A full appreciation of the various aspects of the embodiments disclosed herein can be gained by taking the entire specification, claims, drawings, and abstract as a whole.
It is, therefore, one aspect of the present invention to provide for an improved data-processing method, system and computer-usable medium.
It is another aspect of the present invention to provide for a method, system and computer-usable medium for detecting and consolidating an e-mail box and convert e-mail messages associated with a particular e-mail thread into a forum-type list format.
It is a further aspect of the present invention to provide for a method, system and computer-usable medium for providing improved viewing options with respect to e-mail messages.
The aforementioned aspects and other objectives and advantages can now be achieved as described herein. A computer-implemented method and system for dynamic e-mail view conversion is disclosed. An e-mail inbox capable of displaying one or more e-mail messages (e.g., a group of e-mail messages) associated with a particular thread can be dynamically consolidated. Thereafter, the e-mail messages associated with the particular thread can be converted into a forum-like list. One or more users can then be provided with varying viewing options with respect to the e-mail inbox in order to optimize the user(s) interaction with the e-mail inbox through the use of the forum-like list.
Related e-mail messages can be automatically traced, utilizing header and attribute data, and the e-mail messages then grouped together in a chronological order based on the time it took the user or users to view all replies. Each related e-mail can be tagged with a group ID and the information then stored into a file or repository to create a forum-like view based on defined preferences. Such an approach enables a user to read all replies into threads and view them in a single e-mail in any chronological order. In addition to or in lieu of chronological order, the e-mail messages can be grouped according to other criteria such as, for example, topic, date, recipient, work group, work owner, etc. The forum-like view can be provided as a local view and/or a server view.
Furthermore, the disclosed approach provides more viewing options and allows a user to predefine attributes information to search, find, aggregate, and group related e-mail. The sequences of related e-mail messages can be predicted utilizing a unique ID which can be some combination of timestamp, MAC address, etc. to make the ID unique. The sequence can also be predicted by considering other attributes such as, for example, subject line, recipient name and the order of response within each e-mail section. Several possible prediction techniques may be utilized with respect to the sequences of related e-mail methods. For example, e-mail “sections” or metadata can be analyzed. That is, by extracting metadata from the e-mail message, one can examine the chronological order of the metadata and use this information to make predictions. Another prediction technique involves analyzing the e-mail message subject and/or header to extract some level of information for prediction. Finally, one can utilize tagging in association with a rating table to provide for a prediction capability. A combination of a gradient factor and manual tagging with respect to the e-mail message can assist in prioritizing and more accurately predict a sequence of e-mail message(s).
The disclosed method and/or system stores the essential data in a centralized repository utilizing tagging of the information with respect to each e-mail/thread. The method/system then fetches the centralized repository to perform a query and leverage the result set to create different views that meet the needs of the user including views such as, for example, original, tree, or mind map.
Such an approach essentially changes the mailbox into a forum-like list with one entry for each topic so that every single mail related with a particular topic can be gathered, arranged and viewed in a more systematic manner. The list can be arranged, for example, according to the latest modified time which permits current discussion topics to be displayed and listed at the “top”. The user can view the entire chain of e-mail associated with a thread utilizing such a forum-like list format. The user can quickly sort, change view by tagged attributes, or dynamically merge e-mail messages to return to an original or a standard e-mail view.
The accompanying figures, in which like reference numerals refer to identical or functionally-similar elements throughout the separate views and which are incorporated in and form a part of the specification, further illustrate the present invention and, together with the detailed description of the invention, serve to explain the principles of the present invention.
The particular values and configurations discussed in these non-limiting examples can be varied and are cited merely to illustrate at least one embodiment and are not intended to limit the scope of such embodiments.
The interface 153, which is preferably a graphical user interface (GUI), also serves to display results, whereupon the user may supply additional inputs or terminate the session. In an embodiment, operating system 151 and interface 153 can be implemented in the context of a “Windows” system. Application module 152, on the other hand, can include instructions, such as the various operations described herein with respect to the various components and modules described herein such as, for example, the method 600 depicted in
In the depicted example, server 304 and server 306 connect to network 302 along with storage unit 308. In addition, clients 310, 312, and 314 connect to network 302. These clients 310, 312, and 314 may be, for example, personal computers or network computers. Data-processing apparatus 100 depicted in
In the depicted example, server 304 provides data, such as boot files, operating system images, and applications to clients 310, 312, and 314. Clients 310, 312, and 314 are clients to server 304 in this example. Network data processing system 300 may include additional servers, clients, and other devices not shown. Specifically, clients may connect to any member of a network of servers which provide equivalent content.
In the depicted example, network data processing system 300 is the Internet with network 302 representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, government, educational and other computer systems that route data and messages. Of course, network data processing system 300 also may be implemented as a number of different types of networks such as, for example, an intranet, a local area network (LAN), or a wide area network (WAN).
The following description is presented with respect to embodiments of the present invention, which can be embodied in the context of a data-processing system such as data-processing apparatus 100, computer software system 150 and data processing system 300 and network 302 depicted respectively
Embodiments of the present invention provide for methods, systems and graphical user interface data structures for detecting and organizing a thread of electronic messages in a manner that allows a user to read the message thread in a logical, succinct manner. As used herein, the term “message thread” refers to a group of electronic messages that are related to each other through a tag or other indicator that electronic messaging clients use to recognize electronic messages as being related. Typically, message threads occur in the context of an electronic “conversation” in which one or more users reply to an originating or root message one or more times. Note that the terms “e-mail” and “e-mail message” as utilized herein, can be utilized interchangeably.
The term “message thread” also contemplates that two or more participants in a conversation may branch off of a main e-mail message thread to create one or more side message threads. The e-mail messages in a message thread may include a variety of content. As used herein, the term “content” refers to any information included in the message body of an electronic message which can include, but is not limited to, text, graphics, images, sound, multimedia content, and the like. The organizational techniques employed herein relate to displaying a message thread which reduces or eliminates the duplication of content within the thread and allows a user to read through the message thread according to the conversational flow of the thread, as opposed to a chronological ordering of the messages.
The forum-like list can be configured to provide, for example, a single display of the message thread, which in turn provides the reader/user with the ability to view the content of all e-mail messages in the thread. By providing the content of the messages in a single display, the reader is not required to select multiple messages in order to read an entire e-mail message thread. Instead, the reader can “select” a single e-mail message thread to view, upon which the entire content of the e-mail message thread is displayed to the reader in a single display. Additionally, with such an approach, the user needs not to worry about missing replies in other threads. The latest reply can also be checked and confirmed with respect to, for example, whether the issue is being resolved.
Programs defining functions on the present invention can be delivered to a data storage system or a computer system via a variety of signal-bearing media, which include, without limitation, non-writable storage media (e.g., CD-ROM), writable storage media (e.g., hard disk drive, read/write CD ROM, optical media), system memory such as, but not limited to, Random Access Memory (RAM), and communication media, such as computer and telephone networks including Ethernet, the Internet, wireless networks, and like network systems. It should be understood, therefore, that such signal-bearing media when carrying or encoding computer readable instructions that direct method functions in the present invention, represent alternative embodiments of the present invention. Further, it is understood that the present invention may be implemented by a system having means in the form of hardware, software, or a combination of software and hardware as described herein or their equivalent. Thus, the method 900 described herein can be deployed as process software in the context of a computer system or data-processing system as that depicted in
Unique IDs for e-mail(s) in mailbox can be generated and can be set in the e-mail header, as depicted at block 910. The unique ID can be provided as, for example, a combination of a timestamp, a MAC address, etc. in order to render the ID unique. The unique ID associated with the e-mail message can be provided in the form of a unique combination of data, if the e-mail is the root of the e-mail thread, as depicted at block 920. The unique combination of the root e-mail can be appended to the unique ID of the corresponding reply or forwarded e-mail, as depicted at block 930. For example, if the e-mail is the root of the e-mail thread (i.e., the e-mail is not a reply or a forward e-mail), then its unique ID will only be the result of a unique combination.
The unique combination can be appended to the unique ID of the reply or forward e-mail and make the whole string as the unique ID of the e-mail, if the e-mail is not the root of the e-mail thread. In that case, the whole tree structure of the e-mail thread and the time of creation of each e-mail message can be traced and can also be known by the timestamp. Thereafter, e-mail messages that are initiated with the root e-mail message's unique ID can be automatically traced in order to form an e-mail thread tree, as depicted at block 940. Note that the operations described herein can be performed automatically by a computer. The actual selection depends on the metadata such as the unique ID described herein, which can be inserted into the e-mail header. The process of selection and composition into an e-mail tree can occur via separate operations. Thereafter, as depicted at block 950, an e-mail sequence can be predicted using the unique ID.
Note that the operation illustrated at block 950 involves utilizing one or more possible techniques for predicting the e-mail sequence. Such a sequence can also be predicted by considering header and attributes information such as, for example, subject line, recipient name and the order of response within each e-mail section and can be tagged with a group ID.
The sequences of related e-mail messages can be predicted utilizing a unique ID which can be some combination of timestamp, MAC address, etc. to make the ID unique. The sequence can also be predicted by considering other attributes such as, for example, subject line, recipient name and the order of response within each e-mail section. Several possible prediction techniques may be utilized with respect to the sequences of related e-mail methods and the operation depicted at block 950. For example, e-mail “sections” or metadata can be analyzed. That is, by extracting metadata from the e-mail message, one can examine the chronological order of the metadata and use this information to make predictions. Another prediction technique involves analyzing the e-mail message subject and/or header to extract some level of information for prediction. Finally, one can utilize tagging in association with a rating table to provide for a prediction capability. A combination of a gradient factor and manual tagging with respect to the e-mail message can assist in prioritizing and more accurately predict a sequence of e-mail message(s).
The information can then be stored into a file or repository, as depicted at block 960. Finally, the forum-like view (i.e., forum-like list) can be created based on the defined preferences, as depicted at block 970. The essential data can be stored in a centralized repository (e.g., database) or simply a file, utilizing tagging of the information in each e-mail/thread to perform a query and leverage the result set to create different views such as, for example, an original view, a tree view, or a mind map. Note that the forum-like view can be provided in the form of a local view or a server view. Following processing of the operation depicted at block 980, an operation to implement security aspects can be implemented. For example, a security privilege such as an ACL (Access Control List) can be embedded into the forum-like view (i.e., the forum-like list) as part of the process of converting to the forum-like view. Such a security privilege can, for example, determine who can access the records, how to limit the forum-like view or list and how to segregate data. Thereafter, as indicated at block 990, a filter may be applied to the forum-like view/list in order to filter list by, for example, topic, work groups, etc. For example, the filter can function to divide the incoming email messages into groups or departments who will handle topic 1, topic 2, etc.
E-mail messages related to “e-mail 1” can be selected, for example, utilizing a unique ID “T1” associated with each e-mail message. Hence, any e-mail message with a unique ID starting from “e-mail 1” will possess a unique ID belonging to the e-mail thread related to “e-mail 1”. A node can also be added to the e-mail message to render it into the e-mail thread tree. According to this unique ID, e-mail messages can be automatically selected, which relate to the same issue/topic. An e-mail thread tree can be composed utilizing the unique ID. The time of creation of each e-mail can also be identified by the time stamp included in the unique ID associated with the e-mail message(s). Hence, a related e-mail sequence can be predicted and displayed in a sequential order with respect to the e-mail thread.
Such an approach essentially changes the mailbox into a forum-like list with one entry for an issue so that every single mail related with the same issue can be gathered and arranged and viewed in a more systematic manner (i.e., forum-like view). The list can be arranged according to the latest modified time, which can place current discussion issues at the “top” of the list. The user can then view the entire e-mail chain associated with the thread utilizing the forum-like list format. With this approach, a user can quickly sort, change view via tagged attributes, or dynamically merge e-mail messages to return to an original or standard e-mail view.
Based on the foregoing, it can be appreciated that a number of advantages stem from implementing one or more of the disclosed embodiments. For example, prior art approaches are based mainly on the use of “subject (RE:)” which allows a user to decide if the particular e-mail message is related to another e-mail message. With the disclosed approach, however, the subject is not necessary—(RE). The e-mail message can be forwarded (FW:) or associated with the same subject. With the disclosed approach, one may desire to collect all related e-mail threads into a single forum-like view. This can be achieved by adding some additional header information in each e-mail message such as, for example, a particular serial number (e.g., PMR number).
Additionally, it is important to appreciate that the prior art approaches parse the content to form an email thread. In the scenario discussed herein with respect to
Another advantage of the disclosed embodiments over the prior art approaches, is that such prior art methods list only e-mail messages with respect to the time that the e-mail message was received. However, sometimes the discussion thread may separate into two or more discussions. Then, only a “list by time” can break the connection of each thread. For example, the configuration depicted in
The foregoing detailed description therefore describes a computer-implemented method and system for dynamic e-mail view conversion. An e-mail inbox capable of displaying one or more e-mail messages (e.g., a group of e-mail messages) associated with a particular thread can be dynamically consolidated. Thereafter, the e-mail messages associated with the particular thread can be converted into a forum-like list. One or more users can then be provided with varying viewing options with respect to the e-mail inbox in order to optimize the user(s) interaction with the e-mail inbox through the use of the forum-like list.
Related e-mail messages can be automatically traced, utilizing header and attribute data, and the e-mail messages then grouped together in a chronological order based on the time it took the user or users to view all replies. Each related e-mail can be tagged with a group ID and the information then stored into a file or repository to create a forum-like view based on defined preferences. Such an approach enables a user to read all replies into threads and view them in a single e-mail in any chronological order. In addition to or in lieu of chronological order, the e-mail messages can be grouped according to other criteria, such as, for example, topic, date, recipient, work group, work owner, etc. The forum-like view can be provided as a local view and/or a server view.
Furthermore, the disclosed approach provides more viewing options and allows a user to predefine attributes information to search, find, aggregate, and group related e-mail. The disclosed method and/or system also stores the essential data in a centralized repository utilizing tagging of the information with respect to each e-mail/thread. The method/system then fetches the centralized repository to perform a query and leverage the result set to create different views that meet the needs of the user including views such as, for example, original, tree, or mind map.
Such an approach essentially changes the mailbox into a forum-like list with one entry for each topic so that every single mail related with a particular topic can be gathered, arranged and viewed in a more systematic manner. The list can be arranged, for example, according to the latest modified time, which permits current discussion topics to be displayed and listed at the “top”. The user can view the entire chain of e-mail associated with a thread utilizing such a forum-like list format. The user can quickly sort, change view by tagged attributes, or dynamically merge e-mail messages to return to an original or a standard e-mail view.
While the present invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. Furthermore, as used in the specification and the appended claims, the term “computer” or “system” or “computer system” or “computing device” includes any data processing system including, but not limited to, personal computers, servers, workstations, network computers, main frame computers, routers, switches, Personal Digital Assistants (PDA's), telephones, and any other system capable of processing, transmitting, receiving, capturing and/or storing data.
It will be appreciated that variations of the above-disclosed and other features and functions, or alternatives thereof, may be desirably combined into many other different systems or applications. Also that various presently unforeseen or unanticipated alternatives, modifications, variations or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the following claims.