Current procedure for Callsign change at SOTA database, reflector, etc

[EA2IF]

Hi Andy @MM0FMF,
A number of one letter suffix callsigns have been issued in EA and I guess some of them are participants of the SOTA programme. At least 2 of them are friends of mine and I wanted to help them to manage their callsign change. A search on the Reflector took me to this thread and I just want to be sure that this is still valid now that we have the new database and the SSO.

Changing Callsign / Username on the database

Gentleman, It’s quite common for people to change callsigns. This can be because they have upgraded their type of licence, or they have moved QTH or they have been able to take up a vanity callsign or whatever. We are aware of this and so changing callsigns is handled by the database. When you enter an activation log you specify the callsign you used and this is normally the same as your own callsign. Some people have some cool SOTA club calls (NS0TA for example) and they can enter that callsi…

My two SOTA participants friends with new flamant one letter suffix are:
Alfonso EA4CWN ==> now EA4R
Ricardo EA4ZK ==> now EA4M

Could you please, confirm that the instructions in that thread are still valid for the new database and the SSO?
If they are OK but you still want to rewrite something to make it cristal clear, please, do it and I’ll prepare a translation of such instructions into Spanish to inform the EA community about how they should proceed after their callsign change, as I guess there may be more SOTA programme participants than my 2 friends needing to change their callsigns on their database and SSO, etc
Thank you and 73,

Guru

[EA2IF]

If I understand things right, what they should do is logging in SOTAwatch, after clic on the own callsign box displayed at the top right corner, clic on Update Account, the top one of the two options in the dropdown menu.

This will take us to the following page:

My understanding is that the new callsign holders should write their new callsign on the Callsign box which we can see highlighted in blue in the above image and write the previous callsign on the Alternative Callsigns box at the bottom of the page.
Is that right?
Is that all they will have to do?
Thank you.
73,

Guru

[G0CQK]

Users of the reflector are not currently managed by SSO but have to be changed directly in the reflector admin system so I have changed them and they now need to sign in with those call signs. Passwords remain the same.
Jim

[EA2IF]

Thanks Jim. So I assume they will have now to sign in to the Reflector with their new callsign, while they will still have to keep using their old callsign to log in to the database and all the sites managed by the SSO, right?
Can you also confirm whether the operations I described in my previous post for them to update their callsign are correct and that’s all they will need to do?
Thank you!
73,

Guru

[MM0FMF]

Is that right?
Is that all they will have to do?

Yes. It is important that changes go through this web page now and that SOTAwatch2 and the old database are going to be shutdown. Changes need to be made on here so that the correct server gets updated. It also means that other websites like SOTL.as and apps like sotaspotter etc. see the updates too.

And yes, it’s a bit of pain at present but that is what comes when you provide two dissimilar servers. It will get better!

[VK3ARR]

to keep using their old callsign to log in to the database

They may have issues using the old database if they update via SSO, in which case it’s a perfect time to try newsotadata if they aren’t already (old database will only be around for a little while longer)

[MM0FMF]

old database will only be around for a little while longer

Two Andrew’s speak with one mind!

[G8ADD]

Two Andrew’s speak with one mind!

Ruin for the hills!