Generally, users have to visually scan the whole history (maintained as a recency list) to locate the item of interest. It might be difficult for the user to recognize the page representation (page title or URL) as it might not match with how the person remembers the page. Bookmarking a page is something people have to do explicitly. Therefore, it requires a separate decision from the user to bookmark a page or not. Also maintaining a cluttered list of bookmarks becomes a separate concern.

If all the visited pages are kept in a single storage by integrating the history and bookmarks, the user can directly search and access those pages from that storage. And if the person remembers in hindsight that the page should have been bookmarked, he can do it later from the history. This will also eliminate the need for maintaining the highly cluttered list of bookmarks (which might contain stale and useless links).Moreover, if a good unified user interface is available, it eases and speeds up the search for the then required page.

So, the integration of bookmarks and history will not only enable the user to dynamically perform a search for the revisit, but integrating this integration (bookmarks + history) with Xesam can also be facilitated. Then, Xesam can be used to perform a wide search on the person's system from the central object pool of bookmarks + history alongwith other places on the GNOME desktop.This would also increase the usability of the desktop search and metadata services depending upon the user's interests.

More info on:

Outreach/SummerOfCode/2008/Ideas/CompleteBookmarkHistoryIntegration (last edited 2013-12-03 18:32:29 by WilliamJonMcCann)