Comment 1 for bug 1724321

Adding a clarification of the workflow that leads to a failure of duplicate detection. First of all, you have to have the config.global_flag named 'cat.bib.use_id_for_tcn' set to 'false'. In my testing after that setting was changed on a stock master server, if you search z39.50 for a title, select one, then click "Import", it will fail to import because it sees the already-existing TCN, but you will not see any messages in the UI (see bug 1724885). However, if you click "Edit then Import", it will take you to the editing screen, and clicking "Import" there does not prevent you from importing the record with the duplicated TCN.