D
DaveNF2G
Guest
I think there are two discussions occurring here. Accommodating the Uniden HP-1 is one, proper content of RRDB alpha tags is the other. As the HP-1 does not use the alpha tag field, there should be no conflict.
Relationship between Alpha Tag and Description?
- Thread starter b52hbuff
- Start date
- Status
Alpha tags are described in the Database Administrator Handbook section 6.4. In short, they should be as specific and descriptive as possible in the space provided. Alpha tags "stand alone" and are not a more specific classification under the category, subcategory and description. "CLEMARS 01" is an acceptable alpha tag to the extent that it represents how the channel is known (i.e., it is not an arbitrary RR invention). Furthermore, RR alpha tags are intended for scanner users and in general should not be set to actual transceiver radio alpha tags unless they happen to be as descriptive as our requirements.
The Description is a specific entry under a category and subcategory. The problem that I see with the CLEMARS listings is that there is information captured in the alpha tag that is not captured in the description, subcategory or category. A more appropriate description would be "Ch. 01 (for VHF High-Band agencies)" or something along those lines. Remember, the alpha tag stands alone.
The Description is a specific entry under a category and subcategory. The problem that I see with the CLEMARS listings is that there is information captured in the alpha tag that is not captured in the description, subcategory or category. A more appropriate description would be "Ch. 01 (for VHF High-Band agencies)" or something along those lines. Remember, the alpha tag stands alone.
Thanks for weighing in. The 'standing alone' is a very powerful statement and would make a good addition to the DB Admin Guide. I've been reading it closely. One interesting observation is that Description doesn't get much treatment in the existing guide.
Alpha Tagging gets a section, 6.4.1. But this is all the document says about Description in that section:
If the frequency or talkgroup description is insufficient to provide enough information to create a unique alpha tag, then the frequency or talkgroup number should be included as part of the alpha tag to ensure uniqueness.
The other comment about Description, which seems to be routinely violated is in 6.1.3:
Avoid using any abbreviations in a conventional frequency or talkgroup “description” field.
One other item to clarify is from this newly added section:
3.6. DATABASE ENTITY NAMING POLICY
The RR database entities (e.g., frequencies, talkgroups, categories, subcategories, descriptions, alpha tags, etc.) should never be added, removed, named, renamed or changed to adjust them for a specific device, product or consumer of RR data.
Renaming is appropriate if it is to update the entity to the existing documented standards. I think this is important, because it is clear that 'current events' drives the current discussion and focus on the topic. However, focus should not be confused with goal. The goal is to have entities appropriately named, whether or not they are new or currently contained in the db.
Alpha Tagging gets a section, 6.4.1. But this is all the document says about Description in that section:
If the frequency or talkgroup description is insufficient to provide enough information to create a unique alpha tag, then the frequency or talkgroup number should be included as part of the alpha tag to ensure uniqueness.
The other comment about Description, which seems to be routinely violated is in 6.1.3:
Avoid using any abbreviations in a conventional frequency or talkgroup “description” field.
One other item to clarify is from this newly added section:
3.6. DATABASE ENTITY NAMING POLICY
The RR database entities (e.g., frequencies, talkgroups, categories, subcategories, descriptions, alpha tags, etc.) should never be added, removed, named, renamed or changed to adjust them for a specific device, product or consumer of RR data.
Renaming is appropriate if it is to update the entity to the existing documented standards. I think this is important, because it is clear that 'current events' drives the current discussion and focus on the topic. However, focus should not be confused with goal. The goal is to have entities appropriately named, whether or not they are new or currently contained in the db.
SuperC
Member
Alfa Tag/etc. Descriptions
Have been following this thread with interest. Speaking as an end user, I am thankful for everyone who provides accurate information and useful info into this site. I have been in law enforcement since 1971, after a stint in the Marines. I got my hands on my first scanner in El Paso Texas as a Marine. I am now retired, but still love to listen to scanners. I appreciate being able to pull up the info provided on Radio Reference. There have been times when I have been frustrated, but usually I have found that, listening long enough, I can usually figure out what talk group or frequency is being used for and what I might want to use as a label. Sometimes that is one of the interesting things of this hobby. I really appreciate being able to use software and download the information from the RR site. I then can change the information to what I know or believe to be correct by using software, and download it to my scanner. I want to thank every one of you who provide information and/or administer this site. Be kind to each other. As I have have recently learned, you never know when the fickel finder of fate might catch up with you.
Have been following this thread with interest. Speaking as an end user, I am thankful for everyone who provides accurate information and useful info into this site. I have been in law enforcement since 1971, after a stint in the Marines. I got my hands on my first scanner in El Paso Texas as a Marine. I am now retired, but still love to listen to scanners. I appreciate being able to pull up the info provided on Radio Reference. There have been times when I have been frustrated, but usually I have found that, listening long enough, I can usually figure out what talk group or frequency is being used for and what I might want to use as a label. Sometimes that is one of the interesting things of this hobby. I really appreciate being able to use software and download the information from the RR site. I then can change the information to what I know or believe to be correct by using software, and download it to my scanner. I want to thank every one of you who provide information and/or administer this site. Be kind to each other. As I have have recently learned, you never know when the fickel finder of fate might catch up with you.
- Status
Similar threads
