GenealogicNG news

GenealogicNG is coming along. Not without nits and other bits, however; there always are ….

The first nit is that I’ve not found a good gedcom parser written in Rust. The one I did find barfs json and is built for that sort of data structure, rather than gedcom. There is a more recent, somewhat, fork of it, but the fork is still similar to the original in reading and writing data.

The second nit is that the json parsers need to read in to data structures similar to the source they come from. In this case it’s the GenealogicNG database, so I’d have to code another implementation for the structures I’ve already created.

Either I do the json parser route or continue to figure out the rest of the gedcom parser’s inner workings.

The first bit is that I’ve gotten some data out of the parser and into the glNG.db file. It’s only three pieces, and it’s taken me a couple of weeks to figure out how to do that. Now that I’ve got some of the basic structure of the parser figured out, things should go faster.

The second bit is that I’ve discovered a few typos in the SQL that the database runs. They’ve been fixed.

As an interesting aside, I’ve discovered a product which can help me figure out how the parser works. It’s an AI thingy called Safurai. Safurai is currently in beta, so it’s probably not the best, but I used it to rewrite a few pieces of my code, and they look, and work, better.

Genealogy as a Form of Data Analysis

This paper is loosely based on the Wikipedia article entitled “Data Analysis” and the book Mastering Genealogical Proof.

Genealogists use raw data to accumulate and analyze patterns and trends toward establishing a Genealogical Proof. Evidence in the genealogical community is generally understood as pieces of data that are arranged through collection, sifting, and arranging. Evidence, positive or negative, is acquired through examining and modeling data using generally accepted processes. One such process is to use the computer application Evidentia. Other processes enabling the development of evidence are those used in the legal and forensics professions (e.g., DNA analysis).

Each point of data genealogists use is inspected, cleansed, transformed, and modelled. Most serious genealogists use the Genealogical Proof Standard. While this standard is more qualitative than quantitative, the results are the same, actionable information used to formulate decisions.

The Genealogical Proof Standard follows, simply: Formulating a research question, gathering data sources, considering the information in those sources, formulating evidence from that information, and finally constructing a proof statement. The process is generally iterative since there is no such thing as a final statement of proof in genealogy.

While traditional data analysis is generally thought to be quantitative, there is much similarity to the genealogical research process. The steps in data analysis are analogous to the process used by genealogy professionals. Data analysis begins with a research question, followed by compiling source information, and finally, generating actionable conclusions.

Research Question

Sometimes thought of as a hypothesis, the research question is the beginning of both genealogical research and data analysis. Genealogists formulate a question by asking something such as “Who was Joan Jones’ mother?” Data analysts ask, “How is product A better than product B?” The answers come in basically the same way for both.

Data Collection, Processing, and Cleaning

To answer the research question, both genealogists and data analysts collect, process and classify data relevant to the issue. Almost all data is seen as relevant to analysts, but genealogists often go further, collecting source material relevant not only to the issue, but also surrounding the issue. Data analysts, on the other hand, are more focused on the question itself, locating only data relevant to products A and B.

The difference between traditional and genealogical data analysis is that genealogists have much more fuzzy information to deal with. Items like local and regional history books may include data about their question. Such items are generally not relevant to a data analyst focused on a product research project, unless it involves cultural appropriation, i.e., the Korean car makers’ KIA Tucson vehicle. 😊

Exploratory Analysis

Genealogists often explore different sets of data to glean information and evidence relevant to their questions. Similarly, a traditional data analyst will do the same, focusing more on specific items than general items.

Modelling and Algorithms

There are no “real” algorithms for genealogists to apply to their data findings. There is, however, a Genealogical Data Model, which was constructed to help genealogists apply their data to real-world projects. The Genealogical Data Model was originally constructed to be a basis for software, but since it was completed, no software has used the GDM (except for The Master Genealogist, which used large parts of it).

Data Products and Communications

Genealogists use a proof model to present data and their formulation of the evidence they’ve compiled. A traditional data analyst uses a tool such as business intelligence software to present their findings. The only real difference between the two is that they present findings in a different way.

NPM

ICYMI: Type for Genealogists : Linux Libertine and Biolinum

English: Sample of Linux Libertine typeface
Linux Libertine Typeface Sample

One of my favorite typefaces these days is the Linux Libertine/Biolinum family. The serif Linux Libertine and the sans serif Linux Biolinum family is a set of fonts in a more complete array than one normally gets in a free package. Including the typical roman (yes, it is lower case), bold, and italic, you get

  • Capitals
  • Slanted (or Oblique)
  • Display
  • Initials

The John¹ Burbank Descendants family sketch I posted some years ago uses the Linux Libertine typeface fonts roman, Capitals, and Slanted. The Display and Initials fonts are for other uses than usually found in genealogical text. The Display can be used as titling, for instance, and the Initials for decorative touches.

Despite their name, Linux …, they are universally usable Unicode typefaces. You can use them as defaults on a Windows 10/11 machine. For more information, see the Wikipedia page about them.

NPM

© 2021 N. P. Maling

Centurial – Evidence-based Genealogy Software

I looked at a piece of software called Centurial in 2019. It was quite interesting in its approach to doing genealogical analysis. This review is very dated in its comments, so proceed with caution. [13 May 2022]

The design of the application is quite different from anything I’ve seen in my 25+ years of playing with genealogical software.

The main features are correlation of source materials to instances of persons in such a way that there is little doubt that they refer only to each other. Centurial has a scrollable and zoomable visual “network” view so you can see the relations of persons to each other. Sources are entered in a very nice way, according to the E. S. Mills Evidence Explained format.

There is a space in the analysis pane to enter a proof argument but there is currently no way to output that information in any manner, other than copy and paste; not even to a basic HTML document. You can, however, export a GEDCOM file with the tree you’ve built for transfer to a GEDCOM-based program such as Family Tree Maker or Brothers Keeper.

The Centurial author discusses the differences between his data model and the GEDCOM model on the website referenced below. His website has some small amount of documentation but otherwise you are on your own to figure out how to use the program.

One of the few drawbacks I noticed is that it takes some time to import and convert an average GEDCOM file. For instance, my regular-use GEDCOM is only about 2.5 megabytes and the converted project file is about 25 megabytes. That is a serious size difference. I haven’t looked at the insides of the project file to see what’s what, but I suspect that there is a heckuva lot of XML markup in there.

Centurial is written in English with a European flavor. You may want to view the three tutorials on YouTube before you download and start working with Centurial. They will explain quite a bit about how the author uses it and the potential use cases you may have for it.

Overall, I think Centurial is quite an achievement software-wise. It is not really intuitive but then genealogy itself isn’t all that easy. As it has only been around for a couple of years, I doubt many people have heard of it, though. I recommend it for intermediate or advanced genealogists.

Centurial is available here: https://www.centurial.net/, and was free in 2019. It does require registration and some data collection by the author. It is also a Windows-only product (7, 8, or 10) and requires a recent version of the .NET framework. Personally, I’d like to see a Linux version as well because that’s what I use most of the time.