Changes between Version 8 and Version 9 of MetadataSiblings
- Timestamp:
- 09/19/12 21:44:07 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MetadataSiblings
v8 v9 14 14 * can index these relationships to support search 15 15 * has services for retrieving a specific set of related records or the entire collection of related records 16 This proposal adds sibling relationships between metadata records to !GeoNetwork. The elements in the ISO standard that support sibling relationships are the aggregate dInformation 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.16 This proposal adds sibling relationships between metadata records to !GeoNetwork. The elements in the ISO standard that support sibling relationships are the aggregateInformation 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. 17 17 18 18 [[Image(ClassicSiblingRelationships.png)]] … … 36 36 == Proposal == 37 37 38 Aggregate Information in an ISO record that has a related sibling record uses the aggregateInformation element s. This looks something like the following:38 Aggregate Information in an ISO record that has a related sibling record uses the aggregateInformation element. This looks something like the following: 39 39 40 40 {{{ … … 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'). 67 67 68 69 68 70 === Backwards Compatibility Issues === 69 71 None known.