| Main -> Documentation -> Product Updates -> Open SiteSearch Suite Known Bug List (by Detailed Description) - Part I |
|
OCLC SiteSearch Suite Known Bug List (by Detailed Description) – Part I
Last Updated: November 10, 2000 This document includes detailed descriptions of the bugs (numbered BR001 to BR100) which have been reported in the Open SiteSearch Suite software. To report a bug in the Open SiteSearch Suite software, contact Product Support. Go to Part II: BR101 and higher BR100: Exporting Tables from mSQL Exists in Version(s): 4.1.1 Description: Exporting tables from mSQL fails and returns a java.lang.NoClassDefFoundError error message.
Fix: There
is no fix available, but as a workaround edit the msql file in the scripts
directory.
Add the following to the top of the file:
# What version of SiteSearch is installed Below the "do not edit" line, change the CLASSPATH to this:
CLASSPATH="$JAVAHOME/lib/classes.zip:$ROOTDIR/classes/lib/SS$SSVERSION.jar:
\
BR099: Numbering of Brief Result Set Records Exists in Version(s): 4.1.0 Description: This problem occurs when the default set size for displaying brief records is edited. In this case, the default set size was set to two. If the result set contained an even number of records, record numbering was correct. If the result set contained an odd number of records, so only one record was shown on the last screen, the last record was labeled record number "1" instead of the actual record number. See also BR091. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR098: Handling Missing Records Returned from a Z39.50 Server Exists in Version(s): 4.1.0, 4.1.1 Description: If a Z39.50 server sends missing records, the result set is incorrectly built and SiteSearch does not sort the result set correctly. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR097: Lost Search History Exists in Version(s): 4.1.0, 4.1.1 Description: When a patron uses the stop button from the browser, the command closes the connection to the Z39.50 server, which in turn forced the system to lose the user's search history. The user could no longer display records from any previous searches. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only. Version 4.1.1
Version 4.1.0
BR096: Incorrect System Error Thrown in Record Builder Exists in Version(s): 4.1.0 Description: If a user tries to update a record without proper update authorization, a system failure page is thrown in error. The code was corrected so that an authorization error message is thrown instead. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR095: Proximity Searches with Three or More Terms Do Not Return All Matching Records Exists in Version(s): 4.1.0 Description: If three or more terms are linked with a proximity operator to query a local database, records that should be retrieved are not returned in the result set. This problem has been reported when querying local databases only. Fix: A fix is not yet available. BR094: Assigning Proximity Operator as Default Operator Does Not Work Correctly Exists in Version(s): 4.1.0 Description: Assigning a proximity operator, 'with' or 'near,' as the default operator does not work correctly because a value of zero (0) is being passed with the operator. Fix: This problem will be fixed with the release of SiteSearch 4.1.1. A default value of 2 will automatically be passed when the default operator is set to a proximity operator. BR093: Runaway JaSSI Threads Exists in Version(s): 4.1.0 Description: When a connection fails to the ZBase, the user session is thrown into an endless loop as it continues to attempt to connect. The JaSSI was thrown into a spinning state. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR092: Stats Not Recorded Exists in Version(s): 4.1.0 Description: A user reported that stats weren't showing up when a user logged off. The z39close call expects a response. So when the response isn't sent, the JaSSI client doesn't receive the code for doing the cleanup. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR091: Set Size to "1" in Advanced Search Screen Causes Display Error Exists in Version(s): 4.1.0 Description: When "Set Size" is set to 1 in the advanced search, the record number will appear to be "1" regardless to which record is showing. Fix: . A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR090: Jumping to a New Record from a Full Record Shows Brief Display Instead of Full Record Display Exists in Version(s): 4.1.0 Description: When viewing records in full record display format, selecting a new record from the JumpBar should also display the new record in full format. Instead, the JumpBar displays records in brief format. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR089: Sorting Fails in Logical (Partitioned) Databases Exists in Version(s): 4.1.0 Description: Sorting a pre-merged partitioned database fails when ini/servers/ZBase.ini SupportsMergedReads=false. It was sorting within the individual databases but not merging into a totally sorted list accross all the partitions. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR088: Scanning of FirstSearch 5.0 Databases Fails in SiteSearch 4.0.2 Exists in Version(s): 4.0.2 Description: When FS5.0 was released there was an incompatibility in the 4.0.2 code base reading and parsing scan responses. Fix: Code updated to read the scan response correctly. This is a password protected site accessible to system administrators only.
BR087: Indexes with Punctuation Marks not Indexed Correctly in Database Builder Exists in Version(s): 4.1.0 Description: SiteSearch development corrected a bug found in Database Builder when using the phrase2( ) routine. The routine collapsed punctuation marks during indexing, resulting in incorrectly constructed indexes. This problem only occurs if the pippin -ztable is employed during the build. Fix: . A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR086: Compiling Apache 1.3.6 Exists in Version(s): 4.1.0 Description: A number of users have contacted SiteSearch concerning compiling Apache. The script file we originally provided did not work with SiteSearch 4.1.0 because of a bug in the getini.c file shipped with the software. Fix: . Users can now add modules to Apache 1.3.6 using the revised getini.c file and the corresponding script. This is a password protected site accessible to system administrators only.
BR085: Truncated Searches on Local Newton Databases Fail Exists in Version(s): 4.1.0 Description: Truncated searches return invalid results. This affects only searches on local databases and not remote Z39.50 databases. Fix: . A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR084: Database Building Phrase2() Indexing Handles Punctuation Incorrectly When Using the -ZTable Exists in Version(s): 4.1.0 Description: Trailing punctuation characters are being incorrectly stripped from local database records prior to indexing. This occurs only when using the phrase2() indexing routine in combination with the -ztable parameter. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR083: Sorting Features Do Not Perform Correctly in SiteSearch 4.1.0 Exists in Version(s): 4.1.0 Description: Two related sort problems were found in SiteSearch 4.1.0. (1)When the dataoffset and datalen parameters are both specified in the database configuration file, result sets are not sorted. (2)If a sort fails, subsequent sort requests return an error message that the result set cannot be located. Fix: . Fixes are available from the SiteSearch secure ftp server. . This is a password protected site accessible to system administrators only.
BR082: Rules-Based Formatting Does Not Allow StyleTable Entity Substitution Exists in Version(s): 4.1.0 Description: Formatting rules do not allow users to substitute Styletable entities into label fields for record display. Fix: Rule logic was edited so that the semicolon in an entity is no longer changed. This is a password protected site accessible to system administrators only.
BR081: For Environments that Support Patron Reauthorization, Error Message is Not Thrown Correctly Exists in Version(s): 4.1.0 Description: When a patron attempts to re-logon in a SiteSearch environment that supports reauthorization, an error message is not displayed if the logon fails. This occurs only when the patron has initially logged on with name authorization. The error message is displayed correctly if the user initially logged on with DNS or IP authorization. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR080: External Z39.50 Clients are Not Fully Interoperable with ZBase Server Exists in Version(s): 4.1.0 Description: Proprietary Z39.50 clients, including the Melvyl Z39.50 client, are unable to decode messages sent from a ZBase server. Specifically, they can not read the options sent with the init response and cannot read records in OPAC syntax. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR079: The Field Image File Repeats in Image Database Template Exists in Version(s): 4.1.0 Description: When editing a record in Record Builder, the name of the path to the image file is repeated as both a hotlink and as data in a text box. Fix: No fix available. As a workaround, delete the hotlink reference. BR078: Images Do Not Display in the Full Record Display for Record Builder Exists in Version(s): 4.1.0 Description: When viewing records from an image database, the hotlink to the image does not work from the full record display in Record Builder. This problem occurs only when using the ORG.oclc.mantis.hooks.URL hook to create the hotlink. The image can still be viewed in the WebZ interface. Fix: No fix available. BR077: New Records Added to a Record Builder Database Cannot be Searched on Alpha Platforms Exists in Version(s): 4.1.0 Description: New records added to a Record Builder database cannot be searched on Alpha platforms. The records are added to the database HEDR file, but cannot be located because the postings index files are not updated.
Fix: The databases
were re-built on an Alpha machine to correct for the byteorder on this operating
system. Download the revised databases from the Open SiteSearch secure ftp
server. Untar and decompress the files and move them to the appropriate
area in your <WebZ_root>/dbbuilder/dbs directory. For Alpha
systems only.
This is a password protected site accessible to system administrators
only.
BR076: DRA Holdings Do Not Display Correctly with Merge and DeDup Exists in Version(s): 4.1.0 Description: In a cross-database search, DRA holdings information does not display when the merge and de-duplication features are active. The holdings information displays only if a DRA database record is listed first. If a DRA database record is not listed first, the holdings information is not shown.
Fix: Some records have holdings information in a separate database. With de-duplication, the holdings information is not being attached to the records. The fix sends a separate request to retrieve the holdings information for each duplicate record. To apply this fix, logon to the Open SiteSearch secure ftp server. Follow the instructions from the README file. This is a password protected site accessible to system administrators only.
BR075: Customized Topics Do Not Display in 4.1.0 Exists in Version(s):4.1.0 Description: All topics defined in the ObiTopics ini file are displayed in the dblist screen, even when limited topics are specified in the style ini file. Fix: A fix is available from the SiteSearch secure ftp server. This is a password protected site accessible to system administrators only.
BR074:Open Browse Function Displays Incorrectly in Record Builder Exists in Version(s): 4.1.0 Description:
Under certain conditions, the screen for the "Open Browse" function in
the Record Builder application displays conflicting information. The message
"To Browse for a record in the Fix: No fix available. BR073: DNS Authorization Fails Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2, 4.1.0 Description: Users cannot authorize patron access to databases via Domain Name System (DNS) address.
Fix: The code
for the Authorize verb was corrected to allow DNS authorization.
To apply this fix, logon to the SiteSearch secure ftp server. Follow
the instructions from the README file.
This is a password protected site accessible to system administrators
only.
BR072: Truncated and Proximity Searches on Newton Databases Throw Exceptions Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: Null Pointer and Array Out Of Bounds exceptions are thrown for truncated and proximity searches of Newton databases. Fix: 4.1 BR071: Searches Using Multiple Restrictors on an Advanced Search Page are Parsed Incorrectly Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: A search constructed on the advanced search screen returns an error message if more than one restrictor is used in the query. Fix: 4.1. Parentheses are now placed correctly in the query term string. BR070: Searches Using Multiple Restrictors are Parsed Incorrectly when Using 'NOT' Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: For searches using more than one restrictor: if the second restrictor is connected with the boolean 'not' operator, the query is parsed with the boolean 'and' operator instead, resulting in a wrong search. Fix: 4.1 BR069: Z39.50 Connections to ZBroker Fail Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: After a patron disconnects from ZBroker and ends a Z39.50 session, the remote server name is lost, which prevents other patrons from connecting to ZBroker and starting a new Z39.50 session. Fix: 4.1 BR068: Associated Database Topics Do Not Display when a Patron is ReAuthorized Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: If patron reauthorization (during an active WebZ session) is required to access additional databases, the topics associated with the new databases are not displayed. Fix: 4.1 BR067: HideInMenus Option Ignored After Patron ReAuthorization Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: If patron reauthorization is required to access additional databases, WebZ displays all authorized databases in the database list and ignores whether any databases should be hidden. Fix: 4.1 BR066: Piping Unix Commands to SSAdmin Throws SSAdmin into a Loop Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: Piping Unix commands to ssadmin using the Unix echo command throws ssadmin into an endless loop. Fix: 4.1 BR065: Hotlink Queries from a Scan Term Fail if the Scan Term Contains Special Characters Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: WebZ filters the special characters in a hotlink query from a scan term, resulting in failed searches. Fix: 4.1 BR064: Results of Topic Search Continue to Display After Searching a Single Database Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: An Open SiteSearch user can control the order in which databases are listed in a topic query by changing variables in the StyleTable. The unintended consequence of choosing this option is that the results of a topic search continue to display after a patron switches to searching a single database. Fix: 4.1. Version 4.1 merges result sets and no longer groups results by database. BR063: Error Messages Do Not Display Correctly in WebZ Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: If a search fails (for example, because of too many truncated terms), WebZ returns zero hits instead of an error message explaining why the search failed, which misleads the patron. Fix: 4.1 Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: The ztablefile parameter in Database Builder allows users to replace or delete characters in a data record only for keyword indexes. The parameter does not work for phrase indexes. Fix: 4.1 BR061: WebZ Incorrectly Handles Structure Attributes Exists in Version(s): 4.0.2 Description: Queries with structure attributes greater than 100 are incorrectly parsed as keywords instead of phrases. Fix: 4.1 BR060: WebZ Incorrectly Handles Structure Attributes in a Scan Request Exists in Version(s): 4.0.2 Description: If the structure attribute of an index is set to values 3, 4, 5, or 6, WebZ incorrectly sends a value of 2 in a scan request. Fix: 4.1
Exists in Version(s): 4.0.2 Description: When the byteorder for a local newton database is defined as low-to-high in the database description file (.dsc), searches against the restrictor index are failing. Fix: Complete the instructions below to download the fix for this bug.
BR058: The WebZ Formatting Classes Do Not Parse/Display MARC Holdings Information Correctly Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: The WebZ formatting classes do not parse all of the MARC holdings information retrieved from remote Z39.50 servers correctly and does not display the holdings information to the patron in the appropriate order in the WebZ Out of the Box Interface (OBI). Fix: Complete the instructions below to download the updated addHoldings( ) method MARC catalog formatting class. Tim Prettyman, University of Michigan, contributed to the parts of the logic of this code.
BR057: Searches Using Date Ranges Are Not Configured For Newton Databases in the Out of the Box Interface (OBI) Exists in Version(s): 4.0.2 Description: In the 4.0.2 release, multi-node date range searches are supported in WebZ. However, you must add a new variable to the database configuration file for the JaSSI server to recognize this functionality for a Newton database (i.e., a FirstSearch or local database). If this variable is not included in the database configuration file, patrons will be unable to perform searches using date ranges in the OBI. Refer to the following two bugs for additional bug information on single-node and multi-node date range searches and information about required search syntax:
Fix: FirstSearch 5.0, scheduled for release in August 1999, will include the enhancements from Open SiteSearch 4.0.2 to allow for multi-node date range searches. Until FirstSearch 5.0 is available, add the following to the index definition for year in the Newton database configuration file: useRelationAttribute = true This fix relates directly to local and FirstSearch databases because most Z39.50 servers will NOT support the 'within' Z39.50 syntax for multi-node date range searches and will return an error message. The following is an example of the localERIC.ini with the correct database year index definition: [Year] Finally, complete the instructions below to apply the code fix that works with this variable definition:
BR056: FormatBerUtil Does Not Recognize Subsequent Fields in a List When the First Field is Not Found Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: WebZ does not display subsequent fields in a list when the first field is not found in the record display even when the information is returned with the record data during a search. For example, if you specify both 245 and 246 fields (title and alternative title) in the formatting classes, if 245 is not found, WebZ would not recognize 246. In the 4.0.2 release, FormatBerUtil was fixed to correctly display subsequent fields in the WebZ Out-of-the-Box Interface (OBI). Fix: 4.0.2 BR055: The Topic Name and Database List Are Not Updated Correctly When a Patron Customizes the Topic from the Search Screens Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: If a patron selects "Customize Topic" from the search screen and changes the topic name and selected databases, the changes are not updated on the search screen after the patron is done customizing the topic. Instead, the patron has to return to the database selection screen (dblist.html) and select the new topic name from the list to see the changes reflected on the search screen. Fix: This bug was fixed by altering the code to make sure the topic is set correctly before returning to the search screen. Complete the instructions below to download the bug fix.
BR054: The WebZ Extension 4.0.2 Perl Installer Displays an "NT Not Found" Message Exists in Version(s): 4.0.2 Description: The UNIX 4.0.2 Perl installation program displays an "NT Not Found" message when users try to install the Apache WebZ extension. Please ignore this message; this is an error in the installation script that does not affect the Apache WebZ extension installation. The Apache Web server and extension will be successfully installed. Fix: No fix necessary. This message will be removed from the Perl installation scripts for the Open SiteSearch 4.1.0 release. BR053: WebZ Does Not Accurately Report an Error That Occurs When Performing a Range Search on a Local Newton Database Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: When a patron attempts to perform a range search on a local Newton database index that does not support range searching, WebZ displays "0 hits returned" to the patron. The ZBase server should recognize this search as an error if range searches are not supported. However, the ZBase server is not returning an error message to the patron, implying that the database was searched and no records matching the requirements were found. When this bug occurs, the following error message is reported in the ZBase user log: got Diagnostic1 code= 108 msg = range search improperly specified Official msg= Malformed query from search()
Fix: No fix available. BR052: FirstSearch 4.0 Databases Do Not Support Multi-Node Date Range Searching Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1, 4.0.2 Description: FirstSearch 4.0 databases do not support the new 'within' Z39.50 relation attribute needed to perform searches with multi-node date ranging functionality as implemented in Open SiteSearch 4.0.2. Refer to BR050, WebZ Does Not Fully Support Date Ranges, for a description of the multi-node functionality. Fix: FirstSearch 5.0, scheduled for release in August 1999, will include the enhancements from Open SiteSearch 4.0.2 to allow for multi-node date range searches. Until FirstSearch 5.0 is available, add the following to the index definition for year in the Newton database configuration file: useRelationAttribute = true This fix relates directly to local and FirstSearch databases because most Z39.50 servers will NOT support the 'within' Z39.50 syntax for multi-node date range searches and will return an error message. The following is an example of the localERIC.ini with the correct database year index definition: [Year] Finally, complete the instructions below to apply the code fix that works with this variable definition:
BR051: ZBase Is Looping/Spinning During a Local Database Search on Windows NT Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: When performing a local database search on a WebZ system which is hosted on Windows NT, ZBase can not complete the search request and appears to be unable to end a code loop. The Java Development Kit's (JDK) Just-In-Time (JIT) Compiler is the cause of this problem. With the 4.0.2 release, a -nojit flag is included in the ssadmin.bat and ssmgr.bat files to automatically turn off the JIT functionality in the JDK. Fix: 4.0.2 BR050: WebZ Only Supports Single-Node Searching on Date Ranges Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: In the 4.0.0, 4.0.0a, and 4.0.1 releases, WebZ supports single-node searching for date ranges. The WebZ system takes the date range entered by the patron and marks it as a single term, similar to a phrase search. The system then passes this single-node to the Newton search engine to look for the range, or phrase, within the database index. In the 4.0.2 release, WebZ supports multi-node date ranging, which treats the range as multiple terms by using the 'within' Z39.50 relation attribute. The terms are passed to the Newton search engine to perform the search. With multi-node searching, WebZ supports the following search syntax for date ranges: Inclusive Example 1995-1998 -1998 Exclusive Examples >1990 The following syntax is NOT supported: 1995>1999 Important Note: To search a database that only supports single-node date ranges, you must apply the bug fix described in BR052, FirstSearch 4.0 Databases Do Not Support Multi-Node Date Range Searching, for information about FirstSearch 4.0 or any other databases which only support single-node searching. Minimum and maximum ranges can be set in each database configuration file. If you wish to use zclient to search ranges, use the following syntax: '"1986-1987"/u=30; s=5;' Important Note: Refer to BR057, Searches Using Date Ranges Are Not Configured For Newton Databases in the Out of the Box Interface (OBI), for information about configuring date ranges for Newton databases in 4.0.2. Fix: 4.0.2 BR049: WebZ Does Not Fully Support Truncation Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: WebZ does not fully support truncation. In the 4.0.2 release, WebZ supports truncation in the following ways: a) Right-hand Truncation (truncation type = 1) Right-hand truncation will be supported with 4.0.2. This type of truncation uses the asterisks ('*') wildcard to denote right-hand truncation searching. The patron can identify some characters of a search term and use the asterisks to tell the system to identify indexed terms which begin with this character stem. Refer the example shown below to see how the system will interpret the asterisks wildcard: wom* Returns woman, womanly, womb, wombat, women, etc. b) Single Character Mask (truncation type = 101) The 4.0.2 software supports single character masking. The system finds records by replacing the pound ('#') wildcard with a single character to return records containing terms that meet the criteria set by the search syntax. Refer to the example below: wom#n Returns woman, women c) Variable character mask (truncation = 104) The 4.0.2 software supports variable character masking. The system find records by replacing the question mark('?') wildcard with the number of characters specified by a positive integer, denoted by n. The system will return records containing terms that meet the criteria set by the search syntax. If n is not specified, the question mark is treated as ?n, where n (beginning at 0) is the system limit of the target. Refer to the example below: wo?n Returns wobegon, woburn, wogoman, woman, women, workman In the example shown above, the system will search for all of these keywords because a value for n (a positive integer) was not defined. To only retrieve records containing both "woman" and "women", you would enter the following search syntax: 'wo?2n'. The software supports the ability to combine mask operators in a single term (i.e., 'in##net?23' and '?11tion') To perform truncation searches using WebZ, your database MUST support Z39.50 truncation attributes 1, 101, and/or 104. Fix: 4.0.2 BR048: Microsoft IIS 4.0 and Microsoft IE 4.0 Do Not Work Together Correctly/Additional JaSSIs are Randomly Started in the WebZ System Exists in Version(s): 4.0.1 Description: Microsoft Internet Explorer (IE) 4.0 sends the Microsoft Internet Information Server (IIS) 4.0 an identical request to the ISAPI filter which causes two JaSSIs to start with the same request. In the 4.0.2 release, the WebZ Extension IIS DLL was corrected to avoid the problem by marking the request as having been processed when returning to the JaSSI object after the JaSSI process has completed the request. Fix: 4.0.2 BR047: Surrogate Diagnostic Records Returned in a Present Response Are Thrown Out/Navigation for a Result Set Is Incorrect Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: When Surrogate Diagnostic records are returned in a present response, they are thrown out of the Z39present to the client. This causes all of the numbers associated with the record retrieval to be off, rendering the navigation useless for the search results. In the 4.0.2 release, support was added to the software to retain the surrogate diagnostics in the present response. This support also maintains valid navigation in the search results. Fix: System support for this fix is in 4.0.2.The formatting routines have not been modified to do this because of OCLC's committment to not making frequent changes to these classes. To correct this problem in your formatting classes, you can detect the record in error in the JaSSI by checking that the highest level fldid of each record is formatted = 1. For example, in each formatting class there is a loop to format each record: for (j=0; j< records.size(); j++) {
This can be altered to check if the record was in error: DataDir d; BR046: WebZ Does Not Process Partial Search Results for Display Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: When WebZ performs a search on a remote server (i.e., a Melvyl server), partial results are sometimes returned from the server on large searches. WebZ deems the search in error when the partial results could be displayed. In the 4.0.2 release, DbRemoteZ and QUERY were changed to allow the display of records from a search that indicates partial results are available. Fix: 4.0.2 BR045: zclient Searches Fail Unexpectedly Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: The zclient utility sends the 'b' element set name on every search request, even when no records were expected on the response, causing searches to unexpectedly fail. In the 4.0.2 release, the zclient code was fixed to send the element set name only if it is needed. Fix: 4.0.2 BR044: WebZ Incorrectly Displays Images and Thumbnails When the Search Results Are Sorted Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: WebZ incorrectly displays images and thumbnails after a result set has been sorted. For efficiency purposes, WebZ caches images for display so that the software does not have to re-FETCH the image every time it was displayed. When the result set is sorted, WebZ displays the incorrect cached image from the original result set. In the 4.0.2 release, the software has been changed so that WebZ will re-FETCH the images when the result set is sorted. Fix: 4.0.2 BR043: WebZ Does Not Retrieve the AlternativeTerm in a Scan Response Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: WebZ is not retrieving the AlternativeTerm in a scan response from the Z39.50 scan because it does not recognize the AlternativeTerm in the scan response correctly. In the 4.0.2 release, the software was fixed to recognize the AlternativeTerm in a scan response correctly. Fix: 4.0.2 BR042: WebZ Does Not Display All of the Results for a III Database Search Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: III does not encode the records correctly in the Z39.50 present response structure according to the standard, and the WebZ record decoder was unable to read the records correctly. In the 4.0.2 release, a workaround was put into place to detect the present response encoding error and decode the records for display. Fix: 4.0.2 BR041: WebZ Does Not Create the List of Database Anchors Correctly Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: The line separator for the list of database anchors which are created by ORG.oclc.obi.util.Databases was getting added even when the last database was reached. This line separator is not needed. In the 4.0.2 release, the ORG.oclc.obi.util.Databases package was corrected to add the separator correctly when needed. Fix: 4.0.2 BR040: WebZ Does Not Retrieve All of the Records During a Search Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: When the requested number of records was not retrieved from a search and the hit count is greater than the number of records retrieved (BUT less than the number of records requested), WebZ does not fetch the remaining records. The 4.0.2 release fixes this bug. Fix: 4.0.2 BR039: Indefinite Length Reads from a Remote Z39.50 Server Fail Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: Indefinite length reads from a remote Z39.50 server fail because of a problem allocating the array to read the input. The 4.0.2 release fixes this problem. Fix: 4.0.2 BR038: The WebZ Bookmark Full Display Does Not Wrap the Lines of Text Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: The bookmark full display presents text in one line without breaking the content. Patrons must use the horizontal scroll to view the complete record. In the 4.0.2 release, the BookMarkFull formats are enhanced to break at 70 characters per line to provide for better readability and patron ease-of-use. Fix: 4.0.2 BR037: HTML Characters are Displayed in the E-mail and Full Bookmark Display Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: HTML characters (e.g., < and >) are displayed in the e-mail and full bookmark display of records. In the 4.0.2 release, the formatting classes and utilities were modified to disable the translation of characters into HTML so that e-mailed and bookmarked records do not show the HTML. Fix: 4.0.2 BR036: SUTRS Full Text Record Display Contains Incorrect Data Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: The SUTRS full text record display has four characters of garbage displaying at the start of each record. WebZ has a problem pulling the full text data from the Z39.50 response record. It is retrieving four extra characters that should not be in the record. In the 4.0.2 release, the client decoding the record was fixed. Fix: 4.0.2 BR035: Access Component Incorrectly Processes IP Address Verification Using Subnets Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: An authos record whose autho field is 'ip:141.211.73.57', which gets selected for the client with that address, will also get selected for other clients on the 141.211.73.* subnet. For example, the client at 141.211.73.54 also uses the ip:141.211.73.57 authos record when it should not. In other words, the problem occurred when the ONLY authorization in the access database for the subnet X.X.X is X.X.X.176, and the incoming user authorization is X.X.X.175. This user is authorized with the X.X.X.176 autho because the subnet values match. In the 4.0.2 release, the Access component correctly validates the retrieved entry from the access database against the full IP address. Fix: 4.0.2 BR034: WebZ Cannot OR More Than Two Terms Together When Searching a Local or FirstSearch Database Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: If you OR more than two terms together when searching a Newton database (a local or FirstSearch database), incorrect results are returned. In the 4.0.2 release, the software was fixed to return the correct results. Fix: 4.0.2 BR033: WebZ Cannot Link Correctly to a Web Page Outside of the OBI Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: WebZ is unable to return the correct page when an absolute URL (e.g., http://www.someplace.com) is specified as a next page. In the 4.0.2 release, WebZ was fixed to put the correct HTTP header information on an absolute URL so that the HTTP server retrieves the correct page. Fix: 4.0.2 BR032: The Refine Screen and/or the results.html Page Are Not Displaying Correctly Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: When the refine screen or results.html page is embedded as the next page in the frame HTML, the /WebZ/ was missing so the results of how the next page is displayed are unpredictable. In the 4.0.2 release, the /WebZ/ was added to the anchor substituted into the page. Fix: 4.0.2 BR031: Authorized Patrons Who Login to the WebZ Interface with a New Autho are Automatically Authorized Exists in Version(s): 4.0.0, 4.0.0a Description: If a patron is currently in an authorized session and selects to login with another autho/password using the login anywhere option, the new autho information is not being checked with the Access component and the patron is automatically authorized to re-enter the system. The problem occurs because WebZ does not query the Access component a second time during a user session. Fix: 4.0.1 BR030: WebZ Does Not Display Record Results When the Database Record Syntax is Set to BER Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: For piggy-backed sorts on a QUERY command, when the requesting record syntax is BER, the correct record syntax was not set, and the records could not be presented. In the 4.0.2 release, the QUERY verb was fixed to set the record syntax correctly. Fix: 4.0.2 BR029: Proximity Searches Fail in Local and FirstSearch Databases Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: Proximity searches fail when a patron searches a Newton database (a local or FirstSearch database). In the 4.0.2 release, the software was fixed to correctly read the proximity information from the Newton database. The calculation for getting the length of the proximity data was in error and has been corrected. Refer to BR018 to read about a related bug fix. Fix: 4.0.2 BR028: WebZ Does Not Retrieve All of the BER Records Requested on a Search Response Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: WebZ does not retrieve all the of BER records requested from a remote Z39.50 search if the length of the records exactly matches the allocated buffer size for temporarily storing records in WebZ, which is specified in the Z39search and BerString classes. WebZ displays a partial results set in this instance. Fix: 4.0.2 The following bug fix updates two classes to allow the WebZ system to retrieve all of the BER records requested from a remote Z39.50 server despite the length of the records. BR027: Incorrect Record Data Is Displayed When Refine or Sort Is Selected from the Full Text Screen Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: WebZ displays incorrect record data when a patron selects the refine or sort links from a record's full text screen. Fix: 4.0.2 BR026: WebZ Does Not Return Results from Newton Database Searches When Stopwords are Included in the Search Term Exists in Version(s): 4.0.0, 4.0.0a Description: When patrons search Newton databases (e.g., local database built with Open SiteSearch Database Builder or FirstSearch databases) with a term which includes stopwords, WebZ doesn't recognize the stopwords defined in the database description and returns 0 results. For example, a search for "cat in the hat" would return 0 results because WebZ processes the entire string, instead of ignoring the stopwords "in" and "the." Fix: 4.0.1 BR025: Patrons are Unable to Select the Number of Records for Display on the Advanced Search Screen Exists in Version(s): 4.0.0, 4.0.0a Description: WebZ does not correctly process the "Set Size" value defined by the patron on the advanced search screen. Instead, WebZ always displays a results set of ten records at a time, ignoring any values defined by the patron from the advanced search screen. Fix: The fix for this bug is provided with the Open SiteSearch 4.0.1 release. With this fix, the query command specifies that numrecs=0 (where numrecs is the number of records displayed in a results set at a time). Ten records are retrieved by default on a query as defined in the initialize.java entity &defaultnumrecs;. This entity is used in HTML pages as numrecs=&defaultnumrecs;. The 4.0.1 release also uses the numrecs widget to hot link queries to ensure that the correct numrecs values are set in the WebZ interface. This fix requires changes to the following HTML files and Java classes: SS4_0_1.jar <WebZ_root>/htdocs/html/ advancedsearch.html ORG.oclc.fmts.WebZFormatter BR024: Patrons are Authorized by Access Component After Entering Two Bad Authorizations in a Row Exists in Version(s): 4.0.0, 4.0.0a Description: The WebZ Access component successfully authorizes patrons into the default interface if they enter the same bad authorization in two times in a row, including a blank authorization. Fix: 4.0.1 BR023: Jumpbar is Linked Incorrectly Exists in Version(s): 4.0.0, 4.0.0a Description: In several cases, the jumpbar links visually run together instead of appearing as separate page references, or two linked page references point to the same anchor instead of two separate anchors. Fix: 4.0.1 BR022: Remote Z39.50 Server Configuration InitWait Timeout Value is Not Enforced Unless Specifically Set Exists in Version(s): 4.0.0a Description: The default value for the InitWaitTimeout variable in the database server configuration files is set to 0, unless otherwise specified in the remote server configuration file. If the WebZ system is unable to initialize with a remote Z39.50 server and the InitWaitTimeout is not defined in the configuration file, WebZ will hang indefinitely. Fix: 4.0.1 BR021: WebZ Does Not Set the Correct Search Page When Browse is Not Supported Exists in Version(s): 4.0.0, 4.0.0a Description: If a database does not support browse functionality, WebZ would not set the current search page correctly. WebZ returns patrons to the generic page for browse instead of informing the patron that browse is not supported for the specified database. Fix: 4.0.1 BR020: The Access Component Does Not Authorize Patrons Correctly/Access Component Log File Includes the "java.sql.SQLException: :Too many fields in condition" Error Message Exists in Version(s): 4.0.0, 4.0.0a Description: According to the way that the Open SiteSearch 4.0.0 software implements Hughes Technologies Pty. Ltd.'s Mini Structured Query Language (mSQL), the SiteSearch Access component limits system administrators to 75 databases and resources associated with a single user (e.g., guest, staff, public, etc.) in the mSQL authorization database. If the mSQL database contains more than 75 databases and/or resource entries for a user, the Access component will authorize a patron as specified in the Access.ini configuration file, but will throw an SQL exception while retrieving user information from the database. The following error message will appear in the Access Component log file after the exception is thrown: "java.sql.SQLException: Too many fields in condition." Fix: 4.0.1 BR019: Embedded Wildcarding ('?') Does Not Work Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: With Open SiteSearch 4.0.0, patrons can only use the question mark ('?') as a wildcard to specify truncation for a search. The software supports the Z39.50 truncation attribute values of 1, 2, and 101, but it does not support the attribute value of 102. Thus, this wildcard is only used for truncation, and all of the characters included after the '?' in the search syntax will be ignored by the WebZ system. Refer to the following table for an example of how Open SiteSearch 3.1 and 4.0.0 differ in the processing of Z39.50 truncation.
Notice in the second syntax example above that 4.0.0 ignores the 'y' character after the '?', but 3.1 used the character to identify terms that began with 'osteo' and ended with 'y'. The '?' cannot be used for pattern matching (Z39.50 truncation attribute 102) in Open SiteSearch 4.0.0. Fix: 4.0.2 Refer to BR049 for additional information about truncation supported in the 4.0.2 release. BR018: Proximity Searching Using the Near and With Operators Does Not Return the Expected Results Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: Open SiteSearch 4.0.0 incorrectly processes search requests for local or FirstSearch databases using the near ('n') and with ('w') proximity operators, potentially retrieving an inaccurate results set. Open SiteSearch 3.1 used the near and with operators to identify terms in a search which appear adjacent to one another in a record. The 'n' specified terms which could appear in any order, and the 'w' identified terms which had to appear in the exact order specified. Patrons could also include a number from 1 to 25 after the proximity operator to specify the maximum number of words that appear in a record between the two search terms. In Open SiteSearch 4.0.0, WebZ handles the near and with operators backwards. The system processes a search using the near operator as if it was using the with operator and vice versa. For example, a patron executes the following search:
According to the definition above, the SiteSearch 3.1 system would process the request as "find a record that contains the terms booklet and reston with no more than 5 words in-between the terms." SiteSearch 3.1 would not enforce an order between these two terms. However, SiteSearch 4.0.0 processes this request as "find a record that contains the term booklet followed by the term reston within 5 words." Open SiteSearch 4.0.0 enforces order when using the near operator, not the with operator. Fix: 4.0.2 BR017: Plural Searches Do Not Work with the '+' Operator Exists in Version(s):
4.0.0, 4.0.0a, 4.0.1 In the 4.0.2 release, ZqueryHandler was changed to leave the '+' in the incoming search terms. Fix: 4.0.2 BR016: WebZ is Unable to Return SUTRS Records/WebZ Returns SUTRS Records Containing Incorrect Data Exists in Version(s): 4.0.0, 4.0.0a Description: Z39.50 retrieval of records in the SUTRS record syntax fails because the encoding of the records returned from ZBase is incorrect. The returned record appears as garbage. Fix: 4.0.1 BR015: The Search Screen Tabbar Labels Are Not Correctly Displayed/Linked After Editing a Database Configuration File or a Database Group Definition File Exists in Version(s): 4.0.0, 4.0.0a Description: The search screen tabbar labels contain invalid links if the database configuration and database group definition files define the tabbar specification with less than 3 indexes. By default, the tabbar variable in the [IndexLists] section of database configuration and database group definition files includes the Title, Author, and Keyword indexes. If less than 3 indexes appear in the tabbar list in this database definition, the search option tabbars do not link to the appropriate search screens in the WebZ interface. For example, if you remove Title from the [IndexLists] section in a database configuration file, the following tabbar buttons will remain on all search screens: Author, Keywords, Advanced, and Browse. However, these remaining search screen tabbars will no longer link to the correct search screen. Patrons would have to select the Browse tabbar to link to the Advanced search screen (advancedsearch.html). Fix: 4.0.1 BR014: Access Component Utilities (msqlconvert, msqlexport, msqlimport) Return Error Messages When Executed Exists in Version(s): 4.0.0a Description: The Access component utilities (msqlconvert, msqlexport, msqlimport) can not run in the 4.0.0a release because the CLASSPATH is incorrectly specified for each utility script. Fix: 4.0.1 BR013: Access Component Does Not Work Correctly on DIGITAL UNIX Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: The Java Virtual Machine for JDK 1.1.5 on DIGITAL UNIX is abending the AccessServer process. The JVM abends in thread management and the server core dumps. Fix: Upgrade JDK 1.1.5 to 1.1.6 on DIGITAL UNIX systems. JDK 1.1.6 resolves the thread management problems. BR012: The Netscape Server Does Not Recognize the WebZ Extension/ The Netscape Server Can Not Access the WebZ System Exists in Version(s): 4.0.0a Description: The Netscape WebZ Extension contains an error which prevents the extension from working with the Netscape server. You will not be able to access the WebZ system through your Netscape server using the WebZ Extension shipped with SiteSearch 4.0.0a. Fix: 4.0.1 BR011: Fully Qualified IP Addresses are Not Authorized Correctly Exists in Version(s): 4.0.0a Description: If you store fully qualified IP addresses in your mSQL database, users may not be authorized correctly by the Access component. The Access component can only authorize correctly based on the first three sets of numbers included in a standard IP address. For example, the Access component could authorize a user based on "123.456.78.*" but could not authorize based on "123.456.78.99". The Access component can not read the "99" portion of the IP address and compare it to other similar address in the database. Thus, "123.456.78.99" and "123.456.78.90" would look exactly the same to the Access component, and you would receive an "Unable to Authorize" message from WebZ. Fix: 4.0.1 BR010: "No Title Provided" Appears in MARC Full Record Even If Title Exists Exists in Version(s): 4.0.0a Description: The fieldsExist() method in FormatBerUtil.java does not detect occurrences of input fields correctly. Many full records will then display the "No Title Provided" text in the title when you know there is a title being returned from a remote database. Fix: 4.0.1 BR009: Database Images Do Not Display/ Installation Error Message: Unable to Move sscgi Directory Exists in Version(s): 4.0.0a (full version only, Perl installation only) Description: Two symptoms identify this bug. 1. After performing a search on an image database, the full record results screen shows a broken image. 2. You will receive an installation error reporting that the installer was unable to move the sscgi directory. Fix: 4.0.1 BR008: Right-hand Truncated Phrase Searching Does Not Work Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: Right-hand truncated phrase searching does not work with the WebZ system. Fix: 4.0.2 BR007: User Authorization Occurs Even If Set to FALSE Exists in Version(s): 4.0.0, 4.0.0a Description: If you have built an mSQL database and have started the mSQL server and the WebZ system (including the Access component), the WebZ system will authorize users regardless of the settings defined in the Access.ini configuration file. Fix: Do not start the WebZ Access component unless you want to provide user authorization. BR006: Corrupt mSQL Database on HP-UX Platform Exists in Version(s): 4.0.0 Description: The HP-UX installation procedures can corrupt the mSQL sample database for the Access component. Fix: Re-build the mSQL sample database after installation as you configure the Access component to work with WebZ system. Refer to Configuring the Access Component for Unix for instructions about re-building an mSQL database. BR005: HTML Frames Occasionally Disappear in Internet Explorer 3.x Exists in Version(s): 4.0.0 Description: Frames disappear sporadically using Microsoft browser Internet Explorer 3.x. Fix: 4.0.0a patch BR004: FirstSearch Unable to Process Cross Database Searches Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: FirstSearch is unable to handle cross database results. Fix: Report each FirstSearch authorization (not passwords) to SiteSearch support at Authorizations will be re-routed by FirstSearch to a server that has a fix for this problem. BR003: GEAC MARC Records Contain Empty Fields Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: In some GEAC records, MARC tags exist with no data. These fields will be displayed without data to assist in locating "corrupt" records. Fix: No fix available. BR002: MultiLIS Unable to Perform Boolean Author Keyword Searches Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: MultiLIS author keyword searches work, but boolean author keyword searches do not work (e.g., au:beethovan and au:ludwig). Fix: No fix available. BR001: Sirsi Rejects Long Author Link Searches Exists in Version(s): 4.0.0, 4.0.0a, 4.0.1 Description: Sirsi author link searches are rejected if they are too long. Fix: No fix available. See Also OCLC
SiteSearch Suite Known Bug List (by Detailed Description) – Part
II |
|