starred/photoprism

Fork 0

mirror of https://github.com/photoprism/photoprism.git synced 2026-03-02 22:57:18 -05:00

XMP sidecar dc:subject not imported as Keywords for JPEG (PhotoPrism Build 250707-d28b3101e) #2387

New issue

Closed

opened 2026-02-20 01:10:49 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 01:10:49 -05:00

Owner

Originally created by @vctrvf on GitHub (Aug 20, 2025).

1. What is not working as documented?

Information stored in sidecar XPM doesn't come to PP database / yml

2. How can we reproduce it?

Place JPEG and XMP sidecar with identical basename in Originals, e.g.:

20240127_111247.jpg
20240127_111247.jpg.xmp

XMP sidecar contains valid dc:subject with multiple items:

dc:subject
rdf:Bag
rdf:liArt</rdf:li>
rdf:liContemporaryArt</rdf:li>
rdf:liFineArt</rdf:li>
</rdf:Bag>
</dc:subject>

Run re-index:

photoprism index -f -c "2024/2024.01.27 - Erarta"

Check resulting YAML sidecar in /photoprism/storage/sidecar/.../20240127_111247.yml.

Expected behavior:

Keywords in YAML and UI should contain art, contemporaryart, fineart.

Sidecar values from dc:subject should override and/or merge into Keywords as documented.

According to docs [https://docs.photoprism.app/user-guide/library/metadata/], sidecar metadata should override other sources and dc:subject should be imported as Keywords.

Actual behavior:

photoprism index log shows:

INFO index: updated related xmp file '.../20240127_111247.jpg.xmp'

But YAML contains only automatically generated keywords (from filename/labels):

Details:
Keywords: erarta, museum, …
Subject: ContemporaryArt # taken from embedded JPEG

Keywords from sidecar (dc:subject) are completely ignored.

Same result when also adding lr:HierarchicalSubject.

It looks like only embedded metadata from JPEG and auto-generated labels are used, while sidecar XMP is ignored entirely.

6. Which software versions do you use?

(a) PhotoPrism Architecture & Build Number: AMD64
PhotoPrism® CE
Build 250707-d28b3101e

(b) Database Type & Version: SQLite 3.46.1

(c) Operating System Types & Versions:
Debian GNU/Linux 12 (bookworm)
Linux homenas 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux

(d) Browser Types & Versions: Chrome / Edge

(e) Ad Blockers, Browser Plugins, and/or Firewall Software? no

7. On what kind of device is PhotoPrism installed?

(a) Device / Processor Type: AMD Turion(tm) II Neo N54L Dual-Core Processor
RAM: 8 GB
total used free shared buff/cache available
Mem: 7.5Gi 2.2Gi 282Mi 22Mi 5.3Gi 5.3Gi
Swap: 975Mi 140Mi 835Mi

Storage:

Originals: /mnt/storage/photoprism/originals (ext4, mounted :ro in Docker)
Storage: /mnt/storage/photoprism/storage (ext4, mounted :rw in Docker)

20240127_111247.jpg.xmp.txt

docker-compose.yml.txt

Originally created by @vctrvf on GitHub (Aug 20, 2025). #### 1. What is not working as documented? Information stored in sidecar XPM doesn't come to PP database / yml #### 2. How can we reproduce it? Place JPEG and XMP sidecar with identical basename in Originals, e.g.: 20240127_111247.jpg 20240127_111247.jpg.xmp XMP sidecar contains valid dc:subject with multiple items: <dc:subject> <rdf:Bag> <rdf:li>Art</rdf:li> <rdf:li>ContemporaryArt</rdf:li> <rdf:li>FineArt</rdf:li> </rdf:Bag> </dc:subject> Run re-index: photoprism index -f -c "2024/2024.01.27 - Erarta" Check resulting YAML sidecar in /photoprism/storage/sidecar/.../20240127_111247.yml. Expected behavior: Keywords in YAML and UI should contain art, contemporaryart, fineart. Sidecar values from dc:subject should override and/or merge into Keywords as documented. According to docs [https://docs.photoprism.app/user-guide/library/metadata/], sidecar metadata should override other sources and dc:subject should be imported as Keywords. Actual behavior: photoprism index log shows: INFO index: updated related xmp file '.../20240127_111247.jpg.xmp' But YAML contains only automatically generated keywords (from filename/labels): Details: Keywords: erarta, museum, … Subject: ContemporaryArt # taken from embedded JPEG Keywords from sidecar (dc:subject) are completely ignored. Same result when also adding lr:HierarchicalSubject. It looks like only embedded metadata from JPEG and auto-generated labels are used, while sidecar XMP is ignored entirely. #### 6. Which software versions do you use? (a) PhotoPrism Architecture & Build Number: AMD64 PhotoPrism® CE Build 250707-d28b3101e (b) Database Type & Version: SQLite 3.46.1 (c) Operating System Types & Versions: Debian GNU/Linux 12 (bookworm) Linux homenas 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux (d) Browser Types & Versions: Chrome / Edge (e) Ad Blockers, Browser Plugins, and/or Firewall Software? no #### 7. On what kind of device is PhotoPrism installed? (a) Device / Processor Type: AMD Turion(tm) II Neo N54L Dual-Core Processor RAM: 8 GB total used free shared buff/cache available Mem: 7.5Gi 2.2Gi 282Mi 22Mi 5.3Gi 5.3Gi Swap: 975Mi 140Mi 835Mi Storage: - Originals: /mnt/storage/photoprism/originals (ext4, mounted :ro in Docker) - Storage: /mnt/storage/photoprism/storage (ext4, mounted :rw in Docker) [20240127_111247.jpg.xmp.txt](https://github.com/user-attachments/files/21888301/20240127_111247.jpg.xmp.txt) ![Image](https://github.com/user-attachments/assets/41851316-0109-4fb0-b8a5-357159f18b68) [docker-compose.yml.txt](https://github.com/user-attachments/files/21888149/docker-compose.yml.txt)

deekerman

2026-02-20 01:10:49 -05:00

closed this issue
added the
duplicate
label

deekerman commented

2026-02-20 01:10:50 -05:00

Author

Owner

@graciousgrey commented on GitHub (Aug 20, 2025):

Thank you for your feedback. This is because the dc:subject field is not supported yet.

You can find the related feature request here:

https://github.com/photoprism/photoprism/issues/2075

A full list of supported metadata fields is available here:

https://www.photoprism.app/kb/metadata

Other related issues:

https://github.com/photoprism/photoprism/issues/2260

@graciousgrey commented on GitHub (Aug 20, 2025): Thank you for your feedback. This is because the dc:subject field is not supported yet. You can find the related feature request here: - https://github.com/photoprism/photoprism/issues/2075 A full list of supported metadata fields is available here: - https://www.photoprism.app/kb/metadata Other related issues: - https://github.com/photoprism/photoprism/issues/2260