RootsWeb.com Mailing Lists
Home

Results for list 'bk'

Total: 6/6
    1. [BK] What data to enter for DATE
    2. Barry PYCROFT

    3. Still on Gedcom and VALIDATOR. I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. There is also no [PLAC ] entered for this event. **> What is the proper thing to do? Personally I leave the whole event as unwritten, blank. Others Might write DEAD or UNKNOWN Some might have a Place with no Date. Some receiving programs do not care. If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. Aft, Bef, and Abt are recognised "approximations or guesses". Cir apparently is not a recognised value part for DATE. **> Your thoughts leading to what data to enter will be helpful. Barry P. Barry PYCROFT Christchurch. 8013 New Zealand - - - - - - - - - - - - .

    05/25/2019 09:06:39
    1. [BK] Re: What data to enter for DATE
    2. Jim Dell

    3. BarryI use three (3) question marks for unknown places.For unknown birth or death I use ?/??/19??Guessing at the centuryThat way when I print out a register report and give it to a relative, who is not a genealogist, they know something is missing and might give me some clues where to find the missing information Jim Sent from Yahoo Mail for iPad On Saturday, May 25, 2019, 11:06 PM, Barry PYCROFT <barry@pycroft.co.nz> wrote: Still on Gedcom and VALIDATOR. I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. There is also no [PLAC ] entered for this event. **> What is the proper thing to do? Personally I leave the whole event  as unwritten, blank. Others Might write DEAD or UNKNOWN Some might have a Place with no Date. Some receiving programs do not care.  If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. Aft, Bef, and Abt are recognised  "approximations or guesses". Cir apparently is not a recognised value part for DATE. **> Your thoughts leading to what data to enter will be helpful.     Barry P. Barry PYCROFT    Christchurch.  8013    New Zealand - - - - - - - - - - - - . _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

    05/26/2019 02:55:12
    1. [BK] Re: What data to enter for DATE
    2. Barry PYCROFT

    3. That is good, Jim. It certainly satisfies local & personal application. The Century idea is good,. For that, your reasoning is good. Somehow though, age and Reasonableness calculations get lost. But they do also if blank!! Hi hi. However, I wonder how a remote reader would enjoy the concept? Such as WCBeta? Barry P. -----Original Message----- From: Jim Dell via BK [mailto:bk@rootsweb.com] Sent: Sunday, 26 May 2019 8:55 PM To: barry@pycroft.co.nz; bk@rootsweb.com Cc: Jim Dell <dellji@yahoo.com> Subject: [BK] Re: What data to enter for DATE BarryI use three (3) question marks for unknown places.For unknown birth or death I use ?/??/19??Guessing at the centuryThat way when I print out a register report and give it to a relative, who is not a genealogist, they know something is missing and might give me some clues where to find the missing information Jim Sent from Yahoo Mail for iPad On Saturday, May 25, 2019, 11:06 PM, Barry PYCROFT <barry@pycroft.co.nz> wrote: Still on Gedcom and VALIDATOR. I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. There is also no [PLAC ] entered for this event. **> What is the proper thing to do? Personally I leave the whole event as unwritten, blank. Others Might write DEAD or UNKNOWN Some might have a Place with no Date. Some receiving programs do not care. If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. Aft, Bef, and Abt are recognised "approximations or guesses". Cir apparently is not a recognised value part for DATE. **> Your thoughts leading to what data to enter will be helpful. Barry P. Barry PYCROFT Christchurch. 8013 New Zealand - - - - - - - - - - - - . _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

    05/26/2019 04:55:21
    1. [BK] Re: What data to enter for DATE
    2. Jim Dell

    3. Barry Right now WCBeta is down for maintence;-) Jim -----Original Message----- From: Barry PYCROFT <barry@pycroft.co.nz> Sent: Sunday, May 26, 2019 6:55 AM To: bk@rootsweb.com Subject: [BK] Re: What data to enter for DATE That is good, Jim. It certainly satisfies local & personal application. The Century idea is good,. For that, your reasoning is good. Somehow though, age and Reasonableness calculations get lost. But they do also if blank!! Hi hi. However, I wonder how a remote reader would enjoy the concept? Such as WCBeta? Barry P. -----Original Message----- From: Jim Dell via BK [mailto:bk@rootsweb.com] Sent: Sunday, 26 May 2019 8:55 PM To: barry@pycroft.co.nz; bk@rootsweb.com Cc: Jim Dell <dellji@yahoo.com> Subject: [BK] Re: What data to enter for DATE BarryI use three (3) question marks for unknown places.For unknown birth or death I use ?/??/19??Guessing at the centuryThat way when I print out a register report and give it to a relative, who is not a genealogist, they know something is missing and might give me some clues where to find the missing information Jim Sent from Yahoo Mail for iPad On Saturday, May 25, 2019, 11:06 PM, Barry PYCROFT <barry@pycroft.co.nz> wrote: Still on Gedcom and VALIDATOR. I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. There is also no [PLAC ] entered for this event. **> What is the proper thing to do? Personally I leave the whole event as unwritten, blank. Others Might write DEAD or UNKNOWN Some might have a Place with no Date. Some receiving programs do not care. If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. Aft, Bef, and Abt are recognised "approximations or guesses". Cir apparently is not a recognised value part for DATE. **> Your thoughts leading to what data to enter will be helpful. Barry P. Barry PYCROFT Christchurch. 8013 New Zealand - - - - - - - - - - - - . _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

    05/26/2019 05:34:14
    1. [BK] Re: What data to enter for DATE
    2. Diedrich Hesmer

    3. Hi Barry, Jim et. al. you might have a look to the link https://wiki-en.genealogy.net/Category:GEDCOM-Tag and on that page go to DATE. This is the english version of the results of a working group of 24 german genealogy programmers containing the definitions of GEDCOM standard 5.5.1 and the agreements reached in case of questionable items of the 5.5.1 for most of the GEDCOM tags. Our goal was to # Improve communication between Genealogy programs using GEDCOM files # Reduce loss of data during export/import of GEDCOM files # Common understanding and interpretation of the GEDCOM standard # Agree to a common solution to improve the user satisfaction # By obtaining the uniqueness of every program # Use the GEDCOM standard draft 5.5.1 as base This might help, even in your case. Have a look at the DATE page to item 3.6 Date Phrase: The text must be enclosed in round brackets, e.g. using Jims example: 2 DATE (?/??/19??) would be according to the specification. Usually the exporting program should add these 2 brackets. The only question would be, does a reading program understand the standard correctly. best regards Diedrich (Hesmer) Am 26.05.19 um 12:55 schrieb Barry PYCROFT: > That is good, Jim. > It certainly satisfies local & personal application. The Century idea is good,. For that, your reasoning is good. > Somehow though, age and Reasonableness calculations get lost. But they do also if blank!! Hi hi. > > However, I wonder how a remote reader would enjoy the concept? Such as WCBeta? > > Barry P. > > -----Original Message----- > From: Jim Dell via BK [mailto:bk@rootsweb.com] > Sent: Sunday, 26 May 2019 8:55 PM > To: barry@pycroft.co.nz; bk@rootsweb.com > Cc: Jim Dell <dellji@yahoo.com> > Subject: [BK] Re: What data to enter for DATE > > BarryI use three (3) question marks for unknown places.For unknown birth or death I use ?/??/19??Guessing at the centuryThat way when I print out a register report and give it to a relative, who is not a genealogist, they know something is missing and might give me some clues where to find the missing information Jim > > > Sent from Yahoo Mail for iPad > > > On Saturday, May 25, 2019, 11:06 PM, Barry PYCROFT <barry@pycroft.co.nz> wrote: > > Still on Gedcom and VALIDATOR. > > I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. > There is also no [PLAC ] entered for this event. > > **> What is the proper thing to do? > > Personally I leave the whole event as unwritten, blank. > Others Might write DEAD or UNKNOWN > Some might have a Place with no Date. > > Some receiving programs do not care. If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. > > Aft, Bef, and Abt are recognised "approximations or guesses". > Cir apparently is not a recognised value part for DATE. > > **> Your thoughts leading to what data to enter will be helpful. > > Barry P. > > Barry PYCROFT > Christchurch. 8013 > New Zealand > - - - - - - - - - - - - . > > > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community > > > > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community >

    05/26/2019 05:36:27
    1. [BK] Re: What data to enter for DATE
    2. Barry PYCROFT

    3. This just so brilliant, Diedrich Thank you for the link. The information therein is clean, clear & concise. What is needed now is for users to comply! The computers will handle a wide range of people variables, but not 'free-thought' data entry. I will create a STANDARDS note for myself. Obviously that will be the simplest of singular choices. That means my compliance will be assured. Regards Barry P. ---------===========------ -----Original Message----- From: Diedrich Hesmer [mailto:dhesmer@gmx.de] Sent: Sunday, 26 May 2019 11:36 PM To: bk@rootsweb.com Subject: [BK] Re: What data to enter for DATE Hi Barry, Jim et. al. you might have a look to the link https://wiki-en.genealogy.net/Category:GEDCOM-Tag and on that page go to DATE. This is the english version of the results of a working group of 24 german genealogy programmers containing the definitions of GEDCOM standard 5.5.1 and the agreements reached in case of questionable items of the 5.5.1 for most of the GEDCOM tags. Our goal was to # Improve communication between Genealogy programs using GEDCOM files # Reduce loss of data during export/import of GEDCOM files # Common understanding and interpretation of the GEDCOM standard # Agree to a common solution to improve the user satisfaction # By obtaining the uniqueness of every program # Use the GEDCOM standard draft 5.5.1 as base This might help, even in your case. Have a look at the DATE page to item 3.6 Date Phrase: The text must be enclosed in round brackets, e.g. using Jims example: 2 DATE (?/??/19??) would be according to the specification. Usually the exporting program should add these 2 brackets. The only question would be, does a reading program understand the standard correctly. best regards Diedrich (Hesmer) Am 26.05.19 um 12:55 schrieb Barry PYCROFT: > That is good, Jim. > It certainly satisfies local & personal application. The Century idea is good,. For that, your reasoning is good. > Somehow though, age and Reasonableness calculations get lost. But they do also if blank!! Hi hi. > > However, I wonder how a remote reader would enjoy the concept? Such as WCBeta? > > Barry P. > > -----Original Message----- > From: Jim Dell via BK [mailto:bk@rootsweb.com] > Sent: Sunday, 26 May 2019 8:55 PM > To: barry@pycroft.co.nz; bk@rootsweb.com > Cc: Jim Dell <dellji@yahoo.com> > Subject: [BK] Re: What data to enter for DATE > > BarryI use three (3) question marks for unknown places.For unknown > birth or death I use ?/??/19??Guessing at the centuryThat way when I > print out a register report and give it to a relative, who is not a > genealogist, they know something is missing and might give me some > clues where to find the missing information Jim > > > Sent from Yahoo Mail for iPad > > > On Saturday, May 25, 2019, 11:06 PM, Barry PYCROFT <barry@pycroft.co.nz> wrote: > > Still on Gedcom and VALIDATOR. > > I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. > There is also no [PLAC ] entered for this event. > > **> What is the proper thing to do? > > Personally I leave the whole event as unwritten, blank. > Others Might write DEAD or UNKNOWN > Some might have a Place with no Date. > > Some receiving programs do not care. If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. > > Aft, Bef, and Abt are recognised "approximations or guesses". > Cir apparently is not a recognised value part for DATE. > > **> Your thoughts leading to what data to enter will be helpful. > > Barry P. > > Barry PYCROFT > Christchurch. 8013 > New Zealand > - - - - - - - - - - - - . > > > > _______________________________________________ > Remember - Use the Archives at > http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe > https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal > RootsWeb community > > > > > _______________________________________________ > Remember - Use the Archives at > http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe > https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal > RootsWeb community > > _______________________________________________ > Remember - Use the Archives at > http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe > https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal > RootsWeb community > _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

    05/26/2019 10:44:43