<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Indexing option, luceneSearch sort option in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/indexing-option-lucenesearch-sort-option/m-p/208002#M161132</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have the question:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1) in the WiKi (&lt;/SPAN&gt;&lt;A href="http://wiki.alfresco.com/wiki/Full-Text_Search_Configuration" rel="nofollow noopener noreferrer"&gt;http://wiki.alfresco.com/wiki/Full-Text_Search_Configuration&lt;/A&gt;&lt;SPAN&gt;) we have this info:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;The indexing behaviour of each property can be set in the content model. By default, they are indexed atomically. The property value is not stored in the index, and the property is tokenised when it is indexed.&lt;/BLOCKQUOTE&gt;&lt;SPAN&gt;If I understand correctly by default the indexing is enabled also is enabled a tokenisation.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2) the lucene Search have this condition to the field which we use for sorting (&lt;/SPAN&gt;&lt;A href="http://lucene.apache.org/java/2_3_2/api/org/apache/lucene/search/Sort.html" rel="nofollow noopener noreferrer"&gt;http://lucene.apache.org/java/2_3_2/api/org/apache/lucene/search/Sort.html&lt;/A&gt;&lt;SPAN&gt;&lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;The field must be indexed, but should not be tokenized, and does not need to be stored (unless you happen to want it back with the rest of your document data).&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt;3) I installed alfresco, imported information and forced a full reindex. In the contentModel.xml the "cm:title" field use default indexing options - don't have the &amp;lt;index&amp;gt;&amp;lt;/index&amp;gt; section. From #1 -&amp;gt; this field is indexed and tokenised.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Then WHY I can sort result by "cm:title" in the luceneSearch?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 06 Apr 2009 17:09:09 GMT</pubDate>
    <dc:creator>serverok</dc:creator>
    <dc:date>2009-04-06T17:09:09Z</dc:date>
    <item>
      <title>Indexing option, luceneSearch sort option</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/indexing-option-lucenesearch-sort-option/m-p/208002#M161132</link>
      <description>I have the question:1) in the WiKi (http://wiki.alfresco.com/wiki/Full-Text_Search_Configuration) we have this info:The indexing behaviour of each property can be set in the content model. By default, they are indexed atomically. The property value is not stored in the index, and the property is tok</description>
      <pubDate>Mon, 06 Apr 2009 17:09:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/indexing-option-lucenesearch-sort-option/m-p/208002#M161132</guid>
      <dc:creator>serverok</dc:creator>
      <dc:date>2009-04-06T17:09:09Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing option, luceneSearch sort option</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/indexing-option-lucenesearch-sort-option/m-p/208003#M161133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It is possible to order at the moment it just will not always be right (as it will use the tokens - so anything containing any token starting with "a" will be near the top …).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;In some cases lucene may complain.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This is a trade off between FTS search and ordering.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;In later versions we support FTS and ordering for some properties (like name). Then ordering and FTS will both be correct.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;There are now more options for tokenisation in the property definition in the data dictionary.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;"both" supports ordering and FTS.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Apr 2009 10:29:47 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/indexing-option-lucenesearch-sort-option/m-p/208003#M161133</guid>
      <dc:creator>andy</dc:creator>
      <dc:date>2009-04-07T10:29:47Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing option, luceneSearch sort option</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/indexing-option-lucenesearch-sort-option/m-p/208004#M161134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thank you Andy for your answer. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But we have encountered with these two questions:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1) What is the best/fastest method to correctly sort lucene results by properties that contain multiple tokens?&amp;nbsp; Is the only choice to sort "manually" in the web script after running the lucene query without sorting?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Can you tell us more specifically which versions when you said&amp;nbsp; "In later versions we support FTS and ordering for some properties (like name)"?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2009 20:35:13 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/indexing-option-lucenesearch-sort-option/m-p/208004#M161134</guid>
      <dc:creator>serverok</dc:creator>
      <dc:date>2009-04-09T20:35:13Z</dc:date>
    </item>
  </channel>
</rss>

