DOI

gap

A Digital Object Identifier (DOI) is a permanent identifier used to cite a scientific publication. LT's intended rule is to assign a video DOI at publication, when its content and attribution are final. Publication and Publication Plus are eligible; Profile Video is not. Eligibility is verified in LT Work type configuration. Publish-time assignment remains an intended rule, not an implemented service.

For a visible example, open the DOI link for Marta Mrozowska’s LT video, also displayed on its public page. Existing published editorial content can have a DOI even though the new core minting integration is missing.

Core has a doi_references model and a submission-state enum: draft, ready for submission, submitted, processing, completed and failure states. No registration-agency client or runtime writer was found. The provider, such as Crossref or DataCite, is unresolved.

Source-paper DOI is not video DOI

The LT Work API explicitly returns doi: null. The website payload's publication.doi comes from the primary OpenAlex source paper. It is not a minted LT video DOI. This differs from the brief's description of a DOI passed through from the LT Work.

A published Video is retained as a scientific publication. A new successful projection creates a new Video and marks the previous current output superseded; it does not erase that historical row. The model's DOI wording expresses the product rule, while minting remains missing.

Existing editorial DOI values in Strapi must be distinguished from automatic registration. The open questions track the provider and delivery gap.

For maintainers: source references

These references require repository access. Everything needed to understand this page is explained above.

• LT Work type configuration
• DOI model
• submission states
• LT Work response
• website payload projector
• Video model