| Main -> Documentation -> Product Updates -> Open SiteSearch Known Bug List (by Detailed Description) - Part III |
|
OCLC
SiteSearch Known Bug List (by Detailed Description) – Part III
Last Updated: October 31, 2002 This document includes detailed descriptions of the bugs (numbered BR151 and higher) which have been reported in the Open SiteSearch software. To report a bug in the Open SiteSearch software, contact Product Support.
Go
to Part II: BR150 – BR101 BR182: SSDOT uses a lot of memory to run Exists in Version(s): 4.2.0, 4.2.0a Description: Multiple changes made to the SSDOT utility program so that it runs with a smaller memory footprint. Fix: Created a single StringResolver class that is shared by all classes. This fix is available in SiteSearch 4.2.1. BR181: Apache Security Alert for Apache 1.3.23 Exists in Version(s): 4.2.0, 4.2.0a Description: Apache announced a possible crippling denial of service vulnerability in Apache 1.3.23 and below. This is an upgrade to the current Apache version. Fix: Added a new Apache 1.3.26 build. This fix is available in SiteSearch 4.2.1. This is a password protected site accessible to system administrators only.
BR180: Browse on URL index for terms starting with "http://" returns unexpected results Exists in Version(s): 4.2.0, 4.2.0a Description: On cross-database searches, the query term was being re-normalized in the browse method. Instead of using the normal String.trim() method to trim Strings in a customized DontNormalize class, the BaseTermNormalizer.trim method should be used. Fix: Changed a parameter in the doQParse method call to nonpolish from polish. This fix is available in SiteSearch 4.2.1. This is a password protected site accessible to system administrators only.
BR179: Pears incorrectly mapped MARC character Ayn to Unicode character Exists in Version(s): 4.2.0, 4.2.0a Description: Bibliographic records being converted using Pears incorrectly mapped the MARC character Ayn (0xB0) to the Unicode character \u02bf. Fix: Map MARC character Ayn (0xB0) to Unicode (\u02bb). This fix is available in SiteSearch 4.2.1. This is a password protected site accessible to system administrators only.
BR178: Z39.50 Errors of 125 or 108 when using zclient to Access an EBSCO Database Exists in Version(s): 4.2.0, 4.2.0a Description: This problem has to do with the the piggy-back present mechanism. When you send a search, the result set will either be large, medium or small. You define what you mean by large and small. Large is defined by largeSetLowerBound. If the postings count is greater than or equal to largeSetLowerBound, then the set is large and no records should be returned. If the postings count is less than or equal to smallSetUpperBound, then the set is small and all the records should be returned. If the set is neither large nor small, then the set is medium and mediumSetPresentNumber should be returned. If you set smallSetLowerBound to zero and largeSetLowerBound to one, then no records will be returned because all sets will be large. But, we set largeSetLowerBound to some huge number and set mediumSetPresentNumber to zero, making all sets medium. This causes some servers to blow up. The previous combination is the one that the ZIG has agreed means that piggy-back presents are not wanted. Fix: Default largeSetLowerBound setting to 1. This fix is available in SiteSearch 4.2.1 or can be set directly in the appropriate server.ini file. This is a password protected site accessible to system administrators only.
BR177: When ANDing Two Terms, if One Term Contained 0 Hits, All Hits were Returned Instead of None Exists in Version(s): 4.2.0a Description: Two terms were ANDed together. If one of the terms should have returned 0 hits then all hits were returned (as if the terms were ORed together) instead of no hits as should have been returned. Fix: This fix is available in SiteSearch 4.2.1. This is a password protected site accessible to system administrators only.
BR176: Diacritics Display Incorrectly when Entered through Record Builder Exists in Version(s): 4.2.0, 4.2.0a Description: Diacritics displayed incorrectly when they were entered through Record Builder. When the widgets were processed by the SSwidgets2Infix class to strip out htmlDiacritics and set initial value for "displayquery", it took out the most of the latin1 diacritics, but not any of the UTF-8 diacritics. When the value for "displayquery" gets into the QUERY class, the "displayquery" has to be treated as a UTF-8 encoded string to display correctly. If Latin1 diacritics get passed to the QUERY class, the UTF-8 method there can still handle it properly. Fix: Added a condictional check to allow a user who uses a UTF8 interface to enter combined diacritics in the query term and have them display correctly. This fix is available in SiteSearch 4.2.1. This is a password protected site accessible to system administrators only.
BR175: Screen Display using Language Interface (obiv2) contained Entities where Labels should have Displayed Exists in Version(s): 4.2.0, 4.2.0a Description: The nfrefine.html page in obiv2 contained several errors which caused the entities not to be substituted and showed up incorrectly on the screen display. Fix: This fix is available in SiteSearch 4.2.1. This is a password protected site accessible to system administrators only.
BR174: Not Able to Change the ILL Session Delivery Values with Form Fields from the ILL Screen Exists in Version(s): 4.2.0, 4.2.0a Description:
The problem was with the way java handles method variables that are
"pass-by-value" and "pass-by-reference". In ISOILL.java,
there is a method called getFormData which takes two arguments: Fix: Fixed codes to properly modify the values. This fix is available in SiteSearch 4.2.1. This is a password protected site accessible to system administrators only.
BR173: "Modified Date" Field in Record Builder was not Updated when Change Made and Record Resubmitted Exists in Version(s): 4.2.0, 4.2.0a Description: The "modified date" field was not being updated when a change was made and the record was resubmitted in Record Builder. Fix: Fixed code to reflect current date in the "modified date" when record is edited and resubmitted. This fix is available in SiteSearch 4.2.1. This is a password protected site accessible to system administrators only.
BR172:
Query Parser Cannot Handle Some Russian Diacritic Characters Exists in Version(s): 4.2.0 Description: (1) The query parser cannot interpret certain Russian diacritic characters in a search request. (2) The query parser cannot handle Bath profile relational operators, such as "=", "<", ">", "<=", and ">=". (3) The query parser supports numeric values (such as "1999"), but not strings, such as "=1999" or "am_0001", in a rangeable index. Fix: A single fix to three query parser classes corrects all three of these bugs. This fix is available from the secure ftp server. This is a password protected site accessible to system administrators only.
BR169: E-Mailed Records Do Not Format Diacritics Correctly in Databases with Unicode Characters Exists in Version(s): 4.2.0 Description: When e-mailing records from a UTF8-encoded database (one that contains Unicode characters), the e-mail message does not format diacritics correctly. Fix: Corrected ORG.oclc.obi.extverb.EmailRecs so that it handles diacritics correctly when characterset=UTF8 in the format display specification for e-mail records. This fix is available from the secure ftp server. Also requires the fixes in BR152. This is a password protected site accessible to system administrators only.
BR168: zclient Throws Null Pointer Exception When Connecting to III Server Exists in Version(s): 4.1.2a, 4.2.0 Description: When using zclient to connect to a III (Innovative Interfaces, Inc.) server, zclient throws a null pointer exception after receiving the Init response from the server. The server sent an Init response with malformed data in the optional User-information-field. Fix: Improved error handling in the ORG.oclc.z39.client.Z39init the class so it can continue after receiving an Init response with bad data in the User-information-field. This fix is available from the secure ftp server. This is a password protected site accessible to system administrators only.
BR167: Record Builder Available Actions List Contains Options When Confirming Action Exists in Version(s): 4.2.0 Description: When Record Builder displays a prompt to confirm an action (such as submitting, deleting, or exporting records to a target database or saving a record in the Save database), the metadata specialist can select another option on the Available Actions list instead of being required to confirm or cancel the current operation. While this does not necessarily cause system failure or other errors, it can make the workflow confusing. This occurred because the verbs that perform these actions did not remove all other possible options from the Available Actions list. Fix: Modified the affected verbs and the gadget that creates the Available Actions list so they produce a list with no actions when the metadata specialist must confirm an action before proceeding. This fix is available from the secure ftp server. This is a password protected site accessible to system administrators only.
BR166: System Failure Page When Copying New Record After Restarting Record Builder Exists in Version(s): 4.2.0 Description: The Record Builder administrator restarts Record Builder via ssadmin. Then a metadata specialist starts a Record Builder edit session and submits a new record. Right after submitting the new record, he/she tries to copy the record and receives a system failure. A bug in the MCLONE verb caused this problem. Fix: Modified the MCLONE verb so that it checks the condition of the EditSessionID entity in the UserStateObject, and makes sure that the value of EditSessionID is not null. This fix is available from the secure ftp server. This is a password protected site accessible to system administrators only.
BR165: Record Builder Edit Record Screen Has Redundant Option in Available Actions List When Editing MARCCat Database Exists in Version(s): 4.2.0 Description: When using Record Builder to edit records in a database based on the MARC Catalog (MARCcat) database framework, the Available Actions list on the Edit Record screen has a redundant Edit Record option. Fix: Modified classes that build the Available Actions list that they create a list without the Edit Record option on the Edit Record screen when editing a database based on the MARCCat database framework. This is a password protected site accessible to system administrators only.
BR164: Record Builder System Failure Page When Importing and Exporting Records Exists in Version(s): 4.2.0 Description: Record Builder displays a system failure page after a metadata specialist tries to import or export a record. This occurs only with versions 1.2.22 and higher of the pears.jar file included with Database Builder. (SiteSearch 4.2.0 included version 1.2.20 of the pears.jar so this bug only occurs if you obtained version 1.2.22 or higher of the pears.jar file from the Pears Open Source project Web site.) Fix: Modified the Record Builder MEXPORT and MIMPORT verbs so that they function properly with version 1.2.22 and higher of the pears.jar file. This is a password protected site accessible to system administrators only.
BR163: Cannot Add the First Record to a New Pears Database with Record Builder Exists in Version(s): 4.2.0 Description: After registering a new Pears database with SSDOT for Pears and submitting the first record for this database with Record Builder, Record Builder displays an "Update Failed" message and does not add the record to the database. This occurred because SSDOT for Pears did not create an empty database during database registration. It did not create the new database until it added new records to the database during a batch update. Fix: Modified SSDOT for Pears so that it creates a new, empty database as part of the database registration process. This fix is available from the secure ftp server. This is a password protected site accessible to system administrators only.
BR162: Record Builder Cannot Increment Record IDs that Begin with Alphabetic Characters Exists in Version(s): 4.2.0 Description: Record Builder cannot increment a record ID that begins with alphabetic characters and ends with numeric characters (such as an OCLC number in the form ocmNNNNNN) specified a database's Record Builder recordid.txt file (in <WebZ_root>/dbbuilder/dbs/database_name). Fix: Modified the ORG.oclc.mantis.util.GetRecordIdFromFile class so that it can increment a record ID in the form aaaNNNNNN, where aaa is any number of alphabetic characters and NNNNNN is any number of numeric characters, in addition to record IDs that consist only of numeric values. For example, if you enter aaaNNNNNN as the starting record number in recordid.txt, Record Builder uses aaaNNNNNN as the record ID for the first record added to the database with Record Builder, aaaNNNNNN + 1 as the record ID for the second record, aaaNNNNNN + 2 for the third record, and so on. This fix is available from the secure ftp server. This is a password protected site accessible to system administrators only.
BR161: Newton Database User-Defined Plural Endings Do Not Work When Searching Local Database Exists in Version(s): 4,1.0, 4.1.1, 4.1.2a, 4.2.0 Description: A WebZ search against a local Newton database using a term with a pluralization character (+) only creates queries for the search term plus the default plural endings ("s" and "es"), even though you may have defined additional plural endings for the database in its database description (.dsc) file. For example, a search for "pon+" searches only for "pons" and "pones" even though you defined "ies" as a plural ending for the database. This occurred because the IndexMap class did not pick up changes to the default plural endings defined in the database's WebZ database configuration file. Fix: Modified the ORG.oclc.qparse.IndexMap class so that it reads a plural_endings variable from the [BIB1attributes] section of the database's WebZ database configuration file if it exists. The value of the plural_endings variable should match the plural endings defined for the database in its Newton .dsc file. This fix is available from the secure ftp server. This is a password protected site accessible to system administrators only.
BR160: OpServe Not Maintaining Minimum Number of Servers Exists in Version(s): 4.1.1, 4.1.2a, 4.2.0 Description: Even though you set MaintainMinimum=true in the [servername] section of the OpServe.ini or OpServe_rb.ini configuration file, OpServe does not maintain the minimum number of servers specified for the server in the MinServers variable. Fix: Modified the ORG.oclc.opserve.opserve.PollingThread class so that it starts new servers at the next polling period whenever the number of servers falls below the number specified in the MinServers variable. Beginning with SiteSearch 4.2.0a, each [servername] section in <WebZ_root>/ini/OpServe.ini and OpServe_rb.ini will contain a MaintainMinimum=false line to increase awareness of this variable. The fix to the PollingThread class is available from the secure ftp server. This is a password protected site accessible to system administrators only.
BR159: Barred Diacritic Lost When Followed by Barred Character in Pears Database Exists in Version(s): 4.2.0 Description: When building a local Pears database and creating input to BER records using the OCLC bar syntax for entering ALA characterset data, input of the form |<diacritic>||<letter>| loses the diacritic. For example, |ac||ho| should generate a hooked-o with an acute diacritic, but it only generates the hooked-o. Fix: Corrected the fromBars() method in ORG.oclc.util.Util.java to handle a barred diacritic followed by a barred character. This fix is available from the secure ftp server. This is a password protected site accessible to system administrators only.
BR158: Servers Do Not Report Memory Usage Correctly in Stats Log Exists in Version(s): 4.1.1, 4.1.2a, 4.2.0 Description: Servers report their free and used memory in the stats log as the modulus of 1024, rather than in bytes. Fix: Corrected the ORG.oclc.opserve.opserve.SiteSearchServer to display memory usage in bytes. This fix is available from the secure ftp server. This is a password protected site accessible to system administrators only.
BR157: Cannot Run WebZ or Record Builder as Windows NT Service with Java 2 Exists in Version(s): Any SiteSearch Windows NT version using Java 2 (JDK 1.2.2 or higher) Description: Once you install a Java Development Kit (JDK), version 1.2.2 or higher, for use with SiteSearch, you can no longer run WebZ or Record Builder as a Windows NT service. This occurred because the Java Native Interface (JNI) changed beginning with JDK 1.2.2. Fix: Created a new WebZ service file (java2webzservice.exe) that edits the Windows NT registry and the service with appropriate Java 2 JNI calls. This file is available from the FTP server. This is a password protected site accessible to system administrators only.
BR156: Internet Explorer Does Not Retain Charset Specified in langBase.ini Exists in Version(s): 4.2.0 Description: In some versions of Microsoft Internet Explorer, an interface based on the OBI, version 2 may not retain the charset specified as the default for a language-specific interface in its langBase.ini file (see the example file in the OBI, version 2 in <WebZ_root>/ini/interface/obiv2/en). HTML pages in the OBI, version 2 contain entity references to the variables in the [defaults] section of langBase.ini in their <META> tag in their <head> section, including a charset variable. Fix: Added a semicolon (;) to the end of the value of the content variable in the [defaults] section of langBase.ini so that it reads:
This allows Internet Explorer to interpret the character set specified in the <META> tag correctly. You can edit langBase.ini manually or obtain a new copy of this file from the FTP server. This is a password protected site accessible to system administrators only.
BR155: Cross-Database Search Resulting from Combining Searches on History Screen Produces Search Error Exists in Version(s): 4.2.0 Description: When combining searches on the history screen (<WebZ_root>/htdocs/obiv1/html/historysearch.html in the OBI, version 1) to do a cross-database search, the search produces a Z39.50 search error. In a cross-database search from the history screen that is not a topic search, the <WebZ_root>/ini/dbs/BaseGroup.ini file must contain an index definition for index searched. If it is not, ZBase cannot conduct a search. Fix: Add the appropriate index definition(s) to BaseGroup.ini. SiteSearch 4.2.0 provides an example of adding a new index definition to BaseGroup.ini. BR154: Full Text Button Missing from Full Record Display for ABI/Inform Exists in Version(s): 4.1.2a, 4.2.0 Description: The full record display for the FirstSearch ABI/Inform does not contain a full text button even when full text is available. This occurred because a rule specification for displaying the full text button was missing from the [full] and [nffull] display specifications in <WebZ_root>/ini/format/obiv1/ABIIFormats.ini. Fix: This fix is available in SiteSearch 4.2.0. BR153: Inspec Corporate Name Hotlinks on Full Record Display Do Not Work Properly Exists in Version(s): 4.1.2a, 4.2.0 Description: When searching the FirstSearch Inspec database through the WebZ interface, hotlinks in the Corporate Name field on the full record display always yield 0 hits (no results). This is due to the data in this field in the FirstSearch database itself. Fix: Removed hotlink from field specification for the [corporatename] display specification in <WebZ_root>/ini/format/obiv1/FSInspecFormats.ini. This fix is available in SiteSearch 4.2.0. BR152: Cannot Display Hotlinks and Unicode Diacritics Simultaneously in Pears Databases or Other Databases with Unicode Diacritics Exists in Version(s): 4.2.0 Description: In SiteSearch 4.2.0, there is no way to display for search results from Pears databases with hotlinks for fields such as the author, contributors, and subjects if the database records include Unicode diacritics. This is also true when displaying records from a remote database with records that include Unicode diacritics. One workaround, which displayed the diacritics but not the hotlinks, was to set doHtmlDiacritics = false in the formatting display specifications for Pears databases with records that include diacritics (any characters not in the Latin-1 character set).
Fix: This fix has two parts. You need the first part, described in (1) below, to display hotlinks for Pears and other databases with Unicode diacritics. You need parts (1) and (2) to enable access to databases with Unicode diacritics and databases that do not use UTF8 (Unicode) encoding in the same WebZ environment. (1) Modified three classes (ORG.oclc.fmts.RulesBasedDisplayGenerator, ORG.oclc.fmts.obi.UTFRecordDumper, and ORG.oclc.fmts.FormatBerUtil) so that they handle Unicode diacritics and hotlinks simultaneously when characterset=UTF8 and doHtmlDiacritics=true in a formatting display specification. (2) Created a new formatting configuration file, MarcCatalogFormats_UTF8.ini, to show how to use a localByteConverter to format records from a database that does not use UTF8 encoding (Unicode) in a WebZ interface that has been set up for displaying UTF8-encoded databases. If your WebZ interface includes access to both UTF8-encoded and non-UTF8-encoded databases, use this formatting configuration file as an example for modifying the formatting configuration files of non-UTF8-enclosed databases. These fixes are available from the secure ftp server. This is a password protected site accessible to system administrators only.
After downloading the fixes
BR151:
Refining a Search Using Term that Contains a Colon (:) Returns Error 108
(Malformed Query from Search) Exists in Version(s): 4.1.0, 4.1.1, 4.1.2a Description: Conducting a search using a term that includes a colon, such as "alcoholics:", works as expected and returns search results if matching records exist in the target database(s). However, trying to refine a search using the same search term returns the Z39.50 error 108 (malformed query from search). In the initial search, ZBase creates the search term as "query(ti: {alcoholics\:})". The backslash (\) operates as an escape character, so that the colon is interpreted as the colon character and not the ending character in an index abbreviation. When refining the search, ZBase creates the search term as "query(ti: {alcoholics:})". Without the backslash preceding the second colon, the target database cannot interpret this query properly and returns error 108 in response. Fix: Modified ORG.oclc.webz.SSWidgets2Infix so that it adds the backslash as an escape character to "abbreviations" within the inside braces of a search term when they do not match an index abbreviation contained in the database's configuration file. This fix is available in SiteSearch 4.2.0. Go
to BR150 – BR101 See Also OCLC
SiteSearch Known Bug List (by Detailed Description) – Part
II |
|
||