Hi,
I'm using geonetwork 2.4 as a basis for an interface using most of the
geocat features (i've not yet really finished the migration, but when i'm
ready, i'll try to write a how-to). It uses CSW to perform the searches.
For the moment, it looks like the searches are case-sensitive. E.g., i have
some Vmap0 data in the catalog. I'm getting different results when i perform
a search for 'vmap0' (11 results) and when i look for 'VMap0' (no result),
whereas the keyword in the MD is 'VMap0'. Is it a specifi feature of CSW (i
mean, do i have to add a tag to way i want case-insensitive searches)
combined with sort of minor-case searches in lucene, or is ti a bug
somewhere in GN 2.4 ?
Did someone face this before ?
Thanks
Jean
------
N'imprimez ce message qu'en cas de nécessité. Soyons éco-responsables !
Donnez une nouvelle dimension à vos données…
I G E
Jean POMMIER
*Directeur Associé*
TIC - Webmapping 3D
Port : +33 6 09 23 21 36
Skype : igejean
Information Géographique et Environnement
12 rue Arnaud Vidal
31000 Toulouse
France
Tel : +33 5 61 86 81 49
Fax : +33 5 61 86 09 23
Mail : contact@anonymised.com
Site web : www.ige.fr <http://wwww.ige.fr>
*L'actualité d'IGE sur RSS : *http://www.ige.fr/actualites/rss.php
*Localisez IGE dans WorldWind : *
worldwind://goto/world=Earth&lat=43.55519&lon=1.38256&alt=190&dir=26.7&tilt=60.3
Additionnal info : when i perform a search on the keywords, i get exactluy
the contrary : 'VMap0' gives me the results, and 'vmap0' nothing
I'm lost... :o(
Any idea ?
2009/8/3 Jean Pommier (IGE) <jean.pommier@anonymised.com>
Hi,
I'm using geonetwork 2.4 as a basis for an interface using most of the
geocat features (i've not yet really finished the migration, but when i'm
ready, i'll try to write a how-to). It uses CSW to perform the searches.
For the moment, it looks like the searches are case-sensitive. E.g., i have
some Vmap0 data in the catalog. I'm getting different results when i perform
a search for 'vmap0' (11 results) and when i look for 'VMap0' (no result),
whereas the keyword in the MD is 'VMap0'. Is it a specifi feature of CSW (i
mean, do i have to add a tag to way i want case-insensitive searches)
combined with sort of minor-case searches in lucene, or is ti a bug
somewhere in GN 2.4 ?
Did someone face this before ?
Thanks
Jean
------
N'imprimez ce message qu'en cas de nécessité. Soyons éco-responsables !
Donnez une nouvelle dimension à vos données…
I G E
Jean POMMIER
*Directeur Associé*
TIC - Webmapping 3D
Port : +33 6 09 23 21 36
Skype : igejean
Information Géographique et Environnement
12 rue Arnaud Vidal
31000 Toulouse
France
Tel : +33 5 61 86 81 49
Fax : +33 5 61 86 09 23
Mail : contact@anonymised.com
Site web : www.ige.fr <http://wwww.ige.fr>
*L'actualité d'IGE sur RSS : *http://www.ige.fr/actualites/rss.php
*Localisez IGE dans WorldWind : *
worldwind://goto/world=Earth&lat=43.55519&lon=1.38256&alt=190&dir=26.7&tilt=60.3
Hi Jean,
I have also noted this issue for the search on the keywords and posted a
message a couple days ago.
The search would be much more efficient if it was case-insensitive.
I haven't found a solution yet.
Pierre
Jean Pommier (IGE) wrote:
Additionnal info : when i perform a search on the keywords, i get exactluy
the contrary : 'VMap0' gives me the results, and 'vmap0' nothing
I'm lost... :o(
Any idea ?
2009/8/3 Jean Pommier (IGE) <jean.pommier@anonymised.com>
Hi,
I'm using geonetwork 2.4 as a basis for an interface using most of the
geocat features (i've not yet really finished the migration, but when i'm
ready, i'll try to write a how-to). It uses CSW to perform the searches.
For the moment, it looks like the searches are case-sensitive. E.g., i
have
some Vmap0 data in the catalog. I'm getting different results when i
perform
a search for 'vmap0' (11 results) and when i look for 'VMap0' (no
result),
whereas the keyword in the MD is 'VMap0'. Is it a specifi feature of CSW
(i
mean, do i have to add a tag to way i want case-insensitive searches)
combined with sort of minor-case searches in lucene, or is ti a bug
somewhere in GN 2.4 ?
Did someone face this before ?
Thanks
Jean
------
N'imprimez ce message qu'en cas de nécessité. Soyons éco-responsables !
Donnez une nouvelle dimension à vos données…
I G E
Jean POMMIER
*Directeur Associé*
TIC - Webmapping 3D
Port : +33 6 09 23 21 36
Skype : igejean
Information Géographique et Environnement
12 rue Arnaud Vidal
31000 Toulouse
France
Tel : +33 5 61 86 81 49
Fax : +33 5 61 86 09 23
Mail : contact@anonymised.com
Site web : www.ige.fr <http://wwww.ige.fr>
*L'actualité d'IGE sur RSS : *http://www.ige.fr/actualites/rss.php
*Localisez IGE dans WorldWind : *
worldwind://goto/world=Earth&lat=43.55519&lon=1.38256&alt=190&dir=26.7&tilt=60.3
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
--
View this message in context: http://n2.nabble.com/are-CSW-searches-case-sensitive---tp3376501p3378043.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
OK, I believe I found where the pb was. Or at least a way to by-pass it : it
looks like most of my problem resides in the fact that in the lucene
searcher (java code), Term Queries are not lower-cased. I don't really see
why.
It seems it caused an incompatibility with geocat's javascript code, and
finally, the searches failed.
Changing the javascript, in order for my csw queries to use Fuzzy queries
instead solves my problem, even if it is not really clean....
Jean
2009/8/3 Jean Pommier (IGE) <jean.pommier@anonymised.com>
Additionnal info : when i perform a search on the keywords, i get exactluy
the contrary : 'VMap0' gives me the results, and 'vmap0' nothing
I'm lost... :o(
Any idea ?
2009/8/3 Jean Pommier (IGE) <jean.pommier@anonymised.com>
Hi,
I'm using geonetwork 2.4 as a basis for an interface using most of the
geocat features (i've not yet really finished the migration, but when i'm
ready, i'll try to write a how-to). It uses CSW to perform the searches.
For the moment, it looks like the searches are case-sensitive. E.g., i
have some Vmap0 data in the catalog. I'm getting different results when i
perform a search for 'vmap0' (11 results) and when i look for 'VMap0' (no
result), whereas the keyword in the MD is 'VMap0'. Is it a specifi feature
of CSW (i mean, do i have to add a tag to way i want case-insensitive
searches) combined with sort of minor-case searches in lucene, or is ti a
bug somewhere in GN 2.4 ?
Did someone face this before ?
Thanks
Jean
------
N'imprimez ce message qu'en cas de nécessité. Soyons éco-responsables !
Donnez une nouvelle dimension à vos données…
I G E
Jean POMMIER
*Directeur Associé*
TIC - Webmapping 3D
Port : +33 6 09 23 21 36
Skype : igejean
Information Géographique et Environnement
12 rue Arnaud Vidal
31000 Toulouse
France
Tel : +33 5 61 86 81 49
Fax : +33 5 61 86 09 23
Mail : contact@anonymised.com
Site web : www.ige.fr <http://wwww.ige.fr>
*L'actualité d'IGE sur RSS : *http://www.ige.fr/actualites/rss.php
*Localisez IGE dans WorldWind : *
worldwind://goto/world=Earth&lat=43.55519&lon=1.38256&alt=190&dir=26.7&tilt=60.3
Hi Pierre,
The fact is that for keywords, gn 2.4 does provide you a select list when
you begin entering your keywords. As this list is exaustive, maybe it is not
that important, is it ?
For the other fields, in my raw gn 2.4 installation, you can make the
request more flexible by selecting a lower precision, so that it ends
acceptings all sort af capitalization. But you're true, it's not much
intuitive...
I can't tell you more, as i'm using only the geocat CSW interface, that
gives me other solutions...
2009/8/3 pierre vernier <pierre.vernier@anonymised.com>
Hi Jean,
I have also noted this issue for the search on the keywords and posted a
message a couple days ago.
The search would be much more efficient if it was case-insensitive.
I haven't found a solution yet.
Pierre
Jean Pommier (IGE) wrote:
>
> Additionnal info : when i perform a search on the keywords, i get
exactluy
> the contrary : 'VMap0' gives me the results, and 'vmap0' nothing
> I'm lost... :o(
> Any idea ?
>
> 2009/8/3 Jean Pommier (IGE) <jean.pommier@anonymised.com>
>
>> Hi,
>>
>> I'm using geonetwork 2.4 as a basis for an interface using most of the
>> geocat features (i've not yet really finished the migration, but when
i'm
>> ready, i'll try to write a how-to). It uses CSW to perform the searches.
>> For the moment, it looks like the searches are case-sensitive. E.g., i
>> have
>> some Vmap0 data in the catalog. I'm getting different results when i
>> perform
>> a search for 'vmap0' (11 results) and when i look for 'VMap0' (no
>> result),
>> whereas the keyword in the MD is 'VMap0'. Is it a specifi feature of CSW
>> (i
>> mean, do i have to add a tag to way i want case-insensitive searches)
>> combined with sort of minor-case searches in lucene, or is ti a bug
>> somewhere in GN 2.4 ?
>> Did someone face this before ?
>> Thanks
>>
>> Jean
>>
>> ------
>> N'imprimez ce message qu'en cas de nécessité. Soyons éco-responsables !
>>
>> Donnez une nouvelle dimension à vos données…
>>
>> I G E
>>
>> Jean POMMIER
>> *Directeur Associé*
>>
>> TIC - Webmapping 3D
>>
>> Port : +33 6 09 23 21 36
>> Skype : igejean
>>
>> Information Géographique et Environnement
>> 12 rue Arnaud Vidal
>> 31000 Toulouse
>> France
>>
>> Tel : +33 5 61 86 81 49
>> Fax : +33 5 61 86 09 23
>> Mail : contact@anonymised.com
>> Site web : www.ige.fr <http://wwww.ige.fr>
>>
>> *L'actualité d'IGE sur RSS : *http://www.ige.fr/actualites/rss.php
>> *Localisez IGE dans WorldWind : *
>>
worldwind://goto/world=Earth&lat=43.55519&lon=1.38256&alt=190&dir=26.7&tilt=60.3
>>
>>
>>
>
------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day
> trial. Simplify your report design, integration and deployment - and
focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>
>
--
View this message in context:
http://n2.nabble.com/are-CSW-searches-case-sensitive---tp3376501p3378043.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
Hello Jean,
2009/8/3 Jean Pommier (IGE) <jean.pommier@anonymised.com>:
For the moment, it looks like the searches are case-sensitive.
It depends on the field and the way we're indexing. If Lucene standard
analyzer is used, then field are lower cased and optionnaly tokenized
if you asked for (eg. title but not identifier which is not tokenized
nor lower cased). Then according to the filter encoding (like, eq,
neq) operator you're using you could get different results and all
combinaisons are not yet supported. Lucene search & indexing does not
behave as standard SQL queries.
As you mentionned for keywords, you could retrieve a list of indexed
keywords. You could do this for all CSW fields using the GetDomain
operation. That way you could propose to the user a filtered list of
values for each fields (which could be linked to an autocompletion
list).
If you want to do lower case search, you should probably tokenized
search fields, and lower case your inputs form value using eq
operator. Maybe an option is to have one lower cased and a non
tokenized field in the index but this will not solve all issues. We
should probably address the problem as the new OGC testsuite is more
strict on that. Anyway the GetDomain op is of good help for client
side suggestions I think.
Cheers.
Francois