If it is a training issue on our end (our admins have not updated data that you have submitted for these systems) then please let us know.
Ok, I'll bite. Is there a single, consolidated set of policies/instructions on how the data for each of the above systems is to be stored? I know I've seen some forum posts on specific, nuanced questions but don't recall a broad complete policy.
Trunked systems are pretty straightforward, I think. I think it is conventional data (and especially talkgroups on conventional channels) that I'm not so clear on. Although it would be helpful to see a write-up on standard procedures for the storage of all variations of DMR and NXDN systems.
And, I will add, I don't think the "complaint" (if you can even call it that) in this thread is that the DB doesn't have the capability to "store" this sort of data. Clearly we can "store" anything and everything in wikis, comments, notes and description fields. It's more a matter of optics - for better or worse, the DB doesn't currently appear to have an intentional design to accommodate and clearly/easily/consistently display this sort of data. Rather, it feels/appears more like this data has been stuffed in haphazardly. Here's an example: If MotoTRBO were the only kind of conventional or trunking radio that existed (pretend, for a moment, that analog, P25, etc. didn't even exist), would the RR DB be formatted the way it is to store the data useful to the rapidly-growing population monitoring MotoTRBO communications? Or would we have some additional/different tabular fields in the DB, for example?
I'm not arguing - I'm just explaining. It is what it is, and I confess I am no DB or web expert generally, and not one to take any sort of authoritative view on this. I'm just pointing out my observation of the DB's approach as it relates to the fastest growing radio technology out there right now.
Dan
