Dezi 0.4.3 released

dezi — Wed, 16 May 2018 02:32:43 +0000

Version 0.4.3 is now on CPAN.

This fixes the POD for Dezi::Config.

Swish-e documentation

dezi — Wed, 02 May 2018 22:06:31 +0000

The original swish-e.org site is no more, but the source code is available on GitHub.

As a courtesy, the documentation is available to browse here on dezi.org.

Dezi 0.4.0 released

dezi — Fri, 01 Aug 2014 04:05:53 +0000

Dezi 0.4.0 has been released to the CPAN.

This release explicitly requires Dezi::App instead of SWISH::Prog and removes all references to the older SWISH::Prog classes.

Dezi::App

dezi — Tue, 22 Jul 2014 19:26:39 +0000

As mentioned a couple of months ago, Dezi has been Moosified. The final port of the older code has been released to CPAN as Dezi::App. The 0.400 version of Search::OpenSearch::Engine::Lucy uses Dezi::App instead of SWISH::Prog::Lucy.

Performance is comparable to the older SWISH::Prog-based code, and should provide a cleaner, more community-conformant base upon which to build.

MetaNames and PropertyNames

dezi — Fri, 18 Jul 2014 15:26:59 +0000

The configuration directives MetaNames and PropertyNames are used to define fields in Dezi. The names PropertyNames and MetaNames originate with Swish-e (see the Swish-e FAQ for a description.)

Here are some notes on the differences between those two directives and how they are implemented for Dezi with Apache Lucy. The relevant Perl classes are Dezi::Lucy::Indexer (or SWISH::Prog::Lucy::Indexer, depending on your version of Dezi).

A field defined as either a MetaName, PropertyName or both, can be searched.
Fields are matched against tag names in your XML/HTML documents. See also the TagAlias, UndefinedMetaTags, UndefinedXMLAttributes,
and XMLClassAttributes directives.
You can alias field names with MetaNamesAlias and PropertyNamesAlias.
MetaNames are tokenized and case-insensitive and (optionally, with FuzzyIndexingMode) stemmed.
PropertyNames are stored, case-sensitive strings.
If a field is defined as both a MetaName and PropertyName, then it will be tokenized.
If a field is defined only as a MetaName, it will be parsed but not stored. That means you can search on the field but when you try and retrieve the field’s value from the results, it will cause a fatal error.
If a field is defined only as a PropertyName, it will be parsed and stored, but it will not be tokenized. That means the field’s contents are stored without being split up into words.
You can control the parsing and storage of PropertyName-only fields with the following additional directives:
- PropertyNamesCompareCase – case sensitive search
- PropertyNamesIgnoreCase – case insensitive search (default)
- PropertyNamesNoStripChars – preserve whitespace
There are two default MetaNames defined: swishdefault and swishtitle.
There are two default PropertyNames defined: swishtitle and swishdescription.
The libswish3 XML and HTML parsers will automatically treat a tag as <strong>swishtitle</strong>. Likewise they will treat <body> tag as <strong>swishdescription</strong>.</li> <li>Things get complicated quickly when defining fields. Experiment with small test cases to arrive at the configuration that works best with your application.</li> </ul> </article> <article> <h1>Doozi: Dezi + Moose</h1> <p>dezi — Mon, 28 Apr 2014 15:02:10 +0000</p> <p>A post at <a href="http://blogs.perl.org/users/karpet/2014/04/doozi-dezi-moose.html">blogs.perl.org</a> on the new version of Dezi currently underway.</p> </article> <article> <h1>Ruby dezi-client 1.1.0 released</h1> <p>dezi — Sun, 02 Mar 2014 03:45:05 +0000</p> <p>The dezi-client for Ruby version 1.1.0 has been pushed to https://rubygems.org/gems/dezi-client.</p> <p>This new version uses the Faraday+Excon HTTP client and fixes a bug with multiple values for GET params.</p> </article> <article> <h1>Dezi 0.2.12 released</h1> <p>dezi — Thu, 27 Feb 2014 18:13:37 +0000</p> <p>Dezi 0.2.12 has been released to CPAN: <a href="https://metacpan.org/release/Dezi">https://metacpan.org/release/Dezi</a></p> <p>The Changelog:</p> <pre> 0.002012 27 Feb 2014 - fix Config docs re: Dezi::Admin, add auto_commit note - add --auto_commit (--ac) option to toggle auto_commit via cli </pre> </article> <article> <h1>Reserved fields</h1> <p>dezi — Wed, 13 Feb 2013 11:19:42 +0000</p> <p>Dezi is built on top of <a href="https://metacpan.org/release/SWISH-3/">SWISH::3</a> and <a href="https://metacpan.org/release/SWISH-Prog">SWISH::Prog</a>, which reserve several built-in field names.</p> <p>Here’s a list of the reserved, built-in field names:</p> <ul> <li>swishdefault</li> <li>swishdescription</li> <li>swishdocpath</li> <li>swishdocsize</li> <li>swishencoding</li> <li>swishlastmodified</li> <li>swishmime</li> <li>swishparser</li> <li>swishtitle</li> <li>swishwordnum</li> </ul> <p>The following method names are reserved in <a href="https://metacpan.org/module/SWISH::Prog::Result">SWISH::Prog::Result</a> which are mapped to the built-in field names:</p> <table> <tr> <th>built-in</th> <th>method</th> </tr> <tr> <td>swishdocpath</td> <td>uri</td> </tr> <tr> <td>swishlastmodified</td> <td>mtime</td> </tr> <tr> <td>swishtitle</td> <td>title</td> </tr> <tr> <td>swishdescription</td> <td>summary</td> </tr> </table> <p>Dezi results come from <a href="https://metacpan.org/module/Search::OpenSearch">Search::OpenSearch</a> which uses the method names from SWISH::Prog::Result as the default attribute names.</p> <p>In addition, the SWISH::3 parser aliases some common tag names to built-in fields, in order for HTML documents to get parsed in a more intuitive way. Those tags are <b><code>title</code></b> which is mapped to <b><code>swishtitle</code></b> and <b><code>body</code></b> which is mapped to <b><code>swishdescription</code></b>.</p> <p>Avoid the use of any of these built-in field or method names when you are defining fields in your Dezi configuration. Behavior is unpredictable if there are any namespace collisions.</p> </article> <article> <h1>The –elastic feature</h1> <p>dezi — Wed, 13 Feb 2013 10:53:06 +0000</p> <p>New in Dezi 0.2.10 is the <code>--elastic</code> feature. This option is shorthand for:</p> <pre> engine_config => { indexer_config => { config => { UndefinedMetaTags => 'autoall', } } } </pre> <p>But instead of all that, just pass the <code>--elastic</code> option when you start the server:</p> <pre> % dezi --elastic </pre> <p>The <code>--elastic</code> feature makes your Dezi server act like Elasticsearch: fields are created simply by adding a document that contains them. So when you do this:</p> <pre> $ curl -XPOST 'http://localhost:5000/index/blog/post/1' -d ' { "user": "dilbert", "postDate": "2011-12-15", "body": "Search is hard. Search should be easy." , "title": "On search" }' -H 'Content-Type: application/json' </pre> <p>the fields for <code>user</code> and <code>postdate</code> spring into existence.</p> <p>Note that all field names are lowercased, so <code>postDate</code> becomes <code>postdate</code>. </p> <p>Note also that there are some reserved field names, so <code>title</code> is not added as a field because the <code>title</code> field is already aliased to <code>swishtitle</code>. Likewise, <code>body</code> is aliased to <code>swishdescription</code>.</p> <p>The elastic feature requires the following supporting modules:</p> <ul> <li>SWISH::3 1.000006</li> <li>SWISH::Prog::Lucy 0.17</li> </ul> </article> </main></body></html>