Thanks for reporting this. The REST API uses the UNIXREF XML to generate the JSON. From looking at this discussion it seems like the issue is happening before the REST API gets the data, and at some point shortly after the metadata is deposited. The white spaces are swapped for line breaks. Curiously, though, for 10.1371/journal.pgen.1010373 the XML looks similar but the white space is included in the REST API, which would suggest that the issue is elsewhere. We’ll take a look.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| A way, per DOI, to get original metadata deposit XML? | 6 | 30 | September 29, 2025 | |
| SyntaxError: JSON.parse in Crossref API | 3 | 1466 | August 11, 2021 | |
| Is that normal to get <html> tags in title metadata? | 6 | 1029 | July 3, 2023 | |
| JATS elements in abstract (Is this the expected behaviour?) | 7 | 158 | September 12, 2025 | |
| Flies in your metadata (ointment) - Crossref | 6 | 1275 | August 2, 2022 |