Family Historian User Group

... I did use the Immigration and Emigration fields a long time ago, but became unhappy with them as I felt just arriving somewhere didn't fit my perception of 'immigration' (other's may not care of course). Yes, I think that this is one of those things that a number of us do in different ways. In ...

ColeValleyGirl wrote: ↑

24 Dec 2022 13:05

21072|Inconsistent use of cog-wheel

My own proposal - good job someone remembered roughly where it was.

See also provision of Find In This Note, "hidden" under the cog-wheel menu of the Rich Text Editor, instead of having its own icon on the RT Editor's toolbar. (I am prepared to be told that the toolbar is not accessible to CP's programmers while the cog-wheel is - but if I don't ask...)

The rich text Note editor already has cog Menu > Find in this Note... Ctrl+F to find multiple instances of the same text within one Note, ... IIRC I have suggested somewhere that the cog menu is misused. To me (and maybe others will disagreed), cog menus are for options, and similar, not standard w...

Bear in mind that the warnings are just that - warnings - and the relevant facts may describe "perfectly legitimate" circumstances. (Note my scare-quotes... ;) ) From memory of my personal experience , the majority of my false positive warnings referred to the relative dating of events on a child's ...

... I surmise that you carefully review each online genealogy tree/datasource and manually (aka type) data into your FH file only after convincing yourself that the data is accurate (presumably by validating sources from the online/downloaded data source). ... That's pretty much it, yes. Validating...

Are there any plans to add FamilySearch to the internet data matches besides the two already there, FindmyPast and MyHeritage? Would you be looking for matches to the global megatree (FamilySearch FamilyTree) or to the historical records in FamilySearch (which is much closer to what FMP matching is...

I would seriously question whether it makes sense to download trees as GEDCOMs, load them into your FH database and then identify and merge duplicates. (Or do similar for data from Ancestry trees via RM). If there are "a number of online researchers that have uploaded extensive extensions to my fami...

The report is not intended to be a prototype - it's only my intention to illustrate that something already exists in that area ... The report seems to say that all 14 facts are supported by the Source in its entirety - with no "Where within Source" data - which is indicative of a lumped source. ... ...

... It would seem an almost trivial change to the software to cater for the 'lumper' scenario above and avoid disappointing users. ... Unless I've missed something, I cannot see how allowing citation fields in a bibliography is almost trivial. A bibliography can be run off just by examining the Sou...

So basically, The biography would just contain something like "1920 U.S. Census" instead of " 1920 U.S. Census, Florida, Lee County"? If your source-record refers to just the 1920 US Census, then yes. It's really only just occurred to me (because I'm a splitter, 98% of the time) that many lumpers w...

We've had a long discussion on this somewhere .... (Given Murphy's Law, it might even have been in the Mailing List). Best guess at the basic reason for the restriction is that if you imagine a source as a physical book, with citations referring to pages within the book, then the bibliography is the...

Future providers of the 1921 England & Wales will unquestionably do a better job because they'll be able to look at the full page to get a better hint on the handwriting. I don't think this is the way transcribers are taught to work - certainly not how I was taught anyway, but that was some time ag...

Mark1834 wrote: ↑

16 Dec 2022 18:21

... I believe that there was an orchestrated campaign by the suffragettes to boycott the census, ...

Wasn't that the 1911, or was there still some disgruntlement given that not every adult woman yet had the vote?

Hm. Interesting. But I'm not sure whether it's "Interesting" interesting or "Interesting Times" interesting... I really have problems with any proposal that leads to CP providing such facts and those being the only ones that use Supplementary Names. The whole (delightful) point about user defined fa...

Yes, I have one that is incorrectly transcribed on nearly all censuses, but there seems to be more on 1921. It will be interesting to see if other "future" providers do a better job. ... Future providers of the 1921 England & Wales will unquestionably do a better job because they'll be able to look...

... The way I have it currently specified I think you would define "Cary Grant" as a time-line name from 1931 (because you want it used from a point on the time-line). Nothing stops you setting NAME.TYPE as "TLN: Screen Name". ... Yes, that starts to make sense to me. That's where the person specif...

... Is it too restrictive to say that Supplementary Names can only be used in association with specific facts? ... Just at the moment I fear that it is too restrictive. I think that I might want to refer to Archibald Leach as Cary Grant from 1931 onwards for all facts, even though that's only a Sup...

davidf wrote: ↑

15 Dec 2022 16:34

...
so we would have NAME[n].TYPE's like "TLN: Deed Poll Name Change" and "SN: Pen Name" ...

Ah - that's OK, I didn't realise that's where you wanted TLN and SN to go...

1. The distinction between Time-Line-Names and Supplementary names sounds good. 2. Not keen on saying that any dated %INDI.NAME[n]% is treated as a "time-line name" because I might want to provide a date for the name "John le Carre", etc... 3. The idea of TLN requesting a Time-Line-Name, etc, seems ...

On reflection, since there is an OTHER value for NAME.TYPE, maybe the proposed logic about not overwriting the Primary name in a report by the current Stage Name, should be removed and replaced with a new custom field that indicates whether this particular name of any type should or should not be al...

... - In designing the implementation care will have to be taken to ensure (via NAME.TYPE?) that if a woman had a birth name, name by adoption, a married name (official sequence of names) and a stage or pen name (professional names), that the later is not used in normal reporting. ... Did I miss wh...

So... Note that Right Click / Paste and Right Click / Paste Unformatted Text must continue as now - in particular Right Click / Paste must always paste formatted if that's what is on the clipboard. ... becomes ... Note that Right Click / Paste and Right Click / Paste Unformatted Text in the Rich Tex...

Thank you for reporting that. I have logged the issue and it will be passed to the developers for evaluation

I didn't expect any other response, of course. Which isn't meant cynically...

tatewise wrote: ↑

14 Dec 2022 11:07

IMO What you have observed is a fault in FH. Have you reported it? It existed in FH V6 too.
...

Just raised as #215505.