Skip to main content
OCLC Support

All known issues

Find all known issues for OCLC products and services.

CONTENTdm

CONTENTdm known issues

There are no known issues at this time.

EZproxy

EZproxy known issues

Installation & Configuration

Issue Details

EZproxy on Windows unable to support LDAP over IPv6

Version Affected: V6.0 and later

EZproxy v6.0 added support for IPv6, but did not add this support to LDAP. EZproxy V6.1.6 made LDAP aware of IPv6 addresses, but the library support was not enabled correctly to support this, causing failures for sites that have both IPv4 and IPv6 addresses for their LDAP servers.

At this time LDAP support will be limited to IPv4 on Windows, but IPv6 will be supported on other platforms.

Security

Issue Details

FREAK Vulnerability

 

EZproxy V5.7.44 and V6.0.7 are NOT vulnerable to the FREAK security issue IF you have the following settings in your config.txt:

Option DisableSSL40bit
Option DisableSSL56bit
Option DisableSSLv2

Add the following directives to your config.txt to protect against the FREAK vulnerability:

Option DisableSSL40bit
Option DisableSSL56bit
Option DisableSSLv2

Build issues

Issue Details

Support for IPv6 Addresses via the EZproxy Location directive

Version affected: V6.0

EZproxy 6.0 does not support use of the Location directive to look up IPv6 addresses. We have not yet extended our support to the MaxMind V6 GeoLite database (GeoLiteCityv6).

Fix Date: TBD

A future version of EZproxy will incorporate new compatibility with IPv6 address lookup.

Using IPv4 addresses in IPv6 notation

Version affected: V6.0

Do not use IPv4 addresses in IPv6 notation format to determine whether or not to make IPv6 network calls. For example, the IPv4 address 127.0.0.1 will not be treated equivalently to the IPv6 0:0:0:0:0:ffff:7f00:1 address.

This is the designed behavior, and no remediation is planned

Dual Stack (IPv6/IPv4) cannot run when EZproxy is set to ProxyByPort

Version affected: V6.0

In order to provide support for IPv6 ProxyByPort, you must duplicate the database stanzas using IPv6 syntax.

This is the desired behavior, and no remediation is planned

The way we build EZproxy with OpenSSL

Version affected: V6.0 and earlier

Today we statically link OpenSSL’s binary library with EZproxy. We do this because this build method makes installation of EZproxy much easier for our EZproxy institutions--the institution doesn’t have to track and manage the OpenSSL version on their system.

We will further evaluate whether or not we should build EZproxy by dynamically linking OpenSSL, but we have no current plans to build EZproxy that way.

A 64 bit build of EZproxy

Version affected: V6.0 and earlier

Newer Windows and Linux systems are 64 bit-based operating systems, which provide a much larger address space for programs like EZproxy. Very few EZproxy institutions are seeing this memory limit, however a few are starting to bump up against it.  

In some cases, a 64 bit version of the same program (such as the 64 bit Chrome browser) will run slightly faster than the 32 bit equivalent.  Both Linux and Windows have very good facilities for running 32 bit applications on 64 bit operating systems. However the more significant issue for EZproxy is the memory limit.

Fix Date: TBD

Because of the potential memory limit issues (and it’s still pretty rare), we are planning to provide 64 bit builds of EZproxy V6.x in the future.

WorldCat Discovery

WorldCat Discovery known issues
Issue Details
When Level 1 Library scope and a branch scope are both selected, the “held by” statement displays Level 1 Library information rather than branch information. Workaround: Deselect the Level 1 Library scope filter when a branch filter is in use.
Branch holding display does not appear when search results are ungrouped

Workaround: Enable grouped display of results when searching branches.

When the filter for the grouped display of results is disabled and only a branch is selected, the “held by” statement displays information for Level 1 Library instead of the selected branch.

"Held by" statement for titles under embargo

Update: As of 12/17/19 we have resolved this issue for most types of Discovery index searches. We are continuing to work on resolving this issue for the no: index search.

In WorldCat Discovery, when an article displays a knowledge base link that has an embargo period or moving wall of coverage, links will correctly display or not display in alliance with the coverage information in your knowledge base title. However, the "Held by" statement uses different logic. It is a known issue that the statement might appear for items not yet available, including those that correctly do not surface links.
 
Similarly, if a journal title in your knowledge base has multiple coverage ranges with gaps in coverage, articles that surface in Discovery search results that fall within the gap of coverage will have a "Held by" statement. 

Note: For proper link display, your settings must be correct:

  • In WorldShare Collection Manager, Institution Settings > Coverage > Use Coverage to Determine Holdings should be set to Yes
  • In OCLC Service Configuration, under Default Databases and Licensed Content, Treat as held should be disabled for your selections

 

See all fixed WorldCat Discovery known issues.

WorldCat Validation

WorldCat Validation known issues

There are no known issues at this time.

 

WorldShare Acquisitions

WorldShare Acquisitions known issues

There are no known issues at this time.

 

See all fixed WorldShare Acquisitions known issues.

WorldShare Circulation

WorldShare Circulation known issues

 

Issue Details

Report Missing action not working consistently

The Report Missing dialog box does not close automatically after confirming that the item is missing.

The first item that you mark as Missing during a session will have its status updated as expected. However, any subsequent attempts to mark other items as Missing will fail.

Identified: February 2020

Workaround: Close the Report Missing dialog box by clicking the Cancel button or the x in the top right corner.

To mark several items as Missing, you will need to force WMS to reload or log out between item updates. You can verify an item's status from the Copies screen or by reopening the Item Details page.

Offline Client and POS Printer Server Application do not run from the Start Menu on Java versions later than Java 8u162

Later versions of Java 8 introduced a bug which will fail to launch applications from the Start Menu of your workstation.

Note: Java 9 and higher are not yet supported.
 

Identified: May 2018

Workaround: Install Java SE Runtime Environment 8u162 or earlier to run the Offline Client and POS printer application from your workstation's Start Menu. If you must run a later version of Java 8, you can still run the applications by executing the JNLP files directly (i.e. wms-offline-circulation.jnlp and wms-posprinter-server.jnlp).
 

 

See all fixed WorldShare Circulation known issues.

WorldShare Collection Evaluation

WorldShare Collection Evaluation known issues

 

Issue Details

Date last circulated/Number of times circulated filtering error

An error message appears when attempting to filter My Library or a Unique/Shared Titles Comparison by date last circulated or number of times circulated.

Identified: 20 June 2016

Workaround: Attempt to filter the chart a second time. In most cases, the filter will work on a successive attempt.

This issue will be addressed in a future release.

Benchmark Comparison preview error

An error message appears when attempting to preview a Benchmark Comparison.

Identified: 20 June 2016

Workaround: Attempt to render the preview a second time. In most cases, the preview function will work on a successive attempt.

This issue will be addressed in a future release.

Unique/Shared Titles Comparison against Hathi error

A Unique/Shared Titles Comparison against Hathi fails to load.

Identified: 20 June 2016

Workaround: Attempt to run the comparison a second time. In most cases, the comparison will work on a successive attempt.

This issue will be addressed in a future release.

 

See all fixed WorldShare Collection Evaluation known issues.

WorldShare Collection Manager

WorldShare Collection Manager known issues

 

Issue Details

Searching by WorldCat Registry ID not working as expected when sharing collections at both the institution and collection level

While the functionality to share a collection by Registry ID is working, searching via Registry ID does not result in displaying the value in the input box, for both the institution and collection level share.

You are able to verify that your share was successful via Activity History, the ‘Sharing’ column on the collection search results page, and/or verification that the Registry ID(s) are populated in the Sharing accordion.

We ask for your patience and look forward to resolving the issue as soon as possible.

Tip: Provide the institution name when sharing collections.

Lag times in the WorldShare Collection Manager interface for the reflection of changes you make to knowledge base collections

You might notice an increase in the time of reflection of actions in knowledge base collections in the WorldShare Collection Manager interface such as:

  • Selecting knowledge base collections or titles
  • Adding titles to locally-created collections
  • Changes to title-level data fields

These issues are exacerbated at times and are not always noticeable. We have researched and identified the causes and are working across teams to structure a plan to address them. We ask for your patience and look forward to resolving the issue as soon as possible.

When adding titles or submitting title data changes other than OCLC number through cooperative management, changes are only preserved across data updates from the provider for a subset of collections While OCLC number change submissions are retained for all collections, other cooperative management functionality only works for a subset of WorldCat knowledge base collections. View the list of WorldCat knowledge base collections for which all cooperative changes are retained across data updates.

Do not add titles or submit title data changes (other than OCN) through the cooperative for collections that are not included on the above list. If you do, they will be overwritten on the next data load that OCLC processes from the provider. Note that this will not affect any changes you have made to title data in your local version of the knowledge base collection. We always recommend making the changes you need to customizable collections and saving those changes locally.

This issue does not affect any of the cooperative collections that are added to the knowledge base by member libraries. Also, OCN submissions through the cooperative are now retained for ALL knowledge base collections.
Titles added to knowledge base collections via Cooperative Management When OCLC loads provider data and the provider has changed titles in the collection list (added or deleted items), it is possible that titles added by libraries via cooperative management will drop out of a collection. OCLC is working to re-architect how we ingest data and to solve this issue.
Update records always delivered when Provider Name or Collection Name changes We have a known issue that causes an update record to be delivered whenever a Provider name or Collection name for a knowledge base collection changes, regardless of whether or not those values have been profiled for MARC output.  This issue has been logged and will be resolved in a future release.
"Held by" statement for titles under embargo

In WorldCat Discovery, when search results contain an article or item from a knowledge base title that has an embargo period or moving wall of coverage, links will correctly display or not display in alliance with the coverage information in your knowledge base title. However, the "Held by" statement uses different logic. It is a known issue that the statement might appear for items not yet available, including those that correctly do not surface links.
 
Similarly, if a journal title in your knowledge base has multiple coverage ranges with gaps in coverage, articles that surface in Discovery search results that fall within the gap of coverage will have a "Held by" statement.  

Note: For proper link display, your settings must be correct:

  • In WorldShare Collection Manager, Institution Settings > Coverage > Use Coverage to Determine Holdings should be set to Yes
  • In OCLC Service Configuration, under Default Databases and Licensed Content, Treat as held should be disabled for your selections
Differences in the data for some titles you have edited show in search results in Collection Manager

Edits you have made to coverage and other fields are respected in WorldCat Discovery. However, you could see differences in title search results within Collection Manager under these conditions:

  1. The collection is global and customizable.
  2. You selected the collection in full, not a subset of titles.
  3. You edited fields such as coverage after selecting the collection in full.

When searching for titles from the main Collection Manager search box with My Selected Collections:

  • Selected: Title shows as held; Your overlay coverage is displayed
  • Unselected: Title does not show as held; Global coverage is displayed

When searching within collection, the title will show as held when searching by All Titles and by My Selected Titles; However, your overlay coverage information only shows when searching by My Selected Titles. Again, your edits are used outside of the interface.

 

WorldShare Interlibrary Loan

WorldShare Interlibrary Loan known issues
Issue Details

Please note that this known issue only applies to Referral Center members, a small subset of ILL users. 

If a Referral Center member changes the fulfillment type from Interlibrary Loan to Purchase, the request is no longer accessible in their borrowing queues.  The request ID is still findable by searching on the Home page. 
 

Work-around: Do not change the fulfillment type of an Interlibrary Loan request when signed in as a member of a Referral Center.  ILL staff at the management center are still able to adjust the fulfillment type as needed. 
Potential anomalies in Article Exchange statistics The product team is investigating potential anomalies in the All Article Exchange Monthly Upload report and the Daily Article Exchange Lending report.    
Patron’s ‘Preferred Edition’ is replaced with 'Any Edition' in new borrowing requests that do not match a Direct Request profile New borrowing requests that match a Direct Request profile display the patron’s Preferred Edition correctly.  However, new requests that do not match a profile will display 'Any edition', regardless of the value selected on the patron request form.  Borrowing staff can select a different value (“Most recent edition” or “This edition”) and lenders will see the correct value.
The borrower's maximum cost amount is moved to the Borrowing Notes field (i.e. MC:25.00) when staff submit a request for Direct Request processing from the WorldShare ILL staff interface. Note that the IFM checkbox selection will be retained. Work-around: Manually build the lender string and submit to lenders.

 

 

See all fixed WorldShare Interlibrary Loan known issues.

WorldShare License Manager

WorldShare License Manager known issues
  • The Trial License Survey feature does not work with Internet Explorer 11. This will be fixed in a subsequent release. Firefox and Chrome are unaffected by this issue.

WorldShare Record Manager

WorldShare Record Manager known issues

 

Issue Details

Update Temporary Shelving location for LHRs

When trying to update the Temporary Shelving Location for Local Holding Records in Record Manager from a search results list the option “Change Shelving Location” in the Actions menu is grayed out and cannot be selected.

Workaround: Temporary shelving locations can be updated in WorldShare Circulation and Acquisitions, first search for LHRs you wish to update and change the temporary shelving location using the Actions menu.

Diacritics or punctuation in script names
Diacritics or punctuation in script names will cause the filter to be unable to filter to that script name.

Workarounds: Users should avoid using diacritics or punctuation in script names until this issue is resolved.

Cannot delete a text or field string if the name of the string contains diacritics

If diacritics are used within the name of the text or field string, the text or field string cannot be deleted from the Toolbox.
Workaround: Do not use diacritics in text or field string names until this issue has been resolved.  

Shortcut for label printing

When you are in an LHR and attempt to use the shortcut key for label printing twice in one field, you only receive one entry on the label list.

Workaround: Click on a new field within the LHR and execute the shortcut key again.

 

See all fixed WorldShare Record Manager known issues.

WorldShare Reports

WorldShare Reports known issues

 

Issue Details

Copy Received Date is not being set for monographic series

The Copy Received Date is not being set in Acquisitions for the monographic series. All order items with processing type MONOGRAPHIC_SERIES currently have their received date set to 0001-01-01. In order to see MONOGRAPHIC_SERIES records in the Receiving Activity by Location report you will need to set the From Received Date prompt to 0001-01-01. However, please note the volumes under the monographic series will have the correct Copy Received Date populated with the date the volumes were marked as received.

Identified: 22 January 2020

Impact: Libraries utilizing monographic series orders in the WMS Acquisitions module

Workaround: Selecting a start date of 0001-01-01 in the Receiving Activity by Location report will retrieve the monographic series copy received date.

This will be fixed in a future release.

Users unable to run standard reports from the Analytics tab after selecting 'Log Off' in Report Launch Pad

For users with Report Author and Report Scheduler roles, signing out of a Report Launch Pad session causes the users to not be able to run standard reports from the Reports accordion in the Analytics tab view. User is presented with the SAP log in screen.

Identified: 8 July 2016

Impact: Libraries Utilizing the Report Designer product or Report Schedulers

Workaround: Refreshing the WorldShare browser tab will enable the standard report links.

This will be evaluated for a future release.

Historical shelving locations in circulation events

The shelving locations in circulation events prior to June 21, 2015 may be incorrect as they will contain current shelving locations and not the locations at the time of the event. Historical values in the Monthly Circulation Statistics reports may not reconcile with previous reports run in other OCLC reporting environments.

Identified: 21 June 2015

Impact: All libraries

This will be evaluated for a future release.

 

See all fixed WorldShare Reports known issues.

Tipasa

Tipasa known issues

 

Issue Details
Some library patrons are receiving an "A System error occurred" error message after clicking on the Interlibrary Loan button from a detailed record in WorldCat Discovery. A cookie was discontinued after the January 29th 2020 WorldCat Discovery install. The error occurs when the discontinued cookie is still retained by the patron's browser. Work-around: Patrons should clear their browser cookies and cache. 
 
Libraries serviced by the Australian Data Center (Australia and New Zealand)  are experiencing a delay in notification delivery. Notifications are queuing but are not being delivered to patrons.  

On resubmitted requests, the asterisk may not be displayed on the correct occurrence of the symbol in the lender string when the lender appears more than once.  It will be displayed on the first occurrence in the string, even if the request has actually moved to the later occurrence. This is purely cosmetic and does not affect functionality. 

 
WMS OPAC lookup puts duplicated Branch and Shelving Location into Local ID

 
Work-around: Delete branch location from Local ID field and save prior to printing.  
If a loan request passed through several lenders before being filled, it is possible that the Lending Library to Borrowing Library notifications will be triggered based on the wrong due date.  This happens when any of the earlier potential lenders saved a due date on the request but then said no or the request aged to the next lender.  The notification will be initiated for the current supplier based on their notification settings, but based on the potential lender’s incorrect due date.  
Potential anomalies in Article Exchange statistics The product team is investigating potential anomalies in the All Article Exchange Monthly Upload report and the Daily Article Exchange Lending report.
Patron’s ‘Preferred Edition’ is replaced with 'Any Edition' in new borrowing requests that do not match a Direct Request profile New borrowing requests that match a Direct Request profile display the patron’s Preferred Edition correctly.  However, new requests that do not match a profile will display 'Any edition', regardless of the value selected on the patron request form.  Borrowing staff can select a different value (“Most recent edition” or “This edition”) and lenders will see the correct value.

 

 

See all fixed Tipasa known issues.

 

  • Was this article helpful?