Changes between Version 3 and Version 4 of MetadataRelation
- Timestamp:
- 12/03/09 08:38:19 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MetadataRelation
v3 v4 56 56 57 57 58 Editor could define a layer name using the combo box (which try to retrieve layers from the WMS GetCapabilities document) or typing the layer name in the text field. This information is required to display the layer using the map viewer. 58 Editor could define a layer name using the combo box (which try to retrieve layers from the WMS GetCapabilities document) or typing the layer name in the text field. This information is required to display the layer using the map viewer. A proxy need to be set in order to face the cross domain XHR issue (in config-gui.xml). 59 59 60 61 ==== Link to a feature catalogue ==== 62 Feature catalogues are records stored in ISO 19110 standard. Relation between the 2 records is stored in the relation table of the database. 60 63 61 64 === Proposal Type === … … 82 85 * Metadata navigation between related records 83 86 87 == Minor fix & improvements == 88 * Added an XSL template to get metadata title from UUID (useful to display title instead of UUIDs) 89 * Fixed indexing of operatesOn, parentUUID relations 90 * Fixed add missing namespace to XML fragments in embedded mode 91 * Improved get parameter to take care of UUID or ID if not present (String id = Utils.getIdentifierFromParameters(params, context);). Used in metadata.show, relation.* 92 93 84 94 == Risks == 85 95