>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3609787. --> Reported by: [hexabinaer](https://www.drupal.org/user/258364) >>> <h3>Problem/Motivation</h3> <p> The current license/attribution field (license select + author/author_url + source/source_url) assumes a human creator and a licensable work. AI-generated assets break both assumptions: </p> <ul> <li>There is no clear "author" in the copyright sense for purely AI-generated output.</li> <li>The license select forces editors to assert a CC (or similar) rights claim that may not legally apply to AI-generated content.</li> <li><strong>EU AI Act</strong> Art. 50 disclosure obligations apply from 2 August 2026 and <strong>require sites to label AI-generated/-manipulated content</strong>. This is not a nice-to-have, it is an approaching compliance requirement for deployers.</li> </ul> <p> <strong>Key constraint:</strong> we cannot assume existing assets are human-created just because the field predates this feature. Any migration or default must treat existing creation types as unknown. </p> <h3>Proposed resolution</h3> <ul> <li>Add a <code>creation_type</code> sub-field (<code>human_created</code> | <code>ai_generated</code> | <code>ai_assisted</code>) governing conditional sub-fields (<code>ai_tool</code>, <code>ai_prompt</code>, <code>human_editor</code>) via <code>#states</code>.</li> <li>Add a distinct license option for content with no asserted/no known copyright, rather than reusing existing e.g. CC entries for this case.</li> <li>Default new entries going forward as needed - leave unset/unknown as its own state.</li> </ul> <h3>Data migration / existing content</h3> <ul> <li>New column(s) require a migration path (update hook) that sets <code>creation_type</code> to a neutral "unknown/unspecified" default</li> <li>Bulk-edit tooling: a View (or VBO-style bulk operation) listing assets by current attribution state, letting editors triage and bulk-assign <code>creation_type</code> where known, rather than requiring per-asset manual edits.</li> <li>This should be flagged as review work for site owners post-update (changelog/release note), since it affects legal disclosure obligations and not just display.</li> </ul> <h3>Display/rendering considerations</h3> <ul> <li>Rendering of the attribution field is themeable/overridable per site and varies across sites using this module. For example, the OpenCulturas distribution ships a template override that renders attribution as a popover trigger styled as a &copy; symbol - but that icon choice does not generalize to AI-generated content, since there is no copyright claim being made and reusing a &copy; glyph could be misleading.</li> <li>The label "Attribution" remains valid and appropriate across all creation types and should stay the constant, translatable string. Only icons/visual triggers and the populated sub-fields should vary by <code>creation_type</code>.</li> <li>Provide sensible css classes. Any default icon/label for AI-disclosure should live in the template/formatter layer, not be baked into the field logic itself (let's not assume that/how any given site renders a trigger).</li> </ul> <h3>Remaining tasks / open questions</h3> <ul> <li>Icon/visual convention for AI-generated vs. AI-assisted vs. human-created (needs design input; the EU Commission's proposed "AI"/"KI" visual label is a reference point, not necessarily one to copy verbatim).</li> <li>Confirm schema change strategy: new columns on existing field storage vs. a new field.</li> <li>Decide default license option label/machine name for the "no known copyright" case.</li> <li>Confirm whether <code>human_editor</code> is a separate role from the existing "author" field, or replaces it conditionally when <code>creation_type</code> is not <code>human_created</code>.</li> </ul> <h3>API/data model changes</h3> <ul> <li>New field storage columns: <code>creation_type</code>, <code>ai_tool</code>, <code>ai_prompt</code>, <code>human_editor</code>.</li> <li>Widget: conditional visibility logic keyed on <code>creation_type</code>.</li> <li>Formatter: template changes to render the disclosure label independent of icon choice.</li> </ul> <p>Issue text created with the assistance of Claude, based on human concept ;-)</p>