<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 1, 2009, at 3:33 AM, Ben Morgan wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><span class="gmail_quote">On 01/03/2009, <b class="gmail_sendername">Peter von Kaehne</b> <<a href="mailto:refdoc@gmx.net">refdoc@gmx.net</a>> wrote:</span> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">It appears that all clucene/lucene capable frontends can do proximity searches. BpBible exposes this via its GUI, others rely on the clucene/lucene syntax.<br> <br>Q: Is there anything particular about bpbible's proximity searches or do I simply use the wrong syntax?<br><br>I get on the ABU in xiphos for the following search "god love"~15 32 results, but on bpbible with a proximity search limited to 15 words distance I get 56 hits.</blockquote> <div>BPBible's proximity is an approximation based on some average length of word (~5 letters, I think... - though it may be calculated from the module). So results may not be directly comparable.</div><br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Looking at the list I am find only single verse references in xiphos, but my understanding is that crossboundary searches should be possible.<br> <br>What am I doing wrong? Or is in fact crossboundary search not possible in other frontends?</blockquote> <div> </div> <div>I don't believe proper crossboundary search is possible (as lucene has documents). BPBible also allows (for example) phrases to cross verse boundaries. I don't think any of the others do.</div></div></blockquote><br></div><div>You are mostly right about cross-boundary search, where the boundary is a verse or chapter. JSword does have a limited support for cross-boundary search. But the user has to specify such a choice. It is not automatic.</div><div><br></div><div>I have talked with the Lucene folk about searching adjacent documents and they don't see it being added to core. Their suggestion was to have multiple documents per verse. The first set of documents would be as it is today. The second set of documents would span a particular number of documents, say 2 adjacent verses or the chapter. The size is dependent upon the assumption that a user would not search for phrases or other things beyond that size.</div><div><br></div><div>A phrase search in the second set of documents would find phrases that did not exceed 2 verses or the chapter (using the given example).</div><div><br></div><div>Another approach would be to be to use offsets for the words. Typically Lucene starts the offset for the first term for the document at 0. The second at 2. And so forth. This is a function of the Analyzer and of the Field. But it is possible to change the offsets to be the term position in the source. (Note, this can be used to store alternate terms, n-grams, word forms, etc at the same position.)</div><div><br></div><div>While true cross-boundary search is useful in some situations. I don't think it is very useful. I think most people will use search to find a verse or a short passage.</div><div><br></div><div>For the most part, searching verses in isolation is more than sufficient.</div><div><br></div><div>I'd like to hear other thoughts on the usefulness of proper passage searching.</div><div><br></div><div>In Him,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>DM<br></div><div><br></div><div><br></div><br></body></html>