Changes between Version 37 and Version 38 of ComposedMetadataRecords

Timestamp:

Sep 27, 2009, 9:22:41 AM (15 years ago)

Author:

simonp

Comment:

--

ComposedMetadataRecords

@@ -22 +22 @@
  * '''Subtemplates''': Metadata fragments are equivalent to subtemplates (which were only partially implemented in !GeoNetwork). Subtemplates appear to have been an extension of the template concept in !GeoNetwork. Templates are complete metadata records with some elements filled in. A user can clone such a record for use in the editor as a template. At this stage all connection between the template and the cloned record is broken ie. changes to the template are not visible in the cloned record and vice versa. Subtemplates (as they were partially implemented in !GeoNetwork) took the template concept down to the level of individual elements in the metadata record. So for example, contact information could be saved as a subtemplate and then reused when editing different elements. The implementation of subtemplates didn't make clear whether the link between a subtemplate and the record it had been added to was maintained. This proposal intends to implement subtemplates as fragments of metadata harvested from an external database - the link between a metadata record and a fragment will be maintained ie. changes in the fragment will be visible in the record.  
 
- * '''Composed, Componentized and Relational Metadata''': The idea of composed or componentized metadata and the term composed metadata is not new, it appears to be common to many discussions on the net and in the literature and its implementation is probably an aim of many metadata tools. Another term with similar aims but which uses the concepts of reuse/normalization/removal of redundancy from relational database terminology is "relational" metadata (eg. LISASoft metadata report). Although there has been discussion in and around these topics and even some implementation of fragments in !GeoNetwork as subtemplates, this proposal suggests a mechanisms for implementing these concepts in !GeoNetwork using fragments harvested from a database with a WFS interface. 
+ * '''Composed, Componentized and Relational Metadata''': The idea of composed or componentized metadata and the term composed metadata is not new, it appears to be common to many discussions on the net (see for example Ted Habermann's proposal http://trac.osgeo.org/geonetwork/wiki/ComponentsAndComposites) and in the literature and its implementation is probably an aim of many metadata tools. Another term with similar aims but which uses the concepts of reuse/normalization/removal of redundancy from relational database terminology is "relational" metadata (eg. LISASoft metadata report). Although there has been discussion in and around these topics and even some implementation of fragments in !GeoNetwork as subtemplates, this proposal suggests a mechanisms for implementing these concepts in !GeoNetwork based on the harvester concept. A harvester brings in metadata fragments (initially from a WFS but conceivably any harvest source could do this) and can build composed metadata records from a template and fragments.
 
 === Voting History ===
@@ -77 +77 @@
  * URN resolver and !GeoServer community schema support: !AuScope/Spatial Information Services Stack (SISS) team
  * "Relational" metadata - LISASoft developers?
+ * Ted Habermann and team at NOAA National Geophysical Data Center 
  * Others?