We're currently running image dimensions (width/height) extraction via the FileProcessorComponent in invenio-records-resources. This is useful to "pre-calculate" the dimensions while the record is still a draft and just copy over the result on publish.
Given though that this code runs in an async Celery task right after the file upload, we have the following issues:
The task might fail
The task might run too late, i.e. if a user quickly uploads a file and publishes (e.g. using a REST API client), the task will try to calculate the dimensions and store them on the draft image metadata.
To avoid this, we can use the new RecordFilesProcessorComponent, which runs on publish and can make sure to send off a task for calculating the metadata on the published record's files.
We're currently running image dimensions (width/height) extraction via the
FileProcessorComponentininvenio-records-resources. This is useful to "pre-calculate" the dimensions while the record is still a draft and just copy over the result on publish.Given though that this code runs in an async Celery task right after the file upload, we have the following issues:
To avoid this, we can use the new
RecordFilesProcessorComponent, which runs on publish and can make sure to send off a task for calculating the metadata on the published record's files.