Menu

Unrecognized GEDCOM Code: CLAW

Help
MetaEd
2009-12-17
2013-05-30
  • MetaEd

    MetaEd - 2009-12-17

    This error message is displayed for some individuals in an existing GEDCOM file.

    The cause seems to be family records of the form:

        0 @Fnnn@ FAM
        1 HUSB @Innn@
        1 WIFE @Innn@
        1 CLAW
        1 CHIL @Innn@

    Having very little background in GEDCOM file internals, I assume this is an attempt to record a marriage type of "common law".

    Two questions.

    First: Can I configure PhpGedView to recognize CLAW in a useful way?

    Second and only peripherally related: What is the appropriate way to record a family which consists of cohabitation and children with no common law marriage? This can arise because the law does not recognize a marriage. For example, one party may be married to a third party, or the parties may be gay in a state that does not recognize gay marriages.

     
  • Greg Roach

    Greg Roach - 2009-12-17

    There is no "official" gedcom tag to identify this, but many applications have standardised on the "unofficial" "_NMR" to indicate "Not Married".

    The most useful part of stating this "non-event", is that it provides a nice mutual link on each individual's page.

    You can add support for this by adding a translation for this in your local/cust language file.  Create a file languages/extra.en.php containing the following:

        <?php
        $factarray='Common Law Marriage';

     
  • Greg Roach

    Greg Roach - 2009-12-17

    Oh, and gedcom standards say that an event needs either a date, a place, or a "Y".  So, unless you have a date/place for your CLAW event, you should have

        1 CLAW Y

     
  • MetaEd

    MetaEd - 2009-12-17

    _Thank you!_

     
  • Anonymous

    Anonymous - 2009-12-18

    Can I add that I believe the correct GEDCOM entry for this would be:

        0 @Fnnn@ FAM
        1 HUSB @Innn@
        1 WIFE @Innn@
        1 MARR
        2 TYPE common law
        1 CHIL @Innn@

    or something similar.

     

Log in to post a comment.