Open paul-aloisio opened 1 year ago
@paul-aloisio In this case, Jhove is returning <status>Unknown</status>
, which is being mapped to FITS as valid and well-formed. How would you like this mapped? Invalid and not well-formed? Omitted? Unfortunately, the options are binary in FITS.
Since jpylyzer correctly identifies the jp2 as invalid, this particular case seems less important if there's no clear answer. I am opening an issue with Jhove and connecting it to this one in which they unhandled exception is reported: https://github.com/openpreserve/jhove/issues/712
It would be best if Jhove just handled the error gracefully.
I don't know how many other cases there are in which Jhove returns status unknown.
And the same problem with Jhove was reported in 2015:| https://github.com/openpreserve/jhove/issues/16
Being reviewed by carlwilson in JHOVE issue:
https://github.com/openpreserve/jhove/issues/808#issuecomment-1372316795
In FITS 1.6.0 when Jhove encounters an unhandled exception while checking the validity of a JP2, the recorded response is still "valid and well-formed". There's information in a 'message' field, but that is not accounted for.
This is a section of the FITS output for the file linked below:
The entire FITS output and the console error are in the attached zip.
https://drive.google.com/file/d/1pzRxiFr_EK0IwWjTRgFr7WyGPLgu60jW/view?usp=share_link Jhove_FITS_JP2_error_output.zip