Hi Adam, Can you please complement that informatiom by saying how big are tjose documents? (max, min, avg)
Also whats the distribution of the size for the elements you displayed here? Finally why do you think you need fragmentation? That will help me (and others) giving you a decent enough answer, even though many other things might need to be taken into consideration. Nuno On Apr 8, 2010 4:32 PM, "Adam Patterson" <[email protected]> wrote: Hi, I have a document which looks something like this (oversimplified for demo purposes): <teiCorpus> <teiHeader> ... </teiHeader> <TEI> <teiHeader> ... </teiHeader> <text> <body> <div/> <div/> ... </body> </text> </TEI> <TEI> <teiHeader> ... </teiHeader> <text> <body> <div/> <div/> ... </body> </text> </TEI> ... </teiCorpus> I have rooted fragments at the <text> level, and I have rooted fragments at the <div> level (actually I made the <body> node a fragment parent...but it amounts to the same thing I think). So, the fragments rooted at the <div> level are fragments nested inside the fragment rooted at the <text> level. Now, I am trying to build a search which has two scenarios: (1) It searches at the <div> level and considers a fragment rooted at a <div> to be a hit if at least one match occurs within the <div> node or one of its descendants; (2) searches at the <text> level and considers a fragment rooted at a <text> level to be a hit if at least one match occurs within the <text> node or one of its descendants. Scenario (1) is working well, but for scenario (2) my search is still considering fragments rooted at the <div> level to be hits. Is there any way to tell the search which level of fragment to use for evaluation? In scenario (2) I don’t want the <div> level fragments to be considered hits. I want the higher level fragment, the fragment rooted at the <text> level to be a hit. Feedback is appreciated, and thanks, Adam Patterson _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
