So, the immediate question is whether the value in the Solr source document
has the full taxonomy path for the species, or just parts, and some external
taxonomy definition must be consulted to "fill in" the rest of the hierarchy
path for that species.
-- Jack Krupansky
-----Original Message-----
From: Dan Bolser
Sent: Saturday, July 5, 2014 10:36 AM
To: solr-user@lucene.apache.org
Subject: Re: Field for 'species' data?
One requirement is that the hierarchical facet implementation marches
whatever the Drupal ApacheSolr module does with taxonomy terms.
The key thing is to add the taxonomy to the doc which only has one 'leaf'
term.
On 5 Jul 2014 15:01, "Jack Krupansky" <j...@basetechnology.com> wrote:
Focus on your data model and queries first, then you can decide on the
implementation.
Take a semi-complex example and manually break it down into field values
and then write some queries, including filters, in English, that do the
required navigation. Once you have a handle on what fields you need to
populate, the analysis and processing details can be worked out.
-- Jack Krupansky
-----Original Message----- From: Dan Bolser
Sent: Saturday, July 5, 2014 4:49 AM
To: solr-user
Subject: Re: Field for 'species' data?
I'm super noob... Why choose to write it add a custom update request
processor rather than an analysis pipeline?
Cheers, Dan.
On 5 Jul 2014 03:45, "Alexandre Rafalovitch" <arafa...@gmail.com> wrote:
Do that with a custom update request processor.
Just remember Solr is there to find things not to preserve structure. So
mangle your data until you can find it.
Also check if SirenDB would fit your requirements if you want to encode
the
information as complex structure.
Regards,
Alex
