[Dxbase] Fw: [Club Log] Support for QSL state "Verified"

Mon Dec 10 09:17:52 EST 2012

Hi Jack,
In this case - the QSL_RCVD adif field name has had the standard out ever since
May 2008 with the adif 2.20 .. The standard reflects that the QSL_RCVD field can have:
QSL received status
 Y - yes (confirmed)
 N - no
 R - requested
 I - ignore or invalid
 V - verified 
ClubLog is just making use of the QSL_RCVD " V " within the database.
73 Joe wa6axe
> From: lennoxj at bellsouth.net
> To: al9a at mtaonline.net; dxbase at mailman.qth.net
> Date: 2012年12月10日 09:05:25 -0500
> Subject: Re: [Dxbase] Fw: [Club Log] Support for QSL state "Verified"
>> Gary,
>> As I read your comments regarding your desire on behalf of club log to
> change the specifications of the ADIF field definitions, it occurs to me
> that this is a very alarming trend. The entire intent of ADIF standards was
> to, well, have standards. Imagine if every software maker wanted their own
> unique coding for a particular ADIF defined field. We'd be taking many
> steps backwards to the days when no one who makes software adhered to fixed
> standards and instead we are left to trying to accommodate each and every
> logging program's data uniquely. Personally, I think this is not the
> direction that software makers should be taking. But perhaps "club log" has
> already obtained the approval of the ADIF standards committee for this
> unique coding to support their product, I don't know. But if not, this is
> alarming to me.
>> Cheers,
> Jack
>>> -----Original Message-----
> From: dxbase-bounces at mailman.qth.net [mailto:dxbase-bounces at mailman.qth.net]
> On Behalf Of Gary AL9A
> Sent: Sunday, December 09, 2012 11:17 PM
> To: DXbase Reflector
> Subject: [Dxbase] Fw: [Club Log] Support for QSL state "Verified"
>> I guess this one is for Neal...
>> I periodically upload my DXBase mdb as an adif file to Club Log. The
> following letter from Michael G7VJR explains a new enhancement to his Club
> Log files. To take advantage of this new enhancement in Club Log the adif
> output from DXB would need a modification in the QSL_RCVD and LOTW_QSL_RCVD
> categories. Instead of just QSL_RCVD=Y if this QSO has been accepted for
> the DXCC award the category would have to say QSL_RCVD=V for Club Log to
> recognize the difference between a QSL received and a QSL verified as
> already having been accepted by DXCC. Of course for this to work the Award
> field in DXB has to be set to the DXCC check box.
>> So what say Neal. Is this a big deal or a minor adjustment to the adif
> logic? It doesn't seem like that big a change. Just have the adif output
> routine check the Award field and if is checked for DXCC change the QSL_RCVD
> category from Y to V.
>> 73,
> Gary AL9A
>>>> ----- Original Message -----
> From: G7VJR
> To: clublog at googlegroups.com
> Sent: December 08, 2012 4:50 PM
> Subject: [Club Log] Support for QSL state "Verified"
>>> Hello all,
>>> I'm pleased to announce a new feature which should help busy QSLers to pick
> off the right cards for awards. 
>>> A little background first - as you may know, there are actually three QSL
> states defined in ADIF:
>>> Worked (QSL_RCVD = N)
> Confirmed (QSL_RCVD = Y)
> Verified (QSL_RCVD = V)
>>> Up to now, Club Log has only supported worked or confirmed (a paper QSL or
> LOTW QSL is sufficient). However, while we were chatting at the RSGB
> Convention, Alan 5B4AHJ proposed that it would be helpful if Club Log also
> supported the verified state, which is set when you have your QSL accepted
> and awarded by ARRL.
>>> I've added support for the verified status today, and have adopted a
> distinctive blue 'V' to represent this (I've attached a screengrab). This is
> most useful on the QSL Charts, where it can show you that you possess the
> QSL card and need to present it for awards.
>>> Caveats on this feature:
> a.. Your logging software must support the QSL_RCVD=V field in its ADIF
> exports. The mature DX loggers should be fine, but some won't have this
> feature. 
>> b.. This functionality relies on you actually setting the QSL's as awarded
> (very much depends on your logger but it's less common than QSL_RCVD=Y)
>> c.. You will need to upload a new ADIF to give Club Log this information -
> I didn't collect it historically, but have started to gather it now. Until
> you upload an ADIF with verifications, you'll see the normal
> worked/confirmed behaviour as usual.
> I hope this all makes sense and I hope the new blue verifications are
> useful!
>>> vy 73
> Michael G7VJR
>>>> --
> To post to this group, email clublog at googlegroups.com For more options, see
> http://groups.google.com/group/clublog
>>>> ----------------------------------------------------------------------------
> ----
>>> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 201302793 / Virus Database: 2634/5946 - Release Date: 12/08/12
> ______________________________________________________________
> Dxbase mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dxbase
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Dxbase at mailman.qth.net
>> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>> ______________________________________________________________
> Dxbase mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dxbase
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Dxbase at mailman.qth.net
>> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html