Opened 9 years ago

Closed 9 years ago

Last modified 6 years ago

#1221 closed improve feature (fixed)

Find members feature needs alternate name

Reported by: jeanyves Owned by:
Priority: major Milestone: Legacy Resolved
Component: BW Search Keywords: geo
Cc: philipp

Description

I found out a mysterious problem with Find member, when I was seeking for Barcelona the place was found but not the member. Peter tried it and found the member.

In fact the reason is that because I have browser setup in french, my query was translated by some google app probably from Barcelona to Barcelonne (french name)

I have so changed the Findsearch model to have it looking in alterbates name (where Barcelonne can be found connected to Barcelona).

Alternates name were really very empty, so I uploaded from geonames today in a separated database ("geo") and after I run :

replace into geonames_alternate_names select geo.alternatename.* from geo.alternatename,geonames_cache where geo.alternatename.geonameid=geonames_cache.geonameid

This allowed bearcelonne, Londres, Moscou to exist

Now the point of this ticket: we need to load the values of AlternatesName? for what we have in geonames_cache and to keep them fresh. Apparently it was not the case

Change History (2)

comment:1 Changed 9 years ago by fake51

  • Resolution set to fixed
  • Status changed from new to closed

comment:2 Changed 6 years ago by TimLoal

  • Milestone changed from unassigned to Legacy Resolved
Note: See TracTickets for help on using tickets.