- Article Type: General
- Product: Voyager
- Product Version: 7.0.4
Bug Report Form for Issue 16384-7137
Release(s): reported in 7.0.4; replicated in: 7.1.0
Server Platform(s) affected: Solaris/all
PC O/S (if this is PC specific): n/a
Browser type & version (if WebVoyage): All supported
Loss of functionality from (previous version, if applicable): Classic
Expected Results: In Classic, you could specify the configs (including search types) you wanted to have available for a specific database
Actual Results: In the tomcat interface, while you can specify a particular record display for a specific database, you cannot dictate the specific search types available for that database.
Workflow Implications: Searches that the site wishes to have available for certain dbs but not for others will display in all dbs.
For tomcat WebVoyage, go to /m1/voyager/yyydb/tomcat/vwebv/context/vwebv/ui/en_US/webvoyage.properties
You’ll see that here, for each database definition in the Connections section, you can specify the config properties file name that will control how record details for this db are displayed. However, the searches that you specify in webvoyage.properties will apply to *all* dbs you’ve configured in that skin.
For classic WebVoyage, go to /m1/voyager/yyydb/etc/webvoyage. Here you’ll see the connect.ini, where you specify your database definitions. Using the Locations stanzas (the stanza name will correspond to the db code in question) of the connect.ini, you can specify the config directories that should be applied to each database (Z3950, vcit, zcit, local). In each config directory is a separate search.ini where you can configure the searches you wish to have appear for each database. By using these individual search.inis, you can configure not only the record display for remote databases, but which searches display when searching those dbs.
Other information: You can effectively accomplish the same thing by creating a separate skin for a group of dbs that you wish to have specific search types available for; however, you then have to give users a way to easily access the new skin.
- Article last edited: 10/8/2013