I have to throw my hat in (again) on this growing problem as it's as old as the hills and getting to be a bigger problem if anything. Back in the days of RM3 and prior identical Places were automatically merged, the only thing we really had to worry about was duplicate events.and sources, now we have several contributors and the more we interact and sync with outside sources this can only become a greater problem, so what can RM deal with.
Places: One could easily say that identical Places in respect of Place/Std..Place/Abbre..Place should automatically merge but what about media and Notes which may be identical, complimentary or conflicting? I believe all Rootsmagic or any programmer could do, and should do, is write a utility which presents these seemingly duplicate entries side by side for user decision/interaction, that alone would be a step forward. A further step forward and a desirable feature in any quality program would be to employ the option to apply some fuzzy logic like Duplicate Search Merge to present Places side by side which MAY be duplicates.
Duplicate Search Merge: Presently whilst this very useful utility does not create duplication the process or merging does and every merged individual deserves examination and likely warrants editing at the time of merging. At present the way DSM works does not promote this, nor does it allow the dropping or further examination of events side by side. I have posted a wish for this some years ago and remain hopeful that the next incarnation of DSM more closely resembles the UI of File Compare. At present I merge in small batches and go back over each merge to clean up the information as can be seen here at time code 4:40 , pity I hadn't been so disciplined years ago.
Sources: These continue to be a problem further exacerbated by the introduction of Source Templates which Rootsmagic does not merge even when identical. The problem of Source Duplication can be seen demonstrated here and this also needs to be dealt with in the next version release.
Facts/Events: Well this has been around the longest and whilst Rootsmagic could and should be able to deal with identical duplicate facts they are invariably different in quality or attachments. The Print people with more than one of these facts is a broad brush with no concern as regards Dates so not always very useful except for the likes of Birth and Death dates. Whilst on the subject I have wished some time ago for the option Create Group under the Facts/Print options which would an easy addition and would help deal with Text Dates etc in a more productive manner. The script TomH linked to is very useful in creating a Named Group of all those individuals who have duplicate events of the same year so it will catch those events Jerry described with one fact date being 1848 and the second being 12 Oct 1848.
The management of duplicate information should be a key consideration within any prefessional database program. The failure to manage such duplication progressively reduces the effectiveness of the database, the searching and utilities which analyse the data leaving users bogged down in manually dealing with duplication rather than helping them progress their research, this is a recurring theme on these boards.