Troubleshooting
An import created the same record twice
Why uploading a file again created new drafts instead of updating the existing records, and how to clean up the extra records.
A bulk import recognises an existing record only when the Source system name and the source_id value
match together. If no match is found, the row creates a new record. Check the reasons below.
The rows have no source_id
Each row without a source_id value creates a new record on every upload. The dry-run report shows the warning
"No source_id: importing this row again would create a second record." on these rows. Write each record's ID from the old system into the file, then upload it.
The source system name is different
If you uploaded the file with a different Source system name than the first time, the records do not match. Always upload files from the same old system with the same name. The name used in the first upload appears below the file name in the Earlier imports list.
The old record was deleted
Records in the trash are not taken into account for matching. A row uploaded again with the same source_id creates a
new record. If you want to use the old record, find it with the Show deleted filter in the
Publications list and restore it before the import.
The similar record warning was overlooked
If the catalogue has a record with the same title, type and year, the dry-run report marks the row with a warning. The warning does not stop the row. Before importing, look at the With warnings count and the warnings on the rows.
A row whose ISBN or DOI value is used in another record, on the other hand, is invalid and is not imported. On journal rows the ISSN and e-ISSN are checked the same way. Records with these identifiers are not created twice.
Cleaning up the extra records
The extra records are drafts. The link in the report's Title column opens each record. Delete the extra drafts as in Deleting a Catalogue Record.