I would like to clarify my previous message, since I mixed some concepts… sorry…
Jhove is used for retrieving the Preservation Metadata of a file. In case we are uploading a Photoshop image, as Jhove doesn’t recognise this kind of file, it just sets ‘application/octet-stream’ value to mime type attribute and default values to format and status attributes.
Regarding the Ingest Image workflow, this workflow is triggered during the upload file process, if the file’s mime type corresponds to one of the mime types associated to the Ingest Image workflow. I don’t know if I have understood the whole process, but it seems that the mime type of the uploaded file is provided by the browser, isn’t it? For example, when uploading .fff files, Internet Explorer sets the mime type as “image/tiff”, which is right, while Firefox sets it as “application/octet-stream”.
The problem of this approach is that the behaviour of the application depends on the client browser. I wonder if there is a proper way to identify if a mime type is correct or not, and then, in case it isn’t correct, a way to update it correctly. What do you think? I think that it can be very useful, at lest when uploading images, since the mime type determines if the Ingest Image is triggered or not.
Thanks for your help.