[DogParkList] SWL QSL Ideas

Fri Jun 9 14:56:22 EDT 2006

Hi all,
I am a Contester (& to a lesser extent a DXer), but I used to be a  
SWL too :)    And many of my ideas for MLDX are not contest-specific!
I agree with Aaron's point in his email below, about QSL tailoring  
for SWLs, and would extend that to support for users like me to  
manage and respond to SWL QSLs too.   In fact this was part of a way  
too long list of ideas I sent Don many moons ago and he rightly  
pointed out that I was probably the only one who had requested such  
features!   Anyway now would seem to be the right time to revisit  
some of these QSL ideas for MLDX Cocoa again - anyway I lay 4 of them  
out here for others to consider too.

1) SWL report QSL management:
A first that I have not seen supported in any other QSL management of  
logs would be support for SWL cards received.  An extra tickbox field  
could be added which is ticked when a SWL card is received for that  
QSO.  This could then cause slightly different printing of the QSL  
card/label details when the batch is run for sending so that the card  
is tailored for a SWL reply.  One would want to capture that a SWL  
card has been received (potentially more than one for the same QSO),  
but also when it has been replied to (sent) and what the number of  
the SWL is (his "callsign"), so maybe the tickbox is not the answer -  
maybe a link (by QSO ref number in the main log) to a separate log  
file for listener reports is appropriate, which could be searched  
against when a QSL batch is run.

2) Batch QSL management & extensions to QSL card printing:
So the use case is ... after each contest/special event (where other  
- e.g. used by a club which is PC-bound :( specialist contest logging  
software exports ADIF logs) the log from that event is imported via  
ADIF into MacLogger, to add to the previous entries from previous  
contests/events for that callsign.  Then periodically, QSLs are  
received (via the bureau in batches in envelopes, direct in the post  
or electronically via eQSL) for QSOs which are in the aggregate log.
The need is to be able to
	- search through the log quickly by call and then by date and time  
to find the QSO(s) which each card received refers to
	- then  to record a "received" status against the incoming card (do- 
able now in MacLogger - Y in QSL received field) but a "Pending"  
status in the QSL sent field (maybe "P").
This process is repeated over a period (weeks or months) as QSLs  
arrive, recording them in the aggregated log.  Then periodically,  
when I have enough to make it worthwhile, I want to print a batch of  
QSL cards or Labels etc. to send an outgoing batch to the bureau for  
example.  (For a small contest group like mine, although we want to  
honour all QSLs received 100% returned, it is uneconomic to just QSL  
100% for all contacts made so hence we wait for incoming cards before  
responding.)

Then the need is to automatically print QSL cards or labels (to stick  
on pre-printed cards) for all those QSOs which have QSL sent set to  
"Pending".  The QSL card printing facility would ideally allow  
printing 4 to a sheet of card in landscape mode, inserting the  
relevant details from the log for each contact in turn.  I think this  
would mean extending the QSL card layout customisation a bit over  
what MacLogger already allows.  At the same time, I want the software  
to automatically set the QSL sent fields contents for all the cards/ 
labels that have been printed in that batch from "P" to "Y".   
Actually maybe we could have more of a range of status letters like D  
for direct, B for Bureau M for via manager, E for electronically etc.?

3) Multiple QSO details per QSL:
Another thing that would be great is to be able to group QSO details  
for one station worked many times (on different bands for example) on  
a single QSL card that is printed (up to whatever maximum is sensible  
for the size of card!).  I currently waste a lot of card to send  
print separate cards to the same station for various QSOs with that  
station from the aggregate log, often just for QSOs on different  
bands/modes on the same day/weekend.

4) Event specific details for QSO number ranges within the aggregate  
log:
When I import the ADIF log for a particular contest/event, I use the  
comments field to say which contest/event it was, and from what site  
I operated - it would be good to be able to add this info to the QSL  
card so that the contest name for the contact can be acknowledged  
(e.g. "Tnx fer ???? contest QSO" and any locator information (e.g.  
from JO01MX / IOTA EU-005 / ITU Zone ?) can be correct on the printed  
card.  Maybe this is better implemented by an optional table that can  
be maintained where the QSO numbers ranges in the log can be assigned  
session name (for contest or special event name), and various locator  
references and then these used to display the data on cards/labels or  
on screen (auto populating a field).  People who only use the  
software for the normal logging from home etc could have this table  
auto set to the same default values for all QSOs in the log (although  
it would enable them to track historically what contacts they make  
from holiday locations or when they move house!)
The SRX field already allows extra data to be printed on a card -  
this would simply extend that further.

73 all.
Jonathan G0DVJ
--

On Jun 8, 2006, at 11:00 pm, Aaron G. Prosser wrote:

> I am a SWL and new user of MacLoggerDX, and would love to see a  
> feature whereby I could indicate on the QSL that I received a  
> station, rather than stating that there was a QSO.
>
> Aaron G. Prosser
> WA4098SWL
> http:\\wa4098swl.googlepages.com
>
>
> On 7/6/06 00:02, "Don Agro" <dagro at dogparksoftware.com> wrote:
>
>> It's started !
>>
>> The redesign of MacLoggerDX for Cocoa has begun and I invite any and
>> all to post requests or suggestions.
>>
>> There will be a Contest mode and a DX mode with appropriate changes
>> to the data entry procedures for each etc.
>>
>> Even if you have just been 'lurking', feel free to comment on other
>> submissions or send in your new ideas - now is the time :)
>>
>>
>> 73 Don Agro VE3VRW
>>
>> D o g   P a r k   S o f t w a r e   L t d .
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://two.pairlist.net/pipermail/dogparklist/attachments/20060609/7be9a706/attachment.htm