I'm using The PHP JPEG Metadata Toolkit (GPL of course)
I'm enjoying it because it also supports XMP - which is the future, and fits with my manufactured images. XMP has a semantic specification - better than the random tags that EXIF used to create.
I've got a metadata extractor in dev - that transfers such metadata from files directly into alts, image.module nodes, CCK fields, text overlays on imagecache derivatives, and captions and things. Still in experimental phase, but PJMT is a good start.
I tried to use Exif with Node Gallery, but I couldn't get it to work. The CCK-fields which are configured to be filled by exif-module are not shown. When editing an 'image'-node and saving it without changes there are shown some errors:
* warning: exif_read_data() [function.exif-read-data]: Not a file in /var/www/web610/html/drupal/sites/all/modules/exif/exif.class.php on line 63.
* warning: Invalid argument supplied for foreach() in /var/www/web610/html/drupal/sites/all/modules/exif/exif.class.php on line 65.
I'm not sure if this is a bug in exif-module or in node gallery. But because of the CCK-fields work fine if I create a 'image'-node manually (not throughout node gallery) I think this is an issue of node gallery...
when I try to use the EXIF module, I get an error
(The Function exif_read_data is not available on the system.)
I enabled the php_exif extension, still looking for the solution.
php 5.2.9-2
So I tried this out. It should work from the integration part, but it requires manual work. You have to create a field on the image type for every exif information you want to show. This is just how the exif module works. For us it would imho be better to create a contrib module that calls exif_read_data() if it exists and extracts some hard-coded fields if existing.
In the interest of keeping feature creep from getting out of control, I'll mark this particular issue as fixed. The OP now has an EXIF solution. I don't think too many users would use a submodule, but feel free to create a new issue if so.
Comments
Comment #1
kmontyI don't believe there is. Does anyone possibly know of a good module we could leverage?
Comment #2
dman commentedI'm using The PHP JPEG Metadata Toolkit (GPL of course)
I'm enjoying it because it also supports XMP - which is the future, and fits with my manufactured images. XMP has a semantic specification - better than the random tags that EXIF used to create.
I've got a metadata extractor in dev - that transfers such metadata from files directly into alts, image.module nodes, CCK fields, text overlays on imagecache derivatives, and captions and things. Still in experimental phase, but PJMT is a good start.
Comment #3
dbeall commentedmaybe? http://drupal.org/project/maqum, currently works using image.module
from the project page.
A Drupal 6 version is planned, but based on imagefield instead of image.
last commit was June08 for D5.
Comment #4
blackfox commentedI tried to use Exif with Node Gallery, but I couldn't get it to work. The CCK-fields which are configured to be filled by exif-module are not shown. When editing an 'image'-node and saving it without changes there are shown some errors:
I'm not sure if this is a bug in exif-module or in node gallery. But because of the CCK-fields work fine if I create a 'image'-node manually (not throughout node gallery) I think this is an issue of node gallery...
Comment #5
kmontyI think in version 3.x we'll integrate with CCK ImageField, which will make getting exif data easier.
Comment #6
dddave commentedJust to put this back on the map.
Comment #7
scroogie commentedSomeone should try using the Exif module with NG3. It's probably just a matter of showing the values on the full node view.
Comment #8
dbeall commentedwhen I try to use the EXIF module, I get an error
(The Function exif_read_data is not available on the system.)
I enabled the php_exif extension, still looking for the solution.
php 5.2.9-2
Comment #9
scroogie commentedIs the exif extension listed in phpinfo()? If you're in windows, you have to enable mbstring as well.
Comment #10
scroogie commentedSo I tried this out. It should work from the integration part, but it requires manual work. You have to create a field on the image type for every exif information you want to show. This is just how the exif module works. For us it would imho be better to create a contrib module that calls exif_read_data() if it exists and extracts some hard-coded fields if existing.
Just my 2 cents.
Comment #11
justintime commentedIn the interest of keeping feature creep from getting out of control, I'll mark this particular issue as fixed. The OP now has an EXIF solution. I don't think too many users would use a submodule, but feel free to create a new issue if so.