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 | 45 | 29 September 2025 | |
| JATS elements in abstract (Is this the expected behaviour?) | 8 | 186 | 26 November 2025 | |
| UNIXREF XML API inserting incorrect whitespace between HTML-like elements | 3 | 45 | 1 October 2025 | |
| Is that normal to get <html> tags in title metadata? | 6 | 1057 | 3 July 2023 | |
| ISSN discrepancy between JSON and XML responses | 7 | 769 | 5 October 2023 |