Changes between Version 3 and Version 4 of proposals/relatedResource


Ignore:
Timestamp:
Jan 2, 2013, 11:09:56 PM (12 years ago)
Author:
fxp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • proposals/relatedResource

    v3 v4  
    117117=== Add a parent metadata record ===
    118118
     119In order to add a link to a parent metadata record, search for the target record in the popup and select the parent metadata to link to the current in editing.
     120
    119121[[Image(geonetwork-add-parents.png)]]
    120122
     123Once added, the following XML is inserted in the metadata record:
     124
     125{{{
     126<gmd:parentIdentifier>
     127    <gco:CharacterString>SDN:PRODUCT:1850:Time Series Tributyltin (TBT) in Sediment</gco:CharacterString>
     128</gmd:parentIdentifier>
     129}}}
     130
     131In the editor, the relation could be updated in the metadata section:
     132
     133[[Image(geonetwork-edit-parents.png)]]
     134
     135
     136
    121137=== Add a sibling ===
    122138
     139ISO Metadata records can be related to one another in different ways. The elements in the ISO standard that support sibling relationships are the aggregationInfo element. Sibling relationships types can be specified using an extendible codelist. See http://trac.osgeo.org/geonetwork/wiki/MetadataSiblings for more details.
     140
     141
     142In order to add a sibling link:
     143 * choose a type of association
     144 * choose a type of initiative
     145 * and search for the record to link
     146
    123147[[Image(geonetwork-add-siblings.png)]]
     148
     149
     150The type of sibling is displayed in the relation manager which allows to quickly remove the relation if needed:
     151
     152[[Image(geonetwork-add-siblings-ref.png)]]
     153
     154Once added, the following XML is inserted in the metadata record:
     155
     156{{{
     157<gmd:aggregationInfo>
     158        <gmd:MD_AggregateInformation>
     159            <gmd:aggregateDataSetIdentifier>
     160                <gmd:MD_Identifier>
     161                    <!-- optional gmd:authority here: could have details of a register describing the some details of the sibling record -->
     162                    <!-- code is UUID/urn of the sibling record, could be a gmx:Anchor -->
     163                    <gmd:code>
     164                        <gco:CharacterString>urn:marine.csiro.au:project:1532</gco:CharacterString>
     165                    </gmd:code>
     166                </gmd:MD_Identifier>
     167            </gmd:aggregateDataSetIdentifier>
     168            <gmd:associationType>
     169                <gmd:DS_AssociationTypeCode codeList="http://...#DS_AssociationTypeCode"
     170                                            codeListValue="crossReference">crossReference</gmd:DS_AssociationTypeCode>
     171            </gmd:associationType>
     172            <!-- initiative type describes the type of sibling relationship - in this case the code is a project
     173                 related to the record that contains this aggregateInformation -->
     174            <gmd:initiativeType>
     175                <gmd:DS_InitiativeTypeCode codeList="http://...#DS_InitiativeTypeCode"
     176                                           codeListValue="project">project</gmd:DS_InitiativeTypeCode>
     177            </gmd:initiativeType>
     178        </gmd:MD_AggregateInformation>
     179    </gmd:aggregationInfo>
     180}}}
     181
     182
     183=== Relation manager widget advanced configuration ===
     184
     185
     186
     187
    124188
    125189=== Backwards Compatibility Issues ===