I'm creating INSPIRE compliant metadata using the INSPIRE compliant online
editor (http://www.inspire-geoportal.eu/InspireEditor). Although those
INSPIRE metadata are imported successfully to GN (using Administrator/Batch
import) the language branches are not shown.
The INSPIRE language branch content (resource and metadata language) is
<gmd:language><gmd:LanguageCode
codeList="./resources/codeList.xml#LanguageCode"
codeListValue="spa">spa</gmd:LanguageCode></gmd:language> while GN branch
content is
<gmd:language><gco:CharacterString>spa</gco:CharacterString></gmd:language>
the language branch does not show, because GeoNetwork ist making a mistake
when it comes to writing down the language when you create metadata with
GeoNetwork itself. This was true for version 2.4 and it is also true for
version 2.6 of GeoNetwork.
GeoNetwork writes the following xml-structure for the language:
This is wrong for INSPIRE (maybe it is even wrong for ISO, I cannot tell).
If you import this section or fill it into a template for GeoNetwork, this
part cannot be displayed. I think this is because GeoNetwork has not
information on howto display this part of the metadata. There should be an
information given at import how this metadata can be displayed. So maybe one
has to chose a style sheet for the import. (There is a drop-down list in
GeoNetwork.) The problem for us is, how to create such a style sheet?! And:
is this the right thing to do at all?
The whole thing gets even worse if you try to import metadata from other
catalogues. For each catalogue there has to be a special stylesheet. (Is
this true?) At least this is what we think about at the moment.
I think the users need more information on this topic, so maybe somebody
could document the whole thing: What is the connection between a
metadata.xml you import an the kind of display on the screen within
GeoNetwork? How can one stick the information about the kind of display on
the screen to the importet metadata?
My English is not good at all today, but I do hope you understand my point.
Maybe somebody around here can give us some help
the language branch does not show, because GeoNetwork ist making a mistake
when it comes to writing down the language when you create metadata with
GeoNetwork itself. This was true for version 2.4 and it is also true for
version 2.6 of GeoNetwork.
GeoNetwork writes the following xml-structure for the language:
If you import this section or fill it into a template for GeoNetwork, this
part cannot be displayed. I think this is because GeoNetwork has not
information on howto display this part of the metadata. There should be an
information given at import how this metadata can be displayed. So maybe one
has to chose a style sheet for the import. (There is a drop-down list in
GeoNetwork.) The problem for us is, how to create such a style sheet?! And:
is this the right thing to do at all?
The whole thing gets even worse if you try to import metadata from other
catalogues. For each catalogue there has to be a special stylesheet. (Is
this true?) At least this is what we think about at the moment.
I think the users need more information on this topic, so maybe somebody
could document the whole thing: What is the connection between a
metadata.xml you import an the kind of display on the screen within
GeoNetwork? How can one stick the information about the kind of display on
the screen to the importet metadata?
My English is not good at all today, but I do hope you understand my point.
Maybe somebody around here can give us some help
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
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
Thanks fot the ticket, I'll wait for the solution.
Unfortunately, our metadata must be INSPIRE compliant, that is, validated by
INSPIRE metadata validator.
Unluckily, the ticket has been classified as an improvement (minor
priority), but for our organization it's a must. I cannot put GN into
production till this issue is not solved.
Any ideas to solve that temporarily will be welcome.
