LDS dates

2009-11-14
2013-05-30
  • Marlin Allred

    Marlin Allred - 2009-11-14

    Does the date field support LDS date information on the individual page? It seems to be showing blank instead.

     
  • Anonymous - 2009-11-14

    Not sure what you mean by "the date field"  Every event has its own date, and LDS events are no different. It does support them, but how are you entering them?

    Add New Fact at the bottom of the individual page has four LDS options: Baptism (BAPL), Endowment (ENDL), Child Sealing (SLGC), and Confirmation (CONL).

    Do your entries use these TAGS, giving a format in the raw GEDCOM like:

        1 BAPL
        2 DATE 25 JAN 1958

     
  • Marlin Allred

    Marlin Allred - 2009-11-16

    In your example, if I put an LDS date of CHILD, it is displayed as a blank.

     
  • Anonymous - 2009-11-16

    Not quite sure what you mean, but the options are ONLY:

    Baptism (BAPL)

    Endowment (ENDL)

    Child Sealing (SLGC)

    Confirmation (CONL)

     
  • Stephen Arnold

    Stephen Arnold - 2009-11-16

    Marlin  
    The date of CHILD was deprecated in v5.5 from v5.4 (STILLBORN, INFANT, too)).

    You need to review the acceptable entries for DATE, BEF XXX, AFT XXX, ABT XXXX, MM YYYY, DD MM YYYY, YYY, DIED YOUNG, INFANT (< 1), EST, CAL, etc. Review the v5.5 standard for modifiers.

    The change occurred in v5.5 and states "The definition of the date value was refined to include many of the potential ways in which a person may define an imprecise date in a free form text field. Systems which guide users through a date statement should not result in such a precise way of stating an imprecise date. For example, if software was to estimate a marriage date based on an algorithm involving the birth date of the couple's first child, hardly needs to say "EST ABT 1881". "  

    Stephen

     
  • Mark Hattam

    Mark Hattam - 2009-11-16

    The latest GEDCOM **standard** has not deprecated those terms

        http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#AGE_AT_EVENT

        AGE_AT_EVENT: = {Size=1:12}
          ]
        Where :
        > = greater than indicated age
        < = less than indicated age
        y = a label indicating years
        m = a label indicating months
        d = a label indicating days
        YY = number of full years
        MM = number of months
        DDD = number of days
        CHILD = age < 8 years
        INFANT = age < 1 year
        STILLBORN = died just prior, at, or near birth, 0 years

    A number that indicates the age in years, months, and days that the principal was at the time of the associated event. Any labels must come after their corresponding number, for example; 4y 8m 10d.

    Somehow I anticipate the forum software will mangle the layout here, but just follow the link.

    Mark

     
  • Greg Roach

    Greg Roach - 2009-11-16

    PGV *does* support these age qualifiers.

    What we still haven't established is what allredmp is typing into which field.

    Perhaps he is typing "INFANT", etc. into the DATE field, rather than the AGE field?

    Perhaps he could post the raw gedcom for this record?

     
  • Stephen Arnold

    Stephen Arnold - 2009-11-16

    Mark  
    Thanks for that clarification. As I said, it appears he's not using AGE, but rather DATE. 
    Stephen

     
  • Marlin Allred

    Marlin Allred - 2009-11-16

    1 BAPL
    2 DATE CHILD
    1 ENDL
    2 DATE CHILD

     
  • Anonymous - 2009-11-16

    "allredmp"

    Please - a few words of explanation would really help….

    If that is your GEDCOM data, then it is wrong. It needs to be:

        1 BAPL
        2 AGE CHILD
        1 ENDL
        2 AGE CHILD

    BUT, I see that in fact in PGVs interface there is no AGE option, so until that gets fixed, you will need to either:

    a - enter an actual date in the DATE field, or

    b - edit the raw GEDCOM data (you can do that in PGV) to change DATE to AGE.

    The reason, as you may have seen above, is that CHILD is valid as an age, not as a date.

    I will raise a bug report for the missing AGE field. Hopefully it can be included in the next release of PGV.

     
  • Greg Roach

    Greg Roach - 2009-11-16

    The list of events that get an AGE field are DEAT and CENS, as these are events where a persons age is traditionally recorded.

    To get an AGE field on other events, just add them to the list at line ~70 of includes/functions/functions_edit.php.

    kiwi - if you're going to raise a bug-report, please say which events you want changing.

     
  • Laie Techie

    Laie Techie - 2009-11-19

    As I posted on the bug, it looks like the "Status"field on the LDS ordinance screens serve this purpose. The only reason to include both an AGE subtag is if the individual was living at the time and you wish to express their age at that event.

     
  • Greg Roach

    Greg Roach - 2009-11-19

    laie_techie - in the code, there is a list of "non place facts" - presumably facts that should not have a PLAC field.  Over time, it appears that this list has been used for other things.

    Is it correct that some (but not all) of these tags should have a PLAC field?

     
  • Laie Techie

    Laie Techie - 2009-11-19

    fisharebest,

    LDS Baptism (BAPL) and LDS Confirmation (CONL) are likely to have a place associated with them.  The other LDS ordinances are performed in temples, so a PLAC isn't necessary.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks