Changes between Version 12 and Version 13 of extractSubtemplates

Timestamp:

May 3, 2012, 8:03:58 AM (12 years ago)

Author:

simonp

Comment:

--

extractSubtemplates

@@ -11 +11 @@
 == Overview ==
 
-With the addition of the XLink functions, fragment harvesting, subtemplate (= fragment with an id in the Metadata table of the !GeoNetwork database) support and management of directories of subtemplates, !GeoNetwork can now support reusable fragments of metadata. However many sites have metadata records with common fragments of metadata that they would like to extract into directories of subtemplates. This proposal adds a batch operation for admin users that will extract fragments from a selected set of records. Common fragments are identified by calculating the checksum of the text content and using this as the uuid of the fragment.
+With the addition of the XLink processing, fragment harvesting, subtemplate (= fragment with an id in the Metadata table of the !GeoNetwork database) support and tools for managing directories of subtemplates, !GeoNetwork can now begin to support reusable fragments of metadata linked into records. However many sites have metadata records with common fragments of metadata that they would like to extract into directories of subtemplates. This proposal adds a batch operation for admin users that will extract fragments from a selected set of records. Fragments are identified as follows: if the root element of the subtemplate has a uuid attribute, then this will be the uuid of the extracted subtemplate. If there is no uuid attribute on the root element of the subtemplate, then one is obtained by calculating the checksum of the text content of the fragment. 
 
 === Proposal Type ===
@@ -120 +120 @@
 [[Image(manage-directories-window.png)]]
 
+=== Removing duplicates in the extraction process ===
+
+As mentioned above, subtemplates created from an extraction can be assigned a uuid from the uuid attribute on the root element of the subtemplate or if that doesn't exist, a uuid will be calculated using a sha1 checksum on the text content of the subtemplate.
+
+The advantage of this procedure is that the records can be preprocessed using a batch XSLT operation in GeoNetwork that calculates a uuid and stores it as an attribute using rules appropriate to the site - eg. if extracting contact information as subtemplates, a site may decide that all fragments of contact information with the same organisation name should be linked to one subtemplate. To achieve this, a batch XSLT operation can be run before the subtemplate extraction to assign the same uuid to all fragments with the same organisation name.
+
 === Backwards Compatibility Issues ===