We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
data_file
.yaml
.json
Other data file extensions than .yaml and .json are currently accepted by the validator (e.g. .yalm) but these data files are then not included in the tarfile prepared by the hepdata-converter-ws-client package (see this line). Consequently, file conversion fails with a FileNotFoundError error message from this line of the hepdata-converter package. An example is https://www.hepdata.net/record/85727?version=2 (data files with extension .yalm) fixed in https://www.hepdata.net/record/85727?version=3 (data files with extension .yaml).
.yalm
hepdata-converter-ws-client
FileNotFoundError
hepdata-converter
A "pattern": "^.+\\.(yaml|json)$" should be specified for data_file in the JSON schema:
"pattern": "^.+\\.(yaml|json)$"
hepdata-validator/hepdata_validator/schemas/1.1.1/submission_schema.json
Line 26 in bfcd4fd
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Other data file extensions than
.yaml
and.json
are currently accepted by the validator (e.g..yalm
) but these data files are then not included in the tarfile prepared by thehepdata-converter-ws-client
package (see this line). Consequently, file conversion fails with aFileNotFoundError
error message from this line of thehepdata-converter
package. An example is https://www.hepdata.net/record/85727?version=2 (data files with extension.yalm
) fixed in https://www.hepdata.net/record/85727?version=3 (data files with extension.yaml
).A
"pattern": "^.+\\.(yaml|json)$"
should be specified fordata_file
in the JSON schema:hepdata-validator/hepdata_validator/schemas/1.1.1/submission_schema.json
Line 26 in bfcd4fd
The text was updated successfully, but these errors were encountered: