Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#19 Browse function lucene query issue with OntologyService

v1.1.1
open
nobody
5
2011-11-18
2011-11-18
eggwhites
No

When a geoportal is configured with the OntologyService, and the browse tree is configured to use the Ontology syntax, there are unexpected results when a users filters on the browse page. For example, if the browse-catalog.xml is configured with entries like the following:

<item>
<name resourceKey="catalog.search.filterNoaaTopics.ocean"></name>
<query>searchText=like%20|ocean</query>
</item>

And a user clicks on this node in the tree, then filters by a term (e.g., 'marine'), the Geoportal's query to lucene is crafted as such:

marine AND like |ocean

Which in essence is "find records that have the word 'marine' in them and of those records, filter by ones that have terms that are similar to 'ocean'". What is expected is a query such as the following, which is how the query is formed on the Search Page:

Like |ocean AND marine

Which in essence is "find records that have terms that are similar to 'ocean', and of those records, filter by ones that have the word 'marine'".

The query on the Search page and the query on the Browse page should be crafted similarly such that results are consistent between the two.

Discussion