Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CDATA in abstracts #2132

Closed
hagbeck opened this issue Jan 17, 2025 · 3 comments
Closed

CDATA in abstracts #2132

hagbeck opened this issue Jan 17, 2025 · 3 comments
Assignees

Comments

@hagbeck
Copy link
Collaborator

hagbeck commented Jan 17, 2025

In our process for the data from lobid-resources, we convert the JSON data into XML. This works as long as there is no CDATA stuff in the JSON field. Our converter then turns CDATA into a double CDATA, which is not valid.
So my question is: can you make sure that the CDATA from Alma is not transferred in the JSON of lobid-resources?
I am well aware that the problem is actually already in Alma ;-)

Example: https://lobid.org/resources/99371026459206441.json CDATA in the abstract

Other fields are also affected, e.g. otherTitleInformation, location

@acka47
Copy link
Contributor

acka47 commented Jan 20, 2025

@TobiasNx can you please check whether we can remove this in the transformation process?

TobiasNx added a commit that referenced this issue Jan 20, 2025
TobiasNx added a commit that referenced this issue Jan 21, 2025
TobiasNx added a commit that referenced this issue Jan 24, 2025
@dr0i
Copy link
Member

dr0i commented Jan 24, 2025

Fix will be deployed next Monday.

@dr0i dr0i moved this from Backlog to Review in lobid-resources Jan 24, 2025
@hagbeck
Copy link
Collaborator Author

hagbeck commented Jan 27, 2025

Looks fine. Thanks!

@hagbeck hagbeck closed this as completed Jan 27, 2025
@github-project-automation github-project-automation bot moved this from Review to Done in lobid-resources Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

4 participants