TMSU

Re TMSU, a scan through the bug list turns up this: https://github.com/oniony/TMSU/issues/264

https://github.com/oniony/TMSU/wiki/FAQ#why-does-tmsu-not-au... There are a couple very barebones wrappers around mv and rm, though they could be better (pass through arguments, etc.). https://github.com/oniony/TMSU/wiki/Tricks-and-Tips#filesyst...

I'm thinking of a similar approach with text files and collections of other file types like pdfs, images, etc as you note. For tags, there are some packages for tagging I've come across like TMSU [1], taggo [2], dantalian [3] I'm thinking of tagging by just having a tags folder with a txt file for each tag. You could just stick the path to files you want to "tag" in there. Then if desired, have a script to create a bunch of symlinks for a browsable tag file structure. Maybe even have some custom grep code to find specific keywords in my notes and "tag" them automatically [1] https://github.com/oniony/TMSU [2] https://github.com/xeor/taggo [3] http://darkfeline.github.io/dantalian/

Two sic projects that can help managing files until we get another system TMSU - tags your files and then access them through a virtual filesystem from any other application https://tmsu.org -- https://github.com/oniony/TMSU Tagsistant - Semantic filesystem for Linux, with relation reasoner, autotagging plugins and deduplication https://www.tagsistant.net -- https://github.com/StrumentiResistenti/Tagsistant

tmsu (https://github.com/oniony/TMSU/) is working on that. It's a project to give tags on all the files you care about and then lets you query them either manually on the command line, or through a virtual file system where each "subdirectory" is actually a "and this tag as well". For more complicated queries such as the one you want, it is possible to directly cd into a complicated query; see https://github.com/oniony/TMSU/wiki/Virtual-Filesystem#queri... for instance.

A great idea! I think tags are definitely a better way to organize most personal data than trees. Also I like that they describe what data they actually change on your computer right on the homepage: "TMSU does not alter your files in any way: they remain unchanged on disk, or on the network, wherever you put them. TMSU maintains its own database and you simply gain an additional view, which you can mount, based upon the tags you set up." Unfortunately building on a foundation of sand (meaning not TMSU's code, but Unix filesystems) has downsides: https://github.com/oniony/TMSU/wiki/FAQ#why-does-tmsu-not-de... " Why does TMSU not detect file moves and renames? To detect file moves/renames would require a daemon process watching the file system for changes and support from the file system for these events. As some file systems cannot provid

It looks like it's "hard" to do correctly, so TMSU doesn't do any magic but will try it's best through the "repair" command: https://github.com/oniony/TMSU/wiki/FAQ#why-does-tmsu-not-de...

Yo. I'm the author of TMSU. If you've not heard of it before it's my pet project that lets you tag your files (from the command line) and then mount a virtual filesystem that lets you access them, by tag, from any other program, including those with graphical interfaces. I've just released version 0.5.0, which has a number of new features and bug fixes. This version also provides a Windows binary for the first time, though it's a bit buggy at the moment and doesn't include a virtual filesystem (I'm working on that). Usage goes something like this: $ tmsu tag photo.jpg holiday country=spain year=2014 family $ tmsu tag song.mp3 music big-jazz good $ tmsu files music song.mp3 $ tmsu files "year > 2010 and holiday" photo.jpg You can bring up a virtual filesystem like this: $ mkdir mp $ tmsu mount mp $ ls m

It seems that this also hashes the files to produce a fingerprint. Check out the fingerprinter [1] for the raw details on how it's done, but basically, if the file is below the "sparseFingerprintThreshold" of 5 MB, the whole file is hashed. Any file above is "sparsely hashed" where the first 512 KB, middle 512 KB, and end 512 KB are hashed and combined to produce the fingerprint for that file. It shouldn't produce any performance concerns on large files, so it should be safe to use for your movie collection. [1] https://github.com/oniony/TMSU/blob/master/src/tmsu/common/f...

Ah, I see, thanks. The FAQ also explains some of the strengths and weaknesses of this approach: https://github.com/oniony/TMSU/wiki/FAQ

You may want to check out the repair command. It seems to show that TMSU keeps track of file locations on disk. If you move a file, it can find it if it hasn't been modified. If you move and modify a file, it can't find it and will mark it missing. https://github.com/oniony/TMSU/blob/master/src/tmsu/cli/repa...