Metadata files uploaded using the SCP Metadata convention are validated for the following properties:
- Metadata names
- must exactly match the name in metadata convention for metadata to be added to the query database
- are case-sensitive and must also case-match the conventional metadata name in the schema
- non-metadata convention names may only have alphanumeric characters or underscore
- Ontology terms must
- be correctly formatted ("<ontology name>_<numeric ID>" or "<ontology name>:<numeric ID>")
- example: MONDO_0000001 or MONDO:0000001
- exist in the expected metadata ontology, validated through EBI OLS.
- supply the human-readable label ontology label for the provided ontology ID, if the metadata is Required (<metadata attribute>__ontology_label <- note the usage of double underscore)
- be correctly formatted ("<ontology name>_<numeric ID>" or "<ontology name>:<numeric ID>")
- Ontology labels - exact match to the label in EBI OLS is preferred, ontology synonyms are accepted.
- Metadata with controlled lists (type = enum) must exactly match one of the enumerated values.
- Metadata provided must match their type declarations in the metadata convention.
- Array-valued metadata must be delimited with the pipe symbol (|)
How to upload your metadata file with the metadata convention (File upload wizard interface):
By default the Portal requires that metadata files meet a particular convention and so the button for using that convention is defaulted to "Yes". If for some reason you are not able to use the convention there is a link to reach out for help in the upload wizard.
Visit our metadata validation errors FAQ for information on common metadata file issues and solutions.
Return to metadata convention main page
Comments
0 comments
Please sign in to leave a comment.