Thank you for your update with the additional information. Thanks as well for taking the time to post a screenshot of your mapping rules; very helpful.
Regarding the mapping rules, your “copyright” rule may not be working because EXIF data is case-sensitive and all the images I have seen use “Copyright”, not “copyright”. You can also simplify your rule by just entering “Copyright” in the EXIF/Template field. MLA will assume that “Copyright” is an exif field and will automatically test for and ignore empty values. You can use “GPS.LatitudeSDD” in the same way.
If you haven’t already read through them, you may find these earlier topics interesting:
Camera Exif Fetch
EXIF/Template Value editing
Geo-tag custom field
The first topic was the inspiration for adding the “Field-level enhanced EXIF CAMERA values” (see the Documentation) information you need. It also shows how to format and display the data directly from the image file, without mapping it into the Attachment Metadata area. There are pros and cons of each approach.
You wrote “I can’t seem to actually find those fields anywhere for viewing or editing.” If you mean the raw EXIF data, you can use the ALL_EXIF
pseudo-field in an [mla_gallery]
shortcode to view much of the data. I use Photoshop’s “File Information” feature to see ALL the data in detail, but most photo-editing tools have some ability to display it as well.
If you want to “edit the EXIF data on individual images“, the best approach I can think of is to map these data to individual custom fields and maintain them there. If you use the “Existing Text: Keep” option in your mapping rules any changes you make will not be lost if you re-map the image more than once. It’s a little tedious to set up, but flexible. Would that work for your application?