bjayinoz wrote: ↑01 Nov 2021 06:14
tatewise wrote: ↑29 Oct 2021 11:38
I tend to agree with you David, so replace the %INDI.CENS[last].DATE% filter with:
Exclude if %INDI.BIRT[1].DATE% was earlier than 1820
Still learning, so this may be missing something.
If you replace the last census date with the suggested birthdate filter, wouldn't that return everyone born after 1820 - not just those in England?
thanks - Brian
Brian
Yes, you are correct - Queries often need refining to do exactly what you want and you usually have to accept a compromise.
However sticking with last census date = 1911 will also return those who completed the 1911 census and then went abroad, but not return those were abroad in 1911 and either returned or migrated in before 1921. It would also give confusing results for anyone who completed a non-GB&I census in 1911!
If you are wanting in this case a "work to list" for the 1921 census, you need to consider how "perfect" you want the list. With an internationally diverse family tree, you are probably right in your suspicion that sticking with last census = 1911 is best.
If you do however have an internationally diverse tree, you probably need some strategy for handling the fact that different subsets fall within the scope of different sources - the 1921 census being a prime example. Creating a query that can reliably exclude those who were not in the country is not easy - as almost by definition without the 1921 census, you don't know who was in the country in 1921!
Those of interest to me who migrated are a very small number - and once migrated they tended not to come back. So for me I keep separate projects for different jurisdictions and manage the fact that migrants can appear in multiple projects. (Some strongly disapprove of multiple projects; FH can handle massive projects - it's me that struggles!)