Identify Primary keys

[GoogleCodeExporter]

vendor requests

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

[GoogleCodeExporter]

There is an absence of a keys. Certain keys are not
required in the current schema. Schema is the
lowest common denominator. We transfer it to a
customized Bowman Schema before we can import
it into our product. XSD is a standard for data not
databases.

Original comment by edward.p...@gmail.com on 21 Jun 2011 at 5:00

[GoogleCodeExporter]

There is a lack of key for on-going
data exchanges especially as it
relates to data quality issues.

Original comment by edward.p...@gmail.com on 21 Jun 2011 at 5:02

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Fully agree with this and add that it is related to issues 5 and 19. In this 
case though, there should be a Key element, required, on every Agency, Site, 
Service and ServiceSite element. Like my comments in item 5 for Agency Keys, 
the same rigor should apply for Site, Service, and ServiceSite elements:

Each Key should be uniquely correlated to a single entity, and that the Key 
should correspond to a permanent unique identifier in the source database 
(rather than, say, an ad hoc auto-incremented integer that can be different 
each export). This will allow Update transfers to work properly so that the 
update can be performed on the  correct record already imported.

Original comment by bleeb...@gmail.com on 9 Dec 2011 at 6:51

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Issue 19 has been merged into this issue.

Original comment by e...@ejahn.net on 18 Feb 2012 at 1:58

[GoogleCodeExporter]

Voted for implementation, and in 3.1 release.

Original comment by e...@ejahn.net on 18 Feb 2012 at 2:26

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by e...@ejahn.net on 23 Feb 2012 at 5:06

• Changed state: Fixed