Changes between Version 4 and Version 5 of XLinkedFragments

Timestamp:

Oct 10, 2008, 7:34:38 AM (16 years ago)

Author:

Fxp

Comment:

--

XLinkedFragments

@@ -4 +4 @@
 Store fragments of metadata as reference using XLink. Remote fragments are not editable in the metadata editor. The source document has to be modified.
 
-Metadata stored in DB:
+=== Main principle ===
+Metadata stored in DB
 {{{
 <gmd:contact>
@@ -24 +25 @@
 }}}
 
+== Configuration ==
+In xml/schemas/iso19139/schema-suggestion.xml, catalogue administrator could define which element should propose a popup to select a remote resource and set the xlink for this elements.
+
+ * To add a new xlink popup on an element add a new field <field name="nsPrefix:elementName" mode="xlink|xlinkOnly"/>
+ * Different modes are available:
+  * xlink: will allow classic editor AND xlink popup
+  * xlinkOnly: will only allow xlink popup
+ * If not set default editor is used.
+
+For example :
+{{{
+        <!-- xLink : as defined in XSD, all PropertyType having an
+                attribute group set to gco:ObjectReference could be linked
+                using xlink attributes. 
+                
+                For each elements allows user to use default editor or 
+                defined a remote resource using an xlink.               
+        -->
+        <field name="gmd:contact" mode="xlink"/>
+        <field name="gmd:citedResponsibleParty" mode="xlink"/>
+        <field name="gmd:pointOfContact" mode="xlinkOnly"/>
+        <field name="gmd:distributionFormat" mode="xlink"/>
+        <field name="gmd:descriptiveKeywords" mode="xlink"/>
+        <field name="gmd:referenceSystemInfo" mode="xlink"/>
+}}}     
+
+
+Then if a field is set with mode = xlink, GUI is :
+TODO
+is mode = xlinkOnly, GUI is:
+TODO
 
 == Metadata storage and XLink resolution ==