Dates & Time
Dates & Time
There is no one way to measure time - historians know this almost intuitively. And while computational methods for time vary considerably, finding an adequate system to allow for cross-cultural chronometry is not as straightforward as it might seem. Yet it's crucial for ensuring that the events historians document have as close an approximation of time as close as possible to how time is recored in a source.
Many computation systems and languages use an integer-based measurement of time known as the Unix-time stamp, or epoche time. The timestamp constitutes the number of seconds from 1 Jan 1970 00:00:00 GMT. Even so, the timestamp, as a datatype, runs out on 16 Jan 2038, and is invalid for dates prior to 13 Dec 1901. Nevertheless the timestamp provides an integer-based means of translating between different calendars and time, across numerous platforms.
Importantly, NanoHistory allows users to assign any number of dates to any entity, and does so by noting start and end dates, which can in themselves be a range or ambiguous. Say a source only mentions a year like 1243AD - this is translated using the Julian calendar functions into a range of 2175063.500000 (Jan 1) to 2175427.500000 (Dec 31). More precise dates create a smaller range. Users can vote for confidence in a particular date, allowing one to rise as authoritative over others. Equally, in using data in searches and tools, users can select fuzzy or narrow dating. Fuzzy selects the widest date range possible from all associated dates, while narrow selects the smallest range. By using Julian Days NanoHistory can quickly filter data according to dates using simple techniques, and present data in a calendar selected by a user.