Changes between Version 5 and Version 6 of ComposedMetadataRecords


Ignore:
Timestamp:
08/31/09 20:34:33 (15 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ComposedMetadataRecords

    v5 v6  
    2020
    2121=== Links ===
    22  * '''Other terms''': Metadata fragments are equivalent to subtemplates, a concept which has only ever been partially implemented in !GeoNetwork. This proposal intends to implement subtemplates as fragments of metadata harvested from an external database. The idea of composed or componentized metadata and the term itself, appears to be common to many discussions on the net eg. (albeit obliquely) http://eww.jot.fm/issues/issue_2007_11/column6.pdf. Another term with similar concepts is "relational" metadata. Although there has been discussion in and around these topics, this proposal appears to be the first to suggest the mechanisms for implementing these concepts in !GeoNetwork using fragments harvested from a database with a WFS interface.
     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  This proposal intends to implement subtemplates as fragments of metadata harvested from an external database.
     23 * '' Composed, Componentized and Relational Metadata'': The idea of composed or componentized metadata and the term itself, appears to be common to many discussions on the net eg. (albeit obliquely) http://eww.jot.fm/issues/issue_2007_11/column6.pdf. Another term with similar concepts is "relational" metadata. Although there has been discussion in and around these topics and even some implementation of fragments as subtemplates, this proposal appears to be the first to suggest the mechanisms for implementing these concepts in !GeoNetwork using fragments harvested from a database with a WFS interface.
    2324 * '''Email discussions''':
    2425 * '''Other wiki discussions''':