LOTW select issue 1.16.0.0

Need help? - Post here and we will find a solution for you.
wa2edn
Novice Class
Posts: 8
Joined: 23 Jan 2014, 13:46

Re: LOTW select issue 1.16.0.0

Post by wa2edn »

Terry and I exchanged email and it looks like it's an operator problem.
I was not using it correctly and in the old version it did not matter. I have corrected the issue on my part and everything is now working FINE !
http://www.pisto.it/forum/posting.php?m ... 88f6f83a4b#
Thank you SO much.
BILL
User avatar
G4POP
Log4OM Alpha Team
Posts: 11592
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: LOTW select issue 1.16.0.0

Post by G4POP »

One thing that caused Bill some confusion was the button that is labeled 'Select Required" and I believe it will also confuse other people!

When clicked this button returns a list of QSO's with the sent status marked as R - requested

The status R - requested is past tense I.e. I have already asked for this QSL Which indicates to me and most other people that I am waiting for a response.

N - no however clearly means the the QSL has not been sent and requires upload in the case of eQSL and LOTW or posting in relation to a QSL card

So I believe that most people would expect a list of QSO's with the LOTW/eQSL sent status marked as N - no when they click the 'Select Required' button

May I suggest that either the Select required button is removed because the function can be accomplished by other methods and it's existing function is confusing.

Alternatively change the function of 'Select Required' is changed to provide a list of QSO's with the status marked N-no

I have never understood why the ADIF specification included 'Requested' I think it's pointless especially in the QSL, eQSL & LOTW sent status!

Another point is that I believe the default sent status for all QSL methods should be N-no
73 Terry G4POP
User avatar
IW3HMH
Site Admin
Posts: 2988
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: LOTW select issue 1.16.0.0

Post by IW3HMH »

G4POP wrote:One thing that caused Bill some confusion was the button that is labeled 'Select Required" and I believe it will also confuse other people!
When clicked this button returns a list of QSO's with the sent status marked as R - requested
The status R - requested is past tense I.e. I have already asked for this QSL Which indicates to me and most other people that I am waiting for a response.
No, remember that this field is the QSL SENT STATUS, and it's not correct to assume that i'm WAITING a QSL and this information will be set in the QSL SENT STATUS...
Maybe in the QSL RECEIVED STATUS, the REQUESTED means: I'm waiting for a QSL, and this is the program default.
G4POP wrote: N - no however clearly means the the QSL has not been sent and requires upload in the case of eQSL and LOTW or posting in relation to a QSL card
Assuming that, there is not a status that means: NO, i don't have sent QSL and i will NEVER send a QSL to this user (because he wants $$$ or other reasons).
If you use N = NO to say "qsl not YET sent" you don't have a status where to set "qsl will be never sent".
Requested, in that case, will be unuseful and unused (and REQUESTED in the QSL SENT STATUS cannot be interpreted by "i'm waiting for a qsl back")

In Log4OM logic (but user is allowed to customize this) N means NO, I WILL NOT SEND. and REQUESTED means: User has requested QSL, but i've not sent my qsl yet. Queued, another status, in my interpretation means: QSL Printed but not sent yet, waiting for postage or bureau delivery

Again, everyone can use status as it wants. The only "fixed" status is set in the button you're asking to remove. I can add a combo to let user choose the status he want to load (N or R) but i will not remove the button.
G4POP wrote: So I believe that most people would expect a list of QSO's with the LOTW/eQSL sent status marked as N - no when they click the 'Select Required' button
I believe the opposite, as stated before. The only way i see is to give an option to select what status will be load by the "select required" button, but i also thing we should provide some help to users, and make the software able to drive them...
G4POP wrote: May I suggest that either the Select required button is removed because the function can be accomplished by other methods and it's existing function is confusing.
No :) i will keep this button, because it's the first time an user reports that he's confused by this button, and i think we can explain how it works, instead of removing a feature... Then you're able to use it, if you know what it does.
G4POP wrote: Alternatively change the function of 'Select Required' is changed to provide a list of QSO's with the status marked N-no
Did you have made a survey about how many users will use your convention and how many users use the "requested = qsl needs to be sent" one before asking this?
G4POP wrote: I have never understood why the ADIF specification included 'Requested' I think it's pointless especially in the QSL, eQSL & LOTW sent status!
To provide 2 statuses that means: NO, DON'T SEND and NO, BUT YOU MUST SEND QSL. Removing REQUEST you will remain without this possibility (that is used also in label Printing)
G4POP wrote: Another point is that I believe the default sent status for all QSL methods should be N-no
There is an option in the configuration to set this. You can change it, if you want, but i don't recommend to use this logic.
Anyway Log4OM is open to every choice also in this field, this is the main reason for our enormous list of options/settings :)

73
Daniele
Daniele Pistollato - IW3HMH
User avatar
G4POP
Log4OM Alpha Team
Posts: 11592
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: LOTW select issue 1.16.0.0

Post by G4POP »

I believe that most hams interpret the QSL sent status as follows...

N- no ........... This QSL has not been sent and is therefore waiting to be sent


I - ignore.......... Do not send a QSL for this QSO (I had four QSO's yesterday where the other station explicitly stated that I should not send a QSL so I marked the status I - ignore)

R - requested............... Although I have previously sent a QSL I have not yet received a return QSL so I have made a further request (Personally I think that this is a useless status and never use it, but we are stuck with itx)

Y - yes............... I have sent a QSL

Let's have some feedback from users on this please ASAP
73 Terry G4POP
User avatar
G4POP
Log4OM Alpha Team
Posts: 11592
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: LOTW select issue 1.16.0.0

Post by G4POP »

Daniele said....
The only way i see is to give an option to select what status will be load by the "select required" button..
This would, without doubt, be the best solution
73 Terry G4POP
User avatar
IW3HMH
Site Admin
Posts: 2988
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: LOTW select issue 1.16.0.0

Post by IW3HMH »

I agree with you that we should know how our users use this field :)
Daniele Pistollato - IW3HMH
User avatar
DF5WW
Log4OM Alpha Team
Posts: 2035
Joined: 02 May 2013, 09:49
Location: Kraam, Rhineland Palatinate, Germany
Contact:

Re: LOTW select issue 1.16.0.0

Post by DF5WW »

I´ve don´t use this field b4 but if it would be nice if there was loaded the not sent entries (N).

At the moment i check the LotW tab, klick on search and in the list i mark all unsend and load up to LotW ;)
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
k3dcw
Advanced Class
Posts: 72
Joined: 13 May 2013, 19:06

Re: LOTW select issue 1.16.0.0

Post by k3dcw »

G4POP wrote:I believe that most hams interpret the QSL sent status as follows...
N- no ........... This QSL has not been sent and is therefore waiting to be sent
I - ignore.......... Do not send a QSL for this QSO (I had four QSO's yesterday where the other station explicitly stated that I should not send a QSL so I marked the status I - ignore)
R - requested............... Although I have previously sent a QSL I have not yet received a return QSL so I have made a further request (Personally I think that this is a useless status and never use it, but we are stuck with itx)
Y - yes............... I have sent a QSL
Let's have some feedback from users on this please ASAP

Per the ADIF specification, there are different fields for the Sent and Received, with slightly different meanings. In particular, for the sent QSLs you are leaving one out: "Q"

Yes - QSL has been sent
No - QSL has not been sent
R - QSL has been requested (how is this different from "Y"?)
Q - QSL is queued to be sent
I - QSL is to be ignored or is invalid.

I mark any QSL I want to send via paper, LoTW or eQSL as "Q", meaning that it is queued up and ready to go. It is then a quick search for this value; once sent, it is switched to "Y" and I am good to go.

The ADIF default for QSL/LoTW/eQSL sent is "N". All of these values can be set in the Settings section of Log4OM. I set all new QSOs to default to "Q" for LoTW and eQSL, and all paper to "N". If I want to send a paper QSL, I will manually change it to "Q". That way I know it is waiting to be sent.

I think the "Select Required" button should search only for those marked as waiting to be sent, thus "Q". Of course, this works for me as it is how I already do my workflow. Perhaps the solution is to make this an option in the QSL Options section.

73

Dave
K3DCW
K3DCW
Elecraft K3
User avatar
IW3HMH
Site Admin
Posts: 2988
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: LOTW select issue 1.16.0.0

Post by IW3HMH »

I'm adding that option to the configuration section of Log4OM right now...
Luckily we're flexible to satisfy almost everyone :)

73
Daniele
Daniele Pistollato - IW3HMH
K7PT
Old Man
Posts: 723
Joined: 21 Jan 2013, 13:54

Re: LOTW select issue 1.16.0.0

Post by K7PT »

Dave asked what this means:
R - QSL has been requested (how is this different from "Y"?)

This means I asked the other guy for a confirmation card,
K7PT-Chuck "#1 Top of the Honor Roll"
Locked