[Archivesspace_Users_Group] API output - extra unicode

[Brian Harrington]

Hi Tom,

In my experience \u00c3 appearing in anything is almost always a sign of encoding issues.  I would make sure that everything is UTF-8 all the way through.

Brian

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Tom Hanstra <hanstra at nd.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Friday, September 3, 2021 at 11:06 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] API output - extra unicode

On our local version of ArchivesSpace, we are testing API output and are finding that we are getting extra Unicode characters on export. It looks like the data is right in the database, but doesn't quite come out right from the API extract. It looks like there is an extra unicode character added (in some of the code we reviewed, this was either \u00c3 or \u00a2).


Where might we have something set incorrectly?  Where might the extra data be coming from or have been introduced along the way?


Thanks,
Tom


--
Tom Hanstra
Sr. Systems Administrator
hanstra at nd.edu<mailto:hanstra at nd.edu>

[Image removed by sender.]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20210903/d7ba88d1/attachment.html>