RE: [Gramps-devel] 1.1 database issues

[Eric N. <en...@at...>]

> Yes, but it also directly affects the interface and how the user 
> interacts with it. Its not that difficult to handle in the DB 
> (obviously, since we are already doing it with sources and media 
> objects). The difficult thing is how to present it to the user.
> 
> How do they select an existing event to associate it with another 
> person? Do we need to keep a list of existing events, like we do with 
> sources? This list could quickly grow to be so large that it would be 
> next to impossible to find the event you want. And how does the user 
> identify a unique event?  I can easily see 15000 "Census" 
> labeled events.

You could add an "Events" screen, like the sources, media, and places ones.
Also, you could add a Filter to all of these, like the People screen. Then,
you could allow drag and drop of sources, places, media, and events into
various dialogs / screens. You could put a little note in those dialogs that
allowed dropping to state that you can do so. You could filter Events on
event type, place, date ranges, people who already have this event, etc.
That would make it easier to find the right event.

There should also probably be some other mechanism, because only having it
available through DnD seems wrong. I guess bringing up an Events Search
dialog with the list and Filter box would work. Filter, select, click OK.

Also, you could have a right-click context menu in the People list that
allowed adding of events, adding of attributes, adding of addresses, adding
of notes, and adding of media. With multiple selection, this would allow
adding the same event, attribute, address, note, or media to several people
at once, saving a lot of work.

Just some thoughts,
Eric