Changes between Version 1 and Version 2 of oaipmh_improvements

Timestamp:

07/15/12 21:40:20 (12 years ago)

Author:

simonp

Comment:

--

oaipmh_improvements

@@ -15 +15 @@
  * '''Object harvesting''': In recent times !GeoNetwork has moved from supporting ISO19115/19139 metadata in the form of a 'record' to supporting a tree based hierarchy of ISO19115/19139 metadata 'objects'. The diagram below shows a typical hierarchy:
 
-The mechanisms for handling these relationships are part of the ISO standard. They can be explicit in the form of an xlink that refers directly to the related metadata object:
+The mechanisms for handling these relationships are part of the ISO standard. They can be explicit in the form of an xlink that refers directly to the related metadata object or implicit by including the UUID of a related metadata object as content in an element. Here is an example of an explicit relationship between a metadata record and a fragment of contact information that it includes:
+
+{{{
+
+}}}
+
+Here is an example of an implicit relationship where the UUID of the parent record in a parent-child relationship is held in the content of the parent identifier element:
 
 {{{
 }}}
 
-Or implicit by including the UUID of a related metadata object as content in an element. Here is an example of a parent record UUID in the content of the parent identifier element:
-
-{{{
-}}}
-
-And another example of a sibling relationship between a dataset metadata record and a project metadata record (uuid: urn:marine.csiro.au:marlin:project:187):
+And another example of an implicit relationship where the UUID of the sibling record in a sibling relationship between a dataset metadata record and a project metadata record (uuid: urn:marine.csiro.au:marlin:project:187) is held as a code in an identifier element:
 
 {{{