search

aodn / content

Tracks AODN Portal content and configuration issues
0 stars 0 forks source link

Mini-map not representative of what is shown on step 2 #131

Closed kereid closed 9 years ago

kereid commented 9 years ago

Seeing in Prod and Sys-test

Steps to reproduce:

Narrow down results by selecting Moorings and Buoy. Proceed to last page of results and look at mini-map of collection IMOS - Australian National Mooring Network (ANMN) - Wave time-series

minimap

Add collection to map when taken to step 2 look at bigmap

bigmap

What does happen:

They are different

What should happen:

They should be the same

kereid commented 9 years ago

@bpasquer has confirmed with me that the mini-map is reflective of Manly Hydraulics schema - also the same issue is occurring with Royal Australian Navy (RAN) - CTD profiles in RC

mhidas commented 9 years ago

@kereid I would guess this is a harvester issue - one or more of the harvesters involved are updating the spatial extent in the wrong metadata record!

bpasquer commented 9 years ago

@mhidas I checked ran_ctd, the default context is ok, but not the deployment context. The issue can be solved by correcting the deployment context parameter .

mhidas commented 9 years ago

@bpasquer When harvesters run in production, the values of the context parameters come from the data bags, not from within the Talend project, so that's the place to check. To avoid confusion, however, I think it is a good idea to set the values correctly in both places.

mhidas commented 9 years ago

Here's the problem: https://github.com/aodn/harvesters/issues/283 Probably similar for ANMN Wave as well.

smancini commented 9 years ago

Works fine now