Thanks Matt, Can u tell me in detail how to configure GeoNode to ensure it uses GeoNetwork 2.6.3? How do i upgrade GeoNetwork to the required version?
On Thu, Feb 3, 2011 at 11:49 PM, Matt Bertrand <[email protected]>wrote: > Is it possible that the version of geonetwork included with geonode > contains this bug? : > http://osgeo-org.1803224.n2.nabble.com/Wildcard-in-GetRecords-query-td5578657.html > > That would explain why wildcard search began to work when I upgraded to > geonetwork 2.6.3, without having to change any parameters. I checked the > owslib code and it seems to be inserting wildcard characters correctly: > http://trac.gispython.org/lab/browser/OWSLib/trunk/owslib/filter.py?rev=1698#L116 > > -Matt > > > > On 2/3/11 9:05 AM, David Winslow wrote: > > Currently here's how it works: > > The data search page uses an AJAX endpoint in the Django application. > This endpoint internally queries GeoNetwork's CSW using owslib, adds some > additional information from the Django database, and converts all that info > to JSON for easier consumption by JavaScript. > > The maps search page uses a different endpoint, which goes straight to > the Django database. > > The data search page was originally written by a developer without much > experience in CSW/owslib/etc. so it is a pretty basic usage. The maps > search is a little more expert (it uses some wildcards internally, nothing > too fancy). > > The plan is to, at some point in the future, combine the two search pages > (so you have just a single place to search, rather than searching for data > separately from maps.) Currently, the way I see that playing out is that we > would add functionality to sync map metadata to GeoNetwork, and use the > existing "advanced search" page for all searches. Somewhere along the way > we'll also need to address this issue with overly strict queries. > > Fixing the issue should be a relatively simple matter of identifying the > proper parameters to pass to csw.getrecords at > https://github.com/GeoNode/geonode/blob/master/src/GeoNodePy/geonode/maps/views.py#L1351; > given the state of the OWSLib documentation it will probably take a bit of > code reading to sort out what that actually should be. tomkralidis is an > OWSLib developer who shows up on the IRC list from time to time, he might be > able to help if you are interested in providing a patch. > > Hope this helps. > > -- > David Winslow > OpenGeo - http://opengeo.org/ > > On Thu, Feb 3, 2011 at 3:14 AM, Smitha V <[email protected]> wrote: > >> Hi all, >> >> The search/Advanced search option for data in Geonode doesn't show proper >> results. Is there a problem with it? Say for example, "truemarble" is the >> name of the file and i search for "true", it says no files found. Why is it >> so? This does not happen with map search. The way search is performed for >> data and maps are different? How do it rectify the data search option so it >> works properly like map search? Pls help. Need to fix this very urgently. >> >> -- >> Regards >> Smitha V >> MT2009149 >> IIITB >> >> > > -- Regards Smitha V MT2009149 IIITB
