more attributes for slotGroups

[Fusselwurm]

Hi, I've been thinking about using slotlist.info as backend for our very own slotting tool for some time now.

To not lose features however, I'd need to be able to store some more attributes with the slotGroups – among others: radio frequency, tactical symbol, organisational level (company|platoon|squad), and parent-child-relations.

(For illustration, this is how it looks on our site)

Is this something you'd feel comfortable to accomodate or accept PRs? If necessary, I'd be happy to get a field where I can store a JSON blob or something :D

[MorpheusXAUT]

Hey,

additional info like radio frequencies and tactical symbol/organisational level (although they'd have to be as "independent" from a single country as possible, e.g. using the NATO standards or likewise) would be relatively simple to add.
Parent/child relations would also be possible, but would require a bit more work, especially on the front-end part.

I currently don't have lots of time due to work (and DCS 😄 ) unfortunately, so it might take a bit for me to finish implementing this - especially since there's a few other things I started working on that'd need to be done as well then.
I'm more than happy to accept PRs though (given they're appropriate, obviously). If you feel like contributing and speeding up development, please go ahead, I'd greatly appreciate it!

Regarding the use of slotlist.info as a backend for another, custom made slotting tool:
You're more than welcome to use the slotlist.info backend for that (I assume you've already found the API documentation), just be advised that all API requests (like registering for a slot, etc) currently use relatively short-lived auth tokens (expiry 3 days), issued for the user performing the Steam SSO login. Furthermore, the OpenID return URL would redirect users to the slotlist.info frontend to complete authentication.
I've started working on a fixed, "API token" authentication, however this type of authentication can currently only be used to retrieve (read-only) mission details. Up until now, I haven't had time to implement a user-based fixed token login that could e.g. be used to work with a completely "independent" frontend.

Happy to discuss this in more details via Discord (e.g. on the slotlist.info Discord) or likewise!