baybum
Member
What exactly were the changes made with these, and can explanations be documented in the future?
Explanation of Database Changes
- Thread starter baybum
- Start date
Not sure. I wish people would post in the forums the changes they intend to submit to provide a documentation trail. I also think the RRDB should be more descriptive in their change notes, marking exactly what was changed.
mc48
Member
I believe It shows you what changes were made, Changed site names from #003 to 003, #002 to 002 and #001 to 001, the # was removed.
- Joined
- Sep 15, 2012
- Messages
- 401
Typically when it says stuff like that, it's behind-the-scenes changes, such as changing the order the frequencies shown on a site or changing the lat/long of the site or any of the other meta-data of a specific site. It doesn't go into much detail when changing site details except when changing the site's name (not the case here).
No, that's not what was changed.
Likely. The point is the edit needs to be more specific, because a change in site NAC for instance, could easily be missed and render a radio using site NACs deaf. A range change could also be problematic because Uniden radios that are using location based scanning could be affected, particularly if Favorites list are being used (a database change does not get written to Favorites lists.) A user would need to update a Favorites list manually, and if they don't know what change, it is a PITA.
Last edited:
MCJONES2013 is correct. It is usually housekeeping / behind-the-scenes changes. Nothing that usually affects the user experience. The change log notes are system generated. It is not something that we enter or can elaborate on.
baybum
Member
Maybe not, but an explanation could be provided in the forum.
So are you saying that a change to a range setting or site NAC would be noted? It doesn't get highlighted in green. Changes are something that needs to be better documented / more descriptive, even if it is impossible to do so today.
Some further info here:
DB Updates and Highlighting
Folks, we have had a lot of discussion of late in reference to highlighting on the DB maps and not seeing any changes when following the highlight from map. As such please refer to the following before you ask any questions or decide to be critical. The following uses the United States, but...
Changes in NACS, frequencies, etc would be noted by the system (the same with talk group adds or changes, etc) - that could affect the user experience. This specific instance might have been an internal note for other admins, an add of an FCC call sign, adding neighbor sites, etc.
Sometimes there are many changes to the DB that come into the submission system. Honestly it would be up to the DB Admin as to if they had the time or desire to elaborate. However the admin that made the change is listed. You can always send them a PM conversation and ask.
Sometimes there are many changes to the DB that come into the submission system. Honestly it would be up to the DB Admin as to if they had the time or desire to elaborate. However the admin that made the change is listed. You can always send them a PM conversation and ask.
baybum
Member
So this isn't a matter of IF it can be done, but whether or not the admin has time or wants to do it.
Admins are not required to post any notation of DB changes in the forum. Sometimes it is done. It is up to the individual admin and the circumstances of the change. There are many times that a change of a TG or system starts in the forum by a listener and ultimately is sent to the admin as a submission. Therefore it would be redundant to re-post that change.
Last edited:
"If you still don't see a change, refer to the History page to see what happened. The history will reflect what has happened; however, some of those explanations are somewhat confusing so:
- If the history reflects something was deleted, check against your individual records/programming to see what was deleted.
- If the history reflects something was changed, but it seems to be something that doesn't make sense, just ignore it. (e.g. "6 frequencies updated, 0 frequencies deleted") It indicates something was done that has nothing to do with how it affects you as a scanner user.
- If neither of these seem to offer you a satisfactory explanation, then contact the DB Admin that did the update for further information."
1 & 2 had Neighbor lists changed/added, 3 had the NAC Added AFAIK
Mr_Boh
Member
Also with the call ingest project and future enhancements to it on the way, there have been changes to better support that service since a lot of the metadata tagged with traffic is automated. So I have seen changes on systems in the DB being used for the project that show lots of updates although on the surface to the average user, or folks with commercial scanners that reference the RRDB see no change to site channels, talkgroups, etc.
Yes, I believe these are the changes that I made.
I'll try to document changes better through forum posts, but sometimes the changes are awfully small, such as adding a site NAC, updating neighbor lists, etc.
Dave
Recent changes to MD trunked systems:
Anne Arundel, Charles, IWN, NASA Goddard - location changed to "Various"
JNCR - Naval Academy control channels changed from alternates to primaries (blue to red)
Dave
Anne Arundel, Charles, IWN, NASA Goddard - location changed to "Various"
JNCR - Naval Academy control channels changed from alternates to primaries (blue to red)
Dave
More changes to MD trunked systems:
AstraZeneca - MedImmune - location updated to remove redundancy
Calvert P25 - callsign corrected
Howard - callsigns added
University of Maryland, Baltimore - system name changed to conform to MD university naming system
Worcester - location changed to "Various"
Dave
AstraZeneca - MedImmune - location updated to remove redundancy
Calvert P25 - callsign corrected
Howard - callsigns added
University of Maryland, Baltimore - system name changed to conform to MD university naming system
Worcester - location changed to "Various"
Dave
LOL, a number of Calvert licenses are in danger of being terminated because of failure to update their construction status. The do expect to be online with their new P25 system in the Fall.