Re: [Gramps-users] How to handle places changing names

[Tony P. <to...@pr...>]

I'm not sure how flexible and accommodating Gramps is in respect of 
place-names. However, the approach that most people adopt is generally 
unworkable in the long term.

There's a write-up of this issue that you might find interesting at: 
http://parallax-viewpoint.blogspot.com/2013/08/a-place-for-everything.html.

    Tony Proctor

----- Original Message ----- 
From: "paul womack" <pw...@pa...>
To: <gra...@li...>
Sent: Tuesday, October 08, 2013 8:42 AM
Subject: Re: [Gramps-users] How to handle places changing names


> Pat Clark wrote:
>> I would keep the original name and then add an event note to the birth, 
>> listing the new(er) names and dates of change.
>>
>> And using the using the places editor add a note about the name changes.
>>
>> This is just my way, others will have a different method. Gramps lets us 
>> do things like this however we want.
>
> I often notice people claiming claiming Gramps lets you store
> information however you choose.
>
> This is true, but only for *storing* data,
>
> In practice, if you wish your data to "play nice"
> with the built in Gramps navigation, searching, and reporting
> tools, your choices must be reasonably constrained
> by context.
>
> To be clear, I think this is perfectly reasonable,
> and is one of the reasons I keep asking for a guide
> to "normal practise".
>
>  BugBear
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most 
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
> _______________________________________________
> Gramps-users mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-users