In uploading records to our database we have encountered a similar error message with two datasets. In each case we got the same error message for several records that were unable to be uploaded but the rest of the dataset went through fine. Here is the message:
* Row 191 not uploaded: org.hibernate.exception.ConstraintViolationException: could not insert: [edu.ku.brc.specify.datamodel.CollectionObject].
The strange thing is, row 191 did upload as did all the records nearby it. We can tell that one record did not, as the resulting total is 1 less than the full dataset. But we are having a hard time figuring out which record did not upload. Can anyone shed any light on this?
That error almost always
That error almost always means that the row not uploaded had a catalognumber that had already been used. Specify's testing team has not found any problems with the reported row number, however there is a bug in that when you click the error message the next highest row in the dataset is highlighted.
If you sort the dataset by catalognumber you should find that the catalgnumber for row 191 is duplicated. Or, it could be that a record with the same catalog number as row 191 already existed before the upload.
dataset upload erro
Thanks so much for your reply. I suspected as much but couldn't figure out how to check the duplicated numbers.