SUMMARY *** I'm using a mobile app (for iOS and Android), collecting metadata of camerea, lens, film, camera settings and location while shooting analog images, called Crown + Flint. More info can be found here: https://crown-and-flint.goodman-wilson.com/ This app can export a JSON file including the EXIF metadata for a film roll with the metadata information per frame. The JSON export can be used by e.g. exiftool, to change the metadata of the images files, which are mapped by the image file name. I'd request a feature added to the Metadata Tools, where this process can be automated from within digiKam by selecting the JSON file (exported by Crown+Flint app) and apply the settings per frame to the selected images. *** ADDITIONAL INFORMATION I can provide the contact to the developer of the mobile app if further information is requested.
Maybe this request would be better placed under "Metadata Tools" and "Batch-Queue.Manager", but I couldn't find it in the selection list.
The idea is more to handle json file as sidecar for metadata. https://en.wikipedia.org/wiki/Sidecar_file Gilles Caulier
In digiKam setup metadata dialog page, there is a settings to tune the sidecar file extension. https://docs.digikam.org/en/setup_application/metadata_settings.html#sidecars-settings Using this and ExifTool as metadata backend: https://docs.digikam.org/en/setup_application/metadata_settings.html#behavior-settings ... there is a chance that it work as well. Please test... Gilles Caulier
Not sure if a siddecar file is a solution here, as the JSON file contains EXIF data for all frames on the film roll in one file and the EXIF metadata used are all 'default' (as defined in the exiftool documentation).
(In reply to caulier.gilles from comment #3) > In digiKam setup metadata dialog page, there is a settings to tune the > sidecar file extension. > > https://docs.digikam.org/en/setup_application/metadata_settings. > html#sidecars-settings > > Using this and ExifTool as metadata backend: > > https://docs.digikam.org/en/setup_application/metadata_settings. > html#behavior-settings > > ... there is a chance that it work as well. Please test... > > Gilles Caulier Thank you for this hint. As mentioned below, the JSON file from Crown+Flint contains the metadata of all frames of a roll - in case of a 135 film, there might be 36 frames included. I guess a sidecar file contains the metadata of a single image only. So your suggested solution will not work, IMHO. Please correct me if I'm wrong.
Well, I installed the app as a test and did an ExifTool export. With our BQM in digiKam, it would not be difficult to integrate this function with ExifTool. The question would be, what settings do you expect in the BQM tool, for sure for the JSON file in question? Do you already create the file names of the scans with the sequential image number so that it matches the JSON file? Maik
The responsibility for aligning the file names is on the user side. Either adjust the filenames in the JSON or adjust the image filenames. So we can take this as pre-requisite. I guess the workflow should look like follows: Selecting a number of images, calling the bqm. For the workflow, you need to know the location of the JSON file (e.g. by file selector). The target directory can be the same as the original one, or the user can select a separate one. The workflow then should go through the images one by one, try finding the matching filename in the JSON and then apply the EXIF metadata to the image. Does this sound plausible to you? In a future app release, it is planned to have the filenames configurable, which then would make life easier - as far as I‘m aware. BTW: I also contacted Don Goodman-Wilson, the mastermind behind Crown+Flint. Maybe he is reading this and can comment too ;)
Git commit e9105a640ae98356be2bde3a8b2a8dfec7ae158f by Maik Qualmann. Committed on 11/02/2024 at 17:42. Pushed by mqualmann into branch 'master'. add BQM tool to apply metadata from image or JSON file add BQM tool to apply metadata from image or JSON file FIXED-IN: 8.3.0 M +1 -1 NEWS M +1 -0 core/dplugins/bqm/metadata/CMakeLists.txt A +26 -0 core/dplugins/bqm/metadata/applymetadata/CMakeLists.txt A +209 -0 core/dplugins/bqm/metadata/applymetadata/applymetadata.cpp [License: GPL(v2.0+)] A +59 -0 core/dplugins/bqm/metadata/applymetadata/applymetadata.h [License: GPL(v2.0+)] A +104 -0 core/dplugins/bqm/metadata/applymetadata/applymetadataplugin.cpp [License: GPL(v2.0+)] A +55 -0 core/dplugins/bqm/metadata/applymetadata/applymetadataplugin.h [License: GPL(v2.0+)] M +7 -0 core/libs/metadataengine/exiftool/exiftoolparser.h M +40 -1 core/libs/metadataengine/exiftool/exiftoolparser_command.cpp M +6 -0 core/libs/metadataengine/exiftool/exiftoolparser_output.cpp M +5 -0 core/libs/metadataengine/exiftool/exiftoolparser_p.cpp M +1 -0 core/libs/metadataengine/exiftool/exiftoolprocess.h M +2 -1 core/utilities/queuemanager/manager/task.cpp https://invent.kde.org/graphics/digikam/-/commit/e9105a640ae98356be2bde3a8b2a8dfec7ae158f
Git commit bb8fff435fc6f5b64b0a91fe9262fe6a2b2c0e1c by Maik Qualmann. Committed on 11/02/2024 at 17:53. Pushed by mqualmann into branch 'master'. create temporary directory only if needed M +17 -12 core/dplugins/bqm/metadata/applymetadata/applymetadata.cpp https://invent.kde.org/graphics/digikam/-/commit/bb8fff435fc6f5b64b0a91fe9262fe6a2b2c0e1c
A note: the BQM tool currently expects the image file names as stored in the JSON file in the "SourceFile:" entry. Maik
That's so cool :) Do I have to wait until release 8.3.0 to test this enhancement?
You can test it with the next pre-release package of digiKam-8.3.0 from here: https://files.kde.org/digikam/ Maik
Thank you! I'll make a test as soon as available.
I made a first test and it look very good! It seems as if all EXIF-Data from the JSON file have been added to the image files. I will make a direct filed by field comparison later, but I think this step was successful. If I have any further questions, I'll reopen this request. Is this fine for you? Many thanks to you!
If this is just for Q, just post in this entry. We are in CC. Best Gilles Caulier
Hello, a little late to the party! I'm the developer of Crown + Flint, and I am more than happy to coordinate with you on defining a format that might make more sense than relying on JSONified EXIF metadata—as EXIF was meant for digital cameras, and at least some of the relevant metadata C+F exports is specifically for analog systems. If there's anything I can do to streamline the transfer of metadata from C+F to DigiKam, please let me know.
If you want to define a different format, it should definitely be compatible with ExifTool. I don't know how your users otherwise apply the metadata to the scanned images, but we have no problems with the JSON file. digiKam still uses Exiv2 internally, we create an EXV file, which we then apply to the image with ExifTool if writing with ExifTool is activated. So similar to the JSON file. Best Maik