[daisy] [JIRA] Resolved: (DSY-441) ImagePreSaveHook should have some way to trigger its execution in case the source part data has not changed

[Bruno Dumon (JIRA)]

     [ http://issues.cocoondev.org//browse/DSY-441?page=all ]
     
Bruno Dumon resolved DSY-441:
-----------------------------

    Resolution: Fixed

Fixed in SVN rev 3935.

Followed the strategy of checking for missing extracted data.

>From this it also follows that triggering the image-hook to redo its work can be done by deleting one of the parts or fields (not those assigned from exif) assigned by the imagehook.

> ImagePreSaveHook should have some way to trigger its execution in case the source part data has not changed
> -----------------------------------------------------------------------------------------------------------
>
>          Key: DSY-441
>          URL: http://issues.cocoondev.org//browse/DSY-441
>      Project: Daisy
>         Type: Improvement
>     Reporter: Bruno Dumon
>     Priority: Minor
>      Fix For: public - 2.0.1

>
> In Daisy 2.0, the ImagePreSaveHook was 'enhanced' to only redo its work when the part containing the image data changed.
> However, this makes it difficult to explicitly trigger the ImagePreSaveHook in cases like:
>  * an upgrade from a pre-1.5 Daisy is done
>  * the configuration of the image hook changed
>  * or some other reason (e.g. installing JAI) that would cause the image hook to behave in new ways
> The only way right now to do this is by making sure the image part data is changed, thus by effectively re-assigning the part data. While this works perfectly, it causes needless growth of the blobstore, and this is what this enhancement wanted to avoid in the first place.
> Possible solutions for triggering:
>  - some configurable field has some configurable value (e.g. ImageWidth is set to -1)
>  - or more generically, an expression evaluates to true on the document (using QueryManager.parsePredicateExpression)
>  - (add your own)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira