<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>UAIC: Participation in CLEF-IP Track</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Adrian Iftene</string-name>
          <email>adiftene@info.uaic.ro</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ovidiu Ionescu</string-name>
          <email>ovidiu.ionescu@info.uaic.ro</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>George-Răzvan Oancea</string-name>
          <email>george.oancea@info.uaic.ro</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andrei-Dumitru Balmoş</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>UAIC: Faculty of Computer Science, “Alexandru Ioan Cuza” University</institution>
          ,
          <country country="RO">Romania</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The CLEF-IP track was launched in 2009 to investigate IR techniques for patent retrieval. It is part of the CLEF 2009 evaluation campaign. Also, in 2009 we built a system in order to participate in the CLEF-IP competition. Our system has three main components: filtering module, indexing module, and searching module. Because the process of indexing of all 75 G of input documents with patents took too much time we decided to work in a peerto-peer environment with four computers. In this paper we will see how we managed to built this system.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>Our system has three main modules: module one responsible with extracting of
relevant fields from XML files, module two that indexes the relevant fields, and the
third module that does the searching. The Figure 1 presents the system architecture.</p>
      <sec id="sec-1-1">
        <title>Input</title>
      </sec>
      <sec id="sec-1-2">
        <title>Patents</title>
      </sec>
      <sec id="sec-1-3">
        <title>Results</title>
        <sec id="sec-1-3-1">
          <title>Searching Module</title>
        </sec>
      </sec>
      <sec id="sec-1-4">
        <title>Lucene</title>
      </sec>
      <sec id="sec-1-5">
        <title>Index 1</title>
      </sec>
      <sec id="sec-1-6">
        <title>Lucene</title>
      </sec>
      <sec id="sec-1-7">
        <title>Index 1</title>
      </sec>
      <sec id="sec-1-8">
        <title>Lucene</title>
      </sec>
      <sec id="sec-1-9">
        <title>Index 1</title>
      </sec>
      <sec id="sec-1-10">
        <title>Lucene</title>
      </sec>
      <sec id="sec-1-11">
        <title>Index 1</title>
        <p>Indexing
Module</p>
      </sec>
      <sec id="sec-1-12">
        <title>Patents collection (75G)</title>
        <sec id="sec-1-12-1">
          <title>Filtering Module</title>
        </sec>
      </sec>
      <sec id="sec-1-13">
        <title>Filtered</title>
      </sec>
      <sec id="sec-1-14">
        <title>Patents collection (60G)</title>
        <p>In what follows we will see details about these modules.</p>
        <sec id="sec-1-14-1">
          <title>2.1 Extracting of Relevant Fields</title>
          <p>The aim of this step is to reduce the amount of XML files that must be indexed and to
work only with relevant tags from XML files. Why? Our initial tests demonstrate that
in order to index ~150Mb we need around 94 seconds. Removing the irrelevant fields
the time need for indexing was reduced to 82 seconds.</p>
          <p>We agreed on the tags we will keep (&lt;invention-title&gt;, &lt;claim text&gt; and
&lt;abstract&gt; tags. If &lt;abstract&gt; tag would not be found we will search and keep the
&lt;description&gt; tag). These fields were determined after a review of initial
preprocessed documents.</p>
        </sec>
        <sec id="sec-1-14-2">
          <title>2.2 Index Creation</title>
          <p>
            In order to index the corpora we use Lucene
            <xref ref-type="bibr" rid="ref1">(Hatcher and Gospodnetic, 2005)</xref>
            a suite
of free libraries used for indexing and searching in large corpora. For each XML
document filtered at previous step, we add useful fields to the Index. To do this we
use Lucene Indexer class adapted for our purpose.
          </p>
          <p>Because the process of indexing of all 75 G of documents took too much (for our
initial indexing we need around 80 minutes) we decided to work in a peer-to-peer
environment. Thus, we split the initial corpora on four machines and we create
separate indexes on each of them. In this way the time necessary for indexing was
reduced to 20 minutes.</p>
        </sec>
        <sec id="sec-1-14-3">
          <title>2.3 Searching Component</title>
          <p>This component allows performing searches in index created at previous step. Starting
from patent files with size of 1 M, we extract the same tags used in indexing part and
built a Lucene query in order to search in Lucene index.</p>
          <p>When we create the Lucene query from input patent we use different boost factors
for used tags. Thus, we have the following cases:
i. The greater boost value is used when we find one tag from patent in the same
corresponding field from Lucene index. For example, this is the case
when we search words from invention-title tag of current patent in the
invention-title field of Lucene index.
ii. The boost values depend by current tag name. Thus, boost values are in
descending order starting from invention-title, claim text, abstract and
description tags.
iii. The lower boost values are used when we have cross-searches between tag
from patent and field from Lucene index. For example, if we search words
from invention-title tag from patent in abstract field from Lucene index.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>3 Submitted Run</title>
      <p>Fourteen groups submitted 70 runs at this track. We submitted one run. Details from
official evaluation are presented below:
The CLEF-IP was a new track in CLEF 2009, which utilized a collection of more than
1M patent documents from English, French and German languages with at least
100,000 documents in each language.</p>
      <p>The UAIC system, which took part in the CLEF-IP 2009 competition, has three
main components: filtering module, indexing module, and searching module. The
filtering module has the aim to reduce the amount of XML files that must be indexed
and to work only with relevant tags from XML files. The indexing module used
Lucene and because the process of indexing of all 75 G of documents took too much
we worked in a peer-to-peer environment. The searching module component allows
performing searches in index created at previous step. When we create the Lucene
query from input patent we use different boost factors for used tags.</p>
    </sec>
    <sec id="sec-3">
      <title>Acknowledgements</title>
      <p>We want to give a “thank you” to those who helped from the beginning of
the project: students from second year group 5A.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Hatcher</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Gospodnetic</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>Lucene in action</article-title>
          .
          <source>Manning Publications Co</source>
          .
          <article-title>(</article-title>
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>