Log4OM

Hi,

Today I found a situation that I would like to expose. It seems an error...
I have in alerts the call K1N.
Today I have received an alert with K1N Rule however the call were HK1N. Than I tested with somes spots such us: ZK1N, AK1N, KK1N and even K1NX, it seems that the rule is for containing "K1N" and not for call only equal to K1N.
I created another alert Rule Call= AA1RO I make a spot with the call TRAA1KO and also I have an alert
In my opinion it is not correct, could you please check if you got same behavior.

Log4OM Version 1.20

Many thanks for your attention.

Hi Manuel,
Sorry for the late reply but somehow I missed your posting

You can reduce the issue by adding more filtering to the Alert

If you add the continent as NA and while testing with the cluster spot tester the country as United States (the spot tester does not do a complete lookup so for testing purposes you need to use US) the alert will not be triggered by spots like HK1N, ZK1N, AK1N etc - Change the country filter to Navassa when you have finished using the cluster spot tester.

Hi Terry,
Many thanks for your reply.

As always your comments are very helpful , however I would like to ask if it should not be not more convenient that when we have a call it should respect the exact call without the need to increase filter conditions.
That's only my point of view, because with your reply, it helps and I thank you for your suggestion.

Greetings from Portugal with a beautiful sunny morning and birds singing outside, is spring coming for our joyfulness.

CT1BXX wrote: however I would like to ask if it should not be not more convenient that when we have a call it should respect the exact call without the need to increase filter conditions.

As I said the only way we could do this would be to provide a user selectable choice of "Exact match"

Comments from other users please

I agree with Manual. Exact match is what it should be.

I personally suggest that the exact match should preferable by default , not only in alert but also in all other search functionalities , and use of wild cards (for example % or *) for wider matching

Exact match...
how you manage IW3HMH vs IW3HMH/P with exact match?

I would suggest that IW3HMH and IW3HMH/P are two different call signs as would K7PT/P5 and K7PT/I.

mmmh this works well on some cases...
less better on other cases...
we should evaluate how many times there is a callsign overlap compared to the Whole set of callsigns... 3 letter calls are really rare...
let me think about, maybe an option can help...

Has to be a user option as I said in an earlier post