Hi Francois,
Although it hasn't been implemented yet the proper use of reusing duplicate
information in metadata records is the xlink attribute.
Although one can use the parentIdentifier to identify the fileIdentifier of
the parent metadata record, I don't know of anyway for the content of the
parent metadata record to be included into the child metadata record other
than xlink.
It may be possible for some Australians to look at incorporating xlink into
GeoNetwork. However we won't have that discussion until March 2008 and the
outcomes of that discussion may be that it won't be done.
I hope that this helps.
John
-----Original Message-----
From: geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] On
Behalf Of Francois-Xavier Prunayre
Sent: Wednesday, 2 January 2008 8:50 PM
To: geonetwork-users@lists.sourceforge.net
Subject: [GeoNetwork-users] "Duplicate" metadata, Datasets and Series
Hi list, I'm looking for some advice/comments on how to deal with
"duplicate" metadata between datasets and series.
I've to deal with more and more datasets and sometimes
metadata are more
or less the same between datasets (ie. only title, point of
contact and
bbox are different). These metadata are edited by different
organisations and sometimes in different catalogues.
It looks like we could set up control on the metadata editing / search
tools between a "master" metadata and childs metadata in order to have
easy editing for user but it seems quite difficult and
complex to do so
: some sections in read-only, some sections not ...
Maybe a more generic approach could be to use relationship between
series and datasets as defined in ISO and then set up a MD_Metadata
composed of a series which has 0..n MD_Metadata :
gmd:series/gmd:DS_Series/gmd:composedOf/gmd:DS_DataSet/gmd:has
/gmd:MD_Metadata
Then could we described the dataset completely in the
DS_Series element
or having a gmd:MD_Metadata element pointing to another metadata using
the uuid attribute ? This uuid could be in the local node or even in
another remote node. Then how to resolve uuid ? Use of
xlink:href could
be better ...
Anybody using such mechanism ? Comments are welcomed.
Thanks.
Francois
--------------------------------------------------------------
-----------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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 John for the input.
John.Hockaday@anonymised.com wrote:
Hi Francois,
Although it hasn't been implemented yet the proper use of reusing duplicate
information in metadata records is the xlink attribute.
You're right using an xlink we could probably include the xml document
pointing by the href attribute during xslt processing or only display an
hyperlink to the document using xlink:href and xlink:title attributes.
Although one can use the parentIdentifier to identify the fileIdentifier of
the parent metadata record, I don't know of anyway for the content of the
parent metadata record to be included into the child metadata record other
than xlink.
Problem I have with parentIdentifier is that usually we have the unique
identifier of the metadata in that field. It could be resolved if the
metadata is available in the local catalogue but how to link a metadata
with a parentIdentifier which is in another catalogue. Problem could be
eventually solved using urn adresse (eg.
urn:metadata:catalogue:identifier) but then we need something to be able
to resolve urn to point to a valid resource (that's what xlink does
using the href attribute and it seems much easier) ....
For the implementation of the ISO19119, I'll probably add to the uuidref
attribute an xlink to link the metadata for the service which
"operatesOn" layers to be able to browse from the service metadata to
the layers metadata ...
Ciao. Francois
It may be possible for some Australians to look at incorporating xlink into
GeoNetwork. However we won't have that discussion until March 2008 and the
outcomes of that discussion may be that it won't be done.
I hope that this helps.
John
-----Original Message-----
From: geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] On
Behalf Of Francois-Xavier Prunayre
Sent: Wednesday, 2 January 2008 8:50 PM
To: geonetwork-users@lists.sourceforge.net
Subject: [GeoNetwork-users] "Duplicate" metadata, Datasets and Series
Hi list, I'm looking for some advice/comments on how to deal with
"duplicate" metadata between datasets and series.
I've to deal with more and more datasets and sometimes
metadata are more
or less the same between datasets (ie. only title, point of
contact and
bbox are different). These metadata are edited by different
organisations and sometimes in different catalogues.
It looks like we could set up control on the metadata editing / search
tools between a "master" metadata and childs metadata in order to have
easy editing for user but it seems quite difficult and
complex to do so
: some sections in read-only, some sections not ...
Maybe a more generic approach could be to use relationship between
series and datasets as defined in ISO and then set up a MD_Metadata
composed of a series which has 0..n MD_Metadata :
gmd:series/gmd:DS_Series/gmd:composedOf/gmd:DS_DataSet/gmd:has
/gmd:MD_Metadata
Then could we described the dataset completely in the
DS_Series element
or having a gmd:MD_Metadata element pointing to another metadata using
the uuid attribute ? This uuid could be in the local node or even in
another remote node. Then how to resolve uuid ? Use of
xlink:href could
be better ...
Anybody using such mechanism ? Comments are welcomed.
Thanks.
Francois
--------------------------------------------------------------
-----------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
--
Francois Xavier Prunayre
Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex
Tel : + 33 (0)6 34 11 71 75
http://www.camptocamp.com
francois-xavier.prunayre@anonymised.com
Hi both,
Indeed xlink (or xinclude) could be what we use internally. What goes out to others would be the fully merged metadata document. In the editor, a system very much like the prototype sub-template system could be used, or what BRGM implemented for SRS in geosource (!?).
What we should work on is to define the main metadata objects that we want to store as separate entities. Things like the contacts, SRS, citations et cetera.
Do we want such implementation to be generic with respect to these objects? And if so, how generic to ensure we can build a usable user interface at the front end? Should we store the duplicates as templates? Should they be stored in separate tables, or simply be flagged as objects in the metadata table?
Once we have agreement on those aspects and possibly others, we can define what the implementation should look like.
Implementation of the ebXML meta model seems to move us in such direction and vice versa 
Ciao,
Jeroen
On Jan 3, 2008, at 12:23 AM, John.Hockaday@anonymised.com wrote:
Hi Francois,
Although it hasn't been implemented yet the proper use of reusing duplicate
information in metadata records is the xlink attribute.
Although one can use the parentIdentifier to identify the fileIdentifier of
the parent metadata record, I don't know of anyway for the content of the
parent metadata record to be included into the child metadata record other
than xlink.
It may be possible for some Australians to look at incorporating xlink into
GeoNetwork. However we won't have that discussion until March 2008 and the
outcomes of that discussion may be that it won't be done.
I hope that this helps.
John
-----Original Message-----
From: geonetwork-users-bounces@lists.sourceforge.net
[mailto:geonetwork-users-bounces@lists.sourceforge.net] On
Behalf Of Francois-Xavier Prunayre
Sent: Wednesday, 2 January 2008 8:50 PM
To: geonetwork-users@lists.sourceforge.net
Subject: [GeoNetwork-users] "Duplicate" metadata, Datasets and Series
Hi list, I'm looking for some advice/comments on how to deal with
"duplicate" metadata between datasets and series.
I've to deal with more and more datasets and sometimes
metadata are more
or less the same between datasets (ie. only title, point of
contact and
bbox are different). These metadata are edited by different
organisations and sometimes in different catalogues.
It looks like we could set up control on the metadata editing / search
tools between a "master" metadata and childs metadata in order to have
easy editing for user but it seems quite difficult and
complex to do so
: some sections in read-only, some sections not ...
Maybe a more generic approach could be to use relationship between
series and datasets as defined in ISO and then set up a MD_Metadata
composed of a series which has 0..n MD_Metadata :
gmd:series/gmd:DS_Series/gmd:composedOf/gmd:DS_DataSet/gmd:has
/gmd:MD_Metadata
Then could we described the dataset completely in the
DS_Series element
or having a gmd:MD_Metadata element pointing to another metadata using
the uuid attribute ? This uuid could be in the local node or even in
another remote node. Then how to resolve uuid ? Use of
xlink:href could
be better ...
Anybody using such mechanism ? Comments are welcomed.
Thanks.
Francois
--------------------------------------------------------------
-----------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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