Changes between Version 28 and Version 29 of ComposedMetadataRecords


Ignore:
Timestamp:
08/31/09 23:41:44 (15 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ComposedMetadataRecords

    v28 v29  
    2121=== Links ===
    2222 * '''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. 
     23
    2324 * '''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 and in the literature. Another term with similar concepts but more heavily focused on reuse/normalization/removal of redundancy (as used for relational databases) 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 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.
    2425