Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Welcome to the Judaism community on Codidact!

Will you help us build our community of learners? Drop into our study hall, ask questions, help others with answers to their questions, share a d'var torah if you're so inclined, invite your friends, and join us in building this community together. Not an ask-the-rabbi service, just people at all levels learning together.

Comments on ISO: hierarchical tags

Parent

ISO: hierarchical tags

+7
−0

One thing sorely missing from Mi Yodeya is a tag hierarchy. For example, having the Book-of-Judges tag be a sub-tag of the Books-of-the-Prophets tag, so that keyword searches among the latter will find also questions in the former (or will optionally). As another example, having the labor-of-writing tag be a sub-tag of the labors-of-sabbath tag. This would allow someone to find all questions about a fine point of the labors of the sabbath even if they may have been tagged with a specific labor's tag.

It doesn't seem like Codidact — or at least not Judaism Codidact — has that now. I would like to put it in as a feature request. Any chance? Please post replies below if you can provide info on the likelihood of this happening; but also your opinions on why this would be a good or bad idea.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+3
−0

Let's check some functional requirements. :-)

I'm envisioning tag hierarchies as an overlay, thus:

  • All tags would remain in the tag set and could be individually chosen (i.e. both leaf and non-leaf nodes are available as tags on posts).

  • Tags could be designated as children of other tags, but there would be no requirement to have a single overarching tag tree -- use the relations where they make sense and don't where they don't.

  • The page for an individual tag would indicate its parent and/or children, if any (as links to those tags).

  • Searching on a tag would search the tag and all of its children.

The tools for managing this are TBD and would probably be "workable but not pretty". There wouldn't (yet) be tools for viewing tag hierarchies graphically.

Would this meet the basic need? This seems to me like it would help a lot, but I don't want to just build what I think we need -- I want to check that with others.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (5 comments)
General comments
msh210‭ wrote over 4 years ago

That sounds about right to me fwiw. I think one additional requirement would be that the code either enforces no tag loops or accounts for their existence when (e.g.) searching.

Monica Cellio‭ wrote over 4 years ago

Oh good point; loops could happen and we'd want to handle or prevent that.

msh210‭ wrote over 4 years ago

I should note that I meant loops of two varieties: A is a descendant of itself, or A is a descendant of B via two different routes. Even the latter case may lead to bugs if care isn't taken; e.g. the same post may appear twice in search results for B.

Isaac Moses‭ wrote over 4 years ago

Probably easier to write the search algorithm to not get caught in loops than to create the ideal UI way to stop people from making them.

Monica Cellio‭ wrote over 4 years ago

I agree with Isaac. I'm imagining search rewriting the search query to expand children, so if you search on [a] [b] and [b] has children [c] and [d], the actual search would be [a] [b] [c] [d]. When considering adding a tag to the list via hierarchy expansion, if it's already there we stop processing that branch.