Each week, a report is run which summarises all the comments that have been added to callsigns that have been research by Alan (or added as expedition plans surface). There are usually a dozen or more. As they number in their thousands now, there is no practical way to go through editing each callsign a second time.


Callsign comments are therefore always worded in the past tense, even when the expedition or activity in question is in the future at the time of writing. This is so that the records will read correctly later.
https://clublog.freshdesk.com/support/solutions/articles/53204-why-are-callsign-comments-worded-in-the-past-tense-
clublog.freshdesk.com
crawl=CC-MAIN-2022-40
22182
application/http; msgtype=response
sha1:RO5UEQRFR3VDD6OU2OSC34CTZJSXNP25
<urn:uuid:0e69076d-d18e-44a2-aecd-d9ab3ed4ec6a>
2022-09-29T17:37:53Z
54.205.74.210
text/html
sha1:O6BFZF5RFKMUB575LTL34UAP3QLQOVKD
<urn:uuid:fe518ca7-c2e1-45c5-9d36-5bb3f34d6350>
https://clublog.freshdesk.com/support/solutions/articles/53204-why-are-callsign-comments-worded-in-the-past-tense-
response
<urn:uuid:77945383-0dae-47b1-b47e-6573e0eb655a>
isPartOf: CC-MAIN-2022-40
publisher: Common Crawl
description: Wide crawl of the web for September/October 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-88
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/