Destiny+TitlePeek

If you cannot read this message, please click here
 * || [[image:http://www1.vtrenz.net/imarkownerfiles/ownerassets/1036/Sales%20Exec%20LetterHeader1.jpg]]//The message below contains information for Destiny® Library Manager™ customers who also subscribe to the TitlePeek service. If you do not subscribe to the TitlePeek service, please disregard this message.//
 * || [[image:http://www1.vtrenz.net/imarkownerfiles/ownerassets/1036/Sales%20Exec%20LetterHeader1.jpg]]//The message below contains information for Destiny® Library Manager™ customers who also subscribe to the TitlePeek service. If you do not subscribe to the TitlePeek service, please disregard this message.//

**Yes, Your TitlePeek Images are in Destiny 9.5** If you have upgraded to Destiny 9.5, you may have noticed some changes in the way TitlePeek images display after the upgrade has been completed. Although the system is working properly, the information below will explain why images may or may not be appearing.

In Destiny 9.5, improvements were made to the TitlePeek caching process to increase performance and display title images more quickly. During a search using Destiny 9.0 or previous versions, TitlePeek images would display one at a time, as Destiny communicated live with the service that hosts the copyrighted images. With Destiny 9.5, the first time a topic is searched, Destiny will search the TitlePeek service and add all those images to the district cache. The images will display after the screen has been refreshed, or when the subsequent search is performed. The process applies separately for images in search results, title details and image size. For example, once a title appears in the search results, it is cached and will display when refreshed or when the subsequent search occurs. If the title is clicked on to show title details, the image in title details will be cached and will appear upon refresh, and when the title image is clicked on in subsequent title detail view s. Similarly, each title image size must be viewed once in order to be cached for future display.

Image caching applies across the district. Once an image is searched at any location in the district, the image is stored in the cache. The images are displayed instantly, instead of having to wait for each image to appear as they did in Destiny 9.0.

Once images have been placed in the cache, they are stored until the cache storage limit of 500MB is reached; however, before they are purged from the cache, Destiny reviews frequency of image usage, and images that have been used the least are purged first. The size of the memory cache may be adjusted. For instructions, read "How TitlePeek Image Caching Works in Destiny 9.5" at the end of this message.

The change to TitlePeek image caching in Destiny 9.5 significantly improves the availability and performance of TitlePeek images. The cache will continue to build and collect images more quickly than they had been in Destiny 9.0 or previous. The more your users search for titles, the more images will be cached, resulting in faster image display for all users in your district.

If you have additional questions, please contact Technical Support at 800.323.3397.

Thank you,

Follett Software Company


 * How TitlePeek Image Caching Works with Destiny 9.5 **

Destiny Library ManagerTM caches, or stores, cover images to disk in an effort to increase the speed and network efficiency of its operations. To preserve hard disk space on the server, Destiny has a default limit to the amount of data that will be cached. That limit is 500MB. Because of this effort to save disk space, some cached cover images may be deleted from the server. As new cover images are added to the folder structure, the oldest cover images will be deleted to keep the total disk usage under 500MB. If a user searched for a book where the cover image was deleted, the cover would not display until the second time this book was searched on and that cover image was added to the cover image cache.

To reduce the impact of this situation on the end users, the amount of hard disk space allocated to the caching of images for the Destiny application can be increased by performing the following steps:

It is recommended to periodically check the hard disk space available where Destiny is installed. Likewise, checking the properties of the {installation drive:\path}\FSC-Destiny\fsc\tmp\cache folder will show how much of the allocated space is being used. If needed, further adjustments can be made to the MAX_CACHE_IN_KB value based on need and available hard disk space. || || || ||
 * 1) Consider the available disk space on the drive where Destiny is installed. How much is available for Destiny caching? Can 1GB be allocated? (Note: To verify the installation location of Destiny, open the Windows Services control panel. Double-click on the Destiny Server listing. Note the "Path to executable" value.)
 * 2) Browse into the {installation drive:\path}\FSC-Destiny\fsc\bin folder. Open the config.properties file with NotePad.
 * 3) Add the following line to the bottom of the file: MAX_CACHE_IN_KB=1024000 (Note: Using 1024000 will allocate 1GB to the Destiny image cache. If needed, adjust the value according to the hard disk space available for your needs.)
 * 4) Save and close the config.properties file.
 * 5) At a time when the system is not in use, restart the Destiny Server service via the Windows Services control panel.

**Follett Software Company** ( CustomersFirst@fsc.follett.com ) 1391 Corporate Drive, McHenry, IL 60050 • 800-323-3397 **Unsubscribe** || ||
 * || This message was sent to schwartze@sau25.net by: