Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Extensis DAM Forum at MW2011


Published on

Presentation from the Extensis DAM Forum at Museums and the Web 2011.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Extensis DAM Forum at MW2011

  1. 1. Digital Asset Management Forum <ul><ul><li>Maggie Hanson </li></ul></ul><ul><ul><li>Collections Information Manager </li></ul></ul><ul><ul><li>Portland Art Museum </li></ul></ul><ul><li>Edward Smith </li></ul><ul><li>Product Manager </li></ul><ul><li>Extensis </li></ul>
  2. 2. Presentation Outline <ul><li>Introduction </li></ul><ul><li>Preparing for DAM </li></ul><ul><li>Evaluating Solutions </li></ul><ul><li>Implementation </li></ul><ul><li>Daily Use </li></ul><ul><li>Maintenance & Next Steps </li></ul>
  3. 3. Introduction: Extensis <ul><li>Founded in 1993 </li></ul><ul><li>Software Company </li></ul><ul><li>Digital Asset Management products and services </li></ul><ul><li>Edward Smith </li></ul><ul><ul><ul><li>DAM Product Manager </li></ul></ul></ul><ul><ul><ul><li>DAM Learning Center Editor </li></ul></ul></ul>
  4. 4. Introduction: Portland Art Museum <ul><li>Founded in 1892 </li></ul><ul><li>Oldest museum in the Pacific Northwest </li></ul><ul><li>50,000 works </li></ul><ul><li>~130 FTE </li></ul><ul><li>No Rights & Reproductions dept. </li></ul><ul><li>Maggie Hanson </li></ul><ul><ul><li>Collections Information Manager </li></ul></ul><ul><ul><li>Manage CHAMP grant </li></ul></ul><ul><ul><li>Supervise DAM and interns </li></ul></ul><ul><ul><li>Lead an interdepartmental team of mostly senior staff </li></ul></ul>
  5. 6. What Is Digital Asset Management? DAM is the effective management and distribution of digital assets such as images, documents, creative files, audio and video clips. DAM solutions allow organizations to centrally catalog, store, retrieve and distribute large collections of valuable digital assets.
  6. 8. Asset Metadata <ul><li>“ Data about data” </li></ul><ul><ul><li>Information (metadata) about files (assets) </li></ul></ul><ul><ul><li>Machine or human generated </li></ul></ul><ul><li>Examples: </li></ul><ul><ul><li>Informational (The date a picture was taken) </li></ul></ul><ul><ul><li>Index (search keywords) </li></ul></ul><ul><ul><li>Rights (where/how can this file can be used?) </li></ul></ul>
  7. 9. What Is An Asset? “ Anything tangible or intangible that is capable of being owned or controlled to produce value…” (Wikipedia) “ A media file plus metadata” “ They’re only assets if you can find them”
  8. 10. The Need for DAM <ul><li>Locating assets </li></ul><ul><li>Understanding what assets are available </li></ul><ul><li>Providing access to the “correct” assets </li></ul><ul><li>Providing access to the “correct” format and size </li></ul><ul><li>Reusing assets </li></ul><ul><li>Recreating assets </li></ul><ul><li>Inconsistent use </li></ul><ul><li>Usage and rights management </li></ul>
  9. 11. <ul><li>Problems </li></ul><ul><ul><li>Confusing navigation of current folder structure </li></ul></ul><ul><ul><li>Deletion/duplication of files </li></ul></ul><ul><ul><li>Proliferation of files on desktops, etc. </li></ul></ul><ul><ul><li>No easy access to collections images for staff </li></ul></ul><ul><ul><li>No way to embed metadata in files (or use embedded metadata in a meaningful way </li></ul></ul>Needs: Portland Art Museum
  10. 12. Benefits of DAM <ul><li>Improve efficiency </li></ul><ul><li>Reduce costs </li></ul><ul><li>Increase revenue </li></ul><ul><li>Brand consistency </li></ul><ul><li>Customer service </li></ul>
  11. 13. Presentation Outline <ul><li>Introduction </li></ul><ul><li>Preparing for DAM </li></ul><ul><li>Evaluating Solutions </li></ul><ul><li>Implementation </li></ul><ul><li>Daily Use </li></ul><ul><li>Maintenance & Next Steps </li></ul>
  12. 14. Portland Art Museum <ul><li>Awarded substantial CHAMP grant in 2009 </li></ul><ul><li>CHAMP is an Oregon state “cultural reinvestment package to strengthen state agencies and cultural institutions” </li></ul><ul><li>Goals of grant: </li></ul><ul><ul><li>Increase Access (Internally & Externally) </li></ul></ul><ul><ul><ul><li>Standardize information </li></ul></ul></ul><ul><ul><ul><li>Manage our digital assets </li></ul></ul></ul><ul><ul><ul><li>Digitization </li></ul></ul></ul>
  13. 15. Identify and Involve Stakeholders <ul><ul><li>Find champions </li></ul></ul><ul><ul><li>Create a project team </li></ul></ul><ul><ul><li>Involve your IT department </li></ul></ul><ul><ul><li>Obtain director/executive level support </li></ul></ul>
  14. 16. <ul><li>CHAMP team: </li></ul><ul><li>Directors of Collections, Education, Development, and IT </li></ul><ul><li>Interactive Media Producer </li></ul><ul><li>Digital Asset Manager </li></ul>Stakeholders: Portland Art Museum
  15. 17. Take Inventory <ul><li>IT Assets </li></ul><ul><ul><li>Hardware and Operating Systems </li></ul></ul><ul><ul><li>Software and Applications </li></ul></ul><ul><li>File Assets </li></ul><ul><ul><li>Types (formats) </li></ul></ul><ul><ul><li>Number </li></ul></ul><ul><ul><li>Size (disk space) </li></ul></ul><ul><ul><li>Annual Growth </li></ul></ul><ul><li>Existing Systems and Data </li></ul><ul><ul><li>CMS </li></ul></ul><ul><ul><li>Spreadsheets </li></ul></ul><ul><ul><li>FileMaker/MS Access </li></ul></ul><ul><ul><li>Physical Information Systems </li></ul></ul><ul><ul><li>Other Databases? </li></ul></ul>
  16. 18. Inventory: Portland Art Museum <ul><li>IT Assets </li></ul><ul><ul><li>Primarily Windows </li></ul></ul><ul><ul><li>Some Mac users </li></ul></ul><ul><li>File Assets </li></ul><ul><ul><li>JPEG, Bitmap, TIFF, PDF, .MOV, .MP4, .WAV </li></ul></ul><ul><ul><li>20,000+ collection images </li></ul></ul><ul><li>Existing Systems and Data </li></ul><ul><ul><li>Mimsy XG </li></ul></ul><ul><ul><li>Museum Shared Server(s) </li></ul></ul><ul><ul><li>Several other systems </li></ul></ul><ul><ul><ul><li>FMP databases </li></ul></ul></ul><ul><ul><ul><li>Access databases </li></ul></ul></ul><ul><ul><ul><li>Educational programming content and interfaces </li></ul></ul></ul>
  17. 19. Portland Art Museum CMS (MimsyXG)
  18. 20. Portland Art Museum CMS (MimsyXG)
  19. 21. 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)
  20. 22. ROI Tool
  21. 23. Business Case: Portland Art Museum <ul><li>Supports the mission of our grant </li></ul><ul><li>Supports our institutional mission </li></ul><ul><li>Address pain points associated with: </li></ul><ul><ul><li>Rights management </li></ul></ul><ul><ul><li>Access </li></ul></ul><ul><ul><li>Permissions </li></ul></ul><ul><ul><li>Search </li></ul></ul><ul><ul><li>Limited staff and minimal resources </li></ul></ul>
  22. 24. Document Current Workflow <ul><li>Questions to Ask: </li></ul><ul><li>Who is responsible for managing assets? </li></ul><ul><li>Who needs access to assets? </li></ul><ul><ul><li>What are they looking for? </li></ul></ul><ul><ul><li>What formats do they need? </li></ul></ul><ul><li>What is the folder hierarchy convention (if any)? </li></ul><ul><li>What is the file naming convention (if any)? </li></ul>
  23. 25. Document Current Workflow Prior to evaluating DAM systems, document use case scenarios that describe how people currently work today, and how they would work in an ideal DAM system in the future.
  24. 26. 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.
  25. 27. 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.
  26. 28. <ul><li>Present Day Scenario </li></ul><ul><ul><li>Curator search the folders on the server </li></ul></ul><ul><ul><li>Grabs whatever size/format for their presentation </li></ul></ul><ul><ul><li>Results in calls to registrars (about the image) and IT (about the presentation freezing). </li></ul></ul><ul><li>Ideal Scenario </li></ul><ul><ul><li>Curators open a centralized repository </li></ul></ul><ul><ul><li>Search any number of useful fields </li></ul></ul><ul><ul><li>Download appropriate derivative using presets </li></ul></ul>Workflow Scenario #1
  27. 29. <ul><li>Present Day Scenario </li></ul><ul><ul><li>Marketing calls Registrars about images </li></ul></ul><ul><ul><li>Discussion takes place about image selection, appropriateness, quality, and rights </li></ul></ul><ul><li>Ideal Scenario </li></ul><ul><ul><li>Self-service image access for Marketing </li></ul></ul><ul><ul><li>Fields and galleries available for search and usage info </li></ul></ul><ul><ul><li>Marketing adds usage info to DAM </li></ul></ul>Workflow Scenario #2
  28. 30. <ul><li>Present Day Scenario </li></ul><ul><ul><li>Staff needs images of a past event </li></ul></ul><ul><ul><li>Looks through poorly organized folders </li></ul></ul><ul><ul><li>Tries to locate images based on filenames alone </li></ul></ul><ul><li>Ideal Scenario </li></ul><ul><ul><li>Staff searches DAM </li></ul></ul><ul><ul><li>Search on event name </li></ul></ul><ul><ul><li>Search on person name </li></ul></ul><ul><ul><li>Search for specific purpose </li></ul></ul>Workflow Scenario #3
  29. 31. Presentation Outline <ul><li>Introduction </li></ul><ul><li>Preparing for DAM </li></ul><ul><li>Evaluating Solutions </li></ul><ul><li>Implementation </li></ul><ul><li>Daily Use </li></ul><ul><li>Maintenance & Next Steps </li></ul>
  30. 32. <ul><li>Focus on solving problems, not features. </li></ul><ul><ul><li>What problems do you want to solve? </li></ul></ul><ul><ul><li>What problems are the most important? </li></ul></ul><ul><ul><li>What problems can be solved later (phase 2)? </li></ul></ul>Evaluation of DAM Systems
  31. 33. Requirements: Portland Art Museum <ul><li>DAM for curatorial and marketing search/download </li></ul><ul><li>Intuitive interface </li></ul><ul><li>Ease of </li></ul><ul><ul><li>Searching </li></ul></ul><ul><ul><li>Downloading </li></ul></ul><ul><li>Reduction of duplicates </li></ul><ul><li>Lowers strain on the IT department </li></ul><ul><li>Rights management </li></ul>
  32. 34. <ul><li>Must Have </li></ul><ul><ul><li>Cost </li></ul></ul><ul><ul><li>Ease of use </li></ul></ul><ul><ul><li>Search/embed/extract metadata </li></ul></ul><ul><ul><li>Download derivatives </li></ul></ul><ul><ul><li>Accessibility (Search & Retrieval) </li></ul></ul><ul><ul><li>Managing duplication, providing access to appropriate versions </li></ul></ul><ul><li>Nice to Have </li></ul><ul><ul><li>Customizable views </li></ul></ul><ul><ul><li>Customizable access levels </li></ul></ul><ul><li>Phase 2/TBD </li></ul><ul><ul><li>Granular levels of control </li></ul></ul><ul><ul><li>Deal with our messy folder structure on the back-end. </li></ul></ul><ul><ul><li>Incorporate non-collections assets </li></ul></ul>DAM Evaluation: Portland Art Museum
  33. 35. <ul><li>Types of DAM Systems </li></ul><ul><li>Commercial, Open Source, or Custom </li></ul><ul><li>Location </li></ul><ul><ul><li>Centralized onsite </li></ul></ul><ul><ul><li>Distributed onsite (multiple locations) </li></ul></ul><ul><ul><li>Cloud based (hosted) </li></ul></ul><ul><li>Licensing </li></ul><ul><ul><li>Per server </li></ul></ul><ul><ul><li>Per named user </li></ul></ul><ul><ul><li>Per connection </li></ul></ul><ul><ul><li>Subscription </li></ul></ul><ul><li>Scalability </li></ul>Evaluation of DAM Systems
  34. 36. <ul><li>Give vendors your notes and documentation. </li></ul><ul><li>Ask to see how the system would work with your assets, processes, and data instead of generic data and demos. </li></ul><ul><ul><li>Use cases </li></ul></ul><ul><ul><li>Sample assets </li></ul></ul><ul><ul><li>Metadata schema </li></ul></ul><ul><ul><li>Folder structure example </li></ul></ul>Evaluation of DAM Systems
  35. 37. <ul><li>Ask Vendors: </li></ul><ul><ul><li>For a web demo </li></ul></ul><ul><ul><li>For trial software </li></ul></ul><ul><ul><li>For customer referrals </li></ul></ul><ul><ul><li>How long have they been in business? </li></ul></ul><ul><ul><li>What other organizations like yours are using their software? </li></ul></ul><ul><ul><li>“ How does your system…?” not “ Can your system …?”. </li></ul></ul>Evaluation of DAM Systems
  36. 38. Presentation Outline <ul><li>Introduction </li></ul><ul><li>Preparing for DAM </li></ul><ul><li>Evaluating Solutions </li></ul><ul><li>Implementation </li></ul><ul><li>Daily Use </li></ul><ul><li>Maintenance & Next Steps </li></ul>
  37. 39. <ul><li>1. Project Team </li></ul><ul><li>2. Catalogers – dependant on cataloging strategy: </li></ul><ul><ul><li>Who will add files? </li></ul></ul><ul><ul><li>How much time for initial cataloging? </li></ul></ul><ul><ul><li>How much time for ongoing cataloging? </li></ul></ul><ul><li>3. Server Admin </li></ul><ul><li>4. Training and Documentation </li></ul>Assign Responsibilities
  38. 40. <ul><li>Preliminary Discussions </li></ul><ul><li>Installation </li></ul><ul><li>Configuration </li></ul><ul><ul><li>Configure </li></ul></ul><ul><ul><li>Test </li></ul></ul><ul><ul><li>Review </li></ul></ul><ul><li>Documentation </li></ul><ul><li>Training </li></ul><ul><li>Post-Implementation Evaluation </li></ul>Installation Steps
  39. 41. Define Schema <ul><li>Schema is the framework or structure of your DAM database. </li></ul><ul><li>Your schema will affect: </li></ul><ul><ul><li>How people add assets </li></ul></ul><ul><ul><li>How people categorize assets </li></ul></ul><ul><ul><li>How people search for assets </li></ul></ul><ul><ul><li>How people will understand assets, including: </li></ul></ul><ul><ul><ul><li>Descriptive Info </li></ul></ul></ul><ul><ul><ul><li>Usage Info </li></ul></ul></ul>
  40. 42. 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 list or entering in a desired value not available in the list.
  41. 43. <ul><li>Prioritize metadata field entry </li></ul><ul><li>1. Crucial Info… </li></ul><ul><ul><li>Capture device </li></ul></ul><ul><ul><li>Asset creator’s name </li></ul></ul><ul><ul><li>Date created </li></ul></ul><ul><ul><li>EXIF metadata </li></ul></ul><ul><li>2. Nice to Have… </li></ul><ul><ul><li>Conservation treatment status </li></ul></ul><ul><ul><li>Object collection information </li></ul></ul><ul><ul><li>Curatorial approvals </li></ul></ul><ul><li>3. Can Live Without… </li></ul><ul><ul><li>Work order information </li></ul></ul><ul><ul><li>Exhibition information </li></ul></ul>Define Schema
  42. 44. <ul><li>MIMSY Related Custom Fields </li></ul><ul><ul><li>Accession number </li></ul></ul><ul><ul><li>Title </li></ul></ul><ul><ul><li>Date </li></ul></ul><ul><ul><li>Artist </li></ul></ul><ul><ul><li>Artist Nationality </li></ul></ul><ul><ul><li>Artist Life Dates </li></ul></ul><ul><ul><li>Collection / Curatorial Dept. </li></ul></ul><ul><ul><li>Object Type </li></ul></ul><ul><ul><li>Credit Line </li></ul></ul><ul><ul><li>Copyright Status </li></ul></ul><ul><ul><li>Copyright Instructions </li></ul></ul>Schema: Portland Art Museum
  43. 45. <ul><li>Other Custom Fields </li></ul><ul><ul><li>Department </li></ul></ul><ul><ul><li>Copyright Status </li></ul></ul><ul><ul><li>Archival Storage Disc </li></ul></ul><ul><ul><li>Archival Storage Location </li></ul></ul><ul><ul><li>Event(s) </li></ul></ul><ul><ul><li>Exhibition(s) </li></ul></ul><ul><ul><li>Professional Photograph </li></ul></ul><ul><ul><li>Program(s) </li></ul></ul><ul><ul><li>Project(s) </li></ul></ul>Schema: Portland Art Museum <ul><ul><li>Resource Type </li></ul></ul><ul><ul><li>Digital Image </li></ul></ul><ul><ul><li>View Type </li></ul></ul><ul><ul><li>IPTC Copyright </li></ul></ul><ul><ul><li>IPTC Copyright Status </li></ul></ul>
  44. 46. Metadata Planning Tool
  45. 47. <ul><li>A folder hierarchy is a structure of folders and subfolders. </li></ul><ul><li>Folder hierarchies are used for: </li></ul><ul><ul><li>Browsing assets (instead of searching) </li></ul></ul><ul><ul><li>Access outside of a DAM system </li></ul></ul><ul><ul><li>Applying metadata (keywords from path) </li></ul></ul>Folder Hierarchy
  46. 48. Folder Hierarchy Example
  47. 49. Folder Hierarchy: Portland Art Museum <ul><li>Server #1: Museum Shared Server </li></ul><ul><ul><li>All departments have folders </li></ul></ul><ul><ul><li>Minimal structure </li></ul></ul><ul><ul><li>Messy access issues </li></ul></ul>
  48. 50. Folder Hierarchy: Portland Art Museum <ul><li>Server #2: Collections Server (CMS media—highly limited access) </li></ul><ul><ul><li>Audio </li></ul></ul><ul><ul><li>Video </li></ul></ul><ul><ul><li>Collection Images </li></ul></ul><ul><ul><ul><li>Archival (large images, formatted/unformatted) </li></ul></ul></ul><ul><ul><ul><li>Full </li></ul></ul></ul><ul><ul><ul><li>Thumb </li></ul></ul></ul><ul><ul><li>Conservation, Damage, etc. </li></ul></ul><ul><ul><ul><li>Images </li></ul></ul></ul><ul><ul><ul><li>Documents </li></ul></ul></ul><ul><ul><li>Documents </li></ul></ul>
  49. 51. Folder Hierarchy: Portland Art Museum <ul><li>Server #3: Marketing Server </li></ul><ul><ul><li>Publications </li></ul></ul><ul><ul><li>Branding </li></ul></ul><ul><ul><li>Etc. </li></ul></ul>
  50. 52. File Limitations <ul><li>File extensions? </li></ul><ul><li>Long file names (more than 32 characters)? </li></ul><ul><li>Mac resource forks? </li></ul><ul><li>Mac color labels applied? </li></ul><ul><li>Files larger than 2GB? </li></ul><ul><li>Filenames with anything other than letters (A-Z,a-z), numbers (0-9), spaces ( ), underscores (_), dashes (-), or periods(.) ? </li></ul>
  51. 53. File Naming Convention: PAM Current Portland Art Museum file naming convention: 2009_64_43c.tiff Proposed file naming convention: 2009_0064_0043c_AM.tiff
  52. 54. Documentation: Portland Art Museum
  53. 55. Documentation: Miami Dade College
  54. 56. Documentation: Miami Dade College
  55. 57. DAM Implementation Summary
  56. 58. Presentation Outline <ul><li>Introduction </li></ul><ul><li>Preparing for DAM </li></ul><ul><li>Evaluating Solutions </li></ul><ul><li>Implementation </li></ul><ul><li>Daily Use </li></ul><ul><li>Maintenance & Next Steps </li></ul>
  57. 59. Workflow Example #1: Yale
  58. 60. Workflow Example #2: MDC
  59. 61. Workflow Example #3 – AMNH
  60. 62. Workflow Example #4 – NWF
  61. 63. Workflow Example #5 – PAM
  62. 64. <ul><li>The process of adding files to a DAM system is also known as “ingesting”, “uploading”, or “cataloging”. </li></ul><ul><li>The process may be invoked or automatic (“watch folders”) </li></ul><ul><li>The Process May Involve: </li></ul><ul><ul><li>Addition of metadata by user </li></ul></ul><ul><ul><li>Automatic extraction of embedded metadata </li></ul></ul><ul><ul><li>Automatic generation of derivatives like thumbnails, previews, or video proxies </li></ul></ul>Adding Files
  63. 65. <ul><li>Automatic generation of keywords from file and folder names </li></ul><ul><li>Extraction of metadata from files </li></ul><ul><li>Embedding of metadata to files </li></ul><ul><li>Batch editing </li></ul><ul><li>Import or export of metadata to or from other systems and databases </li></ul>Metadata Management
  64. 66. <ul><li>Custom fields </li></ul><ul><li>File-naming convention </li></ul><ul><li>CMS </li></ul><ul><li>IPTC </li></ul><ul><li>Predefined lists </li></ul>Metadata Management: PAM
  65. 67. Controlled Lists, examples
  66. 68. Controlled Lists, examples
  67. 69. Basic Search Advanced Search Search
  68. 70. <ul><li>Collections Assets </li></ul><ul><ul><li>File-naming convention incorporates accession number </li></ul></ul><ul><ul><li>QuickFind searches Accession Number, Artist Name, and Title </li></ul></ul><ul><ul><li>Galleries </li></ul></ul><ul><ul><ul><li>Public Domain </li></ul></ul></ul><ul><ul><ul><li>High-res </li></ul></ul></ul><ul><ul><ul><li>Professional photog </li></ul></ul></ul>Search: Portland Art Museum
  69. 71. Search: Portland Art Museum <ul><li>Non-collection Assets </li></ul><ul><ul><li>Include </li></ul></ul><ul><ul><ul><li>Marketing collateral </li></ul></ul></ul><ul><ul><ul><li>Education & Public Programming </li></ul></ul></ul><ul><ul><ul><li>Events photography </li></ul></ul></ul><ul><ul><li>Folder and filenames provide keywords </li></ul></ul><ul><ul><li>Controlled lists for user-added info </li></ul></ul><ul><ul><li>Future: </li></ul></ul><ul><ul><ul><li>Cataloging schemas for non-collection assets </li></ul></ul></ul><ul><ul><ul><li>Institutional master keyword list </li></ul></ul></ul>
  70. 72. <ul><li>After previewing an asset on screen, a user may need access to: </li></ul><ul><ul><li>Download a high-resolution original file </li></ul></ul><ul><ul><li>Download a low to medium-resolution file </li></ul></ul><ul><ul><li>Download a watermarked file </li></ul></ul><ul><ul><li>Playback time-based media (video streaming) </li></ul></ul>Download
  71. 73. <ul><li>Batch processing can change one or more of the following attributes on a selection of assets: </li></ul><ul><ul><li>Format </li></ul></ul><ul><ul><li>Color mode </li></ul></ul><ul><ul><li>Dimensions </li></ul></ul><ul><ul><li>Resolution </li></ul></ul><ul><ul><li>Filename </li></ul></ul><ul><ul><li>Image content/pixels (image scripting) </li></ul></ul>Processing
  72. 74. <ul><li>Read-only users (most) download using presets: </li></ul><ul><ul><li>.ppt </li></ul></ul><ul><ul><li>web/email </li></ul></ul><ul><ul><li>thumbnail </li></ul></ul><ul><ul><li>large </li></ul></ul><ul><li>Department reps can access original </li></ul><ul><ul><li>Download original untouched </li></ul></ul><ul><ul><li>Batch convert </li></ul></ul>Processing: Portland Art Museum
  73. 75. <ul><li>Users maintaining digital asset collections typically use client applications to add and maintain the digital asset management system. </li></ul><ul><li>Other “outside” users that are not familiar with the collection may benefit from self-service web portals that provide: </li></ul><ul><ul><li>Access to approved assets in the correct formats </li></ul></ul><ul><ul><li>Insight into collection contents </li></ul></ul><ul><ul><li>Instant and remote access via the web </li></ul></ul><ul><ul><li>Intuitive user interfaces and search forms </li></ul></ul>Self Service Web Portals
  74. 77. Media Sets
  75. 78. The Solution: Portfolio Server
  76. 81. Presentation Outline <ul><li>Introduction </li></ul><ul><li>Preparing for DAM </li></ul><ul><li>Evaluating Solutions </li></ul><ul><li>Implementation </li></ul><ul><li>Daily Use </li></ul><ul><li>Maintenance & Next Steps </li></ul>
  77. 82. Archive != Backup <ul><li>Types of DAM workflows: </li></ul><ul><ul><li>Production/Work in progress </li></ul></ul><ul><ul><li>Archive/Distribution </li></ul></ul><ul><li>Back-up your files! </li></ul><ul><ul><li>RAID is not backup </li></ul></ul><ul><ul><li>Invaluable in terms of recovering files accidentally lost </li></ul></ul><ul><ul><li>Get backups out of the building! </li></ul></ul>Image source:
  78. 83. Software Updates Major Updates (Version 2.0) Minor Updates (Version 2.1) Hosted Solution Updates Maintenance Contracts Customization
  79. 84. Support <ul><li>Internal Support </li></ul><ul><li>Vendor Support </li></ul><ul><ul><li>Email </li></ul></ul><ul><ul><li>Phone </li></ul></ul><ul><ul><li>Web/KB </li></ul></ul><ul><ul><li>In-House vs. Outsourced? </li></ul></ul><ul><li>Consultants </li></ul><ul><li>The Community </li></ul><ul><li>Professional Orgs/List-servs (MCN, ImageMuse, VRA, etc.) </li></ul>
  80. 85. Next Steps: Portland Art Museum <ul><li>Training Timeline </li></ul><ul><ul><li>Registrars (with individual follow-up training as needed) </li></ul></ul><ul><ul><li>Education & Marketing </li></ul></ul><ul><ul><li>Curators </li></ul></ul><ul><ul><li>Assistance and check-ins as needed </li></ul></ul>
  81. 86. Next Steps: Portland Art Museum <ul><li>Cataloging Timeline: </li></ul><ul><ul><li>Refine Mimsy reports </li></ul></ul><ul><ul><li>Schedule CMS imports </li></ul></ul><ul><ul><li>Ongoing rights research </li></ul></ul><ul><ul><li>Incorporate Marketing server </li></ul></ul><ul><ul><li>Cataloging schema for Marketing and Education files </li></ul></ul>
  82. 87. More Information Portland Art Museum DAM Learning Center: /mw2011 @DAMGeek Extensis Portfolio Server: