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.

InfoCamp Seattle DAM!


Published on

Presentation at unconference on Digital Asset Management for Creative Agencies - deciding when to be linear and when to be a squiggly line.

Published in: Career
  • Login to see the comments

  • Be the first to like this

InfoCamp Seattle DAM!

  1. 1. Digital asset management for creative agencies InfoCamp Seattle 2010 Presented by Tracy Guza [email_address]
  2. 2. Things to consider <ul><li>How much stuff do I want to organize? (size, volume) </li></ul><ul><li>What kind of files do I have? (JPG, PDF, TIF, Raw, etc.) </li></ul><ul><li>How do I want to access my stuff? (web based or internal) </li></ul><ul><li>How many people will be using these assets? </li></ul>
  3. 3. Selecting a DAM platform <ul><li>Consider users and assets </li></ul><ul><li>Consider budget </li></ul><ul><li>Consider future growth </li></ul><ul><li>Picasa, Extensis Portfolio, Adobe Scene 7 </li></ul>
  4. 4. Preparation <ul><li>File naming conventions </li></ul><ul><ul><li>Maximum 31 characters </li></ul></ul><ul><ul><li>Descriptive </li></ul></ul><ul><ul><li>Identify client, collection, creator </li></ul></ul><ul><ul><li>Unique identifier (sequential numbering) </li></ul></ul><ul><ul><li>Date </li></ul></ul>
  5. 5. Preparation Continued <ul><li>Image quality </li></ul><ul><ul><li>Is format consistency important? </li></ul></ul><ul><ul><li>How is my resolution? </li></ul></ul><ul><ul><li>Do I need to collect any images from other sources? </li></ul></ul>
  6. 6. Next steps <ul><li>Basic organization </li></ul><ul><li>Metadata </li></ul><ul><li>Data dictionaries </li></ul><ul><li>Controlled vocabulary </li></ul>
  7. 7. Basic organization <ul><li>Batch renaming </li></ul><ul><li>Gather in one place on server </li></ul><ul><li>Create folders and subfolders </li></ul>
  8. 8. Metadata <ul><li>Existing standard or create your own </li></ul><ul><li>Consider the type of content </li></ul><ul><li>Modify an existing standard </li></ul><ul><li>Dublin Core example: </li></ul><ul><ul><li> </li></ul></ul>
  9. 9. Data dictionary <ul><li> </li></ul><ul><li>Essentially, think about your elements and how you will populate the content fields. </li></ul>
  10. 10. Project management <ul><li>Discovery/Design </li></ul><ul><ul><li>What, how, who </li></ul></ul><ul><ul><li>Develop schedule, budget </li></ul></ul><ul><li>Implementation </li></ul><ul><ul><li>The actual work </li></ul></ul><ul><li>Evaluation </li></ul><ul><ul><li>Test and refine </li></ul></ul><ul><li>Maintenance </li></ul>
  11. 11. Controlled vocabulary <ul><li>Consistency </li></ul><ul><li>Findability </li></ul><ul><li>Ease of maintenance and user experience </li></ul><ul><li>Existing, modified, custom? </li></ul><ul><li>Example: </li></ul>