Hi! I'm trying to build a tree index from a tree-structured document (the document has several sections, each section has several subsections, each subsection may have sub-subsection or texts, etc.), where I want to build the index using the existing tree-structure of the document, and also use each (sub)section titles as summary of the non-leaf nodes instead of building non-leaf nodes bottom-up by summarizing leaf nodes. Although I want to use the native tree index, but find it hard to customize in my case. Is the current implementation of tree index support self-providing tree-structure and summaries? i.e. non-leaf nodes might have different number of children nodes, and these children can be of different index types. If not, I'm thinking of the following two ways to build my index:
- Build ComposableGraph on top of indices that are built from leaf nodes, and build parent graphs on top of child graphs until root (although I couldn't find usage of building graph on top of graphs).
- Build IndexNodes on top of leaf TextNodes, and build parent IndexNodes on top of Index or Text nodes until root.
I'm wondering the difference between using ComposableGraph and using IndexNodes to build the custom tree index. Thank you.
