This document outlines the process used by RadioTime to identify and consolidate duplicate stations. A similar process applies to programs.
Duplicate Station Definition
- Duplicate stations are where the same content is transmitted from the same location. Two stations can’t share the same frequency and the same city. Exceptions include especially large cities and low power stations.
- Two stations with the same stream are duplicates or repeaters, or one of the streams does not belong.
- Multiple audio feeds from the same location should be multiple stations in the database (e.g. HD1 and HD2 stations from the same tower).
- However, where a station transmits the same audio from a different broadcast tower, all but the main station is setup as a repeater.
Duplicates are usually found by the following processes:
- Adding a stream for a station which is detected as a duplicate stream belonging to another station. One of the streams doesn’t belong, or the stations are duplicates.
- Scrubbing a location by correcting city and country information, then sorting on city + frequency or using the region map.
- Scrubbing a radio network by searching on the domain name to group stations together, then correcting names and call signs and sorting by name + location.
- Reviewing a list of duplicate candidates that is generated by comparing station information for near-match and likely duplicates.
Likely Dupe Report
This e-mail report shows likely duplicates with the reason why and a link to de-dupe or merge data.
Often the report shows clear duplicates. Others must be investigated further to confirm or fix the problem (e.g. the stream or location doesn’t fit the actual station).
Once a pair of duplicate stations has been identified, the duplicate form is used to consolidate their information.
Dupe Summary Form — What is On the Form?
The duplicate summary form shows key information from each station not otherwise visible, including: source maps, regions, streams, schedules, user favorites, recordings scheduled and other information. Proceed more carefully when you see dependent information, because the change updates other parts of RadioTime.
For example, if the duplicate record has region information and the keep record does not, then consider flipping the duplicate and keeper.
Dupe Summary Form Access — How Do I get Here?
The duplicate summary form is a version of the delete confirmation form. To access the duplicate summary form:
- Set the duplicate number for a station, and press save.
- Click the “delete” link on the top of the station form.
The duplicate summary form is also displayed by clicking the “de-dupe” link on an entry from the duplicate candidate e-mail report described above.
Only editors with delete privileges have access to the dupe summary form. Contact RadioTime if you need to process duplicates but don’t see a delete link on the top of the RadioMill station form.
Dupe Actions — What Happens?
Clicking “consolidate” updates any data from the deleted station that can be used on the keeper. For example, if a slogan is available in the deleted record and empty on the station that stays, the slogan will be automatically populated.
The system will merge genres, affiliates and streams. However, it will only update blank text fields. Be sure to review both stations, and manually adjust the fields and save before confirming the deletion.
Any related information from the deleted station listed above is also moved to the new stations.
Dupe Restrictions — What can’t be de-duped?
- Flat data like slogans are not merged. Empty data is replaced if available.
- Schedules are not merged. You can move an entire schedule, but you can’t combine partial schedules. Do this manually before de-duping.
- The top of the duplicate summary form will warn for other combinations that can’t be duped.
- Pairs that create a conflict with source maps can’t be merged. To fix, first delete the source map that is causing the problem. [David, this is difficult, let's scrub the rules to automate any possible].
- Merging repeaters is another special case. Combinations can’t be de-duped that will create a chain of repeaters. A picture of what’s possible and not:
- Two child stations with different parents – no
- Two child stations with the same parents – yes
- Non child station (delete) and child station (keep) – no
- Child station (delete) to non child station (keep) – no,
- Flip first, or swap the parentID and DupeID for the set
- Child to it’s own parent – no