Open Zweibach opened 4 years ago
One important piece of data that would make this useful for downloading would be what a tag might be called on different sites. If Hydrus could know what tag it's supposed to use in a query a user could simply supply the top (or any in the chain) sibling and the system will pick the correct tag to hit the site with. See #632 for examples.
Tag meta data
Oft and long requested feature, one of the first the wishlist channel.
In short it's tags for tags. Purple hair, long hair, ponytail, etc. would all have the meta tag of hair. Maybe
group:hair
. Ponytail would havegroup:hairstyle
and purple hair would havegroup:colour
. These could be used to create dynamic parents as an example, or lay the groundwork for being able to search tags instead of files, translations, bake related tags into a tag, or any number of other things people can think of.Presentation string is how the tag would without having to take to siblings. Let us say we have the tag
character:kaga (kantai collection)
. You could sibling it tocharacter:kaga
but this could cause issues with characters of the same name from other series. So if we assume the presentation string looks something like this%namespace%:%name% (%series%)
by default we could edit it to instead look like%namespace%:%name%
. Searching, sorting, tag management and everything else would still see the original tag, but if you just look at it you'd see it how you've set it to look.Tag description would be for, you know, describing the tag since not all of them are immediately obvious from name alone not to mention all the people just plain bad at English who don't understand some obvious ones.