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
For which schema is a change/update being suggested?
What should the change/update be?
The following fields should have their examples updated to reflect the acceptable value in the json file, rather than the user friendly inputs:
corresponding_contributor
drop_uniformity
paired_end
official_hca_publication
This update constitutes a patch change to the schema(s) it affects.
Why is the change requested?
As per the discussion going on in the PR https://github.com/HumanCellAtlas/metadata-schema/pull/1396/files#r665483651, it was pointed out that example field. of the properties should reflect the contents of the JSON files and not reflect the implementation of how the schema is presented to the user.
example
The text was updated successfully, but these errors were encountered:
No branches or pull requests
For which schema is a change/update being suggested?
What should the change/update be?
The following fields should have their examples updated to reflect the acceptable value in the json file, rather than the user friendly inputs:
corresponding_contributor
propertydrop_uniformity
propertypaired_end
propertyofficial_hca_publication
property (Not yet available, in PR discussion now)This update constitutes a patch change to the schema(s) it affects.
Why is the change requested?
As per the discussion going on in the PR https://github.com/HumanCellAtlas/metadata-schema/pull/1396/files#r665483651, it was pointed out that
example
field. of the properties should reflect the contents of the JSON files and not reflect the implementation of how the schema is presented to the user.The text was updated successfully, but these errors were encountered: