Login to participate
  
Register   Lost ID/password?
Louis Kessler's Behold Blog » Blog Entry           prev Prev   Next next

Behold Version 1.1 - Sat, 27 Jun 2015

I have released Version 1.1 of Behold.  It is now available on the Download page.

The easiest way to upgrade your existing version is from the Help menu in Behold: select “Check Online for New Version”.

For changes in this version, see the History page.

I’ve changed my Future Plans page. I will no longer be giving projected dates of the next versions. They were taken the wrong way. However, you will see that my next objective is to work towards releasing a beta of Version 2 with editing.

There are three language translation files on the Download page:  Dutch, French and German. However the new version of Behold has a lot more terms, so these language files are now quite incomplete and need to be updated. If you would like to update one of these files, or create a new one in a different language and send it to me, I will make it available for free for all users.

Please try out the new version of Behold and let me know what you like and what you don’t and if anything isn’t working quite right.

To anyone who downloaded Version 1.1 on June 28 or June 29. The old Version 1.0 help file was included by mistake. Just go to the download page and install Behold again right over the one you’ve got without uninstalling and that should give you the new Version 1.1 help file. To check that you’ve got the new help file, open it and search for “life”. The old version only has 1 entry. The new version has 11.

8 Comments           comments Leave a Comment

1. klemens (klemens)
Germany flag
Joined: Thu, 5 Sep 2013
9 blog comments, 4 forum posts
Posted: Sun, 28 Jun 2015  Permalink

Congratulations for the new version!
I have just played around with it for a short time. First thing I have to say is that the Life Events are really GREAT. They make me see connections between people and events much easier, and will definitely help with finding some mistakes in the data, too.

It takes a moment to understand the way the life events are presented:

Older sister 1 Death: (date), age 1
…Older sister 1: (name), age 12

At first, I thought the older sister was 1 year old when she died.
Maybe putting the date and age of the “main person” in front is clearer? It could make for a shorter line, too:

(date), age 1: Death of Older sister 1 (name), aged 12

For the Place Details, it could also make sense to put the date in front of the line, when the events are sorted by date.

before 1585: Birth:
…(details)
1585: Death:
…(details)

As an option for the future, it could be nice to sort the Place Events by type: All Births, all Marriages, all Deaths together. That might be helpful if one wants to check with a source that only records one type of event.

2. Keith Riggle (geneatech)
United States flag
Joined: Sun, 7 Apr 2013
12 blog comments, 0 forum posts
Posted: Sun, 28 Jun 2015  Permalink

Awesome! Can’t wait to try it out. I also took a look at the planned features for version 2, and they look very exciting!

3. Louis Kessler (lkessler)
Canada flag
Joined: Sun, 9 Mar 2003
213 blog comments, 225 forum posts
Posted: Sun, 28 Jun 2015  Permalink

Thanks, Keith.

And thanks Klemens for your ideas. Yes, I do agree with you that the age on the first line may be confusing as to whose age it is. I like your suggestion that the date and age be kept first and the relationship and life event be added following that. Also this would allow the “With Wife” to move up which would be more efficient. But I think I’d still like the event to start on a line of its own. That would make it easier to pick out what the actual event is, e.g.:

Sep 1899, age 27, married 10y to 13y with Wife Margerett (Donovan) McCarthy MCC-2, age 24
   Son 4 Birth: John J. McCARTHY MCC-52 in Boston, Suffolk, MA
   Source: 1900 Census Theodore H. McCarthy Household …

Good idea. I’m not sure offhand if my current data structure will allow simple switching of the order. If it does, I might make the change in a point release (1.1.1). If not, I’ll consider this for Version 2.

I had to think a bit about your suggestion that an event sort order in the place list might be wanted. Usually these will already have a source (otherwise, how did you come up with it?). Therefore, you would rarely want to check your birth lists at a place with a birth list record. I would see it normally work the other way around, where you would find a new birth source for the town, and see if each potential entry from the source would be in your list. In that case, the date order would be fine and maybe even preferable. For example, you might not have the birth record, but do have the Christening record a few days later. Or you don’t have the death but you have the burial.

But once I add source-based data entry, that methodology won’t be needed. Instead, when you get a new source, say a list of births in a place, you’ll enter it as a new source along with all the events it contains that may be relevant to you. Then you’ll link them up to the relevant people.

4. Louis Kessler (lkessler)
Canada flag
Joined: Sun, 9 Mar 2003
213 blog comments, 225 forum posts
Posted: Tue, 30 Jun 2015  Permalink

Klemens,

I’ve taken a look at the idea of putting the date before the event. But at this point, it won’t work. It only became apparent to me when I checked my code and determined my data structures. You need some complex examples with dates and places and sources and notes to see the problem. I won’t try explaining that detail now, but I’ll at least give you this:

Each line is representing an event. So the event comes first, following by the date and place and other event information.

When it’s an event of the person, it is obvious, e.g.:
Birth in 1910 in France

But when it is a Life Event, the relative for the event must be shown, e.g.:
Birth Son 1 in 1940 in France

The line naming the son is extra information that is not part of the event, so it is added after.

Moving the event off the first line removes what is important. And a bit of a logistic problem: If you didn’t have a date or place, then nothing would show on that line.

So the real concept is that the event line is the event as it is related to the main person, which is why the age of the main person is shown there.

As I’m implementing the database for Version 2, I know I’ll be promoting events internally to be their own record. Once I do that, I’ll consider your idea and if there’s a good way to implement it, I might be able to change it then.

Louis

5. klemens (klemens)
Germany flag
Joined: Thu, 5 Sep 2013
9 blog comments, 4 forum posts
Posted: Wed, 1 Jul 2015  Permalink

Thanks for this explanation, Louis. I see what you mean.
Events with unknown dates are really a special case, and I didn’t think of that. Where do they show up now in the life events?
I guess with the presentation of life events, users will quickly notice when an event has no date. And then they may make an educated guess to give it a date-range which will put the event at a plausible position in the persons timeline. So maybe “life events” will make people clean up their data :)

If in the future there is a smart way to implement something like that, I’m now thinking that the age of the main person should be the first thing in the line. They are that person’s life and events, they should be sorted by his age. But what comes after that is not so clear… maybe something like this:

age 0, 1910, Birth in France
   Father (Name) (ID) age 34
   Mother (Name) (ID) age 21
age 2, 1912, Death of Older Sister 1 in France
   Older Sister 1 (Name) (ID) age 3
age 30, 1940-05-05, Birth of Son 1 in France,
   Son 1 (Name) (ID)
   with Wife (Name) (ID) age 25, married 2 years
age unknown, Death of Father in Paris
   Father (Name) (ID)

6. klemens (klemens)
Germany flag
Joined: Thu, 5 Sep 2013
9 blog comments, 4 forum posts
Posted: Wed, 1 Jul 2015  Permalink

argh, there should be indentations in that… (How did you get you example to indent? unicode?

7. Louis Kessler (lkessler)
Canada flag
Joined: Sun, 9 Mar 2003
213 blog comments, 225 forum posts
Posted: Wed, 1 Jul 2015  Permalink

Klemens,

Events without dates generally show up first, with a few exceptions (e.g. Behold tries to be smart about marriages and births and keep them in order if possible).

When I say “event”, I am also including facts and other information that normally don’t include dates, e.g. height, eye color, number of children, DNA info, etc. So there might be quite a bit of information without dates, and it isn’t necessarily because the date is missing.

But it still seems t me that it is the event that is most important and should be first, not the age. I think I want to know that it is a Birth, or a Death of Older Sister 1, or the Death of Father before anything else. And all the following indented information all relates to that event.

For indentations, I’m using the HTML character for a space, which are the 6 characters:   I’ve updated your comment to include them.

Louis

8. Louis Kessler (lkessler)
Canada flag
Joined: Sun, 9 Mar 2003
213 blog comments, 225 forum posts
Posted: Wed, 12 Aug 2015  Permalink

I’m now playing around with better representations.

The solution to putting the date first might be to also have the event and the person on the same line, e.g.:

Age 30, married 2y (wife first name, age 28), Wed 5 June 1940 in France. Birth of Son 1: (Name) (ID)

or possibly (which do you like better, age first or date first?):

Wed 5 June 1940, age 30, married 2y (wife first name, age 28) in France. Birth of Son 1: (Name) (ID)

Then if the date and place is not given, then there is still something on the line for reference, e.g.:

Birth of Son 1: (Name) (ID)

I’m playing with this now to ensure this would work consistently across all the different event types. I’ll post another blog post explaining what I’ve decided on once I’ve done it, and then I’ll release a version 1.1.1.

Thanks again Klemens, for this idea.

Louis

 

The Following 1 Site Has Linked Here

  1. Genealogy 2015 - Modern Software Experience - Tamura Jones : Thu, 31 Dec 2015
    "Louis Kessler introduced Behold version 1.1, which includes Life Events. Behold 1.1 is still a genealogy viewer and editing remains planned for Behold 2.0."

Leave a Comment

You must login to comment.

Login to participate
  
Register   Lost ID/password?