Changes between Version 11 and Version 12 of ComposedMetadataRecords


Ignore:
Timestamp:
Aug 31, 2009, 9:00:08 PM (15 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ComposedMetadataRecords

    v11 v12  
    4848Metadata records as traditionally handled by !GeoNetwork should not be affected by the addition of this feature.
    4949
    50 Effects on harvesting: Composed metadata records can have their !XLinks resolved before they are harvested as a harvester usually updates the set of records harvested from a remote site on a regular basis. If there was a requirement for composed metadata records to be harvested with unresolved !XLinks then this could be made as an
     50Effects on harvesting: Composed metadata records can have their XLinks resolved before they are harvested as a harvester usually updates the set of records harvested from a remote site on a regular basis. If there was a requirement for composed metadata records to be harvested with unresolved XLinks then this could be made as an
    5151
    52 Effects on export (eg. MEF): Composed metadata records exported as MEF files would normally have their !XLinks resolved before export.
     52Effects on export (eg. MEF): Composed metadata records exported as MEF files would normally have their XLinks resolved before export.
    5353
    5454XLinks and metadata records composed from xlink'd fragments can be made optional through the use of a system configuration option.