Hi all,
For MH-5048, the scheduling option data needs to be easily accessible in order
to be displayed on the Admin UI Recording View Info.
The simplest solution is to include those parameters in the configurations
section of the capture workflow, in the same way that they appear in the
post-ingest workflow. They would be put in the top configurations section, not
in the Operations. I'm hoping to find that Ingest doesn't look for those keys
there, since it is already pulling those values from elsewhere.
Before I start down this path. Is anyone already working on the capture agent
workflow (Tobias)?
Thanks!
Karen
From:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<workflow xmlns="http://workflow.opencastproject.org";
xmlns:ns2="http://org.opencastproject.security";
xmlns:ns3="http://mediapackage.opencastproject.org"; state="PAUSED" id="78">
<template>scheduling</template>
<title>Scheduled Workflow</title>
<description>This workflow definition defines the steps involved in
scheduling a recording,
capturing it, and ingesting it, after which processing operations may be
added. </description>
...
</operations>
<configurations>
<configuration key="schedule.start">1354302000000</configuration>
<configuration key="schedule.stop">1354302300000</configuration>
<configuration
key="schedule.location">demo_capture_agent</configuration>
</configurations>
<errors/>
</workflow>
-------------
To:
(Plan A)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<workflow xmlns="http://workflow.opencastproject.org";
xmlns:ns2="http://org.opencastproject.security";
xmlns:ns3="http://mediapackage.opencastproject.org"; state="PAUSED" id="78">
<template>scheduling</template>
<title>Scheduled Workflow</title>
<description>This workflow definition defines the steps involved in
scheduling a recording,
capturing it, and ingesting it, after which processing operations may be
added. </description>
...
</operations>
<configurations>
<configuration key="schedule.start">1354302000000</configuration>
<configuration key="schedule.stop">1354302300000</configuration>
<configuration
key="schedule.location">demo_capture_agent</configuration>
<configuration key="distribution">Matterhorn Media
Module</configuration>
<configuration key="trimHold">true</configuration>
<configuration key="workflowDefinitionId">full</configuration>
<configuration key="archiveOp">true</configuration>
<configuration key="videoPreview">true</configuration>
</configurations>
<errors/>
</workflow>
Plan B is to create a REST endpoint so the View Info javascript can GET
Recording's Agent Parameters in a non iCal format!
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
