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
Removing an item from an existing course removes all titles An issue with WorldCat Discovery Course Reserves is causing the deletion of all titles from a course when a single title is removed. Please refrain from removing titles from Course Reserves while we pursue resolution of this issue. We expect to resolve this issue as soon as possible.
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

Unable to download the Offline Client

An error displays in OCLC Service Configuration when attempting to download the Offline Client.

Identified: September 2020

This issue will be resolved as quickly as possible.

Hold pickup notifications are not delivered for group requests

Hold pickup and shelf expiry emails fail to be sent if the patron and item belong to different instituitions in a circulation group. In notification history, the emails appear stuck in 'Sent for Processing' status. In item statistics, the reminder appears in 'Creation In Process' status.

Identified: September 2020

This issue will be resolved as quickly as possible.

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.

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.

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.

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

Option to add a local knowledge base collection to the global knowledge base is missing from the Collection Manager interface

This issue has been resolved as of late evening 18 August 2020 EDT.

Within local collections, the option to promote the collection to a global, cooperative collection is missing from the interface. In the Collection Actions drop-down, Add Collection to the Global Knowledge Base does not appear. Only Delete Collection is visible.

OCLC plans to fix this bug as soon as possible in this month of August 2020.

 

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
Resubmitting a request results in an error message when a lender in a previous attempt goes non-supply.  Work-around: Create a new request using the Copy function. 
Batch responding Yes as a lender results in an error message if Constant Data is applied during the batch process.   

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. 
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
  • A bug exists where when using Collection Manager to add collections to 'Temporarily Free Licenses' or 'Trial Period Licenses' the license will become stuck with a status of pending. The current workaround for this issue is to only add collections to those license types through the License Manager interface. Perpetual and standard licenses are unaffected by this issue.

WorldShare Record Manager

WorldShare Record Manager known issues

 

Issue Details

When applying constant data to a bibliographic record, the edit icon does not display on the tab

When you have a bibliographic record open and select Record > Bibliographic Constant Data > Apply, when constant data is applied to the record, the orange edit icon is not appearing on the tab to show the record was edited.

Workaround: Not available as this is a display issue and will be fixed in a future release.  
Delete bibliographic record option does not appear in Record drop-down menu when moving LHRs and deleting the holding 

When you move LHRs from a bibliographic record that was created by your institution (040 $c shows your OCLC symbol) and remove the holding, the Delete option is missing from the Record drop-down menu until you close the tabs and reperform your search for the bibliographic record.  
Workaround: Once the move action has been completed, close all tabs and reperform your search for the bibliographic record to see the Delete option in the Record drop-down menu.
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.

When applying constant data to a local holdings record from the preview constant data page, the indicator values for the 852 field do not apply

When you are on the preview constant data page and attempt to apply constant data, the indicator values for the 852 field in the LHR constant data record will not apply to the record being edited.

Workaround: Indicators have to be added manually

 

See all fixed WorldShare Record Manager known issues.

WorldShare Reports

WorldShare Reports known issues

 

Issue Details

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
Resubmitting a request results in an error message when a lender in a previous lender string goes non-supply.  Work-around: Create a new request using the Copy function. 
Batch responding Yes as a lender results in an error message if Constant Data is applied during the batch process.   

Using the Everything option in the Find Patrons search in Tipasa to look for patron records will now only search:

  • ILL Identifier
  • ppid
  • User ID at Source
  • Barcode (if present)
This search will be appropriately renamed Identifier with the 16 August Tipasa release.  Future releases will provide new search capabilities by email address and a new combined index.  Until then, you can use the Admin tab in WorldShare to search for patrons by email address if needed.
The Chat feature often used in Custom Link 1 in Service Config> WorldCat Discovery and WorldCat Local>User Interface Options> Custom links is not working from the User Portal.  Work-around

To make Chat available to your library users from My Account, you can add an additional link link in the Resources menu (formerly Library Links).

To do this:

  1. Go to OCLC Service Configuration and navigate to WorldCat Discovery and WorldCat Local > User Interface Options > Custom Links.
    Note: If the Chat widget is already set up as Custom link 1, and you would like the Chat function to continue to display within WorldCat Discovery, do not make any changes to Custom link 1.
  2. Add a new Custom link for your Chat service with:

·         Link type: other

·         URL: <URL for your virtual reference service>

·         Display text: <descriptive text>

  1. Save Changes.

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.  
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?