1

Topic: Rejected imports - Grid Reference

While importing a set of data from a spreadsheet, I received the message that 6 records had been rejected. The error messages provided did not provide any clue what the problem was: For example:

Items rejected by Recorder 6 in data imported at 20-35-06 on 02/08/2016:
Created SQLSERVER_SURVEY_EVENT
Created SQLSERVER_SAMPLE
Exception on create for SQLSERVER_TAXON_OCCURRENCE: ODBC--call failed

Failed to insert DSS007180000ZJZ7 into TAXON_OCCURRENCE
Database Error Message:
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_TAXON_OCCURRENCE_SAMPLE". The conflict occurred in database "NBNData", table "dbo.SAMPLE", column 'SAMPLE_KEY'.(-2147217873) The statement has been terminated.(-2147217873)
Note: This record may have been rejected because of a parent record that was also rejected.
--------------------

On checking all the imported records, I found that two records had not been imported. It would help if more meaningful error messages could be provided so as to quickly finding where the problem lies.

On entering the records by hand, I discovered that the Grid Reference had a typo and was 12 digits long instead of the intended 10 digits.
Surely that a valid Grid Reference had been provided should be part of the basic checks that are performed on the first page of import.

Harry

Harry Clarke
Surrey County Butterfly Recorder

2

Re: Rejected imports - Grid Reference

I agree that this report can be is difficult to interpret and that some way presenting it in a more user friendly format would be useful. Improvements in recent versions of R6 mean that rejections at the final import stage are now very rare so I m not sure how important improving this is now. However changes in 6.25 which allow the import of Locations with no grid refs can create situations which can not be trapped at the validation stage so improving the rejection reporting may become more important.

Grid refs are checked at the validations stage, but obviously not the length. Adding a validation for this is a very simple change and should be included in release 6.26

Mike Weideli