This blog will contain my thoughts about document handling.
It will reflect my thoughts from a user perspective. I intend to post a little bit of history, a little bit of thoughts about what I would love to have available to me to be more productive.
This blog will contain a lot of complaints about the features of software and hardware products and how other people see things different from how I see things.
Nothing of what I write is meant to be an insult to anyone, but rather an invitation for discussion about the issue.
I do have strong believes of how things might work better, and I am old enought to know that I was very often right. But beeing of a certain age also means that I experienced very often that I was wrong.
So lets start the rumbling.
Wolfram Alpha is defining a huge ontology, is filling the ontology with data from all over the world and is making all this data available through a native language interface where people can ask questions and get an answer.
So its no longer about files, its about single facts connected together with metadata.
You can use it for free at http://www.wolframalpha.com
I asked: “what is the median age of the population of all spanish speaking countries”
and I got the answer: “26,3”
Read about the construction of WolframAlpha at http://www.stephenwolfram.com/publications/recent/datasummit2010/
A number of people relevant to me are in my PIM application. These people could be offered as a tag in digikam. This way I do not have to manage people tags in digikam.
Sometimes I get a document from friends by email to look over it. I read them, make some edits to it and send it back to them.
As I do get the document as an attachement of an email, I first save the attached document in a folder. Usually this is a new folder reflecting the name of the sender of the document.
Then I start editing the document and save the edited version as a new document with a new name in the same directory as the received version.
Then I attach my edited version to the answer email I send to my friend.
It could be that my friend and I exchange several versions of the same document.
I store all of them with different version file names in the directory named after my friend.
For me it would be great if I could just attach a tag to each of those files that indicates that this file is relevant to this friend. No new directories with peoples names would be required. It would not matter where I store the document or what file name the document has.
I could use this people tag to FILTER for all files on my harddisk relevant to my friend.
I could filter for files relevant to one or some of the people I do have in my contact list.
This would make my live much easier finding the relevant documents when interacting with people or preparing a meeting with them.
anyone else wishing for such a feature?
When working with a document, it should be possible to add people tags to this document. The tags are stored when the document is stored. Nepomuk knows what person is related to what document and where the document is stored. Nepomuk need to update the location of the document when the document is moved within the filesystem or erased.
This can also work for downloaded documents like read onyl PDFs.
peopletags can be used to FILTER for documents relevant to people.
anyone else wanting this feature?
It apears to me that lots of websites dealing with lots of files (like music, pictures, news, books, ..) do not use hierarchical directory structure, but other forms of interfaces to get the user to those files user are interested in.
There is a broad variety of solutions out there and darvinistic selection of the fittest will show what user interface concepts are the good ones.
Websites do not need to wait until a new concept of userinterface gets integrated in Linux distributions, they just deploy their new website and users who are interested in the content of the website will use it and adopt to it.
The designer of the new website does have very powerfull tools to watch the users while they use the system to be able to improve its design.
Non of those is available to the developers of Nepomuk.
So it might be that people flock to SaaS offerings just because the ecosystem allows the developers to innovate much faster and makes available new features much faster to the users.
Google is recording what pages we look at, for how long.
Amazon is recording what books we are interesed in.
For me it would be great if I would have automatically documented what I do when.
Then I could answer questions like:
How much time in average per day do I browse the web?
How much time per week do I use for answering emails?
How much time per week/month do I use Openoffice to prepare a presentation?
How much time do I spend in Facebook?
When did I work for how long on what document?
For how long did I work on documents belonging to a certain project?
How is the distribution of my working hours?
What type of work do I get done at what time?
The data would be written by the user applications into the Nepomuk storage.
The questions would be answered by applications reading and analysing the data provided by the Nepomuk storage.
I personally at least want to know as much as possible about be. This raw data should not be stored in the cloud, but should be stored only on my computer which is in my posession.
The following video demonstrates with digikam how efficient it is to filter within thousands of pictures.
No navigation through directories is needed and no renaming of files.
The video also shows that the user interface to find pictures by filtering within digikam could be improved.