A trick with cts:near-query
A reader recently emailed me a question about an old post on the MarkLogic developer’s mailing list. The goal was to run a query such that an element’s value and an attribute on that element both matched. The problem was…
A reader recently emailed me a question about an old post on the MarkLogic developer’s mailing list. The goal was to run a query such that an element’s value and an attribute on that element both matched. The problem was…
I have another reader question today, also from Amit. To summarize, he’s using the Search API and has set up a range constraint like so: Â <options xmlns=””> Â Â <constraint name=”date”> Â Â <range type=”xs:date” facet=”false”> Â Â Â Â Â Â <element ns=””…
Tonight’s post is based on a question from Amit, a reader: I am back again with a doubt. Now we know that the default algorithm used by Marklogic is “score-logtfidf” for the relevance calculation. Now in my project, this is…