TermIt

Currently, the model is built top down, i.e.., each terms points to its possible sub-terms and the glossary itself points only to root terms. This may not be the most natural or efficient way. For example, with this structure, getting all terms in a glossary requires a query traversing all has-child relationships between terms.

Also, the tree select component interprets hierarchies exactly in the opposite direction - terms pointing to their parents, so sending working with clients on the client side has each term pointing both to children and parent.

Consider changing the term hierarchy model.