Custom Property and Advanced Search

[richardgunderse]

Hi

I can't do an advanced search on my custom property. It all seems configured correctly, I can see the value on the details screen for one of my documents, and I can see it appearing as a new search field in the Advanced Search field.

But, when I do a search on it, I get no results found, even though I can see that one of my documents definately has a value set for this property.

Here's how my property is defined:

             <property name="ix:dataSource">
                <type>d:text</type>
                <mandatory>false</mandatory>
                <!–index enabled="true">
                   <atomic>true</atomic>
                   <stored>false</stored>
                   <tokenised>false</tokenised>
                </index–>
             </property>‍‍‍‍‍‍‍‍‍

(I've commented out the index tags - they didn't seem to make any difference.

This is how the search field is defined

    <config evaluator="string-compare" condition="Advanced Search">
       <advanced-search>
          <custom-properties>
             <meta-data aspect="ix:docAspect" property="ix:dataSource"/>
          </custom-properties>
       </advanced-search>
    </config>‍‍‍‍‍‍‍‍

So if my value for dataSource is set to 'SomeDataSource' I should be able to Advanced Search –> Additional options and then enter ''SomeDataSource' and it should bring back my document, right? But it doesn't…

Any help would be great - must be something simple I am doing wrong??

[richardgunderse]

After reading a previous post, I found that I can define the field as d:content, and then in the simple search, my custom field is included in the search.

This is fine for now, but I saw that the enhancement was made some time ago to allow the custom properties to be searchable (Advanced Search).

Would still really appreciate any help. My deadline is tomorrow….! :shock:

[stefano]

This is an interesting question… can you post also the URL of the post related to d:content ?
Thank you

[richardgunderse]

Hi Stefano

Thanks for replying to my message. The post I found is this one

http://forums.alfresco.com/viewtopic.php?f=3&t=421&p=1524&hilit=atomic#p1524

If you look at the 4th entry (by Andy) he mentions that it is an enhancement in the JIRA. The JIRA though, looks as though the issue was fixed some time ago, so it should be in my version of the Alfresco code (I only downloaded it 2 weeks ago).

I wonder if it's something to do with how I have defined my aspect. Do my custom properties need to explicitly extend 'content'? I thought that happened automatically?

Any help you can give me would be really good.

Thanks

[richardgunderse]

If somebody has done this before, in the current version of Alfresco, I would really appreciate knowing the steps you performed to

1) Define the custom properties in the aspect (including indexing settings etc if relevant. An working XML sample would be great to compare with)
2) Configure the advanced search via the web client config XML file

I've followed a few tutorials now, and everything *seems* ok, but the search just refuses to bring back results that I know are there.

Thanks

[richardgunderse]

Anyone please?

[poptarts]

I would love an answer to this myself. I went through the same steps and I could never get it to work.

[davidd]

I am trying to do this as well

[rockycres]

Hi Friends,

I got the results for custom property in advance search page.In BrowseBean.java file,search parameters are there to get the results,in that storeref is one the parameter.In storeref parameter,value stored is workspace,but our webprojects are getting stored in AVM, so we are not able to get the custom property results.
i have changed the store ref value to avm.But i have hardcoded it.Hardcoding is not good way.Iam searching an alternate way to get the storeref as avm.

Friends if u find any solutions for this.Please post it

[liao1108]

After reading a previous post, I found that I can define the field as d:content, and then in the simple search, my custom field is included in the search.

This is fine for now, but I saw that the enhancement was made some time ago to allow the custom properties to be searchable (Advanced Search).

Would still really appreciate any help. My deadline is tomorrow….! :shock:

But define property as d:content make the field un-editable, don't you ?