Changes between Initial Version and Version 1 of MetadataSiblings

Timestamp:

Sep 19, 2012, 8:06:23 PM (12 years ago)

Author:

simonp

Comment:

--

MetadataSiblings

@@ +1 @@
+= Metadata Record Sibling Relationships =
+
+|| '''Date''' || 2012/09/20 ||
+|| '''Contact(s)''' || Simon Pigot ||
+|| '''Last edited''' || 2012-09-20 ||
+|| '''Status''' || complete, being discussed ||
+|| '''Assigned to release''' || 2.9.0 ||
+|| '''Resources''' || Available ||
+|| '''Ticket #''' || #XYZ ||
+
+== Overview ==
+
+ISO Metadata records can be related to one another in different ways. The mechanisms for handling these relationships are most often part of the standard in the form of specific elements eg. parent-child relationships are handled through the parentIdentifier element and the datasets that a service delivers are handled through the operatesOn element. !GeoNetwork:
+ * can index these relationships to support search
+ * has services for retrieving a specific set of related records or the entire collection of related records
+This proposal adds sibling relationships between metadata records to !GeoNetwork. The elements in the ISO standard that support sibling relationships are the aggregatedInformation element. Sibling relationships types can be specified using an extendible codelist. Sibling records would be displayed under the relationship type. An example of how sibling relations are displayed in the classic interface and the new ExtJS interface is shown below.
+
+    
+ 
+
+=== Proposal Type ===
+ * '''Type''': GUI Change, Core Change, Module Change, Guideline and project governance procedures, ...
+ * '''App''': !GeoNetwork or !Intermap
+ * '''Module''': eg. Harvester, Kernel, Data Manager, Metadata Import, Lucene Index, Search Interface ...
+
+=== Links ===
+ * '''Documents''':
+ * '''Email discussions''':
+ * '''Other wiki discussions''':
+
+=== Voting History ===
+ * Vote proposed by X on Y, result was +/-n (m non-voting members).
+
+----
+
+== Motivations ==
+The current configuration is .... A change to ....
+
+== Proposal == 
+
+{{{
+    <gmd:aggregateInformation>
+
+        <gmd:MD_AggregateInformation>
+
+            <gmd:aggregateDataSetIdentifier>
+
+                <gmd:MD_Identifier>
+
+                    <gmd:authority>
+
+                        <gmd:CI_Citation>
+
+                            <gmd:title>
+
+                                <gco:CharacterString>MarLIN Project Register</gco:CharacterString>
+
+                            </gmd:title>
+                            <gmd:date gco:nilReason="missing"/>
+                            <gmd:edition>
+
+                                <gco:CharacterString>urn:marine.csiro.au:projectregister:conceptscheme#0.0</gco:CharacterString>
+
+                            </gmd:edition>
+                            <gmd:editionDate>
+
+                                <gco:Date>2012-06-18</gco:Date>
+
+                            </gmd:editionDate>
+                            <gmd:identifier>
+
+                                <gmd:MD_Identifier>
+
+                                    <gmd:code>
+
+                                        <gmx:Anchor xmlns:gmx="http://www.isotc211.org/2005/gmx" xlink:href="/srv/en/?uuid=urn:marine.csiro.au:projectregister">geonetwork.thesaurus.register.project.urn:marine.csiro.au:projectregister</gmx:Anchor>
+
+                                    </gmd:code>
+
+                                </gmd:MD_Identifier>
+
+                            </gmd:identifier>
+                            <gmd:citedResponsibleParty>
+
+                                <gmd:CI_ResponsibleParty>
+
+                                    <gmd:organisationName>
+
+                                        <gco:CharacterString>CSIRO Marine and Atmospheric Research Data Centre</gco:CharacterString>
+
+                                    </gmd:organisationName>
+                                    <gmd:role>
+
+                                        <gmd:CI_RoleCode codeList="http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="custodian">custodian</gmd:CI_RoleCode>
+
+                                    </gmd:role>
+
+                                </gmd:CI_ResponsibleParty>
+
+                            </gmd:citedResponsibleParty>
+
+                        </gmd:CI_Citation>
+
+                    </gmd:authority>
+                    <gmd:code>
+
+                        <gco:CharacterString>urn:marine.csiro.au:project:1532</gco:CharacterString>
+
+                    </gmd:code>
+
+                </gmd:MD_Identifier>
+
+            </gmd:aggregateDataSetIdentifier>
+            <gmd:associationType>
+
+                <gmd:DS_AssociationTypeCode codeList="http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/resources/Codelist/gmxCodelists.xml#DS_AssociationTypeCode" codeListValue="crossReference">crossReference</gmd:DS_AssociationTypeCode>
+
+            </gmd:associationType>
+            <gmd:initiativeType>
+
+                <gmd:DS_InitiativeTypeCode codeList="http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/resources/Codelist/gmxCodelists.xml#DS_InitiativeTypeCode" codeListValue="project">project</gmd:DS_InitiativeTypeCode>
+
+            </gmd:initiativeType>
+
+        </gmd:MD_AggregateInformation>
+
+    </gmd:aggregateInformation>
+}}}
+An in depth proposal can be found here : link
+...
+
+=== Backwards Compatibility Issues ===
+
+=== New libraries added ===
+Explain which and why new libraries are required for that proposal ...
+
+== Risks ==
+
+== Participants ==
+ * List of participants and role (if necessary) in current GIP