I just signed up for 20GB of free online cloud storage from Copy. This is similar to DropBox, SkyDrive, and others. I love to get free storage especially for genealogy work so I can back up documents and photos and have access to these copies from all my computers, phones, tablets, etc. I also want to start storing the results from the genealogy tools onto the cloud for better safekeeping.
If you click this link https://copy.com?r=kZtbiz and signup, then I will get an additional 5GB for the referral, which I would of course be grateful for. You never know how much you will eventually. Please comment if you sign up so I can say thanks.
I recently read the difficulty that a user was having finding a convenient way to detect ancestral loops in their GEDCOM file.
Ancestral loops are easy enough to detect by scanning an ancestral tree recursively looking for matching ids between the person being scanned and their ancestor being compared. Since Adam (and Bonkers) already have this capability, it was simple enough to update it to add this support to the Bonkers report. With this change Adam has been bumped to rev 1.1.8.
It should be noted that I only did a quick test to make sure that Adam and Bonkers would detect ancestral loops. The test was by no means exhaustive, so if you find an issue, please let me know.
This update adds two new options to the configuration menu for Adam.
HighlightUncertainParents which is now disabled by default. When enabled, uncertain ancestors are grayed out in the Ancestor Lists and the profile charts. I said I wouldn’t add this feature, but being a reasonable man and being that none of 450+ databases that have so far been uploaded use parental associations to establish certainty, it appears to be more of a nuisance to users than not. I, of course, recommend using parental associations and enabling this option, but it is now left up to each user to decide for themselves.
IndicateCertaintyAssessments continues to be enabled by default. When disabled, certainty assessments will no longer be shown on ancestors’ profile pages for each claim. Exceptions are made for
disproved certainty assessments.
This update includes several bug fixes.
1. when creating referrer lists for sources, locations, etc. family events are now included.
2. referrer lists are now sorted by name.
3. restore the comma and space between listed source categories.
4. made surname URL fragments (the portion following a # sign) SEO compatible.
5. when a person’s spouse is missing, but marriage exists, it no longer lists the person as the spouse also.
6. fixed slashes dates (i.e. 5 Mar 1765/66).
Well it finally happened. It was bound to eventually. One of the users of Adam has gone online with their ancestor tree data embedded in a WordPress blog, similar to mine. We did run into a slight problem. The jQuery library that Adam uses to display the tabs apparently interfered with some of his other scripts. Adding the script load to the footer fixed the problem. So if anyone else has trouble getting their tabs to work after embedding, try adding
to the footer and then rebuild your tree using Adam. I will look into moving that line from the config into the build so users do not have to worry about it. I’ll post an update once I’ve done it.
If you want to check out Simon Gatward’s tree and site, bearing in mind that he is just starting it up so it a work in progress, go to http://simongatward.com
I made a change to the source categories. This is a feature that no one uses but myself, so if the feature does not interest you, I guess you can stop reading here.
Firstly, I renamed the authority category (_QUAY1) values from ‘primary’, ‘secondary’ and ‘tertiary’ to ‘original’, ‘transcript’, and ‘copy’. I did this because, the names have a clearer inherent meaning. I also did it because the Genealogy Proof Standard (GPS) commandeered the definitions of ‘primary’ and ‘secondary’ to mean something entirely different than what was commonly thought. The new strings will therefore no longer interfere with the GPS. The old names are still supported for backward compatibility, but as I said, no one uses them. I also extended the category by supporting a new string, “abstract” so that users can distinguish between copies of copies and data not in the original form.
I will admit that when I first came up with my source categories, I did it in vacuum and was not even aware the GPS existed. Randy Seaver was kind enough to inform me. Since the GPS is just a subset of my categories, it was easy to support it. This is done by also supporting the string “derivative” for the authority category. GPS users can now simply set _QUAY1 to “original” or “derivative”. Likewise, GPS users can now also make use of the association category (_QUAY2) by setting it to either “primary” or “secondary”. Using these two categories, users can now get full support for certainty assessments. Unfortunately they still need to be able to add user tags to their sources which very few applications will allow.
While I was adding GPS support, I went ahead and added the strings “direct” and “indirect” to the conclusion model (_MODL) as well.
As a reminder, “negative” evidence (GPS) is already supported by Adam. See the FAQ for how to show a claim has been proved to be invalid. Consult the FAQ for details on source categories and certainty assessments as well.
VGedX 1.14 removes the requirement of the ADDR field as part of the address structure in GEDCOM 5.5.1 and 5.6 that was added in the previous release (VGedX 1.13). It was added because the specification states that it is required when the structure is used, but all usages of the address structure are optional so the intent is that only if an address structure is included, then the ADDR field is required – makes sense. Louis Kessler caught this and posted it on his blog:http://www.beholdgenealogy.com/blog/?p=1303
VGedX 1.13 fixes a bug in the ADDRess structure for GEDCOM 5.5.1 and 5.6 where it was using GEDCOM 5.5 limits. Specifically, the ADDRess line is required in the later versions of GEDCOM and was not in GEDCOM 5.5. Also, the number of CONT line extensions was unlimited in GEDCOM 5.5, but limited to 3 in the later versions. A big thanks to Tamura Jones for pointing this out.
I saw the “before-and-after” photo widget on Klaus Herrmann’s farbspiel photography Blog yesterday, and thought what a novel idea. Probably not though since the WordPress Plugin has been around for 4 years and the JQuery plugin for longer. New to me though, I don’t get out much. So I … Continue reading