Support for IPTC tag Digital source type

[madjufra]

Is your feature request related to a problem? Please describe

No response

Describe the solution you'd like

It would be nice if we could extend

https://github.com/dlemstra/Magick.NET/blob/48c187cf695f44001a832268b221a2fee85d48c1/src/Magick.NET.Core/Profiles/Iptc/IptcProfile.cs

With support for

https://cv.iptc.org/newscodes/digitalsourcetype/

This tag is used to indicate from where the digital asset was created and widely used within generative AI to indicate that it is an AI generated image.

Describe alternatives you've considered

Perhaps we can somehow workaround this manually?

Additional context

No response

[dlemstra]

This doesn't look like an IPTC tag? Can you share a sample image that contains this?

[Arslan-TR]

This is a great idea, but I don't think it belongs in IptcProfile/IptcTag.

Digital Source Type is part of the IPTC Photo Metadata standard, but it was introduced well after the legacy IIM (Information Interchange Model) datasets were frozen. The IPTC User Guide explicitly documents that new IPTC Core/Extension properties added after that point are XMP-only and have no IIM dataset number ("IIM Metadata deprecated in IPTC Core" - only a handful of legacy fields like Urgency/Category are synced between IIM and XMP, and Digital Source Type isn't one of them). I checked the full IIM Application Record 2 dataset list (e.g. via Exiv2's reference table) and there's no dataset that maps to it - IptcTag (src/Magick.NET.Core/Profiles/Iptc/IptcTag.cs) models exactly those binary datasets, so adding a DigitalSourceType member there would just create a tag with no defined encoding that no other IIM reader/writer would recognize.

The good news is you don't need a code change for this - it's XMP metadata, and XmpProfile already gives you full read/write access via ToXDocument()/FromXDocument(). You'd set it under either the plus namespace (https://ns.useplus.org/ldf/xmp/1.0/DigitalSourceType) or photoshop:DigitalSourceType (http://ns.adobe.com/photoshop/1.0/), same as any other custom XMP property, e.g.:

using var image = new MagickImage("input.jpg");
var xmp = image.GetXmpProfile();
var document = xmp?.ToXDocument() ?? new XDocument(...); // build/merge as needed
// set plus:DigitalSourceType or photoshop:DigitalSourceType on the document
image.SetProfile(new XmpProfile(document));

So this looks like it can be closed as "already possible" rather than needing an IptcTag addition - happy to be corrected if I'm missing an IIM mapping for this somewhere.