Table of Contents
Advertisement
The MetadataExtensions.cfg file must be on every computer on which a user would edit
or modify the recording policy. If not, the metadata values could be lost.
When you create, configure, and implement a MetadataExtensions.cfg file, the Metadata tab
will appear in Camera Policies. It will contain the Query blocks listed in the IngestMdExt block
(see details below):
Metadata search options will be available in the Surveillance Video Manager to enable searches
using metadata associated with already captured videos.
When you ingest metadata, special characters normally interpreted as wildcards (?, *, #,
!, ~, ^, &, [ ], { }, \, ") are not interpreted as wildcards. When you search for metadata,
however, wildcards are recognized. Consequently, if metadata that you ingest contains
characters that are normally interpreted as wildcards, when you search for metadata you
need to use the escape character (\) to denote that the wildcard is intended literally, not
as a wildcard. For example, if you ingest 16*37 as metadata, and you then want to
search for this expression, you would search using 16\*13.
The search type options will be identical to those you defined in the ModMdExt block
(see details below).
Create a MetadataExtensions.cfg
You can create MetadataExtensions.cfg using any text editor. Once created, it needs to be
added to the following path: <install-dir>\Config.
MetadataExtensions.cfg is block structured text file. At the end of this section, you will find a
sample MetadataExtensions.cfg. You can implement the file as is (at the path noted above) to
see how it works or modify the file to meet your own criteria and then implement it.
MetadataExtensions.cfg comprises three Blocks (IngestMdExt, SearchMdExt, and ModMdExt)
which comprise one or more Query blocks each.
Record and Capture Video Feeds
111
Advertisement
Table of Contents
