Need assistance for CONTENTdm?

Known Issues


Please see the OCLC System Alerts page for additional active issues.

Updated:  November 14, 2016

Data uploaded via the custom end-user web add form does not land in the approve queue

When a user attempts to upload data via the custom end-user web add form, the data does not successfully make it to the approve queue for indexing, but no errors appear to make this evident to the user.

Bug #: CDM-963

Affects: Hosted users

Status: This bug was fixed on November 10th, 2016.

New custom collection landing pages cannot be added via the Website Configuration Tool

A bug is preventing the dialog from opening in the Website Configuration Tool that allows CONTENTdm administrators to upload or link to a custom collection landing page.

Bug #: CDM-985

Affects: Hosted users

Status: This bug was fixed on November 10th, 2016.

Records missing from search results and browses

Some users are reporting that records known to exist in CONTENTdm are missing from search results and browses. Sometimes reindexing will bring these records back into the search results. In some cases, the missing results will appear and disappear when refreshing the same search in the browser. All of these problems with missing records are caused by a failure in the search engine to index the data properly. The likelihood of the problem to occur relates to the size of the overall index and the size of individual records, but that is not always the case and there is no action you can take to prevent the problem from occurring.

This issue may be able to be resolved by OCLC customer support. If you are experiencing this issue please contact Support and describe the problem, referencing the following bug number.

Bug #: CDM-11182

Affects: Hosted users

Status: This bug was fixed in October 2016. If you are still seeing missing records in search and browse results, please contact support.

"Ghost" records showing up in searches and browses

When you make structural changes to existing compound objects (in CONTENTdm Administration or the Project Client), "ghost" records with no metadata may show up in search and browse results after indexing. This problem is caused by a bug in the indexing code that fails to remove the reference to the page or the object when it has been deleted or moved to another compound object.

This issue may be able to be resolved by OCLC customer support. If you are experiencing this issue please contact Support and describe the problem, referencing the following bug number.

Bug #: CDM-11210

Affects: Hosted users

Status: This bug was fixed in October 2016. If you are still seeing "ghost" records in search and browse results, please contact support.

Duplicate records in searches and browses

When you make structural changes to existing compound objects (in CONTENTdm Administration or the Project Client), you may see duplicate records in search and browse results after indexing. This problem is caused by a bug in the indexing code that creates an extra copy of the record in the index. This bug does not lead to a creation of a second copy of the record, so the duplicate should not be deleted from CONTENTdm. Trying to the delete the duplicate may delete your original record as well.

This issue may be able to be resolved by OCLC customer support. If you are experiencing this issue please contact Support and describe the problem, referencing the following bug number.

Bug #: CDM-11252

Affects: Hosted users

Status: This bug was fixed in October 2016. If you are still seeing duplicate records in search and browse results, please contact support.

Incorrect counts in CONTENTdm Administration Page View Reports

Some users are seeing incorrect page view counts in the page view reports available through CONTENTdm Administration.

Bug #: CDM-11260

Affects: hosted users

Status: This has been fixed as of November 1st, 2016. If you still encounter problems with page view counts, please contact support.

Updates using Catcher result in corruption to metadata containing diacritics and other non-ASCII characters

When using the Catcher web service to update existing metadata records, the character encoding is not being preserved upon integration into the CONTENTdm database. The result is that diacritics and other UTF-8 characters are corrupted. There is currently no workaround for this problem and Catcher should not be used with non-ASCII characters at this time.

Bug #: CDM-11258

Affects: Catcher API users

Status: This bug was fixed on Thursday, October 13, 2016.

Every other ‘configuration’ link is disabled in the CONTENTdm Administration Server tab if the users.txt file is too large

In some cases, when a large number of collections with aliases of a certain length are added to a user's permissions, creating a users.txt file of over 4,096 bytes, every other 'configuration' link in the CONTENTdm Administration -> Server -> Collections tab is disabled.

Workaround: Within CONTENTdm Administration, navigate to the Collections tab, click 'profile' and then choose the collection.

Bug #: CDM-712

Affects: Hosted and locally installed users

Status: Fixed for hosted users in the October 2016 release