Topic: De-Duplication
I am in the process of trying to get a handle on potential duplicates that have found there way into our R6 database over the years.
Just to check i am assuming the H1 and H2 reports pull out all records found to duplicate each other (as opposed to not reporting on an 'original').
It would also be useful to get an idea of how other users are dealing with 'in-db' duplicates. Has anyone established bulk methods of identifying and 'de-activating' these observations? It would be good to establish rules for the process i.e. where a verified version exists it is retained and setting some surveys as preferential over others.