Appearance
LT Work
needs verificationAn LT Work is the workflow record for a chaptered video. It ties together a type, creator, subject researcher, owner context, source papers, chapter uploads, processing history and publication state. The Video is its playable output, not the workflow record itself.
| Type | Chapters | Source papers | Video layout | Created in app | DOI eligible |
|---|---|---|---|---|---|
| Publication | Question, Method, Findings | 1 to 5 | Portrait | Yes | Yes |
| Profile Video | About Me, Area of Research, Findings | None | Portrait | Yes | No |
| Publication Plus | Question, Method, Findings, Relevance, Outlook | Exactly 1 | Landscape | No, editorial production | Yes |
Readiness
Before submitting an app-created work, required chapter media and cover must exist, and Publication must have a source paper. Linked Open Researcher and Contributor ID (ORCID) proof is required for researcher-created Publication and Profile Video. The current configuration does not require it for coordinator-created works. Submitted-stage subject approval is a separate processing gate.
Runtime lifecycle
Revision flags take precedence over normal draft readiness labels. Record Again clears active chapter media after processing failure; resubmission still checks readiness. See the revision service.
Major groups describe the stage. Minor states are derived from content, approval and processing facts. This diagram contains every current minor state. Archive and restore paths are omitted from individual states for readability; the API exposes these as separate actions.
Business specification differs
The older lifecycle specification additionally lists draft_upload_failed, submitted_uploading, published_featured and archived_unpublished. These are not current runtime minor states. Its statement that no runtime state machine was found is also outdated. Admin editorial review is disabled in the minimum viable product (MVP); successful processing supplies the approval marker automatically.
An eligible unpublished work can be canceled, then restored if needed. Restore returns it to Draft or pending confirmation according to its saved previous state. Published work cannot use this cancellation path.
A published Video is retained. Public publish, unpublish and republish API routes are placeholders. Read the publication story and open questions before treating the diagram as an automated production pipeline.
See LT Work statuses for every app label, who acts next, and how revision, cancellation and restoration work.
For maintainers: source references
These references require repository access. Everything needed to understand this page is explained above.