Elias Torres wrote:
A few presentation notes that I think are applicable to our work:
Tags don't map well to SQL. Sometimes you can prune based on usage -
only index the first few pages for example. This keeps indexes small and
fast."""
My suggestion: use the minimum SQL required to assign synthetic IDs and
map relationships. But for querying a large corpus, don't bother with
SQL. The lucene jar is already in roller... use it.
1 - Data model and back-end changes to support storing and querying via
tags
2 - Changes to Weblog Editor page to allow entry of tags
3 - Changes to Weblog Entry management page to allow tag queries
4 - A tag cloud macro suitable for use in weblog pages
5 - A tag cloud macro suitable for use on the front page
6 - A Servlet to provide tag based weblog and site wide RSS/Atom feeds
7 - A tag query page suitable for use on front page
...
2) define the specific feeds that will be supported. This is related to
the better URLs discussion too.
I'm not sure this is an option. We just need to suck it up and make it
work instead of "allowing" specific feeds, etc.
>From Joshua's presentation: **Put RSS everywhere you can**
"""RSS important in del.icio.us, because it's a native way for people to
access lists (of links). Put RSS everywhere you can. del.icio.us does
way more RSS traffic than HTML or API stuff - partly because of poorly
written readers. Understand the headers - especially if-not-modified."""
Shouldn't each query use case for different clouds (tag occurrence
histograms) and streams (posts from one blog or groups/all blogs) be
backed by manager signatures that make the presentation (cloud markup,
rss, atom, json, etc) and URL incidental?
-Ian
--
Ian Kallen || Architect, Technorati Inc. || m: 415.505.5208
http://www.arachna.com/roller/page/spidaman
