Data Discovery Settings

Thread Count

Specifies the number of concurrent threads that will be running during data discovery

Default Settings

The following settings are applied across all discovery locations.

Ignore Imagery Without Spatial Reference

Excludes data without spatial reference from the index

Calculate MD5 Checksum

Detecting duplicate data within your index can be performed using MD5 checksum, which is a very accurate method of detection. However, the calculation is slower than the default methods of detecting duplicates (using a content hash and schema hash) , so this option should only be enabled if a high degree of accuracy is needed in duplicate detection.

Build Thumbnails in Separate Process

Thumbnails can be built within the same process as the data discovery, or within a separate process. Building thumbnails in a separate process means all results will be displayed quickly, but their thumbnails may take a bit more time to be generated. The alternative of building thumbnails within the same process as the data discovery is that the overall indexing time for a large number of files is faster, but certain types of results such as MXDs and Layer Files will be slower to index.

Generate Raster Thumbnails On-The-Fly

Because generating raster thumbnails with GDAL is fast, you can choose to create thumbnails when a user views the data instead of doing it during the indexing process. This saves time during indexing and is most beneficial if you have large amounts of raster data to index.

Save Layer File for Rasters

By default Voyager does not create .lyr files for raster files that are indexed. If Voyager Desktop will not be installed, but you want the option to download .lyr files for items, you can choose to always save layers files for rasters.

Cache All Metadata Records

When metadata is stored as simple .xml files on disk, Voyager will show this file directly when someone askes to see the metadata in the UI. This works well when the index and data will stay together. If you intend to index data, and show the contents disconnected from the data, you may want to cache a copy of the metadata xml in voyager's internal cache.

Ignore Metadata

When indexing large repositories that do not have metadata or where you do not care about the metadata values, ignoring metadata can speed up the indexing process. This will avoid an extra File lookup for each file.

Skip Discovery Queue

While indexing, Voyager normally puts every file and folder into the discovery queue. This provides fault tolerance, gives good statistics, and allows for better indexing load balancing. When indexing large collections of very small data – the overhead to queue items can outweigh the the actual indexing time. In these cases, you may consider skipping the discovery queue.