|
Tuesday, 27 April 2010 07:59 |
|
It's time for a big change in tagsistant. And the main change has to happen into the backend system.
So far tagsistant was able to import files by duplicating it in both copy and link cases. That's disk consuming!
Tagsistant is not able to store directories. That's a big drawback.
That's too much. We need a new backend. And we'll have it!
In the new backend, the link and the copy functions will provide two different behaviours has you usually expect from POSIX systems. If you copy it, Tagsistant will create a copy in a local storage controlled by itself and you'll never risk to loose your data unless you explicitly delete it. If you link it, on the other hand, you'll have a lightweight reference to your data inside tagsistant and you'll be able to tag your data wherever located.
Since this schema is object independend, you'll have the possibility to save directories too, and pipes, devices and sockets.
How about it? |
|
|
 What is a semantic file system? Honestly, I don't know! Many people say that is something you can use to organize your contents using ontologies based on labels or tags. Others say it is related to relationship between files or "things". Others claim it has something to do with circles in fields! ;-)
To me, a semantic filesystem is basically a tool that allows one to catalogue files and to extract subsets using logical queries. But why a filesystem and not a database or a desktop application? That's the most obvious but often hidden consideration a programmer should do! Software should be as interface neutral as possible. Interface neutral means that you should be able to communicate with this software easily and efficiently. A desktop tool can be comfortable for the user, can be assistive and accessible. But other softwares will not be advantaged in interfacing with that tool. Perhaps other tools should be modified to apply to new API, requiring days of coding and possibly introducing new bugs! Universal, well known and well tested interfaces should be preferred against special, new, particular interfaces. A filesystem is probably one (or the most) universal interface you can think of (especially on UNIX, and especially talking about files!). Later, someone will write a colorful and intuitive desktop application (or a series of) which will be appealing, but right now, with a 3 days hack, everyone can tag his/her files by simply using the filemanager interface he's used to. |
|
|
Donation