[ home / board list / faq / random / create / bans / search / manage / irc ] [ ]

/hydrus/ - Hydrus Network

Bug reports, feature requests, and other discussion for the hydrus network.

Catalog

8chan Bitcoin address: 1NpQaXqmCBji6gfX8UgaQEmEstvVY7U32C
The next generation of Infinity is here (discussion) (contribute)
Name
Email
Subject
Comment *
File
* = required field[▶ Show post options & limits]
Confused? See the FAQ.
Embed
(replaces files and can be used instead)
Options
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 1 per post.


New user? Start here ---> http://hydrusnetwork.github.io/hydrus/

 No.896

ITT we discuss and propose new siblings and parents.

For the Hydrus public tag repository, there are 37000 tags for Eyes Closed and 8000 for Closed Eyes.

Currently there is no sibling relationship for these tags to my knowledge, so I'd propose we replace Eyes Closed with Closed Eyes (new sibling relationship). It's more of a descriptor that way, although it'd mean replacing more tags.

Any thoughts?

 No.897

Eyes closed is just fine. Don't overdo it.


 No.899

>>897

The point is we have a major redundancy, which defeats the point of the tag system. One has to go.


 No.902

File: 1435791431810.jpg (687.53 KB, 1665x2331, 5:7, 4cbeba95dc785dc9844ac5d75a….jpg)

I find it difficult working out which of these sorts of things is the best, and even when I decide I like 'smiling' over 'smile' or whatever, I usually forget what I preferred afterwards. Perhaps I should formalise a rough schema for parents and siblings on my public tag repo and add it to my help.

That said, I think 'adjective noun' is probably the more common way of usually putting this sort of stuff–'large x'/'clean x'/'open x'. The other examples of 'closed' things, like 'legs' and 'mouth', seem to be this way around. I am not sure why 'eyes closed' would be so popular the other way around, perhaps it rolls off the mental tongue better?

Then again, for these sorts of situations, where people can reasonably differ, and there is no obviously 'true' way of putting it, I don't mind if a file has both tags until I extend the client to hide one or the other. I will probably extend sibings in future to allow people to choose which way they prefer the relationship to go. This sort of thing could be easily automated for classes of sibling like 'I prefer the translated english name of a series' vs 'I prefer the original japanese name'.


 No.906

>>902

That would require mutual sibling searches. I didn't think that was possible because siblings don't actually stamp the dominant sibling tag on the files.

Am I wrong?


 No.907

>>902

This could be a good motivation to get OR searches working. Siblings could be implemented as a single hierarchy which is checked for every search and then all the siblings are searched and OR'd together. The dominant sibling would then just be a display flag.


 No.909

File: 1436119298341.jpg (273.66 KB, 1368x1818, 76:101, 27881d2ce21a7f13b37dcd6162….jpg)

>>906

>>907

In most normal cases, when the the db searches for a tag, it checks if it has any siblings and does its search for all of those, like an implicit OR, so they don't need the dominant to be included.

There are still places that aren't checked (e.g. I think wildcards don't). There are stupid quick ways of patching these slips and clever difficult ways of completely fixing all of them, and I am not sure which I want to commit to. For now, if you notice a place where siblings are acting illogically, let me know and I can patch it.




[Return][Go to top][Catalog][Post a Reply]
Delete Post [ ]
[]
[ home / board list / faq / random / create / bans / search / manage / irc ] [ ]