If there is a UTF-8 encoding issue in the database, When the post is done in the ArchivesSpace Client, possibly use the same mechanism that is used in the Archon migration tool:
In the Archon post method, see this line (https://github.com/archivesspace/archon-migration/blob/cfc9abe534e5c19b47de364625bab8535556cf31/src/org/nyu/edu/dlts/utils/ASpaceClient.java#L160):
post.setRequestEntity(new StringRequestEntity(jsonText, "application/json", "UTF-8"));
The corresponding line of code in the AT post method is (
|
post.setRequestEntity(new StringRequestEntity(jsonText, "application/json", null)); |
):
post.setRequestEntity(new StringRequestEntity(jsonText, "application/json", null));
If there is a UTF-8 encoding issue in the database, When the post is done in the ArchivesSpace Client, possibly use the same mechanism that is used in the Archon migration tool:
In the Archon post method, see this line (https://github.com/archivesspace/archon-migration/blob/cfc9abe534e5c19b47de364625bab8535556cf31/src/org/nyu/edu/dlts/utils/ASpaceClient.java#L160):
post.setRequestEntity(new StringRequestEntity(jsonText, "application/json", "UTF-8"));
The corresponding line of code in the AT post method is (
at-migration/src/org/archiviststoolkit/plugin/utils/aspace/ASpaceClient.java
Line 166 in 55c4e7f
post.setRequestEntity(new StringRequestEntity(jsonText, "application/json", null));