datacurator-filetree VS TagSpaces

For the most part I follow this file tree. However when it comes to some of my intererests, like electronics, I am unsure if I should keep splitting these interest-based files by file type, for example:

I have redesigned my entire computer to follow the datacurator methodology: https://github.com/roboyoshi/datacurator-filetree/tree/main/root

P.S. I've been lurking this sub and have considered this particular problem for a long time and have read maybe everything Karl, Nayuki, Reddit, and Hacker News have had to say on the subject. Running into this post is a treat. If tags don't work out for you roboyoshi and contributors have made a really nice unified file tree https://github.com/roboyoshi/datacurator-filetree

As always, credit to u/Roboyoshi for the Datacurator filetree.

But it will obviously depend on the use case. As example you have JohnnyDecimal or a more simple approach

This tool will be useful to generate repos like these and sharing them with friends without actually needing to share them TB of data.

back in the days I started with this structure tho: https://github.com/roboyoshi/datacurator-filetree

This is a mix of this post and https://github.com/roboyoshi/datacurator-filetree. Im still having trouble with a few things:

https://github.com/tagspaces/tagspaces

Either way, will definitely be keeping an eye on your app, it seems ducking cool ;)

TagSpaces – Your versatile file organizer (version 50504): organize, tag and browse your files, photos and documents

Take a file. Add [awesome] to the name. There. You've tagged a file, and you can search for it with your desktop search / fzf / etc. Switch system, copy it anywhere, it works. You can do this by hand. Or, if you like clicks and drag-n-drop, use TagSpaces. Or, use tss.

The UNIX filesystem has traditionally been a graph for ever. I haven't looked at details for a couple of decades, but definitely all UNIX/POSIX/Linux filesystems operate on a graph model.

A distinction I used to make when I was teaching this stuff: on your filesystem tree, on Unix names (labels) are on the links (arrows), while on DOS/Windows names are on nodes (boxes).

If you want to explore a tag-based system, take a look at https://www.tagspaces.org/

The quickest workaround – and the most satisfactory one to boot – is to abandon Windows Media Player. Use a digital asset management app like TagSpaces.

TagSpaces: TagSpaces is a cross-platform tagging and organizing tool that can help you tag and manage your files and folders. It supports various file formats and can be used with local and cloud storage providers.

If the naming convention is different, or you'd prefer to go the tagging route, tagspaces may be your best bet. It can use standard tags in the file, or a sidecar file (file with the same name, but different extension next to the original file) to keep tags with the file.

Agreed. Why not use the filesystem as the database that it is? Modern filesystems support tags or extended attributes that could be used to implement tags. Failing that, just encode tags in the filename. Document management tools could then use the filesystem as the source of truth.