Consider / implement a strategy for avoiding duplicate entities

[mpresteg]

Consider / implement a strategy for avoiding duplicate entities (Population, Cohort, etc). Perhaps a hash scheme to be implemented in the service(?). Need to define default behavior when a duplicate is detected (silently use existing OR return error)

[mpresteg]

A near time strategy may be to implement a bot that can evaluate and react to new submissions, providing feedback upon them.

[mmaiers-nmdp]

Make the name field constrained to be unique in the database

[mmaiers-nmdp]

And propagate errors to the service and from there to the UI as appropriate