Content modeling and indexing

[drisschelouati]

Hi,

i had some issue working with my custom types (2 subtypes of cm:content for witch i also created advanced search forms)

1- Tags and categories work fine with the 2 subtypes (i can add to a custom type as much tags and categories as i want) but they are not effectively associated to the document (means i dont get any result when clicking on a tag  or a category in the document library), it shows "no content to show" eventhow i can see several elements next to the tags (shown like this : "Invoicing (3)", but no result if i click it)

2- My advanced search custom forms dont give me any result, like if the custom properties are not handled by Solr or something (or not indexed)


Does it have something to do with the search configuration as stated in the alfresco documentation?:

<type name="cm:content">
   <title>Content</title>
     <parent>cm:cmobject</parent>
      <properties>
        <property name="cm:content">
          <type>d:content</type>
          <mandatory>false</mandatory>
           <index enabled="true">
             <facetable>true</facetable>
             <atomic>false</atomic>
             <tokenised>true</tokenised>
           </index>
        </property>
      </properties>
</type>

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

and this example of indexing defaults:

<index enabled="true">
  <atomic>true</atomic>
  <stored>false</stored>
  <tokenised>true</tokenised>
</index>
‍‍‍‍‍‍‍

Should i  use some of those search properties to make my custom content indexed by Solr? I didnt get the meaning of "Tokenization", "faceting" and "atomic" indexing.


What should i do to solve those issues, did i miss something?

Thank you

[dsmith]

Not sure on #1, but on #2, I didn't define any < index > element for my custom types and Adv. Search is working well.  Maybe if you defined custom index settings try commenting them out?  The wiki page <a href="https://wiki.alfresco.com/wiki/Full-Text_Search_Configuration#Data_dictionary_options">here</a> has a good description of each field.  For most data, it would appear the defaults inherited from cm:content should do fine.

Facetable isn't listed but usually has to do with counting how many results match each search parameter (IE: "dogs(5), big(2), yellow(3)"), so you can drill down like in an online store.  So it shouldn't cause search failure either way.