From: Nick H. <ni...@gr...> - 2015-01-26 21:12:31
|
On 26/01/15 20:50, Enno Borgsteede wrote: >> On 25/01/15 20:39, Enno Borgsteede wrote: >>> >>Not having much experience with 4.x, I'd say that name, type and code >>> >>are enough, but this brings me to the question where the phone number >>> >>goes during conversion. Can you tell? >> >The phone number gets put into the code field. > With every place having a code field, what type is it converted to? I > mean, suppose I have a location with a ZIP code and a phone number, and > nothing else, what do I get after conversion? The code would contain the ZIP code and phone number concatenated. The place type would be set to "Unknown". >> >Searching places by gramps id, name, type and code is very easy. I have >> >already written a rule for this. > OK, I see no title mentioned here, but no sign that it will completely > disappear or be generated either. What about that? I could easily add a title field in the filter. >>> >>As an extension, it might be nice to expand the filter so that it can >>> >>find words in different levels of a hierarchy, so that I can enter say a >>> >>street name and city, and have it match all parts of the location tree >>> >>where both apply. Ideally, this should work without specifying types in >>> >>the search itself. >> >The existing filter sidebar actually searches locations created from the >> >hierarchy. > I assume that it will use the old types then, like street, locality, > city, etc. What about new types, or user defined ones? That is why bug #7860 was opened. >> >If someone comes up with a good user interface design, them I'm happy to >> >code it. > What I'd love to see is maybe a bit like Google maps. When you type a > single name, maybe even separate words like "nieuwe kerk" or "Noord > Holland", it will find places with a matching name, on any level, and > when you type a comma separated list, like "nieuwe kerk, Amsterdam" you > will find any occurrence of "nieuwe kerk" embedded by "Amsterdam" > regardless of the number of levels between them. > You could do this with a regular expression search on the title field. Nick. |