Tag hierarchy

Name
Email
Subject
Comment *
File	Select/drop/paste files here
* = required field	[▶ Show post options & limits] Confused? See the FAQ.

Embed	(replaces files and can be used instead)
Options	Do not bump (you can also write sage in the email field) Spoiler images (this replaces the thumbnails of your images with question marks)
Password	(For file and post deletion.)
Allowed file types:jpg, jpeg, gif, png, webm, mp4, swf, pdf Max filesize is 8 MB. Max image dimensions are 10000 x 10000. You may upload 5 per post.

File: 1457278380449.jpg (148.5 KB, 1111x1587, 1111:1587, sts98plume_nasa_big.jpg)

Tag hierarchy Anonymous 03/06/16 (Sun) 15:33:00 No.2203

I've been trying to use tags with hierarchy which lets subtags describe the tags above them, using periods as delimiters.

hair

hair.black

hair.long

hair.long.knee length

hair.style.braids

hair.style.ribbon

This is nice for keeping relevant tags close and finding characteristics of tags that I want to describe in more detail.

The problem is searching. If I try to search "braid" it doesn't hit on "hair.style.braids" and if I search *braid it takes a very long time, along with the danger of the autocomplete taking off with searching for the asterisk and locking up the client for several minutes.

I've been able to work around this a little bit with siblings and searching for "braided hair" -> "hair.style.braids".

Can you think of a way to start searches inside tags following some kind of delimiter like a period?

Anonymous 03/08/16 (Tue) 05:15:15 No.2210

File: 1457414115214.jpg (53.61 KB, 813x357, 271:119, 080a2df3c5830895725f35a6b3….jpg)

There are namespaces i.e.

someNamespace:some tag

which, if you type the namespace and one letter and then autocomplete, hydrus will fetch all the tags in the namespace that start with that letter; if you type a tag without a namespace that is in a namespace, hydrus will still fetch the file.

For example, lets say you have the "hair" namespace which you populate with the tags "black," "long," and "braided." If you type "long" into the search bar, hydrus will get all the files with the tag long ignoring any namespace (so if you have the tags "hair:long," "long," and "legs:long" hydrus will return all of them), but if you type "hair:long" hydrus will only return that.

The only problem is that namespaces cannot be nested so you cannot have "hair:style:braids" as hydrus will just interprite it as the tag "style:braids" in the "hair" namespace. Which actual sounds like a bug as you wouldn't want the namespace delimiter inside of tags.

If your "subnamespaces" aren't abstract, you can use parent tags so that the children get the parent tag in the taging process.

sanitization_anon!zJCzW0dX0. 03/08/16 (Tue) 15:36:39 No.2211

>>2210

Namespace delimiters not being recursive is tricky - you could think of it as a bug, but also there's stuff like "series:the legend of zelda: ocarina of time" in which you do actually want "series" to be the namespace and the rest of it to be a full tag.

sanitization_anon!zJCzW0dX0. 03/08/16 (Tue) 15:37:10 No.2212

>>2211

Or less controversially, "series:2001: a space odyssey"

Anonymous 03/08/16 (Tue) 23:05:08 No.2216

>>2210

Unfortunately the sub-namespaces are pretty much abstract and arbitrary. I was wondering if the delimiter could be an option or maybe two characters. The idea would be to avoid using asterisks in the search to keep the search time down, otherwise I could just put asterisks on both sides of the search term. Namespaces kind of do this already, but like you guys said it's hard to avoid recursion blowing up the search.

Ideally I'd like the search to hit on any of the nested tags individually. I picture it working like this:

set delimiter to ":."

long matches

hair:.long

hair:.long:.knee length

clothing:.shirt:.long sleeves