Galicaster and Opencast, the best match

{pop-away:metadata | comments | children | labels}
{section}

{column}

{column:width=2%}

{column}
{column:width=28%}
{center}
\\

!captura_screencast.png|align=center,width=300!

*MH engage player capture*
{center}{column}
{section}

----
{section}
{column:width=28%}
\\
\\
\\

!compatible.png!
{column}
{column:width=2%}
{column}
{column:width=68%}

h5. How does Galicaster fit in Matterhorn?

Every Galicaster application can work as a standard Matterhorn capture agent. It can register as a capture agent, thus being able to receive scheduled recordings and ingest the resulting mediapackages automatically. The main advantages of Galicaster, compared to a standard Matterhorn capture agents are:

* It has a *graphic interface*.
* It can be *manually operated*.
* *Reingesting media* is very *easy*.
* Users can *replay and review* the recorded media, and
* It provides *media repository features* such metadata edition, recording search and export to side by side compostion.

Manual recordings can be introduced into the Opencast Matterhorn system like a regular scheduled mediapacakge.. Galicaster harvest the available series to use them to edit and catalog a mediapackage before ingesting. Also, a predefined workflow can be set for those recordings, including the paramaters.

Galicaster is compatible wiht Opencast Mattehorn 1.2, 1.3 and the upcoming 1.4.

* _(New in 1.1)_ Custom workflow parameters can be set on each Galicaster agent.

Due to its *seamless integration with Matterhorn*, Galicaster can be used in combination with standard Matterhorn Capture Agents in the same installation, allowing institutions to choose the combination that meets their needs best.



{column}{section}
{section} !uvigo_deploy.png|align=center! 
{section}