If the preview videos do not have the flavor "*/preview", the "eye" icon is not displayed
Steps to reproduce
Steps to reproduce:
1. Modify the default workflow ("ng-partial-preview.xml") so that the videos tagged as "preview" have a flavor different from "/preview". For instance, "/test"
2. Ingest a video using the "Process upon upload and schedule" workflow, checking the "Hold" option
The workflow runs without errors, the "preview" tag is correctly applied and the files are correctly arquived, but the user cannot see the "eye" icon to preview the video and continue processing.
The preview videos that were published internally should be displayed, regardless their flavour.
EDIT: Rationale for the need to change this behaviour:
The "Event.java" class models an event in the new admin UI. Apart for the serialization logic, it includes some methods (like the one attached) that control the behaviour of this object. However, if the property "has_preview" should depend exclusively on the subflavors of the published elements, then why are there also a getter and a setter method for the property? A simple method "hasPreview" or "getPreview", which returns the result of "subflavorMatches" would be more consistent, and it can be annotated for serialization as well.
On the other hand, making the "has_preview" property depend exclusively on the flavor subtype prevents the workflow designers to re-use a different MP element as the preview. What if I want to use the "work" flavor as the preview, and thus avoid an extra encoding to generate it? What if I assume that my operators will always be in my institution's internal network and it makes no difference to use big video as the preview, because it will load quickly anyway?
In order to allow any arbitrary flavor as the preview video for the editor, the "has_preview" condition should be like "this mediapackage contains at least one track that is published internally". There is no need to make any more restrictions.
Just closing old issues.
Hi Rubén, I checked the configuration section of the documentation and unfortunately didn't find anything about it. http://docs.opencast.org/r/2.0.x/user/configure/
I'm not even sure it this would be the correct place to document it. The configuration file itself is documented as all the others, maybe this is sufficient enough.
That is nice to hear! I'm afraid I missed this file. Is it documented somewhere?
Thanks for your answer and best regards!
There is a configuration file to change the name of the 'preview' sub-flavor.
So you could change it to 'test' instead and get the same results as with the 'preview' behavior.