From: Joachim B. <ma...@jo...> - 2007-02-28 11:23:36
|
Hi, Am Mittwoch, den 28.02.2007, 12:15 +0100 schrieb Martin Hawlisch: > Hi, >=20 > Von: Joachim Breitner <ma...@jo...> > > Places change names during the times, and therefore Gramps has an > > =E2=80=9Calternative place name=E2=80=9D field. But events still refer = to the place as > > a > > whole, which is not correct it seems: Events should contain the place > > name that was relevant at that time. >=20 > We could achieve that with one small addition: Adding a date field to the= locations. So historical place names could then be entered as alternate l= ocations having the timespan given. Reports could then choose the alternate= name that matches the date of the event and optionally print out the curre= nt name. Yupp, that=E2=80=99s what I have in mind :-) > > Another idea that might be interesting for research might be an =E2=80= =9Cis > > included in=E2=80=9D attribute for places. E.g. the place =E2=80=9CPari= s=E2=80=9D is > > included in > > =E2=80=9CFrance=E2=80=9D (which I use for events where I don=E2=80=99t = know where in France > > it > > happened), and when searching for events in =E2=80=9CFrance=E2=80=9D I = might > > (optionally) also find all events in =E2=80=9CParis=E2=80=9D. Just an i= dea, it might > > be > > a bad one. >=20 > What I would like to see here is a hierachy of place objects so that they= can be organized as a tree. This is what for example GeneWeb does. It sounds good, the questions is whether this is overkill for Gramps (after all, it is (not yet) a GIS :-)) and it=E2=80=99s users (some of whom might not care about that), or whether it is desirable. I=E2=80=99m not sur= e myself about his point :-) Greetings, Joachim --=20 Joachim Breitner e-Mail: ma...@jo... Homepage: http://www.joachim-breitner.de ICQ#: 74513189 |