Changes between Version 3 and Version 4 of MetadataRelation


Ignore:
Timestamp:
Dec 3, 2009, 8:38:19 AM (15 years ago)
Author:
fxp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MetadataRelation

    v3 v4  
    5656
    5757
    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.
     58Editor 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).
    5959
     60
     61==== Link to a feature catalogue ====
     62Feature catalogues are records stored in ISO 19110 standard. Relation between the 2 records is stored in the relation table of the database.
    6063
    6164=== Proposal Type ===
     
    8285 * Metadata navigation between related records
    8386
     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
    8494== Risks ==
    8595