Louis Kessler’s Behold Blog     The Behold User Forum

You're probably right that FTB's database is simpler than RM's, and maybe citation elements are not a good idea for Behold anyway, because they don't look natural in an editable everything report, and only make things more complicated for your intended audience. Formatted citations actually work pretty well if ...

Hi Louis, It's true that I don't like EE, because it's too much work to translate to all languages that we support with Gramps, but I assume that your main audience is in English speaking countries, for which it can work very well. And if EE support benefits your audience, it's good for Behold too, isn't it? I ...

Hi Louis, SQLite is a good choice, My Heritage is not. I have a subscription to their data plan, and found that for Europe, most of their records come from FamilySearch, where they can be accessed for free, and for the English speaking countries, Ancestry and FindMyPast have better data, which can both be ...

Note that SQLite files in Gramps 5.0 will have binary data too. That is because many primary objects are not normalized. The person object for instance has all name parts and alternative names embedded as lists, which are saved in blobs corresponding with the relevant Python objects. See ...

I ran a quick test today, and didn't see any encryption in My Heritage Family Tree Builder 8, build 8260. When I found that I couldn't open the database with SQLiteman for Windows, I copied it to the Linux host that my Windows 10 session is running on (in VirtualBox), and found that the Linux versions of ...

Louis, Interesting idea, which suggests that you think about a sort of versioning in the data layer. Is that what you mean? Preserving the data as it was before a change looks like versioning to me, because there is a chance that the process needs to be repeated when another application not supporting the ...

Louis, I'm with arb, because I don't think the issues are solvable, except when unprocessed objects are completely isolated from the ones that are edited. You mention the extreme example of a program that doesn't process sources, and I that's a perfect illustration. When you have a tree where for example an ...

Louis, That's right. You can take elements from A2A, or Dublin Core, whatever you like, but things can get easily out of hand if you take too many. When you need more than a dozen, I think something's wrong. Enno

Louis, yes, it can be done, but I prefer for Film: 1234567, Frame: 344, Line: 28 to appear in separate GEDCOM tags, like FILM, PAGE, and LINE, because that makes things less dependent on language, and more straight-forward to parse, IMO. Sources referencing other sources with a similar construct to how ...

Louis, I call it realism. The APIs that I see now serve a vertical market, where data exchange is centralized and controlled by the big companies and FamilySearch, and where, interestingly, when it comes to handling evidence, FamilySearch does a much better job than its commercial partners, as you can read in ...