[MarkLogic Dev General] RE: search:search options constraints

[Keith L. Breinholt]

// p[starts-with(ref:anchor/@id, "para_")]/text[fn:contains( "sometext",  .)]

Keith L. Breinholt
breinholtkl at ldschurch.org<mailto:breinholtkl at ldschurch.org>

From: general-bounces at developer.marklogic.com [mailto:general-bounces at developer.marklogic.com] On Behalf Of Steiner, David J. (LNG-DAY)
Sent: Thursday, March 25, 2010 1:21 PM
To: general at developer.marklogic.com
Subject: [MarkLogic Dev General] search:search options constraints

I have an XML structure like this:

...

                            <p xmlns="namespace1">

                                <ref:anchor id="para_2" xmlns:ref="namespace2"/>

                                <text>This is a bunch of text that I want to search.</text>

                            </p>

...

I want to search for words (multiple terms: word1 AND word2 AND word3) in the <text> element of the <p> elements where the <ref:anchor>@id starts with the string "para_".

<text> elements appear elsewhere and <p> elements do to...  and there are other types of id values, such as "subpara_..."

I'm trying to use search:search and I see how to constrain to a specific element or attribute (or collection, etc.), but how do you do more complex things - i.e., constrain to a specific element under a specific parent where a sibling's attribute starts with a particular string?

Hopefully I've been clear - the XPath of the element I want to search: // p[starts-with(ref:anchor/@id, "para_")]/text

Thanks,
David Steiner
Consulting Research Scientist
Global Architecture & Research iLabs
LexisNexis Group
david.j.steiner at lexisnexis.com<mailto:david.j.steiner at lexisnexis.com>
Toll Free:    800-227-9597 ext. 51894
Direct:        937-865-1894


 NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://xqzone.marklogic.com/pipermail/general/attachments/20100325/3e9e2a2a/attachment.html