[ / / / / / / / / / / / / ] [ dir / asmr / flutter / girltalk / jewess / newbrit / strek / tijuana / zoo ]

/hydrus/ - Hydrus Network

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

Catalog

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 12 MB.
Max image dimensions are 10000 x 10000.
You may upload 5 per post.


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

Current to-do list has: 1015 items

Current big job: downloader engine overhaul


80c74a No.6443

Hi, this idea might be stupid, impossible, or both.

I I have a rather futile obsession with achieving hierarchical tagging, but ofc have no ability to code something myself (it seems likely that number of relationships would kill a database but that's just a hunch).

Anyway, I figured you could use namespaces in hydrus to group indexed "entities" to achieve one level of tag grouping, but this is only useful if the client allowed a strange form of wildcard search.

Say I have two images, both with two people. (namespaces "entitiy1:" and "entity2:").

I want to search for an image where a single entity has both Blue Skin and Glasses.

I could group them like this:

(image 1)

entity1:blue skin

entity1:glasses

entity2:glasses

(image 2)

entity1:blue skin

entity2:glasses

Using traditional tag search, both images would match, they both contain both tags ("glasses" and "blue skin"). But I am only interested in the image that features both tags in the same namespace. So in this example the first image has a match for my search, a single entity with both tags under its namespace. BUT! How would I search for it? If I used a wildcard character in the namespace ("entity*:") that would still match both images, since I have now eliminated the indexing that differentiated between the enteties. And using a known unique namespace would defeat the whole exercise.

What would be handy would be a wilcard character that can match any "entityX" across a database, but will only return a match if each tag with the wildcard is under the same namespace on a single image. A search where I do not care what the wildcard/namespace match *is*, only that it is *the same* for all the specified tags.

I do not know if this is worthwhile or even possible to implement, but it has been churning around in my head and I though I should at least mention it.

c3521a No.6452

Welcome to hell, my friend


721ac4 No.6467

File: 7c8f02993019323⋯.gif (943.3 KB, 300x189, 100:63, 7c8f029930193239a049ae4f42….gif)

I have decided to write up my thoughts on tagging in a proper file in the help, as this stuff comes up quite often and I should probably just link a proper document rather than rushing every time on this important and good and frequent topic.

tl;dr of all that and my general opinion on tagging: I think your idea is neat and I have thought about the same problem, but I don't have a better solution than what we currently do. How much time would it take to create and maintain your system? How much time would it save finding files vs using regular tags? Even simple tagging is difficult and unending, and atm it looks like we aren't clever enough to create a perfect solution.




[Return][Go to top][Catalog][Post a Reply]
Delete Post [ ]
[]
[ / / / / / / / / / / / / ] [ dir / asmr / flutter / girltalk / jewess / newbrit / strek / tijuana / zoo ]