Family Historian User Group

Interestingly, many other tabs in the Records Window have Filters that use the 'contains' strategy rather than 'begins with'. Whilst I can see that you would want "contains" (at least as an option) for picking up: "Mc" and "Mac" - i.e. contains the post Mac/Mc bit "Anna" and "Hannah" and "Marianne"...

Name Filtering Requirement The Name Filter Function in the Records Window and Selection dialogues should be able to handle situations where Names have been miss-slashed or inconsistently slashed (e.g. Compound Surnames, Patronymics and Toponymics). It should be more tolerant of miss-placed or miss-...

I think a wish list item would be good. I've never submitted one as I fear that it would get so few votes that CP might be unlikely to implement it. Bill I think if it is required by a few it should be discussed as a Wish List Request (which is just another sub-forum). Then if it is feasible, I per...

Are we getting to a stage where a Wish List Request is beginning to become relevant (and be exposed to people who are not interested in Patronymics etc.)? The Requirement might be something general along the lines of: Name Filtering The Name Filter Function in the Records Window and Selection dialog...

As I have always understood it, the standard entry format for genealogy is, as you say, to specify the month by using its short form name, rather than just the number. ... As a general point, I would strongly advise against displaying dates in a numerical form because of the potential ambiguity. IM...

... Another option I've thought would be handy rather than an additional box would be a Contains radio button for the first and last name so the filtering would not be limited to just the beginning characters. Bill That (a "contains option" or similar - wildcards?) would be a help when you are not ...

With all the Norwegian and German names I have in my tree, I have long wished there was a filter on the records window that would find whatever you are searching for no matter where in the name it is rather than just the beginning. It could be an additional box so their would be a 'Last Name' box, ...

How would your proposal search for initials M. J. without returning a much longer set of results than necessary? Really useful when working with DNA and an online tree that somebody has helpful 'anonymised'. Well "M._J." (underscore = a space) would match (at first thought): M./J./ - which is proba...

Helen, Can I push you as to why? I've tried to suggest some of the benefits when I originally floated the idea - particularly in circumstances where you are not sure whether a name element has been entered "between the slashes". As for disbenefits, I can understand that such a search would produce a...

So, a lot like Edit > Find with the search restricted to Names? Well that searches across all records (and all name parts?) not just Individual records and the speed and output are different. I am thinking of a change to the input of a Name to filter: Screenshot from 2022-11-10 10-45-15.png Hence p...

I am not 100% sure what you mean, but it is definitely clear that the GEDCOM standard falls short on many fronts. Unfortunately, within FH we are forced to work within these constraints, and so any method to record (and reference and search) this data inherits these constraints. One of the issues t...

You could also point out that if it [Ahnentafel number] did apply to adoptive families then in cases where both the biological family and the adoptive family have been recorded FH would have to assign Ahnentafel numbers to both! So the individual would have a duplicate set of Ahnentafel numbers. Bu...

... Is there mileage in considering whether this issue could be mitigated by being able to filter not just on "Name" but also on "Name Parts"? ... Very possibly - however, we still need to ponder how complex names need to be parcelled up when submitting queries to FMP (say) to find hints. That is a...

For this reason, what I do with my Norwegian ancestors is that I chose a normalized version of any given ancestor and then record additional name entries for every source where it differs from this normalized version. Does my pondering whether filtering of names should be first/surname agnostic off...

Indeed, but I think the certifier has to have treated the deceased for a period of time (i.e. known to them - but could be a long term "deception") - failing that I think it goes to the coroner if the deceased had not been seen by a doctor (any doctor?) within, is it, two weeks of death? What identi...

I think deaths do require a doctor's medical certificate ("the letter") which confirms who died, when and of what, but apart from that ... I have a suspicion that if the birth I am looking for actually happened, it was under a false name and just spotting that in a quarter's worth of birth indices ....

I just use parish registers, GRO and censuses to confirm all my assumptions, as everyone else does. I think most us of do, but where there are "non-paternity events" for instance, they rarely show up in registers GRO censuses etc., particularly if the "father" is unaware of what his partner may hav...

So you have "DNA proof" of all claimed relationships - i.e. that you are genetically descended from that 2'great grand-mother?

What did you do before DNA?

But pedigrees are "claimed" pedigrees. Unlike the kennel club the "genealogist" is rarely there when the mating takes place! But when Ahnentafel Numbers were being developed, surely it was to display the "claimed ancestry" which could be in ignorance or full knowledge of adoptions or non-paternity e...

Again, perversely thinking laterally: Is a table still a "valid transcription" if instead of producing rows of data (e.g. one row per person in a census household) you produce columns of data? With large households you would still have too many columns to avoid awkward word wrapping. But with (Engli...

To help the dynamic process, would it be rational to identify a "preferred split point" on a column boundary? i.e. Rather like the MS Word "Keep with next" and "Keep lines together" paragraph options. Actually, that might be a better concept ~ a "Keep with next" option for each column to ensure suc...

Wouldn't it be better to have this happen dynamically? Often but not always, so the solution needs to be outside AS. Yes, but, ...! No "dynamic" process will get the semantics right and dynamic column breaks will, according to sod's law, happen in the wrong place and split information (e.g. US "whe...

Thinking in a way for which you may not thank me ...! These wide tables are often created by Ancestral Sources (usually census transcriptions). Census information often splits into "groups" of information: - Household relationships - Personal information: age, occupation, employer, (in US) race - Wh...

If the first column contained something meaningful such as a name, your final version is surely to be preferred. There is another option for tables that are "a little bit too wide" which is to put them on a landscape oriented page, with page breaks before and after. You would need to measure the tab...

Ah, Language! it's a curse but where would we be without it? For that last case, he says "add a Shared Note for a couple which nicely adds (a link, I assume) to both spouses" but it is not linked to both spouses' Individual records but is a single link to the Family record. (My emboldening) We need ...