DemandBridge Best Practices is designed to keep you informed and provide you with better and more efficient procedures. This first edition offers you some insight into managing your Image Library files.
|
Image Library
As you may already know, the DB Image Library is a module that captures all of the documents and journals that DB Distributor creates, and indexes them to the transactions to which they relate. External documents can be imported, or scanned and indexed as well. In addition to greatly reducing the need for filing, the DB Image Library also puts all of these digital files at your fingertips so that you spend less time searching for documents. It also allows you to reclaim your valuable office space where areas were previously committed to file cabinets.
However, using the same directory, year after year, for storage of your Image Library files can cause some latency when searching for a particular image among the thousands, or tens of thousands that might be stored. The following procedure will improve your server's performance as well as better organize your images so that they can be easily removed and stored offline when appropriate.
At the time of your DB Image Library implementation, the following path was probably designated for your Image Library files.
/usr/lib/pvx/images
Then under images you have the directories for each of the different image types.
As the full path name is kept in the IL1 file, you can change the path as part of your year-end routine and have images stored in a subdirectory associated with the year in which the image was created. For example:
/usr/lib/pvx/images_2009
/usr/lib/pvx/images_2010
/usr/lib/pvx/images_2011
This will allow you to back up and remove older directories that contain documents that are no longer routinely accessed. This frees up disc space, enhances performance, and reduces the size of your routine backups.
Changing the path is easy. |
