rouggy
747c2b9105
QRZ's XML carries <iota>EU-048</iota> for an operator on an island, and OpsLog read past it. Wired end to end: the provider, the lookup cache (a column, like web and zip before it), and the entry's award references. It matters more here than the same field would for another award. There is no live "who is on an island right now" feed anywhere — POTA has one and that is what OpsLog matches spots against; SOTA has one behind conditions; IOTA publishes only static lists. So the callbook record is the practical source, and it is known BEFORE the contact is logged, which is when a reference is useful. The reference goes in as an IOTA award reference, exactly as one picked by hand, so the existing path carries it to the qso.iota column on save. Two limits, both deliberate. A reference the operator typed or picked WINS: a callbook entry can be years out of date, and the operator in front of the radio has just been told where the station is. And the value must look like an IOTA reference — two letters, a hyphen, three digits — because writing anything else into the award makes a reference no list contains, which counts for nothing and has to be found by hand later.
9 lines
471 B
SQL
9 lines
471 B
SQL
-- The lookup cache gains the IOTA reference QRZ was already sending.
|
|
--
|
|
-- QRZ's XML carries <iota>EU-048</iota> for an operator on an island, and
|
|
-- nothing read it — so the one place an IOTA reference can be known BEFORE the
|
|
-- contact is logged was thrown away on every lookup. There is no live "who is
|
|
-- on an island right now" feed anywhere (unlike POTA), which makes the callbook
|
|
-- record the practical source.
|
|
ALTER TABLE callsign_cache ADD COLUMN iota TEXT;
|