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
The current volume metadata file validation is performed in two steps. First, the format-specific validation is performed in recognizesFile(). Second, the validation of the parsed metadata is performed.
The first validation step is not implemented very well because a user uploading a malformed file only gets a message "file is not valid". We should implement a mechanism for metadata parsers to return more meaningful error messages for the validation (e.g. "category x is missing the name attribute"). The recognizesFile() method can be replaced with a validate() method that may return a special MetadataValidationException with a message that is passed on to the frontend. Any other exception is handled like an unexpected server error.
The text was updated successfully, but these errors were encountered:
The current volume metadata file validation is performed in two steps. First, the format-specific validation is performed in
recognizesFile()
. Second, the validation of the parsed metadata is performed.The first validation step is not implemented very well because a user uploading a malformed file only gets a message "file is not valid". We should implement a mechanism for metadata parsers to return more meaningful error messages for the validation (e.g. "category x is missing the name attribute"). The
recognizesFile()
method can be replaced with avalidate()
method that may return a specialMetadataValidationException
with a message that is passed on to the frontend. Any other exception is handled like an unexpected server error.The text was updated successfully, but these errors were encountered: