Handle publishing during Media Object creation via API

[masaball]

Description

Since we are adding checks for accessibility compliance that prevent publication, how should we handle the publishing action when creating via the API? Currently, there is just a publish: true flag that can be passed during API creation. With the default publishing enforcement behavior being implemented, any API creation post compliance date (2026-04-26) with the publish flag will be blocked.

Possible Implementations

• Enforce accessibility compliance for API creation
• Bypass enforcement for API creation for all users (keep current behavior)
• Bypass enforcement for API creation for certain users (Admins, Collection managers?)
• Provide an additional flag for explicitly overriding enforcement
• Provide an additional flag for certain users

Questions

• Are there other implementations that might be better?
• Are there any concerns/considerations we need to keep in mind when choosing a way forward?

Additional Notes

• API creation is typically going to be limited to power users who should be able to be trusted to determine if it is okay to publish an item without captions/transcripts

Done Looks Like

• Add flag/attribute for passing in exemption value to the API for media objects
• Update documentation to include information on requirements about accessibility compliance and the requirement for the publish action to be successful

[masaball]

@joncameron I've confirmed that adding override_accessibility: true to the creation payload works for publishing via the API. So the JSON just needs to include publish: true, override_accessibility: true. If only publish is provided, the user will receive an error about publication not being allowed and the media object will not be created. I am not sure how we want to phrase things in the documentation, but it should just be updating the example payload and adding an entry for "override_accessibility" in this section