-------- Original Message --------
Ok, This one is totally web 2.0...
So, you start tagging these excerpts/chunks/bits of info, ok? You log
into chandler and tag a class-note transcription; or a paragraph you
find interesting from a web-site, from a blog, etc.; you log and tag a
random bit of info that you want to remember later. Then, you find
yourself having a big collection of data that you collected and tagged,
and that collection starts to grow from itself, because you start to
reexam data from inside Chandler, and adding new tag content to parts of
data once tagged as a whole. You may split that class-note transcription
in 5 parts, keeping the original data logged (the class-note
transcription of that day tagged, like i said, as a whole), but making
the paragraphs of the transcription new entries themselves, with new and
specific, tagging. You may make a new entry just of a phrase you
tag-logged into Chandler, a phrase that made and still makes part of a
bigger entry, but is, itself, so important that it demands to be an
entry itself, having altogether, more specific tagging.
You may pick two anterior entries of data you logged, and are
correspondent to the same subject, and merge them into a new entry,
having new tag content, or maybe having all the tags that once were
attributed to each entry. The anterior entry remains, though nothing
restricts the user from deleting it manually if he thinks that the
anterior/partial entries have no use in remaining independent.
So you start logging, de-logging, re-logging, split-logging, and
merge-logging info without any hierarchy.... this is where the new use
for Chandler comes in, because it may add a quirk to what we do today in
web-logging: It would be very useful, if there is a tool on Chandler,
that you can automatically post:
1) all the entries you have just filtered on Chandler's entries
visualizer. So, lets say, you filter the entires tagged <C++>
<PROGRAMMING> <TIPS> that were edited on the period of 1 year. Those
entries are visualized on your screen, and then you go to, lets say, the
TOOL menu, and select the option named "Blog currently enforced
entries". So, Chandler logs into the user's blog service and posts the info.
2) But lets say the user, for some reason, doesnt want to blog some
entries. So he select just the entries he wants to blog, right mouse
click on one of the tags just selected, and chooses the option: "Blog
selected entries".
Now, this might just put the use we currently make of blogs on
steroids... because on the long run, after his database grows, the
Chandler user may review all his data and publish a very big (if
desired) ammount of data on a few mouse clicks. It would be specially
bloga.licio.us if blogging services start to support tags... because, in
this case, the user may replicate his chandler database on a blog, if
desired. But of course, for a discerning user, it would be only
interesting to publish a portion of the database. If you come to think
of it, Delicious is nothing more than a blog of bookmarks....
Hope to hear from you. If this is compatible in some way to what you are
doing with Chandler, be free to fwd it to the design list!
- Paulo
