<div dir="ltr">For subject/topic searches, we don't give the whole choice to the user (i.e. we prefer some Bibles based on context in the search bar, but always complement them with other key modules). So key functionality would appear to be broken if the ESV index happened to have no heading stems. (It wouldn't break badly, it just would look like something's missing/gone/was there and no longer is). On the Desktop/Mobile, we ensure (will be ensuring) at setup time that some modules/Bibles are installed as mandatory. <div>
<br></div><div>IMHO, if the user expects stuff in an area of the screen and it's blank, this is akin to broken. Similarly, if the out-of-the-box install looks different on 1 computer than it does on another (which has BD on it already), then this would be a bug for us to resolve.</div>
<div><br></div><div>Chris</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 21 April 2014 19:25, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div class=""><br><div><div>On Apr 21, 2014, at 1:24 PM, Chris Burrell <<a href="mailto:christopher@burrell.me.uk" target="_blank">christopher@burrell.me.uk</a>> wrote:</div>
<br><blockquote type="cite"><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<span style="font-family:arial,sans-serif;font-size:13px">DM>Right now, if we use the same analyzer for search and for index construction across all fields, we can share the same indexes even if we use different index policy adapters.</span><br>
</div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<font face="Verdana, Geneva, Helvetica, Arial, sans-serif">CJB> I'm not sure this is true? If BD is configured to disable headings in the policy adapter, but STEP has headings enabled in the Policy adapter, then the index will contain different content. I.e. STEP will lack headings if BD created the index. BD will not suffer, if STEP has created the index. This would then break the auto-completing aggregation aforementioned. Or am I mis-understanding something?</font></div>
<br></blockquote></div><br></div><div><div>Not really missing anything. There are many modules without headings. Obviously STEP has to cope with not being able to search that module for headings.</div><div><br></div><div>
Likewise, if one app wants to allow searching of headings and the index does not have that field, it behaves the same way, the index works properly and does not return a wrong answer. It merely returns no answer. The index is fully compatible between the two applications from a Lucene perspective. Not ideal, but certainly not a broken index.</div>
</div></div></blockquote></div><br></div>