Open eroux opened 6 years ago
In which way this would be different from http://purl.bdrc.io/query/Etexts_contents?L_NAME=%22%E0%BD%98%E0%BD%81%E0%BD%93%E0%BC%8B%E0%BD%86%E0%BD%BA%E0%BD%93%E0%BC%8B%22&LG_NAME=bo&I_LIM=10 ?
It needs to be integrated into the regular search (optionally), so that results can be displayed on http://library.bdrc.io/search?q=%22%E0%BD%98%E0%BD%81%E0%BD%93%E0%BC%8B%E0%BD%86%E0%BD%BA%E0%BD%93%22&lg=bo-x-ewts&t=Any the results could be grouped by etext entity, but the etext results shouldn't be sent by default, only when an option is set.
I'm not sure it would work, but I'm thinking that something like that could be used for the option:
with a parameter called ?searchEtexts
:
{
normal stuff
} union {
filter (?searchEtexts = "true"^^xsd:boolean)
do the search in the etext
}
I think it would be worth testing... if the Lucene search is triggered after the filter, it shouldn't be called (I think)
(all in the title)