[Evergreen-catalogers] Setting to generate an alternate TCN when importing a z39.50

[Mackenzie Johnson]

Hi everyone,

One of the staff in my unit has had an issue with z39.50 imports that match against a pre-existing TCN (and not attempting a merge/overlay), as I've documented on Launchpad here: https://bugs.launchpad.net/evergreen/+bug/2008488

As being provided an option to automatically generate a TCN when otherwise faced with a match apparently used to be a feature, I am wondering if it is possible that this functionality is hiding behind a setting somewhere -- I was looking in the documentation and couldn't really find anything, but maybe there's somebody out there who is using 3.8.0 and is still able to use this functionality when importing z39.50 records.

Regards,

Mackenzie Johnson, MLIS
(he/his/him)
Metadata Librarian
University of Prince Edward Island
Email: mtjohnson at upei.ca
Phone: 902-620-5290
ORCID: 0000-0002-9358-5081
Book an appointment with YouCanBookMe<https://mackenziejohnson.youcanbook.me>

UPEI is located on Mi'kma'ki, the unceded territory of the Mi'kmaq people.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-catalogers/attachments/20230224/76f00b5c/attachment.htm>