You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Failed to PUT data registry record with ID "dist-dap-9908911". 4 retries left. Status code: 400, body:
{
"message": "#/issued: [] is not a valid date-time. Expected [yyyy-MM-dd'T'HH:mm:ssZ, yyyy-MM-dd'T'HH:mm:ss.[0-9]{1,9}Z, yyyy-MM-dd'T'HH:mm:ss[+-]HH:mm, yyyy-MM-dd'T'HH:mm:ss.[0-9]{1,9}[+-]HH:mm]"
}
Failed to PUT data registry record with ID "dist-dap-9908911". 3 retries left. Status code: 400, body:
{
"message": "#/issued: [] is not a valid date-time. Expected [yyyy-MM-dd'T'HH:mm:ssZ, yyyy-MM-dd'T'HH:mm:ss.[0-9]{1,9}Z, yyyy-MM-dd'T'HH:mm:ss[+-]HH:mm, yyyy-MM-dd'T'HH:mm:ss.[0-9]{1,9}[+-]HH:mm]"
}
Describe the bug
magda-dap-connector generates date string that doesn't match JSON schema for dcat-dataset-strings aspect
To Reproduce
Deploy
magda-dap-connector
with config:Make sure
validateJsonSchema
option istrue
to turn json validation onThe text was updated successfully, but these errors were encountered: