Piwigo Bugtracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000174Piwigometadatapublic2005.10.15 14:022005.10.19 22:15
Assigned Toplg 
PlatformOSOS Version
Product Version1.5.0RC1 
Target VersionFixed in Version1.5.0RC2 
Summary0000174: use_exif_mapping is not taken into account during metadata synchronisation to update database
Descriptionuse_exif_mapping may describe other field than date_creation when using an extended config_local.inc.php
$conf['use_exif_mapping'] = array(
  'date_creation' => 'DateTimeOriginal',
  'author' => 'Artist',
  'comment' => 'ImageDescription'

In that case, we would like to have these fields updated as for IPTC in the update_metadata() function.
this code: $update_fields = array_merge($update_fields,
is also good for EXIF.

A problem may occur when both EXIF and IPTC are used. Need a way to choose one or the other in the config file ?
Additional InformationThanks a lot to all the team for its very good work!

Waiting for RC2....
TagsNo tags attached.
Database engine and version
PHP version
Web serverApache 1.3.x
Attached Files

- Relationships

-  Notes
photiolo (reporter)
2005.10.15 14:58

Issue category "metadata" and 1.5 RC1 (sorry)
plg (manager)
2005.10.18 22:35

I've just updated the "Product version". My current filter is on release 1.5.0RC1 so I didn't see your bug entry. I'll look at it tomorrow in depth.
plg (manager)
2005.10.19 20:54
edited on: 2005.10.19 20:55

Thanks for your accurate analysis.

Here I read two issues :

1. bug: in admin/include/functions_metadata.inc::update_metadata function, only date_creation is added to $update_fields even if other keys are configured in $conf['use_exif_mapping']. The correction is as you say, copied from IPTC.

2. feature request: by default IPTC values overload EXIF values for a single key (date_creation for example). You ask a configuration parameter to choose EXIF more important than IPTC.

Concerning the bug correction, I've made the correction and it works fine.

Concerning the feature request, I refuse it. Indeed, I think you should not have keys in common among EXIF and IPTC. If you really want that, you'll have to modify (easy for you I think) the order of EXIF and IPTC retrieval in the foreach loop.

Do you agree with this? (OK means I close the bug entry)

photiolo (reporter)
2005.10.19 22:07

Thank you for such a quick answer and reactivity!
The most important for me is the bug correction to avoid a code modification in each new version. Thanks for that.
Regarding point 2, as you said, I dont use IPTC at all, then it is not a problem for me to have the code left as it is now (IPCT priority over EXIF when both exist). I suppose also that most people wont use both at the same time with the same fields... hope so ;)

plg (manager)
2005.10.19 22:15

Fine :-) I've just commited the bug correction in CVS.

- Issue History
Date Modified Username Field Change
2005.10.15 14:02 photiolo New Issue
2005.10.15 14:02 photiolo browser => any
2005.10.15 14:02 photiolo Web server => Apache 1.3.x
2005.10.15 14:58 photiolo Note Added: 0000285
2005.10.18 22:35 plg Note Added: 0000297
2005.10.18 22:35 plg Assigned To => plg
2005.10.18 22:35 plg Status new => assigned
2005.10.18 22:35 plg Category category management => metadata
2005.10.18 22:35 plg Product Version => 1.5.0RC1
2005.10.19 20:54 plg Note Added: 0000301
2005.10.19 20:55 plg Note Edited: 0000301
2005.10.19 20:56 plg Status assigned => feedback
2005.10.19 22:07 photiolo Note Added: 0000303
2005.10.19 22:15 plg Note Added: 0000306
2005.10.19 22:15 plg Status feedback => closed
2005.10.19 22:15 plg Resolution open => fixed
2005.10.19 22:15 plg Fixed in Version => 1.5.0RC2

Copyright © 2000 - 2015 MantisBT Team
Powered by Mantis Bugtracker