Extra features

[NN7D]

Terry, what we are talking about is not the lookup of data from QRZ or HamQTH, which is done when a callsign is entered into the Callsign field on the main Log4OM interface. But the ability to do an external browser lookup on QRZ of the subject station already in the log.

I believe the main reason that users are seeking to have this QRZ lookup on historical QSO's is to gain QSL, OQRS and mailing information on the subject contact. This is probably the top needed modification, in my estimation, for Log4OM, and I have been asking for it since I started using it 10 months ago. And it would be so easy to facilitate.

So we have the ability to do a QRZ lookup for the currently worked or about to be worked station using the Lookup button and Ext Browser checkbox on the right panel of the main Log4OM window. We have the ability to do a data lookup when importing from an ADIF file. Both of these are great to have. What we need now is the ability to do a clean, simple QRZ lookup on stations already in our log. Either by doing a right click on the QSO record, or by having a button on the Update QSO window, or both. These option should open up a new Ext browser window with QRZ with a search of the subject contact.

I am really looking forward to this function in the next version. Please!

Doug - W7DRM

[G4POP]

Doug,

Mike said:

I have loaded 1.19.0 and was disappointed to see that while additional options have been added to the context menu when right click on a Recent QSO entry, one can still not perform a "Lookup",

That I what I responded to, he does not ask for a browser to be opened, that would be something I could see some use for!

[G4POP]

Terry, what we are talking about is not the lookup of data from QRZ or HamQTH, which is done when a callsign is entered into the Callsign field on the main Log4OM interface. But the ability to do an external browser lookup on QRZ of the subject station already in the log.

I believe the main reason that users are seeking to have this QRZ lookup on historical QSO's is to gain QSL, OQRS and mailing information on the subject contact. This is probably the top needed modification, in my estimation, for Log4OM, and I have been asking for it since I started using it 10 months ago. And it would be so easy to facilitate.

So we have the ability to do a QRZ lookup for the currently worked or about to be worked station using the Lookup button and Ext Browser checkbox on the right panel of the main Log4OM window. We have the ability to do a data lookup when importing from an ADIF file. Both of these are great to have. What we need now is the ability to do a clean, simple QRZ lookup on stations already in our log. Either by doing a right click on the QSO record, or by having a button on the Update QSO window, or both. These option should open up a new Ext browser window with QRZ with a search of the subject contact.

I am really looking forward to this function in the next version. Please!

Doug - W7DRM

If you want to actually harvest the information you mention like mailing addresses etc from a browser window you would have to copy and paste from the browser window, isn't it easier to use the provided "QSO Update" facility for the historic QSO's?

Please do not miss-understand me, I am not against a selection to open a browser from the historic QSO's I am just trying to correctly understand why? because at this time the only reason I can see is just for some interesting reading from this proposed browser window option!

Or am I still missing the point?

[NN7D]

Hi Terry,

Thanks for the response. The reason I would really like to see a external browser QRZ look-up on historical QSO's is for several reasons. One reason is as you suggested for general curiosity about the station. But the the more practical reason is this: When I am working on confirming countries, bands or modes, I will open up Statistics and Awards, Country Status, then select a country, band or mode which I have worked and not confirmed. This will display a list of worked contacts. Now to decide which one of those contacts is the "best", or "easiest" to confirm! I start that process by looking up each contact in QRZ to see what their QSL policy is. This is sort of a hierarchical process which flows something like this:
1) If I find a contact which uses LotW, then I will make a note of that in their QSL tab, and probably wait to see if I can get LotW validation. To me, this is the easiest to confirm, so if this is the case, I will likely end the search right there.
2). If not above, then will look for hints of using OQRS system, maybe using Clublog, or direct paypal. If they offer that, will use that and end search. (By the way, don't know if this is possible, but it would be nice to have a Clublog lookup capability too!).
3). If not above, then will looks for direct QSL, or manager QSL information, get address, or manager, then look up manager, etc. Make notes in QSL tab of this information, then mark QSL Sent field as "Queued", for later label printing.

I do this for each contact within that country, band or mode which I might have a chance of confirming, to see which one I want to confirm. So if might require 2, 4 or 10 look-ups for each country, band or mode. No, I don't try to confirm each contact I make. It would be too expensive and time consuming for me, so I cheery pick.

All of these "look-ups" now require opening up QRZ in my browser, then coping and pasting the call sign into the QRZ search field. Not a big deal or one or two, but when you are looking up 10, 20 or 50 contacts at a time, it would be much easier if there were a QRZ, HamQTH, and maybe even a Clublook lookup buttons on the Update QSO window, or ability to right click on the historical qso record and do the same lookups.

So, button line, I use the look-up primarily to figure out 1) which contact will be the most efficient to confirm, and 2) to gain the necessary information about that contact to actually request a confirmation.

As you can see, its not just about getting their current address from QRZ or HamQTH, which can be gotten from using the Update info feature of QSO Archive window. And its not just for curiosity sake.

I hope that makes sense. Sorry for the long answer, and all the detail about my QSL process flow, but maybe someone has a better method for figuring out which contacts to confirm, and could tell me about it!

Thanks,

Doug - W7DRM

[NN7D]

Hmm, all this discussion may be over settled business. In this link to previous thread, Lele said it was on the list. It might have already been accomplished! We can hope!
http://www.pisto.it/forum/viewtopic.php?f=11&t=1154

Doug

[G4POP]

The reason I would really like to see a external browser QRZ look-up on historical QSO's is for several reasons. One reason is as you suggested for general curiosity about the station.

But the the more practical reason is this: When I am working on confirming countries, bands or modes, I will open up Statistics and Awards, Country Status, then select a country, band or mode which I have worked and not confirmed. This will display a list of worked contacts. Now to decide which one of those contacts is the "best", or "easiest" to confirm! I start that process by looking up each contact in QRZ to see what their QSL policy is. This is sort of a hierarchical process which flows something like this:
1) If I find a contact which uses LotW, then I will make a note of that in their QSL tab, and probably wait to see if I can get LotW validation. To me, this is the easiest to confirm, so if this is the case, I will likely end the search right there.
2). If not above, then will look for hints of using OQRS system, maybe using Clublog, or direct paypal. If they offer that, will use that and end search. (By the way, don't know if this is possible, but it would be nice to have a Clublog lookup capability too!).
3). If not above, then will looks for direct QSL, or manager QSL information, get address, or manager, then look up manager, etc. Make notes in QSL tab of this information, then mark QSL Sent field as "Queued", for later label printing.

I do this for each contact within that country, band or mode which I might have a chance of confirming, to see which one I want to confirm. So if might require 2, 4 or 10 look-ups for each country, band or mode. No, I don't try to confirm each contact I make. It would be too expensive and time consuming for me, so I cheery pick.

So, button line, I use the look-up primarily to figure out 1) which contact will be the most efficient to confirm, and 2) to gain the necessary information about that contact to actually request a confirmation.

As you can see, its not just about getting their current address from QRZ or HamQTH, which can be gotten from using the Update info feature of QSO Archive window. And its not just for curiosity sake.

Doug,
Don't ever worry about posting a long explanation, as you just proved the long explanation provides us with a much clearer insight than just "QRZ lookup" I have studiously re-read all of the post in this thread and the other one that you referred us to and they all seem to indicate that this right click feature was just for interested browsing - Not exactly high priority if I may say so!

However with your interesting and detailed explanation above I now completely understand the need to add a feature, but not necessarily just the "QRZ lookup' on selection from right click, that feature, as you have pointed out, has been noted already by Lele.

As a result of your last post I have a more realistic suggestion for consideration!

The API data received from QRZ when doing a lookup and also I believe from HamQTH contains "QSL by Mail", "QSL by Eqsl" and "LOTW user" (Yes or no) so we have the information when a lookup is carried out we just don't use it.

My idea would be to apply this information to some extra 'program specific' fields and display them in the Statistics/Country status screen as shown below. Plus an "Update" button for updating QSO's that perhaps have not been previously updated with this information

This in conjunction with a filter to select the Worked/Not confirmed (countries/bands/modes) only to avoid having to study the complete list of worked countries should make it more efficient.

Of course this is not 100% perfect and the is no OQRS data available at this time from QRZ or HamQTH but it should enable the bulk of the work to be streamlined?

We also download the LOTW User data from HB9ZA which is currently only used to highlight LOTW users in the cluster so we could combine that with the QRZ/HamQTH data which would help where the normal online lookup facilities do not contain the information.

Comments will be appreciated but with detailed explanations please
.
.
.

[G4POP]

maybe even a Clublog lookup buttons on the Update QSO window, or ability to right click on the historical qso record and do the same lookups.

I will have to check with Michael of Clublog about this because I don't know if he provides an API for this facility for external software.

Unfortunately, as you can see below, the Clublog Callsign Exceptions records that we can download do not contain this QSL/LOTW/EQSL/OQRS information but perhaps Michael might consider adding it!

<ExceptionRecord>
<End xsi:nil="true" />
<Start xsi:nil="true" />
<Latitude>45</Latitude>
<Longitude>-80</Longitude>
<Cont>NA</Cont>
<Ituz>0</Ituz>
<Cqz>5</Cqz>
<Adif>1</Adif>
<Entity>CANADA</Entity>
<Call>VE1ST/NA14</Call>
</ExceptionRecord>

[NN7D]

As a result of your last post I have a more realistic suggestion for consideration!

The API data received from QRZ when doing a lookup and also I believe from HamQTH contains "QSL by Mail", "QSL by Eqsl" and "LOTW user" (Yes or no) so we have the information when a lookup is carried out we just don't use it.

My idea would be to apply this information to some extra 'program specific' fields and display them in the Statistics/Country status screen as shown below. Plus an "Update" button for updating QSO's that perhaps have not been previously updated with this information

This in conjunction with a filter to select the Worked/Not confirmed (countries/bands/modes) only to avoid having to study the complete list of worked countries should make it more efficient.

Of course this is not 100% perfect and the is no OQRS data available at this time from QRZ or HamQTH but it should enable the bulk of the work to be streamlined?

We also download the LOTW User data from HB9ZA which is currently only used to highlight LOTW users in the cluster so we could combine that with the QRZ/HamQTH data which would help where the normal online lookup facilities do not contain the information.

Comments will be appreciated but with detailed explanations please
.
.
.

Terry, you may have something here. Although I don't think it will eliminate the need for the QRZ and/or ClubLog lookup in an external browser as we have discussed, it certainly has merit. As you said, its not perfect, at least not now, as some hams give conflicting data in the QRZ narrative from the QSL categories listed, and as you said, QRZ does not have a category for OQRS yet, but that could change. It could certainly eliminate some contacts from consideration, or cut down the time required to narrow the search.

I really like the idea of integrating the LotW user data with the qso record, that would definitely save some time.

I think its worth considering. Any others with thoughts on this??

Thanks Terry!

Doug - W7DRM

[KA4CDN]

Thank you Terry for your continued consideration of the lookup feature.

I'm not trying to do anything complicated at all. I just would like to be able to easily launch the external browser with the configured URL (QRZ or HamQTH) to see a previously worked station's page. It helps me remember the guy/gal if I can see their picture, station information, etc. I am not trying to update data in Log4OM by copying/pasting or anything else. I just want to see the station's page. Just like I can do from the Lookup button before I log the station into recent QSOs. It seems very easy to implement and uncomplicated to use/document.

So that and to be able to use different sources for the automatic data retrieval when you type in the call sign (in my case the data comes from HamQTH) and the 'Lookup' external browser source/URL.

Thanks again for Log4OM. Happy holidays to all the developers and folks here on the forum.

Cheers,
Mike