Comment 4 for bug 1968196

One solution would be to add a tsvector search index column for searchable acq fields containing normalized values. That's what we do for patron name searches: you're not searching the various name fields directly, you're searching the normalized values in the actor.usr.name_kw_tsvector column. With patron names the normalization is done using the evergreen.unaccent_and_squash function; that might suffice for acq search as well, but there are probably more robust approaches, e.g. https://www.2ndquadrant.com/en/blog/unicode-normalization-in-postgresql-13/