<?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 Re: Alfresco search and file extension in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-search-and-file-extension/m-p/249867#M202997</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;That use case should be fine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However, the lucene standard analyser we use by default can create some unexpected tokens trying to handle dates, product codes etc.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The latest versions of Alfrecso have cm:name tokenised and "as is" so you can do FTS and pattern mathing using Alfresco FTS (which is now exposed directly via share although you may not know it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; )&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can change the tokenizer for all d:text properties to avoid the lucene tokenisation funnies - but not yet per property&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Jan 2011 09:46:55 GMT</pubDate>
    <dc:creator>andy</dc:creator>
    <dc:date>2011-01-26T09:46:55Z</dc:date>
    <item>
      <title>Alfresco search and file extension</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-search-and-file-extension/m-p/249866#M202996</link>
      <description>Hi,We're struggling with searching the Alfresco index. It looks like Alfresco needs the file extension in the search-string in order to find the correct files.eg: we have a file test alfresco.docWhen we use alfresco as a search-term the document isn't found. However, when we search for alfresco* or</description>
      <pubDate>Thu, 20 Jan 2011 14:00:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-search-and-file-extension/m-p/249866#M202996</guid>
      <dc:creator>ruudruud</dc:creator>
      <dc:date>2011-01-20T14:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: Alfresco search and file extension</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-search-and-file-extension/m-p/249867#M202997</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;That use case should be fine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However, the lucene standard analyser we use by default can create some unexpected tokens trying to handle dates, product codes etc.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The latest versions of Alfrecso have cm:name tokenised and "as is" so you can do FTS and pattern mathing using Alfresco FTS (which is now exposed directly via share although you may not know it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; )&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can change the tokenizer for all d:text properties to avoid the lucene tokenisation funnies - but not yet per property&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Jan 2011 09:46:55 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-search-and-file-extension/m-p/249867#M202997</guid>
      <dc:creator>andy</dc:creator>
      <dc:date>2011-01-26T09:46:55Z</dc:date>
    </item>
  </channel>
</rss>

