Metadata added during import missing

[ChristopheNL]

Hello,

== Update ==
By Assigning a Category (File/Import and Sort / Categories to assign), and forcing "Create XMP sidecars", the sidecars do get created, but containing only the categories I listed. IPTC template seems to be ignored.
===

Xnview MP 1.10.5 / Windows 11

I'm using XnView MP as a viewer to review my photos post-processing, and I'm now evaluating using XnView MP at the beginning of my workflow: Ingesting the pictures from the SD-Card > SSD while adding Metadata in sidecars files

In Tools/Settings/Metadata/Sidecar, I set
"Create or update XMP Side": checked
"Update Master files": unchecked
Use "filename".xmp

From File/Import and Sort:
Source: The SD-Card
Dest: Some local (Empty) folder
Photos: IPTC Template checked, with a basic templates for testing
Everything else unchecked / untouched

The photos get copied, but no XMP are created, IPTC templates is not applied.

I can't see what I miss..

Thanks

[xnview]

'IPTC template' adds IPTC metadatas not XMP, if i understand correctly you would like to assign to the sidecar, right?

[ChristopheNL]

That's indeed the idea.

Let's call a cat, a cat: i'm evaluating XnView to replace PhotoMechanics in my workflow.
Doing 99% of concert photo(volunteering mostly), i need to have some fast culling.

I like the fact that PM does not actually update the RAW files at all, and i'd love to achieve the same with XNView.

My current WF:
- ingest from SD card to Portable M2 drive
- IPTC metadata is applied (in the sidecars at ingest)
- culling is then processed (usually from a laptop with coffee at hand)
- processing will be done (lightroom on a WIP-catalog) on the culled images from my Mac Mini
- again LR will update the XMP files
- once processing is 100% done, the files are copied to my NAS before final import into my main LR catalog.

[jkm]

Welcome to the forums, Christophe...

XnViewMP is frequently updated, and Importing and Culling is on the roadmap for significant enhancements in the near future. I'm sure it will be able to meet your needs for a non-destructive workflow.

You mentioned that you're applying IPTC metadata at import, but you talk about "in the sidecars"...

Do you mean that you're applying new IPTC data that you want to store in sidecars, or that you when you import, there is already IPTC data in sidecars that you want to capture?

I'm curious about your thoughts on using IPTC vs XMP, and why you're currently using the "less modern" IPTC. Are there specific interoperability needs that you have that require IPTC?

As for your question, there are many settings in XnViewMP that complicate your issue. But in general:
-The IPTC template was not ignored; the metadata was applied to the images, but is probably only stored in the database and has not been written to the sidecars yet.

-You can get all the import-applied data into sidecars, without modifying the master files, but at the moment it's a two-step process. This will be improved in the future.

For your workflow, you should probably set the following settings:
-In Settings:Metadata, ensure everything is enabled under import and export
-In Settings:Metadata:Sidecar, enable "Create or update XMP Sidecar" and disable "update master file". Ensure your sidecar naming convention is set correctly.
-In Settings:File List:Companion Files, make sure both options are checked in "Link companion files..."

Now, when doing your import, set the other things as you desire, but instead of forcing "Create XMP Sidecar for all files" the safest thing to do is to select "No action" in that same menu. It seems counter intuitive, but it's ok. Then run your import.

Once your import is done, all the metadata has been assigned, but it's in the database...

So in the app, browse to your folder where you deposited your imported images, select them all, and then from the Metadata menu, select "Update files from Catalog".

This last step will write XMP files for all the selected files, containing all the metadata you have assigned. After that step is done, future metadata modifications done in the app will generally automatically be written to the XMP files.

In the future, this will be more streamlined.

Hopefully this helps...

[ChristopheNL]

Thank you for the extensive answer.

I'll try to answer your questions are completely as possible (and probably my wording was biased by my usage of Photomechanics I realized).

From the camera, on top of the "pure photographic" metadatas, I only set the Author & copyright.
So, at import time, I want to apply keywording, location etc in non-destructive, so in the sidecars.

I honestly have no thoughts about IPTC vs XMP, (Photomechanics "applies" IPTC at import and store the results in XMP - totally biased here ), and tbh I don't really care (nor I want to care).
What I'm looking is a way to store in XMP files the keywords, copyright, color class & ratings. in a format allowing for interoperabilit between Lightroom, DxO, Canon DPP.

I'm very keen on the nondestructive, I want to keep/preserve the RAW files as they were exiting the camera.

I'll give a try to your procedure and see if it can fit my WF, and will keep an eye on the updates coming

[jkm]

So, at import time, I want to apply keywording, location etc in non-destructive, so in the sidecars.

What I'm looking is a way to store in XMP files the keywords, copyright, color class & ratings. in a format allowing for interoperabilit between Lightroom, DxO, Canon DPP.

Yes, XnViewMP can do those things. The settings just have to be configured appropriately.

[xnview]

See issue, XMP template will be supported

[ChristopheNL]

Thanks !

[xnview]

This problem is supposed to be fixed in XnView MP 1.11.1. Please check and confirm the bug fix here.