Future of MAQUM - Drupal 6 and image vs. imagefield
pobster - June 10, 2008 - 10:31
| Project: | MAQUM |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
You can add me as a maintainer if you like - I assume this is the same module I wrote for you? I don't mind updating it for the 6.x branch, let me know!
Thanks,
Pobster
#1
Hi Pobster,
I've made some changes to it, but finally got around to creating an actual project for it so everyone else can download it.
I was actually waiting to see how the entire imagefield/CCK vs. image module thing plays out for Drupal 6. I was thinking of upgrading MAQUM to D6 and in the process, switching it from relying on image module to relying on imagefield/CCK. Assuming that CCK with an imagefield takes over from a simpler, plain image module, rather than have each IPTC field and EXIF field be created as taxonomy terms within their own vocabulary, maybe the future of MAQUM is mapping EXIF fields and IPTC fields (the metadata in the images) to CCK fields.
I'm not sure if this would be better or worse than using taxonomy, possibly just plain different.
This weekend I'm hoping to create a screencast for the module and link to it from the project page.
#2
It seems like in addition to image being merged into imagefield/imagecache, there is also talk of ending imagefield in favor of filefield with an image helper (more). So for this reason, a Drupal 6 version of MAQUM looks best to be postponed.
#3
subscribing... (I might be in favour of a image-version rather than the CCK-one (because i'm unfamiliar with it))
#4
In the interim, if I wanted to get MAQUM working with imagefield/imagecache, instead of with image, how could I do it?
#5
You might want to look at filefield and filefield image, instead of imagefield, though it really is up to you. See #275011: MAQUM in Drupal6 for some links regarding the future of image handling in Drupal 6
and why I'm hesitant to just pick one way of doing it.As for how it would be done, I think the phrase you need to look out for is programmatically creating CCK nodes. Here's a bunch of likes you can use to get started:
Programmatically creating CCK nodes in PHP (interaction with the Path module) | sacha chua
Programmatically create a node with CCK fields? | groups.drupal.org
Programmatically Create, Insert, and Update CCK Nodes | civicactions
I don't think it should to too hard to switch gears, my concern is constantly switching gears, no one wants to do that.
#6
It looks like long term (Dripal 6+), the better bet is MAQUM relying upon imagefield and putting the metadata into CCK fields (as opposed to creating a vocabulary for each metadata field, as is currently done). The exception being the IPTC field, keywords, that should be a taxonomy vocabulary that is set up for tagging.