Bulk files renaming using csv tables

I went over to Windows 10 and created a CSV that was saved with Code page 1252 (Windows Western European) encoding. This had trailing CRLF line endings and when run through the above Run Shell Script, it produced the trailing ? on the renamed JPG images.

I have made a slight modification to the script to remove the carriage return part of each CSV line ending, and this will eliminate the trailing ? on the renamed images. Ideally you would save the CSV as UTF-8 text, but the fixes I have made should deal with Windows CRLF line endings.

Replace the contents of the Run Shell Script with the following updated script:

#!/bin/bash

cd "$1"

# simply exit if CSV file is absent or empty
[[ -s data.csv ]] || exit 1

# Strip quoted CSV fields (if present) and replace CRLF (if present) with LF
# Dynamically adapt IFS to different CSV delimiters
while IFS=$'\t,;:!' read oldfile newfile
do
    # Skip entry if old filename in CSV doesn't exist in current folder
    [[ -f "$oldfile" ]] || continue
    # printf '%s\t%s\n' "$oldfile" "$newfile"
    # rename
    mv $PWD/{"$oldfile","$newfile"}
done < <(sed -e 's/"//g;' < data.csv | tr -d '\r')
/usr/bin/osascript -e 'display dialog "Processing complete."' &> /dev/null
exit 0

https://www.imore.com/how-rename-multiple-files-once-mac

I would recommend that your CSVFile be renamed to data.csv. The following Automator solution makes these assumptions:

1. The data.csv file will be present among the images to be renamed.
2. Header rows, and images in the OldImageName column that do not exist in the folder will be ignored without interruption in processing.
3. If CSV data is double-quoted, these quotation marks will be removed before the row data is processed.
4. This script is capable of dynamically adapting to different separator characters in the same CSV document instead of a single separator character. Just in case.
5. The script makes no effort to deal with a Byte-order-mark (BOM) that MS Excel may place at the beginning of the CSV.

The only user interaction is to pick the folder whose contents are to be processed by the script, and to ensure that the correct CSV data is in that folder. This was tested on macOS High Sierra 10.13.6.

In the Run Shell Script action, replace the boiler plate text with the following Bash syntax:

cd "$1"

# simply exit if CSV file is absent or empty
[[ -s data.csv ]] || exit 1

# Strip quoted CSV fields (if present) before reading the data
# Dynamically adapt IFS to different CSV delimiters
while IFS=$'\t,;:!' read oldfile newfile
do
    # Skip entry if old filename in CSV doesn't exist in current folder
    [[ -f "./$oldfile" ]] || continue
    # printf '%s\t%s\n' "$oldfile" "$newfile"
    # rename
    mv $PWD/{"$oldfile","$newfile"}
done < <(sed -e 's/"//g;' < ./data.csv)
/usr/bin/osascript -e 'display dialog "Processing complete."' &> /dev/null
exit 0

The Automator application workflow will look like the following:

I cannot reproduce the trailing question marks on your image files when run on Mojave 10.14.2, and using the exact same data.csv as shown in your above image.

How did you create that data.csv file, and did it originate on Windows, or macOS?

I knew you'd have a better answer! :)

Thanks. Just a coding exercise if the OP does not respond. 🤓

Same functionality using a high-level language (e.g. Ruby). It won't auto-sense the separator, and thus expects a true CSV, and in this example, it also expects CSV headers.