It is somewhat abandoned.
Generic Hierarchical Meta data is cool! There are many ways to implement it with a standard relational database. Most of them are considered anti-patterns, but sometimes we need to optimize for flexibility, not raw database performance. Here are some of my notes on the subject: If all entities in the system can contain a list of tags, and the tagging system is structured correctly, the following features can be supported:
This should allow for a flexible meta-data system over top of the entities which can be customized with very little code modifications.
This can be accomplished by having a tag tree, where tag entities have the following fields:
The following tag search can then be implemented in SQL:
Assuming that most tag trees are only 2 levels deep and using a subtree inclusive search when this is not the case (or always), we treat each tag tree as a facet in a faceted search.
A hierarchy of categories and sub categories can be built by building the tag hierarchy and assigning all items into leaf tags and once again using an inclusive tag search as we drill down.
If tags in a tree are given weights, entities can be sorted by these tags in , for instance, a grid.
Null Tag :
Null tag could be added to any subtree which would catch all entities without a tag in that tree. This would be helpful for facet navigation and search.
Null tag for facet:
A null tag of “Unknown color” could be added as a child of the color tag, and would return all entities without a color tag.
Null tag for sorting:
A null tag of “no priority” could be added as a child of the priority tag and be given a weight of zero, hence sorting on this priority tag tree would return un-prioritized entities last.
Need cohesive example. Another Post.
Tags as categories:
Znode uses Tag groups to represent categories and to implement a faceted search. Their implementation is only 2 fixed levels however.