Family Historian User Group

I'm sure our more specialist contributors are well aware of this, but it was only recently that I picked up that current Edge is a completely different product to the one launched back in 2015. Legacy Edge was much more of an updated IE, but "new" Edge is based on the same open source core technolog...

Clear thanks. I’ll pm you with the url changes when I submit for review.

I’m getting on with my draft, but a couple of questions on process from a newbie author. As I’m creating a new page to replace two existing ones, it will have a new url. It probably makes sense to create new versions of linked pages with the url and associated descriptive text tweaked accordingly, a...

OK, I was trying to get working across 2 PCs onto the front page, as it is a FAQ, but I’ll draft my bit and let’s see how it looks then.

OK, I'll work on that this week. One suggestion before I start - synchronizing FH across two computers comes up quite often on this forum, but the existing KB material is not that easy to find unless you know exactly what you are looking for. It's a bit of lots of different things, backup, cloud sto...

Since we had this discussion, I've been operating with the master copies of folders such as Plugins, Queries, etc. in a dedicated FH folder in my OneDrive cloud storage. On each PC running FH (one on FH7, one on FH6, and one still with the FH7 beta), I have set up links using the mklink command. Thi...

Version 1.01 with a corrected selection routine is attached.
An overview of Ancestry synchronization via RootsMagic has now been published on the Knowledge Base, and this will always link to the latest version of the plugin.

Ok thanks. I can see good reason not to run a second unofficial store. There have been a number of threads discussing this process over the past couple of years. Inevitably, discussion wanders around a little, so the danger is that they confuse readers rather than clarifying. I think the best option...

I’ve finished drafting a piece for the KB on syncing with Ancestry in a way that maintains your hint history, but what’s the preferred method for distributing the custom plugin that is part of the process? It’s probably not appropriate for the main plugin store (not least because it describes using ...

It annoyed me initially, as it's displayed for significantly longer in FH7 than for FH6 on the same PC, but I've learnt to live with it. Disabling it requires additional software, which is something I don't like doing unless it's absolutely necessary.

I used a Linux box plugged into gigabit ethernet as my common server, then just went around every system I could (Windows box, ancient laptop, NUC, various generation of Raspberry Pi), wired, wireless next to access point, wireless other end of house, etc. It gave an excellent overview of how everyt...

If you can set up two separate computers (which can be any OS) on your network, iPerf3 is an excellent tool for benchmarking the network speed. Just run it on each end, one in client mode, the other as server. The figures it gives you are well above real world file transfer speeds, but represent the...

I was assuming that Simon ran his benchmark without compressing. Even so, that's fairly pedestrian network performance, so presumably a wi-fi connection? If you can run it wired, it could be a factor of 10 quicker if it is gigabit all the way through. I've just tested with a similar size folder (tot...

Sorry about that - fixed now. There is a subtle typo in line 344 of the plugin script, where "Min = M" should be "min = M". This resulted in it ignoring the minutes part of the update time, so recent changes were not listed. The short term workaround is to just select any other slightly older file t...

Just a thought - remember that individuals where either the Living or Private flags are set are neither exported nor listed.

David, I read those timestamps as you recreated your master file and imported into RM. Then changed a record, created an update file, and imported that. All the routine does is read the date/time stamp of the file you select, and show records updated since then. So selecting your master should show ...

In an ideal world, every app would support _UID as a unique personal identifier (so essentially a universal primary key for the database of individuals), so all these imperfect merges and syncs would be consigned to history. One parameter does it all. Meanwhile, back in the real world, we have to ma...

The danger here is that we end up muddling different issues - RM manages merging an import into a database perfectly if _UID is available for the import (but merging is only additive, not update), but doesn't handle the comparison between databases correctly, even if _UID is consistent across them.

Poor wording - I know that they are retained as undefined. What FH doesn’t do is generate its own or have a specific field for them. The KB article seems to just refer to them as local to particular apps, and makes no mention of their potential to unambiguously identify individuals across different ...

As you are discovering David, the RM file comparison is probably the weak link in this process. There are two problems that you are likely to encounter. The first is what you are seeing, that there are a large number of records shown as not matching that are in fact identical. The pragmatic fix for ...

Two reasons - the legal tradition is to use phrasing that is unambiguous and does not require punctuation for clarity. Secondly, it avoids any problems with changing the meaning of a sentence by inserting punctuation after it is written.

Yes, I was initially thinking of a very simple plugin to handle duplication of any common individuals or lumped sources, but by the time I got back from our lockdown permitted dog walk exercise in the sunshine, I’d decided it would be quicker and easier just to delete duplicate individuals (only 3) ...

I don't necessarily agree that it is bad to split trees. That should be a case by case decision, and there may well be good reason to do just that. I have separate trees for myself and my wife, as we were born and grew up hundreds of miles apart. There is no credible risk that they overlap in the ti...

David, glad it’s useful. The early part of the Procedures document in this thread will form the basis of what goes into the KB. I think the best thing to do will be to make a limited number of changes to existing entries in your FH database, and see if you can work through the process. If that goes ...

Mike, mostly that, and also how the retrievals treat undated facts and when the CENS to RESI conversion is done. Order in the GEDCOM file is largely irrelevant, so I just set up whichever method is easier to code in the two languages. Shosh, agree. I don’t see LuaSQL coming to FH7 anytime soon, so I...