Known issues
Please see the OCLC System Status Dashboard for active issues.
Updated: 17 May 2021
Current Issues
| Issue | Details |
|---|---|
| Query collections in WorldShare Collection Manager are not processing records when the WorldCat Selection Criteria contains a hyphen. |
Query collections in WorldShare Collection Manager that contain a hyphen (-) in the WorldCat Selection Criteria are not returning records to My Files. Workaround: Replace the hyphen(s) in your WorldCat Selection Criteria with two periods (..). The Query collection will return records. |
| The Updated Records report is not populating the Provider and Collection Name columns when a record has an Update Reason of Subsequent record output | At this time, both the Provider and Collection Name columns are not being populated if the Update Reason provided is Subsequent record output. Please note that both columns are being populated for all other update conditions. We ask for your patience and look forward to resolving the issue as soon as possible. |
|
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:
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. Note: For proper link display, your settings must be correct:
|
| 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:
When searching for titles from the main Collection Manager search box with My Selected Collections:
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. |