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 Narratives for Transylvania DH


Published on

A survey of metadata driven narrative with specific use of Omeka

Published in: Education
  • Be the first to comment

Digital Narratives for Transylvania DH

  1. 1. Constructing Narrative
 Using Digital Objects Amplifying the Traditional Craft Shawn Day Transylvania Digital Humanities Centre / 30 April /1 May 2015
  2. 2. Agenda
  3. 3. Objectives ‣ A brief introduction to Metadata, it’s value and how it can be leveraged in Omeka as a digital narrative tool; ‣ To evaluate what digital narrative tools - such as Omeka or others - may be of use in sharing your research – and telling your story. ‣ Why à How
  4. 4. Logistics ‣ Sign-Up
  5. 5. Telling a Story Online Examples
  6. 6. Omeka in Action ‣ Example 2
  7. 7. Gothic Past
  8. 8. Hilda Tweedy
  9. 9. Metadata and the Story
  10. 10. Who works with Metadata today?
  11. 11. "If a resource does not have any associated metadata information, then it is essentially lost."
  12. 12. "If a resource has erroneous, inconsistent, or not enough metadata information, then it is essentially non-existent."
  13. 13. Why and How? - Basic Metadata ‣ What is this resource? ‣ Who created the resource? ‣ When was this resource created or published? ‣ Why was this resource created? ‣ Who owns or how do you purchase the resource? ‣ Can you re-use and/or share this resource? (Licensing)
  14. 14. Types of Metadata ‣ Descriptive metadata —> Identification; ‣ Structural metadata —> Referential; ‣ Administrative metadata —> Manage; ‣ Technical metadata —> Production Process; ‣ Preservation metadata —> Preservation Processes; ‣ Rights metadata —> Access and Use. ‣ Some or all
  15. 15. A Universe of Standards
  16. 16. A Few Common Standards ‣ Dublin Core (ISO15836) ‣ Resource discovery across domains ‣ General and Abstracted ‣ GIS Metadata (ISO19115) —> OGC GML ‣ VRA Core -Visual Materials ‣ MODS (METS) —> MARC ‣ MPEG21 - Multimedia Resources
  17. 17. Why Metadata? 1. Facilitate Discovery of Content; 2. Help Organise Content; 3. Facilitate Harvesting of Content; 4. Support Archiving and Preservation.
  18. 18. A Rather Quick Introduction
 to Dublin Core Just Enough to be Dangerous
  19. 19. TITLE ‣ Title ‣ <dc:title></dc:title> ‣ What the formal name of this resource - how would a user know it? ‣ Examples: title of a painting, photo, document; the name of a person when using the "person" item type; the name of a lesson plan. ‣ <dc:title>Arab Gentleman</dc:title>
  20. 20. SUBJECT ‣ Subject ‣ <dc:subject></dc:subject> ‣ What is the domain area/topic (non-spatial or temporal) that the object is part of? ‣ Controlled vocabularies such as the Getty can help here. ‣ Typically keywords, key phrases, or classification codes. ‣ Examples: Library of Congress subject headings; subject- specific nomenclature. ‣ <dc:subject>Bell, Gertrude Lowthian 1868-1926 — Journeys — Pictorial works.</dc:subject>
  21. 21. DESCRIPTION ‣ Description ‣ <dc:description></dc:description> ‣ What sort of short narrative will help a user to know whether this resource is relevant to their needs? ‣ This is often an abstract, a table of contents or even a graphical representation of the object ‣ Examples: a photo caption; descriptive information of an artifact/ museum object; summary of a lesson plan; abstract or summary of a long document. ‣ <dc:description>[Arab gentleman - possibly Am’a Abdullah Pasha]</dc:description>
  22. 22. CREATOR ‣ Creator ‣ <dc:creator></dc:creator> ‣ Who is responsible for making this digital resource - digtiser, digital author? ‣ The original author or the digitising institution? ‣ Examples: Author/authors; artists; photographers; institutional authors or producers, such as university or federal agency. ‣ <dc:creator>Gertrude Bell</dc:creator>
  23. 23. SOURCE ‣ Source ‣ <dc:source></dc:source> ‣ From what resource did the derived digital resource come from? ‣ This can be a type, a descriptor but best practice recommends a string conforming to a formal identifier system ‣ Examples: Accession number; Collection of objects; Division of an archive or library. ‣ <dc:source>Gertrude Bell Papers, Special Collections, Newcastle University</dc:source>
  24. 24. PUBLISHER ‣ Publisher ‣ <dc:publisher></dc:publisher> ‣ Who (what institution is making this resource available? ‣ If there is a license or copyright involved helps to determine this one ‣ Examples: actual publisher, if there is one; entity or consortium publishing digital materials. ‣ <dc:publisher>University Library, Newcastle University</ dc:publisher>
  25. 25. DATE ‣ Date ‣ <dc:date></dc:date> ‣ A point or period in the lifecycle of the digital object ‣ When was this scanned?When was it published? ‣ Consistency - decided by project management - documented ‣ Consider in relation to the coverage of the object ‣ Date is one of the trickiest fields to fill.You will want to decide how best to use it for your project for consistency. There is an open text field for date so that you can reflect the type of date information you have whether it is a very specific date MM/DD/YYYY or if it is "circa 1940". ‣ <dc:date>1905-03</dc:date>
  26. 26. CONTRIBUTOR ‣ Contributor ‣ <dc:contributor></dc:contributor> ‣ Who (individual, institution, organisation - entity) is making this object available/responsible for its digitisation? ‣ Examples: person who contributed a story or file for an Omeka collecting project; owner or donor of collected objects. ‣ <dc:contributor>Special Collections, Newcastle University</ dc:contributor>
  27. 27. RIGHTS ‣ Rights ‣ <dc:rights></dc:rights> ‣ What restrictions are held in and over this resource? ‣ This is typically a statement relation to the intellectual and usage rights relating to this digital object ‣ Examples: spell out conditions of use for specific items here; Creative Commons type; Public Domain. ‣ <dc:rights>Reproduction of these materials in any format for any purpose other than personal research and study may constitute a violation of CDPA 1988 and infringement of rights associated with the materials. Please contact us for permissions information at</dc:rights>
  28. 28. RELATION ‣ Relation ‣ <dc:relation></dc:relation> ‣ What resources are related to this digitised object? ‣ Best practice is to refer to a <dc:identifier> ‣ Examples: a still image of a person entered as a "person" type. ‣ <dc:relation>Gertrude Bell Collection</dc:relation>
  29. 29. FORMAT ‣ Format ‣ <dc:format></dc:format> ‣ What is the file format of this digital resource? ‣ Examples include size and duration. Recommended best practice is to use a controlled vocabulary such as the Internet Media Types (MIME). ‣ <dc:format>JPG</dc:format>
  30. 30. LANGUAGE ‣ Language ‣ <dc:language></dc:language> ‣ What is the language(s) of the digital resource? ‣ Again best practice is to use a controlled vocabulary such as RFC4646 ‣ Examples: English; Russian; Spanish, et al.
  31. 31. TYPE ‣ Type ‣ <dc:type></dc:type> ‣ What defined type best represents the object you are referencing? ‣ Best practice to use the DCMI Type controlled vocabulary ‣ ‣ Examples: For consistency, use item type controlled vocabulary provided by Omeka: Document, Moving Image, Oral History, Sound, Still Image,Website, Event, Email, Lesson Plan, Hyperlink, Person, or Interactive Resource. ‣ < ‣ dc:type>Still Image</dc:type>
  32. 32. IDENTIFIER ‣ Identifier ‣ <dc:identifier></dc:identifier> ‣ Where will a user find this resource via the web? ‣ A direct and unambiguous identification of the resource - unique and persistent - handle? ‣ <dc:identifier>658/2</dc:identifier>
  33. 33. COVERAGE ‣ Coverage ‣ <dc:coverage></dc:coverage> ‣ To what defining place or time is this item relevant (spatial or temporal)? ‣ Typically relies on a controlled vocabulary relevant to the domain, ie. The Getty Museum / Research Institute ‣ Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges. ‣ <dc:coverage>Damascus - Syria</dc:coverage>
  34. 34. An Arab Gentleman – and a Digital Object ‣ <?xml version="1.0"?><!DOCTYPE rdf:RDF PUBLIC "-//DUBLIN CORE//DCMES DTD 2002/07/31//EN" ‣ ""> ‣ <rdf:RDF xmlns:rdf="" ‣ xmlns:dc=""> ‣ <rdf:Description rdf:about=""> ‣ <dc:title>Arab gentleman</dc:title> ‣ <dc:subject>Bell, Gertrude Lowthian 1868-1926 — Journeys — Pictorial works.</dc:subject> ‣ <dc:description>[Arab gentleman - possibly Am'a Abdullah Pasha]</dc:description> ‣ <dc:creator>Gertrude Bell</dc:creator> ‣ <dc:source>Gertrude Bell Papers, Special Collections, Newcastle University</dc:source> ‣ <dc:publisher>University Library, Newcastle University</dc:publisher> ‣ <dc:date>1905-03</dc:date> ‣ <dc:contributor>Special Collections, Newcastle University</dc:contributor> ‣ <dc:rights>Reproduction of these materials in any format for any purpose other than
 personal research and study may constitute a violation of CDPA 1988 and infringement of 
 rights associated with the materials. Please contact us for permissions information at</dc:rights> ‣ <dc:relation>Gertrude Bell Collection</dc:relation> ‣ <dc:format>JPG</dc:format> ‣ <dc:language>EN</dc:language> ‣ <dc:type>Still Image</dc:type> ‣ <dc:identifier>658/2</dc:identifier> ‣ <dc:coverage>Damascus - Syria</dc:coverage> ‣ </rdf:Description></rdf:RDF>
  35. 35. Keepinging the User in Mind ‣ How will people find what they are looking for? ‣ How will they differentiate from one 'thing' over another? ‣ How will your information architecture refer to the digital objects? ‣ Useful for Straight Dublin Core: Dublin Core Generator
  36. 36. Lessons ‣ The world is fluid and formats and standards change ‣ How can I choose the right one? ‣ Be consistent and you can transform and evolve - Crosswalks ‣ How can I make the right decisions? ‣ I am a big fan of the Digital Curation Centre (DCC) ‣ They have some very useful tools:
  37. 37. Exercise One Getting Intimate with Digital Objects
  38. 38. Seeing Metadata in Action 1. Browse to imagine~11~memorie-colectiva~child-and-car.html 2. Explore the context of the image within the collection - browse 3. Copy the Dublin Core information – digitally preferred 4. (NotePad)
  39. 39. Reporting Back
  40. 40. Introducing Omeka Collecting and Managing Digital Objects
  41. 41. Who’s Behind Omeka?: CNMH ‣ Roy Rosenzweig Centre for New Media and History ‣ Founded 1994 ‣ George Mason University inWashington ‣ Collaborative Space Supporting 50+ Scholars ‣ To preserve and present history online ‣ Transform scholarship across the humanities ‣ Supported by grants from AHA, NEH, NHC, Library of Congress, Mellon, Sloan, Rockefeller and Kellog Foundations amongst others
  42. 42. Products Zotero Zotero [zoh-TAIR-oh] is a free, easy-to-use Firefox extension to help you collect, manage, and cite your research sources. Omeka Designed for cultural institutions, enthusiasts, and educators, Omeka is a platform for publishing online collections and exhibitions. Let host your collections, research, exhibits, and digital projects. THATCamp Short for “The Humanities and Technology Camp," THATCamp is a BarCamp-style, user- generated “unconference” on digital humanities. Scripto Scripto is a free, open source tool that enables community transcriptions of document and multimedia files. PressForward PressForward is pioneering new methods to capture and highlight orphaned or underappreciated scholarship and share it with digital humanists across the web. ScholarPress Manage your class, publish research, or collaborate on a conference presentation with this hub for scholarly & educational plugins. Anthologize Anthologize is a free, open- source, plugin that transforms WordPress into a platform for publishing electronic texts. Survey Builder Build online surveys that are especially applicable to oral histories. Timeline Builder CHNM Labs: Easily create and manage a timeline of historical events for your website. Serendip-o-matic Serendip-o-matic connects your sources to digital materials located in libraries, museums, and archives around the world. Web Scrapbook Store all kinds of media items — URLs, images, text, and movies — & collaborate thru the CHNM online scrapbook.
  43. 43. What is Omeka? ‣ Omeka was developed at Center for History and New Media (CHNM) at George Mason University as a "next generation web publishing platform for museums, historical societies, scholars, enthusiasts, and educators." The feature-rich offering provides for the presentation, searching and browsing of digital collections along with a robust metadata management facility.
  44. 44. Situating Omeka
  45. 45. OMEKA Core Features ‣ Based on Open Source Technology: Linux, Apache, MySQL, PHP; ‣ Free to Use, Free to Change; ‣ Easy to Use; ‣ Change Design using Themes; ‣ Add Functionality with Plug-Ins; ‣ Unqualified Dublin Core Metadata; ‣ Strong Support Community; ‣ Extensible, Scalable, Flexible; ‣ Interoperable
  46. 46. What is 'an Omeka' ‣ An Omeka 'instance' contains: ‣ Items (digital Objects of various types) ‣ Collections (of objects) ‣ Sites (set of collections) ‣ Exhibits (curated subsets of site collections)
  47. 47. Exercise Two: Adding Digital Objects to a Collection
  48. 48. Workshop Logistics 1. Hopefully you have been able to register and have confirmed your username and password 2. Please access your User Account on 
 http://* ‣ You are all SuperAdmins – really super! ‣ Our first objective is to Add an Item to the Collection ‣ Follow Along inYour Own Browser
  49. 49. Logging In
  50. 50. The Dashboard ‣ The Dashboard is where it all happens
  51. 51. Item List ‣ All of the digital objects
  52. 52. Add an Item
  53. 53. Specify Item Type ‣ You can select from the default ypes supported by Omeka. ‣ These can correspond to the dc:type but not tied directly
  54. 54. Supported Item Types ‣ Document ‣ Still Image ‣ Moving Image ‣ Sound ‣ Oral History ‣ Email ‣ Lesson Plan ‣ Website ‣ HyperLink ‣ Event (Time-Based Occurrence) ‣ Person (Biographic) ‣ Interactive Resource
  55. 55. Add an Item
  56. 56. Add an Item
  57. 57. Add a File to the Item ‣ You can have one or multiple files; ‣ Depends on type of item.
  58. 58. Add an Item – Optional but Fun
  59. 59. Add Tags to the Item ‣ Why Tags with all the DC metadata?
  60. 60. The Completed Item
  61. 61. Adding an Item and its MetaData ‣ Return to the Item List ‣ Choose Add Item ‣ Take your Metadata record and populate the item record ‣ Dublin Core more info: ‣ 15 Metadata Elements of a generic and wide-ranging number of digital resources; ‣ Each Dublin Core element is optional and may be repeated
  62. 62. WhereWe are At : Item Added ‣ Enter data to the best of your ability for the Dublin Core info - bearing in mind not all fields are mandatory; ‣ Title, Description and Subject important. ‣ Title: ‣ Description: ‣ Subject:
  63. 63. Spend time thinking about your metadata in advance ‣ It’s really about best practice which means although you can touch and feel an object, you must define it properly first
  64. 64. Let’s Take a Look atWhatWe Have
  65. 65. The Steps in Adding an Item 1. Go to the DashBoard 2. View Existing Items 3. Choose Add Item 4. Take the MetadataYou Have along with the Image File and create an Item and locate it geospatially. 5. Choose a Collection to which it belongs 6. Save and you are Done. 7. There is an alternative.
  66. 66. Batch Uploading
  67. 67. Remember this stuff?
  68. 68. Dublin Core in Excel
  69. 69. Batch Uploading
  70. 70. Managing Omeka
  71. 71. The Dashboard
  72. 72. Appearance - Themes
  73. 73. Plug-ins
  74. 74. Users
  75. 75. Settings
  76. 76. Building a Narrative Exhibit Leveraging Exhibit to Tell A Good Story
  77. 77. Create an Exhibit ‣ What is an Exhibit? A carefully composed and curated digital showcase that organizes the images, texts, video, audio, and other uploaded items on your Omeka site into a coherent narrative for people to browse. - Harriet Green, Librarian, University of Illinois Scholarly Commons
  78. 78. Create an Exhibit ‣ Exhibits consist of Sections and Pages and Groups of Collections and Items ‣ The first step is to take the time to plan your exhibit to consider basic user interaction.
  79. 79. Create an Exhibit ‣ Time spent at this stage is
 essential - define the display
  80. 80. ConsiderYour Assets
  81. 81. An Object Driven Narrative
  82. 82. A Collaborative Narrative Platform
  83. 83. Considerations ‣ Browse versus Search ‣ Guided versus Serendipitous ‣ Navigation ‣ Story Arc ‣ The Glue ‣ Varying Levels of Engagement
  84. 84. A Simple Metaphor ‣ Museum ‣ Wings ‣ Rooms ‣ Tours ‣ Objects
  85. 85. A Simple Metaphor ‣ Omeka ‣ Collections ‣ Exhibits ‣ Pages ‣ Items
  86. 86. A Simple Metaphor ‣ Omeka ‣ Collections ‣ Exhibits ‣ Pages ‣ Items
  87. 87. Planning an Omeka Site 1. What is the Primary Goal for the Site? 2. Who is the Primary Audience for the Site? 1. Who Else Might Use the site? - Secondary audiences? 3. What sections will this Site or Exhibit Include? 1. Items: (renamed however you would like Archive/Sources/Objects) links to a browseable list of items, sortable by type of item and tags. 2. Collections (renamed however you would like): groups of items, public can dig through collection to find items. 3. Exhibits: (renamed however you would like) Exhibits contain interpretative text and rely on items/sources/objects as their building blocks. 4. About-- a simple page good for publishing project descriptions, credits, rights, et al 4. Keyword Search box – option to link to advanced search page
  88. 88. Without Magic
  89. 89. Create an Exhibit ‣ Make sure that the Exhibit Plug-In in installed and Enabled
  90. 90. Create an Exhibit ‣ Add an Exhibit
  91. 91. Create an Exhibit
  92. 92. Add a Page
  93. 93. Populate Page Sections
  94. 94. So,Where are we Now?
  95. 95. You can Add Static Page ‣ Use the Simple Page Plug-In to Add A Static Page
  96. 96. Group Exercise : Build An Exhibit
  97. 97. Possible Sources ‣ ‣
  98. 98. Extending Collections
  99. 99. Thinking About Items inYour Site 1. The item is the building block of your site. 1. Add the objects and materials you want to display in your site. 2. Add descriptions using some or all of the standard Dublin Core fields. 3. Once you have items in the Omeka archive, then you can build an exhibit with them or display categories of items organized by collections or tags. 2. Determine the types of items/sources/objects you plan to use in this site: 
 (ie, Document, Still Image, Moving Image, Audio, et al), 3. Do you want to modify any of the item type fields or types? 
 See Item_Types for additional types and explanations. 4. Do you need additional core fields? —> Install the Dublin Core Extended plugin. 5. It is wise to determine before you start building the item archive what type of consistencies you desire in your metadata--this may be especially true for fields such as date, publisher, creator, et al.
  100. 100. What About All those Lovely Plugins?
  101. 101. To Control Data Entry ‣ Establish your own ControlledVocabulary for specific metadata fields? ‣ Make it easier for your team to enter consistent data? ‣ Install SimpleVocab
  102. 102. Use Library of Congress Subjects • Do you want to easily use Library of Congress subject headings? • Do you want to make it easier for entry and ensure consistency? • > Library of Congress Suggest
  103. 103. DoYouWant to EstablishYour Own Taxonomy? • Do you want to establish a controlled tagging schema? • You may add tags to individual items and exhibits; • Before building your archive you may want to devise this schema to help control vocab and spelling; • Tags can help you pull together different items for the purpose of arranging them on a map or creating navigational links to browse items with a specific tag; • This is a standard feature for Omeka Items.
  104. 104. DoYou Have Objects in other Repositories? • You may be able to batch add them into your Omeka site. 
 Can items be exported in a Comma SeparatedValue format? 
 Is there an OAI-PMH harvestable set? • Do you have hundreds of files, or large media files? • Are you using Fedora?
  105. 105. DoYour Objects Have Locations? • Activate the Geolocation Plugin. • You must geolocate each item individually. • A Great way to browse a collection.
  106. 106. DoYouWant to CrowdsourceYour Content? • Collaborate with MyOmeka • Create Custom Tags and Annotations • Collect these to Author Posters • Contribution Plugin • a way to collect stories, images, or other files from the public and manage those contributions in your Omeka archive as items.
  107. 107. DoYouWant to MakeYour Site Social? • Add social bookmarking icons to the bottom of items; • Allow users to share links to that item w/their social networks. • Allow the public to ‘comment’ using the Omeka Comment Plug-In
  108. 108. DoYouWant to Extend a Physical Exhibit? • The Reports And Codes Plugin exports a list of items selected/browsed/matching criteria and generates PDFs of QR Codes. • Use Mobile Devices to Browse Omeka Collectionss for more information
  109. 109. DoYouWant to Have Users Read Supporting Documents Online? • Use the DocsViewer Plugin • Embeds a Google document viewer into item show pages. PDF documents, PowerPoint presentations, TIFF files, and some MicrosoftWord documents are supported.
  110. 110. DoYouWant to Transcribe Items? • Crowdsource the transcription of Omeka Items. • Uses MediaWiki, and Scripto allowing items with files to be transcribed. 
 Transcriptions are then captured into Omeka.
  111. 111. Extending Omeka Even Further ‣ Do you want to allow users to be notified of changes to your items, collections, or exhibits? ‣ —> Atom Output (Atom Syndication Format) ‣ Do you want users to be able to harvest objects to their own bibliographic managers (such as Zotero)? ‣ —> COinS metadata ‣ Do you want to track user demographics? ‣ —> Google Analytics ‣ Do you want to generate derivative images? ‣ —> Derivatives plug-in
  112. 112. DoYou need Help?
  113. 113. Omeka in a Nutshell Pros ‣ Simple ‣ Lightweight ‣ Standards-Based ‣ Extensible ‣ Embeddable in other systems Cons ‣ Scalability ‣ Restrictions on Look and Feel ‣ Extensive customisation means getting into code ‣ A few lingering mobile usage issues
  114. 114. Comparing and Features Server LAMP server required no server required FTP client Required for file uploads and modifying Omeka not required Web-based administrative interface Yes Yes Storage Space Determined by your server admin Determined by your plan: 500 mb; 1 gb; 5 gb; 10 gb; or 25gb File size limitations Determined by your server admin, with ability to use Dropbox plugin for files that exceed that limit. 32 mb maximum Sites per Installation One website for one Omeka installation Depending on plan, multiple sites available managed by one user. Custom Domain Redirects You may point any Omeka installation to any domain name. No redirects available. All sites are subdomains of ( Plugins and Themes Any and all available in Add-ons directory (see more on other pages) Not all Omeka plugins are available for use on .Net. And availability of those plugins depends on the plan chosen (see more on other pages). Pricing Free: all versions of Omeka, and all of its plugins and themes are free and will be always. Free basic plan will always be available, with other options available for small fee: Support User Forums: Help section with detailed instructions: Developers' Google Group: omeka-dev/ Troubleshooting help form: Advanced development: GitHub:
  115. 115. Digital Narrative Alternatives
  116. 116. Alternatives ‣ WordPress ‣ Drupal ‣ Exhibit? ‣ ContentDM ‣ Duraspace (DSpace and Fedora) ‣ MapStory ESRI ‣ NeatLine .... ‣ Noting that Omeka and these all can co-exist
  117. 117. Wordpress
  118. 118. Exhibit
  119. 119. Neatline
  120. 120. ThankYou Shawn Day - - @iridium