Skip to main content
OCLC Support

CONTENTdm release notes, October 2018

Release Date: October 25, 2018

Overview

This release expands CONTENTdm’s advanced customization capabilities, provides the ability to integrate the IIIF Mirador viewer into your site, makes significant accessibility improvements, and removes the 400-collection server limit. Additionally, there are changes to improve end-user privacy and to better comply with the European Union’s General Data Protection Regulation (GDPR).

If you are using the responsive CONTENTdm website, OCLC offers free HTTPS support at a *.contentdm.oclc.org domain of your choosing. If you would like to use HTTPS with your institution domain name instead, we can support it. Visit Configure CONTENTdm domain with SSL to support HTTPS for more information on HTTPS and custom domains.

Release overview recording 

 View a recording of the CONTENTdm release overview, October 2018.

Features and enhancements

This release enables the following capabilities:

  • You can have more than 400 collections on your CONTENTdm site.
  • It’s much easier to work with a large number of custom files and folders in the Website Configuration Tool.
  • You can create sophisticated advanced customizations, including embedding the Mirador viewer.
  • Accessibility is significantly improved based on feedback from current user accessibility offices.
  • You can better protect end-user privacy when using Google Analytics and by displaying your privacy policy.
  • You’ll notice other miscellaneous fixes.

You can have more than 400 collections on your CONTENTdm site

The server limit of 400 collections has been eliminated. There is currently no upper limit defined. We have tested up to 1,200 collections. This feature was beta-tested by two current users over the past few months and is now available to all sites.

Please note, as your collections count increases, you might gradually experience longer approval and indexing times.

It’s much easier to work with a large number of custom files and folders in the Website Configuration Tool

If you have done significant customizations on your site, you may have noticed limitations with the file manager in the Website Configuration Tool (Custom > Custom Pages > manage files). This file manager has been upgraded and now supports uploading multiple files at once and uploading entire directories. Now you can drag-and-drop an entire folder to upload, and this folder can even contain sub-folders.

upload_file1.png
 
This change makes creating complicated customizations much more feasible and makes it easier to manage your local copies of your custom files.

upload_file2.png

You can create sophisticated advanced customizations, including embedding the Mirador viewer

The improvements to the file manager have made it much easier to incorporate more advanced customizations. Instructions for integrating Mirador into your website will be available in the customization cookbook after the release.  

embed_mirador_viewer.png

Another improvement for customization is the addition of class names to the metadata fields in the Object Description and Item Description accordions. This makes it easier to create customizations based on the metadata values in specific fields and improves the robustness of your custom code.

Notice that the nicknames of the fields, which are used in CONTENTdm API calls and in search URLs, make up the new class names, e.g. “field-descri” or “field-title” as shown below:

class_names1.png

 class_names2.png

To differentiate the same field in Object Description and Item Description, prepend “object-” and “item-” to the class names.

This change will make some very interesting customizations more feasible. It gives your custom code a reliable method to identify and utilize the information stored in metadata fields. Here is a short list of customization ideas:

  • streaming or other external content URLs in a metadata field that get pulled into an embedded <iframe> in the page;
  • referencing linked data URIs stored in metadata so that the end user sees something friendlier, like a Creative Commons license statement or rightsstatements.org descriptive paragraph; or
  • adding IIIF Image and Presentation links that you want to expose or adapt for drag-and-drop with Mirador viewer.

Accessibility is significantly improved based on feedback from current user accessibility offices.

Two current CONTENTdm users performed accessibility reviews through their official accessibility assurance offices. Based on the feedback from these usability tests, we made several improvements to the markup of most pages in the CONTENTdm website.

  •  All default CONTENTdm pages now have an <H1> heading, which is important for helping a screen reader user understand the page structure.
  • We have improved labeling on several UI elements, and reorganized the use of WAI-ARIA groups.

You can better protect end-user privacy when using Google Analytics and by displaying your privacy policy

Due to increasing privacy concerns and specifically GDPR, we modified the embedded Google Analytics snippet to anonymize the end user IP address. This brings your Google Analytics usage into compliance with GDPR.

Another part of GDPR is making your privacy policy statement easily accessible. The text of this privacy policy will have to come from your institution, but we have published customization recipes to integrate these policies into your CONTENTdm site. You can either display the policy directly within CONTENTdm as a custom page or simply add a menu link to the policy statement on your main institution website. See Privacy policy for more information.  

You’ll notice other miscellaneous fixes

  • The Website Configuration Tool interface for “Suggested Topics” (Collection-level Settings > Page Types > Landing Pages) now shows all of your previous edits.
  • The navigation panel for monographs in mobile view now scrolls to and highlights the current node when jumping between nodes.
  • The “Browse” and “About” menu links show up in the same order in the main hamburger menu and the footer menu.

Looking ahead

This list is a summary of frequently requested enhancements by current CONTENTdm users and has been flagged as high priority for upcoming releases.

  • Custom collection aliases
  • Support for IIIF collection manifests
  • Support for text annotations and transcripts in the IIIF Presentation API
  • “Go to page ##” functionality on search results and the homepage
  • Ability to open results in new tab or window

We are always looking to you to help us determine the priority of new features, improvements, and fixes. If one of the above issues is urgent for your site, or if another issue not listed above is more important to you, please contact OCLC Support and let us know. You are also invited to post your ideas to the CONTENTdm Community as a discussion thread or an enhancement suggestion.

The next release of CONTENTdm is expected for early 2019. Not all of the above items are expected to be completed in that timeframe.

Upgrading to the new responsive website

The new CONTENTdm website is completely separate from the 6.x CONTENTdm website. When you are ready to publish the new website as your production website, contact OCLC Support to schedule your upgrade.

OCLC is continually improving the new website interface and is no longer enhancing the 6.x website. The CONTENTdm responsive website is now the default end-user website for about 200 active users.

 

  • Was this article helpful?