Digital Asset Management Forum Chicago 2011
•Télécharger en tant que PPTX, PDF•
7 j'aime•3,021 vues
This document outlines best practices for implementing a digital asset management (DAM) system. It discusses identifying stakeholders, taking inventory of existing assets and systems, making a business case, documenting workflows, evaluating DAM solutions, implementing a system, configuring metadata schemas and folders, ingesting and managing assets, searching, downloading, processing assets, and maintaining the DAM system over time through software updates, backups, and support. The overall goal is to provide guidance on setting up an effective DAM system to better locate, access, reuse and manage digital assets.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (7)
Similaire à Digital Asset Management Forum Chicago 2011
Similaire à Digital Asset Management Forum Chicago 2011 (20)
Plus de Extensis
Plus de Extensis (20)
Dernier
Dernier (20)
Digital Asset Management Forum Chicago 2011
- 1. Digital Asset Management Best Practicesdamlearningcenter.com/chicago2011 Edward Smith Product Marketing Manager, Extensis @DAMGeek
- 2. The Need for DAM Locating assets Understanding what assets are available Providing access to the “correct” assets Providing access to the “correct” format/size Reusing assets Recreating assets Inconsistent use Usage and rights 1
- 3. Presentation Outline Initiating your DAM Project Evaluating Solutions Implementing DAM Daily use of DAM Maintenance 2
- 5. Create a project team
- 6. Involve your IT department
- 7. Obtain director/executive level support3
- 10. Number
- 16. Making a Business Case for DAM How does DAM support organizational goals/mission? Quantify the current pain points Does the cost justify the outcome? (ROI) 5
- 17. ROI Tool Handout Page #1 6
- 19. What formats do they need?What is the folder hierarchy convention (if any)? What is the file naming convention (if any)? 7
- 20. Document Current Workflow Prior to evaluating DAM systems, document use casescenarios that describe how people currently work today, and how they would work in an ideal DAM system in the future. 8
- 21. Document Current Workflow Present Day Scenario Images are frequently requested by staff for use within PowerPoint presentations or for print and web use. The person maintaining the image collection fulfills image requests by browsing through folders on several different file servers. Once an appropriate image is located, a spreadsheet is cross referenced for usage rights. If the image does not meet the desired usage, the search continues. Once an appropriate set of images are selected, each image is opened in Photoshop and resaved in the correct format and resolution. The images are then uploaded to an FTP server and download instructions are emailed to the requesting staff member. 9
- 22. Document Current Workflow Ideal Scenario Images added to file server folders are automatically ingested by the DAM system. The collection maintainer adds search keywords and usage rights information to images in the DAM system using drop-down menus. A secure web portal allows staff to search items from the image collection using keywords and other automatically applied information such as “Date Created”. The web portal only displays search results for items that have an “approved” metadata value. Important information such as usage rights appear next to search results. Staff can download and convert images on the fly into low, medium, and high resolution formats. 10
- 23. Presentation Outline Initiating your DAM Project Evaluating Solutions Implementing DAM Daily use of DAM Maintenance 11
- 25. What problems are the most important?
- 26. What problems can be solved later (phase 2)?12
- 28. Location
- 30. Distributed onsite (multiple locations)
- 32. Licensing
- 33. Per server
- 34. Per named user
- 35. Per connection
- 36. Subscription
- 37. Scalability13
- 39. Sample assets
- 40. Metadata schema
- 41. Folder structure example14
- 45. How long have they been in business?
- 46. What other organizations like yours are using their software?
- 47. “How does your system…?” not “Can your system …?”.15
- 48. Presentation Outline Initiating your DAM Project Evaluating Solutions Implementing DAM Daily use of DAM Maintenance 16
- 50. How much time for initial cataloging?
- 51. How much time for ongoing cataloging?3. Server Admin 4. Training and Documentation 17
- 52. Installation Steps Preliminary Discussions Installation Configuration Configure Test Review Documentation Training Post-Implementation Evaluation 18
- 54. How people categorize assets
- 55. How people search for assets
- 56. How people will understand assets, including:
- 57. Descriptive Info
- 58. Usage Info19
- 59. Define Schema Controlled vocabulary A taxonomy or thesaurus that uses predefined lists of values. Unrestricted vocabulary An non-hierarchical collaborative method to categorize metadata where freely chosen keywords are used instead of a controlled vocabulary. Many organizations prefer not to use folksonomy, as it creates inconsistencies in the classification of information (kitty versus cat; product SKU versus product part number).Hybrid Vocabulary Offers users the choice of choosing values from controlled vocabulary listor entering in a desired value not available in the list. 20
- 62. Date created
- 67. Metadata Planning Tool Handout Page #2
- 69. Access outside of a DAM system
- 70. Applying metadata (keywords from path)23
- 71. Handout Page #3
- 73. Long file names (more than 32 characters)?
- 74. Mac resource forks?
- 75. Mac color labels applied?
- 76. Files larger than 2GB?
- 77. Filenames with anything other than letters (A-Z,a-z), numbers (0-9), spaces ( ), underscores (_), dashes (-), or periods(.) ?25
- 78. Documentation: Portland Art Museum Handout Page #4
- 79. Documentation: Miami Dade College Handout Page #5
- 80. DAM Implementation Summary Handout Page #6-8 28
- 81. Presentation Outline Initiating your DAM Project Evaluating Solutions Implementing DAM Daily use of DAM Maintenance 29
- 82. Workflow: Yale
- 83. Workflow: Miami Dade College
- 84. Workflow: AMNH
- 85. 33 Workflow: National Wildlife Federation
- 86. 34 Workflow: Portland Art Musuem
- 88. Automatic extraction of embedded metadata
- 89. Automatic generation of derivatives like thumbnails, previews, or video proxies35
- 91. Extraction of metadata from files
- 92. Embedding of metadata to files
- 93. Batch editing
- 94. Import or export of metadata to or from other systems and databases36
- 95. Handout Page #9
- 96. Handout Page #10
- 97. Handout Page #11
- 98. Search Basic Search Advanced Search 40
- 99. Handout Page #12
- 101. Download a low to medium-resolution file
- 102. Download a watermarked file
- 103. Playback time-based media (video streaming)42
- 105. Color mode
- 106. Dimensions
- 107. Resolution
- 108. Filename
- 109. Image content/pixels (image scripting)43
- 111. Insight into collection contents
- 112. Instant and remote access via the web
- 113. Intuitive user interfaces and search forms44
- 114. Handout Page #13
- 115. Media Sets Handout Page #14
- 116. The Solution: Portfolio Server Handout Page #15 47
- 117. Handout Page #16
- 118. Handout Page #17
- 119. Presentation Outline Initiating your DAM Project Evaluating Solutions Implementing DAM Daily use of DAM Maintenance 50
- 122. Invaluable in terms of recovering files accidentally lost
- 123. Get backups out of the building!Image source: http://www.flickr.com/people/roadhunter/ 51
- 124. Software Updates Major Updates (Version 2.0) Minor Updates (Version 2.1) Hosted Solution Updates Maintenance Contracts Customization 52
- 126. Phone
- 127. Web/KB
- 128. In-House vs. Outsourced?Consultants The Community 53
- 129. More Information DAM Learning Center: www.damlearningcenter.com/chicago2011 @DAMGeek 54
Notes de l'éditeur
- [Exercise: think of the most important field: controlled, uncontrolled, hybrid]
- example folder hierarchy different levels represent different categories It’s likely that this was folder structure was setup in advance Otherwise we would probably see some level of disorganization like: Spaces/underscores in filenames Duplicate folder names And “out of place folders”
- Here’s an example of part of a cheat sheet we made for the Registrars .
- Another example of basic documentation – cheat sheet for file standards
- Workflow (story)Here are some example use cases implemented into real-world workflows Prof. Foster has taught with projector slides and will continue to do so for the foreseeable future. However, students wanted to be able to review class images. A workflow was set up using the features in Portfolio which allow for automating cataloging on the server. Slides shown taken to photography services Slides are digitized/placed in weekly folders on server The DAM system watches the folders and adds items to the catalog putting the folder name in the keyword field Students search for images by week in web-based portal. The non-technical faculty member never touches the interface nor is any cataloging field provided
- Images are scannedMetadata is embedded to files using Adobe BridgeThe scans are added to the DAM with extracts metadata from the fileMetadata is refined in the DAM as needed for search purposes
- Example metadata fieldsDescription (text block)Keywords (multiple values)Date
- Master keyword list – a list of predefined keywords
- Predefined lists for department, event, image category, physical location
- We see an example of a taxonomy for “Physical location matches ocean life” where a user must choose from a predfined list. We also see an example of a folksonomy where a user can enter text into a freeform field.
- Predefined lists provide insight into collection contents
- You can see that the search interface is customized for search by weekThe entire collection is not exposed to students, only relevant materials
- Here’s an example of a collection of headshots from the National Gallery of London