/hydrus/ - Hydrus Network

>>12692

>to specify which kind of animal ears, include a species: tag in the search

this kind of thinking has problems in my view. This search has the possibility to turn up false positives where multiple characters are depicted. Say we want to see only images with dog ears depicted, so we search for species:dog and animal_ears. A resulting file might have one character sporting cat ears and another character who is known to be a dog anthropomorphism, but no dog ears are visible.

This sounds contrived but I think the problem becomes noticeable for more common tags.

I like to create more specific tags for particular concepts that are important to me, and add lots of tag parents as necessary

>Any artwork that lacks a series: tag is assumed to be an original work

This seems dangerous if you have lots of files that have yet to be tagged at all. I suppose it makes sense if you are strict with your inbox/archive

>Underscores are always used for spaces. This is done so that wildcard searches function properly.

I didn't realise this was a problem. Personally I wouldn't sacrifice the prettiness of my tags for this, so hopefully the program gets fixed

>My namespace for SFW/NSFW

For me, this is the perfect opportunity to use rating systems instead, because a file necessarily only has one level of explicitness. It is much easier to click on a rating bar rather than deal with tags.

>The cutoffs between "white", "silver", and "grey"

I much prefer to play this by eye. This kind of ambiguity can really annoy me, especially for characters like Anchovy (girls und panzer) whose hair clearly looks green-ish, but is often tagged as silver. When in doubt, I just add all the colours which could reasonably describe the file

> This search has the possibility to turn up false positives where multiple characters are depicted. Say we want to see only images with dog ears depicted, so we search for species:dog and animal_ears. A resulting file might have one character sporting cat ears and another character who is known to be a dog anthropomorphism, but no dog ears are visible.

This problem only happens if you blindly use child/parent tags for things that are "often true" but not "always true". You either need to manually fix tags when it is only "often true" (which may be a time saver compared to manually tagging). You also run into the same problem when searching for dog_ears if the file is also tagged cat_ears because it has an anthropomorphic cat character in it given the image is mistagged to begin with.

>This seems dangerous if you have lots of files that have yet to be tagged at all. I suppose it makes sense if you are strict with your inbox/archive

If you don't know if a character is from a series or not, would a mistag of series:original be better or worse? If the character is known from a series but doesn't have a series: tag it is trivial to add. I don't see any benefit to this tag, no matter how incomplete or complete your library's tagging is. It arguably has more to do with how familiar you are with the images in your gallery. If you download a bunch of images of characters you're unfamiliar with then the tag becomes more beneficial.

It's beneficial for group, anonymous usage where knowledge of the browsed images is not assumed. However, I only tend to save images of characters I know of/care about and so there is no question about whether they are an original character or from a series because I'll know what series the character is from.

I do see the merit in it if you use Hydrus for file discovery and not only tag management of already known files.

*>For me, this is the perfect opportunity to use rating systems instead, because a file necessarily only has one level of explicitness. It is much easier to click on a rating bar rather than deal with tags.*

I currently don't use the rating system and can't even figure out where it's hidden under. I agree that using ratings would make more sense for this.

*>I much prefer to play this by eye. This kind of ambiguity can really annoy me, especially for characters like Anchovy (girls und panzer) whose hair clearly looks green-ish, but is often tagged as silver. When in doubt, I just add all the colours which could reasonably describe the file*

I dislike having multiple hair colors assigned to one character, except when they in fact have multiple hair colors. More of a tidiness thing than a practical thing. It is a pain point though.

>>12704

Those series: tags are driving me nuts. Like 4 of them should be aliases and Nintendo isn't even a series it's a creator or copyright. Same with the character:toad character:toad (Mario). That tag redundancy is the primary reason I never use public tags. The rest of your tags make sense and seems pretty consistent. I imagine not all of these tags were from you anyway, so if pulling namespaced tags from where you're downloading the images from you get the mess with it. If you were the one who tagged it series:mario bros five times, why?

>>12705

>I imagine not all of these tags were from you anyway

It's PTR mixed with MD5 searches from every booru that allows for MD5 searches.

I'll fix them eventually, but it works for now, so it'll probably be the last thing I do, if I even get to it one day.

I try to be practical about it and take a few things into account:

>This is private, I'm doing this myself

That means I use tags based on how I would search for an image later. I'm not doing an essay in tags for every minor detail I will never remember. The main purpose for me is to find images so I tag in a way that I will find them.

>This is private, no one but me will ever use this set of tags

Ties in to the first but it means very personal tags. You woudn't use "cute" on a booru, for example.

>I have a fuckton of images to sort and there's always more to come

That's why I keep it down. There's rarely more than a handful of tags and if there are, it's obvious things. A knight for instance will have something like "knight, armor, helmet, sword, shield, fighting, blood, deus vult" and there might be more because I utterly made that up.

I do however use tags for one other purpose other than finding things: to provide source. I do try to be specific with the creator: series: and character: tags for that reason.

Apart from that, since I see no reason to run an SFW database right now, I do have rating tags for questionable, explicit (this includes non-sexual stuff too, like a certain australian's lifestream) and pornographic, the latter two being a parent-child pair. So in the rare case someone is standing behind me I exclude those.

Oh, and I tag if it's a gif, a video, a readable or an audiofile.

One thing to remember when tagging is that you don't need nail the tags down so exactly from memory that you only find a single image. There's a nice big screen full of thumbnails. I firmly believe that some visual searching is far faster than trying to go by tags alone.

Pro tip: If you want to replace a tag entirely, not just via sibling, fetch all files with the old one, tag them new and remove the old one. I did this a few times already.

>>12705

>I currently don't use the rating system and can't even figure out where it's hidden under.

Services > Manage Services > Add > Local Numerical Rating Service

The beauty of rating services is that they will not be carelessly pushed to the public repo, which is great because I think explicitness is very subjective

> Metholodogy

Why not we gather all the major ways of managing Hydrus and create a "common workflow"?

>>12741

This is a good idea.

>>12748

That's not really something that should go into the tags at all, it's not really something you search with. If the file's notes could be shared on the public server it would go in there

>>13156

Wanna pitch in on how things can be done, judging by this thread? Of course the more variations the merrier

>>13156

>>13219

Not the other guy but what about a collaborative parent and sibling database? I mentioned this once to the dev awhile back when he first added the option to import and export parent and siblings.The idea is something where everyone can contribute to and add to their client database. For parent tags, my biggest issue is trying to connect each and every character to a series or a sub series to a parent series. If there was a parent database that already did this then this could save a lot of time for some people.

A sibling database though might be a bit tricky to pull off as not everyone is going to agree on a certain term used for a tag and certain people can be pretty autistic about their tags. Over the years of using Hydrus, I've noticed how some booru and sites create useless tags that clog up my client. Some would have misspellings, other times I would have tags like "buttjob", "assjob", "butt job", "ass job", "hotdogging" or tags like character:[first name] [last name] and character:[last name] [first name] when they all mean the same thing. With a collaborative sibling database, not only could we eliminate stuff like this by merging everything that means the same but, also pick and choose which term you like best and have hydrus remember that from now on even when you download a new database. This would also be great for sites with different language tags like Pixiv.

Something like this though would also mean you'd need a site other then github and 8chan to pull this off as you'd also need a place to decide and discus a tagging schema that everyone can look through and follow.

>>13284

> Not the other guy but what about a collaborative parent and sibling database? I mentioned this once to the dev awhile back when he first added the option to import and export parent and siblings.

> The idea is something where everyone can contribute to and add to their client database. For parent tags, my biggest issue is trying to connect each and every character to a series or a sub series to a parent series. If there was a parent database that already did this then this could save a lot of time for some people.

> A sibling database though might be a bit tricky to pull off as not everyone is going to agree on a certain term used for a tag and certain people can be pretty autistic about their tags. Over the years of using Hydrus, I've noticed how some booru and sites create useless tags that clog up my client

> With a collaborative sibling database, not only could we eliminate stuff like this by merging everything that means the same but, also pick and choose which term you like best and have hydrus remember that from now on even when you download a new database. This would also be great for sites with different language tags like Pixiv

I would say that the first step of solving that issue is to have a wiki and a forum/chat dedicated to sorting those issues out. We urgently need a platform to debate such issues.

Here is a basic idea: tag relationship diagrams like [core word] [derivatives] [misspellings] [disambiguation] and [{foreign language}] for siblings, and [subsets] [supersets] for parent/child.

From these we create a page for each tag, from that we can start and sketch out a taxonomy that makes everything clear, like how Wikipedia manage their pages.

If I am allowed to pick a repo, I would choose https://github.com/Requarks/wiki for Javascript-based or maybe a Python-based wiki if the whole of Javascript is a no-go (but it definitely needs page crosslinks, chats/forums, moderation.permissions, branching/forking, archives, page versioning, page categorization/heirarchy and other needed features)

>>13287

example https://github.com/edgewall/trac https://github.com/moinwiki/moin

See also https://wiki.python.org/moin/PythonWikiEngines https://www.progracoding.com/10-best-wiki-cms/