BIG PICTURE STRATEGY

CLEVELAND MUSEUM OF ART

Jane Alexander, Chief Information OfficerAndrea Bour, Collection Information Data AnalystJeanne DeBonis, Web DeveloperNiki Krause, Application Services Manager

IMTS Applications TeamWill, Andrea, Linda, Niki, Jeanne

GALLERY ONE + ARTLENSinteractives test-bed

GALLERY ONE• 1st ‘beneficiary’ of digital strategy• 78 works of important art• 6 thematic lenses• 3 dynamic interactives:

– Collection Wall(40’ long, 125 microtiles, 4000+ works)

– Matching & Sorting game (2 stations)– Beacon (favorites, stats, visitor experiences)

10

12

13

15

16

ARTLENS• 55 works interpreted from Gallery One• 150+ interpreted works in collection galleries• 800+ videos & narrated slideshows• 700+ text & image offerings• 25 predefined tours• wayfinding via 175+ APs• 9,200 downloads to date• 1,000+ visitor tours created

NO ONE-OFFS!

A FEW OF THE MANY…• integrated CCMS• DAM upgrade• archival repository• open-source website• mobile site• central table

OTHER PROJECTSall intertwined

search

view

editupload

connect

plan

collaborate

CCMS

WEBSITE• open source

• extensible and extremely

customizable

• rapid application development

• sophisticated theming layer

• intuitive interface

• in-house expertise

• highly-engaged developer

community

• active use and development in

museum, library, and non-profit

community

better and faster search and faceting

ease of theming & design

streamlined mobile site

LIBRARY INTEGRATION

linking art citations + donors

DAM UPGRADE

ARCHIVAL REPOSITORY

records in the cloud

CENTRAL TABLE

CCMSbuilding a core system

SEARCH • EDIT • APPROVE

UPLOAD : Document Management

CONNECT : WorldCat

CONNECT : Getty and VIAF

PLAN : Exhibitions • Service

COLLABORATE

Product Description• built on open technologies of Microsoft SharePoint Server, Microsoft SQL Server and .Net

• built with Collaboration as a primary goalo employs SharePoint embedded features and custom workflows for sharing information with

internal colleagues

o institutional based premise for sharing information between museums

o community based premise for publishing information to the world

• cloud-ready to support a community of museum catalogers and professionals from multiple institutions regardless of size

• built using the latest frameworks and design patterns including SOA (Service oriented architecture) and MVVM (Model-View-View-Model)

• designed to be agile and adaptable to multiple platforms; iOS, Android, Surface

• designed to scale from a few users to tens of thousands of users

• designed to be adaptable to specific museum by allowing theming and branding according to preference

PICTION DAMevolving

PICTION DAM UPGRADE• Piction 7 application upgrade• flattened legacy record structure (1:1)• expanded staff-requested tools

– export PPT and Excel– contact sheets– batch downloads

• integrated with CCMS• turbocharged downstream use

A Basic DAM

An Awesome DAM

ARCHIVAL REPOSITORYOAIS + cloud computing

ARCHIVAL STORAGEdigital assets

(original + normalized)

DATA MANAGEMENTmetadata

(descriptive, technical, preservation)

INGEST ACCESS

Preservation Planning

Administration

OAIS

MANAGEMENT SOFTWARE• IMTS preference for open source• options reviewed:

– DSpace (piloted and chosen)– Fedora Commons (piloted)– Archivematica– ContentDM

• custom loaders, search interface

• sustainability concerns• in-house server/storage• hosted/SaaS solutions• cloud-based server/storage

– full access to server & management software– top-flight local provider– same ISP backbone– out-of-region redundancy

PLATFORM

CUSTOM LOADER

ISSUES• mapping by collection group• custom CMA schema added

to DCMI, IPTC metadata• original + normalized archival file format

– TIFF– PDF-A

• preserving Photo Studio edits to images• automation of workflow steps

WEBSITEmigration and innovation

GOALS OF MIGRATION TO DRUPAL CMS• staff intranet

– ease of use– true content management by and for staff– ability to search documents, show news and alerts

• museum website– consolidation of Sitecore website and Wordpress blog– understandable content and categorization– massive migration of data (>65,000 pages)

• library website– migration from LAMP site, opacs, and Wordpress

STAFF INTRANET (before Drupal)

STAFF INTRANET CONVERSION• The easy part: implementation

– installation

– customization of content

– theming

• The challenge: training/retraining staff

– content management means extra work (despite ease of use)

– gatekeeper strategy requires single content manager per

department

– daily updates on intranet replace “all staff” emails

STAFF INTRANET(with Drupal)

PUBLIC WEBSITE CONVERSION• Save money with open source

– software cost– license fees– developer fees– training fees

• Legacy system (Sitecore CMS) disadvantages– non-standard implementation, heavy customization– out of house development and updates– search engine issues: limited SEO and lack of Google image indexing– problematic social sharing– unintuitive admin interface with buggy plug-ins and limited browser

support

PUBLIC WEBSITE CONVERSION

• in-house expertise

• rapid application development

• intuitive admin interface for content managers

• sophisticated theme layer separate from content

• highly-engaged developer community

• active use and development in museum, library, and

non-profit community

WEBSITE MIGRATION SCOPE• Time Challenges: July-December 2012

– hire third-party developers for decision making and complex migration– “redesign”– build– migrate– launch

• “Redesign” Challenges: branded site• Migration Challenges

– export >65K pages from relatively-unstructured database (“blobs”)– decide how to handle user data and customizations

• Special Challenges– integrate with Piction DAM (weekly refresh of ~60K objects’ metadata and images)– feed daily events to ArtLens (iPad application)

GOALS OF SITE DESIGN & “REDESIGN”

• fix things that were “broken”

– Facilitate SEO

– Reinstate images to Google index

– Make social sharing work properly

• follow already-established branding guidelines

– Maintain menu and landing page layout

– Keep general page look (banner, text, navigation)

• update layout and functionality where possible

• incorporate responsive design

Homepage

Landing Pages (Rendered Menus)

CONTENT PAGESupdated for usability

• Remove menu overlay• Add peer content in left menu• Move related content to top

of left menu• Reinstate browser “back”

button functionality

COLLECTION ONLINEsearch layout and functionality

• Installed Apache SOLR search for speed

• Added facets to search navigation

• Added hover info for objects

COLLECTION ONLINEobject pages

• Layout and functionality updated for usability

• Meta data displayed in pocketed sections NEXT to main image

• Thumbnail carousel for slide-show functionality

MOBILE SITE CHANGES• Make entire site available on mobile platform

• Maintain as much imagery as possible

(Pentagram design guideline)

• Work within user expectations for mobile site

(menu dropdowns, single-column layout and

“button” lists)

RESPONSIVE DESIGN VS. MOBILE SITE

MOBILE SITE IMPLEMENTATION• responsive design abandoned below tablet level

• separate theme for mobile

• templates, CSS, and Javascript

• swipe and scroll functionality for image menus and slideshows

• install server-side switching using Apache Mobile Filter for platform

detection and domain assignment

• create mobile site domain: m.clevelandart.org

• use Domain Access module in Drupal to handle theme assignment

based on domain served

DIGITAL STRATEGYlooking at the big picture

OBJECTIVES• activate the collection• connect art and audience through active experience• promote new scholarship• support research• facilitate internal and external collaboration• drive attendance• increase revenue• streamline work

DIGITAL STRATEGYenjoying the big picture