Adding keywords to multiple files in multiple sub directories

[Skids]

Hi,
Recently I have discovered that a large number of jpeg files in my image collection have no keywords set.  I wish to add keywords to these files based on their filenames.  This issue has occurred because the application I have been using fails to write keywords into jpeg files if there is an xmp file of the same name in the folder.  This situation may occur when a camera is set to record both raw and jpeg files.

I have created a crude tool that outputs lists of jpeg files with no keywords.  My first attempts have been to try and use a JSON file to list all these jpegs and new keywords but despite reading the documentation and reading multiple posts I have not been able to update the keywords. 

So far my approach has been to create a simple JSON file that just lists the file path and the keywords that should be added.  For example :

Code Select Expand

[{
  "SourceFile": "/Volumes/Image_Library_SSD/JPEG-Nil-Keywords-copy/2012-09-16-123457-P1040633-.JPG",
  "Keywords": ["KeywordOne","KeywordTwo","KeywordThree"],
},
{
  "SourceFile": "/Volumes/Image_Library_SSD/JPEG-Nil-Keywords-copy/2012-09-16-123805-P1040641-.JPG",
  "Keywords": ["KeywordFour","KeywordFive","KeywordSix"],
}]


I have tried to use the file in the following command

Code Select Expand

exiftool -json /Volumes/Image_Library_SSD/AddTheseKeywords.json Unfortunately this does not work and just prints a single record of JSON text. 

Code Select Expand

[{
  "SourceFile": "/Volumes/Image_Library_SSD/AddTheseKeywords.json",
  "ExifToolVersion": 11.80,
  "FileName": "AddTheseKeywords.json",
  "Directory": "/Volumes/Image_Library_SSD",
  "FileSize": "329 bytes",
  "FileModifyDate": "2021:03:11 06:04:27+00:00",
  "FileAccessDate": "2021:03:11 06:04:27+00:00",
  "FileInodeChangeDate": "2021:03:11 06:04:27+00:00",
  "FilePermissions": "rw-r--r--",
  "FileType": "JSON",
  "FileTypeExtension": "json",
  "MIMEType": "application/json",
  "Keywords": ["KeywordOne","KeywordTwo","KeywordThree","KeywordFour","KeywordFive","KeywordSix"],
  "SourceFile": "/Volumes/Image_Library_SSD/JPEG-Nil-Keywords-copy/2012-09-16-123805-P1040641-.JPG"
}]

Reading posts on this site suggest that using a json file in this way may not work as it seems that the command line command also needs to  include a list of file paths that are to be modified.

Another method may be to just issue a single ExifTool command per file.  I can probably do this from within the utility that is creating the JSON file or possibly by using the (gulp!) -args command.

At present I am fumbling about and will appreciate some advice on the best method to use.

best wishes
Simon

[StarGeek]

This issue has occurred because the application I have been using fails to write keywords into jpeg files if there is an xmp file of the same name in the folder.

Do the sidecar files still exist?  Because then you can just copy the keywords from the sidecar into the files.  See Metadata Sidecar Files for some examples

I have tried to use the file in the following command

Code Select Expand

exiftool -json /Volumes/Image_Library_SSD/AddTheseKeywords.json

That command reads the "AddTheseKeywords.json" files and prints the output as a json file.  You'll want to read the docs on the -j (-json) option and FAQ #26.  Also, you need to list a directory or filenames to process.  The json file is just a lookup table.  It isn't used as a list of files to process.

Another method may be to just issue a single ExifTool command per file.

Not the best option, as it would be very slow.  Exiftool's biggest performance hit is the startup time and running it individually over hundreds or thousands of files could take a long time.  See Common Mistake #3.

[Skids]

Hi Stargeek,

Thanks for the information.  I will try adding the building of the command along when the list of keywords is built although I suspect that I will hit a line length limit at some point.  Yes, some of the sidecar files do exist so my next stop is to read the link you posted.

best wishes

Simon

[Skids]

It seems that command line length may not be an issue as the system reports it can accept 1048576 characters (see ARG_MAX command).

S