I have a question related to CSW behaviour with multilingual metadata.
I think that Geonetwork handles multilanguage metadata quite nice: for
instance, if I open GN and I choose the catalan language and I search for
metadata, the multilingual metadata are shown in catalan (that is, the
catalan "locale" metadata branches are shown instead of the default language
branches), if I change GN to french language, and I search for metadata, the
multilingual metadata are shown in french (that is, the french "locale"
branches are shown instead of the default language branches),and so on.
The question is, how can I get the same behaviour with *CSW *'*GetRecords*'
and '*GetRecordsByID*'. Can anybody give me some advice how to write the two
POST messages to receive the multilingual metadata *only in a specified
"locale" language* like the GN interface provides?
I have a question related to CSW behaviour with multilingual metadata.
I think that Geonetwork handles multilanguage metadata quite nice: for
instance, if I open GN and I choose the catalan language and I search for
metadata, the multilingual metadata are shown in catalan (that is, the
catalan "locale" metadata branches are shown instead of the default language
branches), if I change GN to french language, and I search for metadata, the
multilingual metadata are shown in french (that is, the french "locale"
branches are shown instead of the default language branches),and so on.
The question is, how can I get the same behaviour with *CSW *'*GetRecords*'
and '*GetRecordsByID*'. Can anybody give me some advice how to write the two
POST messages to receive the multilingual metadata *only in a specified
"locale" language* like the GN interface provides?
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
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
-----Original Message-----
From: Francois Prunayre [mailto:fx.prunayre@anonymised.com]
Sent: Tuesday, 28 June 2011 06:03
To: mmarco
Cc: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] CSW GetRecords and CSW
GetRecordsByID for multilingual metadata
Hi Montse,
2011/6/28 mmarco <mmarcosabate@anonymised.com>:
> Hi,
>
> I have a question related to CSW behaviour with
multilingual metadata.
>
> I think that Geonetwork handles multilanguage metadata
quite nice: for
> instance, if I open GN and I choose the catalan language
and I search
> for metadata, the multilingual metadata are shown in
catalan (that is,
> the catalan "locale" metadata branches are shown instead of the
> default language branches), if I change GN to french
language, and I
> search for metadata, the multilingual metadata are shown in
french (that is, the french "locale"
> branches are shown instead of the default language
branches),and so on.
>
> The question is, how can I get the same behaviour with *CSW
*'*GetRecords*'
> and '*GetRecordsByID*'. Can anybody give me some advice how
to write
> the two POST messages to receive the multilingual metadata
*only in a
> specified "locale" language* like the GN interface provides?
Use the english CSW entry point http://localhost:8080/geonetwork/srv/en/csw
or the french http://localhost:8080/geonetwork/srv/fr/csw
or others
and if CSW requests ask for dublincore output, you'll get
metadata content according to the entry point URL (like in the GUI).
If you ask for ISO record in output, then the client has to
look for the translation in the ISO PT_FreeText elements.
Francois: does GN CSW accept the Accept-Languages HTTP header? I'm also
guessing one can do this with a filter against apiso:Language (for
APISO).
-----Original Message-----
From: Francois Prunayre [mailto:fx.prunayre@anonymised.com]
Sent: Tuesday, 28 June 2011 06:03
To: mmarco
Cc: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] CSW GetRecords and CSW
GetRecordsByID for multilingual metadata
Hi Montse,
2011/6/28 mmarco <mmarcosabate@anonymised.com>:
> Hi,
>
> I have a question related to CSW behaviour with
multilingual metadata.
>
> I think that Geonetwork handles multilanguage metadata
quite nice: for
> instance, if I open GN and I choose the catalan language
and I search
> for metadata, the multilingual metadata are shown in
catalan (that is,
> the catalan "locale" metadata branches are shown instead of the
> default language branches), if I change GN to french
language, and I
> search for metadata, the multilingual metadata are shown in
french (that is, the french "locale"
> branches are shown instead of the default language
branches),and so on.
>
> The question is, how can I get the same behaviour with *CSW
*'*GetRecords*'
> and '*GetRecordsByID*'. Can anybody give me some advice how
to write
> the two POST messages to receive the multilingual metadata
*only in a
> specified "locale" language* like the GN interface provides?
Use the english CSW entry point http://localhost:8080/geonetwork/srv/en/csw
or the french http://localhost:8080/geonetwork/srv/fr/csw
or others
and if CSW requests ask for dublincore output, you'll get
metadata content according to the entry point URL (like in the GUI).
If you ask for ISO record in output, then the client has to
look for the translation in the ISO PT_FreeText elements.
Francois: does GN CSW accept the Accept-Languages HTTP header?
No AFAIK.
I'm also
guessing one can do this with a filter against apiso:Language (for
APISO).
Then you make a query on the language criteria but does not do any
filter on the content returned by the CSW response.