De-duplication

[GoogleCodeExporter]

    * Scheme does not have a place holder to differential between geography served for data imports from multiple centers to put together a single composite site.
    * A mechanism to de-duplicate data for statewide systems so that records that exist in every system only appear once in the composite syste

Original issue reported on code.google.com by edward.p...@gmail.com on 21 Jun 2011 at 4:54

[GoogleCodeExporter]

There needs to more of an accurate
definition of geographic service areas.

Original comment by edward.p...@gmail.com on 21 Jun 2011 at 4:58

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

If I am understanding the issue correctly, I think moving to a Normalized 
structure (item 22) would accomplish this nicely. If not, at least including 
unique Keys  (items 5, 19 and 24) would help when importing to accomplish this.

Original comment by bleeb...@gmail.com on 9 Dec 2011 at 7:16

[GoogleCodeExporter]

Original comment by e...@ejahn.net on 20 Dec 2011 at 5:03

• Added labels: Group-Normalization

[GoogleCodeExporter]

This seems to us to be the responsibility of the importing vendor, not of the 
schema itself.  So, as Neil points out, as long as we include primary keys and 
require enough identifying information about the records, each vendor should be 
able to de-dupe as the import occurs.

Original comment by gglbwmn2...@gmail.com on 18 Jan 2012 at 5:12

[GoogleCodeExporter]

Voted for implementation, and in 4.0 release.  Probably needs to be merged into 
another existing issue.

Original comment by e...@ejahn.net on 18 Feb 2012 at 3:02

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by e...@ejahn.net on 18 Feb 2012 at 3:03

• Added labels: Milestone-Release4.0
• Removed labels: Milestone-Release3.1

[eric-jahn]

By resolving #37 and #22, we may have resolved this.