Encoding problem when uploading RDF to triplestore Blazegraph

Open
#6 1 comment 0 reactions 1 assignee View on GitHub

@fils is already working on this.

Since Sep 23, 2023.

Assessment

This issue has not been assessed yet.

Description

We use Gleaner CLI and follow the procedure at https://book.oceaninfohub.org/indexing/cliDocker/index.html with Minio Client and minio2blaze script. Data for indexing are being encoded in UTF-8 and are generated dynamically, for example http://20.124.232.205:8081/api/json?projectId=2, and we have a sitemap with all the projects for indexing at http://20.124.232.205/pr/sitemap.xml (test version).

Gleaner is working fine and with minio client we checked Spanish accents:
image

But when uploading RDF to the triplestore the accents are converted to "??" characters in the blazegraph client and the endpoint:
image

We tried to set the UTF-8 encoding in the minio2blaze (curl -X POST -H 'Content-Type:text/x-nquads; charset=UTF-8'), create a temporary file to save the stdin of the minio client and secure the UTF encoding and then pass it to the triplestore and finally, changing the JAVA_OPTS in gleaner-IS.yml to include some flags by a comment on blazegraph's github (https://github.com/blazegraph/database/issues/206#issuecomment-1623798570), but we are unable to display any accents.

Thanks in advance

Dominant language
CSS
Stars
4
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gleanerio/archetype

All issues in gleanerio/archetype

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.