XMP and/or IPTC: set some required metadata fields...

[Gerald_Ire]

Hello to all XNViewers, I'd like to setup some XMP and/or IPTC metadata fields in that way that they are required before saving on server or sending via ftp...

Is there an option for that?

[Gerald_Ire]

Let me explain what I'm looking for:

Metadata of an image contains in my view three parts:

• image content

• image rights

• image administration for a database

So some of metadata fields are:

• obligatory or desired

• not relevant or not given

Q#1: If someone has to write metadata, how can I lead them to the obligatory and desired metadata field?

Q#2 Is there a chance to extend the code in iptc.ini or xmp.ini for such a function?

"field is ok"-code = field isnt empty = OK
"field is required"-code = field is empty = Warning/Error

[Gerald_Ire]

My - personal - wish list for iptc/xmp:

image content:
iptc / xmp
092 Sublocation
090 City
095 State/Province
101 Country
020 Supl.Category
025 Keywords
105 Headline
120 Caption-Abstract

image rights:
iptc / xmp
040 Specl.Instructions
080 By-line
110 Credit
115 Source
116 Copyright Notice

... or all/any other metadata as well...

[Gerald_Ire]

Samples only!

Some screenshots of xmp-metadata fields:

Location of the image has been taken:

Copyrights of the autor / creator / photographer:

Suppl. Category: sometimes used for image content and/or administration

Image content part one:

Image content part two:

[Gerald_Ire]

I still see thousands of images every day running thru the file servers und only the few professionals and enthusiasts have clue where and what metadata to edit...

Is there anybody who would support this idea for flexible a setup of "required metadata fields"...?

This should be flexible to choose on/off, but I think this option is urgent needed.

[xnview]

So user can't write XMP/IPTC without having filled all required fields?

[Gerald_Ire]

Hi Pierre, thx for reply...

Yes, this could be the result.
Otherwise, you get images in the database without any required copyrights etc.

The main idea is to lead an unexpired user what to do with metadata...
Another alternative to "required" could be "recommended" with the option to carry on...