Differences

This shows you the differences between two versions of the page.

--- c3tracker:start [2022/02/27 14:48] – andi
+++ c3tracker:start [2022/02/27 16:25] (current) – andi
@@ Line 1: / Line 1: @@
-= C3 Ticket Tracker
+= CRS Ticket Tracker
-The C3 Ticket Tracker is the central managing component in our [[docu:overview#postprocessing|postprocessing]] pipeline, releasing the final recordings. The tracker is a PHP web application and distributes tasks in form of '//tickets//' to various //workers//. The workers – written in Perl, Python, or PHP – advance the state and update the ticket's properties via tracker's XML RPC API. The core system was initially written by FeM for 27C3 in 2010, and was released under the Apache License 2.0 end of 2017. Our instance is deployed at https://tracker.c3voc.de.
+The Ticket Tracker is a web platform tracking process of video recording and ingest sources and video encoding progress. It guides users through manual processes like editing and checking and provides an API for scripts doing post processing and encoding.
+The tracker is a PHP web application and distributes tasks in form of '//tickets//' to various //workers//. The worker scripts – written in Perl, Python, or PHP – advance the state and update the ticket's properties via tracker's XML RPC API.
+The core system was initially written by [[:FeM]] for 27C3 in 2010, and was released under the Apache License 2.0 end of 2017. Our instance is deployed at https://tracker.c3voc.de.
 source code:
@@ Line 20: / Line 24: @@
 == Concepts
-The C3 Ticket Tracker ermöglich die (teil-)automatisierten Aufzeichnung, Schnitt & Release von mehrsprachigen Videos. Um ein Release erfolgreich abzuschließen, müssen bestimmte Projekt-Einstellungen  konfiguriert werden und einige wenige Status-Übergänge bedient von Hand bedient werden:
+The C3 Ticket Tracker enables the (semi-)automated recording, editing & release of multilingual videos. In order to complete a release successfully, certain project settings must be configured and a few of the state transitions must be operated manually:
 === Ticket types and hierarchy
-One of the really good features of the C3 tracker is that property are inherited through the hierarchy:
+One of the really good features of the C3 tracker is that propertyies are inherited through the hierarchy:
 * Project settings (Conference or Series)
     * Meta ticket (Parent with Fahrplan-ID & -Metadata)
         * Recording ticket (Language, etc)
-           - Master encoding ticket (MP4)
+           - Main encoding ticket (MP4)
            - additional encoding tickets, e.g. WebM, MP3, Opus, SD formats, etc.
 === Ticket states
+For each ticket type, the tracker has a predefined set of states, which can be enabled and disabled on an per project basis. Here is an example workflow with only one manual `checking` step:
 {{drawio>c3tracker:states}}