Changes between Version 9 and Version 10 of MetadataSiblings

Timestamp:

Sep 19, 2012, 10:18:30 PM (12 years ago)

Author:

simonp

Comment:

--

MetadataSiblings

@@ -66 +66 @@
 The UUID of the related record is held in an MD_Identifier element, the associationType is set to crossReference (which seems the most appropriate association type code) and the initiativeType is set to the type of sibling relationship (in this example 'project').
 
-
+To retrieve and display related records from the aggregateInformation block, we extend the process that is used for parent-child and other relationships:
+ * in the java code underlying the GetRelated guiservice. A simple XPath extraction for all aggregateInformation elements that have an aggregateDataSetIdentifier with a code, an associationType with value set to crossReference and an initiativeType is used to assemble the list of codes (UUIDs/URNs). Sibling metadata records are extracted from the database and attached to the XML output of the GetRelated guiservice.
+ * add processing of the GetRelated output in relations.xsl which is used in the xml.relation service - returns a simple/brief view of the related records.
+ * add processing of related sibling records from guiservice to iso19139/present/metadata-iso19139-utils.xsl - this XSLT generates the classic presentation of related records - see below.
+ * add processing of related sibling records from xml.relations to the ExtJS MetadataRelationStore.js and the ExtJS user interface.  
 
 === Backwards Compatibility Issues ===