This sounds similat to Australian clubs, which may have multiple
callsigns under their administration. Firstly, there's often a club
callsign, which is used for club nets, special events, sometimes contest
and field day stations operated as a club. And like your situation,
repeaters have their own callsigns, typically one per site.
I can see this ending up similar to domains, where club and other
"special" subdomains have multiple contacts, similar to what you have
when you register a domain - administrative contact, technical contact,
etc. Individual callsign subdomains simply become a special case where
all those contacts are the same person (ie callsign holder), which is
obviously a lot less administrative overhead.
Over here in Australia, we also have to deal with the fallout of major
administrative changes where non assigned amateur stations (basically
everything except repeaters and beacons, which have frequencies assigned
to them at specific sites) no longer have individual licences and
operate under a class licence, provided the operator has amateur
qualifications and an allocated callsign. The issue is for some of us,
proving we're qualified is still not easy, as existing licence holders
like myself didn't receive a formal certificate when we transitioned to
the new system. All we got is an email from the ACMA stating our
qualifications and allocated callsigns that carried over from the
individual licences.
On 16/6/24 12:32 am, Rob PE1CHL via 44net wrote:
I brought that up before.
The way I expected it to work was that I could manage a number of different callsigns
on behalf of our club or organisation or whatever you want to name it. But I would still
login under my own personal account, which would get access to some different callsigns
which are then also subdomains of
ampr.org.
I do not seem to understand how it is working now. At first I was asked to make an
account
for our club, but then I need to login using the credentials supplied for that account,
and I do not like that. It also causes confusion, because when I make a ticket I get the
usual "your ticket has been updated" mail which does not have much info, but
when I then
click on the link to the ticket I just get "ERROR" and it took a while before I
realized
that this was becuase the mail was about a ticket for the club, and I cannot access it
unless I login "as the club".
Then, there also is the issue of the number of callsigns. Apparently it was envisioned
that a club would have a single callsign, and that one could attach that to the club
account,
and for flexibility it would be allowed to have up to 5 callsigns.
But our club has way more than that! We operate several repeaters, and unlike the
situation
in the US repeaters do not operate under a personal or club callsign, but have a unique
callsign per repeater. This even used to be different for the same site on different
bands or
modes, but that requirement has been lifted by the authorities. So now for new repeaters
we
can use the same callsign on 2m, 70cm, 23cm, FM, DMR, D-Star, Fusion etc. Before that
was
not the case so we still hold a lot of callsigns for all permutations of that, and for
callsigns that have been changed in the meantime there still are legacy
"aliases".
So basically there is a requirement for a "club" (or "organisation"
or whatever) that is
responsible for maintaining HAM infrastructure, including repeaters etc, and holding a
reasonable number of callsigns (5 is too limiting). And it should be possible to make a
regular user an admin for the club, so they can perform changes for that club from their
user account with their own password and 2FA. There can (and should) be more than one
admin
for a club, and it should be possible to see which admin made a change, if not
immediately
in the user interface then at least on query to the
ampr.org admin (via a ticket).
(note that I was not suggesting it would have to be that complex. the simple method of
having one or more local coordinators who can enter the data as necessary was a lot
easier)
Rob
On 2024-06-14 19:49, Dave Koberstein via 44net wrote:
In our ARES/RACES organization we'd be
interested in having at least 2 people being able to have access to a subdomain. That
would enable a backup in case of SK, travel, or whatever issue might arise. Of course
sharing a login works also, just a little less secure and harder to manage 2FA.
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org