This article's content is incomplete or a placeholder stub.
This page documents advanced features of Gramps dates.
Dates in Gramps are much more complex than just a month, day, and year. Dates are always in a particular calendar, can span a time frame, can be approximate, and have support for many other subtleties specific to genealogy data.
- The Date Editor in Gramps 3.0 looked like
In Gramps 3.1, we have added two features for dates:
- full support for dual dated dates
- ability to mark dates belonging to a year that did not begin on Jan 1
The second of these required a database change, as we now store a new code with each date to indicate the new year day. This now gives one the ability to better document dates in particular times and places in history.
Some locations changed from the Julian calendar to the Gregorian calendar at the same time that they changed the new year from March 25 to January 1. However, in many places in the world these two events did not happen at the same time.
- The Gramps 3.1 data entry screen looks like
Dual dated dates (also called "double dating", "slash dates", "mixed-style dates", and sometimes "Old Style/New Style" dates) appear like Jan 23, 1735/6. Often mistaken as a year uncertainty, this actually has a specific historic meaning. The dual dated date represents a time when an area was in a transition between moving to January 1 as the beginning of the new year. Thus 23 January 1735/6 (Julian) is an indication to make it clear what date is being referred to.
"For example, England and the American colonies didn't officially accept the new calendar until 1752. Before 1752, the English government still observed March 25 as the first of the year, but most of the population observed January 1 as the first of the year. For this reason, many people wrote dates falling between January 1 and March 25 with both years..."Rootsweb : Double date
Sometimes, a dual date may appear as a fraction, as in this grave stone (170 and 3/4, which means 1703 and 1704):
Marking a date as dual dated can be done by simply putting a slash between the years. For example:
- 1721/2 will appear as 1721/2 (Julian)
- 1719/20 will appear as 1719/20 (Julian)
- 1799/800 will appear as 1799/800 (Julian)
These slash-years can appear anywhere in a date that a regular year can appear.
Dual dated dates will be represented in the Julian calendar so their mon/day will be the same as that in the textual representation.
New Year's Day
As mentioned, many places changed from Julian to Gregorian at the same time they changed from a March 25 new year to a January 1 new year. As these are related, they are represented in similar manners. To indicate that a calendar is in Julian (or any other calendar) one only need put the calendar name in parenthesis after the date. For example:
- January 15, 1750 (Julian)
Gregorian is the default and you need not indicate that. Likewise, to indicate the beginning of a year that is different from that of January 1, you use the following codes:
You can put that as the only item in parenthesis, or right after a calendar name (comma, and no space). For example:
- Jan 20, 1865 (Mar25)
- Jan 20, 1750 (Julian,Mar1)
- Feb 23, 1710/1 (Mar25)
Note that if new year's day is not Jan 1, then January may come after December that year!
Dates with new year day codes will be sorted appropriately. For example, using the Python Gramplet:
> dates = ["Dec 31, 1720", "Jan 1, 1720", "Mar 1, 1720", "Mar 25, 1720", "Mar 26, 1720", "Dec 1, 1720"] > dates.sort(key=lambda x: Date(x)) > dates ['Jan 1, 1720', 'Mar 1, 1720', 'Mar 25, 1720', 'Mar 26, 1720', 'Dec 1, 1720', 'Dec 31, 1720'] > dates.sort(key=lambda x: Date(x + " (Mar25)")) > dates ['Mar 25, 1720', 'Mar 26, 1720', 'Dec 1, 1720', 'Jan 1, 1720', 'Dec 31, 1720', 'Mar 1, 1720']
This creates a list of date strings. You can sort them by wrapping Date() around them and comparing to another Date. In the first example, they have a normal, January through December ordering.
In the second example we append a " (Mar25)" after the date. Now when we sort, we see that the year begins with Mar, followed by all of the months up to Dec, then Jan, Feb and the first part of March is last.
Likewise, date differences can also be made with this method. For example, consider the two dates, Jan 1, 1750 and Dec 1, 1750. Without considering what was the first day of the year with normal sequencing, those dates are 11 months apart. However, if they are actually separated by the new year, then they are actually only a month apart, and the first follows the second:
> Date("Dec 1, 1750") - Date("Jan 1, 1750") 11 months > Date("Dec 1, 1750 (Mar25)") - Date("Jan 1, 1750 (Mar25)") -1 month, -1 day
The Date object in Gramps 3.1 has been enhanced in the way that dates are compared to one another. There are actually three different uses for comparing dates:
- for sorting (eg, for listing in a table)
- for describing (eg, for describing an age)
- for ranking (eg, for computing "record holding" spans)
When a date is subtracted from another, a Span is created. A date Span can be used for creating a textual representation of the difference. A Span can also be used for ranking the difference, including a minimum difference, and a maximum difference.
There are three methods for seeing if one date happened before another date:
- simple method: date1.sortval < date2.sortval
- more sophisticated and expensive: date1.match(date2' "<")
- more restrictive: date1.match(date2, "<<")
Likewise for seeing if two dates are the same:
- simple method: date1.sortval == date2.sortval
- more sophisticated and expensive: date1.match(date2' "=")
and for seeing if one date happened after another date:
- simple method: date1.sortval > date2.sortval
- more sophisticated and expensive: date1.match(date2' ">")
- more restrictive: date1.match(date2, ">>")
Related Gramps bugs
1133: Dates in Event view do not display in chronological order 1834: Dates do not respect new-year boundaries in history 1842: Editing double-dated dates (slash) in GUI box loses slash 2260: fractional year dates not interpreted correctly