Here are the two versions. One I get by using the staff interface ‘export’
button. The other via the api.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
On Behalf Of
Majewski, Steven Dennis (sdm7g)
Sent: Friday, March 27, 2020 3:08 PM
To: Archivesspace Users Group
Subject:
By directly, I mean when logged into the staff interface and use the Export
menu option. This results in the correct character, but not if I try via the
API, against the same instance.
[cid:image002.jpg@01D6044C.D1150690]
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
On
And maybe send the resulting XML or at least diffs of the two.
( Guessing that there might be a mismatch of file encoding and xml encoding
declaration. )
> On Mar 27, 2020, at 3:02 PM, Mayo, Dave wrote:
>
> Can you be more precise about what “directly from the archivesspace” means?
>
Can you be more precise about what “directly from the archivesspace” means?
What page (URL) and control on the page you’re using to generate this? I want
to make sure it’s the same code path in both cases.
Also, when you say “locally,” do you just mean the script is running locally
against
Hi all –
Today I noticed that if I export an EAD with “Yin-Hsü” directly from the
archivesspace, my EAD results carry through with the correct encoding.
But, when I export locally via the API, I end up with “Yin-Hs端”. I’m using
python 3.7.4, via local windows machine. I’ve tried both
