Target and Process Policies Processing Tab

Previous Next  Print this Topic

Use the Processing tab to define settings for how you want to process files or video. The contents on the Processing tab are the exact same as displayed in User Preferences. The preferences entered in at the Processing tab override any defaults that may be set in the User Preferences window, but only for the current job or policy.

Target and Process Policies - Processing tab

Video Processing Options

Use these options to ingest video files for viewing. Elect to generate low resolution proxy videos (also called companion files), preview images during video ingest, or extract closed captioning. The low resolution proxies and preview images have a relatively small file size, making it quick and easy to search for video files and clips without having to wait for the retrieval of large, original video files.

Select the Process Video Components checkbox to process video and for the associated options to enable. If not selected, video files ingest, but search applications cannot open and view them as video files, and preview images are not generated.

Elements

Description

Generate low resolution proxy

1.Select to generate low resolution companion files. If not selected, the proxies do not create, but you can always view the original video in the Information Repository.

The low resolution file is a fraction of the size of the original video size. When searching for video, the low resolution video is the primary video footage received, but it is always teamed with the original source video. The original, stored either online, near-line, or offline is totally accessible when needed and under full Phoenix VCM management.

2.Select a resolution quality setting for the proxy/companion video. A lower setting produces a smaller file.
High - Same frame size as original, high video quality, audio is compressed to QDesign 44kH.
Medium - 320x240 frame size, medium video quality, audio is compressed to QDesign 44kHz
Low - 320x240 frame size, low video quality, audio is compressed to QDesign 14kHz
3.Select the Save copy of low resolution proxy checkbox to save an additional copy of the low resolution file, and then type a path in the Location text box, or click the Browse button to navigate to a save location.

Alternatively, you are able to use third party software to create low resolution proxy files that will be included with the ingested video or image. See Telestream Vantage and FlipFactory for more information and setup instructions.

Phoenix VCM is unable to generate thumbnails and low resolution proxies for files that are not videos or images.

Generate preview image

1.Select to generate a preview image; if not selected a preview image is not created.
2.Use the Preview image quality drop-down list to select a resolution setting. A lower setting produces a smaller file.
High - Original size
Medium - 320x240
Low - 100x75
3.Select the Save copy of preview image checkbox to save an additional copy of the preview image, and then type a path in the Location text box, or click the Browse button to navigate to a save location.

Extract Closed Captioning

1.Select to extract closed captioning text (if it exists), and to search against its contents. The extracted closed captioning text becomes the base for performing script searches when viewing a video in a media player, or when creating a search in the Search Criteria pane.
2.Select the Save a copy of Closed Captioning checkbox to save an additional copy of the closed captioning text, and then type a path in the Location text box, or click the Browse button to navigate to a save location. The generated file will be name <filename>_cc.srt, where <filename> is the name of the video it corresponds to.

Closed captioning text may be extracted from mpeg-2 video files if it exists in the picture user data as defined in the EIA-708 standard.

Alternatively, you can ingest a closed caption file,  when ingesting the video file, instead of having it generated. The ingested file must have the name <filename>_cc.srt, where <filename> is the name of the video it corresponds to. Target and Process will not generate a closed caption file if you supply your own.

Picture Processing Options

Use these options to ingest picture files for viewing in Phoenix VCM search applications. Elect to generate preview images, or thumbnails, when picture files are ingested. Since these files are typically a smaller file size, searching for picture files is quick and easy, without having to wait for the retrieval of large, original picture files.

Select the Process Picture Components checkbox to process picture files and for the associated options to enable. If not selected, picture files are ingested but the preview images are not generated and viewable in Phoenix VCM search applications.

Phoenix VCM is unable to generate preview images for picture files with file names that contain `, ", $, or \.

Elements

Description

Generate preview image

1.Select to generate preview images. If not selected, preview images do not create, but as long as the Picture Processing Options checkbox is selected, you can view picture files in the Information Repository.
2.Select an image quality resolution setting for when preview images are generated. A lower setting produces a smaller file.
High - Original size
Medium - 320x240
Low - 100x75
3.Select to save an additional copy of the preview image to a location outside of the Information Repository. Type a path in the Location text box, or click the Browse button to navigate to a save location.

File Processing Options

Use to set processing options for permissions, file processing, and metadata processing.

Elements

Description

Override original file permissions to allow any user to retrieve

Phoenix VCM adheres to the level of rights and access control that is set for the operating system where files are  ingested from. Typically, only the owner, author of the files or a system administrator with administrative or root level access privileges is able to view, open, and retrieve files in the Information Repository.

Select to allow access on stored files so any user can retrieve files.

This feature negates all protection associated with your files; anyone on your network using Phoenix VCM can access your stored files.

File Grouping Processing

Active only when Phoenix VCM plug-ins are implemented, this option determines how ingested files are grouped and recognized by search clients. Use this feature to group non-video files with video files so search results include all associated files.

Select from options:

None - No file grouping.

Files in each folder together - Groups files by folder so  all of the files in any given ingested folder are in a single group.

All files together - Groups all of the files in a job into one group, regardless of what folder they are in.

For example, if ingesting a video file, a metadata file for the video, and an .stx file for the video from the same folder, and you want them all to be returned when searching for just the video file, you would select Files in each folder together; if they are in disparate folders, you would select All files together.

File grouping does not affect the folder structure seen in Search and Retrieve.

Extended Metadata Processing

Add custom metadata to files that are being ingested. In contrast to the Metadata tab, which allows you to manually add metadata during ingest processing, the Extended Metadata Processing allows you to programmatically add metadata, on a per directory or per file basis, during ingest processing.

Ingest.ExtMetadata, <filename>.md, and script files have diverse purposes, select from options:

None - No extended metadata processing.

Use Ingest.ExtMetadata - Affects files in its own folder and child folders. If a child folder has its own Ingest.ExtMetadata, files in that folder and its child folders use it instead of a Ingest.ExtMetadata in a parent folder.

Use '.md' file - Adds metadata only to files that have an identical filename and reside in the same folder. For example, if a .md file is created and named films.md and it is placed in a folder in primary storage, metadata would be added, at ingest, only to the file named films.doc in the same folder.

Use script - Adds metadata based on a user-provided script file located in the Config folder in the Phoenix installation directory. The file must be named UserExtMdProc.bat (for Windows) or UserExtMdProc.sh (for Linux/Mac). This script file will create an XML file for the metadata values that will be added at ingest with the files being ingested.

Low resolution engine

Choose which engine to use to generate low resolution proxies when ingesting files.

Select from options:

ffmbc first, then QuickTime

QuickTime only

ffmbc only

default - This will be your system default.

Setup for Extended Metadata Processing

Using Ingest.ExtMetadata and <filename>.md

There are three different delimiters available for use when creating a Ingest.ExtMetadata or a <filname>.md file. You can use a:

Equal sign: <token>="<value>"
Tab: <token>        "<value>"
Comma: <token>,"<value>"

Delimeters must be consistent within the file and cannot be mixed. The first delimiter found (equal sign, tab, or comma) will be used as the delimiter when parsing the rest of the file. The following example uses an equal sign (=) as the chosen delimeter.

DVD_Title="The Passion of the Christ"

Actors="James Caviezel Monica Bellucci Maia Morgenstern Christo Jivkov Francesco De Vito"

Directors="Mel Gibson"

Writers="Mel Gibson Benedict Fitzgerald"

Producers="Mel Gibson Bruce Davey Enzo Sisti Stephen McEveety"

Format="AC-3 Closed-captioned Color Dolby DTS Surround Sound DVD Full Screen Subtitled NTSC"

Language="Hebrew"

Subtitles="English Spanish"

Region="1"

Aspect_Ratio="1.33:1"

Number_discs="1"

DVD_Release_Date="2004/08/31"

Run_Time="127 minutes"

Tokens may not contain spaces, and values must be enclosed in quotation marks.

When using an equal sign as a delimiter, there can be no white space before or after the equal sign.

If you use multiple values for a single token and want to find a single value using a Phoenix VCM search application, search using "contains". If you searched using "equals", only results that match the full string of multiple values would be returned.

Follow these steps to implement an extended metadata Ingest.ExtMetadata or <filename>.md file:

1.Create the Ingest.ExtMetadata or <filename>.md file using any text editor.
2.Name it either Ingest.ExtMetadata or <filename>.md depending on the functionality you want.
3.Copy Ingest.ExtMetadata to a folder where all files have associated metadata. Copy <filename>.md to folders where a specific file, named identically to <filename>, is to have associated metadata.
4.Select an extended metadata option from the Extended metadata processing drop-down list on the Processing tab.

Using Script

Selecting the option Use script for extended metadata processing will add metadata based on a user-provided script file. There are two phases to processing extended metadata: Process and Finalize. In each phase, certain parameters are passed to the user-provided script file in a file in the following format:        

<EmdScriptParameters>

   <Phase>Process</Phase>

   <TargetFile>/file/being/stored</TargetFile>

   <IsContainer>No</IsContainer>

   <OutMdFile>/location/of/output.xml</OutMdFile>

</EmdScriptParameters>

Phase = Process or Finalize

TargetFile = The file being stored in the Information Repository

IsContainer = Yes or No and indicates whether the target file is a container (directory) or a file

OutMdFile = The location of the XML output file that the script will generate

The above example is in the first phase, Process. When Use script is chosen on the Processing Tab of Target and Process Policies, Target and Process Policies calls the user-provided script and passes it a file with the arguments listed in the example above. The script needs to create an XML file for the metadata in key/value pairs. These key/value pairs will be contained within ExtendedMetadata tags as shown below.

<ExtendedMetadata>

   <Key>Value</Key>

   <Key>Value</Key>

   <Key>Value</Key>

</ExtendedMetadata>

The XML output file needs to be created in the location specified by the OutMdFile parameter that was passed to the script by Target and Process Policies.

After the XML file has been created by the user-provided script and the Process phase is complete, Target and Process Policies will call the script again with a new file. Now it is in the Finalize phase and the preliminary XML metadata values will be included in the EmdScriptParameters block that is passed to the script.

<EmdScriptParameters>

   <Phase>Process</Phase>

   <TargetFile>/file/being/stored</TargetFile>

   <IsContainer>No</IsContainer>

   <OutMdFile>/location/of/output.xml</OutMdFile>

 

   <ExtendedMetadata>

       <Key>Value</Key>

       <Key>Value</Key>

       <Key>Value</Key>

   </ExtendedMetadata>

 

</EmdScriptParameters>

At this point during the Finalize phase, the user-provided script will have a chance to normalize the preliminary metadata values that were included within the EmdScriptParameters block and make any corrections or changes if needed. The script will create a new XML file with the final metadata values at the location specified by the OutMdFile parameter that was passed to the script by Target and Process Policies during the Finalize phase. The final XML file at the location specified by the OutMdFile parameter will be used by Target and Process Policies to create metadata that will be processed and included with each file or folder that is being ingested.

To see an example script file, go to http://www.SoleraTec.com and visit the Phoenix VCM Resources page.

Follow these steps to implement an extended metadata Script file:

1.Create the batch/script file that will produce metadata in an XML format (as shown above).
2.Name the existing file UserExtMdProc.bat (Windows) or UserExtMdProc.sh (Linux or Mac).
3.Place the file in the Config folder in the Phoenix installation directory.
4.Select the Use script option from the Extended metadata processing drop-down list on the Processing tab.