Phyllis Kaiden Product Manager, Digital Collection Services

1. CONTENTdm 6 Overview March 1, 2011 Phyllis Kaiden Product Manager, Digital Collection Services

2. 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

3. Before we begin . . . • Training • CONTENTdm Basic Use Training: Live Web Session – Mar 22 • Events • 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

4. CONTENTdm 6 • Coming in early March 2011 • End-user interface redesign • Website configuration tools • CONTENTdm Server • Project Client • Catcher

5. 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.

6. New end-user interface

7. Goals – CONTENTdm 6 Website Ensure the new interface supports the end-user • Provides access to unique digital materials • Is intuitive, accessible, and supports end-users in their research goals • Is modern and familiar, and meets end-user expectations • Is fun, dynamic, and provides opportunity for discovery • Provide simpler ways to configure and customize • Easier to apply a branded look and feel • Easier to maintain customizations

8. User-centered design *97% of end users were able to accomplish their tasks!

9. Revised End User Experience

10. 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

11. 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

12. 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

13. 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

14. 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

15. What’s in CONTENTdm 6 Website?

16. What’s in CONTENTdm 6 Website?

17. Deprecated or Delayed

18. New configuration tools

19. 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

20. Configuration Toolset

21. 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

22. Quick Config Tool Get started in 3 steps • Name and describe your website • Create a custom header • Describe your collections Quick Config sets the basic configurations that were set for Hosted users by OCLC staff in prior versions

23. 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.

24. Global and Collection settings • Configuration settings can be global or by collection • Global settings are inherited by collections • Collection settings override global

25. 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.

26. New customization methods

27. 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

28. 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

29. 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 Scripts Global: ../cdm/Website/public_html/ui/custom/default/collection/default/js Collection: ../cdm/Website/public_html/ui/custom/default/collection/coll_alias/js

30. 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: varhome_url = $(“#collectionHomeUrl”).val(); The following code shows how a field is defined in a page: <input type="hidden" id="collectionHomeUrl" value="/cdm/" />

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

32. 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.

33. 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.

34. New architecture

35. New Architecture All on one box or separate boxes for scalability.

36. CONTENTdm Website • Goals: • Customizations become configurations • Ease of configuration – Global, Collection • Persistent customizations • Easy to switch between custom and standard

37. Directory Structure

38. Directory structure - Collections

39. 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.

40. 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.

41. 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.

42. CONTENTdm 6 • Project Client • Server • Catcher

43. 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

44. CONTENTdm 6 – Project Client

45. CONTENTdm 6 – Project Client

46. 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 collections • Updates 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

47. 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

48. Catcher Web Service • Available at no cost to current CONTENTdm licensees • Intended for the advanced CONTENTdm user

49. Catcher report

50. Upgrade Options