<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket #906: Ability to search without accents for accented words</title>
    <link>http://localhost/ticket/906</link>
    <description>&lt;p&gt;
In Slovakia users are expecting from sites to be able to search without typing accents, for example if they do not have SK keyboard, just US. For example searching for: 'Obyvateľstvo' and 'obyvatelstvo' (population) or 'štatistika' and 'statistika' (statistics) should yield same results.
&lt;/p&gt;
&lt;p&gt;
This should work the other way around as well, as some people might enter entries without accents into CKAN instance and others might search with accents.
&lt;/p&gt;
&lt;p&gt;
For SK language simple ASCII transliteration for searched term and indexed words is sufficient (iconv ASCII&lt;em&gt;TRANSLIT).
&lt;/em&gt;&lt;/p&gt;
</description>
    <language>en-us</language>
    <image>
      <title>CKAN</title>
      <url>http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png</url>
      <link>http://localhost/ticket/906</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
      
        <dc:creator>thejimmyg</dc:creator>

      <pubDate>Tue, 06 Dec 2011 11:18:32 GMT</pubDate>
      <title>status changed; owner, repo, theme, milestone set</title>
      <link>http://localhost/ticket/906#comment:1</link>
      <guid isPermaLink="false">http://localhost/ticket/906#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;owner&lt;/strong&gt;
              set to &lt;em&gt;thejimmyg&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;repo&lt;/strong&gt;
                set to &lt;em&gt;ckan&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;theme&lt;/strong&gt;
                set to &lt;em&gt;none&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;new&lt;/em&gt; to &lt;em&gt;assigned&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;milestone&lt;/strong&gt;
                set to &lt;em&gt;current-ckan-sprint-2011-12-19&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>rgrp</dc:creator>

      <pubDate>Mon, 19 Dec 2011 13:03:13 GMT</pubDate>
      <title></title>
      <link>http://localhost/ticket/906#comment:2</link>
      <guid isPermaLink="false">http://localhost/ticket/906#comment:2</guid>
      <description>
        &lt;p&gt;
Do we need to change in core code or just configure solr?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>dread</dc:creator>

      <pubDate>Tue, 07 Feb 2012 18:31:05 GMT</pubDate>
      <title>cc set</title>
      <link>http://localhost/ticket/906#comment:3</link>
      <guid isPermaLink="false">http://localhost/ticket/906#comment:3</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;cc&lt;/strong&gt;
              &lt;em&gt;amercader&lt;/em&gt; added
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
This was done in &lt;a class="closed ticket" href="http://localhost/ticket/1701" title="enhancement: Normalize character encoding for ckan search. (closed: fixed)"&gt;#1701&lt;/a&gt; but only in a custom SOLR schema in the ecportal extension: &lt;a class="ext-link" href="https://github.com/okfn/ckanext-ecportal/commit/6682926d8895f146cdf1e52ab4fbead9b065af77"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://github.com/okfn/ckanext-ecportal/commit/6682926d8895f146cdf1e52ab4fbead9b065af77&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Can the ASCIIFoldingFilterFactory be added to core CKAN's SOLR schema for all CKAN users to benefit from?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>amercader</dc:creator>

      <pubDate>Thu, 09 Feb 2012 10:08:07 GMT</pubDate>
      <title></title>
      <link>http://localhost/ticket/906#comment:4</link>
      <guid isPermaLink="false">http://localhost/ticket/906#comment:4</guid>
      <description>
        &lt;p&gt;
Yes, I don't think there will be any problem, and we won't need to create a new version of the schema as the change is backwards compatible.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>kindly</dc:creator>

      <pubDate>Mon, 05 Mar 2012 23:33:20 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost/ticket/906#comment:5</link>
      <guid isPermaLink="false">http://localhost/ticket/906#comment:5</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;assigned&lt;/em&gt; to &lt;em&gt;closed&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                set to &lt;em&gt;fixed&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>