Don't fabricate facts!
Don't fabricate facts!
Place or date unknown LEAVE IT BLANK. or enter as such -
Place assumed by other given facts - enter as eg: <, , Ohio>
- Parents place of KNOWN marriage place
- other siblings KNOWN birthplae
- Place of residence pre Census Records
Date should be left blank or listed as:
- est - estimated
- bef - before
- aft - after
- betw - between
- or if assumed <1899>
- DO NOT LIST a married woman by her husbands SURNAME
- If unknown use a place holder such as [-?-]
- DO NOT LIST a married divroced woman by her exhusbands SURNAME
- Again use a Place holder eg: Jane [-?-] Doe or Jane Doe nee Smith or Jane [-?-] Smith
- If assumed surrname can be entered as such Jane [-?Smith-] Doe or Jane [-?Smith-]
Placing facts not known and doucmented into field names, dates, places generates factual data and many family genealogist take then as GOSPEL FACT when found in GEDCOM's, World Family Tree's and refuse to accept new information or documentation
Many family genealogists over the decades have taken out the assumed markers "<>" for place <, , Ohio> that was generate by many computer programs such as PAF when a GEDCOM was created leaving just the location place as a given fact. and as well as taking the the bef., est, aft, betw out the the date fields.
Use Standard accepted abbreviations
IF IN DOUBT - DO NOT abbreviate - or if you feel that the abbreviation may be taken out of context or misconstruded - -
in using/coping sourcing - do not change abbreviations or spellings to suite yourself. copy it VERBATIM and changing no spellings and it you feel you just must change the information any changes you make should be placed within [...] it indicate the changes made to the original entry.
these are being constantly used as birth dates - this provides a false presentation of data for the birth date -
A christening date can occur as:
- an infant at birth
- an infant shortly after birth when death has occured
- as an infant several days, weeks or months or up to a year after birth has occured
- as a child
- as a young adult
some christening/baptismal records if you can obtain a true abstraction of photo copy of the parish record will give both a birth date and a christening date - ie
Margaret Hardesty Daughter of Thomas Hardesty and Ann his wife was Born Oct. 20 1800 and Baptizd Nov 10 1801 by The Revd Nicholas H. Lane - - - All Hallow's Parish Anne Arundel County, Maryland Resgister 1685-1858 Vestry Proceedings 1761-1844, pg. 166.
DEATH PLACE - SSDI
Ancestry.com is placing "Last Known Residence" or "where last benfit was sent/recieved" at - as the place of death -- THIS IS NOT ALWAYS the PLACE Of DEATH and should be double checked and VERIFIED as to whether the DEATH PLACE entry was generated from the SSDI source!
This quirk in Ancestry.com is leading to a great deal of misinformation and incorrect data being put into databases!!!!
again these are being constantly used as death dates - this provides a false presentation of data for the death date - just maybe if lucky and one can get a true abstaction of the record it might just also state a death date or hint at a death date
The christening/baptismal date and place are constantly being used as the birth date on GENI as is the burial date being given for the death date these dates should be put into the proper sppots since the do exist - when they do not exist in a genealogy program they should be anotated either in the notes or in the birth/death line or place line [which ever will allow correct anotation]
a chrsitening/baptismal date placed within the birth date field should read;
- bp/bap. Nov 10 1801
- Nov 10 1801 - bp/bap.
a burial date if appearing in the death field should read:
- bur. Nov 10 1801
- Nov 10 1801, bur.
will, date is written
are being given as a death date -
Will can be written:
- on the day one dies - in early days
- several days defore one death
- weeks, months even years before one dies
Will, probated or proved
This is could been done:
- on the day of death, but unlikely
- several days after or longer
If lucky - enough the one attesting to to the authenticty of the may state the death date of the testator - ie.
George H. Marquart Will Book 6 pg. 531-2
The Last Will and Testament of George H. Marquart of the Precinct of Mt. Carmel in the county of Wabash and State of Illinois made and published the eighteenth day of September in the year of our Lord One Thousand and nine hundred forty-one....
IN WITNESS WHEREOF, I have hereunto set my hand and seal, the 18th day of September in the year of our Lord One Thousand Nine hundred Forty-one. - George H. Marquart (seal)
State of Indiana Greene County ss} On this 29th day of Aug. 1947 in open court in Greene Curcit [Circuit] Court state of Indiana, Bert Miller a resident of Greene Co., Indiana,.... to the annexed instrument purporting to be the last will and testament of George H. Marquart deceased, late of Greene Co. Indiana, and who departed this life under date of Aug. 18, 1947. ....
When using the will dated - will proven as a death date it should be either fully documented in notes - or well annotated in the date date line or place line (which ever allows it to de done correctly) as:
- between 18 Sep 1941 - 29 Aug 1947
- will dtd 18 Sep 1941 - proved 29 aug. 1947
Thus this proves the correct and accurate time frame of death - I have seen many instances where only one of the above dates has been used as the death date - this provides a false presentation of data for the death date
These were GENEALOGICAL STANDARDS whe the were no place spots for christening/baptism and burial dates - and the should still be adhered to today when doing genealogy either on paper or on computer - Above all since they now most generally have there own spot in computer programs and on paper forms they should be placed in there and not in the brith/death fields as has been occuring.
Death Place per SSDI
Is being stated as the place of death - yes this can occur but in today's society this is not always so today we are a mobile society and we travel around - -
Last Residence: today is - where the last Social Security check was deposited/mailed to:
- The person's place of residence
- The person's postal box
- The person's payee representative address which is not always the same as the benifit person
- The person's direct deposit to a banking insitutation or debit/credit card
- A nursing home facility
- A hospice facility
There is always the possiblity that the person died in a hospital either in a nearby community, several miles away or several hundred or thousand miles away or even while on a trip abroad or across our continential borders in Mexico or canada
when comming from this record if should either be entered as:
- prob - 69130 Cozad, Dawson, Nebraska, United States of America
- 69130 Cozad, Dawson, Nebraska, United States of America - prob
ancestry.com is the biggest culprit of entering it as the place of death with is totaly wrong to do - unless it is a proven fact and supported by a death certificate
Global Replace= - computer genealogy programs
Have you ever wondered where those funny looking place names come from???
Its called Global Search and replace -
One should not use it to clean up files - espescially with state abbriviations such as IN, In. etc. to make then a whole un-abbreviated name as Indiana - even is "case sensitive" is used as people do use full capitalization for place names. This would even apply to the correcting the abbrivation of 'co' for county and "twp' for township/
Doing a global to replace IN or In for full spelling of Indiana will replace the "in" or "IN" in any place name
Thus Washington twp, Greene, Indiana becomes - Washindianagton twp, Greene, Indianadiana
If one does so they then should check every place entery in there data file to make sure that place speelign are all still in proper spelling --
I find it usefully to take out "county" in the place name ot take down the spelling of township to "twp' is space is needed and also USA and United States and I also find it usefull in correcting spelling errors found as they may be compounded throughout the file.
Some early genealology enthusaist decided it shorten the entry of entering dates down to
when no format statement was given the 1st two sets of numbers can be interperted as either
- month-day year
also with the passing of the 1800's and 1900's, if the material bears no dates - assumptions have been made if they years was only added as a tow digit number
This has also lead to transcriptions errors occuring over the many years
Many people even insisted on sending genealogy material in this manner - which had to be guessed at or either sent back and clarification on dates made -
Its easy to fall back into number only format when hand writing data - but one must always remember to write the month out in full or use the first three letters in the month as an abberviation. I know I was guilty of doing this in my early years of genealogy.
BIGGEST ERROR - is blindly accepting a GEDcom without opening it up and seeing what is within
this SHOULD ALWAYS be done no matter what = this is the root of all EVIL - in the genealogy community - sorry.
All l profiles that are 'marked as living' 'unknown' should be deleted out of the newly open file any profiles with a '?" in them should be either also or either evaluated for significant data content and do they warrant enough to keep them - these generate a night mare in the merging process
all profiles - with only a surname attached should be eleted - only profiles with data with in should be kept if no full name is attached = the blank data field can be replaced with "[-?-]' to indicate that it has been evaluated and deemed valuable to retain.
profiles with either a first name or last name if attached to another profiles with full or partial data should be retained filling the missing name area in with "[-?-]'
Go back and make sure you have caught all the 'living', 'unknown' blank no name profiles and delete them -
next go to Marriage lists and review it - making sure you delete every marriage record that is not attached to anyone - or just attached to a child - the latter is a common GEDCOM fluke - in gedcoms the attached spouse but often exported but not the spouses parents if they were data based in.
Now you are ready to merge - be thoughtful, and take out all the "Garbage' such as
- Wft Est. 1823-1912
- deceasedwithin the fields
- possibly even the gedcom generated data which will appear within <> it it sounds or appears to be relatively in accurate - this is based on "known' data also could of been generated most generated data is based on
- marriage date/place
- birth date/ place
- death date place
NOW with this done = you are ready to generate a new very clean gedcom - to import into your personal files
Allot of work YES - worth while doing YES - it makes matching profiles easier - plus you end up with allot less UNWANTED junk profiles - and if you share - you don't share extra hidden junk files -
the effort of opening up a newly acquired gedcom - cleaning up will very well be worth the time involved in doing it - plus it is a real "eye opener' as to how someone really cares about the data they share - and pass on - if its an extra "dirty file' it shows their lack of ability in my mind to preserve the integrity of genealogical data Integrity
this in my mind is a mandatory thing that should be done - if you are planning to upload it up online it programs such as GENI, Ancestry.com etc. as you are only perpetuating someone else's errors and compounding and passing on the misinformation and since it is your gedocm now it reflects back on to you first - then others.
DO NOT RELY on the person sending the gedcom to have spent time cleaning it up before sending it to you.!