Future CERN Video Workflow

Wednesday 24 Apr 2013, 14:00 → 16:00 Europe/Zurich

VMO Office (CERN)

The main goal of the meeting was to agree on the scope of the next generation video submission workflow, users, validation and archiving.
 
It was agreed that what was discussed for videos should also be applicable to other kinds of multimedia documents, and as a starting point Ludmila mentioned that she is currently working on setting up something for photos and described the model.
 
The model for the videos will mimic the one being setup for photos:
·         Each user community will have their own video collection on CDS
·         The DG-CO video production team will have their own cleanly separated collection
o   A name should be proposed for this collection [Noemi]
·         An “Open” collection will be available for anyone with a CERN account to submit and archive a video on CDS
o   This collection will not be moderated but instead a “report inappropriate” button will be added to the page of the video. A mail may also be sent to the collection responsible (DG-CO, CDS?) for each submission.
o   DG-CO may even use this collection to post some of their (less official) work
·         A single “Videos” collection will allow to search and browse all the collections together.
o   This will be the main entry point for users seeking videos on CDS so this may cause problems while exposing non-CERN related activities (the “pizza” effect)
·         Each video collection will have its own numbering scheme (CERN-MOVIE-YYYY-NNN, ATLAS-MOVIE-YYYY-NNN, OPEN-MOVIE-YYYY-NNN etc.)
 
Then more specific details were discussed for the future service
·         The new submission workflow should include
o   An option to review the submitted clip before transcoding and publishing
§  This option already exists in the FCS workflow [Thomas to explain to Noemi]
o   An option to preview the produced web formats before their final publication on CDS
o   A simplified way to push the published video to other publishing service (like YouTube)
§  Probably from CDS
§  Including an optional approval workflow
o   A possibility to lock completed/published projects
§  This lock would prevent deletion/replacement of the files on the file storage system and modification of the metadata on CDS
§  If a modification is needed, the user should unlock the project first
o   Marek proposes to create a new service in Snow for the AV workflow
§  Thomas would rather wait to have a wider scope available before doing this not to raise expectations too prematurely.
·         Concerning the future specialized media asset management system (to replace Final Cut Server)
o   Noemi thinks it’s worthwhile to have a MAM system separated from CDS because it’s useful for the team’s daily work
o   If all user communities use (or are given the possibility to use) this MAM It should be possible to strictly separate user communities (this is not the case in Final Cut Server)
 
And other points for the current service:
·         There is a consensus on the fact that generating as many web formats for RUSHES as for MOVIES is useless, since rushes are seldom used and only by very few people
o   This number will then be reduced to 1 web format only [Thomas/Marek]
·         For very specific rushes, Noemi will concatenate the individual clips and submit only one big file
o   Requested by the Press Office for their stockshots