Update SIP to handle foreign characters (diacritics)
SIP should handle foreign characters (diacritics) correctly. When a patron's name or an item's title has a diacritic then it throws an error. For some vendors, it breaks the application and prevents customers from logging in and/or accessing their checked out or held items.
Susan Millwater
shared this idea
There are configuration options in Polaris for adjusting the CharacterEncoding and ChecksumWidth with for the SIP service, which can be modified via Support tickets. It is also possible it disable the checksum validation in System Administration (not required for data integrity with the Polaris SIP service). These configurations should address all issues with diacritics and checksum errors.
-
Kristine den Boon
commented
As mentioned, this is really important for cataloguing World Language collections.
-
TJ Heffers
commented
Cataloging items for our World Language collections is really difficult and requires a lot of workarounds because diacritics are handled so poorly. Our library has a large number of patrons who natively speak Indian languages. We try to provide lots of books for them in their native language, but each new item in Hindi or Tamil risks breaking things.
-
Susan Millwater
commented
SIP should handle foreign characters (diacritics) correctly. When a patron's name or an item's title has a diacritic then it throws an error. For some vendors, it breaks the application and prevents customers from logging in and/or accessing their checked out or held items.