Create Recurrence Recordings

Workflow Description

As a user, you may want to configure recurring recordings. In this case, the user wants to save time by filling in certain data at the recordings again and again (inherited metadata). For this purpose it is possible to define certain information once at the recording and then have it available at every recording. It can happen that recurring recordings collide with other scheduled recordings. In addition, the user does not want all repetitive recordings to be already stored in VidiCore. For this purpose, the system creates temporary recordings, which are automatically or manually scheduled by the user and transformed into regular recordings. If there is a collision with another recording at that time, the system alerts you to become active.

If the recording is initiated by the system or manually, the state of the recording is persisted and loses the dependency on the repeat pattern. A subsequent change of the recurrence rule does not change an initiated recording.

Motivation and Considerations

To not create again the same recording with entering similar datasets.

Recurring recordings are motivated by creating a series of recordings to be scheduled recurrently with the same data. The function supports vidicore's inheritance logic regarding metadata.

A collection is created for every Booking definition item in Vidicore which represents the recurring recording.

Inherited metadata can by manually overwritten by the user.

For recurrence recordings lying in the future, a placeholder “Virtual Recording” is created. Two days (configurable) prior to the recording, the recording is instantiated. This step can also be done by the user. After instantiation, the Booking Component is available for metadata support etc.

If virtual recordings are planned as pool recording, they will be shown in unassigned lane under the pool if the system is not able to automatically place them.

An action for a collision of virtual recordings will be created by the system, which has to be solved by the user.

If a single recording is manually edited by the user then this is recording is no longer considered in the reoccurrence series.

Collections are created by VidiControl itself in VidiCore (Booking Definitions). The collections will not get a deletion lock from VidiControl. Please be aware that as long as an item exists inside of a collection the collection must be saved from deletion.

For every Booking Definition VidiControl will create a Collection. VidiControl will set the metadata V3_CollectionType for Collections in VidiCore at this collection.

Step by Step

Phase 1

The user creates a new Booking among the possibilities that the system offers him. See Create a New Booking

Phase 2

After the Booking dialog opens the user switches directly to the Definition tab and selects Recurrence to on:

The recurrences specification opens and can be edited Area: Create a Booking Definition [VCon UG]. After the specification the user has to confirm with save.

Occurrences are limited to 100. This can be changed in the VidiControl Config UI. VidiControl does not take any responsibility for performance problems if more repetitions are allowed.

Phase 3

The user switches back to the Components tab. The recordings have to be created. In this case the user defined three daily recordings. The recording times and sources are the same. The recording will already be scheduled, if the start time is within the next 48 hours. Otherwise, a virtual recording is created. The upcoming will be virtual recordings with the state planned and are displayed crosshatched on the timeline. Area: Timeline | Timeline-Indications

Phase 4

The user can manipulate the individual recordings if needed. As long as the virtual recording is not planned the user cannot edit metadata. Also inherited metadata will be shown here.Inherited Metadata For creating a scheduled recording from a planned (virtual recording) the user has to manually initiate the recording. After that manual step a VidiCore item is created and metadata can be set. The system will automatically plan a virtual recording if now collision is detected. Otherwise an action will be created for the user to solve the collision. Solve Actions