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.

Digital Art History: From Practice to Publication

1,263 views

Published on

Presentation given at colloquium during Beyond the Digitized Slide Library, a summer institute at UCLA in July 2015. More info: http://www.humanities.ucla.edu/getty/ #doingdah15

Published in: Government & Nonprofit

Digital Art History: From Practice to Publication

  1. 1. Digital Art History from Practice to Publication Susan Edwards Associate Director, Digital Content The Hammer Museum @jolifanta
  2. 2. Apologies
  3. 3. The Scholarly Process
  4. 4. The Scholarly Process
  5. 5. The Scholarly Process Start here?
  6. 6. The Scholarly Process ?
  7. 7. The Scholarly Process Product Development
  8. 8. The Scholarly Process Product Development
  9. 9. ? Product Development • Setting goals • Audience • Applying for Grants • Budget • Timeline • Iterative work • Programming • Formative ideas • Research questions • Collecting data • Analysis • Forming conclusions • Editing The Scholarly Process • Testing • Editorial • Design
  10. 10. Working with Technologists?
  11. 11. 14 filled out the survey 10 interviewed (2 didn’t fill out survey) 16 responded https://docs.google.com/forms/d/1nw4MgcCvbKFnAicq5EoYLCWlWti5ibNSStcFlP0br6k/viewform
  12. 12. • I am a: [check boxes for different skills] • My role in DH projects has been: [check boxes] • Here are some projects I have worked on that may be good models for the field: • I like to work with scholars because: • Working with scholars is challenging because: • When scholars approach me about a project, it's helpful to have the following information: • If I were to give one piece of advice to scholars about working with technologists on DH projects, it would be: The Survey
  13. 13. • How do you define Digital Humanities? • Why is Digital Humanities important? • Tell me about some projects you have worked on. • How do you typically come to work on these projects? What is your role? • What do scholars struggle with? • Do scholars need to understand the technology? Do they need to code? • Why do you work on these projects? The Interview
  14. 14. 14 filled out the survey 10 interviewed (2 didn’t fill out survey) 16 total The Response
  15. 15. 3 art historians 10 have worked on art history projects 16 total The Response 6 technologists 7 work in or have worked for museums
  16. 16. 4 work in museums 16 total The Response 8 affiliated with a university 3 are freelance
  17. 17. The Response 4 work in museums 8 affiliated with a university (at least 4 work in DH center) 3 are freelance 16 total
  18. 18. Results >> • 3 common themes • 10 pieces of advice
  19. 19. 3 common themes >>  Audience  Collaboration  Project Management
  20. 20.  Audience “Scholarship for other scholars…is that what it is? Are we missing a big opportunity [to reach a wider audience]?”
  21. 21.  Audience Who is it for? • Be honest • Is it other scholars? • Is it students? General public?
  22. 22.  Audience Why are you doing it? • Share the data to demonstrate validity of your scholarship. • Provide data and materials to larger community for use. • Reach a wider public. • Instruction/pedagogy
  23. 23.  Audience Testing with your users • Ensures you achieve your goals • Be open to failure and changing tactics • Adds to timeline but helps ensure a successful product
  24. 24.  Collaboration “Scholars struggle with understanding what is possible…they have a hard time determining what may be a simple solution from a difficult one.”
  25. 25.  Collaboration Bring Technologists in as early as possible • Formative phase – it starts with conversations • Technologists can help with ‘goals triage’ • Include them in grant application
  26. 26.  Collaboration Technologists are experts too! • Let technologist suggest the solution – you don’t know what you don’t know • Be open to suggestions, and new solutions to meet your goals. • Don’t drop the project on a technologist and walk away
  27. 27.  Collaboration http://xkcd.com/1425/
  28. 28.  Collaboration Think TEAM - understand various roles required • You probably can’t do it all • Be self-aware of your own skills, and the role you will play • Be realistic about timelines • Find your community
  29. 29.  Project Management “Scholars struggle with planning and time….they underestimate complexity, time, and resources.”
  30. 30.  Project Management Project manager’s role is to “live in the future” • Anticipate problems • Thinks about longevity of project • Watches time and dependencies, enforces deadlines • Gets everyone on the same page
  31. 31.  Project Management Guides the process, provides structure • Facilitates collaboration and conversations • Translates between technologists and content experts • Can help you design the minimal viable product, and plan for staged releases of new features
  32. 32.  Project Management Keeps energy up when initial excitement wanes
  33. 33. 3 common themes >>  Audience  Collaboration  Project Management
  34. 34. 10 Pieces of Advice
  35. 35. 1. Bring in a technology collaborator as early as possible. 10 Pieces of Advice
  36. 36. 2. Focus on the goals of the project. 10 Pieces of Advice
  37. 37. 3. Learn about project management; have a project manager. 10 Pieces of Advice
  38. 38. 4. Learn the language—understand basic concepts of computer programming, web technology, databases, etc. 10 Pieces of Advice
  39. 39. 5. Be self-aware of your own skills. 10 Pieces of Advice
  40. 40. 6. Check your ego at the door. 10 Pieces of Advice
  41. 41. 7. Pay attention to timelines. 10 Pieces of Advice
  42. 42. 8. Get commitment from the top. 10 Pieces of Advice
  43. 43. 9. Start small—better to have one small thing accomplished. 10 Pieces of Advice
  44. 44. 10. Find a community, create a network. 10 Pieces of Advice
  45. 45. ? Product Development
  46. 46. ? Product Development Start here
  47. 47. ? Product Development Start here
  48. 48. ? Product Development Start here Project Manager
  49. 49. Thank You Tina Shah, Art Institute of Chicago Ben Brumfield, independent software developer Paul Marty, Florida State University A. L. McMichael, The Graduate Center, CUNY Javier de la Rosa, University of Western Ontario Heather Marie Wells, Crystal Bridges Museum Beth Harris, Khan Academy and Smarthistory Mike Toth, independent technology consultant Steph Grimes, J. Paul Getty Trust Wayne Graham, University of Virginia

×