/usr/share/doc/lire/dev-manual/ch04s02.html is in lire-devel-doc 2:2.1.1-2.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Writing an Analyser</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Lire Developer's Manual"><link rel="up" href="ch04.html" title="Chapter 4. Writing a New DLF Analyser"><link rel="prev" href="ch04.html" title="Chapter 4. Writing a New DLF Analyser"><link rel="next" href="ch04s03.html" title="DLF Analyser API"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Writing an Analyser</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Writing a New DLF Analyser</th><td width="20%" align="right"> <a accesskey="n" href="ch04s03.html">Next</a></td></tr></table><hr></div><div class="section" title="Writing an Analyser"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sect:writing-analyser"></a>Writing an Analyser</h2></div></div></div><p>When a categoriser isn't sufficient for your needs, you
can write an <code class="classname">Lire::DlfAnalyser</code> which
gets complete control on the analysis process. The main
difference with at categoriser is that the
<code class="methodname">dst_schema</code> method will contain
refer to a derived schema instead of an extended schema.
</p><p>The core of the analyser is done in the
<code class="methodname">analyse</code> method that takes
a reference to the store onto which data will be analysed
and to a <code class="classname">Lire::DlfAnalyserProcess</code>
callback object which should be use to write new DLF records
and report errors. The method also receives the plugin
configuration data. The analyser should create a
<code class="classname">Lire::DlfQuery</code> to select the records
necessary for its analysis.
</p><p>The <code class="filename">doc/examples</code> in the source
distribution contains the a boiler plate for witing an Analyser.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch04s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Writing a New DLF Analyser </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> DLF Analyser API</td></tr></table></div></body></html>
|