Comment 6 for bug 1353036

I have a better understanding of what you are doing.... I still would not use the Z39.50 interface this way because of the potential for duplicating a record in your database.

The problem isn't that the OCLC based TCN in your local catalog contains the nonnumerical characters, but that you need to filter them out in a Z39.50 search.

It sounds, then, like you have a wishlist request:

In the Z39.50 interface, when the local catalog is checked, both with and without choosing a Z39.50 source, TCN searches within the local catalog should filter out all nonnumerical characters.

The problem I see with this is for those libraries that do not have OCLC access and are searching other Z39.50 sources. TCNs in those sources may have nonnumerical characters that are retained within Evergreen, meaning they would not want to filter out those characters if searching local and nonlocal catalogs.

Since I am not a developer and don't know the under the hood parts, I don't know that development would be able to focus specifically on OCLC searching without a lot of structural changes to the interface so that OCLC searching with local catalog searching is treated differently from other Z39.50 searches. Filtering for just OCLC tcns here may be really complex.