[MarkLogic Dev General] Question on creating a facet using document property in Marklogic 4.1-1 / Application Builder

[Danny Sokolsky]

Hi Sundar,

I expect this is because the default searchable-expression is fn:collection(), and properties are their own fragments and are not returned from collection().   You need to search over the properties for these to show up (for example, xdmp:document-properties()).      To do this, you will have to modify the searchable-expression element in the options node generated by Application Builder.

If what you are trying to do is use this facet combined with data in the corresponding documents, you might consider putting the information in your meta:filetype element in your document instead of in a property.  One approach would be to put it as an attribute value on some node (maybe the root node) of your document.

-Danny

From: general-bounces at developer.marklogic.com [mailto:general-bounces at developer.marklogic.com] On Behalf Of Sundar Iyer
Sent: Thursday, October 15, 2009 1:59 PM
To: general at developer.marklogic.com
Subject: [MarkLogic Dev General] Question on creating a facet using document property in Marklogic 4.1-1 / Application Builder

Hello,

I'm trying to create a facet using a document property. Hence, I created a element range index as below.

scalar type: string
namespace uri: http://www.company.com/meta
localname: filetype
collation: Root collation
range value positions: false

You can presume that I've set doucment property as below:


<prop:properties xmlns:prop="http://marklogic.com/xdmp/property">

  <dls:version xmlns:dls="http://marklogic.com/xdmp/dls">
            .... dls entries .....

  </dls:version>
  <dls:update-permissions xmlns:dls="http://marklogic.com/xdmp/dls">

            .... more elemnets here. ...

  </dls:update-permissions>
   <meta:filetype xmlns:meta="http://www.company.com/meta">doc</meta:filetype>
</prop:properties>



After deploying the application built using the application builder,  the filetype facet doesn't show any entries although it contains lots of matching documents.



Can someone help me to resolve this.



Is there a problem in my element range definition Or Is there a bug in the way application builder interprets element range indexes created on document properties.



Thanks

Sundar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://xqzone.marklogic.com/pipermail/general/attachments/20091015/ed7dac60/attachment.html