Sundeep,
Why not add the desired root element name to the cts:search call? For
example, to restrict the search to the xhtml output:
cts:search(
xdmp:directory('/cpf/msword')/xh:html, $my-query
)[$start to $stop]
-- Mike
On 2009-01-13 01:38, Sundeep_Raikhelkar wrote:
1. Documents search: This happens fine at content level for documents that
are uploaded (MS-Word and MS-Excel). I have to plan to avoid XML and XHTML
files generated because of CPF framework getting searched. For example, I
uploaded a word document, this created a few XML and a XHTML, now when I search
in /cpf/ms-word I get two results. I was looking for some mechanism to tell
MarkLogic pipeline for MS-Word to place the internal files like XML and XHTML
in another location, preventing them from getting picked when searched.
/cpf/ms-word/Mule-Threading& DB-Connection-Pooling Tuning _doc_parts/css.xml -
element css:styles
/cpf/ms-word/Mule-Threading& DB-Connection-Pooling Tuning _doc.xhtml - element
html
/cpf/ms-word/Mule-Threading& DB-Connection-Pooling Tuning _doc.xml - element
section
/cpf/ms-word/Mule-Threading& DB-Connection-Pooling Tuning .doc - binary
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
