Re: [Gramps-devel] 1.1 database issues

[Alex R. <sh...@al...>]

Don,

On Thu, Feb 12, 2004 at 11:32:06AM -0700, Don Allingham wrote:
>   1. Should events be "shared" in the same way that sources and media
>      objects are? In other words, should we associate more than one
>      person to an event? If we do this, how do we manage it in the
>      interface? This could give a lot of power, but could make the
>      interface more complex.

Regardless of how to handle this in an optimal way for the user, and=20
regardless of the database table setup, what is the purpose of sharing
the events?=20

The event is something unique: something that happend once to one person.=
=20
If similar event (e.g. graduation) happened to another person, chances
are that it's not the exact same event.=20

Marriage, divorce, etc. are shared events, but they apply to the
relationship and not each person independently, so in a way it is a single
event and not the two events that need to be shared.=20

There are also mass graves, these would be a common event of burial for=20
hundreds or so people, but this is hardly an object of a genealogical=20
research.=20

So, how is sharing the events good or useful in real practice?
I guess I'm missing something obvious again, but please enlighten me :-)

>   2. Similarly, should addresses be shared?

The addresses could be shared I guess, which probably makes them the more
detailed place objects, right?

>   3. Should the primary view be switched from the Person View to Family
>      View? If the view most people work in is the FamilyView, then this
>      makes sense.

Personally, I like People View, since it's showing more people at one time.
I do use Family View, but would like to keep People View primary.

Just my two cents,
Alex

--=20
Alexander Roitman   http://ebner.neuroscience.umn.edu/people/alex.html
Dept. of Neuroscience, Lions Research Building
2001 6th Street SE, Minneapolis, MN  55455
Tel (612) 625-7566   FAX (612) 626-9201