On 27/04/11 19:50, Walter Underwood wrote:
This kind of thing is really easy in an XML database. That is an XPath
expression, not even a search.
Indeed, in fact SIREn is based on a XML IR technique, i.e., a simplified
node-based indexing scheme.
--
Renaud Delbru
This kind of thing is really easy in an XML database. That is an XPath
expression, not even a search.
MarkLogic implements it with search engine technology, but you don't have to
care about that.
wunder
Walter Underwood, MarkLogic
On Apr 27, 2011, at 11:43 AM, Renaud Delbru wrote:
> On 27/04/
On 27/04/11 19:37, Renaud Delbru wrote:
Hi Jason,
On 27/04/11 19:25, Jason Rutherglen wrote:
Renaud,
Can you provide a brief synopsis of how your system works?
SIREn provides a new "field type" for Solr. In this particular SIREn
field, the data is not a piece of text, but is organised in a t
Hi Jason,
On 27/04/11 19:25, Jason Rutherglen wrote:
Renaud,
Can you provide a brief synopsis of how your system works?
SIREn provides a new "field type" for Solr. In this particular SIREn
field, the data is not a piece of text, but is organised in a table.
Then, SIREn provides query object
Thanks Renaud - I'll look into that asap.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Search-across-related-correlated-multivalue-fields-in-Solr-tp2871176p2871395.html
Sent from the Solr - User mailing list archive at Nabble.com.
Renaud,
Can you provide a brief synopsis of how your system works?
Jason
On Wed, Apr 27, 2011 at 11:17 AM, Renaud Delbru wrote:
> Hi,
>
> you might want to look at the SIREn plugin [1,2], which allows you to index
> and query 1:N relationships such as yours, in a tabular data format [3].
>
> [1
Thanks Jonathan. We thought this through and have done quite a bit of digging
on this and saw there was no easy way around this. It was our last attempt
to post to the forum and see if there was some killer feature we were
missing somehow
We thought of the concatenated fields route, but quickly g
Hi,
you might want to look at the SIREn plugin [1,2], which allows you to
index and query 1:N relationships such as yours, in a tabular data
format [3].
[1] http://siren.sindice.com/
[2] https://github.com/rdelbru/SIREn
[3]
https://dev.deri.ie/confluence/display/SIREn/Indexing+and+Searching+
There is no great way.
One approach would be to 'de-normalize' at index time, to actually have
a field that looks like this:
institution_year: 2010.OHIO_ST ; 2007.YALE
Then, with some code on client side, you could more easily facet and
search how you want. It still doesn't (I don't think
