FYI - preserving the mpeg-7/text flavor did not help it getting found
during the flavor tagging in a future workflow's publish.
The Mpeg-7/text file named "slidetext.xml" was ignored and a
non-existent file named "0" (on the same path) was sent instead.
Sent, doesn't exist:
/.... /files/mediapackage/5d0adaee-96ed-4413-9043-b249c2788133/catalog-4/0
Not sent, does exist:
/..../files/mediapackage/5d0adaee-96ed-4413-9043-b249c2788133/catalog-4/slidetext.xml
- Karen
On 9/26/2012 8:53 AM, Karen Dolan wrote:
During the workflow's publish step, the Engage server chokes with a
bad link to the mpeg-7 file. Engage can not parse the empty xml in the
link sent, so it logs the error and leaves the workflow hanging. The
link sent was to an empty file on the Admin server, not the good link
to the mpeg-7 file on the Engage server.
"2012-09-25 16:43:50 WARN (StaticMetadataServiceDublinCoreImpl:293) -
Unable to load metadata from catalog
'http://admin...edu/episode/archive/mediapackage/12a663c2-78c1-4ace-bc95-f60fec00ee4b/49037340-33e9-43f8-8a9d-7dba29d0cbef/0'
2012-09-25 16:43:50 DEBUG (SolrIndexManager:383) - Looking for mpeg-7
catalogs containing segment texts ...."
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
