Developer Wanted For Metadata Aware Image Uploading Module

Hmmm I was hoping to be able to do this during the day today (as I've been *really* bored) but you've posted a little bit on the late side and I'm packing up work now... I've not got much spare time this weekend but I'll attempt to mock up something, if not definitely on Monday - that's FINISHED on Monday at the latest just to give you a schedule.

It'll probably depend on having the image module installed, hope that's not a problem for anyone? Just seems a bit pointless to rewrite existing code.

As for payment, wait until I'm done with a 'first draft' and happy with what I'm putting out...

Thanks

Pobster

I mean "psuedo-image node" as the module currently creates an image node rather than a MAQUM node, so we're both on the right page with that part by the sounds of it. Just to break that down in case it's not clear enough; In order to get an entry on the 'create content' page you're required to "be" a new nodetype, so I've created 'MAQUM' as a new nodetype but when the node is submitted I've changed $node->type = 'image', so yes it's a regular image node.

Currently the module uploads a supplied image to the servers temporary directory and does all the footwork with categorizing it here using exiftool; here's a freebie:

function _MAQUM_exiftool($path) {
  $temp = shell_exec(variable_get('MAQUM_path', '/usr/bin/').'exiftool --list '.escapeshellarg($path));
  $temp = explode("\n", $temp);
  foreach ($temp as $item) {
    $plip = explode(':', $item);
    $info[trim($plip[0])] = trim($plip[1]);
  }
  return $info;
}

The idea next is to pass this already uploaded image to _image_insert which is (obviously) part of the image module. This will grab the uploaded image out of the temporary folder and process it attaching it to the node we've just created. The reason we don't do this ourselves is to keep up with progressions in image.module, this way we stay 'bleeding edge' so to speak... So if image.module is updated it doesn't make any difference to our code. I haven't done this part yet, currently the module creates a blank node of type 'image' which has a title and creation date gained from exiftool and is assigned metadata terms which already exist (creating new terms on-the-fly is easy enough, I just didn't manage to finish this part before I left work).

I wish you'd stop reminding me that you're an 'individual' and not some company, who the hell do you think I am??!! I'M AN INDIVIDUAL and the only reason we haven't discussed your requirements in depth is because at the VERY start I asked;

Okay, so assume I uploaded this photo 'freshly', you simply want it to be 'atuo-tagged' with taxomony terms gained from this information and have the date and time of the image nodes creation set as when the photo was actually taken??? Is that it? Is that all?!!

And well... You repeated what you'd written before just in a different way, so the answer was 'yes' then to - "is that all?" I don't see anywhere where you've asked for anything different to the module I'm writing? This post and your last one (which I'll confess I didn't fully follow as I'm not up on photography lingo, but then that's why I tried to give you an example to make sure I was on the same level as you) simply asked to have something which creates an image node which using Drupal taxonomy, categorizes the image with EXIF metadata gained from exiftool. Anyone who needs two months to complete a simple module like this is an idiot, this is a short module - it hijacks functions from image.module and uses routines which are present in already existing modules - the function I've included in this very post is more or less the only new piece of programming this module requires. This is a SHORT module, it's one full days work at the very most...

I write modules for free if I'm going to use them myself, but I've absolutely no interest in using this module. I only took this one on to help out, not particularly for the pocket money which I don't *need* at all - I've a very good job which doesn't have anything in the slightest to do with programming!

The module is for 4.7, but it's not the kind of module which will require any upgrading to 5.0 - you'll simply need to add a .info file and a menu item for the settings - that should be all.

Pobster