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.

Content & Collections Management - Scalability, Sustainability

122 views

Published on

AAM Presentation on Enterprise Content and Collections Management, facilitating more effective resource spend on production instead of reproduction. Presentation from my chapter in Lord Cultural Resources book Manual of Digital Museum Planning.

Published in: Design
  • Be the first to comment

  • Be the first to like this

Content & Collections Management - Scalability, Sustainability

  1. 1. Corey Timpson VP, Exhibitions, Research, and Design Canadian Museum for Human Rights corey.timpson@humanrights.ca
 @coreytimpson Building Relevance Operational Efficiency & Inclusion
  2. 2. . Intangible heritage . Stories are our artefacts . Unique opportunities for: - collecting intangible heritage - mixed and transmedia storytelling Canadian Museum for Human Rights @coreytimpson
  3. 3. . Intangible heritage . Stories are our artefacts . Unique opportunities for: - collecting intangible heritage - mixed and transmedia storytelling . Unique challenges: - contemporaneity
 - dialogic - relevant Canadian Museum for Human Rights @coreytimpson
  4. 4. Contemporary Subject to interpretation Practical Context
  5. 5. Contemporary Subject to interpretation . scalability . changeability Practical Context
  6. 6. @coreytimpson
  7. 7. 95 digital installations + 100 hours of video + 2600 images in gallery 2 soundscapes 19 mixed-media immersive environments 300 objects/artefacts 1 Enterprise Web site 1 Core Mobile Program (2 platforms, scalable) 2 Exhibit specific Apps (2 platforms) Social: Twitter (2), FB (2), YouTube (2), Flickr, Instagram, Tumblr + Digital Signage System (5 different instances) 465 square meter (5000 square feet) temporary exhibition gallery 140 square meter (1500 square feet) temporary exhibition gallery ECOSYSTEM @coreytimpson
  8. 8. 100,000 words of text Library collection, Archival collection, Museum collection Oral History Program (longest OH = 8hrs) Born digital artefacts Intensive loan program Copyright ECOSYSTEM @coreytimpson
  9. 9. The most foul word in museum technology. As builders of the museum, what will our legacy be? Legacy @coreytimpson
  10. 10. The most foul word in museum technology. As builders of the museum, what will our legacy be? Technology, matured, and technical methodolgy, can be a facilitator of change, and a mitigation against/ for legacy. Legacy @coreytimpson
  11. 11. ENTERPRISE CONTENT MANAGEMENT SYSTEM ECMS @coreytimpson
  12. 12. STRATEGIC PREREQUESITES . strict separation of content from presentation . store content once and reference often . dynamically deliver content . be able to do “anything” . allow the creation of business rules to constrain the system . be completely modular and scalable . standards compliance ECMS @coreytimpson
  13. 13. COMPONENTS . DAM — Digital Asset Management System . ALM — Archives, library, collections management system . CMS — Content Management System . Enterprise Search . Thesauri & Vocabulary Management . Copyright Management ECMS @coreytimpson
  14. 14. COMPONENTS . DAM — Digital Asset Management System . ALM — Archives, library, collections management system . CMS — Content Management System . Enterprise Search . Thesauri & Vocabulary Management . Copyright Management FUNCTION . Catalogue, Preserve, Aggregate, Manage: All information . Feed all digital endpoints with dynamic content. ECMS @coreytimpson
  15. 15. THE ROAD - 4 PHASE PROJECT PHASE 1 2010 — CONCEPT DEVELOPMENT . requirements definition . environmental scans (incl. CHIN’s ALM research) . data architect (pink sky) . product demos . interviews . conferences and schmoozing - collections teams, digital platforms team, IT, researchers, etc. ECMS DEV @coreytimpson
  16. 16. THE ROAD - 4 PHASE PROJECT PHASE 2 2011/12 — PROCUREMENT & DEVELOPMENT . formal requirements documentation . RFP . award & negotiations . development ECMS DEV @coreytimpson
  17. 17. THE ROAD - 4 PHASE PROJECT PHASE 2.5 2012 — RE-DEVELOPMENT . proprietary solution . it wasn’t what it claimed to be . data was not easily extracted or accessible ECMS DEV @coreytimpson
  18. 18. THE ROAD - 4 PHASE PROJECT PHASE 2.5 2012 — RE-DEVELOPMENT . proprietary solution . it wasn’t what it claimed to be . data was not easily extracted or accessible Decision: - spend dev efforts on the front end, instead of the backend - go open source (our culture and approach) ECMS DEV @coreytimpson
  19. 19. THE ROAD - 4 PHASE PROJECT PHASE 3 2013/14 — DEVELOPMENT & INTEGRATION . Component Integration (DAM, ALM, Search, etc.) . API dev (and content modelling) . full steam ahead on cataloguing (we had begun acquisitions on spreadsheets) . production ECMS DEV @coreytimpson
  20. 20. THE ROAD - 4 PHASE PROJECT PHASE 4 2015 - PRESENT — ITERATION & “FINAL” DEV . function elaboration . unification of look and feel on admin sides . module customization ECMS DEV @coreytimpson
  21. 21. WHITE BOARD - 2009 ECMS DEV @coreytimpson
  22. 22. PROOF OF CONCEPT - 2012 ECMS DEV @coreytimpson
  23. 23. LOGICAL DIAGRAM - 2014 ECMS DEV @coreytimpson
  24. 24. The most foul word in museum technology. As builders of the museum, what will our legacy be? Technology, matured, and technical methodolgy, can be a facilitator of change, and a mitigation against/ for legacy. ——————————- Preserve, manage, find, present information in scalable, efficient, and dynamic ways. Legacy @coreytimpson
  25. 25. Why? @coreytimpson
  26. 26. Resource management. Why? @coreytimpson
  27. 27. Resource management. OLD PROCESS . content development . acquisition . catalogue . design & layout . production . software dev . publishing <repeat> Why? @coreytimpson
  28. 28. Resource management. OLD PROCESS . content development . acquisition . catalogue . design & layout . production . software dev . publishing <repeat> Why? @coreytimpson NEW PROCESS . content development . acquisition . catalogue <published>
  29. 29. Resource management. OLD PROCESS . content development . acquisition . catalogue . design & layout . production . software dev . publishing <repeat> Old content across new installations and new digital end-points. New content across existing installations and end-points. Why? @coreytimpson NEW PROCESS . content development . acquisition . catalogue <published>
  30. 30. So we can spend our resources on development, rather than on production. Or on new production, instead of re-production. Why? @coreytimpson
  31. 31. ALM . AtoM (Archives) . Koha (Library) . Collective Access (Museum Collections/Objects) . iQvoc (HRT) DAM . Alfresco Search . Solr CMS . Drupal ECMS @coreytimpson
  32. 32. ALM . AtoM (Archives) . Koha (Library) . Collective Access (Museum Collections/Objects) . iQvoc (HRT) DAM Integrated and shared data through the ECMS. Searchable/findable anywhere. Publishable anywhere. ECMS @coreytimpson
  33. 33. RECENT CHANGE - 2016/17 Added the functionality to track and manage ALL text. Treat text as any other asset, even it is non-digital. ECMS @coreytimpson
  34. 34. RESULTS . 95 digital installation, web site, reference centre, mobile apps, digital signage, etc. . All pull data from the ECMS ECMS @coreytimpson
  35. 35. RESULTS . Text-to-speech + Mobile App (Near Me mode) INCLUSION @coreytimpson
  36. 36. We need to preserve things, find things, and use things. It’s all just data. LESSON @coreytimpson
  37. 37. We need to preserve things, find things, and use things. It’s all just data. The most important aspect of the system design and development was thinking long-term. Scalability, changeability, being able to use the data later in ways you cannot imagine right now. LESSON @coreytimpson
  38. 38. Corey Timpson Vice President, Exhibitions, Research, and Design Canadian Museum for Human Rights @coreytimpson | corey.timpson@humanrights.ca

×