Sana,

I think MarkLogic will be great for modeling virtual worlds, like multiplayer 
games. The scene or part of the world that people are interacting with, and 
each person's personal profile or situation would very naturally be modeled as 
documents. An interaction would access all the visible or nearby profiles, so 
the data required for each transaction is naturally limited. Not having to map 
all the data to relational back ends would be a big advantage.

I doubt your project would have enough X3D data to fully exercise a powerful 
database product like marklogic, so the player/person profiles and other 
aspects of a virtual world may make the project more interesting.

BTW, I suggest posting your questions under their own topic, rather than doing 
a "reply all" to an existing topic so everyone knows you're asking a new 
question.

Yours,
Damon

________________________________
From: [email protected] 
[[email protected]] On Behalf Of Sana CSE 
[[email protected]]
Sent: Monday, October 01, 2012 2:30 PM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] Issue with search api constraints

Hey ,
       Hi i m a Engineering student from Computer science and engineering 
branch. I am really new to the MarkLogic but have      studied many tutorials, 
and found it very valuable for my final year project. I am trying to use VRML 
or X3D  at front end for web development and backend MarkLogic server.

As you are expert, can you suggest me something or what do you think about my 
idea. Is it good?


On Sun, Sep 30, 2012 at 6:17 PM, amit gope 
<[email protected]<mailto:[email protected]>> wrote:
 What i am trying to achieve is to provide a term option of "unstemmed"  to the 
constraints so that i get non-English documents. For example in my search 
option i have  constraints defined as ::
        <term>
<empty apply="no-results" />
<term-option>case-insensitive</term-option>
</term>
<!-- search contraints -->
<constraint name="doi">
<value>
<element ns="http://www.marklogic.com/app/meta"; name="DOI"/>
<term-option>unstemmed</term-option>
</value>
</constraint>
<constraint name="metapressid">
<!--<element-query ns="http://www.marklogic.com/app/meta"; name="MetaPressId" 
/>-->
<value>
<element ns="http://www.marklogic.com/app/meta"; name="MetaPressId"/>
<term-option>unstemmed</term-option>
</value>
</constraint>

<constraint name="title">
<word>
<element ns="http://www.marklogic.com/app/meta"; name="Title"/>
<term-option>unstemmed</term-option>
</word>
</constraint>
<constraint name="isbn">
<value>
<element ns="http://www.marklogic.com/app/meta"; name="ISXN"/>
<term-option>unstemmed</term-option>
</value>
</constraint>
<constraint name="issn">
<value>
<element ns="http://www.marklogic.com/app/meta"; name="ISXN"/>
<term-option>unstemmed</term-option>
</value>
</constraint>
<constraint name="orgname">
<word>
<element ns="http://www.marklogic.com/app/meta"; name="OrgName"/>
<term-option>unstemmed</term-option>
</word>
</constraint>
<constraint name="journal">
<word>
<element ns="http://www.marklogic.com/app/meta"; name="Journal"/>
<term-option>case-insensitive</term-option>
<term-option>unstemmed</term-option>
</word>
</constraint>
<constraint name="book">
<word>
<element ns="http://www.marklogic.com/app/meta"; name="Book"/>
<term-option>unstemmed</term-option>
</word>
</constraint>
<constraint name="name">
<word>
<element ns="http://www.marklogic.com/app/meta"; name="Author"/>
<term-option>unstemmed</term-option>
</word>
</constraint>
<constraint name="date">
<range type="xs:date" facet="false">
<element ns="http://www.marklogic.com/app/meta"; name="Date"/>
<term-option>unstemmed</term-option>
</range>
</constraint>
<constraint name="volume">
                      <value>
                                <element ns="http://www.marklogic.com/app/meta"; 
name="VolumeId"/>
                                <term-option>unstemmed</term-option>
                        </value>
        </constraint>

        <constraint name="issue">
                      <value>
                                <element ns="http://www.marklogic.com/app/meta"; 
name="IssueId"/>
                                <term-option>unstemmed</term-option>
                        </value>
        </constraint>

so whenever i supply the query text based on the above constraints i get the 
non-English document results along with the English contents. For example if my 
application URL is http://myapi.com/metadata?q=book:Physics&s=19&p=10 i get 
results of non-English document along with English documents.

 But in my search option i also have constraints as ::
<constraint name="subject">
<range type="xs:string" collation="http://marklogic.com/collation/"; 
facet="true">
<element ns="http://www.marklogic.com/app/meta"; name="Subject"/>
<facet-option>frequency-order</facet-option>
<facet-option>descending</facet-option>
</range>
</constraint>
<constraint name="keyword">
<range type="xs:string" collation="http://marklogic.com/collation/"; 
facet="true">
<element ns="" name="Keyword" />
<facet-option>frequency-order</facet-option>
<facet-option>descending</facet-option>
</range>
</constraint>
<constraint name="pub">
<range type="xs:string" collation="http://marklogic.com/collation/"; 
facet="true">
<element ns="http://www.marklogic.com/app/meta"; name="Publication" />
<facet-option>frequency-order</facet-option>
<facet-option>descending</facet-option>
</range>
</constraint>
<constraint name="year">
<collection prefix="/collections/year/">
<facet-option>descending</facet-option>
</collection>
</constraint>
<constraint name="country">
<range type="xs:string" collation="http://marklogic.com/collation/"; 
facet="true">
<element ns="http://www.marklogic.com/app/meta"; name="Country"/>
<facet-option>frequency-order</facet-option>
<facet-option>descending</facet-option>
</range>
</constraint>

<constraint name="type">
<range type="xs:string" collation="http://marklogic.com/collation/"; 
facet="true">
<element ns="http://www.marklogic.com/app/meta"; name="PublicationType" />
<facet-option>frequency-order</facet-option>
<facet-option>descending</facet-option>
</range>
</constraint>

Now when my request becomes http://myapi.com/metadata?q=book:Physics 
subject:Light&s=19&p=10 i only get results from the English contents. Please 
suggest how to get the results for these constraints.

On 27 September 2012 22:05, amit gope 
<[email protected]<mailto:[email protected]>> wrote:
Hello All,

I want to apply "unstemmed" option to a range constraint. The reason being is 
that when I use the condition <term-option>unstemmed</term-option> against word 
or value, I get back non-English documents in the result set but since I cannot 
apply this to a range constraint or to a collection, hence I don't get the 
non-English documents in the result set. Please explain how to achieve this.



--
Regards
Amit





--
Regards
Amit



_______________________________________________
General mailing list
[email protected]<mailto:[email protected]>
http://developer.marklogic.com/mailman/listinfo/general


_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to