Reading tags does not work as expected
Hello,
I've been trying for a while now to import my existing photos sorted in a year-month-based folderstructure (YYYY-MM-DD - Keyword1, Keywords, etc.). My final goal is, not to lose the structure. Best option would be to import into folder-named albums automatically, which I did not find any option for.
So, my idea to workaround was, to automatically get immich setting tags. For this, I used exiftool to tag the photos according to the folder names. This seems to work as the tags are being set as they should. However, the result after importing to Immich is, the separated tags (using , or ; as separators) are recognized as a single tag string ("Keyword1, Keyword1, etc."), which makes no sense at all.
I've been trying different approaches with exiftool, using , or ; as separators. The result in exiftool looks fine, but as said, Immich joins the tags into a single tag string. There is one option which worked, when I added each keyword separately with exiftool. Strangely, the result look exactly the same when I review it with exiftool itself, no difference between using the folder name or to add manually. But, obviously, there is a difference, as Immich's result differs. Here I hope some Immich expert might understand the reason.
Below the commands I've beens using:
To tag based on folder name:
exiftool -overwriteoriginal -progress:%50b -P -r "-subject<${directory;my @a=split m( - );$=$a[-1]}" "C:\temp\test\2024_0107 - Keyword1, Keyword2, etc"
To tag manually:
exiftool -overwrite_original -progress:%50b -P -r "-subject+=Keyword1 "C:\temp\test\2024_0107 - Keyword1, Keyword2, etc\pic_1.jpg"
exiftool -overwrite_original -progress:%50b -P -r "-subject+=Keyword2 "C:\temp\test\2024_0107 - Keyword1, Keyword2, etc\pic_1.jpg"
etc.
The result from exiftool output looks exactly the same:
Keywords: Keyword1, Keyword2, etc
But Immich recognize separated tags only in the second case, when I added the tags one by one manually.
Any idea is heavily appreciated.
1 Reply
:wave: Hey @UwE,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark: