Okay, (small rant to follow) does it bother anyone else that app-makers interpret Apple's guidelines of limiting the locations of application-written files etc. to 'Application Support,' 'Preferences,' or 'Documents' as 'put everything in the damn Documents folder?'

Its just kind of anti-social behavior on the part of developers makes it hard for users to keep documents in their Documents folder. I, for one, have done my best to keep non-documents out of my Documents folder. Microsoft apple division, I hate you for putting 'Microsoft User Data' in my Documents folder. you suck. Keep your nasty data files where they belong. And you others...you know who you are. Shape up.

Seriously, guys, if something is a database app, like DevonThink or Delicious Library, what is documenty about the database file itself?!? (More, and more serious stuff, after the break..)

So, I have decided to stop whining about how the tools 'just are not there' or 'just have so many shortcomings'.

From now onward, I am building a system - a dependable (ok, ill settle for pretty reliable and mostly stable) environment within which tailored workflows can be semi-automated to the best of my ability, and to the furthest extent possible with the available tools...

As I read through a text (I've remarked on the paper-to-digital conversion process elsewhere) I want to be able to highlight and capture whole swaths of text.

It is critically important to repurposing my captured snippets (bits, fits, blobs, fragments, portions) that I am able to recontextualize them easily.

How can this recontextualization happen?

First; the bibliographic information must be embedded in each bit.

Also, its relative location in the linear flow of the text must be recorded, so as to be able to quickly pull up various degrees of context around the bit.