curl -X POST "https://demo.borealisdata.ca/api/dataverses/myL/datasets?doNotValidate=false" \
-H "X-Dataverse-key: c5a4ca99-2cfc-4392-897b-76b10c9e38fd" \
-H "Content-Type: application/json" \
-d @payload.json -v
as well as the validate API which returns that the JSON is valid,
curl -H "X-Dataverse-key: c5a4ca99-2cfc-4392-897b-76b10c9e38fd" \
-X POST "https://demo.borealisdata.ca/api/dataverses/myL/validateDatasetJson" \
-H "Content-Type: application/json" \
--upload-file payload.json \
-v
any assistance would be great, thank you.
Colin Spetz
myLaminin
A quick guess would be that the server doesn’t have the dataverse.api.allow-incomplete-metadata setting set to true and that there is/was a bug in v6.4 w.r.t. sending an appropriate error message (I think there was also a solr schema change in ~v5.14 that is required to make the incomplete metadata setting work). Borealis may be able to find info in their server.log to confirm/invalidate that guess.
If you want to try your call against demo.dataverse.org, which is v6.6 and does not have that setting true, we can verify if it’s a current bug (in which case adding bug report to github.org/IQSS/dataverse would help get it fixed.)
-- Jim
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
dataverse-commu...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/dataverse-community/7bd86a21-93ff-4ca8-ab99-0afcae7c1531n%40googlegroups.com.