We are including literature references on GN, and using the Dublin Core profile. We are following the sample record provided with GN. A couple of things have arisen.
1. the sample data for the coverage entry (<dc:coverage>North 90, South -90, East 180, West -180. (Global)</dc:coverage>) seems to require the trailing "." after the -180, plus some character(s) before the terminating tag. Is this a bug?
2. is there support for GN features like the interactive map for Dublin Core, or the link to Google Earth?
One alternative we have considered is to flip the metadata into ISO-19115, but it seems excessive.
Hi Terry,
2014-02-06 20:05 GMT+01:00 Terry <terry.curran@anonymised.com>:
We are including literature references on GN, and using the Dublin Core
profile. We are following the sample record provided with GN. A couple
of things have arisen.
1. the sample data for the coverage entry (<dc:coverage>North 90, South
-90, East 180, West -180. (Global)</dc:coverage>) seems to require the
trailing "." after the -180, plus some character(s) before the
terminating tag. Is this a bug?
Maybe this part should be more flexible.
https://github.com/geonetwork/core-geonetwork/blob/develop/web/src/main/webapp/WEB-INF/data/config/schema_plugins/dublin-core/present/metadata-edit.xsl#L246
2. is there support for GN features like the interactive map for Dublin
Core, or the link to Google Earth?
AFAIK no, mainly because in DC records, links have no type (protocol)
information so we can't now which links are WMS. BTW you should be able to
create link to KML documents which will be opened in Google Earth.
Cheers.
Francois
One alternative we have considered is to flip the metadata into
ISO-19115, but it seems excessive.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
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
Hi Francois,
In the github code, would this replacement string fix the last coordinate pair value? There is a space between \. and the single quote. Or, are we fixing something that should not happen?
<xsl:variable name="coverage" select="tokenize( . ,'\. ')"/>
On 2014-02-20 12:34 AM, Francois Prunayre wrote:
Hi Terry,
2014-02-06 20:05 GMT+01:00 Terry <terry.curran@anonymised.com <mailto:terry.curran@anonymised.com>>:
<-- snip -->
1. the sample data for the coverage entry (<dc:coverage>North 90,
South
-90, East 180, West -180. (Global)</dc:coverage>) seems to
require the
trailing "." after the -180, plus some character(s) before the
terminating tag. Is this a bug?
Maybe this part should be more flexible.
https://github.com/geonetwork/core-geonetwork/blob/develop/web/src/main/webapp/WEB-INF/data/config/schema_plugins/dublin-core/present/metadata-edit.xsl#L246
<-- snip-->