Phyllis Kaiden. Product Manager, Digital Collection Services. Project Client Server Catcher Website: End-User Experience Redesign

Transcription

1 2010 Upper Midwest User Group 11/8/2010 CONTENTdm Update Phyllis Kaiden Product Manager, Digital Collection Services Agenda What s Coming CONTENTdm 6 Project Client Server Catcher Website: End-User Experience Redesign Q & A Sandbox Demo of new Public Interface Demo of Quick Config tool Demo of Website Configuration tool Migration Beta status 1

2 Upcoming Training and Events Training CONTENTdm Basic Use Training: Live Web Session Nov 9 User Groups Upper Midwest User Group Nov 8-9 Southwest User Group Dec 2-3 ALA Midwinter User Group Jan 10 Stay abreast of upcoming training and events through the USC! USC Forums Stay informed! Participate! 2

3 CONTENTdm 6 Sandbox Sandbox lets you follow progress of CONTENTdm 6 Try the new website interface and give us feedback Sandbox is supported by a USC forum What s in the Sandbox now? Sandbox Alpha: Testing with real data your data! Single images only What s next in the Sandbox? Any day now: Images with text, single PDF Late November: Compound Objects (monograph, document) December: Update with more functionality as ready CONTENTdm Calendar July 2010 CONTENTdm 5.4 released August 2010 Flex Loader released CONTENTdm 6 Nov 2010 Catcher Pilot starts 11/9 Nov Dec 2010 Website Migration Beta started 11/3 Sandbox Update (text, PDF) November Sandbox Update (compound objects) - December Early 2011 General Release, includes Project Client, Server, Website, and Catcher 3

4 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. Withdrawing support for 4.3 when 6 releases in early The Project Client will auto-update if you are on 5.2 or higher. For earlier versions, you will need to download Project Client from the USC. CONTENTdm 6 Project Client EXIF/IPTC metadata extraction Automatic extraction of metadata stored within images You map extracted fields to DC or QDC 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 t captured at the source Bug Fixes 4

5 CONTENTdm 6 - Server Indexing and Searching updates Find search engine fixes for field bleed-over and bad UTF- 8 character Addition of 13 Qualified Dublin Core fields Brings CONTENTdm into compliance with latest standard Support for new website (public interface) PHP 5.3 Image Library User permissions for customizing website Separation of Website from CONTENTdm Server Bug Fixes Catcher new with CONTENTdm 6 Web service for batch editing, addition and deletion of CONTENTdm data 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 The RefURL for an item remains unchanged when processed through the Web service Initial release supports requests to edit, add or delete metadata in single items Available at no cost to current CONTENTdm licensees Intended for the advanced CONTENTdm user 5

6 Catcher Benefits 1. Manage your collection metadata while maintaining the existing RefURLs 2. Submit batch edits to your collection metadata fields 3. Submit batch additions of metadata records to your collection from other repositories 4. Utilize an unattended scripting process and access a web service available 24x7 5. Write scripts in your preferred language; sample scripts provided in Java and C#.NET but any language that handles XML will probably work CONTENTdm 6 Website How different is CONTENTdm 6? VERY! New architecture New user interface New customization methods New configuration tools Fresh approach to end-user experience and customizations requires fresh approach by CONTENTdm users. Let it be new. Take a new look. 6

7 Goals CONTENTdm 6 Website Ensure the new interface supports the end-user 1. Provides access to unique digital materials 2. Is intuitive, accessible, and supports end-users in their research goals 3. Is modern and familiar, and meets end-user expectations 4. Is fun, dynamic, and provides opportunity for discovery Provide simpler ways to configure and customize 1. Easier to apply a branded look & feel 2. Easier to maintain customizations Some CONTENTdm 6 Website features 1. Configuration at global or collection level 2. Enhanced image viewer: zooming, panning 3. Easier access to features that support research-oriented goals: refining, downloading, printing, sharing 4. QuickView to keep users focused on their research 5. Community features: tagging, commenting, rating 6. More intuitive for a first time user to find what they need 7. Search all, some or one collection. 8. Breadcrumbs and other features provide context to end-user. 7

8 Demo of CONTENTdm 6 Website New public interface for end-users Configuration tools for collection administrator Quick Configuration Tool to get started Website Configuration Tool to fine tune 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15

16 16

17 17

18 Migration Process getting to CONTENTdm 6 1. Upgrade to CONTENTdm 5 if you are still on 3 or Install CONTENTdm 6 using Installation Guide. Installs Server and creates Website. Project Client will auto-update t or you can install. 3. Existing 5.x web templates still available and functioning. 4. Customize your CONTENTdm 6 Website. OCLC provides Getting Started Guide. Quick Configuration Tool no programming needed Website Configuration Tool no programming needed Modular Customizations custom Javascript lets you alter appearance and behavior of all or selected page types. Deep Customizations if needed custom programming. Should be the exception. 5. Switch production website from CONTENTdm 5 to 6 when ready. Architecture Overview 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 18

19 CONTENTdm 6 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 19

20 Optimized for Customization Application is configured by changes to.css and config (XML) files Configuration utility manages the changes through an admin UI Editing PHP not required Additional customizations can be done by editing CSS, using API or adding custom modules Both configurations and customizations will persist across updates Migration Beta in progress Beta program Nov 3 Dec 10 is testing installation, customization, and update. Many thanks to our 17 beta program participants! Institutions Server Type State Library of NC Hosted Govt Lehigh University 5.4 on CentOS 5 Academic South Central Regional Library Council Hosted Consortium Louisiana Library Network Hosted Consortium University of Houston Hosted Dev Academic Pepperdine University Hosted Academic U.S. Fish & Wildlife Services 5.1 on Win 2003 Govt University of Leicester Hosted Academic Morristown & Morris Township Pub Lib Hosted Public Southeastern NY Lib Resources Council 5.4 on Ubuntu 10 Consortium University of Nebraska Lincoln on RedHat 5.5 Academic OCLC Library Hosted OCLC CAMIO Hosted OCLC Customer Support Department on Linux OCLC Customer Support Department on Windows OCLC Training Hosted OCLC Technical Support on Linux OCLC 20

21 How can you participate? Visit the Sandbox and provide feedback in the forum Volunteer your collection for inclusion in the Sandbox Unrestricted No copyright constraints Metadata less than 1 GB Good match for functionality in Sandbox Early 2011 CONTENTdm 6 Release CONTENTdm Calendar July 2010 CONTENTdm 5.4 released August 2010 Flex Loader released CONTENTdm 6 Nov 2010 Catcher Pilot starts 11/9 Nov Dec 2010 Website Migration Beta started 11/3 Sandbox Update (text, PDF) November Sandbox Update (compound objects) - December Early 2011 General Release, includes Project Client, Server, Website, and Catcher 21

22 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 s user experiences e evolve, so will CONTENTdm. Thank you! Phyllis Kaiden CONTENTdm Product Manager kaidenp@oclc.org 22