VK1AO
March 9, 2025, 6:04am
1
Multiple activations today. SOTA hunts in more than one. But when you activate the logs from the second activation, the SOTA hunt log is overwritten because the filename is not unique.
Minor issue but can we add something small to the filenames for SOTA hunt logs so they are unique for the operation?
Alan
M1SDH
March 11, 2025, 11:39pm
2
Just looking at new templating features in March release, you could add {{first8 op.uuid}}
to the filename as workaround for now.
VK1AO
March 12, 2025, 9:40am
4
I’d like to know a bit more of the logic behind the template settings:
At the moment I cannot work them out
e.g. the leading r? Is that a literal?
The > symbol?
How are the filename Templates interacting with the choice of compact versus non-compact file naming selections?
Alan
KI2D
March 12, 2025, 9:44am
5
I’m adding, by default, a timestamp to the filename to make it more unique.
But M1SDH’s suggestion should work for now.
VK1AO
March 12, 2025, 9:47am
6
first.8 op.uuid comes back an error, op.uuid is fine but first.8 won’t work. Ideas?
it’s first8 NOT first.8
no decimal - the template instructions are correct the example threw me
Alan
KI2D
March 12, 2025, 9:47am
7
Yup, the templates will need some documentation.
As of now, this file in the source code has some notes:
/*
* Copyright ©️ 2024 Sebastian Delmont <sd@ham2k.com>
*
* This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0.
* If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/.
*/
/*
# Explanation of how PoLo manages exports for one operation.
For each station callsign in the operation, we collect "export options" from:
- The handler for each reference in the operation.
- Any "export" handler.
Each of these handlers can suggest zero or more export options, for which they provide:
- A format (ADIF, Cabrillo, etc.)
- A name template (e.g. "{date} {call} {ref}")
- A title template (e.g. "{call} {ref} {date}")
- A templateData object (a set of key-value pairs that are passed to the name and title templates)
This file has been truncated. show original
There’s also some brief text at the end of the Export Options Settings Screen.
VK1AO
March 12, 2025, 9:49am
8
Yes - and I assume the qso is accessible to the qso records, op is accessible to both filename and qso, but qso. is not accessible to a template filename.
Needs to be documented with lots of examples.
Alan
KI2D
March 12, 2025, 9:52am
9
Indeed.
The templating system is rather powerful, and I’ll start using it in other places, like spotting messages for example.
VK1AO
March 12, 2025, 9:56am
10
The example displayed under the template entry,
doesn’t really marry with reality
Where is the “for” literal? and the callsign?
Alan
KI2D
March 12, 2025, 10:10am
11
{{>OtherActivityName}} references an internal template with the default file names.
The comments on the file linked above explain a bit how it works.
And you can see the templates themselves in line #246
KI2D
March 12, 2025, 10:12am
12
That particular template, OtherActivityName
looks like
{{op.date}}{{#if log.includeTime}} {{op.startTime}}{{/if}} {{log.station}} for {{log.handlerShortName}}
(this includes the new timestamp to fix the issue for SOTA Hunted)