Browse Prior Art Database

MESSAGE THREAD NAVIGATION

IP.com Disclosure Number: IPCOM000126829D
Publication Date: 2005-Aug-15
Document File: 1 page(s) / 22K

Publishing Venue

The IP.com Prior Art Database

Abstract

System and Method of navigating message threads When reading pin or email messages, users typically move between the message they are currently viewing, and the next or previous message. Users also like to move to the next unread message. When viewing a particular message, users would also like to see other messages on the message thread prior to taking action on questions in this message. This is to prevent replying to the message with the same response as another recipient. Presently, this can be achieved in two different ways: one can use the current functionality to move between the next and previous messages. This method is awkward because there may be many other messages that the user has to navigate through before getting to the next/previous message in the thread. The other method is searching the message list based on the subject of the message. This will show all of the messages in the message thread on a separate screen, which the user can navigate through using next and previous hotkeys. This way is awkward too, since it requires additional steps, and moving to the next message thread is time consuming since a new search has to be completed. The solution does not require any sorting and keeps the messages in the order in which they were received. This solution provides a way for the user to easily and quickly move to the previous or next message without having to other unrelated messages or doing a manual search. This is done automatically by the system when requested by the user. Current implementation allows moving to the next or previous message in the thread using hotkeys. An addition or alternate implementation could provide verbs on the menu. For the system to determine the next or previous message in the thread, the inventor(s) use the subject of the message. First, the original subject is extracted from the message that the user is currently viewing. This is done by removing any prefixes to the subject. Then, the next or previous message from the message list is located. Its original subject is then extracted. A comparison is done between the two subjects. If they match, the message is probably in the same thread and the user is then taken to that message. If they do not match, the user continues by looking at the next message in the message list until a matching subject is found. When located, the user is automatically taken to that message, while irrelevant messages are skipped over. When the user gets to the top of the message of the message list, they are taken to the oldest message in the thread. When they get to the bottom, they are led to the newest message in the thread. If one of the hotkeys is invoked and there are no other messages in this thread, a notification is given to the user.

This text was extracted from a Microsoft Word document.
This is the abbreviated version, containing approximately 53% of the total text.

MESSAGE THREAD NAVIGATION

System and Method of navigating message threads

Disclosed Anonymously

When reading pin or email messages, users typically move between the message they are currently viewing, and the next or previous message.  Users also like to move to the next unread message.  When viewing a particular message, users would also like to see other messages on the message thread prior to taking action on questions in this message.  This is to prevent replying to the message with the same response as another recipient. 

Presently, this can be achieved in two different ways: one can use the current functionality to move between the next and previous messages.  This method is awkward because there may be many other messages that the user has to navigate through before getting to the next/previous message in the thread. 

The other method is searching the message list based on the subject of the message.  This will show all of the messages in the message thread on a separate screen, which the user can navigate through using next and previous hotkeys.  This way is awkward too, since it requires additional steps, and moving to the next message thread is time consuming since a new search has to be completed.  The solution does not require any sorting and keeps the messages in the order in which they were received.

This solution provides a way for the user to easily and quickly move to the previous or next message without having to other unrelated messages or doing a...