Task #725
closedRevisit the structure of term hierarchies in glossary
0%
Description
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.
Related issues
Updated by Martin Ledvinka almost 6 years ago
- Related to Task #724: Add support for multiple parents of term added
Updated by Martin Ledvinka almost 6 years ago
- Status changed from New to Resolved
I believe this has been resolved. An inferred property now specifies the vocabulary to which a term belongs, so getting all terms from a vocabulary involves just getting all subjects of this property for a particular vocabulary.
The tree component has far more important issues that parent/child duplication. In addition, this duplication possibly occurs only on client side.
Updated by Martin Ledvinka over 5 years ago
- Status changed from Resolved to Closed