Wishlist: restore ability to generate alternate TCN when non-merging z39.50 import matches on existing TCN
Bug #2008488 reported by
Mackenzie Johnson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
New
|
Undecided
|
Unassigned | ||
Bug Description
Evergreen 3-8-0
It is my understanding that in older versions of Evergreen, when attempting to import a record via z39.50, if the recommended TCN matched against an existing TCN in the catalogue (and one was not trying to merge/overlay the records), a pop-up appeared that indicated this and provided the option to generate an alternate TCN for the record being imported. In EG 3.8.0, this functionality has been removed, with matches against existing TCNs only returning an error message, and any adjustments to make an alternate TCN have to be done manually (which of course takes more time). We are seeking for this functionality to be restored.
To post a comment you must log in.
