User talk:Eggfree: Difference between revisions
| Line 7: | Line 7: | ||
=== Proposing bookmarks=== | === Proposing bookmarks=== | ||
'''Develop a proposal of candidate links'''<br> | '''Develop a proposal of candidate links'''<br> | ||
*1) analyze browsing history to cluster page groups that are often browsed in sequence (for example I often view 'slashdot','nytimes',theinquirer' first thing in the morning) | *1) analyze browsing history to cluster page groups that are often browsed in sequence (for example I often view 'slashdot','nytimes',theinquirer' first thing in the morning) Assume the last week of history. | ||
*2) score pages in the current history by frequency of visitation and length of stay. | *2) score pages in the current history by frequency of visitation and length of stay. | ||
*3) aggregate page scores for pages in the same domain that cluster: | *3) aggregate page scores for pages in the same domain that cluster: | ||
| Line 13: | Line 13: | ||
**http://www.nytimes.com, | **http://www.nytimes.com, | ||
**http://www.nytimes.com/2005/11/15/international/asia/15cnd-flu.html all aggregate to score nytimes.com. | **http://www.nytimes.com/2005/11/15/international/asia/15cnd-flu.html all aggregate to score nytimes.com. | ||
*4) take the top 10 links that are not already bookmarks.This is a candidate list. | |||
'''Presenting the proposal'''<br> | '''Presenting the proposal'''<br> | ||
These three steps produce a set of likely bookmark candidates, and a set of groups. We can assume there is a list of existing bookmarks. We compare the existing bookmarks against our new proposal candidates. At the beginning of each browsing session we present these cadidates to the user for a "thumbs up" or "thumbs down" (think tivo) | These three steps produce a set of likely bookmark candidates, and a set of groups. We can assume there is a list of existing bookmarks. We compare the existing bookmarks against our new proposal candidates. At the beginning of each browsing session we present these cadidates to the user for a "thumbs up" or "thumbs down" (think tivo). | ||
"Thumbs up" makes it on the permanent list in the suggested group. "thumbs down" eliminates it from consideration and resets scoring for the candidate link and or cluster. no action preserves the item on the proposal list for as long the analysis of browsing habit suggest it is valid. | |||
* A candidate may be proposed when visiting the page, the same way warings and update notices are delivered via the yellow bar | * A candidate may be proposed when visiting the page, the same way warings and update notices are delivered via the yellow bar | ||
Revision as of 19:46, 15 November 2005
Design Topics
This page catalogs a set of design ideas and proposals for some current projects. I include a synopsis below each.
Bookmarking Various research leans to the idea that effective bookmark lists can be imputed and modified based on a users browsing habits then proposed, rather than requiring explicit actions. Thee are three steps in this bookmarking scheme: bookmark proposal, presentation, and editing.
Proposing bookmarks
Develop a proposal of candidate links
- 1) analyze browsing history to cluster page groups that are often browsed in sequence (for example I often view 'slashdot','nytimes',theinquirer' first thing in the morning) Assume the last week of history.
- 2) score pages in the current history by frequency of visitation and length of stay.
- 3) aggregate page scores for pages in the same domain that cluster:
- http://www.nytimes.com/pages/world/index.html,
- http://www.nytimes.com,
- http://www.nytimes.com/2005/11/15/international/asia/15cnd-flu.html all aggregate to score nytimes.com.
- 4) take the top 10 links that are not already bookmarks.This is a candidate list.
Presenting the proposal
These three steps produce a set of likely bookmark candidates, and a set of groups. We can assume there is a list of existing bookmarks. We compare the existing bookmarks against our new proposal candidates. At the beginning of each browsing session we present these cadidates to the user for a "thumbs up" or "thumbs down" (think tivo).
"Thumbs up" makes it on the permanent list in the suggested group. "thumbs down" eliminates it from consideration and resets scoring for the candidate link and or cluster. no action preserves the item on the proposal list for as long the analysis of browsing habit suggest it is valid.
- A candidate may be proposed when visiting the page, the same way warings and update notices are delivered via the yellow bar
- A candidate list may be proposed on a bookmarks page (home page) that may do some other fancy things (see bookmark presentation)
Presenting Bookmarks
Bookmarks are conventionally shown in a drodown menu and a toolbar. I'm not suggesting we change the toolbar mechanism , but I would suggest that the menu might change to a slightly different formatting, on the asumption that the bookmark proposal system would help edit the bookmark list to a more reasonable number (n < 30) or at least help. Last but not least I see bookmark editing as happening on the start page, which could become an editable "dashboard" of links and feeds.
- need to include dash snap *
- need to include menu snap *
Bookmarks to sites with rss feeds
Bookmarks to site clusters (say nytimes.com) where certain subpages are dominate the history/duration scoring.
Editing Bookmarks
Outside of the mechanisms for proposing bookmarks, bookmarks would be edited on the bookmark "dashboard"