A few weeks ago I managed to upload a DOI record in the .json format. This worked OK. Now when I try, the system complains about “badly formatted XML”. What is going wrong. Is it possible to upload in json?
Hello,
Thank you for the post, and welcome to Crossref community forum.
Please share with us the submission ID that you received for this failed deposit.
We will have a look at the submission and advise further once you get to share it.
Best,
Evans
3 Likes
Hi, thanks for getting back. Submission ID (eg) is https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1675321990 .
Neil
Hi Neil,
Thanks for sharing the requested information.
We do not support metadata deposits in JSON format. Our content registration tool only accepts metadata deposits in XML format, and the XML files must align with our schema.
You can view the best journal article XML example here best-practice-examples/journal.article5.3.0.xml · master · crossref / Schema · GitLab, and schema guide here Schema documentation for crossref5.3.1.xsd
Please let us know if you have any additional questions.
Best,
Evans
Thanks for this. But I did manage to deposit several DOI records in json earlier this month – this one for instance
https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1670553820
Best Neil
Thank you Neil for the prompt response.
This last deposit you made with submission ID 1670553820 was registered via the new journal registration form, and the metadata we received was in an XML format (not json).
That said, the new journal registration form has been designed to allow you to download and save your record to your local computer for future edits, and the record will download as a .json file which is named automatically after the journal’s e-ISSN (or p-ISSN if no e-ISSN is available) and article title. This json file can be loaded back into the form at a later date to make changes to your record. I believe this is what you meant by saying that you have a json file that you uploaded in your last deposit.
Please go though our documentation guide on how to use the record registration form here.
Best,
Evans
1 Like
No, I have never uploaded any XML data. I have uploaded several json files successfully (although this no longer works). An example json file that was successfully uploaded follows. You can see the result here https://doi.crossref.org/10.69894/857284 .
Neil
{
“recordName”: “OITJ20230111”,
“recordType”: “journal-article”,
“formData”: {
“journal”: {
“titles”: {
“fullTitle”: “Oil Information Technology Journal”,
“abbreviatedTitle”: “Oil IT Journal”
},
“journalTitle”: [
{}
],
“issn”: {
“onlineIssn”: “1634-0590”
}
},
“issue”: {
“issue”: “278”,
“volume”: “28”,
“publishedOnline”: “2023-12-31”
},
“article”: {
“articleTitle”: [
{}
],
“contributors”: [
{
“role”: “first-author”,
“sequence”: “first”,
“givenName”: “Neil”,
“familyName”: “McNaughton”
}
],
“abstract”: [
{
“language”: “en”,
“abstract”: “OSDU at The Open Group. Plans for 2023. How "open" is the "open" subsurface data universe? M15 Release and the geospatial consumption zone. OSDU and the incumbent data stores. OSDU in retail (?!?)”
}
],
“funding”: [
{}
],
“publicationDates”: {
“publishedOnline”: “2023-12-31”
},
“title”: “OSDU Update”,
“doi”: “10.69894/857284”,
“resourceUrl”: https://oilit.com/2023+1+11
}
},
“fileName”: “OITJ20230111.json”,
“schemaName”: “Crossref Journal Article Schema”,
“schemaVersion”: “1.0.0”,
“recordExtension”: “json”
}
Hi Neil,
It’s possible that there has been an update to the journal article registration form since you downloaded this JSON file that has caused it to not be accepted anymore. We have tried to avoid this but I can’t entirely rule it out - I’m very sorry about that!
Although you’re right that the form accepts JSON data, it does automatically convert that data into XML before sending it to our deposit system. That’s why we received XML from your submissions even if you’ve never had to touch that format yourself.
I’ve tried to generate a new JSON with your data by entering it in the form and downloading it - could you see if this one works for you?
1634-0590 OSDU Update.json (979 Bytes)
2 Likes