Difference between revisions of "GEPS 035: Attach family events to individuals"

From Gramps
Jump to: navigation, search
(Created)
 
(Advantages)
Line 14: Line 14:
  
 
* Information related to the bride and groom could be stored in event reference attributes in a more consistent manner.
 
* Information related to the bride and groom could be stored in event reference attributes in a more consistent manner.
 +
 +
As it currently stands, Gramps' recommended practice is to associate marriage "Events" with Family's as opposed to individuals for obvious reasons. However, a valid case can be made for also associating the marriage "Event" with the bride and groom as individuals as there is important information that is best stored and reflected that way too.
 +
 +
From an aesthetic standpoint on the GUI, it also makes sense when viewing individual details to see the marriage within the context of the other individual life events. It is redundant (and less tidy) to see the marriage event listed again a second time underneath on the same page, associated with the Family events. This not only applies to the marriage "Event," but also to Divorce "Events" for which the same can be said.
 +
 +
This is less of a problem to Witnesses to marriage events, as in such cases the marriage only appears within the context of the Witnesses individual timeline. Unless of course they are also part of the Family at issue, and hence the Event will also appear twice which is equally redundant.
  
 
== Problems ==
 
== Problems ==

Revision as of 20:48, 24 June 2014

Purpose

The purpose of this GEPS is to investigate recording family events against individuals.

Options

  • Record family events against individuals instead of families.

Primary or Bride/Groom roles?

  • Record family events against individuals in addition to families.

Advantages

  • Information related to the bride and groom could be stored in event reference attributes in a more consistent manner.

As it currently stands, Gramps' recommended practice is to associate marriage "Events" with Family's as opposed to individuals for obvious reasons. However, a valid case can be made for also associating the marriage "Event" with the bride and groom as individuals as there is important information that is best stored and reflected that way too.

From an aesthetic standpoint on the GUI, it also makes sense when viewing individual details to see the marriage within the context of the other individual life events. It is redundant (and less tidy) to see the marriage event listed again a second time underneath on the same page, associated with the Family events. This not only applies to the marriage "Event," but also to Divorce "Events" for which the same can be said.

This is less of a problem to Witnesses to marriage events, as in such cases the marriage only appears within the context of the Witnesses individual timeline. Unless of course they are also part of the Family at issue, and hence the Event will also appear twice which is equally redundant.

Problems

  • Family events should still be used in the GEDCOM export.