@Stenis I picked the ‘IPTC’ fields for a specific reason, there are a lot of them which I don’t use so “high jacking” the odd field or two might be “useful” particularly if it is possible to find one that might be (vaguely) appropriate to this particular scenario.
I do understand the risks you identified and would never propose such a “solution” for anyone that is using the IPTC data with a serious intent, or at least to use the most “obvious” fields that are not currently required by the user!
For private use it should be O.K. provided the images are not destined for “publication” or the metadata is actually going to remain in DxPL, i.e. AS(OFF) {or MS(OFF)} and no ‘Metadata’/‘Write to image’ is executed!
As you identified that comes at a price!?
@Sparky2006 Not exactly Auto keyword embed original image file name requests the opposite, i.e. embed the original name in the metadata because you want to rename the file but retain the original name for reference purposes.
This request is to allow a “pseudonym” while retaining the original name (for the purpose of preserving any such references).
In my case I have multiple backup copies and the software I use will allow my to synchronize, when I will wind up with duplicates with the old and the new names, or Mirror when I will wind up overwriting DOP (and Xmp sidecar files) and images files for JPGs, and yes I do understand the notion of preserving multiple versions of the same data but when you changes file names then …
@Joanna are Finder tags visible in DxPL(Mac)!?
Because I use DxPL(Win) I was looking for a “solution” (workaround @JoJu) that would work for all users, including me, for this particular “issue”, and chose to suggest adding “clutter” to the IPTC metadata rather than the keywords!
Not an uncommon trick to avoid the need to re-organize a database, either as a permanent feature or as a temporary measure until a proper re-organization could be scheduled! One of my customers had the entire U.K. households on file!?