Hi,
I am new to Mark logic. And I am analyzing the difference between
search:search() and cts:search() functions.
Can we get facet in cts:search() result?
If yes,please let me know how to get facet in results of cts:search as we
get in search:search.
Thanks in Advance.
Regards,
Jonna
Jonna,
Welcome. The Search API (i.e. the functions that use the “search” namespace
prefix by default) is a higher-level abstraction above some of the other
built-in APIs, including Core Text Services (“cts”). It provides conveniences
like Google-style query parsing, pagination, faceting, and
Hi Justin,
Thanks for your reply.
Can you please give me a sample to get facet in cts:search() function?
Regards,
Jonnna
On Tue, Aug 24, 2010 at 5:22 PM, Justin Makeig
justin.mak...@marklogic.comwrote:
Jonna,
Welcome. The Search API (i.e. the functions that use the “search” namespace
Jonna,
cts:search gives you a list of results based on a cts:query. You can also use a
cts:query to limit the scope of a facet, but you don’t use cts:search to
generate the values and counts. You’ll need a lexicon for that. The first thing
you need to do is to create a range index on the
Hi,
This is regarding not being able to search in for a phrase/search term in an
element in which phrase is combination of text and node . Please find the
details below and sample data attached.
Use Case : search for a phrase in which phrase is a combination of text and
node. For ex. search for
Hi Debabarata,
If I'm not mistaken, you want a Word-Through which is not currently
supported. MarkLogic has filed an RFE (#5849, Enable per-database word-through
specifications, as well as a Word-Around) for consideration in a future
release. We have requested that this be implemented in
Hi Jonna,
Justin gave you the solution. This a little something extra we did one
occasion in a MarkLogic Essentials class to respond to this question:
- http://gist.github.com/343528 (see listing 8)
Dont know if you attended the class but case you did you can try this out.
Also if anyone is
The data is being tokenized on whitespace, and you're introducing whitespace.
Wouldn't the following solve the problem?
TitleMagnetic anisotropy data of
CSubscript24/SubscriptHSubscript12/Subscript/Title
Just a guess….
On Aug 24, 2010, at 1:40 PM, Shannon wrote:
Hi Debabarata,
If I'm
Hi Shannon,
Thanks for the answer. The answer may solve my purpose. I think this might
be the case.
-- Debabrata --
On Tue, Aug 24, 2010 at 11:18 PM, Shannon shifl...@virginia.edu wrote:
The data is being tokenized on whitespace, and you're introducing
whitespace. Wouldn't the following
Just for clarification here, while Shannon's example makes fn:data of the Title
element return the string that is desired, search tokenization does not.
For search purposes, each text node is tokenized separately. A word boundary
will never cross a text node. The following demonstrates how
Hi Danny,
Thanks for the response!
We are not introducing any spaces in the text and i have confirmed in the
title element no space is present, following is the text TitleMagnetic
anisotropy data of
CSubscript24/SubscriptHSubscript12/Subscript/Title. It is just
the XML representation of the text
11 matches
Mail list logo
