How to fix tags in Dolphin

I think this is a totally different use case to tagging within the file manager/filesystem, something like TagStudio or TagSpaces, even if those tools don’t quite suit your needs (I can only assume they don’t have a CLI). I think tagging in the file manager/filesystem has its place alongside systems like that, as I addressed in my previous comment.

To expand on that, a file you send to another computer or keep on a different drive would retain this type of tag, and that tag could be altered on another computer, and the file sent back with its new updated tag. This maintains the flexibility of managing files directly, but allows you to navigate those files non-hierarchically. I think that is incredibly beneficial, just not really what you are looking for with tags with important information attached.

In cases where you need a more robust organisational system, more info attached to tags etc., a library is more appropriate, or some sort of centralised index at least, but you give up that flexibility. I think it also creates more dependence on that system, as opposed to a filesystem + tags where losing your tags should still leave files somewhat able to navigate using a standard hierarchical structure that can be transferred to or reorganised on just about any filesystem.

But obviously it needs to be more robust on the Dolphin side, and I would definitely like to see it or something like the tags in Dolphin standardised and accepted more broadly. Tags as file attributes just makes a lot of sense, and it’s present in MacOS so feature parity would be nice. Likewise, a plugin that allows tags from other types of apps like TagStudio or TagSpaces to appear in Dolphin would be great, and it sounds like this is what you are looking for.

Sounds like you want cooperation to be a big thing. As well as adoption and standardization. And to have the features work right on top of the filesystems. In a unix-adhering manner. Well, lot of time has passed and not much evolution has taken place in this regard, so I am not sure I want to wait around for that. I just want for myself a centralized annotation system for brain mapping, studying.

No, I mainly want what Dolphin already has but with some bug fixes and my GUI suggestions.

Sounds like you are looking for some sort of CLI version of Obsidian. That’s not something I use but I did a quick google and there do seem to be some 3rd party CLI tools.

1 Like

Hello, this is my first post here.

I think as long the CLI-3rd-party-tools for successful and persistent tagging (how it actually should be) are open source, one could relative easily add either some GUI to them or (as I’d prefer much more) “convert”/rewrite one of those tools f.e. into a plugin for Dolphin.

Btw. it’s only some related topic, but I am sure most if not all of you know as well that “commenting” files brings exactly the same problems with it. At least if you do it the same way (in Dolphin + usual file handling like copying, moving, etc.) as it were tags.

If I got it right, the bug(s) were submitted certain time ago and most of you are waiting. Or maybe some of you are looking for some personal or “universal” workaround. Unfortunately I have absolutely no clue of the API provided by KDE - or should I rather speak of that which comes with Dolphin?

A spontaneous idea for an ugly / quick’n’dirty workaround (sorry for using pseudocode):

1. Select some directory with a hand full of files you want to add different tags.
2. Tag them resp. add those new tags to "the list"; stay in the directory, keep the window/terminal open.

Did I get it right that tags are (meant to be) saved “in” each file’s attributes (creation/modification/access times, permissions, owners, etc.) or at least related, not separable from those (attributes)? By changing (w/o intention even) some attributes, the tags get lost (probable the comments as well in this step). Not only “the table” of “what was tagged”, but even the manually created tags too. If that’s (almost) correct:

3.1. The actual workaround...could be f.e. via a daemon ("tagfixd", "metad", whatever) to read-out all tags/comments/metadata. Thus it automatically gets some tags that were created prior using them. In our case, he gets everything at once because it's just one directory.
3.2. If not via some daemon, then maybe by registering (on login or so) certain callbacks? Don't know if this can be implemented w/o causing pain in the ass, but if you can f.e. make our script or program for "safe tagging" to check each open directory for accessed files -> "do they have new tags/metadata"? If yes and not listed in the taggedfiles-table (depending on the present data types / structures of the language used of course; if a list fits better than a map, set, dictionary, whatever - "table" is meant in a very broad sense here.

4. Now tags and affected files should be safe/saved. Depending on whether you take the approach with a daemon or the one which operates with callbacks (f.e. on moving, copying, deleting any file as well as on adding/changing tags of any file resp. renaming/deleting some tag itself as a whole.

I hope that didn’t sound hyper-naîve or somehow idiotic - I am working during the last few years to 90% either in Lua 5.1, Python 3 or Bash and despite my basic knowledge of languages (f.e. C/++, Java) surely used much more frequently in..well, serious, big and time/efficiency-critical applications, whole (desktop) environments resp. their provided APIs - unfortunately I haven’t studied a single line of code of “KDE” neither it’s single components.

What do you say? That idea came spontaneously to my mind after reading this thread and now I am getting even excited to write something similar at least for myself (after reading the API one would need in such case of course)…I just hope that there are possibilities “in KDE’s source code / used lang.” to export some functions to Lua or even better, Python (if not it may get too hard for me cee-pee-pee’ing around at the moment)…

It’s baffling to me that you can’t use ctrl+f / ctrl+i to search / filter for tags, and I guess the application launcher search also does not look for them. So how the hell are you supposed to use them? The only “functions” I can find is that you can display tags beneath the file name (nice to have) and to sort them by tags (okayish), but that seems fairly gimmicky / surface level stuff, if that’s all there is.

It’s also weird that you can add tags through the context menu, but not edit / assign them from existing ones. You always have to type them out and they only exist for a per file basis, which increases the potential error rate. Even if you go through the file properties → details → add tags, you end up with an empty list. It’d be great it there was at least a list saved per file type (like videos, music, etc.), to make it easier to quickly tag things in a consistent way.

I feel those would be very basic level tag features for Dolphin / KDE, no?

Edit: Seems like you can’t tag multiple files at once either. Oof…

You can filter tags from control+f (that was always a feature but broken until a recent update, now fixed, but I stand by my suggestion in my original post) and you can also search tags from KRunner/app launcher. You can also tag/untag multiple items at once, but only through the info panel, not context menu. If you can’t do those things, you are probably experiencing a bug.

But yes, it’s very inconsistent and implemented only in half measures, despite the feature having a lot of potential.

Hey @TagEnthusiast, I’ve been editing the Dolphin code to test some experimental semantic filesystem features, maybe we can discuss ideas related to tagging. I wanted to support both tags and relationships between files based on Semantic File Systems David K. Gifford, Pierre Jouvelot1 , Mark A. Sheldon, James W. O’Toole, Jr. Programming Systems Research Group MIT Laboratory for Computer Science

One thing I’m especially interested in supporting for KDE Neon is transducers with HuggingFace models for automatically embedding user programmable meta data extractors.

I’ve been using BLAKE3 to hash file contents to ~/.local/share/semantic_desktop instead of setting xattrs .