http://brainstorm.ubuntu.com/item/9560/
If you use a hierarchical filesystem, you have to duplicate your file when you want to put them in the folders or making symbolic links which make it difficult if you want to delete it.

A tag filesystem on the other hand solve completely the problem. And because it can be implemented as kernel filesystem, every application can then use it instead of being an extra application.

Because of its interest in everyday use of the computer I put this project in the category office

Please check here:
http://www.tagsistant.net/

some articles:
http://nascent.freeshell.org/programming/TagFS/
http://citeseer.ist.psu.edu/741340.html

also some interesting work:
http://code.google.com/p/tagfs/


similar ideas have already been posted:
http://brainstorm.ubuntu.com/idea/1981/
http://brainstorm.ubuntu.com/idea/1982/
http://brainstorm.ubuntu.com/idea/3798/


[67 votes] Solution #1: Auto-generated solution of idea #9560


]]> en-us Fri, 06 Jun 2008 07:40:32 +0000 Fri, 16 Oct 2009 18:23:02 +0000 QAPoll module http://brainstorm.ubuntu.com/idea/9560/ Fri, 06 Jun 2008 09:15:04 +0000 Fri, 06 Jun 2008 18:01:06 +0000 Nepomuk seems to be a good project
but what about all other applications including the so terminal that do not include nepomuk

Also it probably makes things slow.

nevermind85
hard links have do be manually set (for each tag/folder you want to put it) and if you want to remove a file for all tags/folder, you will have to go to all tag/folder to delete it.

]]> Fri, 06 Jun 2008 22:05:19 +0000
One good tag to place on files is the current task. But this would require knowing what project the user is working on. With a task-oriented UI, you would have that information.]]> Sat, 07 Jun 2008 05:15:39 +0000
Stratus - [url=http://wealthandpower.org/stratus/]http://wealthandpower.org/stratus/[/url]

FITaFS - [url=http://fi-mihej-en.blogspot.com/]http://fi-mihej-en.blogspot.com/[/url] (now). My development. There is while little information because I will lay out complete description hardly later - after a publication in a paper magazine (in a flow month-two). Approximately in also plan to lay out time the first working version of the module for FUSE. Why did I decide to create another tag-based filesystem? One of reasons are serious problems, showing up at other tag-based filesystems, at presence of plenty of tags: 1) to the man becomes uncomfortably in them to be oriented; 2) at the programs, trying to go round all tree folders failures appear.

P. S.: I am sorry for my English.]]> Tue, 10 Jun 2008 15:11:44 +0000
FITaFS - http://fi-mihej-en.blogspot.com/

sorry ]]> Tue, 10 Jun 2008 15:15:58 +0000 Mon, 25 Aug 2008 16:52:07 +0000
Tagsistant is developed with ease of use for the average user as one of its primary goals. Some design choices that may sound unnatural at first glance are a direct consequence of the research of a intuitive interface both at shell prompt and inside a file manager.

I hope Ubuntu can get interested in it and someday will plan the integration.

Best wishes.]]> Tue, 09 Sep 2008 08:41:37 +0000
I've never liked the idea of categorizing files based on their file type, like with Microsoft's "My Pictures" or "My Music" folders. They should be categorized based on their content.

If you go on a fishing trip with your family, do you really want the photos to be in a Photos folder, the videos to be in a Videos folder, and maps and emails in completely different folders? Of course not. You want everything related in the "2008 Family Fishing Trip" folder.

With a tag-based system, they would automatically be tagged with metadata like the date they were taken: "date:2008-10-12", and you could also add descriptive tags like "family", "fishing trip", and "vacation". The images would automatically be tagged with something like "mime:image/jpeg", and the act of downloading them from your camera would automatically tag them with "Photos", to differentiate from other types of graphics that can be stored in jpegs. A map of the directions to the fishing hole, for instance, would have a "Maps" tag instead of "Photos", but would otherwise have all the other tags, so it would show alongside the photos if you searched for "2008 family fishing trip". The photos would be tagged with the name/ID of the person who took them, and then you could select a bunch of images and tag them with the names of the people that are in them.

Then you could navigate and find things by topic, by date, by file type, or any combination! You could type a friend's name and the word "photo" and instantly see every picture you own of them at once, or you could type the name of an event and view all the photos and other related files for a single event at once. Or you could type a name and an event and see all the pictures of them at that particular event, as well as emails to them about the event, etc.]]> Wed, 15 Oct 2008 04:53:36 +0000
]]> Wed, 15 Oct 2008 05:18:47 +0000 "what about hardlinks?"

Hmmm... Are links supported by all filesystems? Maybe tags could be implemented as hard or soft links. The tags exist as folders (maybe hidden folders?) in the Home directory, and files would be linked into each folder if they were tagged. Then file browsers would interpret this with a more advanced interface.

The best solution would be independent of desktop and independent of file system.]]> Mon, 20 Oct 2008 14:34:48 +0000
Surely this has been proposed before, though. What are the proposed implementations?

I imagine a system in which different "kinds" of properties of the file are encoded in the tag, and the human-readable GUI implementation of the tag might show different classes of tags ("names" given by the user vs file types generated by the system, for instance) in different colors, maybe. So if you searched for "jpeg" and "Family", the jpeg would be recognized as a file type and shown with some kind of filetype prefix and color, and the "Family" would be recognized as a user-generated label and given a different color?

This looks relevant:
http://www.foo.be/cgi-bin/wiki.pl/MachineTag
http://www.flickr.com/groups/api/discuss/72157594497877875/


]]> Mon, 20 Oct 2008 15:29:59 +0000 Wed, 22 Oct 2008 21:16:54 +0000 Wed, 29 Oct 2008 20:19:21 +0000
For example:

cd /usr/share/hello-world

would work... but so would:

cd /hello-world/share/usr

or simply

cd /hello-world

(assuming there is only one hello-world in the filesystem)]]> Tue, 04 Aug 2009 20:18:38 +0000 Also I think that Metadata should be reformed. All metadata is currently done through different ways, usually information is just stored about the name of the file, the time the file was created, and the permissions.

MP3s use ID3 tags to store track information. This leads to problems with formating. But what if ID3 tags were done through the filesystem level? What if there was a tag for each author just like there would be for the time, or the name, this would end a lot of compatibility issues.]]> Fri, 16 Oct 2009 18:23:02 +0000