[OhQP-mail] OHQP LOGGING BEST PRACTICES

[K9TM]

>From a log checking perspective, just log the callsign (k8mr or k8xx in
the below examples). 

The log checking does not need to know /m, /r, /county-abbr from the
callsign field... 

The log checking software gets the QTH from the QTH part of the exchange
(both sent and received). 

Some logging software is brain dead with respect to duping and does not
look at QTH must match for dupe and that's why some people enter
call/county-abbr... to make their logging software happy for duping. 

73, Tim K9TM 

On 2020-08-17 12:29, Bob wrote:

> What are  your recommended best practice  for logging  qso's with /m and /r stations? 
> 
> What   saves the most time for  the mrrc team when  reviewing/editing logs? 
> 
> Hypotheical Examples: 
> 
> * Could  a qso with  k8mr/m  be logged k8mr/m  or k8mr/Athe?
> 
> * Could a qso with k8xx/r  be logged K8xx/r  or k8xx/lake?
> 
> Ive done all those at different times over the years. 
> 
> Or doesn't it matter? 
> 
> FWIW I use N1MM+ for logging purposes and during  test entries, they all seem to work. 
> 
> Bob 
> 
> W3HKK 
> 
> The all-wire antenna  farm in Licking County 
> 
> 160-80-40-20-15-10m 
> 
> PS  Bank cndx  seem to  be much improved the past couple of weeks  for both  dx and domestic sigs.  Hope NVIS on 40m comes back this year  and  lets us hear most OH counties again, like it  did a few years ago. 
> 
> Have  a safe trip to all who will be  out and about. 
> 
> Sent from Mail [1] for Windows 10 
> 
> _______________________________________________
> OhQP-mail mailing list
> OhQP-mail at ohqp.org
> http://mail.ohqp.org/mailman/listinfo/ohqp-mail_ohqp.org
 

Links:
------
[1] https://go.microsoft.com/fwlink/?LinkId=550986
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ohqp.org/pipermail/ohqp-mail_ohqp.org/attachments/20200817/b776189d/attachment.html>