topic Re: When edit document properties, new value is not searchable in Alfresco Archive

When edit document properties, new value is not searchable

entropicsinkhol — Thu, 04 Sep 2014 18:09:47 GMT

Alfresco 5.0.a - Documents arriving in Alfresco's repository have custom properties (mapped from Ephesoft). Once arriving in Alfresco via CMIS, the values show up correctly in Alfresco's property fields (using Types, not Aspects). You can search for these properties no problem. But if you change

Re: When edit document properties, new value is not searchable

mitpatoliya — Fri, 05 Sep 2014 06:57:00 GMT

You are changing value where? from alfresco interface or Ephesoft. You should check noderef properties stored in alfresco weather those are changed or not. If your new values are avilable in alfresco noderefs then it is the issue of indexes.
So, basically three areas you need to look.
If editing done from ephesoft–> Check for syncing of property value with alfresco
Check for nodeRef properties
If alfresco values are updates–> Check for indexing issue

Re: When edit document properties, new value is not searchable

entropicsinkhol — Fri, 05 Sep 2014 16:22:48 GMT

Thanks! The changes were made in Alfresco (select document then click 'Edit Properties', then save it)

On the Alfresco end, I've already tried re-running the Solr indexing. SOLR.log is set to 'debug' mode, but I'm not seeing any obvious errors.

Looking into noderefs, but not sure where/how to start to look at the properties?

Re: When edit document properties, new value is not searchable

mitpatoliya — Sat, 06 Sep 2014 06:39:36 GMT

Re: When edit document properties, new value is not searchable

entropicsinkhol — Mon, 08 Sep 2014 15:36:00 GMT

HUGE EDIT (The minute I posted it, I figured out my syntax mistake).

When I searched using TYPE: "docmgmt:docmgmt" it brought up a list of the documents. And all the properties I changed (that couldn't be searched for) were there correct.

So, does this mean indexing is the issue?

IGNORE BELOW (Left in case it's useful to someone else) —————————————–

Well, spent the morning playing with NodeBrowser and reading various wiki 'How-Tos' on using lucene search syntax, etc. I have no idea what I'm doing.

So, I went to the NodeBrowser page. I couldn't search for nodeRef. It was already listed as a something to select under 'search' option. Couldn't find out how to bring up a list of properties (attached a screenshot search page so you know what I'm looking at). When you mentioned properties, I was expecting a list of options (like in a file) where I could turn features on/off. Apparently not?

So then I assumed that this page could be used to locate search for Types, but I'm obviously doing something wrong as I couldn't even get results from that. I tried various versions of the syntax listed on the webpages below:

https://wiki.alfresco.com/wiki/Full_Text_Search_Query_Syntax
https://wiki.alfresco.com/wiki/Search#Finding_Nodes_By_Type
http://simchaudhary.blogspot.ca/2012/05/lucene-searching-in-alfresco.html

For example, for the search I typed TYPE:"docmgmt" (syntax listed was TYPE:"qname")

Also tried searching for:

TYPE:"{http://www.alfresco.org/model/content/1.0}content"
TYPE:"cm:content"
TYPE:"content"

Below is a small portion of my custom model xml file, so you can see the naming I used:

<code>
<namespaces>
      <namespace uri="work.model" prefix="docmgmt"/>
   </namespaces>

   <types>

      <!– Definition of new Content Type: Standard Operating Procedure –>
      <type name="docmgmt:docmgmt">
         <title>docmgmt Document Procedure</title>
         <parent>cm:content</parent>
         <properties>
            <property name="docmgmt:invoiceDate">
               <type>d:text</type>
            </property>
<blockcode>

Re: When edit document properties, new value is not searchable

entropicsinkhol — Tue, 09 Sep 2014 13:39:07 GMT

So, I can search for the changed fields using docmgmt:[fieldname]:'[valuetosearchfor]' with no problem.

So this actually appears to be a similar problem that I had with the last version (4.2+). That one was resolved by changing the namespace name, but that didn't work this time.

Looking into modifying the search config, which is apparently stored in a jar file in Alfresco 5 –> as per kaynezhang's Reply to #14: https://forums.alfresco.com/forum/developer-discussions/content-modeling/search-custom-properties-05302012-2038

Will post results