The workstation says 1:30. Which 1:30?
· Compsyscon preservation editorial desk · Worked example and worksheet
A directory listing from an offline workstation shows a file last modified at 01:30 on November 3, 2024. You want to place that file before or after another one in a collection. Even if you know the machine used New York time, that reading points to two possible instants. Keep the original 01:30 in the record. A UTC time can go alongside it once you have evidence for the offset.
1. Keep the original reading
Copy the date and time as shown, the file reference, the name of the tool or screen, and the field you were reading. A directory listing’s “last modified” field answers a different question from the wall clock visible at the corner of the desktop. If the listing uses a date such as 03/11/24, keep that exact string until you can establish the display convention.
For a handover, record where the listing came from and when you observed it. Give the disk or image a reference from the workstation storage inventory. An offline machine can have the right time or the wrong time. Its location today is a poor basis for assigning a time zone to a file it held years ago.
2. Identify what stored the time
For Windows filesystems, Microsoft’s file-time documentation makes a distinction that matters here. FAT stores local time. NTFS stores time in UTC. A program displaying an NTFS time may convert it to local time, so a screenshot of that display and a UTC value read from the filesystem deserve separate labels.
Record FAT or NTFS only when you have identified the volume. A drive letter or the make of the workstation is too little evidence. Also record whether you read the original volume, an image or a later copy. If all you have is a printed directory listing, put that in the source field and leave the filesystem and zone unresolved. A timestamp stored in UTC can still reflect a clock that was set incorrectly.
3. Work through the repeated hour
For the test, assume the displayed date is November 3, 2024 and the zone is America/New_York. When the clocks went back, 01:30 occurred twice. We ran this example with Python’s zoneinfo, which uses the fold attribute to distinguish the earlier and later occurrences.
- First 01:30,
fold=0. The offset is UTC−04:00, giving 05:30 UTC on November 3. - Second 01:30,
fold=1. The offset is UTC−05:00, giving 06:30 UTC on November 3.
Converting each UTC result back to New York time returned 01:30 and its original fold. Both conversions work. The round trip checks the arithmetic. To date a particular file, you still need evidence of which occurrence its clock showed. If the zone itself is unknown, leave the UTC field empty. Either New York result would assign the machine a location the listing never gave.
4. Leave a record the next reader can use
Download the clock evidence worksheet. Its first two rows hold the two interpretations of the same synthetic reading. The third shows how to enter an unlabelled listing: the original reading stays, and the zone, offset and UTC cells stay blank. There is a final row for your own observation.
What would settle the example? A contemporaneous record of the same event giving an explicit offset could distinguish the two occurrences. Record the supporting reference before choosing one. If the two files you want to order fall within that uncertain hour, leave their order open. When the question is whether a preservation copy has the same bytes, turn instead to the checksum comparison guide.


