I really like tag suggestions. Should help a lot more than recently used.
I just finished cleaning up and refining a bunch of my personal parent-child tag relationships. I've made it such that this chain of implications is followed,
>kemono:catgirl -> kemono:furry girl > kemono:furry & kemono:kemono girl > furry level:kemono
And mirrored this structure for the kemonomimi:* and feral:* namespaces such that,
>Kemonomimi:dragonboy > kemonomimi:reptile boy > kemonomimi:reptile & kemonomimi:kemonomimi boy > furry level:kemonomimi
I also did three larges passes over everything in the character:* and ip:* namespaces to clean up a bunch of un-childed characters and add two new categories of parent focused namespaces. Firstly, a set of namespaces, developer:*, animation studio:*, and publisher:* which I've all made red just like the creator:* namespace. Secondly, genre:*, which is often used a bit loosely, but is effective enough and especially useful for specific videogame genres like run and gun, fighting, platformer, et cetera. I'm feeling very accomplished with my autism as of late, though I still have many months of tagging until I am unboned, and so decided to skim this and the last thread so I could collect and condense my previous suggestions for Hydev. Half to remind him, half so I don't forget what I've already said and waste my and others' time repeating them, and a third half to add a couple new ones. I just updated Hydrus to the latest version so I could double check that nothing was implemented that I missed. I've ordered them by what I would guess is difficulty of implementation and will probably post them once per thread from now on, and drop any that he says are outright impossible even long term
like mutex.
Parent display
Modify either one of the experimental dropdown options in the tag manager, "switch to 'mulitple media views' tag display" or "switch to 'display tags' tag display" so it is a permanent toggle, rather than reverting upon closing the tag manager.
I do not know what the difference between these two options are. This already displays all parent tags that are applied through the parent child relationship with other tags on a file as regular tags in the tag manager, but lacks permanence. Add decoraters to the parent tags denoting they are only present as a parent tag if they are not already hard tagged on a file.
Sibling display
An option to display siblings as ideal tags in the tag manager with decorators denoting they are not actually the ideal tag. Similar to the option above, however this would hide the unideal sibling tag.
archive thumbnails
When a .zip, .rar, .7z, etc. file contains images, the first image should be used as a thumbnail. This makes browsing a collection of manga/comics
or hentai much more feasible as once you narrow down the search pool to a reasonable amount you can still browse the files by eye and decide to look at something based on often untaggable art styles or visual memory. This can be simulated by turning an archive into a .png archive with the cover page as the png image, but that's of course quite tedious and impractical.
Grouping namespaces By color
You've said this is on the back burner. Hopefully it can be done one day, as it will vastly improve the presentation of tags in the tag manager and increase the speed of viewing them.
"Non-existant" parent tag autocomplete in tag/parent/sibling managers
When creating a new parent tag, unless that parent tag is manually tagged on some file, it does not show up in the autocomplete window for either the tag/parent/sibling managers. I'd like such cases to show up in the managers' autocomplete with the number (0) beside them.
Effective tag count display option for parents and siblings in tag/parent/sibling managers
Given you can have a wealth of files tagged with unideal siblings and child tags that effectively apply the ideal and parent tags, it would make sense to have an option for the display of a tag's count, the number in parenthesis beside the tag, to display the number of files that have the tag effectively applied to it, rather than just the number of files hard tagged with the tag. This may help get better autocomplete results for some use cases since this number determines the order in which they display. If possible it'd be nice for this idea to be expanded to the meta information under "review sevices" -> "tags" so that you can see a seperate number for mappings that shows how many mappings there are if soft-tagged parents were to be treated like hard tags, and redundant unideal/ideal siblings tagged on the same file are not counted. With this you can get an accurate number of how many tags are effectively applied to your files on average, rather just how many are hard tagged on average.
I really like this sort of info and it feeds directly into my autism.
Namespace siblings
As an alternative solution to editing namespaces, but also good for when the namespaces taken from boorus and such aren't the ones you want to use. One could make a custom parser to automatically change the namespace of incoming tags, but this is done on a per site basis as I've come to understand and I believe is more technical, while siblinging namespaces would apply across a wide variety of sites that tend to have uniformity in tagging and would be more user friendly.
Editing tags/namespaces i.e. hard replace siblings
It's been said many times that this is a difficult task, and that siblings will take care of most use cases, I still believe in the utility it has for altering typos and fixing namespaces which can't be sibling'd. Sibling tags still cause the ideal tag to show up in searchs, so typo siblings will negatively effect a search if the typo is similar to other tags. This also expedites the process of eliminating typo tags that may already have been caught up in a web of child-parent relationships so they don't have to be reapplied.
>>>/hydrus/18934
>I often find files marked as safe, questionable, AND explicit!
Mutex would be nice for this, but it's an easy fix without it just by searching for combinations of these three tags and eliminating one or more from any files that show up until there's no search results, but mutex would have a lot of use for other more complex relationships. Probably many years away though, if ever, given how complex it'd make things.
>make sibling tag 1 out of bad tag 1, select all files with bad tag 1 and, in the tag manager, add sibling 1 and delete bad 1.
This seems like a decent solution until tag editing is implemented, if it ever is, as last December Hydev said it was very complex and he was still thinking about it.