Abstract:
A message viewer for generating a prioritized view of a plurality of messages stored in an email mailbox is disclosed. The viewer includes a script for defining one or more concepts against which a message can be prioritized, the or each concept comprising one or more conditions against which a message can be tested. A display script operates on each message, to generate a fit to a selected one or more of the concepts, the fit corresponding to whether or not the message fulfils the conditions. Once complete, the display script creates a display representative of the respective fits of the messages to the one or more selected concepts.

Description:
BACKGROUND OF THE INVENTION 
   1. Field of Invention 
   The present invention relates to an improved display aimed at assisting a user in the prioritisation of effort applied to reading and responding to messages. 
   2. Description of the Related Art 
   Email systems generally provide the user with a number of core directories, or folders, which usually comprise: an inbox to which all new messages are added; an outbox containing those messages which have been sent; and a deleted or trash folder containing recently deleted messages—once an update, such as a replication with a server, has been requested this folder is usually emptied. 
   In addition to these folders, users are usually provided with the ability to create hierarchies of new folders, for example one for each of their different work activities, and store emails in those folders and sub-folders. Traditionally, the user is provided with the ability to view summary information for a list of the email messages in a folder. The summary information includes: the originator of the message; the subject heading; and the date and time of receipt. 
   In addition to this information, some email systems, such as Lotus Notes, enable the user to allocate categories to a message such as: urgent; for your information; or company confidential. These additional categories are also shown when viewing the summary information for email messages in each folder. For example, Lotus Notes displays those messages flagged as urgent with a red exclamation mark alongside them. 
   A challenge being faced by the many email recipients, particularly in the commercial sector, is that the volume of email received is increasing. In some extreme cases email recipients may receive in excess of a hundred messages a day relating to any one of their ongoing work activities. Some email systems are providing agent based capabilities which automatically filter email to reduce the volume of apparently unactioned messages. 
   Nonetheless, in deciding how to deal with messages, recipients face the following problems: it is difficult to prioritise the actioning of messages. This is because reading email is time consuming, especially when very large numbers of messages are received, and simply scanning the directory lists represents an ineffective approach to prioritisation. For example, unimportant messages are occasionally flagged as urgent whilst very important messages may be received from an unknown sender with no subject listed; the current email display mechanisms, in particular those which use folders and lists of message, do not necessarily represent the recipient&#39;s priorities; not all email requires immediate action and in some cases a recipient may wish to take time to consider a response. In such case the email must either be filed or it gradually drifts down the email display. In either case it is possible to forget a response; messages are occasionally filed incorrectly and are then overlooked in subsequent reviews; and email psychology tends to focus individuals on maintaining a tidy inbox as opposed to an effective prioritisation of work activity. 
   It is an object of the present invention to provide an improved display aimed at assisting users in prioritisation of work through the use of message priority definition and graphical display of prioritised messages. 
   Accordingly, the invention provides a method for generating a prioritized view of a plurality of messages, comprising the steps of: defining one or more concepts against which a message can be prioritized, the or each concept comprising one or more conditions against which a message can be tested; for each message, generating a fit to a selected one or more of said concepts, said fit corresponding to whether or not said message fulfils said conditions; and creating a display representative of the respective fits of said messages to said one or more selected concepts. 
   While the problems addressed by the invention are described in terms of email messages, it will be seen that the invention can be applied to the prioritisation of work associated with messages of any type. 
   Nonetheless, in relation to email systems, a discussion thread is the term used for the group of messages resulting from users replying to messages received from another user. Some email systems provide functionality enabling the user to view the summary information of messages grouped in discussion threads. In a preferred embodiment of the present invention, the messages are grouped into discussion threads before being displayed according to the invention. 

   
     BRIEF DESCRIPTION OF THE DRAWINGS 
     Embodiments of the invention will now be described with reference to the accompanying drawings, in which: 
       FIG. 1  is a block diagram of an email system; 
       FIG. 2  is a flow diagram of a portion of a script for graphical display of prioritised messages; 
       FIG. 3  shows a priority definition dialog box; 
       FIG. 4  shows messages displayed with a variation in colour; and 
       FIG. 5  shows messages displayed with a variation in size. 
   

   DESCRIPTION OF THE PREFERRED EMBODIMENT 
   Referring now to  FIG. 1 , where a preferred embodiment of the invention based on a Lotus Notes mailbox is described. The Lotus Notes mail box is one of many applications capable of running on Lotus Notes. In Lotus Notes, the mailbox is a database in which each message is an object having a plurality of attributes, for example, “Body” includes the text of a message and “Subject” includes the subject line. While other email applications may not be strictly based on a database core, messages can nonetheless be thought of as individual objects having identifiable attributes, such as To, From, Subject, Body and Date. 
   In common with other Lotus applications and also Microsoft applications, a scripting language is provided within the Notes environment, enabling an application developer to either develop applications from scratch or to customise existing applications such as the mailbox. 
   In Lotus Notes, the scripting language, LotusScript, is used. Nonetheless it can be seen that the invention can be deployed within any email product using for example Visual Basic macros for Microsoft Exchange. Alternatively, the invention may be implemented as an integral part of any email product, using the API of the product. 
   In the preferred embodiment, two scripts are provided:
         a criteria generating script which enables a user to interactively enter a prioritisation definition; and a display script which accesses email messages, divides the messages into groups, parses the messages, applies the prioritisation definitions to the results of the email parsing and displays those results graphically for subsequent retrieval by the user.       

   In a preferred embodiment of the invention, the user may either be viewing one of the core folders, for example, the inbox, or one of a number of user defined folders. A button or icon is provided enabling the user to select a prioritized view generated according to the invention. 
   In the preferred embodiment, the display script responds to the button or icon being selected, to first group messages appearing in the currently viewed folder into discussion threads. 
   In Lotus Notes, every message has a unique identifier. A message which is a response to an outgoing message includes a $REF attribute which stores the unique identifier of the outgoing message. More than one response to an outgoing message may be stored in an in-box and responses may in turn be replied to leading to hierarchical groups of messages in a discussion thread. 
   With reference to  FIG. 2 , the display script groups messages by looping through all messages in the folder currently being viewed. The script initially determines if a message is an original message or a response, step  20 . If the message is a response, (even if it had been an originator for another message), the script checks for the originating message by searching in the currently viewed folder for a message having the identity stored in the $REF attribute, step  22 . A table  24  is then used to determine the next course of action. In the table, N/A means that either the current message is an original, so there is no originating message, or if the current message is a response, the originating message was not found. 
   If the current message is an original or if there is no message in the folder with an identity matching the $REF attribute, a new group is allocated and the current message added to the group, steps  26  and  32 . If the originating message is found and neither message is in a group, the response message and the original message are added to a new group, steps  28  to  32 . If the originating message is found and is already in a group and the current message is not in a group, the current message is added to this group, step  32 . If the current message is in a group and the originating message is not in a group, then the originating message is added to the group, step  34 . If both the current and originating messages are in groups, then the groups, if different, are merged, step  36 . Finally, if the current message is grouped and an originating message is not available, nothing needs to be done. 
   It will be seen that messages may in fact be related although they may not be in such rigidly defined discussion threads, and this may result in an unnecessarily large number of groups being generated. 
   It is therefore preferable that groups containing more than one message, discussion thread groups, should be used as seed groups with which groups containing fewer messages might possibly be merged, single message groups. 
   A number of criteria can be used to merge groups. Groups can be merged if, for example:
         a substantial portion of the subject line of a single message group appears in any message of a discussion thread group; or   the sender or recipient (according to whether the message was received or sent by the mailbox owner) of a message in a single message group matches one or more names in the From or To lines in any message of a discussion thread group.       

   In any case, it is preferable to provide a “No Category” group for messages that remain in single message groups. At a later stage the user may manually transfer messages from the “No Category” group to any of the other groups or create a new group. 
   Groups can be simply given numerical names such as “Discussion Thread #n”, or the display script can use some analysis of the subject lines or senders/recipients of messages within a group to determine a meaningful name. For example, if the same or mostly the same subject line is used in most messages in a group, this can provide the name of the group; or the messages are all received or sent to one other person, that person&#39;s name can be used. 
   Groups can be further merged if, for example, groups of keywords are either manually associated with a group by a user or if they are automatically extracted from the respective Bodies of messages in a group. Thus, if the same keyword is associated with more than one group, those groups can be merged. 
   This leads to an alterative manner of grouping messages which can be particularly useful where the user is looking at messages that are stored in hierarchical folders. In this case, the display script simply groups messages according to the folder in which they are stored, or if the user is looking at messages in a folder, messages can be grouped according to sub-folder. It should be seen that in this case, the folder names also provide readily meaningful names for the groups. 
   Once messages are grouped, the display script now assesses each message against a pre-defined prioritisation concept. 
     FIG. 3  presents a schematic of a dialog box presented by the criteria generating script. The box enables a user to interact and define a series of concepts which are used to prioritize messages—clearly this needs to have been done, either by a user or supervisor—remotely or locally, before the user can meaningfully run the display script. 
   Nonetheless, in a typical interaction, the user right clicks with a mouse button on the Concept Name box and is presented with a pop-up menu allowing for addition, deletion, renaming etc. of a concept. For each concept, the user is able to specify one or more scenarios which determine the applicability of message to a concept. 
   In the present embodiment, the user can specify a number of conditions for a given scenario: 
   the name of the sender—enabling a recipient to rank the importance of individual email authors. The name could be specified as either an individual or a member of a certain group in an address book—assuming one is associated with the email application. 
   the occurrence of key phrases—in its simplest form this could include a client&#39;s name or a subject. A more complex mapping could include searches for words or phrases which represent more subtle concepts such as an argument between two team members. Examples of such phrases are, “strongly disagree” or “inappropriate action”.
 
the number of emails exchanged—indicating the intensity of activity in a particular group. It will be seen that in the message grouping phase described above, the system determines how many messages are associated with a given discussion thread. It is therefore useful, even if discussion threads have subsequently been merged into a single group, to keep track of the number of messages in the discussion thread to which a message belongs. A discussion thread containing a large number of messages may indicate a “hot” topic even within a group containing a large number of other messages.
 
the time since the last message in the group—indicating that a response is awaited from the user to an incoming message or from a member of the group to which the user sent a message. Again the message grouping phase can be adapted to provide for this condition, by noting the last message in a discussion thread hierarchy. A further check on the last person to contribute to the discussion thread and the specified recipients would enable some inference regarding the source of the delay.
 
   For the example in  FIG. 3 , the recipient has specified the three concepts: “Priority Project” (for example a project approaching acceptance), “Crisis Sale” (for example an opportunity where the Client is upset with the company) and “Dispute” (for example an argument within a group). For each of these concepts the recipient is able to define one or more scenarios where each scenario comprises a number of conditions. 
   In the case of  FIG. 3 , one of the scenarios representing the concept of a “Crisis Sale” has been defined using a combination of the 4 available conditions: 
   the Originator of the email is either a member of the sales team or a client. Membership of groups can be determined through comparison with the Users Address book which provides the facility to define address groups. 
   Alternatively the user could specify an actual email address. 
   the Body of the email includes the words “Upset” and “Endanger”. For example, this condition would be met if the Body of the email included the phrase, “at our last meeting the Client was very upset and stated that this development would endanger our future relationship”.
 
the number of emails field has been left blank. In this scenario the number of emails in the discussion thread is not considered significant as a single email can represent a business critical issue. In a scenario representing a “Dispute” the number of emails exchanged could be considered significant.
 
the last email exchange field has been set as greater than 1 day. In this scenario this indicates that a potential problem (Sales Crisis) has been identified, however no response has been forthcoming.
 
   The display script applies a simple, weighted voting scheme to calculate a fit to the conditions specified by the email recipient. The best fit corresponds to the highest priority mail and is represented using the Display Parameter which is also specified by the recipient in the priority definition dialogue box. 
   Thus, in the example of  FIG. 3 , where the user intends prioritizing the display of messages according to the concept of “Crisis Sale”, the display script compares each message against each of the three scenarios for the concept. In the present embodiment, the best fit from the three scenarios is taken as the final fit. Alternatively, the fit from the three scenarios could be aggregated to give the final fit. 
   The final step in defining a concept is to select a display parameter. In the present embodiment, the parameter can be either one of a number of colours, for example, red, green or blue; or size. It should be noted that the display parameter is the same for each scenario in a concept and as such the display parameter dialog box can alternatively be displayed in a separate window associated with the concept name rather than with the scenario conditions. 
   Use of a selectable display parameter enables a user to prioritize mail against more than one concept at a time or simply to select the display parameter for a single concept which they comprehend most readily. 
     FIG. 4  presents a schematic of a window produced by the display script where messages are divided into groups “No Category” and “Discussion 1 . . . 9” and displayed in cells extending from their associated group in date order from the newest on the left to the oldest on the right. In  FIG. 4 , mail is only prioritized against one concept, and it is the redness of the email cells (shown as shades of grey) which varies to reflect the fit to the concept definitions. In  FIG. 5 , it is the length of the cells which changes according to the fit. 
   If, however, the user wishes to prioritize against more than one concept, then one concept can be associated with size as a display parameter and another can be associated with a colour as a display parameter. This means that messages closely fitting more than one concept will be associated with large and red cells, and those of little significance will be associated with small and, say, pale pink cells. 
   Where the user wishes to prioritize against more than two concepts then a number of possibilities may be employed. It will be seen that where four boolean conditions are used, as in  FIG. 3 , a fit will have 16 different possible values. The system can set a threshold, say 13, above which a message becomes a fit, and below which it is not considered significant. The user can then associate at least two of the concepts with colours, however, it will be seen that only one concept at a time can usefully be associated with size. When a message is tested against a colour associated concept, the cell for that message is only displayed in that colour if it exceeds the threshold. Where a messages exceeds the threshold for two or more concepts, then the colour associated with the concept to which the message fits best is used for the cell. If the message fits two concepts equally, then the message&#39;s cell can be displayed in a mixed, hashed or flashing or other highlighted mode or simply one colour or the other may be chosen at random. Thus, the display will shows cells possibly of varying sizes and possibly with cells of differing colours. 
   In any case, it will be seen that the prioritized view can be displayed instead of, or complementary to, the conventional summary information list. 
   In the preferred embodiment, the prioritized view is interactive. In Lotus Notes, the message&#39;s unique identifier can be associated with its corresponding displayed cell. When the user clicks on the cell associated with a message, then an API call is made to display the message in a conventional manner, allowing the user to read and/or reply to the message. 
   Possible enhancements to the display include: 
   the addition of functionality to capture the users feelings about the scale of a concept&#39;s applicability and the application of Artificial Intelligence algorithms to develop more sophisticated criteria. This is analogous to the use of AI to understand a user&#39;s needs in searching the Internet and would make use of similar technology;
 
the addition of functionality to enable a manager to impose concept priorities. For example, a manager could state that all emails which referred to client relationships were of a higher priority than internal correspondence; and
 
the use of system monitoring techniques to reflect the level of effort expended by an individual on each group.
 
   It will be seen that the present invention can be applied to the process of prioritizing views of differing types of messages, not necessarily email messages by simply applying the steps of defining one or more concepts against which a message can be prioritized, generating a fit of a message to one or more of such concepts and creating a display representative of the fit of such messages to the concepts. For example, the invention can be applied to viewing messages in queues.