Release Date: June 26, 2019
This release adds the ability to print metadata with digital items, improves search engine discovery for compound object pages, adds IIIF collection manifests, clarifies single collection date search rules, adds two more interface languages, and includes some miscellaneous bug fixes.
The CONTENTdm responsive website is now the default end-user website for more than 350 active users.
Release overview recording
View a recording of the CONTENTdm release overview, June 2019.
Features and enhancements
This release enables the following capabilities:
- You can now print metadata with a digital item image, rather than just the item preview.
- The individual pages of your compound objects have been added to sitemap files to make them discoverable by search engines.
- IIIF collection manifests are now automatically generated, allowing IIIF resources to take advantage of entire collections
- In Advanced Search, date search within a single collection now only uses the first field with the data type of “Date” to ensure seamless searching.
- Two more interface languages have been added for localization support: Italian and Portuguese.
- Fixed a bug where, when searching, certain compound objects display pages in the incorrect order.
- Fixed a bug where certain compound objects display the incorrect page title in the navigation pane.
In March 2019, we made a change for sites that have permanently switched to the new responsive website: the home page URL no longer must have “/digital” appended to the end. For example, you can now use https://cdmdemo.contentdm.oclc.org to be your home page in addition to https://cdmdemo.contentdm.oclc.org/digital.
The above features and enhancements are described in more detail below.
Print metadata with a digital item image
After many user requests, you can now print metadata along with the digital item, rather than only the item preview. Having more descriptive context when printing images makes archiving, teaching, and general management easier. Previously, the item metadata was prevented from printing with digital items.
Choose what metadata you want to print by expanding or collapsing the “Transcript,” “Object Description” and “Item Description” sections. As illustrated below, if you collapse “Transcript” and “Object Description” on the webpage (first image), then they will not print (second image):
Individual pages of compound objects have been added to sitemap files
The URLs to individual pages of your compound objects have been added to sitemap files to make them more discoverable by search engines. Including pages means all page transcripts and other page-level metadata will be more easily added to the indexes of major search engines. For CONTENTdm sites with a large number of compound objects, you may notice a significant increase in the size of sitemap files and the total number of records that search engines will index. This increase is intentional and should increase the amount of traffic to your website referred by Google and other search engines.
Note that sitemaps in CONTENTdm are built one day per week per site. Your sitemaps may not automatically be updated on June 26th (the day of this release) but will be updated within a week the day of your next scheduled sitemap build.
IIIF collection manifests are automatically generated for all collections
We continue to expand support for IIIF. All image records in CONTENTdm already had IIIF Image and Presentation API responses built in, but with this release complete manifests listing every item in a collection will be automatically built. These “collection manifests” can be used to give any IIIF viewer the full list of all records in your collection. For example, the Universal Viewer supports direct reading of collection manifests to load every image in a collection.
Collection manifests are also useful for aggregation and bulk processing use cases. You can now point your harvester at the collection manifest and have a way to discover every image record. Because the collection manifest links to the IIIF Presentation manifest for each item, the harvest can crawl each record, read associated metadata, and ultimately retrieve the IIIF Image API link for every image. One way to think about IIIF collection manifests is as analogous to the OAI-PMH concept of a “set”. Additionally, CONTENTdm will now automatically generate a top-level “collection of collections” IIIF manifest which serves as a repository-wide summation of all of your image resources. This collection of collections manifest is roughly analogous to an XML Sitemap as it gives harvesting tools a way to discover every image resource at a given repository URL.
The new repository-wide manifest will appear at a new path at your site URL. For example, on the CONTENTdm Sandbox site the collection of collections manifest can be found here:
The individual collection manifests are linked within that top-level manifest. For example, the Sandbox “Assorted Newspapers” collection manifest will be found here:
These manifests will be updated whenever you change the contents of a collection and build the index to activate your changes.
In addition to these new manifests, we made some other improvements to CONTENTdm’s IIIF functionality:
- All IIIF Presentation manifest for an item now contains links that route back to the parent collection’s manifest.
- Transcripts have been removed from IIIF Presentation manifests because they are not considered “metadata” in the IIIF Presentation API specifications. Including them as metadata sometimes affects the performance of the IIIF functions. We plan to add transcripts as annotations in the future.
- Miscellaneous fixes for issues with syntax, http vs. https in the links, and page-level vs. object-level manifests.
Interest and use of IIIF in CONTENTdm is increasing. We recently published a new recipe to the customization cookbook for integrating the Mirador viewer into your site here. Mirador provides an exceptional viewing and browsing experience, supports side-by-side comparison of multiple images, and is already very popular with early adopters.
Date search within a single collection uses the first field with the data type of “Date”
In Advanced Search, date search within a single collection now strictly uses the first field with the data type of “Date” to ensure seamless searching. The new rule for the Date search is simple and clear: in the fields list from CONTENTdm Administration, the first field of data type “Date” will be used for Date search. To ensure your Date search works and you are searching in the desired field, check your field settings in CONTENTdm Administration > collections > fields, as indicated in the image below:
Note that in the above example, the field “Date aaa” is the first field of type “Date” so this field will be used in Date search when you perform an Advanced Search within this single collection. You should also make sure this field is set to be “searchable” and that the data in the field is formatted correctly.
This original issue only affected a small number of collections if the Date fields were named and modified in a certain way. Previously, CONTENTdm used the field with a nickname of “date” as the field it searched against for Date search. Because the nickname of a collection cannot be changed and is obscure, it caused issues with searching. For normal workflows, if you create a collection using a template, the Date Search works since the Date field is automatically assigned the “date” nickname. However, the Date search can break if you further manipulate the fields.
Please note that multi-collection Date search works differently than single-collection. Multi-collection Date search uses all fields that have the “DC map” field mapped to “Date”. If you want your date field to also work when searched with other collections, you need to make sure its “DC map” field is set to “Date” as well.
Italian and Portuguese have been added as interface languages
Two more interface languages have been added for localization support: Italian and Portuguese. CONTENTdm now supports 15 interface languages, including:
- Simplified Chinese
- Traditional Chinese
You can choose to add them to your website and pick one as your default language in the Website Configuration Tool. Translations of all interface text has not been provided for Italian and Portuguese but you can use the Website Configuration Tool to add it as needed.
Fixes a bug where, when searching, certain compound objects display pages in the incorrect order
This release fixes a bug where, when searching, certain compound objects display pages in the incorrect order. This bug only affected a small number of compound objects. If you used the function in CONTENTdm Administration to manipulate page order for a compound object, the display order of the pages could display differently during browsing vs. searching. Now the page order is correct and displays consistently.
Fixes a bug where certain compound objects display the incorrect page title in the navigation pane
This release fixes a bug where certain compound objects display the incorrect page title in the navigation pane. When you add a compound object through the Project Client, you can assign a structural title (called “page names” in Project Client as shown in screen capture below) for each of its pages, usually “page 1”, “page 2”, etc. The structural titles are only used in the compound object’s navigation pane, and most times they are left the same as the actual title of the page in its metadata, making them undiscernible when searching. Now the structural titles in the navigation pane no longer change to the metadata titles when searching.
Fixes a bug where the grid view title showed as underlined on mouse hover.
This list below shows a few enhancement requests that we consider to be of high priority for upcoming releases, some of which are already implemented or in progress:
- We are changing the way searches are shown in compound objects. A new “Show all pages” view will be added to the navigation window alongside the filtered view that shows only pages containing your search term. This new “Show all pages” view will be the default and users can toggle a button to show the “Filtered pages” view.
- We will fix some inconsistencies with collection scope when users are browsing searching in global pages, collection-level pages, and the advanced search page. This will better support users who are refining an existing search and will generally be more intuitive behavior.
- Providing collection-level grid view/list view default setting in Website Configuration Tool.
- Adding hierarchical IIIF Presentation manifests for monograph compound objects.