[GeoNetwork-users] Thesaurus support / online demo

[Lagarde_Pierre]

Hi françois,

Very good to start the integration of french developments of GN (Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate keywords (we don't use this solution in Geosource. See http://212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be better to limit the thesaurus query in the thematic of the keywords in function of the 19115 list. For example, place thesauri, theme thesauri,... And, when the user has chosen a specific word, GN could add the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net [mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part de François Prunayre
Envoyé : vendredi 5 janvier 2007 17:19
À : geonetwork-devel@lists.sourceforge.net; geonetwork-users@anonymised.comforge.net
Objet : [GeoNetwork-users] Thesaurus support / online demo

Hi list, here is a first demo adding support for thesaurus in Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such as Agrovoc, Gemet or other in rdf/skos format and creation of "local" thesaurus which will be entirely managed by the administrator of the geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for each
term) used for thesaurus of type discipline, theme, temporal or of type place where you could also defined a bounding box for each term. Thesaurus creation only support flat thesaurus (ie. you can not defined narrower, broader and related term).
When editing metadata, geonetwork will provide an autocompletion field for keyword searching in all thesaurus available in the current node.
When searching for metadata, in the search field keyword, an autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / password admin. Go to the administration > Manage thesauri. The demo is set up with 3 external thesauri (agrovoc, a thesaurus for the water domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to be done for ISO19139)
- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the current webpage language. But this not really the best option. For the first implementation, maybe I proposed 2 options for the editing part :
- if a language parameter is defined in the current metadata, query the thesaurus in that language
- if not use the webpage language or we could also defined a parameter "metatada default language" ? This will allow user not having geonetwork translation (for now en, fr, es, cn) to use their own language for thesaurus.

For the search this is a more complex part. For now, if the user interface is in spanish, it will look for term in spanish in each thesaurus. If the metadata are in english ... it will not be relevant. Here as a first implementation, we could at least use a parameter "metatada default language". Other and more complex options could be, for the keyword criteria
:
- search for a term in user interface language and then query using the keyword and its translation. Here users need to have multilingual thesaurus.
- proposed the list of keyword found by Lucene in metadata in the indexing process. That way, geonetwork propose only keyword that are used somewhere in one or more metadata
- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/codelist/thesauri directory of Geonetwork. They are loaded on startup and RDF manipulation is made with Sesame, an opensource java library for RDF (http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard for their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels, confidentiels et prives. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal, confidential and secret. Any total or partial publication, use or distribution must be authorized.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
**********************************************************************************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de réception de cet
e-mail par erreur, le signaler à son expéditeur et ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient néanmoins de
vérifier l'absence de corruption à sa réception. The contents of this email and any attachments are
confidential. They are intended for
the named recipient(s) only. If you have received this email in error please notify the
system manager or the sender immediately and do not disclose the contents to
anyone or make copies. eSafe scanned this email for viruses, vandals and malicious
content.
**********************************************************************************************

[ticheler]

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a kind of middle way of handling keywords. I feel that using the auto-completion facility is the way to go, but it would need to give a more flexible way of selecting the right keywords. This should include the hierarchy in a thesaurus and also be multilingual in the first place. On that part I think the only way to go is to store a keyword identifier and not the translated keyword in the text element. The system should than use these identifiers to display the local versions of the keyword (or provide the default language of the thesaurus if no translation is available).

In the editor, the full thesaurus content should e available, while, as François indicated, in the Search interface, only keywords used in the catalog should be presented. In fact, that auto-completion as implemented by François would than be a very good first step while a pop-up could provide a full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC records. I know the alpha 2 is still not finished what the editor concerns, so I assume that is the cause. Roberto is working on it and a functional editor should be ready by the second week of February in a first beta release.

I suggest that we do not add the thesaurus functionality to the code base until the prototype is more functional if that's OK with you François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN (Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate keywords (we don't use this solution in Geosource. See http://212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be better to limit the thesaurus query in the thematic of the keywords in function of the 19115 list. For example, place thesauri, theme thesauri,... And, when the user has chosen a specific word, GN could add the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net [mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part de François Prunayre
Envoyé : vendredi 5 janvier 2007 17:19
À : geonetwork-devel@lists.sourceforge.net; geonetwork-users@lists.sourceforge.net
Objet : [GeoNetwork-users] Thesaurus support / online demo

Hi list, here is a first demo adding support for thesaurus in Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such as Agrovoc, Gemet or other in rdf/skos format and creation of "local" thesaurus which will be entirely managed by the administrator of the geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for each
term) used for thesaurus of type discipline, theme, temporal or of type place where you could also defined a bounding box for each term. Thesaurus creation only support flat thesaurus (ie. you can not defined narrower, broader and related term).
When editing metadata, geonetwork will provide an autocompletion field for keyword searching in all thesaurus available in the current node.
When searching for metadata, in the search field keyword, an autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / password admin. Go to the administration > Manage thesauri. The demo is set up with 3 external thesauri (agrovoc, a thesaurus for the water domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to be done for ISO19139)
- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the current webpage language. But this not really the best option. For the first implementation, maybe I proposed 2 options for the editing part :
- if a language parameter is defined in the current metadata, query the thesaurus in that language
- if not use the webpage language or we could also defined a parameter "metatada default language" ? This will allow user not having geonetwork translation (for now en, fr, es, cn) to use their own language for thesaurus.

For the search this is a more complex part. For now, if the user interface is in spanish, it will look for term in spanish in each thesaurus. If the metadata are in english ... it will not be relevant. Here as a first implementation, we could at least use a parameter "metatada default language". Other and more complex options could be, for the keyword criteria
:
- search for a term in user interface language and then query using the keyword and its translation. Here users need to have multilingual thesaurus.
- proposed the list of keyword found by Lucene in metadata in the indexing process. That way, geonetwork propose only keyword that are used somewhere in one or more metadata
- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/codelist/thesauri directory of Geonetwork. They are loaded on startup and RDF manipulation is made with Sesame, an opensource java library for RDF (http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard for their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels, confidentiels et prives. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal, confidential and secret. Any total or partial publication, use or distribution must be authorized.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net
**********************************************************************************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de réception de cet
e-mail par erreur, le signaler à son expéditeur et ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient néanmoins de
vérifier l'absence de corruption à sa réception. The contents of this email and any attachments are
confidential. They are intended for
the named recipient(s) only. If you have received this email in error please notify the
system manager or the sender immediately and do not disclose the contents to
anyone or make copies. eSafe scanned this email for viruses, vandals and malicious
content.
**********************************************************************************************

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

[Francois_Prunayre]

Hi, that's fine for me Jeroen, problem of storing Ids instead of keyword
could cause problem later when people export (or harwest) without having the
same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword" based on
Lucene Index (and not thesaurus). That way, user will select only keywords
which are in metadata. Here you could have a mix of multilingual keywords
according to what the editors put in.
- Lucene index configuration : Lucene will not create tokens based on
keyword but will index keyword as term (ie. "polar ecosystem" will be index
as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on the
thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2. You
will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / password
admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com]
Envoyé : lundi 8 janvier 2007 11:21
À : Lagarde Pierre; François Prunayre
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a kind of
middle way of handling keywords. I feel that using the auto- completion
facility is the way to go, but it would need to give a more flexible way of
selecting the right keywords. This should include the hierarchy in a
thesaurus and also be multilingual in the first place. On that part I think
the only way to go is to store a keyword identifier and not the translated
keyword in the text element. The system should than use these identifiers to
display the local versions of the keyword (or provide the default language
of the thesaurus if no translation is available).

In the editor, the full thesaurus content should e available, while, as
François indicated, in the Search interface, only keywords used in the
catalog should be presented. In fact, that auto-completion as implemented by
François would than be a very good first step while a pop-up could provide a
full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC records. I
know the alpha 2 is still not finished what the editor concerns, so I assume
that is the cause. Roberto is working on it and a functional editor should
be ready by the second week of February in a first beta release.

I suggest that we do not add the thesaurus functionality to the code base
until the prototype is more functional if that's OK with you François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN
(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate keywords
(we don't use this solution in Geosource. See http://
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be
better to limit the thesaurus query in the thematic of the keywords in
function of the 19115 list. For example, place thesauri, theme
thesauri,... And, when the user has chosen a specific word, GN could
add the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or
new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part de
François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :
geonetwork-devel@lists.sourceforge.net; geonetwork-
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus
support / online demo

Hi list, here is a first demo adding support for thesaurus in
Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such as
Agrovoc, Gemet or other in rdf/skos format and creation of "local"
thesaurus which will be entirely managed by the administrator of the
geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for
each
term) used for thesaurus of type discipline, theme, temporal or of
type place where you could also defined a bounding box for each term.
Thesaurus creation only support flat thesaurus (ie. you can not
defined narrower, broader and related term).
When editing metadata, geonetwork will provide an autocompletion field
for keyword searching in all thesaurus available in the current node.
When searching for metadata, in the search field keyword, an
autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin /
password admin. Go to the administration > Manage thesauri. The demo
is set up with 3 external thesauri (agrovoc, a thesaurus for the water
domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to be
done for ISO19139)
- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the
current webpage language. But this not really the best option. For the
first implementation, maybe I proposed 2 options for the editing part
:
- if a language parameter is defined in the current metadata, query
the thesaurus in that language
- if not use the webpage language or we could also defined a parameter
"metatada default language" ? This will allow user not having
geonetwork translation (for now en, fr, es, cn) to use their own
language for thesaurus.

For the search this is a more complex part. For now, if the user
interface is in spanish, it will look for term in spanish in each
thesaurus. If the metadata are in english ... it will not be relevant.
Here as a first implementation, we could at least use a parameter
"metatada default language". Other and more complex options could be,
for the keyword criteria
:
- search for a term in user interface language and then query using
the keyword and its translation. Here users need to have multilingual
thesaurus.
- proposed the list of keyword found by Lucene in metadata in the
indexing process. That way, geonetwork propose only keyword that are
used somewhere in one or more metadata
- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/codelist/
thesauri directory of Geonetwork. They are loaded on startup and RDF
manipulation is made with Sesame, an opensource java library for RDF
(http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard for
their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could
put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and earn
cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
**********************************************************************
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à
l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de
réception de cet e-mail par erreur, le signaler à son expéditeur et
ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient
néanmoins de vérifier l'absence de corruption à sa réception. The
contents of this email and any attachments are confidential. They are
intended for the named recipient(s) only. If you have received this
email in error please notify the system manager or the sender
immediately and do not disclose the contents to anyone or make copies.
eSafe scanned this email for viruses, vandals and malicious content.
**********************************************************************
************************

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and earn
cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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

-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels, confidentiels et prives. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal, confidential and secret. Any total or partial publication, use or distribution must be authorized.

[Francois_Prunayre]

Hi all, some news from the thesaurus prototype.
For now, thesaurus support allows to control vocabulary on the metadata
editing side (using autocompletion). Then Lucene will make the index based
on metadata keywords (and not on the thesaurus you have on the node).
The administration interface allows import/export/creation/browse thesaurus.

Changes are :
- Keyword / metadata edit work for ISO191XX, DC (On FGDC, edit keywords is
not working. Any ideas why ?)
- Keyword / metadata edit / ISO191XX : Search only according selected
thesaurus Type (discipline, stratum, theme, ...)
- Keyword / Added services for narrower, broader and related keyword search
- Administration / Browse thesaurus

The demo is set up with the Agrovoc thesaurus.
http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin/admin

Any comments, ideas ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
François Prunayre
Envoyé : mercredi 17 janvier 2007 15:00
À : 'Jeroen Ticheler'; 'Lagarde Pierre'
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support /online
demo

Hi, that's fine for me Jeroen, problem of storing Ids instead of keyword
could cause problem later when people export (or harwest) without having the
same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword" based on
Lucene Index (and not thesaurus). That way, user will select only keywords
which are in metadata. Here you could have a mix of multilingual keywords
according to what the editors put in.
- Lucene index configuration : Lucene will not create tokens based on
keyword but will index keyword as term (ie. "polar ecosystem" will be index
as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on the
thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2. You
will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / password
admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé : lundi 8
janvier 2007 11:21 À : Lagarde Pierre; François Prunayre Cc :
geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a kind of
middle way of handling keywords. I feel that using the auto- completion
facility is the way to go, but it would need to give a more flexible way of
selecting the right keywords. This should include the hierarchy in a
thesaurus and also be multilingual in the first place. On that part I think
the only way to go is to store a keyword identifier and not the translated
keyword in the text element. The system should than use these identifiers to
display the local versions of the keyword (or provide the default language
of the thesaurus if no translation is available).

In the editor, the full thesaurus content should e available, while, as
François indicated, in the Search interface, only keywords used in the
catalog should be presented. In fact, that auto-completion as implemented by
François would than be a very good first step while a pop-up could provide a
full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC records. I
know the alpha 2 is still not finished what the editor concerns, so I assume
that is the cause. Roberto is working on it and a functional editor should
be ready by the second week of February in a first beta release.

I suggest that we do not add the thesaurus functionality to the code base
until the prototype is more functional if that's OK with you François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN
(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate keywords
(we don't use this solution in Geosource. See http://
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be
better to limit the thesaurus query in the thematic of the keywords in
function of the 19115 list. For example, place thesauri, theme
thesauri,... And, when the user has chosen a specific word, GN could
add the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or
new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part de
François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :
geonetwork-devel@lists.sourceforge.net; geonetwork-
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus
support / online demo

Hi list, here is a first demo adding support for thesaurus in
Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such as
Agrovoc, Gemet or other in rdf/skos format and creation of "local"
thesaurus which will be entirely managed by the administrator of the
geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for
each
term) used for thesaurus of type discipline, theme, temporal or of
type place where you could also defined a bounding box for each term.
Thesaurus creation only support flat thesaurus (ie. you can not
defined narrower, broader and related term).
When editing metadata, geonetwork will provide an autocompletion field
for keyword searching in all thesaurus available in the current node.
When searching for metadata, in the search field keyword, an
autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin /
password admin. Go to the administration > Manage thesauri. The demo
is set up with 3 external thesauri (agrovoc, a thesaurus for the water
domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to be
done for ISO19139)
- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the
current webpage language. But this not really the best option. For the
first implementation, maybe I proposed 2 options for the editing part
:
- if a language parameter is defined in the current metadata, query
the thesaurus in that language
- if not use the webpage language or we could also defined a parameter
"metatada default language" ? This will allow user not having
geonetwork translation (for now en, fr, es, cn) to use their own
language for thesaurus.

For the search this is a more complex part. For now, if the user
interface is in spanish, it will look for term in spanish in each
thesaurus. If the metadata are in english ... it will not be relevant.
Here as a first implementation, we could at least use a parameter
"metatada default language". Other and more complex options could be,
for the keyword criteria
:
- search for a term in user interface language and then query using
the keyword and its translation. Here users need to have multilingual
thesaurus.
- proposed the list of keyword found by Lucene in metadata in the
indexing process. That way, geonetwork propose only keyword that are
used somewhere in one or more metadata
- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/codelist/
thesauri directory of Geonetwork. They are loaded on startup and RDF
manipulation is made with Sesame, an opensource java library for RDF
(http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard for
their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could
put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and earn
cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
**********************************************************************
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à
l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de
réception de cet e-mail par erreur, le signaler à son expéditeur et
ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient
néanmoins de vérifier l'absence de corruption à sa réception. The
contents of this email and any attachments are confidential. They are
intended for the named recipient(s) only. If you have received this
email in error please notify the system manager or the sender
immediately and do not disclose the contents to anyone or make copies.
eSafe scanned this email for viruses, vandals and malicious content.
**********************************************************************
************************

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and earn
cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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

-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et
rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels, confidentiels et prives. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal, confidential and secret. Any total or partial publication, use or distribution must be authorized.

[ticheler]

Hi Francois,
Looks very nice!

We have a range of problems we run into, some related to the editor I assume (on my Firefox the codelists appear all empty in the editor, Roberto?). On Patrizia's Internet Explorer the list did not expand with some of the ISO records.

- It would be better to filter the keyword list to only show items once.
- It's not very clear which Thesaurus you are using. Do I understand correctly that you define one thesaurus per thesaurus type now?
- When adding a keyword, the associated thesaurus name element should also be filled to point to the thesaurus. Anyone an idea what should be put here best? A URI to the rdf of the resource or so?

On Feb 13, 2007, at 8:50 AM, François Prunayre wrote:

Hi all, some news from the thesaurus prototype.
For now, thesaurus support allows to control vocabulary on the metadata
editing side (using autocompletion). Then Lucene will make the index based
on metadata keywords (and not on the thesaurus you have on the node).

Cool!! Is there a minimum number of characters a user has to type in before the query to the application for a list starts?

The administration interface allows import/export/creation/browse thesaurus.

Changes are :
- Keyword / metadata edit work for ISO191XX, DC (On FGDC, edit keywords is
not working. Any ideas why ?)
- Keyword / metadata edit / ISO191XX : Search only according selected
thesaurus Type (discipline, stratum, theme, ...)
- Keyword / Added services for narrower, broader and related keyword search

It looks interesting but also quite complex to me, especially because you have to expand each item manually. It maybe useful to automatically expand the first level and on click on the next item do the same for that item instead of clicking on three icons? Also, how are recurring loops deal with?

All in all, pretty impressive! Hope others have ideas and suggestions too!

Ciao,
Jeroen

- Administration / Browse thesaurus

The demo is set up with the Agrovoc thesaurus.
http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin/admin

Any comments, ideas ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
François Prunayre
Envoyé : mercredi 17 janvier 2007 15:00
À : 'Jeroen Ticheler'; 'Lagarde Pierre'
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support /online
demo

Hi, that's fine for me Jeroen, problem of storing Ids instead of keyword
could cause problem later when people export (or harwest) without having the
same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword" based on
Lucene Index (and not thesaurus). That way, user will select only keywords
which are in metadata. Here you could have a mix of multilingual keywords
according to what the editors put in.
- Lucene index configuration : Lucene will not create tokens based on
keyword but will index keyword as term (ie. "polar ecosystem" will be index
as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on the
thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2. You
will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / password
admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@…1…] Envoyé : lundi 8
janvier 2007 11:21 À : Lagarde Pierre; François Prunayre Cc :
geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a kind of
middle way of handling keywords. I feel that using the auto- completion
facility is the way to go, but it would need to give a more flexible way of
selecting the right keywords. This should include the hierarchy in a
thesaurus and also be multilingual in the first place. On that part I think
the only way to go is to store a keyword identifier and not the translated
keyword in the text element. The system should than use these identifiers to
display the local versions of the keyword (or provide the default language
of the thesaurus if no translation is available).

In the editor, the full thesaurus content should e available, while, as
François indicated, in the Search interface, only keywords used in the
catalog should be presented. In fact, that auto-completion as implemented by
François would than be a very good first step while a pop-up could provide a
full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC records. I
know the alpha 2 is still not finished what the editor concerns, so I assume
that is the cause. Roberto is working on it and a functional editor should
be ready by the second week of February in a first beta release.

I suggest that we do not add the thesaurus functionality to the code base
until the prototype is more functional if that's OK with you François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN
(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate keywords
(we don't use this solution in Geosource. See http://
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be
better to limit the thesaurus query in the thematic of the keywords in
function of the 19115 list. For example, place thesauri, theme
thesauri,... And, when the user has chosen a specific word, GN could
add the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or
new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part de
François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :
geonetwork-devel@lists.sourceforge.net; geonetwork-
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus
support / online demo

Hi list, here is a first demo adding support for thesaurus in
Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such as
Agrovoc, Gemet or other in rdf/skos format and creation of "local"
thesaurus which will be entirely managed by the administrator of the
geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for
each
term) used for thesaurus of type discipline, theme, temporal or of
type place where you could also defined a bounding box for each term.
Thesaurus creation only support flat thesaurus (ie. you can not
defined narrower, broader and related term).
When editing metadata, geonetwork will provide an autocompletion field
for keyword searching in all thesaurus available in the current node.
When searching for metadata, in the search field keyword, an
autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin /
password admin. Go to the administration > Manage thesauri. The demo
is set up with 3 external thesauri (agrovoc, a thesaurus for the water
domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to be
done for ISO19139)
- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the
current webpage language. But this not really the best option. For the
first implementation, maybe I proposed 2 options for the editing part
:
- if a language parameter is defined in the current metadata, query
the thesaurus in that language
- if not use the webpage language or we could also defined a parameter
"metatada default language" ? This will allow user not having
geonetwork translation (for now en, fr, es, cn) to use their own
language for thesaurus.

For the search this is a more complex part. For now, if the user
interface is in spanish, it will look for term in spanish in each
thesaurus. If the metadata are in english ... it will not be relevant.
Here as a first implementation, we could at least use a parameter
"metatada default language". Other and more complex options could be,
for the keyword criteria
:
- search for a term in user interface language and then query using
the keyword and its translation. Here users need to have multilingual
thesaurus.
- proposed the list of keyword found by Lucene in metadata in the
indexing process. That way, geonetwork propose only keyword that are
used somewhere in one or more metadata
- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/codelist/
thesauri directory of Geonetwork. They are loaded on startup and RDF
manipulation is made with Sesame, an opensource java library for RDF
(http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard for
their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could
put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and earn
cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at http://sourceforge.net/
projects/geonetwork
**********************************************************************
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à
l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de
réception de cet e-mail par erreur, le signaler à son expéditeur et
ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient
néanmoins de vérifier l'absence de corruption à sa réception. The
contents of this email and any attachments are confidential. They are
intended for the named recipient(s) only. If you have received this
email in error please notify the system manager or the sender
immediately and do not disclose the contents to anyone or make copies.
eSafe scanned this email for viruses, vandals and malicious content.
**********************************************************************
************************

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and earn
cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at http://sourceforge.net/
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et
rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at
GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels, confidentiels et prives. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal, confidential and secret. Any total or partial publication, use or distribution must be authorized.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

[Francois_Prunayre]

Hi Jeroen,

I have to update to the latest svn, maybe it will fixe some problems. For
the list in ISO19139, I have an exception "sheet :
D:\APP\GN20070131\web/xsl/metadata-edit.xsl
file:///D:/APP/GN20070131/web/xsl/metadata-iso19139.xsl; Ligne #145; Colonne
#14
1; Impossible de charger le document demandÚ :
\Users\rgiaccio\Documents\Program
s\GeoNetwork\svn\geonetwork\trunk\web\xml\schemas\iso19139\schema\resources\
Code
list\gmxCodelists.xml (Le chemin d'accÞs spÚcifiÚ est introuvable)"

- It would be better to filter the keyword list to only show items once.
<<< FIXED.

- It's not very clear which Thesaurus you are using. Do I understand
correctly that you define one thesaurus per thesaurus type now?
<<< Yes you have to put your thesaurus in a type. But the type info is used
only for ISOxx standards, if you select a type when editing. When editing
DC, you'll search in all thesaurus because there's no type of thesaurus in
DC.

- Is there a minimum number of characters a user has to type in before the
query to the application for a list starts?
<<< Yes this is a property of the Ajax.Autocompleter.

Ciao. Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com]
Envoyé : mardi 13 février 2007 11:13
À : François Prunayre
Cc : geonetwork-devel@lists.sourceforge.net; Roberto Giaccio
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support /online
demo

Hi Francois,
Looks very nice!

We have a range of problems we run into, some related to the editor I assume
(on my Firefox the codelists appear all empty in the editor, Roberto?). On
Patrizia's Internet Explorer the list did not expand with some of the ISO
records.

- It would be better to filter the keyword list to only show items once.
- It's not very clear which Thesaurus you are using. Do I understand
correctly that you define one thesaurus per thesaurus type now?
- When adding a keyword, the associated thesaurus name element should also
be filled to point to the thesaurus. Anyone an idea what should be put here
best? A URI to the rdf of the resource or so?

On Feb 13, 2007, at 8:50 AM, François Prunayre wrote:

Hi all, some news from the thesaurus prototype.
For now, thesaurus support allows to control vocabulary on the
metadata editing side (using autocompletion). Then Lucene will make
the index based on metadata keywords (and not on the thesaurus you
have on the node).

Cool!! Is there a minimum number of characters a user has to type in before
the query to the application for a list starts?

The administration interface allows import/export/creation/browse
thesaurus.

Changes are :
- Keyword / metadata edit work for ISO191XX, DC (On FGDC, edit
keywords is not working. Any ideas why ?)
- Keyword / metadata edit / ISO191XX : Search only according selected
thesaurus Type (discipline, stratum, theme, ...)
- Keyword / Added services for narrower, broader and related keyword
search

It looks interesting but also quite complex to me, especially because you
have to expand each item manually. It maybe useful to automatically expand
the first level and on click on the next item do the same for that item
instead of clicking on three icons? Also, how are recurring loops deal with?

All in all, pretty impressive! Hope others have ideas and suggestions too!

Ciao,
Jeroen

- Administration / Browse thesaurus

The demo is set up with the Agrovoc thesaurus.
http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin/admin

Any comments, ideas ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
François Prunayre Envoyé : mercredi 17 janvier 2007 15:00 À : 'Jeroen
Ticheler'; 'Lagarde Pierre'
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support
/online demo

Hi, that's fine for me Jeroen, problem of storing Ids instead of
keyword could cause problem later when people export (or harwest)
without having the same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword"
based on
Lucene Index (and not thesaurus). That way, user will select only
keywords which are in metadata. Here you could have a mix of
multilingual keywords according to what the editors put in.
- Lucene index configuration : Lucene will not create tokens based on
keyword but will index keyword as term (ie. "polar ecosystem" will be
index as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on
the thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2.
You will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin /
password admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé : lundi 8
janvier 2007 11:21 À : Lagarde Pierre; François Prunayre Cc :
geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a
kind of middle way of handling keywords. I feel that using the auto-
completion facility is the way to go, but it would need to give a more
flexible way of selecting the right keywords. This should include the
hierarchy in a thesaurus and also be multilingual in the first place.
On that part I think the only way to go is to store a keyword
identifier and not the translated keyword in the text element. The
system should than use these identifiers to display the local versions
of the keyword (or provide the default language of the thesaurus if no
translation is available).

In the editor, the full thesaurus content should e available, while,
as François indicated, in the Search interface, only keywords used in
the catalog should be presented. In fact, that auto-completion as
implemented by François would than be a very good first step while a
pop-up could provide a full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC records.
I know the alpha 2 is still not finished what the editor concerns, so
I assume that is the cause. Roberto is working on it and a functional
editor should be ready by the second week of February in a first beta
release.

I suggest that we do not add the thesaurus functionality to the code
base until the prototype is more functional if that's OK with you
François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN
(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate
keywords (we don't use this solution in Geosource. See http://
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be
better to limit the thesaurus query in the thematic of the keywords
in function of the 19115 list. For example, place thesauri, theme
thesauri,... And, when the user has chosen a specific word, GN could
add the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or
new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part de
François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :
geonetwork-devel@lists.sourceforge.net; geonetwork-
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus
support / online demo

Hi list, here is a first demo adding support for thesaurus in
Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such
as Agrovoc, Gemet or other in rdf/skos format and creation of "local"
thesaurus which will be entirely managed by the administrator of the
geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for
each
term) used for thesaurus of type discipline, theme, temporal or of
type place where you could also defined a bounding box for each term.
Thesaurus creation only support flat thesaurus (ie. you can not
defined narrower, broader and related term).
When editing metadata, geonetwork will provide an autocompletion
field for keyword searching in all thesaurus available in the current
node.
When searching for metadata, in the search field keyword, an
autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin /
password admin. Go to the administration > Manage thesauri. The demo
is set up with 3 external thesauri (agrovoc, a thesaurus for the
water domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to
be done for ISO19139)
- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the
current webpage language. But this not really the best option. For
the first implementation, maybe I proposed 2 options for the editing
part
:
- if a language parameter is defined in the current metadata, query
the thesaurus in that language
- if not use the webpage language or we could also defined a
parameter "metatada default language" ? This will allow user not
having geonetwork translation (for now en, fr, es, cn) to use their
own language for thesaurus.

For the search this is a more complex part. For now, if the user
interface is in spanish, it will look for term in spanish in each
thesaurus. If the metadata are in english ... it will not be
relevant.
Here as a first implementation, we could at least use a parameter
"metatada default language". Other and more complex options could be,
for the keyword criteria
:
- search for a term in user interface language and then query using
the keyword and its translation. Here users need to have multilingual
thesaurus.
- proposed the list of keyword found by Lucene in metadata in the
indexing process. That way, geonetwork propose only keyword that are
used somewhere in one or more metadata
- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/codelist/
thesauri directory of Geonetwork. They are loaded on startup and RDF
manipulation is made with Sesame, an opensource java library for RDF
(http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard for
their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could
put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation
ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and
earn cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
*********************************************************************
*
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à
l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de
réception de cet e-mail par erreur, le signaler à son expéditeur et
ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient
néanmoins de vérifier l'absence de corruption à sa réception. The
contents of this email and any attachments are confidential. They are
intended for the named recipient(s) only. If you have received this
email in error please notify the system manager or the sender
immediately and do not disclose the contents to anyone or make
copies.
eSafe scanned this email for viruses, vandals and malicious content.
*********************************************************************
*
************************

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and
earn cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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

-- Ce message a ete verifie par MailScanner pour des virus ou des
polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont
personnels,
confidentiels et prives. Toute publication, utilisation ou
diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is
personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et
rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels,
confidentiels et prives. Toute publication, utilisation ou
diffusion, meme
partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation
ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial
publication, use or distribution must be authorized.

----------------------------------------------------------------------
---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your
job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?
cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels, confidentiels et prives. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal, confidential and secret. Any total or partial publication, use or distribution must be authorized.

[Roberto_Giaccio]

My fault, I commited some test xsl code to the svn repository.
Going to fix this.

        Roberto

On Feb 13, 2007, at 1:15 PM, François Prunayre wrote:

Hi Jeroen,

I have to update to the latest svn, maybe it will fixe some problems. For
the list in ISO19139, I have an exception "sheet :
D:\APP\GN20070131\web/xsl/metadata-edit.xsl
file:///D:/APP/GN20070131/web/xsl/metadata-iso19139.xsl; Ligne #145; Colonne
#14
1; Impossible de charger le document demandÚ :
\Users\rgiaccio\Documents\Program
s\GeoNetwork\svn\geonetwork\trunk\web\xml\schemas\iso19139\schema\resources\
Code
list\gmxCodelists.xml (Le chemin d'accÞs spÚcifiÚ est introuvable)"

- It would be better to filter the keyword list to only show items once.
<<< FIXED.

- It's not very clear which Thesaurus you are using. Do I understand
correctly that you define one thesaurus per thesaurus type now?
<<< Yes you have to put your thesaurus in a type. But the type info is used
only for ISOxx standards, if you select a type when editing. When editing
DC, you'll search in all thesaurus because there's no type of thesaurus in
DC.

- Is there a minimum number of characters a user has to type in before the
query to the application for a list starts?
<<< Yes this is a property of the Ajax.Autocompleter.

Ciao. Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com]
Envoyé : mardi 13 février 2007 11:13
À : François Prunayre
Cc : geonetwork-devel@lists.sourceforge.net; Roberto Giaccio
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support /online
demo

Hi Francois,
Looks very nice!

We have a range of problems we run into, some related to the editor I assume
(on my Firefox the codelists appear all empty in the editor, Roberto?). On
Patrizia's Internet Explorer the list did not expand with some of the ISO
records.

- It would be better to filter the keyword list to only show items once.
- It's not very clear which Thesaurus you are using. Do I understand
correctly that you define one thesaurus per thesaurus type now?
- When adding a keyword, the associated thesaurus name element should also
be filled to point to the thesaurus. Anyone an idea what should be put here
best? A URI to the rdf of the resource or so?

On Feb 13, 2007, at 8:50 AM, François Prunayre wrote:

Hi all, some news from the thesaurus prototype.
For now, thesaurus support allows to control vocabulary on the
metadata editing side (using autocompletion). Then Lucene will make
the index based on metadata keywords (and not on the thesaurus you
have on the node).

Cool!! Is there a minimum number of characters a user has to type in before
the query to the application for a list starts?

The administration interface allows import/export/creation/browse
thesaurus.

Changes are :
- Keyword / metadata edit work for ISO191XX, DC (On FGDC, edit
keywords is not working. Any ideas why ?)
- Keyword / metadata edit / ISO191XX : Search only according selected
thesaurus Type (discipline, stratum, theme, ...)
- Keyword / Added services for narrower, broader and related keyword
search

It looks interesting but also quite complex to me, especially because you
have to expand each item manually. It maybe useful to automatically expand
the first level and on click on the next item do the same for that item
instead of clicking on three icons? Also, how are recurring loops deal with?

All in all, pretty impressive! Hope others have ideas and suggestions too!

Ciao,
Jeroen

- Administration / Browse thesaurus

The demo is set up with the Agrovoc thesaurus.
http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin/admin

Any comments, ideas ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
François Prunayre Envoyé : mercredi 17 janvier 2007 15:00 À : 'Jeroen
Ticheler'; 'Lagarde Pierre'
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support
/online demo

Hi, that's fine for me Jeroen, problem of storing Ids instead of
keyword could cause problem later when people export (or harwest)
without having the same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword"
based on
Lucene Index (and not thesaurus). That way, user will select only
keywords which are in metadata. Here you could have a mix of
multilingual keywords according to what the editors put in.
- Lucene index configuration : Lucene will not create tokens based on
keyword but will index keyword as term (ie. "polar ecosystem" will be
index as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on
the thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2.
You will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin /
password admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé : lundi 8
janvier 2007 11:21 À : Lagarde Pierre; François Prunayre Cc :
geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a
kind of middle way of handling keywords. I feel that using the auto-
completion facility is the way to go, but it would need to give a more
flexible way of selecting the right keywords. This should include the
hierarchy in a thesaurus and also be multilingual in the first place.
On that part I think the only way to go is to store a keyword
identifier and not the translated keyword in the text element. The
system should than use these identifiers to display the local versions
of the keyword (or provide the default language of the thesaurus if no
translation is available).

In the editor, the full thesaurus content should e available, while,
as François indicated, in the Search interface, only keywords used in
the catalog should be presented. In fact, that auto-completion as
implemented by François would than be a very good first step while a
pop-up could provide a full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC records.
I know the alpha 2 is still not finished what the editor concerns, so
I assume that is the cause. Roberto is working on it and a functional
editor should be ready by the second week of February in a first beta
release.

I suggest that we do not add the thesaurus functionality to the code
base until the prototype is more functional if that's OK with you
François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN
(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate
keywords (we don't use this solution in Geosource. See http://
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be
better to limit the thesaurus query in the thematic of the keywords
in function of the 19115 list. For example, place thesauri, theme
thesauri,... And, when the user has chosen a specific word, GN could
add the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or
new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part de
François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :
geonetwork-devel@lists.sourceforge.net; geonetwork-
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus
support / online demo

Hi list, here is a first demo adding support for thesaurus in
Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such
as Agrovoc, Gemet or other in rdf/skos format and creation of "local"
thesaurus which will be entirely managed by the administrator of the
geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for
each
term) used for thesaurus of type discipline, theme, temporal or of
type place where you could also defined a bounding box for each term.
Thesaurus creation only support flat thesaurus (ie. you can not
defined narrower, broader and related term).
When editing metadata, geonetwork will provide an autocompletion
field for keyword searching in all thesaurus available in the current
node.
When searching for metadata, in the search field keyword, an
autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin /
password admin. Go to the administration > Manage thesauri. The demo
is set up with 3 external thesauri (agrovoc, a thesaurus for the
water domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to
be done for ISO19139)
- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the
current webpage language. But this not really the best option. For
the first implementation, maybe I proposed 2 options for the editing
part
:
- if a language parameter is defined in the current metadata, query
the thesaurus in that language
- if not use the webpage language or we could also defined a
parameter "metatada default language" ? This will allow user not
having geonetwork translation (for now en, fr, es, cn) to use their
own language for thesaurus.

For the search this is a more complex part. For now, if the user
interface is in spanish, it will look for term in spanish in each
thesaurus. If the metadata are in english ... it will not be
relevant.
Here as a first implementation, we could at least use a parameter
"metatada default language". Other and more complex options could be,
for the keyword criteria
:
- search for a term in user interface language and then query using
the keyword and its translation. Here users need to have multilingual
thesaurus.
- proposed the list of keyword found by Lucene in metadata in the
indexing process. That way, geonetwork propose only keyword that are
used somewhere in one or more metadata
- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/codelist/
thesauri directory of Geonetwork. They are loaded on startup and RDF
manipulation is made with Sesame, an opensource java library for RDF
(http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard for
their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could
put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation
ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and
earn cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
*********************************************************************
*
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à
l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de
réception de cet e-mail par erreur, le signaler à son expéditeur et
ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient
néanmoins de vérifier l'absence de corruption à sa réception. The
contents of this email and any attachments are confidential. They are
intended for the named recipient(s) only. If you have received this
email in error please notify the system manager or the sender
immediately and do not disclose the contents to anyone or make
copies.
eSafe scanned this email for viruses, vandals and malicious content.
*********************************************************************
*
************************

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and
earn cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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

-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont
personnels,
confidentiels et prives. Toute publication, utilisation ou
diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is
personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et
rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels,
confidentiels et prives. Toute publication, utilisation ou
diffusion, meme
partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation
ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial
publication, use or distribution must be authorized.

----------------------------------------------------------------------
---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your
job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?
cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels, confidentiels et prives. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal, confidential and secret. Any total or partial publication, use or distribution must be authorized.

[Francois_Prunayre]

Hi Jeroen, the administration interface for thesaurus is easier to use now :
- search for keywords
- go to its description (with narrower, broader and related terms)
- click on another term to browse the thesaurus.
... classic thesaurus search interface.

http://dev.sandre.eaufrance.fr/gnthesaurus/
admin / admin

Ciao. Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com]
Envoyé : mardi 13 février 2007 11:13
À : François Prunayre
Cc : geonetwork-devel@lists.sourceforge.net; Roberto Giaccio
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support /online
demo

Hi Francois,
Looks very nice!

We have a range of problems we run into, some related to the editor I assume
(on my Firefox the codelists appear all empty in the editor, Roberto?). On
Patrizia's Internet Explorer the list did not expand with some of the ISO
records.

- It would be better to filter the keyword list to only show items once.
- It's not very clear which Thesaurus you are using. Do I understand
correctly that you define one thesaurus per thesaurus type now?
- When adding a keyword, the associated thesaurus name element should also
be filled to point to the thesaurus. Anyone an idea what should be put here
best? A URI to the rdf of the resource or so?

On Feb 13, 2007, at 8:50 AM, François Prunayre wrote:

Hi all, some news from the thesaurus prototype.
For now, thesaurus support allows to control vocabulary on the
metadata editing side (using autocompletion). Then Lucene will make
the index based on metadata keywords (and not on the thesaurus you
have on the node).

Cool!! Is there a minimum number of characters a user has to type in before
the query to the application for a list starts?

The administration interface allows import/export/creation/browse
thesaurus.

Changes are :
- Keyword / metadata edit work for ISO191XX, DC (On FGDC, edit
keywords is not working. Any ideas why ?)
- Keyword / metadata edit / ISO191XX : Search only according selected
thesaurus Type (discipline, stratum, theme, ...)
- Keyword / Added services for narrower, broader and related keyword
search

It looks interesting but also quite complex to me, especially because you
have to expand each item manually. It maybe useful to automatically expand
the first level and on click on the next item do the same for that item
instead of clicking on three icons? Also, how are recurring loops deal with?

All in all, pretty impressive! Hope others have ideas and suggestions too!

Ciao,
Jeroen

- Administration / Browse thesaurus

The demo is set up with the Agrovoc thesaurus.
http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin/admin

Any comments, ideas ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
François Prunayre Envoyé : mercredi 17 janvier 2007 15:00 À : 'Jeroen
Ticheler'; 'Lagarde Pierre'
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support
/online demo

Hi, that's fine for me Jeroen, problem of storing Ids instead of
keyword could cause problem later when people export (or harwest)
without having the same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword"
based on
Lucene Index (and not thesaurus). That way, user will select only
keywords which are in metadata. Here you could have a mix of
multilingual keywords according to what the editors put in.
- Lucene index configuration : Lucene will not create tokens based on
keyword but will index keyword as term (ie. "polar ecosystem" will be
index as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on
the thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2.
You will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin /
password admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé : lundi 8
janvier 2007 11:21 À : Lagarde Pierre; François Prunayre Cc :
geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a
kind of middle way of handling keywords. I feel that using the auto-
completion facility is the way to go, but it would need to give a more > flexible way of selecting the right keywords. This should include the
hierarchy in a thesaurus and also be multilingual in the first place.
On that part I think the only way to go is to store a keyword
identifier and not the translated keyword in the text element. The
system should than use these identifiers to display the local versions > of the keyword (or provide the default language of the thesaurus if no > translation is available).

In the editor, the full thesaurus content should e available, while,
as François indicated, in the Search interface, only keywords used in
the catalog should be presented. In fact, that auto-completion as
implemented by François would than be a very good first step while a > pop-up could provide a full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC records.
I know the alpha 2 is still not finished what the editor concerns, so
I assume that is the cause. Roberto is working on it and a functional
editor should be ready by the second week of February in a first beta
release.

I suggest that we do not add the thesaurus functionality to the code
base until the prototype is more functional if that's OK with you
François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN
(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate
keywords (we don't use this solution in Geosource. See http://
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be
better to limit the thesaurus query in the thematic of the keywords
in function of the 19115 list. For example, place thesauri, theme
thesauri,... And, when the user has chosen a specific word, GN could
add the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or
new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part de >> François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :
geonetwork-devel@lists.sourceforge.net; geonetwork-
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus
support / online demo

Hi list, here is a first demo adding support for thesaurus in
Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such
as Agrovoc, Gemet or other in rdf/skos format and creation of "local"
thesaurus which will be entirely managed by the administrator of the
geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for
each
term) used for thesaurus of type discipline, theme, temporal or of
type place where you could also defined a bounding box for each term.
Thesaurus creation only support flat thesaurus (ie. you can not
defined narrower, broader and related term).
When editing metadata, geonetwork will provide an autocompletion
field for keyword searching in all thesaurus available in the current >> node.
When searching for metadata, in the search field keyword, an
autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin /
password admin. Go to the administration > Manage thesauri. The demo
is set up with 3 external thesauri (agrovoc, a thesaurus for the
water domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to
be done for ISO19139)
- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the
current webpage language. But this not really the best option. For
the first implementation, maybe I proposed 2 options for the editing
part
:
- if a language parameter is defined in the current metadata, query
the thesaurus in that language
- if not use the webpage language or we could also defined a
parameter "metatada default language" ? This will allow user not
having geonetwork translation (for now en, fr, es, cn) to use their
own language for thesaurus.

For the search this is a more complex part. For now, if the user
interface is in spanish, it will look for term in spanish in each
thesaurus. If the metadata are in english ... it will not be
relevant.
Here as a first implementation, we could at least use a parameter
"metatada default language". Other and more complex options could be, >> for the keyword criteria
:
- search for a term in user interface language and then query using
the keyword and its translation. Here users need to have multilingual >> thesaurus.
- proposed the list of keyword found by Lucene in metadata in the
indexing process. That way, geonetwork propose only keyword that are
used somewhere in one or more metadata
- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/codelist/
thesauri directory of Geonetwork. They are loaded on startup and RDF
manipulation is made with Sesame, an opensource java library for RDF
(http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard for >> their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could
put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation
ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and
earn cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
*********************************************************************
*
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à >> l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de
réception de cet e-mail par erreur, le signaler à son expéditeur et
ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient
néanmoins de vérifier l'absence de corruption à sa réception. The
contents of this email and any attachments are confidential. They are >> intended for the named recipient(s) only. If you have received this
email in error please notify the system manager or the sender
immediately and do not disclose the contents to anyone or make
copies.
eSafe scanned this email for viruses, vandals and malicious content.
*********************************************************************
*
************************

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and
earn cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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

-- Ce message a ete verifie par MailScanner pour des virus ou des
polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont
personnels,
confidentiels et prives. Toute publication, utilisation ou
diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is
personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et
rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels,
confidentiels et prives. Toute publication, utilisation ou
diffusion, meme
partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

---------------------------------------------------------------------- > ---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation
ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial
publication, use or distribution must be authorized.

---------------------------------------------------------------------- > ---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your
job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?
cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

This message has been scanned by the Trend Micro IGSA and found to be free of known security risks.

This message has been scanned by the Trend Micro IGSA and found to be free of known security risks.

[Francois_Prunayre]

Hi Jeroen, in the advanced search interface I added a popup for keyword
selection and remove duplicate service for keyword search (thanks for the
hint ;). This will allow multiple keywords search : "keyword1" or "keyword2"
or .... that feature was asked by Mathieu also.

The button is named "choose" but maybe an image could be better ... Any
proposal for that ? The advanced search is becoming more and more complex !

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/

Ciao. Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
François Prunayre
Envoyé : mardi 20 février 2007 09:55
À : 'Jeroen Ticheler'
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support
/onlinedemo

Hi Jeroen, the administration interface for thesaurus is easier to use now :
- search for keywords
- go to its description (with narrower, broader and related terms)
- click on another term to browse the thesaurus. ... classic thesaurus
search interface. http://dev.sandre.eaufrance.fr/gnthesaurus/ admin / admin

Ciao. Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé : mardi 13
février 2007 11:13 À : François Prunayre Cc :
geonetwork-devel@lists.sourceforge.net; Roberto Giaccio Objet : Re:
[GeoNetwork-devel] [GeoNetwork-users] Thesaurus support /online demo

Hi Francois,
Looks very nice!

We have a range of problems we run into, some related to the editor I assume
(on my Firefox the codelists appear all empty in the editor, Roberto?). On
Patrizia's Internet Explorer the list did not expand with some of the ISO
records.

- It would be better to filter the keyword list to only show items once.
- It's not very clear which Thesaurus you are using. Do I understand
correctly that you define one thesaurus per thesaurus type now?
- When adding a keyword, the associated thesaurus name element should also
be filled to point to the thesaurus. Anyone an idea what should be put here
best? A URI to the rdf of the resource or so?

On Feb 13, 2007, at 8:50 AM, François Prunayre wrote:

Hi all, some news from the thesaurus prototype.
For now, thesaurus support allows to control vocabulary on the > metadata

editing side (using autocompletion). Then Lucene will make > the index based
on metadata keywords (and not on the thesaurus you > have on the node).

Cool!! Is there a minimum number of characters a user has to type in before
the query to the application for a list starts?

The administration interface allows import/export/creation/browse >

thesaurus.

Changes are :
- Keyword / metadata edit work for ISO191XX, DC (On FGDC, edit >
keywords is not working. Any ideas why ?)
- Keyword / metadata edit / ISO191XX : Search only according selected
> thesaurus Type (discipline, stratum, theme, ...)
- Keyword / Added services for narrower, broader and related keyword >
search

It looks interesting but also quite complex to me, especially because you
have to expand each item manually. It maybe useful to automatically expand
the first level and on click on the next item do the same for that item
instead of clicking on three icons? Also, how are recurring loops deal with?

All in all, pretty impressive! Hope others have ideas and suggestions too!

Ciao,
Jeroen

- Administration / Browse thesaurus

The demo is set up with the Agrovoc thesaurus.
http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin/admin

Any comments, ideas ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de >

François Prunayre Envoyé : mercredi 17 janvier 2007 15:00 À : 'Jeroen >
Ticheler'; 'Lagarde Pierre'

Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support >
/online demo

Hi, that's fine for me Jeroen, problem of storing Ids instead of > keyword

could cause problem later when people export (or harwest) > without having
the same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword" >
based on Lucene Index (and not thesaurus). That way, user will select only
keywords which are in metadata. Here you could have a mix of >

multilingual keywords according to what the editors put in.

- Lucene index configuration : Lucene will not create tokens based on >

keyword but will index keyword as term (ie. "polar ecosystem" will be >
index as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on > the

thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2. > You

will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >
password admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé : lundi 8 >

janvier 2007 11:21 À : Lagarde Pierre; François Prunayre Cc :

geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a >

kind of middle way of handling keywords. I feel that using the auto- >
completion facility is the way to go, but it would need to give a more >
flexible way of selecting the right keywords. This should include the >
hierarchy in a thesaurus and also be multilingual in the first place. > On
that part I think the only way to go is to store a keyword > identifier and
not the translated keyword in the text element. The > system should than use
these identifiers to display the local versions > of the keyword (or provide
the default language of the thesaurus if no > translation is available).

In the editor, the full thesaurus content should e available, while, > as

François indicated, in the Search interface, only keywords used in > the
catalog should be presented. In fact, that auto-completion as > implemented
by François would than be a very good first step while a > pop-up could
provide a full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC records. > I

know the alpha 2 is still not finished what the editor concerns, so > I
assume that is the cause. Roberto is working on it and a functional > editor
should be ready by the second week of February in a first beta > release.

I suggest that we do not add the thesaurus functionality to the code >

base until the prototype is more functional if that's OK with you >
François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN >>

(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate >> keywords

(we don't use this solution in Geosource. See http:// >>
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be >>

better to limit the thesaurus query in the thematic of the keywords >> in
function of the 19115 list. For example, place thesauri, theme >>
thesauri,... And, when the user has chosen a specific word, GN could >> add
the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or >>

new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part de >>

François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :

geonetwork-devel@lists.sourceforge.net; geonetwork- >>
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus >>
support / online demo

Hi list, here is a first demo adding support for thesaurus in >>

Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such >> as

Agrovoc, Gemet or other in rdf/skos format and creation of "local"

thesaurus which will be entirely managed by the administrator of the >>

geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for >>
each
term) used for thesaurus of type discipline, theme, temporal or of >>

type place where you could also defined a bounding box for each term.

Thesaurus creation only support flat thesaurus (ie. you can not >>

defined narrower, broader and related term).

When editing metadata, geonetwork will provide an autocompletion >> field

for keyword searching in all thesaurus available in the current >> node.

When searching for metadata, in the search field keyword, an >>

autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >>

password admin. Go to the administration > Manage thesauri. The demo >> is
set up with 3 external thesauri (agrovoc, a thesaurus for the >> water
domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to
>> be done for ISO19139)
- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the >>
current webpage language. But this not really the best option. For >>
the first implementation, maybe I proposed 2 options for the editing
>> part
:
- if a language parameter is defined in the current metadata, query
>> the thesaurus in that language
- if not use the webpage language or we could also defined a >> parameter

"metatada default language" ? This will allow user not >> having geonetwork
translation (for now en, fr, es, cn) to use their >> own language for
thesaurus.

For the search this is a more complex part. For now, if the user >>

interface is in spanish, it will look for term in spanish in each >>
thesaurus. If the metadata are in english ... it will not be >> relevant.

Here as a first implementation, we could at least use a parameter >>
"metatada default language". Other and more complex options could be,
>> for the keyword criteria
:
- search for a term in user interface language and then query using >>

the keyword and its translation. Here users need to have multilingual >>
thesaurus.

- proposed the list of keyword found by Lucene in metadata in the >>
indexing process. That way, geonetwork propose only keyword that are
>> used somewhere in one or more metadata
- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/codelist/ >>

thesauri directory of Geonetwork. They are loaded on startup and RDF >>
manipulation is made with Sesame, an opensource java library for RDF >>
(http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard for >>

their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could >>

put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des >>

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >>

personnels, confidentiels et prives. Toute publication, utilisation >> ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >>

personal, confidential and secret. Any total or partial publication, >> use
or distribution must be authorized.

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share >> your
opinions on IT & business topics through brief surveys - and >> earn cash
http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
*********************************************************************
*
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à >>
l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de >>

réception de cet e-mail par erreur, le signaler à son expéditeur et >> ne
pas en divulguer le contenu.

L'absence de virus a été vérifié à l'émission du message. Il convient >>

néanmoins de vérifier l'absence de corruption à sa réception. The >>
contents of this email and any attachments are confidential. They are >>
intended for the named recipient(s) only. If you have received this >> email
in error please notify the system manager or the sender >> immediately and
do not disclose the contents to anyone or make >> copies.

eSafe scanned this email for viruses, vandals and malicious content.
*********************************************************************
*
************************

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share >> your
opinions on IT & business topics through brief surveys - and >> earn cash
http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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

-- Ce message a ete verifie par MailScanner pour des virus ou des >
polluriels et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation ou
> diffusion, meme partielle, doit etre autorisee.
Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des >
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation ou
> diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

----------------------------------------------------------------------
> --- Take Surveys. Earn Cash. Influence the Future of IT Join >
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and earn
cash http://www.techsay.com/default.php? >
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

-- > Ce message a ete verifie par MailScanner pour des virus ou des >

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont > personnels,

confidentiels et prives. Toute publication, utilisation > ou diffusion,
meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is > personal,

confidential and secret. Any total or partial > publication, use or
distribution must be authorized.

----------------------------------------------------------------------
> --- Using Tomcat but need to do more? Need to support web services, >

security?

Get stuff done quickly with pre-integrated technology to make your > job

easier.

Download IBM WebSphere Application Server v.1.0.1 based on Apache >
Geronimo http://sel.as-us.falkag.net/sel? >
cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/ >
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

This message has been scanned by the Trend Micro IGSA and found to be free
of known security risks.

This message has been scanned by the Trend Micro IGSA and found to be free
of known security risks.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

This message has been scanned by the Trend Micro IGSA and found to be free
of known security risks.

[ticheler]

Hi Francois,
Tested it on the Mac with Firefox, but the popup form showed very small and I couldn't do anything with it Wasn't able to use it. On what system did you check it?
Is it so that the keyword search directly in the keyword field does not work anymore?
Ciao,
Jeroen

On Mar 19, 2007, at 9:34 AM, François Prunayre wrote:

Hi Jeroen, in the advanced search interface I added a popup for keyword
selection and remove duplicate service for keyword search (thanks for the
hint ;). This will allow multiple keywords search : "keyword1" or "keyword2"
or .... that feature was asked by Mathieu also.

The button is named "choose" but maybe an image could be better ... Any
proposal for that ? The advanced search is becoming more and more complex !

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/

Ciao. Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
François Prunayre
Envoyé : mardi 20 février 2007 09:55
À : 'Jeroen Ticheler'
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support
/onlinedemo

Hi Jeroen, the administration interface for thesaurus is easier to use now :
- search for keywords
- go to its description (with narrower, broader and related terms)
- click on another term to browse the thesaurus. ... classic thesaurus
search interface. http://dev.sandre.eaufrance.fr/gnthesaurus/ admin / admin

Ciao. Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@…1…] Envoyé : mardi 13
février 2007 11:13 À : François Prunayre Cc :
geonetwork-devel@lists.sourceforge.net; Roberto Giaccio Objet : Re:
[GeoNetwork-devel] [GeoNetwork-users] Thesaurus support /online demo

Hi Francois,
Looks very nice!

We have a range of problems we run into, some related to the editor I assume
(on my Firefox the codelists appear all empty in the editor, Roberto?). On
Patrizia's Internet Explorer the list did not expand with some of the ISO
records.

- It would be better to filter the keyword list to only show items once.
- It's not very clear which Thesaurus you are using. Do I understand
correctly that you define one thesaurus per thesaurus type now?
- When adding a keyword, the associated thesaurus name element should also
be filled to point to the thesaurus. Anyone an idea what should be put here
best? A URI to the rdf of the resource or so?

On Feb 13, 2007, at 8:50 AM, François Prunayre wrote:

Hi all, some news from the thesaurus prototype.
For now, thesaurus support allows to control vocabulary on the > metadata

editing side (using autocompletion). Then Lucene will make > the index based
on metadata keywords (and not on the thesaurus you > have on the node).

Cool!! Is there a minimum number of characters a user has to type in before
the query to the application for a list starts?

The administration interface allows import/export/creation/browse >

thesaurus.

Changes are :
- Keyword / metadata edit work for ISO191XX, DC (On FGDC, edit >
keywords is not working. Any ideas why ?)
- Keyword / metadata edit / ISO191XX : Search only according selected

thesaurus Type (discipline, stratum, theme, ...)

- Keyword / Added services for narrower, broader and related keyword >
search

It looks interesting but also quite complex to me, especially because you
have to expand each item manually. It maybe useful to automatically expand
the first level and on click on the next item do the same for that item
instead of clicking on three icons? Also, how are recurring loops deal with?

All in all, pretty impressive! Hope others have ideas and suggestions too!

Ciao,
Jeroen

- Administration / Browse thesaurus

The demo is set up with the Agrovoc thesaurus.
http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin/admin

Any comments, ideas ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de >

François Prunayre Envoyé : mercredi 17 janvier 2007 15:00 À : 'Jeroen >
Ticheler'; 'Lagarde Pierre'

Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support >
/online demo

Hi, that's fine for me Jeroen, problem of storing Ids instead of > keyword

could cause problem later when people export (or harwest) > without having
the same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword" >
based on Lucene Index (and not thesaurus). That way, user will select only
keywords which are in metadata. Here you could have a mix of >

multilingual keywords according to what the editors put in.

- Lucene index configuration : Lucene will not create tokens based on >

keyword but will index keyword as term (ie. "polar ecosystem" will be >
index as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on > the

thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2. > You

will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >
password admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@…1…] Envoyé : lundi 8 >

janvier 2007 11:21 À : Lagarde Pierre; François Prunayre Cc :

geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a >

kind of middle way of handling keywords. I feel that using the auto- >
completion facility is the way to go, but it would need to give a more >
flexible way of selecting the right keywords. This should include the >
hierarchy in a thesaurus and also be multilingual in the first place. > On
that part I think the only way to go is to store a keyword > identifier and
not the translated keyword in the text element. The > system should than use
these identifiers to display the local versions > of the keyword (or provide
the default language of the thesaurus if no > translation is available).

In the editor, the full thesaurus content should e available, while, > as

François indicated, in the Search interface, only keywords used in > the
catalog should be presented. In fact, that auto-completion as > implemented
by François would than be a very good first step while a > pop-up could
provide a full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC records. > I

know the alpha 2 is still not finished what the editor concerns, so > I
assume that is the cause. Roberto is working on it and a functional > editor
should be ready by the second week of February in a first beta > release.

I suggest that we do not add the thesaurus functionality to the code >

base until the prototype is more functional if that's OK with you >
François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN >>

(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate >> keywords

(we don't use this solution in Geosource. See http:// >>
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be >>

better to limit the thesaurus query in the thematic of the keywords >> in
function of the 19115 list. For example, place thesauri, theme >>
thesauri,... And, when the user has chosen a specific word, GN could >> add
the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or >>

new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part de >>

François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :

geonetwork-devel@lists.sourceforge.net; geonetwork- >>
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus >>
support / online demo

Hi list, here is a first demo adding support for thesaurus in >>

Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such >> as

Agrovoc, Gemet or other in rdf/skos format and creation of "local"

thesaurus which will be entirely managed by the administrator of the >>

geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for >>
each
term) used for thesaurus of type discipline, theme, temporal or of >>

type place where you could also defined a bounding box for each term.

Thesaurus creation only support flat thesaurus (ie. you can not >>

defined narrower, broader and related term).

When editing metadata, geonetwork will provide an autocompletion >> field

for keyword searching in all thesaurus available in the current >> node.

When searching for metadata, in the search field keyword, an >>

autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >>

password admin. Go to the administration > Manage thesauri. The demo >> is
set up with 3 external thesauri (agrovoc, a thesaurus for the >> water
domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to

be done for ISO19139)

- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the >>
current webpage language. But this not really the best option. For >>
the first implementation, maybe I proposed 2 options for the editing

part

:
- if a language parameter is defined in the current metadata, query

the thesaurus in that language

- if not use the webpage language or we could also defined a >> parameter

"metatada default language" ? This will allow user not >> having geonetwork
translation (for now en, fr, es, cn) to use their >> own language for
thesaurus.

For the search this is a more complex part. For now, if the user >>

interface is in spanish, it will look for term in spanish in each >>
thesaurus. If the metadata are in english ... it will not be >> relevant.

Here as a first implementation, we could at least use a parameter >>
"metatada default language". Other and more complex options could be,

for the keyword criteria

:
- search for a term in user interface language and then query using >>

the keyword and its translation. Here users need to have multilingual >>
thesaurus.

- proposed the list of keyword found by Lucene in metadata in the >>
indexing process. That way, geonetwork propose only keyword that are

used somewhere in one or more metadata

- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/codelist/ >>

thesauri directory of Geonetwork. They are loaded on startup and RDF >>
manipulation is made with Sesame, an opensource java library for RDF >>
(http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard for >>

their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could >>

put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des >>

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >>

personnels, confidentiels et prives. Toute publication, utilisation >> ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >>

personal, confidential and secret. Any total or partial publication, >> use
or distribution must be authorized.

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share >> your
opinions on IT & business topics through brief surveys - and >> earn cash
http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at http://sourceforge.net/ >>
projects/geonetwork
*********************************************************************
*
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à >>
l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de >>

réception de cet e-mail par erreur, le signaler à son expéditeur et >> ne
pas en divulguer le contenu.

L'absence de virus a été vérifié à l'émission du message. Il convient >>

néanmoins de vérifier l'absence de corruption à sa réception. The >>
contents of this email and any attachments are confidential. They are >>
intended for the named recipient(s) only. If you have received this >> email
in error please notify the system manager or the sender >> immediately and
do not disclose the contents to anyone or make >> copies.

eSafe scanned this email for viruses, vandals and malicious content.
*********************************************************************
*
************************

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share >> your
opinions on IT & business topics through brief surveys - and >> earn cash
http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at http://sourceforge.net/ >>
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des >polluriels et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation ou

diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des >
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation ou

diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

----------------------------------------------------------------------

--- Take Surveys. Earn Cash. Influence the Future of IT Join >

SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and earn
cash http://www.techsay.com/default.php? >
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at
GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

-- > Ce message a ete verifie par MailScanner pour des virus ou des >

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont > personnels,

confidentiels et prives. Toute publication, utilisation > ou diffusion,
meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is > personal,

confidential and secret. Any total or partial > publication, use or
distribution must be authorized.

----------------------------------------------------------------------

--- Using Tomcat but need to do more? Need to support web services, >

security?

Get stuff done quickly with pre-integrated technology to make your > job

easier.

Download IBM WebSphere Application Server v.1.0.1 based on Apache >
Geronimo http://sel.as-us.falkag.net/sel? >
cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at http://sourceforge.net/ >
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

This message has been scanned by the Trend Micro IGSA and found to be free
of known security risks.

This message has been scanned by the Trend Micro IGSA and found to be free
of known security risks.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at
GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

This message has been scanned by the Trend Micro IGSA and found to be free
of known security risks.

[ticheler]

Oh, and than it suddenly was there... Looks cool! How / is the list limited when a lot of keywords are used?
Ciao,
Jeroen

On Mar 19, 2007, at 9:34 AM, François Prunayre wrote:

Hi Jeroen, in the advanced search interface I added a popup for keyword
selection and remove duplicate service for keyword search (thanks for the
hint ;). This will allow multiple keywords search : "keyword1" or "keyword2"
or .... that feature was asked by Mathieu also.

The button is named "choose" but maybe an image could be better ... Any
proposal for that ? The advanced search is becoming more and more complex !

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/

Ciao. Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
François Prunayre
Envoyé : mardi 20 février 2007 09:55
À : 'Jeroen Ticheler'
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support
/onlinedemo

Hi Jeroen, the administration interface for thesaurus is easier to use now :
- search for keywords
- go to its description (with narrower, broader and related terms)
- click on another term to browse the thesaurus. ... classic thesaurus
search interface. http://dev.sandre.eaufrance.fr/gnthesaurus/ admin / admin

Ciao. Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@…1…] Envoyé : mardi 13
février 2007 11:13 À : François Prunayre Cc :
geonetwork-devel@lists.sourceforge.net; Roberto Giaccio Objet : Re:
[GeoNetwork-devel] [GeoNetwork-users] Thesaurus support /online demo

Hi Francois,
Looks very nice!

We have a range of problems we run into, some related to the editor I assume
(on my Firefox the codelists appear all empty in the editor, Roberto?). On
Patrizia's Internet Explorer the list did not expand with some of the ISO
records.

- It would be better to filter the keyword list to only show items once.
- It's not very clear which Thesaurus you are using. Do I understand
correctly that you define one thesaurus per thesaurus type now?
- When adding a keyword, the associated thesaurus name element should also
be filled to point to the thesaurus. Anyone an idea what should be put here
best? A URI to the rdf of the resource or so?

On Feb 13, 2007, at 8:50 AM, François Prunayre wrote:

Hi all, some news from the thesaurus prototype.
For now, thesaurus support allows to control vocabulary on the > metadata

editing side (using autocompletion). Then Lucene will make > the index based
on metadata keywords (and not on the thesaurus you > have on the node).

Cool!! Is there a minimum number of characters a user has to type in before
the query to the application for a list starts?

The administration interface allows import/export/creation/browse >

thesaurus.

Changes are :
- Keyword / metadata edit work for ISO191XX, DC (On FGDC, edit >
keywords is not working. Any ideas why ?)
- Keyword / metadata edit / ISO191XX : Search only according selected

thesaurus Type (discipline, stratum, theme, ...)

- Keyword / Added services for narrower, broader and related keyword >
search

It looks interesting but also quite complex to me, especially because you
have to expand each item manually. It maybe useful to automatically expand
the first level and on click on the next item do the same for that item
instead of clicking on three icons? Also, how are recurring loops deal with?

All in all, pretty impressive! Hope others have ideas and suggestions too!

Ciao,
Jeroen

- Administration / Browse thesaurus

The demo is set up with the Agrovoc thesaurus.
http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin/admin

Any comments, ideas ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de >

François Prunayre Envoyé : mercredi 17 janvier 2007 15:00 À : 'Jeroen >
Ticheler'; 'Lagarde Pierre'

Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support >
/online demo

Hi, that's fine for me Jeroen, problem of storing Ids instead of > keyword

could cause problem later when people export (or harwest) > without having
the same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword" >
based on Lucene Index (and not thesaurus). That way, user will select only
keywords which are in metadata. Here you could have a mix of >

multilingual keywords according to what the editors put in.

- Lucene index configuration : Lucene will not create tokens based on >

keyword but will index keyword as term (ie. "polar ecosystem" will be >
index as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on > the

thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2. > You

will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >
password admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@…1…] Envoyé : lundi 8 >

janvier 2007 11:21 À : Lagarde Pierre; François Prunayre Cc :

geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a >

kind of middle way of handling keywords. I feel that using the auto- >
completion facility is the way to go, but it would need to give a more >
flexible way of selecting the right keywords. This should include the >
hierarchy in a thesaurus and also be multilingual in the first place. > On
that part I think the only way to go is to store a keyword > identifier and
not the translated keyword in the text element. The > system should than use
these identifiers to display the local versions > of the keyword (or provide
the default language of the thesaurus if no > translation is available).

In the editor, the full thesaurus content should e available, while, > as

François indicated, in the Search interface, only keywords used in > the
catalog should be presented. In fact, that auto-completion as > implemented
by François would than be a very good first step while a > pop-up could
provide a full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC records. > I

know the alpha 2 is still not finished what the editor concerns, so > I
assume that is the cause. Roberto is working on it and a functional > editor
should be ready by the second week of February in a first beta > release.

I suggest that we do not add the thesaurus functionality to the code >

base until the prototype is more functional if that's OK with you >
François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN >>

(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate >> keywords

(we don't use this solution in Geosource. See http:// >>
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be >>

better to limit the thesaurus query in the thematic of the keywords >> in
function of the 19115 list. For example, place thesauri, theme >>
thesauri,... And, when the user has chosen a specific word, GN could >> add
the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or >>

new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part de >>

François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :

geonetwork-devel@lists.sourceforge.net; geonetwork- >>
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus >>
support / online demo

Hi list, here is a first demo adding support for thesaurus in >>

Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such >> as

Agrovoc, Gemet or other in rdf/skos format and creation of "local"

thesaurus which will be entirely managed by the administrator of the >>

geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for >>
each
term) used for thesaurus of type discipline, theme, temporal or of >>

type place where you could also defined a bounding box for each term.

Thesaurus creation only support flat thesaurus (ie. you can not >>

defined narrower, broader and related term).

When editing metadata, geonetwork will provide an autocompletion >> field

for keyword searching in all thesaurus available in the current >> node.

When searching for metadata, in the search field keyword, an >>

autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >>

password admin. Go to the administration > Manage thesauri. The demo >> is
set up with 3 external thesauri (agrovoc, a thesaurus for the >> water
domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to

be done for ISO19139)

- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the >>
current webpage language. But this not really the best option. For >>
the first implementation, maybe I proposed 2 options for the editing

part

:
- if a language parameter is defined in the current metadata, query

the thesaurus in that language

- if not use the webpage language or we could also defined a >> parameter

"metatada default language" ? This will allow user not >> having geonetwork
translation (for now en, fr, es, cn) to use their >> own language for
thesaurus.

For the search this is a more complex part. For now, if the user >>

interface is in spanish, it will look for term in spanish in each >>
thesaurus. If the metadata are in english ... it will not be >> relevant.

Here as a first implementation, we could at least use a parameter >>
"metatada default language". Other and more complex options could be,

for the keyword criteria

:
- search for a term in user interface language and then query using >>

the keyword and its translation. Here users need to have multilingual >>
thesaurus.

- proposed the list of keyword found by Lucene in metadata in the >>
indexing process. That way, geonetwork propose only keyword that are

used somewhere in one or more metadata

- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/codelist/ >>

thesauri directory of Geonetwork. They are loaded on startup and RDF >>
manipulation is made with Sesame, an opensource java library for RDF >>
(http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard for >>

their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could >>

put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des >>

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >>

personnels, confidentiels et prives. Toute publication, utilisation >> ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >>

personal, confidential and secret. Any total or partial publication, >> use
or distribution must be authorized.

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share >> your
opinions on IT & business topics through brief surveys - and >> earn cash
http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at http://sourceforge.net/ >>
projects/geonetwork
*********************************************************************
*
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à >>
l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de >>

réception de cet e-mail par erreur, le signaler à son expéditeur et >> ne
pas en divulguer le contenu.

L'absence de virus a été vérifié à l'émission du message. Il convient >>

néanmoins de vérifier l'absence de corruption à sa réception. The >>
contents of this email and any attachments are confidential. They are >>
intended for the named recipient(s) only. If you have received this >> email
in error please notify the system manager or the sender >> immediately and
do not disclose the contents to anyone or make >> copies.

eSafe scanned this email for viruses, vandals and malicious content.
*********************************************************************
*
************************

---------------------------------------------------------------------
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share >> your
opinions on IT & business topics through brief surveys - and >> earn cash
http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at http://sourceforge.net/ >>
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des >polluriels et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation ou

diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des >
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation ou

diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

----------------------------------------------------------------------

--- Take Surveys. Earn Cash. Influence the Future of IT Join >

SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and earn
cash http://www.techsay.com/default.php? >
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at
GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

-- > Ce message a ete verifie par MailScanner pour des virus ou des >

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont > personnels,

confidentiels et prives. Toute publication, utilisation > ou diffusion,
meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is > personal,

confidential and secret. Any total or partial > publication, use or
distribution must be authorized.

----------------------------------------------------------------------

--- Using Tomcat but need to do more? Need to support web services, >

security?

Get stuff done quickly with pre-integrated technology to make your > job

easier.

Download IBM WebSphere Application Server v.1.0.1 based on Apache >
Geronimo http://sel.as-us.falkag.net/sel? >
cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at http://sourceforge.net/ >
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels
et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.
Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

This message has been scanned by the Trend Micro IGSA and found to be free
of known security risks.

This message has been scanned by the Trend Micro IGSA and found to be free
of known security risks.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at
GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

This message has been scanned by the Trend Micro IGSA and found to be free
of known security risks.

[Francois_Prunayre]

Limit is set to 1000 in the service config (same parameter as portal.search
service). Maybe my server is slown today ...

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com]
Envoyé : lundi 19 mars 2007 14:09
À : François Prunayre
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support
/onlinedemo

Oh, and than it suddenly was there... Looks cool! How / is the list limited
when a lot of keywords are used?
Ciao,
Jeroen

On Mar 19, 2007, at 9:34 AM, François Prunayre wrote:

Hi Jeroen, in the advanced search interface I added a popup for
keyword selection and remove duplicate service for keyword search
(thanks for the hint ;). This will allow multiple keywords search :
"keyword1" or "keyword2"
or .... that feature was asked by Mathieu also.

The button is named "choose" but maybe an image could be better ...
Any
proposal for that ? The advanced search is becoming more and more
complex !

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/

Ciao. Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
François Prunayre Envoyé : mardi 20 février 2007 09:55 À : 'Jeroen
Ticheler'
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support
/onlinedemo

Hi Jeroen, the administration interface for thesaurus is easier to use
now :
- search for keywords
- go to its description (with narrower, broader and related terms)
- click on another term to browse the thesaurus. ... classic thesaurus
search interface. http://dev.sandre.eaufrance.fr/gnthesaurus/
admin / admin

Ciao. Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé :
mardi 13
février 2007 11:13 À : François Prunayre Cc :
geonetwork-devel@lists.sourceforge.net; Roberto Giaccio Objet : Re:
[GeoNetwork-devel] [GeoNetwork-users] Thesaurus support /online demo

Hi Francois,
Looks very nice!

We have a range of problems we run into, some related to the editor I
assume (on my Firefox the codelists appear all empty in the editor,
Roberto?). On Patrizia's Internet Explorer the list did not expand
with some of the ISO records.

- It would be better to filter the keyword list to only show items
once.
- It's not very clear which Thesaurus you are using. Do I understand
correctly that you define one thesaurus per thesaurus type now?
- When adding a keyword, the associated thesaurus name element should
also be filled to point to the thesaurus. Anyone an idea what should
be put here best? A URI to the rdf of the resource or so?

On Feb 13, 2007, at 8:50 AM, François Prunayre wrote:

Hi all, some news from the thesaurus prototype.
For now, thesaurus support allows to control vocabulary on the >
metadata

editing side (using autocompletion). Then Lucene will make > the index
based on metadata keywords (and not on the thesaurus you > have on the
node).

Cool!! Is there a minimum number of characters a user has to type in
before the query to the application for a list starts?

The administration interface allows import/export/creation/browse >

thesaurus.

Changes are :
- Keyword / metadata edit work for ISO191XX, DC (On FGDC, edit >
keywords is not working. Any ideas why ?)
- Keyword / metadata edit / ISO191XX : Search only according selected

thesaurus Type (discipline, stratum, theme, ...)

- Keyword / Added services for narrower, broader and related keyword
> search

It looks interesting but also quite complex to me, especially because
you have to expand each item manually. It maybe useful to
automatically expand the first level and on click on the next item do
the same for that item instead of clicking on three icons? Also, how
are recurring loops deal with?

All in all, pretty impressive! Hope others have ideas and suggestions
too!

Ciao,
Jeroen

- Administration / Browse thesaurus

The demo is set up with the Agrovoc thesaurus.
http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin/admin

Any comments, ideas ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
>

François Prunayre Envoyé : mercredi 17 janvier 2007 15:00 À :
'Jeroen >
Ticheler'; 'Lagarde Pierre'

Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support >
/online demo

Hi, that's fine for me Jeroen, problem of storing Ids instead of >
keyword

could cause problem later when people export (or harwest) > without
having the same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword" >
based on Lucene Index (and not thesaurus). That way, user will select
only keywords which are in metadata. Here you could have a mix of >

multilingual keywords according to what the editors put in.

- Lucene index configuration : Lucene will not create tokens based on
>

keyword but will index keyword as term (ie. "polar ecosystem" will be
> index as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on
> the

thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2.
> You

will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >
password admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé :
lundi 8 >

janvier 2007 11:21 À : Lagarde Pierre; François Prunayre Cc :

geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a
>

kind of middle way of handling keywords. I feel that using the auto- >
completion facility is the way to go, but it would need to give a more
> flexible way of selecting the right keywords. This should include
the > hierarchy in a thesaurus and also be multilingual in the first
place. > On that part I think the only way to go is to store a keyword
> identifier and not the translated keyword in the text element. The >
system should than use these identifiers to display the local versions
> of the keyword (or provide the default language of the thesaurus if
no > translation is available).

In the editor, the full thesaurus content should e available, while,
> as

François indicated, in the Search interface, only keywords used in
> the
catalog should be presented. In fact, that auto-completion as >
implemented by François would than be a very good first step while a >
pop-up could provide a full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC
records. > I

know the alpha 2 is still not finished what the editor concerns, so
> I
assume that is the cause. Roberto is working on it and a functional
> editor
should be ready by the second week of February in a first beta >
release.

I suggest that we do not add the thesaurus functionality to the code
>

base until the prototype is more functional if that's OK with you >
François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN >>

(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate >>
keywords

(we don't use this solution in Geosource. See http:// >>
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be >>

better to limit the thesaurus query in the thematic of the keywords
>> in
function of the 19115 list. For example, place thesauri, theme >>
thesauri,... And, when the user has chosen a specific word, GN could
>> add the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or
>>

new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part
de >>

François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :

geonetwork-devel@lists.sourceforge.net; geonetwork- >>
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus >>
support / online demo

Hi list, here is a first demo adding support for thesaurus in >>

Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such
>> as

Agrovoc, Gemet or other in rdf/skos format and creation of "local"

thesaurus which will be entirely managed by the administrator of the
>>

geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for
>> each
term) used for thesaurus of type discipline, theme, temporal or of
>>

type place where you could also defined a bounding box for each term.

Thesaurus creation only support flat thesaurus (ie. you can not >>

defined narrower, broader and related term).

When editing metadata, geonetwork will provide an autocompletion
>> field

for keyword searching in all thesaurus available in the current >>
node.

When searching for metadata, in the search field keyword, an >>

autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >>

password admin. Go to the administration > Manage thesauri. The demo
>> is set up with 3 external thesauri (agrovoc, a thesaurus for the >>
water domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to

be done for ISO19139)

- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the >>
current webpage language. But this not really the best option.
For >>
the first implementation, maybe I proposed 2 options for the editing

part

:
- if a language parameter is defined in the current metadata, query

the thesaurus in that language

- if not use the webpage language or we could also defined a >>
parameter

"metatada default language" ? This will allow user not >> having
geonetwork translation (for now en, fr, es, cn) to use their >> own
language for thesaurus.

For the search this is a more complex part. For now, if the user >>

interface is in spanish, it will look for term in spanish in each >>
thesaurus. If the metadata are in english ... it will not be >>
relevant.

Here as a first implementation, we could at least use a parameter >>
"metatada default language". Other and more complex options could
be,

for the keyword criteria

:
- search for a term in user interface language and then query using
>>

the keyword and its translation. Here users need to have multilingual
>> thesaurus.

- proposed the list of keyword found by Lucene in metadata in the >>
indexing process. That way, geonetwork propose only keyword that are

used somewhere in one or more metadata

- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/ codelist/
>>

thesauri directory of Geonetwork. They are loaded on startup and RDF
>> manipulation is made with Sesame, an opensource java library for
RDF >> (http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard
for >>

their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could
>>

put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des >>

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >>

personnels, confidentiels et prives. Toute publication, utilisation
>> ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >>

personal, confidential and secret. Any total or partial publication,
>> use or distribution must be authorized.

--------------------------------------------------------------------
-
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share
>> your
opinions on IT & business topics through brief surveys - and >> earn
cash http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
********************************************************************
*
*
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à >>
l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas
de >>

réception de cet e-mail par erreur, le signaler à son expéditeur et
>> ne pas en divulguer le contenu.

L'absence de virus a été vérifié à l'émission du message. Il
convient >>

néanmoins de vérifier l'absence de corruption à sa réception. The >>
contents of this email and any attachments are confidential. They are
>> intended for the named recipient(s) only. If you have received this
>> email
in error please notify the system manager or the sender >> immediately
and do not disclose the contents to anyone or make >> copies.

eSafe scanned this email for viruses, vandals and malicious content.
********************************************************************
*
*
************************

--------------------------------------------------------------------
-
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share
>> your
opinions on IT & business topics through brief surveys - and >> earn
cash http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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

-- Ce message a ete verifie par MailScanner pour des virus ou des >
polluriels et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation
ou

diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des >
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation
ou

diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

---------------------------------------------------------------------
-

--- Take Surveys. Earn Cash. Influence the Future of IT Join >

SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and
earn cash http://www.techsay.com/default.php? >
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

-- > Ce message a ete verifie par MailScanner pour des virus ou des
>

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >
personnels,

confidentiels et prives. Toute publication, utilisation > ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal,

confidential and secret. Any total or partial > publication, use or
distribution must be authorized.

---------------------------------------------------------------------
-

--- Using Tomcat but need to do more? Need to support web services,
>

security?

Get stuff done quickly with pre-integrated technology to make your >
job

easier.

Download IBM WebSphere Application Server v.1.0.1 based on Apache >
Geronimo http://sel.as-us.falkag.net/sel? >
cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/ >
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation ou
diffusion, meme partielle, doit etre autorisee.
Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

This message has been scanned by the Trend Micro IGSA and found to be
free of known security risks.

This message has been scanned by the Trend Micro IGSA and found to be
free of known security risks.

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys-and earn
cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

This message has been scanned by the Trend Micro IGSA and found to be
free of known security risks.

[Francois_Prunayre]

Works fine for me on windows (firefox, ie) and linux (firefox).

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de Jeroen
Ticheler
Envoyé : lundi 19 mars 2007 14:08
À : François Prunayre
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus
support/onlinedemo

Hi Francois,
Tested it on the Mac with Firefox, but the popup form showed very small and
I couldn't do anything with it Wasn't able to use it. On what system did
you check it?
Is it so that the keyword search directly in the keyword field does not work
anymore?
Ciao,
Jeroen

On Mar 19, 2007, at 9:34 AM, François Prunayre wrote:

Hi Jeroen, in the advanced search interface I added a popup for
keyword selection and remove duplicate service for keyword search
(thanks for the hint ;). This will allow multiple keywords search :
"keyword1" or "keyword2"
or .... that feature was asked by Mathieu also.

The button is named "choose" but maybe an image could be better ...
Any
proposal for that ? The advanced search is becoming more and more
complex !

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/

Ciao. Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
François Prunayre Envoyé : mardi 20 février 2007 09:55 À : 'Jeroen
Ticheler'
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support
/onlinedemo

Hi Jeroen, the administration interface for thesaurus is easier to use
now :
- search for keywords
- go to its description (with narrower, broader and related terms)
- click on another term to browse the thesaurus. ... classic thesaurus
search interface. http://dev.sandre.eaufrance.fr/gnthesaurus/
admin / admin

Ciao. Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé :
mardi 13
février 2007 11:13 À : François Prunayre Cc :
geonetwork-devel@lists.sourceforge.net; Roberto Giaccio Objet : Re:
[GeoNetwork-devel] [GeoNetwork-users] Thesaurus support /online demo

Hi Francois,
Looks very nice!

We have a range of problems we run into, some related to the editor I
assume (on my Firefox the codelists appear all empty in the editor,
Roberto?). On Patrizia's Internet Explorer the list did not expand
with some of the ISO records.

- It would be better to filter the keyword list to only show items
once.
- It's not very clear which Thesaurus you are using. Do I understand
correctly that you define one thesaurus per thesaurus type now?
- When adding a keyword, the associated thesaurus name element should
also be filled to point to the thesaurus. Anyone an idea what should
be put here best? A URI to the rdf of the resource or so?

On Feb 13, 2007, at 8:50 AM, François Prunayre wrote:

Hi all, some news from the thesaurus prototype.
For now, thesaurus support allows to control vocabulary on the >
metadata

editing side (using autocompletion). Then Lucene will make > the index
based on metadata keywords (and not on the thesaurus you > have on the
node).

Cool!! Is there a minimum number of characters a user has to type in
before the query to the application for a list starts?

The administration interface allows import/export/creation/browse >

thesaurus.

Changes are :
- Keyword / metadata edit work for ISO191XX, DC (On FGDC, edit >
keywords is not working. Any ideas why ?)
- Keyword / metadata edit / ISO191XX : Search only according selected

thesaurus Type (discipline, stratum, theme, ...)

- Keyword / Added services for narrower, broader and related keyword
> search

It looks interesting but also quite complex to me, especially because
you have to expand each item manually. It maybe useful to
automatically expand the first level and on click on the next item do
the same for that item instead of clicking on three icons? Also, how
are recurring loops deal with?

All in all, pretty impressive! Hope others have ideas and suggestions
too!

Ciao,
Jeroen

- Administration / Browse thesaurus

The demo is set up with the Agrovoc thesaurus.
http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin/admin

Any comments, ideas ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
>

François Prunayre Envoyé : mercredi 17 janvier 2007 15:00 À :
'Jeroen >
Ticheler'; 'Lagarde Pierre'

Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support >
/online demo

Hi, that's fine for me Jeroen, problem of storing Ids instead of >
keyword

could cause problem later when people export (or harwest) > without
having the same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword" >
based on Lucene Index (and not thesaurus). That way, user will select
only keywords which are in metadata. Here you could have a mix of >

multilingual keywords according to what the editors put in.

- Lucene index configuration : Lucene will not create tokens based on
>

keyword but will index keyword as term (ie. "polar ecosystem" will be
> index as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on
> the

thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2.
> You

will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >
password admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé :
lundi 8 >

janvier 2007 11:21 À : Lagarde Pierre; François Prunayre Cc :

geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a
>

kind of middle way of handling keywords. I feel that using the auto- >
completion facility is the way to go, but it would need to give a more
> flexible way of selecting the right keywords. This should include
the > hierarchy in a thesaurus and also be multilingual in the first
place. > On that part I think the only way to go is to store a keyword
> identifier and not the translated keyword in the text element. The >
system should than use these identifiers to display the local versions
> of the keyword (or provide the default language of the thesaurus if
no > translation is available).

In the editor, the full thesaurus content should e available, while,
> as

François indicated, in the Search interface, only keywords used in
> the
catalog should be presented. In fact, that auto-completion as >
implemented by François would than be a very good first step while a >
pop-up could provide a full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC
records. > I

know the alpha 2 is still not finished what the editor concerns, so
> I
assume that is the cause. Roberto is working on it and a functional
> editor
should be ready by the second week of February in a first beta >
release.

I suggest that we do not add the thesaurus functionality to the code
>

base until the prototype is more functional if that's OK with you >
François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN >>

(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate >>
keywords

(we don't use this solution in Geosource. See http:// >>
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be >>

better to limit the thesaurus query in the thematic of the keywords
>> in
function of the 19115 list. For example, place thesauri, theme >>
thesauri,... And, when the user has chosen a specific word, GN could
>> add the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or
>>

new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part
de >>

François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :

geonetwork-devel@lists.sourceforge.net; geonetwork- >>
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus >>
support / online demo

Hi list, here is a first demo adding support for thesaurus in >>

Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such
>> as

Agrovoc, Gemet or other in rdf/skos format and creation of "local"

thesaurus which will be entirely managed by the administrator of the
>>

geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for
>> each
term) used for thesaurus of type discipline, theme, temporal or of
>>

type place where you could also defined a bounding box for each term.

Thesaurus creation only support flat thesaurus (ie. you can not >>

defined narrower, broader and related term).

When editing metadata, geonetwork will provide an autocompletion
>> field

for keyword searching in all thesaurus available in the current >>
node.

When searching for metadata, in the search field keyword, an >>

autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >>

password admin. Go to the administration > Manage thesauri. The demo
>> is set up with 3 external thesauri (agrovoc, a thesaurus for the >>
water domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to

be done for ISO19139)

- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the >>
current webpage language. But this not really the best option.
For >>
the first implementation, maybe I proposed 2 options for the editing

part

:
- if a language parameter is defined in the current metadata, query

the thesaurus in that language

- if not use the webpage language or we could also defined a >>
parameter

"metatada default language" ? This will allow user not >> having
geonetwork translation (for now en, fr, es, cn) to use their >> own
language for thesaurus.

For the search this is a more complex part. For now, if the user >>

interface is in spanish, it will look for term in spanish in each >>
thesaurus. If the metadata are in english ... it will not be >>
relevant.

Here as a first implementation, we could at least use a parameter >>
"metatada default language". Other and more complex options could
be,

for the keyword criteria

:
- search for a term in user interface language and then query using
>>

the keyword and its translation. Here users need to have multilingual
>> thesaurus.

- proposed the list of keyword found by Lucene in metadata in the >>
indexing process. That way, geonetwork propose only keyword that are

used somewhere in one or more metadata

- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/ codelist/
>>

thesauri directory of Geonetwork. They are loaded on startup and RDF
>> manipulation is made with Sesame, an opensource java library for
RDF >> (http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard
for >>

their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could
>>

put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des >>

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >>

personnels, confidentiels et prives. Toute publication, utilisation
>> ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >>

personal, confidential and secret. Any total or partial publication,
>> use or distribution must be authorized.

--------------------------------------------------------------------
-
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share
>> your
opinions on IT & business topics through brief surveys - and >> earn
cash http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
********************************************************************
*
*
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à >>
l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas
de >>

réception de cet e-mail par erreur, le signaler à son expéditeur et
>> ne pas en divulguer le contenu.

L'absence de virus a été vérifié à l'émission du message. Il
convient >>

néanmoins de vérifier l'absence de corruption à sa réception. The >>
contents of this email and any attachments are confidential. They are
>> intended for the named recipient(s) only. If you have received this
>> email
in error please notify the system manager or the sender >> immediately
and do not disclose the contents to anyone or make >> copies.

eSafe scanned this email for viruses, vandals and malicious content.
********************************************************************
*
*
************************

--------------------------------------------------------------------
-
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share
>> your
opinions on IT & business topics through brief surveys - and >> earn
cash http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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

-- Ce message a ete verifie par MailScanner pour des virus ou des >
polluriels et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation
ou

diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des >
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation
ou

diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

---------------------------------------------------------------------
-

--- Take Surveys. Earn Cash. Influence the Future of IT Join >

SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and
earn cash http://www.techsay.com/default.php? >
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

-- > Ce message a ete verifie par MailScanner pour des virus ou des
>

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >
personnels,

confidentiels et prives. Toute publication, utilisation > ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal,

confidential and secret. Any total or partial > publication, use or
distribution must be authorized.

---------------------------------------------------------------------
-

--- Using Tomcat but need to do more? Need to support web services,
>

security?

Get stuff done quickly with pre-integrated technology to make your >
job

easier.

Download IBM WebSphere Application Server v.1.0.1 based on Apache >
Geronimo http://sel.as-us.falkag.net/sel? >
cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/ >
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation ou
diffusion, meme partielle, doit etre autorisee.
Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

This message has been scanned by the Trend Micro IGSA and found to be
free of known security risks.

This message has been scanned by the Trend Micro IGSA and found to be
free of known security risks.

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys-and earn
cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

This message has been scanned by the Trend Micro IGSA and found to be
free of known security risks.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

[Francois_Prunayre]

Autocompleter is also available on the keyword field ... Both are available.

Use the autocompleter to select one keyword or the popup for a multiple
keywords search.

For the time being we have a simple thesaurus for regions - but this is
duplicate with the table regions in the db. Maybe we have to provide a
sample thesaurus for demo ... Ideas ? Agrovoc is quite big ! ...

Cheers. Francois

PS : demo web site was updated with the latest svn.

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de Jeroen
Ticheler
Envoyé : lundi 19 mars 2007 14:08
À : François Prunayre
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus
support/onlinedemo

Hi Francois,
Tested it on the Mac with Firefox, but the popup form showed very small and
I couldn't do anything with it Wasn't able to use it. On what system did
you check it?
Is it so that the keyword search directly in the keyword field does not work
anymore?
Ciao,
Jeroen

On Mar 19, 2007, at 9:34 AM, François Prunayre wrote:

Hi Jeroen, in the advanced search interface I added a popup for
keyword selection and remove duplicate service for keyword search
(thanks for the hint ;). This will allow multiple keywords search :
"keyword1" or "keyword2"
or .... that feature was asked by Mathieu also.

The button is named "choose" but maybe an image could be better ...
Any
proposal for that ? The advanced search is becoming more and more
complex !

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/

Ciao. Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
François Prunayre Envoyé : mardi 20 février 2007 09:55 À : 'Jeroen
Ticheler'
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support
/onlinedemo

Hi Jeroen, the administration interface for thesaurus is easier to use
now :
- search for keywords
- go to its description (with narrower, broader and related terms)
- click on another term to browse the thesaurus. ... classic thesaurus
search interface. http://dev.sandre.eaufrance.fr/gnthesaurus/
admin / admin

Ciao. Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé :
mardi 13
février 2007 11:13 À : François Prunayre Cc :
geonetwork-devel@lists.sourceforge.net; Roberto Giaccio Objet : Re:
[GeoNetwork-devel] [GeoNetwork-users] Thesaurus support /online demo

Hi Francois,
Looks very nice!

We have a range of problems we run into, some related to the editor I
assume (on my Firefox the codelists appear all empty in the editor,
Roberto?). On Patrizia's Internet Explorer the list did not expand
with some of the ISO records.

- It would be better to filter the keyword list to only show items
once.
- It's not very clear which Thesaurus you are using. Do I understand
correctly that you define one thesaurus per thesaurus type now?
- When adding a keyword, the associated thesaurus name element should
also be filled to point to the thesaurus. Anyone an idea what should
be put here best? A URI to the rdf of the resource or so?

On Feb 13, 2007, at 8:50 AM, François Prunayre wrote:

Hi all, some news from the thesaurus prototype.
For now, thesaurus support allows to control vocabulary on the >
metadata

editing side (using autocompletion). Then Lucene will make > the index
based on metadata keywords (and not on the thesaurus you > have on the
node).

Cool!! Is there a minimum number of characters a user has to type in
before the query to the application for a list starts?

The administration interface allows import/export/creation/browse >

thesaurus.

Changes are :
- Keyword / metadata edit work for ISO191XX, DC (On FGDC, edit >
keywords is not working. Any ideas why ?)
- Keyword / metadata edit / ISO191XX : Search only according selected

thesaurus Type (discipline, stratum, theme, ...)

- Keyword / Added services for narrower, broader and related keyword
> search

It looks interesting but also quite complex to me, especially because
you have to expand each item manually. It maybe useful to
automatically expand the first level and on click on the next item do
the same for that item instead of clicking on three icons? Also, how
are recurring loops deal with?

All in all, pretty impressive! Hope others have ideas and suggestions
too!

Ciao,
Jeroen

- Administration / Browse thesaurus

The demo is set up with the Agrovoc thesaurus.
http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin/admin

Any comments, ideas ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
>

François Prunayre Envoyé : mercredi 17 janvier 2007 15:00 À :
'Jeroen >
Ticheler'; 'Lagarde Pierre'

Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] [GeoNetwork-users] Thesaurus support >
/online demo

Hi, that's fine for me Jeroen, problem of storing Ids instead of >
keyword

could cause problem later when people export (or harwest) > without
having the same thesaurus...

I made the following changes to the prototype in order to :
- Search interface : Autocompletion for search criteria "keyword" >
based on Lucene Index (and not thesaurus). That way, user will select
only keywords which are in metadata. Here you could have a mix of >

multilingual keywords according to what the editors put in.

- Lucene index configuration : Lucene will not create tokens based on
>

keyword but will index keyword as term (ie. "polar ecosystem" will be
> index as "polar ecosystem" and not as "polar", "ecosystem").

As proposed by Pierre, I will add for ISO standard a filter based on
> the

thesaurus type (place, temporal, discipline ...).

You're right Jeroen, the editor is not working because it's alpha 2.
> You

will be able to have a keyword list but not able to save it.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >
password admin

Francois

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com] Envoyé :
lundi 8 >

janvier 2007 11:21 À : Lagarde Pierre; François Prunayre Cc :

geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-users] Thesaurus support / online demo

Hi François and Pierre,

Both implementations have some nice aspects and I hope we can find a
>

kind of middle way of handling keywords. I feel that using the auto- >
completion facility is the way to go, but it would need to give a more
> flexible way of selecting the right keywords. This should include
the > hierarchy in a thesaurus and also be multilingual in the first
place. > On that part I think the only way to go is to store a keyword
> identifier and not the translated keyword in the text element. The >
system should than use these identifiers to display the local versions
> of the keyword (or provide the default language of the thesaurus if
no > translation is available).

In the editor, the full thesaurus content should e available, while,
> as

François indicated, in the Search interface, only keywords used in
> the
catalog should be presented. In fact, that auto-completion as >
implemented by François would than be a very good first step while a >
pop-up could provide a full-fledged selector that includes hierarchy!?

François, I didn't manage to edit keywords in the FGDC and DC
records. > I

know the alpha 2 is still not finished what the editor concerns, so
> I
assume that is the cause. Roberto is working on it and a functional
> editor
should be ready by the second week of February in a first beta >
release.

I suggest that we do not add the thesaurus functionality to the code
>

base until the prototype is more functional if that's OK with you >
François?

Ciao,
Jeroen

On Jan 6, 2007, at 6:22 PM, Lagarde Pierre wrote:

Hi françois,

Very good to start the integration of french developments of GN >>

(Géosource in french) in GN alpha2 !

The autocompletion is a very interested approach to integrate >>
keywords

(we don't use this solution in Geosource. See http:// >>
212.208.217.23/geosource/srv/fr/main.home).

To complicate yours remarks in Edit interface, I think it will be >>

better to limit the thesaurus query in the thematic of the keywords
>> in
function of the 19115 list. For example, place thesauri, theme >>
thesauri,... And, when the user has chosen a specific word, GN could
>> add the thesaurus name in the specific field !

In your demo, impossible to add new "descriptive keywords" block or
>>

new "keyword" block (id=12)... Side effect ?

Pierre.

-----Message d'origine-----
De : geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] De la part
de >>

François Prunayre Envoyé : vendredi 5 janvier 2007 17:19 À :

geonetwork-devel@lists.sourceforge.net; geonetwork- >>
users@lists.sourceforge.net Objet : [GeoNetwork-users] Thesaurus >>
support / online demo

Hi list, here is a first demo adding support for thesaurus in >>

Geonetwork (based on alpha2 version - thanks Andrea :).

Thesaurus support allows import/export of "external" thesaurus such
>> as

Agrovoc, Gemet or other in rdf/skos format and creation of "local"

thesaurus which will be entirely managed by the administrator of the
>>

geonetwork node.

Local thesaurus could be basic (id, label, definition and lang for
>> each
term) used for thesaurus of type discipline, theme, temporal or of
>>

type place where you could also defined a bounding box for each term.

Thesaurus creation only support flat thesaurus (ie. you can not >>

defined narrower, broader and related term).

When editing metadata, geonetwork will provide an autocompletion
>> field

for keyword searching in all thesaurus available in the current >>
node.

When searching for metadata, in the search field keyword, an >>

autocompletion process is also available.

Demo is http://dev.sandre.eaufrance.fr/gnthesaurus/ login admin / >>

password admin. Go to the administration > Manage thesauri. The demo
>> is set up with 3 external thesauri (agrovoc, a thesaurus for the >>
water domain, and the Geonetwork list of regions) and 2 local ones.

Main features available for now :
- Administration :
  - thesaurus import/export in RDF skos format
  - thesaurus creation/edition for "flat" thesaurus
  - support for multilingual thesaurus.
- Edit interface :
  - Autocompletion for field "keyword" in DC, FGDC and iso19115 (to

be done for ISO19139)

- Search interface :
  - Autocompletion for search criteria "keyword"

For the time being, the user interface query all thesaurus in the >>
current webpage language. But this not really the best option.
For >>
the first implementation, maybe I proposed 2 options for the editing

part

:
- if a language parameter is defined in the current metadata, query

the thesaurus in that language

- if not use the webpage language or we could also defined a >>
parameter

"metatada default language" ? This will allow user not >> having
geonetwork translation (for now en, fr, es, cn) to use their >> own
language for thesaurus.

For the search this is a more complex part. For now, if the user >>

interface is in spanish, it will look for term in spanish in each >>
thesaurus. If the metadata are in english ... it will not be >>
relevant.

Here as a first implementation, we could at least use a parameter >>
"metatada default language". Other and more complex options could
be,

for the keyword criteria

:
- search for a term in user interface language and then query using
>>

the keyword and its translation. Here users need to have multilingual
>> thesaurus.

- proposed the list of keyword found by Lucene in metadata in the >>
indexing process. That way, geonetwork propose only keyword that are

used somewhere in one or more metadata

- analyzed Lucene support for thesaurus ...

The thesaurus are stored in a RDF/SKOS format in the /xml/ codelist/
>>

thesauri directory of Geonetwork. They are loaded on startup and RDF
>> manipulation is made with Sesame, an opensource java library for
RDF >> (http://www.openrdf.org/).

Thanks to Laurent Magnien, Arnaud Dupuis and Jean-Pascal Boignard
for >>

their first ("french") implementation.

Any comments, ideas, bugs ? If that sounds good to the list, I could
>>

put it on the alpha 2 version.

Cheers. Francois

--
Ce message a ete verifie par MailScanner pour des virus ou des >>

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >>

personnels, confidentiels et prives. Toute publication, utilisation
>> ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >>

personal, confidential and secret. Any total or partial publication,
>> use or distribution must be authorized.

--------------------------------------------------------------------
-
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share
>> your
opinions on IT & business topics through brief surveys - and >> earn
cash http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
********************************************************************
*
*
************************
Le contenu de cet e-mail et de ses pièces jointes est destiné à >>
l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas
de >>

réception de cet e-mail par erreur, le signaler à son expéditeur et
>> ne pas en divulguer le contenu.

L'absence de virus a été vérifié à l'émission du message. Il
convient >>

néanmoins de vérifier l'absence de corruption à sa réception. The >>
contents of this email and any attachments are confidential. They are
>> intended for the named recipient(s) only. If you have received this
>> email
in error please notify the system manager or the sender >> immediately
and do not disclose the contents to anyone or make >> copies.

eSafe scanned this email for viruses, vandals and malicious content.
********************************************************************
*
*
************************

--------------------------------------------------------------------
-
-
---
Take Surveys. Earn Cash. Influence the Future of IT Join >>

SourceForge.net's Techsay panel and you'll get the chance to share
>> your
opinions on IT & business topics through brief surveys - and >> earn
cash http://www.techsay.com/default.php?

page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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

-- Ce message a ete verifie par MailScanner pour des virus ou des >
polluriels et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation
ou

diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des >
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >
personnels, confidentiels et prives. Toute publication, utilisation
ou

diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

---------------------------------------------------------------------
-

--- Take Surveys. Earn Cash. Influence the Future of IT Join >

SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys - and
earn cash http://www.techsay.com/default.php? >
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

-- > Ce message a ete verifie par MailScanner pour des virus ou des
>

polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont >
personnels,

confidentiels et prives. Toute publication, utilisation > ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is >
personal,

confidential and secret. Any total or partial > publication, use or
distribution must be authorized.

---------------------------------------------------------------------
-

--- Using Tomcat but need to do more? Need to support web services,
>

security?

Get stuff done quickly with pre-integrated technology to make your >
job

easier.

Download IBM WebSphere Application Server v.1.0.1 based on Apache >
Geronimo http://sel.as-us.falkag.net/sel? >
cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/ >
projects/geonetwork

-- Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.
Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation ou
diffusion, meme partielle, doit etre autorisee.
Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

This message has been scanned by the Trend Micro IGSA and found to be
free of known security risks.

This message has been scanned by the Trend Micro IGSA and found to be
free of known security risks.

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys-and earn
cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

This message has been scanned by the Trend Micro IGSA and found to be
free of known security risks.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork