You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2016/08/11 12:01:20 UTC

[jira] [Commented] (LUCENE-5317) Concordance capability

    [ https://issues.apache.org/jira/browse/LUCENE-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417097#comment-15417097 ] 

Tim Allison commented on LUCENE-5317:
-------------------------------------

Now available via Maven central.

<!-- https://mvnrepository.com/artifact/org.tallison.lucene/lucene-5317 -->
<dependency>
    <groupId>org.tallison.lucene</groupId>
    <artifactId>lucene-5317</artifactId>
    <version>6.1-0.2</version>
</dependency>

If anyone has an interest in helping me change the namespace back to org.apache.lucene, let me know. ;)

> Concordance capability
> ----------------------
>
>                 Key: LUCENE-5317
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5317
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: core/search
>    Affects Versions: 4.5
>            Reporter: Tim Allison
>              Labels: patch
>         Attachments: LUCENE-5317.patch, LUCENE-5317.patch, concordance_v1.patch.gz, lucene5317v1.patch, lucene5317v2.patch
>
>
> This patch enables a Lucene-powered concordance search capability.
> Concordances are extremely useful for linguists, lawyers and other analysts performing analytic search vs. traditional snippeting/document retrieval tasks.  By "analytic search," I mean that the user wants to browse every time a term appears (or at least the topn)  in a subset of documents and see the words before and after.  
> Concordance technology is far simpler and less interesting than IR relevance models/methods, but it can be extremely useful for some use cases.
> Traditional concordance sort orders are available (sort on words before the target, words after, target then words before and target then words after).
> Under the hood, this is running SpanQuery's getSpans() and reanalyzing to obtain character offsets.  There is plenty of room for optimizations and refactoring.
> Many thanks to my colleague, Jason Robinson, for input on the design of this patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org