Working Wednesday: Gigging at Fiverr

I just put up two gigs on Fiverr (see below) and so far, so good.

The vibe is like how GenLighten operated five years ago before it changed to a subscription model and shut down. There you were able to put up an offering for all to view and buy. At Fiverr you do the same in a comparable way.

The experience at Fiverr is much better, though, as you can see more stats about how well your offers are being received. You can also create links for marketing, which you could not easily do at GenLighten.

Right now, the competition in the Genealogy category seems all right. Most entries in the genealogy / family history section are good, and some not so much. I can’t comment on the quality of the deliverables, though, since I’m a seller, not a buyer.

Here are my two current gig listings:
Full-scale genealogy research
Obituary search

I am thinking about adding a third gig, for proofreading, editing, and writing family histories.

Thoughts?

NPM


Alaska Genealogical Resources

Here’s a link for the Alaska State Library’s genealogy resources. They even have a WorldCat link so you can search for other libraries with the same materials. Some of these materials are also available at Seattle area archives where I’m a researcher available for hire.

 

Sanity Checking with Multiple Genealogy Programs

There are some people, like me, who are not quite satisfied with just one program for genealogical purposes. I use several, and keep an eye out on the others for features that might suit me well.

Lifelines

LifeLines

LifeLines (Photo credit: Wikipedia)

is one of the programs I use on a semi-regular basis. It is an old program (console window, anyone?) and has a long history of strong development by the maintainers. Thomas Wetmore originally wrote it back in the olden days of Unix and DOS, but it’s still around.

One of the things I like about Lifelines is it’s powerful scripting language. This language takes a bit of getting used to but once you know it, it seems intuitive. The program comes bundled with a lot of scripts, some better than others, and some near-duplicates of others. The verify script is one of the most powerful sanity-checkers on the market (did I mention that Lifelines is free?). Some of the things it reports on are age boundaries (birth, marriage, and death), multiple marriages, kids out of order, and so on. Several scripts check for people who might be in the Social Security Death Master Index. Another script called, weirdly enough, zombies, looks for people who don’t have death items (death, probate, burial, and so on).

I ran verify recently on a 5500+ person database and it came up with nearly 1600 items that it thought were interesting and that fell outside of user-programmable boundaries. It’s not for the faint-of-heart to look at this report as it can be a lot to digest. The nice thing about the report is that when I go through it, item by item, I can tighten up the quality of the data on a semi-regular basis, and gain a semi-regular consistency for the entire database. It might take years to finally go through the entire list and complete each item, but knowing about these items is the important thing.

Like verify, the zombies script reads through the database and plucks out those that have death items. This report is much simpler, and sortable so you can find the people by year, instead of in database order. The great thing about this report is that you find out who is in the database that is not marked as dead, dead, dead, as in dead. The script doesn’t consider the deceased flag, if there is one on the person, it makes you think about getting the details, and you’ll want to go out and get the details right away.

If you’ve added a lot of what I call “the moderns” you’ll want to run one of the SSDI check scripts and follow up on a visit to the Death Master Index on your favorite online site that has one. I used to use the one at Rootsweb.com, but Ancestry.com removed it to their own site for some reason. Shucks, the Rootsweb version was better, IMHO.

Enough about the great Lifelines scripts. Multiple programs for genealogical data analysis are a must if you are serious about the pastime. Knowing what’s good data and bad is a good idea, as well as ethically correct. My other genealogy programs include an old version of Legacy, and a current version of The Master Genealogist.

TMG is the one I use on a regular basis as it is almost as powerful as Lifelines in the analysis and reporting facets. The only drawback to TMG’s reporting is that it’s not as flexible and programmable as Lifelines. Legacy, on the other hand, even though my copy is quite dated, is pretty good at picking out bad data, too. Even though I haven’t used Legacy for a while, like Lifelines, I keep it around as a variant finding tool.

T4G: Punctuation and Text Formatting

Hyphens are punctuation, a part of the text; en and em dashes are not, they are formatting marks. I’ll talk a little about the differences and genealogical applications of each. A brief resources section to highlight significant sources used in this article is also given.

The hyphen, en, and em dashes discussed here are part of the standard font package. The hyphen is in the Basic Latin section and the other two are found in the General Punctuation part of the font’s special characters listings.

Punctuation and Text Formatting

Hyphens

Hyphens are punctuation, a part of the text. In the old days of the typewriter and early days of the computer, hyphens were doubled and tripled to substitute for dashes. This is unnecessary now as we have proper dashes available. The hyphen is also distinct from a minus sign, but mathematical expressions occur only rarely in our type of writing.

En Dash

En dashes are what Bringhurst (see resources section) calls analphabetic characters. His thought about the handling of them is different from traditional usage. The differences he considers significant take into account more languages than English, which most fonts are designed for.

In genealogical writing, the en dash is the strongest visual indicator for date ranges. En dashes are meant to separate the two ends of a range such as 1582–1752. Some textual terms can also benefit from its use. En dashes emphasize a separation between a prefix and a word in a compound term such as post–1945, or pre–marriage.

Em Dash

Em dashes separate thoughts. They represent missing data in some cases as in unknown surnames (—?—).

In terms of formatting, there are several micro-stylistic thoughts to consider. One is how much spacing there should be around the em dash.

Bringhurst would have us use spaces around the en dash as an alternative to the (subjectively) lengthy em dash as in “… – …”. Doing this would lead to putting a non-breaking space between the last characters before the en dash to keep the two together, possibly affecting a text’s justification.

One of the faults with Times New Roman is that the em dash is too long. Most professionally designed fonts compensate for the length of the em dash by making the capital M a more realistic width. Times New Roman was designed for a specific purpose: newspapers, and should only be used by that type of publication. Linux Libertine, on the other hand, was designed for more common publications such as this one, and books, so its readability is greater.

Illustration: Linux Libertine and Times New Roman em dashes

Illustration: Linux Libertine and Times New Roman em dashes

Hatcher, and Leclerc and Hoff (see resource section for both), differ on whether there should be spaces around an em dash in text. I would prefer the latter, and include the spaces. Doing this also requires that you pay attention to justification and word breaks at the beginning, so the dash doesn’t sit by itself at the beginning of a line.

My own thought on doubling or tripling the em dash for missing names is that it’s unnecessary. A triple dash, or in Unicode terminology a “horizontal bar” (―) can stand in. It is shorter, and more representative of the strong emphasis necessary. I prefer to denote missing data with just an em dash or as (—?—) [opening parenthesis em dash question mark em dash closing parenthesis].

Dumb and Curly Quotes, Redux

Using real quotes (curly “ / ”) raises the tone of what we read. It’s also what we’re most brought up to see in printed published materials. Online it’s another matter, though, since most early computer systems couldn’t handle curly quotes and kept the dumb quote from the teletype repertoire.

Resources

The Chicago Manual of Style, 15th ed., Chicago, Illinois: University of Chicago Press, 2003.

Robert Bringhurst, The Elements of Typographical Style, version 3.2, Point Roberts, Washington: Hartley & Marks, Publishers, 2008. See in particular chapter 5 “Analphabetic Characters.” on punctuation and textual markup.

Patricia Law Hatcher, Producing a Quality Family History, Salt Lake City, Utah: Ancestry, Inc., 1996.

John D. Lamb, Notes on OpenOffice Writer: Large and Complex Documents, n. p.: n. pub., 2009. Available online at the author’s home page. See in particular Chapter 2 “Characters, Fonts and Highlighting,” on the details of the characters and their handling.

Michael J. Leclerc and Henry B. Hoff, eds., Genealogical Writing in the 21st Century, Boston, Massachusetts: NEHGS, 2006.

Peter Wilson, A Few Notes on Book Design. Normandy Park, Washington: The Herries Press, 2009. Available online at the LaTeX archives . See in particular, chapter 5 “Picky Points,” on punctuation and textual markup.

© N. P. Maling — Sea Genes – Family History & Genealogy Research