Phyllis KaidenProduct Manager, Digital Collection

Services

CONTENTdm 6 OverviewMarch 1, 2011

Agenda

• What’s in CONTENTdm 6• Website• Server• Project Client• Catcher• System Requirements

• Upgrade Options• Website Walkthrough

• New website• New configuration tools• New customization methods• New architecture

• Q & A

Before we begin . . .

Training• CONTENTdm Basic Use Training: Live Web Session – Mar

22Events• CONTENTdm 6 Overview: Live Web Sessions

• March 1, 8:30 – 10 a.m. Pacific• March 2, 12 – 1:30 p.m. Pacific• March 16, 11:30 – 1 p.m. Pacific

Web sessions will be recorded and made available on the User Support Center.

Stay abreast of upcoming training and events through the USC!

http://www.contentdm.org/USC/training/index.php

CONTENTdm 6

Coming in early March 2011End-user interface redesignWebsite configuration toolsCONTENTdm ServerProject ClientCatcher

CONTENTdm 6 Website

Complete redesign of end-user experience• New end-user interface• New configuration tools• New customization methods• New architecture

Fresh approach to end-user experience and customizations requires fresh approach by CONTENTdm users.

Let it be new. Take a new look.

New end-user interface

Goals – CONTENTdm 6 Website

Ensure the new interface supports the end-user1. Provides access to unique digital materials 2. Is intuitive, accessible, and supports end-users in

their research goals3. Is modern and familiar, and meets end-user

expectations4. Is fun, dynamic, and provides opportunity for

discoveryProvide simpler ways to configure and customize1. Easier to apply a branded look and feel 2. Easier to maintain customizations

User-centered design

*97% of end users were able to accomplish their tasks!

Usability Studies* User

Community Input

Security & Performance

Ease of Customization

New Website

Revised End User Experience

CONTENTdm 6 Sandbox

http://sandbox.contentdm.org• Try the new end-user interface using collections

volunteered by users• Supported by a USC forum• Will be updated soon with version 6 release and 11

new collections including audio, video, finding aids, picture cubes, and postcards

• Sandbox will continue to exist for version 6.1

CONTENTdm end-user interface redesign

• Simpler access to your digital materials • An intuitive user interface that supports end-

users in their research goals• Easier navigation path between results, items,

pages within compound objects and collections

• Dynamic interaction with digital materials that provides more opportunity for discovery

Highlighted Features

• Ability to share digital items (via e-mail, bookmark, Facebook, Twitter, Flickr and many more)

• An enhanced image viewer for zooming and panning, and viewing images in full screen

• A compound object viewer that is easier to navigate and understand

• Improved visibility of collections (Home page, collection landing page, breadcrumbs, cross-collection searches, collection list)

• Improved browsing and searching experience that supports research goals (searching within results, Advanced Search that expands in place, results display options)

• Features that support discoverability such as QuickView, image carousels, suggested topics, facets, breadcrumbs and RSS feeds

Search Engine Optimization

• Improved SEO means improved discoverability through search engines such as Google, Yahoo and Bing

• CONTENTdm 6 helps SEO with:• RESTful URLs• Crawlable HTML: no tables, no i-frames• Separates presentation layer from application

layer• Recognizable site hierarchy: breadcrumbs• Efficient crawler path• Title tag at top of page• Javascript in separate file, not on every page

What’s in CONTENTdm 6?

• What’s in CONTENTdm 6?• See the contents list for version 6

• What’s not in CONTENTdm 6?• See the contents list for version 6.1

• CONTENTdm 6 is focused on new users and evaluators or existing users with basic customizations

• CONTENTdm 6.1 is a better choice for users with advanced customizations or specialized viewers

What’s in CONTENTdm 6 Website?

What’s in CONTENTdm 6 Website?

Deprecated or Delayed

CONTENTdm 5 CONTENTdm 6Browse by Date Search by DateImage viewer: double-click to zoom • Zoom using slider bar or keyboard controls

• Double click will mean something else in NewspapersImage viewer: icon for Max Resolution • zoom via slider (couldn’t do this before) and keyboard controlsImage viewer: limit max size of image displayed Maximum zoom increased to 200% but can be throttled in

configuration of allowable zoom.Results: Bibliographic view lost, usability studies indicate not useful to end-usersResults: End-user preferences End-user controls results view, QuickView, number of items per

page, and primary sort. Usability studies showed it was better to keep controls simple and distinct.

Results: End-user specifies secondary and reverse sorts • still works in queries• revisit after 6.1

Results: Facets expanded Facets displayed in accordions and are controlled by end-user. This saves real estate, providing room for Suggested Topics

Results: Hierarchical view replaced by grid with sort and facetsResults: Title view lost, usability studies indicate not useful to end-usersSearch by Proximity lost, usability studies indicate not useful to end-usersSearch: Collection dropdown

• Collection list in sidebar and pop-up• Collection names on Homepage – previously the only way to navigate was via the dropdown• Ability to list collection name in results

Search: Collection list ordered by Server settings • Alphabetical list of collections to help end-users find collections• Revisit ability to specify order after 6.0 release.

Search: Override of default results columns in URL Columns are configured in Website Configuration ToolSearch: Grouping collections (S_CUST_DIR_ALIAS_LIST) delayed to 6.1Search: Show Terms list in Adv Search delayed to 6.1Unpublished collections accessible by all Unpublished collections require user login

New configuration tools

New configuration tools

Provide simpler ways to configure and customize

• Easier to apply a branded look and feel: Configuration tools make it easy to add a name, theme, headers, colors, logos, descriptions and more

• Programming skills are not required to configure your website

• Additional customization is possible: Ability to add custom HTML or PHP pages

• Easier to maintain customizations: Customizations will persist through future updates

Configuration Toolset

Configuration Toolset

Configurations are stored in layout and configuration files (global and by collection). Use OCLC tools to edit.

• Quick Configuration Tool = 3 steps to get started• Quickly creates a simple functional site• Use it once and probably not again

• Website Configuration Tool = ongoing fine tuning• Can do what Quick Config does and more• Configurations grouped into categories• Configurations control appearance and behavior• Configurations will continue to evolve

Quick Config Tool

Get started in 3 steps1. Name and describe your website2. Create a custom header3. Describe your collections

Quick Config sets the basic configurations that were set for Hosted users by OCLC staff in prior versions

Website Configuration Tool

• Replace many of your CONTENTdm 5 customizations with configurations, eliminating the need to carry those programming changes forward.

• Configure your website at the global or collection level, putting control of the public interface into the hands of the collection administrators who know the collection best.

• Save time by setting configurations globally so that they are automatically inherited by the collections. When you have time to configure a collection, you only need to set the configurations that differ from the global settings.

• Preview your website before publishing your changes.• Undo (revert) your saved changes before publishing.• Create a branded look and feel for your website without

programming skills or Web developer resources. • All customizations will persist through future software updates.

Global and Collection settings

• Configuration settings can be global or by collection

• Global settings are inherited by collections• Collection settings override global

Do’s and Don’ts of Website Configuration

• Do use the Quick Config Tool to get started.• Do use the Website Configuration Tool to change

configuration settings.• Don’t use other tools or editors to change

configuration (CSS and config XML) files.• Don’t call Support for help if you edit

configuration files using other tools. The complexity of these files makes manual editing error-prone and, therefore, unsupported.

New customization methods

New customization methods

• Website configuration toolset• Quick Config – get started and then probably won’t

use again• Website Configuration Tool – global or collection

settings• Modular customizations

• Custom pages: Home page, Collection landing pages, About

• Custom scripts: JavaScript at top and/or bottom of pages

• Custom CSS• Deep customizations

Modular Customizations: Custom Pages

• Custom Home Page, Collection Landing Pages, About Page• Website Config Tool: enter name of custom file and

select default or custom layout• Default layout uses configured theme and custom

content• Custom layout uses custom .css and custom content

• Extra pages – add your own custom pages<install

directory>/public_html/ui/custom/default/collection/default/resources

Modular Customizations: Custom Scripts

Move metadata, eCommerce, coolIRIS, Google Analytics, etc.• Custom JavaScript at top <head> and bottom </body> • Any language that will run on your Web server, such as

PHP, Python, Ruby, ASP, ASP.Net (Hosted users have PHP)

• Website Config Tool: Custom ScriptsGlobal:

../cdm/Website/public_html/ui/custom/default/collection/default/jsCollection:

../cdm/Website/public_html/ui/custom/default/collection/coll_alias/js

Custom Scripts - Variables

Hidden fields in the default pages provide variable names to pass data when writing your custom scripts. You can access these variables via JavaScript by using jQuery, as shown in the following example:

var home_url = $(“#collectionHomeUrl”).val();

The following code shows how a field is defined in a page:

<input type="hidden" id="collectionHomeUrl" value="/cdm/" />

Custom Scripts – sample variables of dozens that are pre-defined

Hidden Field Name

Description Default Value

Possible Values

Results Pagescdm_results_page query parameter

for number of results per page

no value by default

/display/xxx (possible values for xxx are from the resultsPerPageOptions config property, which has 20, 50, 100, 200 by default)

cdm_query_total total queries in the current search

Number

cdm_quickview_page

page for QuickView JavaScript to check against config setting for enabling QuickView

Results

Deep Customizations

Viewers, Layouts, Mobile, Hybrids, etc.• Talk to OCLC first. Version 6.1 will be better for

users who need to make extensive or advanced customizations.

• API used in CONTENTdm 5 still exists but is accessed via a new web service on the CONTENTdm Server

• PHP coding. Recommend using Zend.

API

• Server API documentation will be available as on-line Help in version 6.1

• One-to-one correspondence to CDM v5 PHP API calls except for some added calls for v6.  Light Web layer on top of the API. CDM v5 application developers will find it very familiar.  (Many thanks to Simon Fraser and Athabasca universities for sharing the API with OCLC.)

• Before using the API, determine if you can accomplish your goal with configurations or modular customizations.

• Share how you are using the API. Other users may be interested in your extension.

New architecture

New Architecture

All on one box or separate boxes for scalability.

CONTENTdm Website

Goals:1. Customizations

become configurations

2. Ease of configuration – Global, Collection

3. Persistent customizations

4. Easy to switch between custom and standard

Directory Structure

Directory structure - Collections

Architecture - Technology

• Model View Controller architecture• Isolates application logic from user interface

• PHP Version 5.3• General purpose scripting language suited for Web

development

• Zend Framework• Open source framework for developing Web

applications with PHP 5

• New API web service for accessing the CONTENTdm API.

RESTful URLs

The URLs in version 6 are RESTful (REpresentational State Transfer) and look quite different from the query-based URLs of version 5.

RESTful URLs are general; that is, they do not contain references to the underlying technology (e.g., no “.php” or “.asp” or “.htm” appears in any of them, and no “?” or “&” with Web parameters). 

An advantage of having more general URLs is that they are more likely to have a longer lifetime and be more resistant to changes in technology.

Version 5 Compatibility

• Version 5 URLs will continue to function with a few limitations.

• Fields to be displayed in results are configured using the Website Configuration Tool, not passed in via queries.

• Hierarchical, Bibliography and Title views have been deprecated, given end-user feedback that Grid and Thumbnail views provided the information needed, with facets to aid in refining searches.

• Search by Proximity (“near”) has also been deprecated. Custom Queries & Results can still be used to create version 5

queries with limitations noted above. CQR will eventually become part of Website Configuration Tool in order to consolidate all website customization functionality into a single toolset.

CONTENTdm 6

• Project Client• Server• Catcher

CONTENTdm 6 – Project Client

• EXIF/IPTC metadata extraction• Automatic extraction of metadata stored within

images• You map extracted fields to DC or QDC – only tiff or

jpeg• More efficient workflow – you don’t have to manually

re-enter this metadata• Your contributors (faculty, researchers) add

metadata to images using familiar tools such as PhotoShop

• Accurate metadata captured at the source• Backwards compatible with Server 5.x• Your projects remain viable through the

upgrade provided you accept default port numbers during Server installation

CONTENTdm 6 – Project Client

CONTENTdm 6 – Project Client

CONTENTdm 6 - Server

• Separation of the Website from the CONTENTdm Server for improved administration and security

• Supports the new public interface with updates to the Image Library, PHP 5.3 compatibility and separate user permissions for Website customization

Addition of 13 Qualified Dublin Core fields brings CONTENTdm into compliance with latest standard

Collection limit increased to 350 collectionsUpdates for 6 of 10 Controlled Vocabularies: ATT,

CASH, LCTGM, MeSH, TGN and ULAN.• Indexing and Searching updates

• Find search engine fixes for field bleed-over and bad UTF-8 character

Catcher – new with CONTENTdm 6

• Web service for batch editing, addition and deletion of metadata in single items in a CONTENTdm collection

• Utilizes CONTENTdm XML format for data transactions sent to a CONTENTdm Server

• Users supply a script of transactions in a programming language of their choosing to access a Web service available 24x7

• The Reference URL for an item remains unchanged when processed through the Web service

• May be used to submit batch additions of metadata records to a CONTENTdm collection from other repositories

• Designed to complement the Project Client

Catcher Web Service

• Available at no cost to current CONTENTdm licensees

• Intended for the advanced CONTENTdm user

Catcher report

Upgrade Options

Upgrade Path to CONTENTdm 6

•Upgrade path to CONTENTdm 6 Server:• From 3.x or 4.x, upgrade to 5.4• From 5.x, upgrade to 6

•Must be on 5.x to upgrade to 6.•Migration from 4.3 to 6 will not be supported. •Withdrew support for 4.3 on January 31, 2011.

The Project Client will auto-update if you are on 5.2 or higher. For earlier versions, you will need to download the Project Client from the USC.

Should you wait for CONTENTdm 6.1?

• Existing Hosted and Direct users can choose. All new sales and evaluators will automatically receive version 6.

• Consider upgrading to CONTENTdm 6 if• The features in version 6 meet your needs• You are new to CONTENTdm• You have only basic customizations (header, logo, color, email)• You want to get started and have no imminent deadlines

• Consider waiting for CONTENTdm 6.1 if • You need the features that are in 6.1• You have made extensive or advanced customizations• You have imminent deadlines and don’t have time right now

Hosted Users will receive details via email

• To opt in to version 6: contact contentdmsupport@oclc.org before the end of March 2011

• The migrated version 6 Hosted instance will include:• Existing 5.4 web templates continue to function as your

production end-user view• Upgrade to CONTENTdm 6 Server• New CONTENTdm 6 Website will exist at a temporary test

URL• Five basic configurations will be migrated to 6 for you:

Header background color, Header text, Contact Us email address, About description of your website, Logo

• One set of collection data managed by the new CONTENTdm 6 Server – no copying required

• User accounts remain the same

Migration Process – getting to CONTENTdm 6

1. Upgrade to CONTENTdm 5 if you are still on 3 or 4.2. Project Client 6 will auto-update or you can install.

(Backwards compatible with 5.x Server) 3. Decide which path to take: Migration or Install/Cut-over 4. Existing 5.x website still available and functioning.5. Customize your CONTENTdm 6 Website. 6. Switch production website from CONTENTdm 5 to 6

when ready.

Path 1: Migration

Choose Migration if one or more of these conditions are met:

• Insufficient storage space for two copies of CONTENTdm collection data

• Insufficient RAM for two instances of FIND • Prefer to maintain only one set of collection data, shared among

versions 5.x and 6 • With this upgrade path you install CONTENTdm 6

Server and Website and include your version 5.x website in the installation.

• Gain the improvements of CONTENTdm 6 Server immediately.

• Retain your version 5.x website while you prepare your version 6 website.

• Keep a single copy of all your collections. • Keep running on your current server.

After Migrating and Before Switching

After Switching to CONTENTdm 6 Website

Path 2: Install/Cut-over

Choose Install/Cut-over if one or more of these conditions are met:

• Parallel CONTENTdm 5.x and 6 instances, with a copy of the data in each and sufficient RAM to run two instances of Find

• Customizations made to version 5.x files outside of the /cdm4 directories and you need access to those customizations while you prepare your version 6 website

• With this upgrade path you install CONTENTdm 6 Server and Website on a separate server, and make a copy of your existing collections to the new server.

• You can run both 5.x and 6 simultaneously for up to 90 days before cutting over to CONTENTdm 6 and disabling your CONTENTdm 5.x.

Install/Cut-over

New Machine: version 6

Existing Machine: version 5

CONTENTdm Calendar

• Version 6 release – early March 2011• OAI update – Spring 2011• Version 6.1 release – Summer 2011

Q & A

Website Walkthrough

• New public interface for end-users• Configuration tools for collection

administrator• Quick Configuration Tool to get started• Website Configuration Tool to fine tune

Past, Present, Future – Content, for the User

•As your digital library programs have grown, so have your needs for tools.•As your users’ expectations have grown, so have their needs for an effective experience.•As user experiences evolve, so will CONTENTdm.

• Phyllis Kaiden• CONTENTdm Product Manager• kaidenp@oclc.org

Thank you!