Hello, cqrlog team,
there is this web application that organizes stuff for our club station, in particular, collects logs.
Individual OPs may use whatever logging software they prefer, so naturally, I use cqrlog. I want to export ADIF out of cqrlog and import into that web application. Doing so, I have a problem.
The programmer of that web application has read the ADIF spec and found that the QSL_SENT field should contain the letter "R" for "Requested", for people that want a paper QSL from our club station. (In case it matters, that programmer, that's also me. But I think it doesn't.)
So I enter "R" in this field in all pertinent QSOs in cqrlog. Which is not offered in the drop down list, but can still be entered into the field all right. The "R" becomes visible in the QSO list, and it also is listed duly when I execute an SQL statement such as
select qsl_s from view_cqrlog_main_by_qsodate;
However, when I export this to an ADIF file to contribute to our club station effort, the export process out of cqrlog changes the value from "R" to "Y". Incidently, even the automatic backup file has the same problem. So should I ever need to make use of the backup file, my original "R" values would be lost. (Should I ever decide to make use of both "R" and "Y" in the way suggested by the ADIF spec, utter chaos will ensue.)
This is about cqrlog version 2.3.0 as available for the Debian Stretch Linux distribution.
Hi!
Export to adif looks like this:
if Length(QSLR) > 0 then
tmp := ' '' then
d.QSL_RCVD := d.APP_CQRLOG_QSLR
else begin
if d.QSL_RCVD = 'Y' then
d.QSL_RCVD := 'Q'
else
d.QSL_RCVD := ''
end;
So when exported it is always Y if any kind of marking has been done.
And if imported it will be always Q in cqrlog if it is marked as Y in adif tag.
And if exported again ... and again ..and again it will be Q in log and Y in adif tag.
Only at first export the existing mark (if it is something else than Q) is lost and can not be returned.
By adif specs using Y and R (received and Requested) could be possible. Perhaps this needs some fixing.
--
Saku
OH1KH
Ooops!
Someting messed up with paste of source codes, but anyway "what ever letter" becomes adif-Y in export and in import adif-Y becomes Q in log
--
Saku
OH1KH
This is a violation of the principle of least surprise. Or several such violations, actually.
$HOME/.config/cqrlog/database/*.tar.gz), I will not able to re-establish this field of my QSO db.My opinion: Yes. This needs to be fixed.
Hi!
You should either copy whole ~/.config/cqrlog folder with all files and subfolders as complete backup, or do database backup with mysqlodump to get 100% identical copy. There are lot of log settings that are not copied with adif export that copies only qso contents.
--
Saku
OH1KH
I was afraid of something like that...
My take on this:
The ADIF spec allows the letters
Y,N,R,Q, andI.These letters should be both imported and exported as they are, with no change whatsoever. Any other cqrlog behavior negatively impacts cooperation between cqrlog and other ADIF-consuming or ADIF-producing software.
Q in CQRLOG means confirmed and it has been using this since the first release 11 years ago, much sooner that the Q letter gets into ADIF specs.
When you exported the ADIF file, it's marked as Y because it means that QSO was confirmed.
As far as I know, CQRLOG also exports tag APP_CQRLOG_something with the letter used by CQRLOG internally.
73 Petr
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
HI !
Only Y,N,R,I usage produces backup that can be restored 100%.
How ever letters usage inside cqrlog must be studied first. At least they are used in DXCC status, perhaps also elsewhere.
--
Saku
OH1KH
This remark by myself was probably nonsense. In the backup file, there is this field APP_CQRLOG_QSLS which has the original data actually inside the database. So all the original data is there and can be restored.