Media Mover currently supports 4 "verbs" - operations: harvest, process, storage, complete.

Sometimes, this is not enough. For example, if you are processing files from FTP, saving them as a node and then putting them into CCK, you need harvest, storage (save as a node) and complete (save to cck field). What we need now is to somehow respond to original uploaders using email. Therefore I was thinking about creating a new verb called "finish". However, this might not be enough again for some people.

What I propose to do is to create an universal framework, used in media_mover_api_verbs() function to define multiple operations. Media Mover API itself will then take case of running all of these cases and will implement a default "bypass" function for every verb.

Patch to follow.

Comments

arthurf’s picture

arthurf commented

I advise against this in media mover 1x. The DB is the limitation. Look at the 6.2x and 7x branches for where media mover is going- I don't think it's worth it to spend the time updating the 1x branch for this.

FYI, the 2x version does support this already. It needs more work, but the framework is there. The major issue is that D7 has a hook_file_load() which needs to be considered in the architecture.

arthurf’s picture

arthurf commented

I take it back. I've gotten further along on the 6-2x branch than I thought. While there are some serious considerations to be made in regards to D7 (uri handling, hook_file_load, etc), I'm thinking that it might be better to forge ahead with the 6-2x branch as much of it will be reused in D7 anyway.

meba’s picture

meba commented

I am closing this issue right now since it's already in 2.x version. Thanks anyway for feedback. Btw. would you have time to review #646686: How does harvest and storage/complete interact? ? Thanks!