Table of Contents
Advertisement
296
Buffalo Surveillance Server
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.
Pay particular attention to braces [ ]; there needs to be an opening brace after
"IngestMdExt" and a closing brace after its last Query block; an opening brace after
"SearchMdExt" and a closing brace after its last Query block; and an opening brace after
"ModMdExt" and a closing brace after its last Query block.
Query block statements describe the controls that will appear on the application. These can
include any number of string fields, check boxes, spin controls, pathname fields, and choice
controls. Each Block can have any number of Query blocks. Its best to ensure that the
IngestMdExt block and SearchMdExt contain the same Query blocks since the Buffalo
Surveillance Server will search for only ingested metadata. However, if you prefer, the Query
blocks contained in SearchMdExt can be limited to a subset of those you have in IngestMdExt.
In this case, you will be able to search only based on the Query blocks listed in SearchMdExt.
If a Query block contains an error, the entire metadata extension block (IngestMdExt or
SearchMdExt) will be ignored.
Metadata Extension Block Structure
The following example is only for the sake of illustration. Note that tokens can not be used in
Query blocks indiscriminately. Each Query block supports only specific tokens. See Valid
Token/Values for Query Blocks below for details.
Advertisement
Table of Contents
