Can we have an option to also read from a user defined SCL file as well as the public version. Currently VK9DLX has no country associated as the SCL file suggests the expedition has ended and it has not.
I would appreciate this "Expert Mode" also very much. The current VK9DLX operation is a prominent example as described. In the recent past I worked a special callsign 2SZ (see qrz.com) from the UK and it is now lost because I cannot find it in the log with F7 though it is there. The same happened with the famous call sign RAEM from Russia and so on. So please give the possibility to customize SCL by user.
"The original plan was that Robert will stay until November 8th on Lord Howe Island to do some more RTTY operation and to have an eye on the sea freight when it leaves the island. But plans are there to be revised. Robert had to depart for home for business reasons. So the last man on the island is Joe DF7TH. He extended his stay until November 11th. He will operate until November 10th on the remaining bands 30m, 17m, 12m and 10m we left antennas up."
The DXpedition has ended with one op remaining as noted above.
In managing the SCL contents, I can't keep up with stragglers.
It is certainly a rare occurance, but if an expert mode were tpo be enabled, individual users could make an exception in the SCL file if they work these rare occurrances, it would save you having to "keep up with the stragglers"
My previous logging program before i saw the light (DxLabs suite) had this facility enabled
I would like to add that we all appreciate the work done in the back ground on things like SCL and other LoTW files.
The SCL was out of sync with the dxpedition dates and some times happens and this is not the fault of the SCL file owner in any way.
I suggested the option so these small number of date changes and lesser known calls can be dealt with easily by ourselves without causing an workload to another.
The use custom SCL file still needs attantion as 7QAA iscurrently not mapping to Malawi. This is annoying to be relying on someone else to alter this. I know I can tweek the files but a long term fix is needed. Strange as 7QAA is mapping OK within clublog. Not sure what the clublog file sync does ?
7QAA is a not-expected callsign because has been assigned without following any of the commonly adopted naming conventions.
This is wht Log4OM doesn't recognize this as potential callsign and doesn't start any further lookup.
To save resources and roundtrip to external websites only callsign that have a "legal" form are passed through the callsign check routines. This is to avoid that typing "hello" in the callsign box will start polling databases and external resources without needs.
I'm working for a solution, but SCL doesn't help because Log4OM stops this before.
