-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comments
@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
Merged
Fix will be deployed next Monday. |
Looks fine. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: