What considerations should be given to I/NET SEVEN and ID Works during the setup procedures?

[Product_Support]

Issue

What considerations should be given to I/NET SEVEN and ID Works during the setup procedures?

Environment

• I/NET Seven
• DataCard ID Works

Cause

Some best practices when considering implementing DataCard ID Works during setup with I/NET Seven. 

Resolution

Consider the following suggestions as you configure your ID Works project for use with I/NET Seven:

1. Keep Image Path Short
   When you create a project that will be accessed from PC’s across a network, keep the image paths as short as possible. Long images paths accessed across the network can slow the performance of your Video Badging system.
    
2. Define a "UNC" Image Path
   In a network, the Universal Naming Convention (UNC) is a way to identify a shared file without having to specify (or know) the storage device on which it resides. This type of path will allow ID Works users at different machines across the network to successfully retrieve image files. Please refer to the DbCreate chapter in the I/NET Seven “Getting Started” guide for more information about UNC paths.
    
3. Store a Project's Images at a Single Location
   An ID Works project does not allow you to store images in multiple locations. Therefore, if you assign images to individuals from within I/NET Seven, ensure that each image is stored at the single location used by the ID Works project.
    
4. Rules for Multiple Image Location
   If the site requires multiple Image locations. It requires an ID Works Project defined for each image location. Note these Projects can be of the same design, however, the file name of the project must be different.