[Dxbase] PJ and UA problem

Sat Sep 11 09:47:08 EDT 2010

 Offered as food for thought:
There is now a big database of calls with prefix exceptions, corrections, etc. 
that exists at clublog.org.
I don't think it would help in the time sensitivity issue you raise but it 
ultimately sorts this out almost with a "voting" process or the use of actual 
QSL cards.
Wes N7WS
On 9/11/2010 6:21 AM, Jack wrote:
> The concept of a downloadable reference data file for prefixes could
> certainly be done, but the success of this approach would be dependent on a
> number of factors:
>> 1. Time sensitivity ... user just works xyz station and discovers that the
> prefix selection is incorrect. Oh, and let's make it more interesting by
> saying he/she plans to submit this to ARRL at a hamfest tomorrow. What does
> user do.
> 2. Would user be able to make changes to prefix database without fear of
> the download file overwriting their changes. If changes are made, would
> user know what changed.
> 3. Callsign exceptions to the normal prefix selection. Zone exceptions,
> deleted vs not deleted.
> 4. Potential issues with cluster spots where incorrect prefix is selected
> if current logic is kept.
> 5. How would prefix data be maintained for QSOs... part of log or not part
> of log? At least one logging package out there does not keep the prefix as
> part of the QSO record. This is viewed by many of their users as a
> significant irritation. Personally, I wouldn't like it either.
> 6. Data corruption during download, download interruptions, version
> differences. Dumb users who won't recognize any of this or who just don't
> know how to download something.
>> Just some thoughts. I'm sure there may be other issues to reconcile in
> developing the plan. I'm not really asking for a response to the comments
> above, I just point them out as food for thought during the design of the
> changes that are planned.
>> Cheers Jack