If your application permits you can consider de- normalizing the book  
info into each chapter doc. Then you can easily get the book level  
information for each result.

Frank Rubino

On Aug 22, 2009, at 9:59 PM, "Mattio Valentino" <[email protected] 
 > wrote:

> Thanks both Mike and Kelly.  I appreciate the responses, especially on
> the weekend!
>
> The suggestions make perfect sense (and Mike knows I've worked with
> that chunking approach before).
>
> One area I'm still not sure about is how to return a reference to the
> book if *any* fragment/chunk contains the user's search terms.  For
> example, if the user searches for "digestive system" I want to know
> which books contain the phrase anywhere within them.  The only idea
> I've had so far is to have the chunks loaded as you both describe, but
> then to have the book loaded again in it's entirety as a single
> document, but perhaps with the tagging and print index stripped out to
> help reduce its size.  We did both this and the chunking in a previous
> system.
>
> Is there another approach I'm not seeing?
>
> Thanks again,
> Mattio
>
> On Sat, Aug 22, 2009 at 10:35 AM, Michael  
> Sokolov<[email protected]> wrote:
>> Mattio - we find we get good results by chunking books into  
>> documents when
>> we load them, not using fragmentation.  After removing the chapters  
>> (we
>> insert reference nodes in their place), the remaining shell serves  
>> as a
>> convenient "book" (ie title) document.
>>
>> Cheers
>>
>> -Mike
>>
>>> -----Original Message-----
>>> From: [email protected]
>>> [mailto:[email protected]] On Behalf Of
>>> Mattio Valentino
>>> Sent: Friday, August 21, 2009 8:59 PM
>>> To: General Mark Logic Developer Discussion
>>> Subject: [MarkLogic Dev General] Searching large documents
>>> above thefragment root level.
>>>
>>> I have large documents stored in MarkLogic -- books.  My
>>> fragment roots are set to the chapter level because we
>>> display material at that level and we have a search feature
>>> at that level. Performance is good with those queries.
>>>
>>> We also have a feature where we want to search at the title
>>> level where title metadata is returned as a result if it
>>> contains the search term anywhere within it.
>>>
>>> I've written this query a number of different ways and I
>>> can't get good performance out of it.  There are a number of
>>> requirements I'm leaving out, but does anyone have a pattern
>>> or general strategy for these types of queries where you are
>>> searching at the document level instead of the fragment root level?
>>>
>>> Thanks,
>>> Mattio
>>> _______________________________________________
>>> General mailing list
>>> [email protected]
>>> http://xqzone.com/mailman/listinfo/general
>>>
>>
>> _______________________________________________
>> General mailing list
>> [email protected]
>> http://xqzone.com/mailman/listinfo/general
>>
> _______________________________________________
> General mailing list
> [email protected]
> http://xqzone.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general

Reply via email to