Other Topic Library Versions

Adding an export rule

The GV STRATUS Rules Engine can watch a source location that is in the GV STRATUS system and export assets that match your criteria to a location that is external to the GV STRATUS system. An export rule can export clips, subclips, and playlists. For playlists, a conform job is automatically triggered to render the complex asset as a simple clip. The Rules Engine exports the assets to the destination that you configure. For an export rule, only K2 storage locations are available as the source scope. Other locations, such as FTP, are not available.
  1. Log in to the GV STRATUS Control Panel application with administrator privileges.
  2. In the GV STRATUS Control Panel application, click General | Rules.
  3. Click Add. Rule Editor settings open.
  4. In the Rule Type drop-down list select Export.
  5. In the Name field type in a name for the rule you are configuring.
  6. In the Description field type in a description for the rule you are configuring.
  7. In Rule Options settings, specify the rule behavior.

    1. Select the Visible in STRATUS UI check-box if you want to trigger the rule via context menu in the Asset List panel.

      By default, all users can see all rules that had been set to Visible in STRATUS UI.

      To configure the rule to be only visible to specific user or user groups, click the button.

      The Modify Rule Permissions dialog box appears.

      To assign permissions, click + and enter any user or group in the Add Users or Groups dialog box. If necessary, click Advanced to open Windows operating system dialog box to find and validate users or groups.

      • + : Opens the Add Users or Groups dialog box to assign users or groups with permissions.
      • - : Removes a user or group from the list.

      After adding specific user or group, set permission for Apply in UI setting by selecting Allow or Deny as appropriate.

    2. Select whether the rule copies the asset.
    3. Select whether the rule renames or overwrites the asset.
      • Rename: The rule appends a suffix to the new asset file name. The existing asset is retained.
      • Overwrite: The new asset overwrites the existing asset. The existing asset is deleted.
    4. Select when the rule is applied each asset.
      • Execute rule only once per asset: The rule is applied once per asset. The Rules Engine uses data stored in the asset's ExecutedByRules metadata field to determine if the rule has been applied to the asset. If it has been applied, the Rules Engine does not apply it again, even if the rule criteria still match for the asset.
      • Execute every time rule conditions apply: The rule can be applied multiple times per asset, if the asset matches rule conditions multiple times.
    5. Select the priority that the Rules Engine processes the rule, with the transfers and transcodes the rule controls, when there are multiple rules in a queue waiting to be processed.
      • Priority: High: Put this rule in a queue with other high priority rules and process through the high priority rule queue before any normal priority or low priority rules.
      • Priority: Normal: Put this rule in a queue with other normal priority rules and process through the normal priority rule queue after any high priority but before any low priority rules.
      • Priority: Low: Put this rule in a queue with other low priority rules and process through the low priority rule queue after any high priority or medium priority rules.
    6. Select the condition when the rule is applied to each asset.
      • Apply rule on growing file: The rule is applied to all files, including those that are still recording.
      • Apply rule on completed files: The rule is only applied to files that have finished recording.
  8. In Rule Notification settings, specify the notification behavior, if desired.

    1. Enter email addresses to which emails are sent. Separate multiple email addresses with a comma.
    2. Select one or more notification types:
      • Delivery Failed: Emails are sent if the rule operation fails.
      • Delivery Completed: Emails are sent if the rule operation succeeds.
    In order to send emails, the email server must be configured in Workflow Engine settings.
  9. In Scope settings, specify the location or locations in which the rule operates.

    1. Click Add location. The Location Selection dialog box opens.
    2. Navigate to and select the desired location.

      You can select multiple locations in the Location Selection dialog box.

      For Transfer, Export, Custom, Archive, and Transfer to Avid rules, you can also select logical asset locations under Groups | Lost and Found.

      If desired, you can edit scope location path manually in the text box.

      This is the location that contains the files on which the rule operates. Every time the rule runs, it looks in this location to determine if there are any assets that match the rule conditions and then operates on the assets that match.
    3. Click OK. The location is added to the Scope list.
    4. For a location in the list, if you want the rule to operate on sub-folders as well, select Include Subfolders. When this is selected, if there are multiple directories under the selected location, the rule operates in each of the sub-directories.
    5. Repeat these steps to add additional locations as desired.
    6. To change a location in the list, click the Browse button
    7. To remove a location from the list, click X.
  10. In Export Filename Format settings, set the convention for the name of the exported file.

    1. Select each filename option that you want to be a part of the exported file name.

      The order in which you select filename options determines the order in which they appear in the file name.

    2. Make sure Add Format Name is selected if you intend to configure Export Options settings for multiple transcode formats.

      Multiple transcode formats result in multiple files, so the format must be part of the name to avoid file overwrite. One transcode format results in one file only, so the format is not required as part of the file name.

    Asset Name is set by default, as the exported file or files must have a name.
  11. In Frequency settings, specify how often the Rules Engine triggers the rule.

    1. Select one of the following options:
      • Metadata Change: The rule is constantly monitoring files in the “Scope” folder (and file types depend on the rule condition).
      • Periodically: Sets the number of minutes.
      • Daily: Sets the number of days.
      • Weekly: Sets the number of weeks.
      • Monthly: Sets the day of each month.
      • STRATUS UI only: The rule is only applicable when triggered by users via the context menu in Asset List of the STRATUS UI.
      For Daily, Weekly, and Monthly options, a Start Time setting opens. Set the day and time the rule is triggered for the first time.
  12. In Export Options settings, configure the format of the exported files.

    You can select either a Native Format or a Transcode Format, but not both.
    1. For Native Format, select the interchange standard in which to export. When a Native Format is selected, Transcode Format is automatically set to None and disabled.
    2. For Transcode Format, configure as follows:
      • Select None: The exported file is the same format as the source on the K2 storage system.
      • Select one or more transcode formats as follows:
        • Select a single format for the transcoder.
        • To use multiple formats from a single transcoder, select the formats for that transcoder.
        You cannot select multiple transcoders.

      To select multiple formats, first make sure that in Export Filename Format settings, Add Format Name is selected. If Add Format Name is not selected, only one transcode format is allowed.

      When a Transcode Format is selected, Native Format is automatically set to None and disabled.

      The Transcode Format list is populated by the transcode profiles that you create and place in the transcode profile directory.

      Supported transcoders include Harmonic ProMedia™ Carbon (formerly Carbon Coder™), Telestream Vantage™, Elemental® , Harmonic WFS, and GVRE Transcoder.

      You can also select STRATUS Native Proxy Format in the Transcode Format list so existing proxy assets can be exported without the need for transcoding.

      If no high resolution asset is available, you can still export the proxy asset and XML metadata file from the location in Groups | Lost and Found.

    3. For Metadata Format, select as follows to additionally export an XML metadata file:
      • None: No additional XML metadata file is exported.
      • Final Cut Pro: Metadata is exported to a Final Cut Pro project XML file. Set all other Export Options to None to export metadata only.
      • GV STRATUS Simple: Metadata is exported to a GV STRATUS schema XML file.
      These metadata format selections are XSL transforms of the STRATUS XML metadata. If you need a customized transform for your workflow, contact Grass Valley Support. Set all other Export Options to None to export metadata only. If you select a metadata format, the Metadata-Destination Path field is enabled.
    4. For Metadata-Destination Path, configure as follows:
      • If you are exporting the metadata file to the same destination as the asset file, leave this field blank. The file goes to the path configured in Destination settings.
      • If you are exporting the metadata file to a different destination than the asset file, enter the metadata file's destination path. For an FTP path, use a ftp://server/path convention. For a UNC path, use a \\server\share\path convention.
    5. If you entered a Metadata-Destination Path, configure User Credentials for that destination.
    6. For Thumbnails - Marker, select as follows:
      • None: The export does not contain thumbnails.
      • Marker Thumbnail Quality - High: High: The export contains a full-resolution JPG thumbnail with no compression (100%).
      • Marker Thumbnail Quality - Medium: The export contains a full-resolution JPG thumbnail compressed 85%.
      • Marker Thumbnail Quality - Low: Low: The export contains a half-resolution JPG thumbnail compressed 70%.
      • Reference Thumbnail Quality - High: High: The export contains a key-frame marker with full-resolution JPG thumbnail of no compression (100%).
      • Reference Thumbnail Quality - Medium: The export contains a key-frame marker with full-resolution JPG thumbnail compressed 85%.
      • Reference Thumbnail Quality - Low: Low: The export contains a key-frame marker with half-resolution JPG thumbnail compressed 70%.
      An export thumbnail is defined by a tn marker added to the source asset. Multiple thumbnails are exported when the source asset has multiple tn markers. Additionally the default or user defined thumbnail can be exported. Exported thumbnail files are automatically named according to asset names with the timecode extension _hh-mm-ss-ff so that each JPG file can be differentiated. The first exported thumbnail JPG file has the same name as the asset.
    7. For Closed Caption Format, select as follows:
      • None: No additional Close Caption file is exported.
      • K2-SCC: Workflow Engine extracts CEA-608 information stored in Ancillary data (CEA-708) from the asset on the K2 system and exports to a file in SCC format.
      • K2-SRT: Workflow Engine extracts CEA-608 information stored in Ancillary data (CEA-708) from the asset on the K2 system and exports to a file in SRT format.
      • K2-TTML: Workflow Engine extracts CEA-608 information stored in Ancillary data (CEA-708) from the asset on the K2 system and exports to a file in TTML format.
      Only K2 system metadata extraction is recommended. It has much better performance than transcoder metadata extraction. If you select a Closed Caption format, the CC-Destination Path field is enabled.
    8. For CC-Destination Path, configure as follows:
      • If you are exporting the Closed Caption file to the same destination as the asset file, leave this field blank. The file goes to the path configured in Destination settings.
      • If you are exporting the Closed Caption file to a different destination than the asset file, enter the Closed Caption file's destination path. For an FTP path, use a ftp://server/path convention. For a UNC path, use a \\server\share\path convention.
    9. If you entered a CC-Destination Path, configure User Credentials for that destination.
    10. For Audio Mapping Profile, configure as follows:

      • The Native Format setting must be set to Material eXchange Format (mxf). If set to any other format, the Audio Mapping Profile drop-down list is not selectable.
      • Audio Mapping Profiles must have been configured in the Audio Tag Management setting of GV STRATUS Control Panel prior to configuring rules.
      • If you want to transfer content with a subset of the existing audio tracks to Avid, you can configure an existing Audio Mapping Profile to the locations configuration.
  13. In Destination settings, define the destination location on which the rule operates.

    For Export rules, the destination must be a location that is external to the GV STRATUS system and not managed by the GV STRATUS system. An external location is not visible in the GV STRATUS application Navigator panel.

    You can set any destinations for exports as follows:
    • FTP path: ftp://server/path
    • UNC path: \\server\share\path
    • FASP path: fasp://<Aspera server>/<directory name>

    If the destination is a network share accessible from the machine hosting the GV STRATUS Control Panel application, you can click the Browse button to configure Destination Path.

    The Firewall friendly checkbox is only visible if the selected Native Format is GXF or MXF, and FTP path is entered as the destination path. If the Firewall friendly checkbox is selected, asset transfer will be performed by the Data Mover engine. If not selected, asset transfer will be performed by K2 Summit.

  14. Configure User Credentials as required. If a UNC path destination, requirements for user credentials are as follows:
    • If both the K2 system and the export location are on the same domain, you can use domain credentials.
    • If the K2 system and the export location are on different domains and the domains have a trust relationship, you can use domain credentials.
    • If the K2 system and the export location both have a local user with the same name and password, you can use the local user credentials.
    Other UNC path user credentials are not supported.
  15. In Rule Conditions settings, specify the conditions the Rules Engine looks for to qualify an asset.

  16. In the Select items when drop down list, select one of the following:
    • ALL of the conditions below are met: Assets that match all conditions.
    • ANY of the conditions below are met: Assets that match any condition.
    • Custom: A Custom Expression field opens in which you can enter a custom expression.

    Conditions and custom expressions are similar to those in GV STRATUS Advanced Search. Simple boolean operators AND, OR, and NOT are supported. Enter these operators in all capital letters.

  17. Configure conditions as follows:
    • For each condition (1, 2, 3, 4, etc) click the Add Condition button and select from lists to define the condition.
    • Click the X button to remove a condition from the list.

    The is Empty setting and the period (.) mark are also supported when creating conditions. In case you want to use a ‘relative time’ (for example the asset ‘Modified Date’ is before 2 minutes ago) as a rule condition, you should not use rule triggers based on ‘Metadata Changes’ but use ‘periodically’ rule triggers only and enter a cycle time (for example 3, 4 or 5 minutes). This is because when a ‘relative time' matches the condition, but no metadata change happens at the same time, the rule will not trigger in your operation.

    If a newly created custom metadata field is not available in the Add Condition dialog, restart the GV STRATUS Control Panel application.

  18. In Set Metadata settings, define the metadata that Rules Engine will set during the execution of a rule for an asset.

  19. Configure metadata as follows:
    • For each metadata, click the Add Metadata button and select from the drop-down list to select the metadata.
    • Define the metadata value which will be added into the data field of the asset when the rule is applied to.
    • Select whether to enter the metadata value at the start or the end of the rule workflow.
    • Click the X button to remove a metadata from the list.

    If a newly created custom metadata field is not available in the drop-down list, restart the GV STRATUS Control Panel application.

    You can create new custom metadata by selecting Core | Metadata | Custom Metadata | Add in the GV STRATUS Control Panel.

  20. Click Save.
In the exported content, custom metadata values entered here replace any current values. So if you previously entered values for these same custom metadata fields elsewhere in the GV STRATUS system, those values are overwritten in the exported content by the values you enter here.
Next, enable the rule.

Copyright © 2018 Grass Valley Canada. All rights reserved. GV STRATUS 6.5 gvtp_20181001_01:18:31