Strip incompatible characters from patron feed before processing
Our IT department occasionally produces a patron load XML that contains small amounts of non-ascii characters. Currently a single character in a Brazilian mailing address, for example, stops the entire load. I think the behavior should be that any unrecognized character needs to be stripped out by Exlibris so the rest of the SYNCHRONIZE job can proceed, and the locations of the stripped out characters should end up in a warning.
3
votes
Matt Lawson
shared this idea