What do you do, when the Census Record has people listed, that may not be family?
This is a 1940 U.S. Federal Census Record, where Raymond Lane and Donald Dutton are both listed in the Household. Since this is a 1940 Census Record which indicates that they both are Hired Hands.
I have spend a couple of days thinking and seeing if it is important to capture this information. That is, add these two people to the database. So, I played around with this to see if there was any benefit.
When I enter a Census Record, I Copy what Ancestry provides in the Transcription and Paste it into the Residence Fact NOTES.
You will notice, that these two "extra" people are in Bold. That is the indication to me, that I have entered them into my database, as Unrelated People. The Data Error Report will show them with that they have No Spouse, No Children, No Parents. I can deal with that.
But, what about later, I find that person again, in another record. I wanted to be able to see, that in a Census Record, there were in a Census Record, but NOT related to the Head of Household. So, I created a Fact called "How Related", where I enter the Census Year, Head of Household, and what the relationship is. Here is what Donald looks like, with the Data Error Report and the How Related Facts appear.
He is unrelated, and will appear in the Data Error Report, but when I run that report, I filter OUT everyone who has a Data Error Report Fact. Meaning, I KNOW about that error.
Why the Extra Work?
I found this one person, Relation to Head of Household as Boarder. A throw-away, right ? Wrong.
As it turns out, the Head of Household would become his Mother In Law.
Here she is in the 1900, 1920, 1930, and 1940 Census (haven't gotten to the 1910 census yet)
1900 she is Head of household where I found my person as a boarder. 1920, 1930, and 1940, she is the Mother-in-Law to the Head of Household. (don't jump to conclusions please).
Those are the Residence facts as recorded, but look at the How Related Fact looks.
The 1940 Census record shows that she had moved into another Daughter's home. Because the 1940 has the reference to 1935, showing Same House, I can now pin point as to WHEN show moved from on daughter's house to another, and in a different state.
My records indicate that the "mother in law" was widowed about 1911. I have not yet found a reason why she might have moved back to Pennsylvania, only that the "son in law" and her daughter had 6 children in the 1920 Census and the second daughter, the one in Philadelphia, only had 1 daughter.
I have added this to my new Best Practices: Add seemingly Unrelated Individuals to the Database.
The secret to this is the Bolding of the Name, in the Residence Fact Note, when you Add that "Unrelated" person to the database.
____________________________________________________________
Copyright © 2019 by Cousin Russ
These are notes from a Family Tree Maker User. With FTM2017 and FTM2019 the blog posts will apply to both the PC and the Mac Versions of the programs. Any differences will be noted
Showing posts with label Data_Error_Report. Show all posts
Showing posts with label Data_Error_Report. Show all posts
Friday, November 29, 2019
Sunday, July 29, 2018
Managing the Data Error Message Report - Follow up
Spent some time revising how I handle all of my Task List / ToDo List Items. It was a follow up from the process mentioned earlier in this series.
Bottom Line, It's Working
_______________________________________________________________
Copyright © 2018 by H R Worthington
Bottom Line, It's Working
_______________________________________________________________
Copyright © 2018 by H R Worthington
Saturday, July 28, 2018
Managing the Data Error Report - Part 4
Final Post on Managing the Data Error Report
This is really Part 4, not part 5. User Error
Results of the process discussed in the previous 3 videos.
Comments in the Community
https://plus.google.com/u/0/b/104046972028906209620/+FtmuserBlogspot/posts/j1tkQ6wZva6
or on the Blog
[ blog post link ]
_______________________________________________________________
Copyright © 2018 by H R Worthington
_______________________________________________________________
Copyright © 2018 by H R Worthington
Friday, July 27, 2018
Managing the Data Error Report - Part 3
Did some clean up and want to see how the Data Error Report is doing.
Comments in the Community
https://plus.google.com/u/0/b/104046972028906209620/+FtmuserBlogspot/posts/6HSxkvcMHHK
or on the Blog
_______________________________________________________________
Copyright © 2018 by H R Worthington
Comments in the Community
https://plus.google.com/u/0/b/104046972028906209620/+FtmuserBlogspot/posts/6HSxkvcMHHK
or on the Blog
_______________________________________________________________
Copyright © 2018 by H R Worthington
Thursday, July 26, 2018
Managing the Data Error Report - Part 1
Will demonstrate how I now manage the Data Error Report, Part 1
I have figured out a way to Manage the Date Error Report. First, to identify the Potential Errors, Secondly, Give me the ability to SEE that the profile has an Error, Thirdly to Have a ToDo List to work from, by a specific Error Message Group.
I had not been dong a good job of managing these errors at all, until I used the Data Error Report when helping others. (read smaller FILES).
After spending a couple of days, I have 823 Tasks / ToDo Items to work from.
Part 2 will be, so now what. I identified the Errors, found the reason for the Potential Error, Resolve that error in the database, the make sure the Potential Error has been resolved.
I will add a few people to this database, as see if There are NEW Errors. I will also then, clear some of the ones I have identified.
Comments in my Google+ Community
https://plus.google.com/u/0/b/104046972028906209620/+FtmuserBlogspot/posts/dHFHseKFaoX
or on the Blog
http://ftmuser.blogspot.com/2018/07/managing-data-error-report-part-1.html
_______________________________________________________________
Copyright © 2018 by H R Worthington
I have figured out a way to Manage the Date Error Report. First, to identify the Potential Errors, Secondly, Give me the ability to SEE that the profile has an Error, Thirdly to Have a ToDo List to work from, by a specific Error Message Group.
I had not been dong a good job of managing these errors at all, until I used the Data Error Report when helping others. (read smaller FILES).
After spending a couple of days, I have 823 Tasks / ToDo Items to work from.
Part 2 will be, so now what. I identified the Errors, found the reason for the Potential Error, Resolve that error in the database, the make sure the Potential Error has been resolved.
I will add a few people to this database, as see if There are NEW Errors. I will also then, clear some of the ones I have identified.
Comments in my Google+ Community
https://plus.google.com/u/0/b/104046972028906209620/+FtmuserBlogspot/posts/dHFHseKFaoX
or on the Blog
http://ftmuser.blogspot.com/2018/07/managing-data-error-report-part-1.html
_______________________________________________________________
Copyright © 2018 by H R Worthington
Wednesday, November 15, 2017
How to manage a large Marriage Report ?
A FTM2017 (for the Mac) was having difficulty managing a large Marriage Report, where relationships needed to be updated.
_______________________________________________________________
Copyright © 2017 by H R Worthington
_______________________________________________________________
Copyright © 2017 by H R Worthington
Wednesday, November 7, 2012
Consistency Check Reminders
One of the Blogs that I follow is that created by Tamura Jones, Modern Software Experience. Today his blog was on Consistency Check Reminders. I hadn't thought about that as a topic of this blog, but I agree with Tamura on what he wrote. Our genealogy software should provide us with options on this topic, as well as the Back Up mention at the end of the article.
Back Ups:
Family Tree Maker has always provided us with Back Up features. But Tamura went further then having a feature available, but reminders or user options to have the Back Up's performed. FTM2012 does have options for us, plus offers us a Back Up reminder when preparing to perform some tasks within the program.
For example: the Tools, Compact File utility does offer a Back Up window / reminder before the compacting of the file is performed. Going to the Tools menu and selecting Compact File, this window will open.
Placing the cursor in that box will start the back up process. WE, the user, should take advantage of that.
We also have options on WHERE to put that back up. The Default is in the SAME folder where the Family File is located. Usually in My Documents, under Family Tree Maker. I do NOT put my Back Ups on the SAME Hard Drive where my Family File is located.
I put my Back Up's in a Custom Directory, on an External Drive. (my "J" drive)
We also have options in what we want to include in the Back Up. I always Back Up every thing. I am NOT concerned about disk space. I want to ensure that I can recover any problem with the file quickly and easily.
OH, I also run a Restore from Back Up, once a month, to make sure that the Back Up works.
If you look at the filename of the Back Up (FTMB), you will see that it included the DATE of the Back Up. It makes it very easy to see the most recent file to restore.
There are other operations, that may impact the entire file, where the Back Option is offered. I take advantage of that when offered.
Taking Tamura's statements to heart, FTM2012 also provides us with the Option to Back Up the file automatically, when we close the file, without actually having to do any mouse clicks. That option is in the Tools, Options menu, General Tab.
Putting a check mark in that box, which is the default setting, will cause the program to create a back up of the family file. Using the Automatic Back Up feature, will put a Back Up in the SAME folder as the family file and it will NOT include images. So, the size of this back up will be smaller the the Back Up mentioned earlier.
Consistency
The major thrust of Tamura's article, by my reading, was our ability to make our data consistent.
FTM2012 provide two versions or help in this area. 1) during Data Entry, and 2) a report, in this case the Data Error Report.
The Tools, Options menu has a Warnings Tab.
We have options on what data we want to have a Warning Screen appear, or not appear.
IF I enter a 2 digit year, I will be warned to enter a 4 digit year.
For example: I entered 06/06/12 into the Date field. There is a Warning ICON on the Right of the Date field. It took my 12 to mean 12 AD, instead of 2012.
The warning says "Error: The data you entered has an ambiguous year" message.
Below the previous Waring screen are three more options:
There is a Data Entry Report in the Publish Workspace.
The Person Reports and select the Data Error Report. Once the report is generating the Items to Include where the below window will open.
We have plenty of options of what we want in the report. I use this report frequently, but normally focus on certain bits of information at a time. For example, the Children being out of order.
So, in my mind, we have the proactive Warning messages during data entry, then a report to work from.
Place Name Consistency
This has always been a concern of mine. However, until FTM2012 (704), the struggle has been around Historical Place Names. That update has resolved that for me. I can visually see my "current" Place Names and the Historical Place Names at a glance.
For example: All Hallows Parish, is a historical place name, while the All Hallows Church Cemetery is in the town of Birdsville. The Cemeteries and the Plantation are in Annapolis, Anne Arundel County, Maryland.
The ICON with the Check Mark, is the visual indication that these place names have yet to be resolved. In each of these cases, I am researching what the place name should be. Upper Burlington County, New Jersey, doesn't currently exist. So, I need to view the DATES of the events that took place in Upper Burlington County, New Jersey to see if it is a historical name based on that time frame.
If I understand the trust of Tamura's article, for me, FTM2012 offers me the features we described in his article.
_______________________________________________________________
Copyright © 2012 by H R Worthington
Back Ups:
Family Tree Maker has always provided us with Back Up features. But Tamura went further then having a feature available, but reminders or user options to have the Back Up's performed. FTM2012 does have options for us, plus offers us a Back Up reminder when preparing to perform some tasks within the program.
For example: the Tools, Compact File utility does offer a Back Up window / reminder before the compacting of the file is performed. Going to the Tools menu and selecting Compact File, this window will open.
Placing the cursor in that box will start the back up process. WE, the user, should take advantage of that.
We also have options on WHERE to put that back up. The Default is in the SAME folder where the Family File is located. Usually in My Documents, under Family Tree Maker. I do NOT put my Back Ups on the SAME Hard Drive where my Family File is located.
I put my Back Up's in a Custom Directory, on an External Drive. (my "J" drive)
We also have options in what we want to include in the Back Up. I always Back Up every thing. I am NOT concerned about disk space. I want to ensure that I can recover any problem with the file quickly and easily.
OH, I also run a Restore from Back Up, once a month, to make sure that the Back Up works.
If you look at the filename of the Back Up (FTMB), you will see that it included the DATE of the Back Up. It makes it very easy to see the most recent file to restore.
There are other operations, that may impact the entire file, where the Back Option is offered. I take advantage of that when offered.
Taking Tamura's statements to heart, FTM2012 also provides us with the Option to Back Up the file automatically, when we close the file, without actually having to do any mouse clicks. That option is in the Tools, Options menu, General Tab.
Putting a check mark in that box, which is the default setting, will cause the program to create a back up of the family file. Using the Automatic Back Up feature, will put a Back Up in the SAME folder as the family file and it will NOT include images. So, the size of this back up will be smaller the the Back Up mentioned earlier.
Consistency
The major thrust of Tamura's article, by my reading, was our ability to make our data consistent.
FTM2012 provide two versions or help in this area. 1) during Data Entry, and 2) a report, in this case the Data Error Report.
The Tools, Options menu has a Warnings Tab.
We have options on what data we want to have a Warning Screen appear, or not appear.
- Double Dates
- Title in Name fact
- One or two digit years
- Text in quotes (nickname) in the name fact
- Copy media files to media folder
- Auto populate Smart Stories
IF I enter a 2 digit year, I will be warned to enter a 4 digit year.
For example: I entered 06/06/12 into the Date field. There is a Warning ICON on the Right of the Date field. It took my 12 to mean 12 AD, instead of 2012.
The warning says "Error: The data you entered has an ambiguous year" message.
Below the previous Waring screen are three more options:
- Show alerts for unlikely birth, death and marriage dates
- Show unrecognized place name indicators
- Show informational alerts (i.e., changed name, changed home person...)
There is a Data Entry Report in the Publish Workspace.
The Person Reports and select the Data Error Report. Once the report is generating the Items to Include where the below window will open.
We have plenty of options of what we want in the report. I use this report frequently, but normally focus on certain bits of information at a time. For example, the Children being out of order.
So, in my mind, we have the proactive Warning messages during data entry, then a report to work from.
Place Name Consistency
This has always been a concern of mine. However, until FTM2012 (704), the struggle has been around Historical Place Names. That update has resolved that for me. I can visually see my "current" Place Names and the Historical Place Names at a glance.
For example: All Hallows Parish, is a historical place name, while the All Hallows Church Cemetery is in the town of Birdsville. The Cemeteries and the Plantation are in Annapolis, Anne Arundel County, Maryland.
The ICON with the Check Mark, is the visual indication that these place names have yet to be resolved. In each of these cases, I am researching what the place name should be. Upper Burlington County, New Jersey, doesn't currently exist. So, I need to view the DATES of the events that took place in Upper Burlington County, New Jersey to see if it is a historical name based on that time frame.
If I understand the trust of Tamura's article, for me, FTM2012 offers me the features we described in his article.
_______________________________________________________________
Copyright © 2012 by H R Worthington
Subscribe to:
Posts (Atom)













