Penn State University Presentation

DAMSDAMS

James Hilton,Provost’s Office

John Williams, Louis E. King, Al McCord,Digital Media Commons, Duderstadt Center

Penn State University July 14, 2004

Digital Asset Management SystemsUniversity of Michigan

Agenda - Morning

Time Item By

08:30-09:00 Light Breakfast at Duderstadt Center, Suite 1180 All

09:00-09:30 Introductions James

09:30-10:00 Context Al

10:00-11:00 Demonstration Louis

11:00-11:30 Business break All

11:30-12:00 DAMS Living Lab defined John

12:00-12:30 Working lunch served All

Agenda - Afternoon

Time Item By

12:30-01:00 Solution Overview John

01:00-02:00 Lessons Learned Louis

02:00-02:15 Break All

02:15-03:00 Discussion All

03:00-03:30 Year 2 and beyond John

03:30-04:00 Wrap up John

DAMSDAMSIntroductions

http://sitemaker.umich.edu/dams

DAMSDAMSContext

??Why DAMS Is Important

• We are challenged to acquire, index, access, use, and archive “perishable intellectual property” for• Course delivery (on-campus and DL)• Archives and collections• Research projects• External communications (Web, Broadcast, and print)

??Why DAMS Is Important

• Our networks can support digital video payloads• Students use P2P to manage their personal media assets

• Many isolated repositories on our campuses• Institutional file systems• Library collections• Course management systems• Web content management systems

• BUT• Rich media still absent from most instruction• Lack of large-scale rich media services• Faculty and librarians lack experience / tools for managing rich media• Lack of rich media workflow tools• Lack of tools to manage IP rights

Internalization

Institutionalization

Adoption

Trial Use

Understanding

Awareness

Contact

2000 2001 2002 2003 2004 2005 2006 2007 2008

Case in Technology Adoption

Adoption

Commitment

How This Got Started

• Contact (May 2000)• Via UM Television and Informix

• Awareness• Internal dialogs, demonstrations• Executive interest

AhaAhaHow This Got Started

• Understanding (April 2001)• CNN visit (the “Aha!” moment)• Executive interest and commitment

How This Got Started

• Early demonstration (Dec 2001)

• Informix / Media360 / Virage

• Campus Interest Group

• Opt-in community

• RFP (May 2002)

• Decision (April 2003)

• DAMS Initiative (Jul 2003)

• Provost/Unit funding

• Digital Media Commons “Living Lab”

What We’ve Assumed

• IT Commons approach• Campus-wide collaboration

• Federal / community / neighborhood approach

• Two-year experimentation and adoption window to create demand-pull shared services

• Open standards

• Campus metadata standards

• Infrastructure tools for ingestion, cataloging, and retrieval

• Bandwidth and storage to be addressed

The Trial Use Environment

• Context of “IT Commons”• Collaborative model

• “Demand pull” versus “provider push”

• Cross-unit dialog and discussion• Opportunities

• “Buy versus build” dialog

• Executive support• RFP for integrated COTS solution

• Location for trial use (“DAMS Living Lab”)

• Experimental support for units

• Firm commitment to experimental model

DAMSDAMSDAMS Demonstration

DAMSDAMSDAMS Living Lab – Defined

Explore an infrastructure that will lower the barriers preventing us from using time-based media in a manner

similar to our use of text and images today!

DAMS Living Lab

• Ingest, manage, store and publish digital rich-media assets and their associated metadata.

• Streamline the “workflow” required to create new works with digital rich-media assets.

• Search, share, edited and repurpose assets in the academic model.

• Prepare for future application of campus-wide rights and intellectual property management to existing assets.

Sourcing Considerations

• DAMS as a vehicle to consolidate:• Transcoding and derivative technology• Metadata analysis, search and management• Integrate with our storage strategy• Investigate Search tools integration• Authentication and access control tools

• Internal Development vs. Commercial off-the-shelf?

• Campus-wide selection team/RFP process

• Living Lab as a development platform and a policy tool

Living Lab

Goals

• Proof of concept leading to a rigorous specification for theselected software hardware solution

• Campus “sandbox” for experimentation with academic applications

• Campus-wide participation = community readiness

• Advantage of non-committed state (to campus and vendors)

Structure

• Hardware and software donated by vendors, integration consulting fee ($210K)

• UM “thin-staffing” = 1.25 FTE support core and Affiliates

• Affiliate-led projects constitute proof of concept

• Affiliates participate in Living Lab support ($20K/yr. typical)

Production, Publications, Broadcast Content

Collaborative Research

Archived Collections

Casual Learning & Exploration

Course Materials

Digita

l Lib

rarie

s

Depar

tmen

tal S

tora

ge

Team

Work

spac

e/Sto

rage

Content M

gmt.

Syste

ms

Perso

nal S

hare-

fold

ers

Product

ion S

yste

ms

Inst

itutio

nal R

eposi

torie

s

Collaborative Learning

Ty

pe

s o

f C

oll

ab

ora

tio

nT

yp

es

of

Co

lla

bo

rati

on

Ad-hoc Sharing

ePortfolios

Course

Mgm

t. Sys

tem

s

Individual Content Owners Institution

Individual Browsing

Research

Portal Development & Content

What Space Does DAMS Occupy?

• Create an end-to-end digital asset management system as the “Living Lab” – a working demonstration environment

• Identify areas for collaborative research projects around subjects such as digital rights, open standards, and learning technologies.

• Support pilot projects

• Co-create a marketing and communications program to promote the Lab’s efforts across campus, the higher education community

IBM, Stellent, and U of M Partnership

Academic Projects

• Participation by Academic Units (Assessing demand on campus)• LS&A – History of Art, Psychology, English• Business• Dentistry• Pharmacy, Information, Music, News

• Faculty focused

• Affiliate Supported

• Digital Media Commons• Stewardship• Campus Partners – ITCS, ITComm, News Services

Living Lab Goals

• Understand compelling academic outcomes

• Evaluate IBM/Stellent solution

• Specify DAMS application, service layer, and technical architecture

• Build community readiness

DAMSDAMSSolution Overview

EncodeEncodeEncodeEncode

TranscodeTranscodeTranscodeTranscode

MetatagMetatagMetatagMetatag

ProxiesProxiesProxiesProxies

EncryptEncryptEncryptEncrypt

StoreStoreStoreStore

TrafficTrafficTrafficTraffic

File ServeFile ServeFile ServeFile Serve

StreamingStreamingStreamingStreaming

BroadcastBroadcastBroadcastBroadcast

Web Pub.Web Pub.Web Pub.Web Pub.

PrintingPrintingPrintingPrinting

CD/DVDCD/DVDCD/DVDCD/DVD

ViewViewViewView

MetadataMetadataMetadataMetadata

AccessAccessAccessAccess

WorkflowWorkflowWorkflowWorkflow

VersionVersionVersionVersion

Check in/outCheck in/outCheck in/outCheck in/out

DRMDRMDRMDRM

Enterprise Enterprise DataData

Enterprise Enterprise DataData

UnitUnitUnitUnit UnitUnitUnitUnit UnitUnitUnitUnit UnitUnitUnitUnit UnitUnitUnitUnit UnitUnitUnitUnit

Near-lineNear-lineNear-lineNear-line Near-lineNear-lineNear-lineNear-line Near-lineNear-lineNear-lineNear-line Near-lineNear-lineNear-lineNear-lineOfflineOfflineOfflineOffline OfflineOfflineOfflineOffline OfflineOfflineOfflineOffline

AuthoringAuthoringStationsStations

AuthoringAuthoringStationsStations

MediaMediaAppliancesAppliances

MediaMediaAppliancesAppliances

Remote Remote UsersUsers

Remote Remote UsersUsers

Campus Campus UsersUsers

Campus Campus UsersUsers

StudiosStudiosStudiosStudios

Producers

Collaborators

Audience

Ingest

Store

PublishManage

CampusCampusBroadcastBroadcastCampusCampus

BroadcastBroadcastPrintPrint

PublishingPublishingPrintPrint

PublishingPublishing

SecureSecureWebWeb

SecureSecureWebWeb

PublicPublicWebWeb

PublicPublicWebWeb

CampusCampusServicesServicesCampusCampusServicesServices

CourseCourseManagementManagement

CourseCourseManagementManagement

DAMS Component Services

Applications, Course Management Systems, Production Systems

DAMS

Institutional and Individual Assets

Network

Storage

Publishing: Teaching, Collaboration, Production, Distribution, Broadcast

Authentication & Authorization

DAMS Service Layer

Solution Architecture

Local source:• Tape Deck• Live Media Stream• Scanner• Existing Digital File

Remote Source:• Telestream ClipMail Pro• FTP upload of existing digital file

Library ServerLibrary Server

Resource ManagerResource Manager

Ancept Media ServerMetadata creation

Version controlCheck-in/out

WorkflowXML

Websphere TivoliStorage Management

Asset ProcessingAsset Processing

Streaming ServersIBM VideoChargerApple QuickTime

1 TB storage

Telestream FlipfactoryTranscoding

Metadata ExtractionProxy Creation

VirageEncoding & LoggingMetadata Extraction

Speech-to-textVoice, face recognition

Remote iSCSI Storage


1TB

DB2SMART

Self-Management And Resource Tuning

IBM Content ManagerMetadata Mngmnt.

Resource ManagementSecurity

Cosign single sign-on

DAMS Living Lab Software Configuration






TranscodeIBM x345 dual 2.67GHz Xeon, 1.5 GB DDR

Telestream FlipFactory440 GB Ultra 320 (10K rpm) SCSI Raid 5i

Windows 2000 Server

Encode and LogIBM x345 dual 2.67GHz Xeon, 1.5GB DDR

146 GB Ultra 320 (10K rpm)Osprey 560 Video Capture Card

Video Logger (Virage)Windows 2000 Server

Video StreamingIBM x345 dual 2.67GHz Xeon, 1.5 GB DDR

146 GB Ultra 320 (10K rpm)QuickTime ServerIBM Video Charger

Windows 2000 Server

Device attached storage1 TB - IBM Ultra 160 (10K rpm)

Content Manager 8.0 (DB2, Tivoli, Websphere)

Ancept Media Server

IBM P645 2-way 1.2GHZ, PWR4+, 8GB293 GB SCSI U3 (15K rpm)

AIX 5.1

DAMS Living Lab Hardware Configuration



1TB

IBM Ultra 160 (10K rpm)








1TB



Windows 2000 Server






Windows 2000 Server




Ancept Media Server


AIX 5.1

SMBSMBSMBSMB

SAMBASAMBASAMBASAMBA

CosignCosignCosignCosign

ITCommITCommITCommITComm

DAMS Living Lab UMCE Integration

DAMSDAMSLessons Learned

Neighborhood CentralLocal

Lessons Learned - Architecture

LiveTape/CD/DVDInternet Appliance

Satellite

Video LoggerFlip Factory

(Optional)

AMS 3.5Content ManagerDB2

Spinning Disk Spinning DiskNearline/OfflineBackupTivoli

PrintWebCD/DVD

Media StreamingReal/Win/QT

Course MgmtePorfoliosPersonal Storage

Capture

Ingest

Manage

Store

Publish

X

X

X

X



Library Server

Resource Manager

Asset Processing


1TB



Windows 2000 Server






Windows 2000 Server




Ancept Media Server


AIX 5.1

Lessons Learned - Workflow

XX

Neighborhood

Lessons Learned - Managing Access Control Lists

In the commercial sectorasset privileges correspond to

corporate hierarchy!

Easily managed centrally through system defined ACLs

In higher educationasset privileges are unrelated to the

institutional hierarchy!

Requires distributed management through User Defined ACLs

De

cis

ion

Ma

kin

gD

ec

isio

n M

ak

ing

+

-

.

Rights Holders

System Admins

Affiliates

Collaborators

Viewers

Guests

Board of DirectorsExecutive StaffAdministratorsCustomers - Level 1Customers - Level 2Customers - Special

RegentsExecutive StaffFacultyStudentsStaffFriends/Affiliates

Privileges

CorporateHierarchy

Privileges

InstitutionalHierarchy

Rights Holders

System Admins

Affiliates

Collaborators

Viewers

Guests

Rights Holders / Creators

Licensees

Administrators

Collaborators

Groups

Open Access

Lessons Learned - More Access Control Lists Needed

In the commercial sector, access to media is defined and

controlled centrallyDozens of Access Control Lists

In higher education, access to media is defined and

controlled by end users.100,000+ Access Control Lists

Board of Directors

Executive Staff

Administrators

Customers - Level 1

Customers - Level 2

Customers - Special

Lessons Learned - Metadata

• UM Core = Dublin Core + UM Special

• Provide structured metadata but allow users to map into fields in unstructured ways (contrary to controlled taxonomies of our libraries)

• Allow for multiple metadata schemas to be attached to a single asset (ie Dublin Core, IMS, SCORM, etc.)

Lessons Learned - Interface

• Indicators of privileges

• Grayed menu items

• User defined ACLs

• Open source application Assets Show PrivilegesAssets Show Privileges

Gray Menu ItemsGray Menu Items

Lessons Learned - Policy

• Rights DeclarationCopyright issues must be addressed in a systemic way – to start, UMCore metadata schema can support a rights declaration

• Digital Rights ManagementThe largest early us of DRM is for distribution of licensed materials. Need to evaluate products that allow keys to be set to control access and expire media after its intended period of use.

• Statutory ComplianceManaging regulatory issues such as FERPA (Family Educational Rights and Education Act) and HIPAA (Health Insurance Portability and Accountability Act) must be built in.

• User Education & Use PolicyEducation, training, and support on metadata and file quality will help distribute the work load and maximize the ability to share materials and ensure appropriate use

Near Loomings

• User Defined ACLs

• Interface development for UD-ACLs

• Clip-making functionality

• Enterprise environment pilot w/ neighborhood(s)

• IP, Copyright, Privacy, Use and Misuse policy

• Building a great user experience

Far Loomings

• Ongoing interface design to meet project and user requirements(Taking into consideration asset management’s inherently different approach of presenting multiple items, each of which may have a different set of user capabilities associated with it)

• Integration with other academic tools (Sakai) or portal

• Relationship to Library, Institutional Repository and federatedcatalogue searching

Bloomings

• Possible partnership w/ IBM to build a JSR168 compliant DAMS interface to IBMs Content Manager Middleware

• Leverage extensibility, massive computational power and scheduling of M-Grid to weave together the DAMS service layer – i.e. distributed neighborhoods of media transcoding, analysis, storage, and streaming.

UM DAMS Contacts

University of Michigan DAMS Initiativehttp://sitemaker.umich.edu/dams/

James Hilton [email protected]

Associate Provost for Academic, Information and Instructional Technology Affairs

Louis E. King [email protected]

Managing Producer, Digital Asset Management Systems

Alan McCord, Ph.D [email protected]

Vendor and Institutional Relationships

John Merlin Williams [email protected]

Executive Producer, Digital Media Commons

http://sitemaker.umich.edu/dams/

mailto:[email protected]




Penn State University Presentation

Documents

dams demonstration dams

john dams

context dams

introductions dams

trial use dams

dams initiative

living lab support

digital richmedia assets