Closed chpicone closed 3 years ago
Keywords now will be handled in two different points:
GeoNode
. Only those will be preserved and will continue the processKeywordHandler
in GeoNode
goes in append/extend
, the keywords automatically assigned (like filename, GeoTIFF ecc..) are going to be deleted in the METADATA_STORERS hook. The hook will loop all the keywords assigned to the layer and will keep ONLY the keywords that are considered valid from the parsing process.Example: Parsing: | XML | In GeoNode | Output | Notes |
---|---|---|---|---|
k1 , k2 , k3 |
k1 , k2 , k5 |
k1 , k2 |
k3 is discarded |
Storing: | From parsing | Layer | Output | Notes |
---|---|---|---|---|
k1 , k2 |
k1 , k2 , k6 , k7 |
k1 , k2 |
k6 and k7 are going to be deleted |
Ouput:
The Layer uploaded will have k1
and k2
as keywords
When we import a raster using the REST GeoNode Api, currently GeoNode is adding some custom keywords like the name of the layer, "geotif" ect. The customer wants to use (from the provided set of keywords in the metadata) just the keywords already defined via the Hierarchical Keywords admin page.
Example 1: In GeoNode the following keywords are defined: A; B; C If we load an image with the keywords C; D; E (from the XMP metadatadefinition) just the keyword C must be saved.
Example 2: In GeoNode the following keywords are defined: A; B; C If we load an image with the keywords D; E (from the XMP metadatadefinition). Cause GeoNode needs at least 1 keyword we will use the type of the layer (eg GeoTif)