Personal Learning Repository in Omeka.net; exhibit building assignment

In my HIST2809, Historian’s Craft this term, I’ve been asking for students to maintain a repository of their learning using Omeka.net. Every time we do an assignment or an exercise, that work is meant to go into their repository. The final exercise in the course is to build an exhibit of their learning progress. Here is the assignment prompt; I thought folks might be interested.

Omeka is not just for storing items. It is also for exhibiting them. Exhibits are built around the idea that you are telling a story with these items. You will have collected many different items over the course of this term.

Your exhibit should tell the story of your learning in HIST2809.

Help in building the exhibit is available here. An example of an exhibit built by a student at Carleton is ‘Black History in Canada

Your exhibit should:

  • be built around at least five items, including your assignment 1 & 2 originals
  • incorporate (either copy or link to) 2 items from SOMEBODY ELSE’S Omeka repository, providing citation to the original item location (see the forum at the top of cuLearn for the URLs to other people’s repositories)
  • link outwards to at least three other sites or sources (eg an item in a library catalogue, public zotero page, Wordle, Voyant Tools corpus, existing online exhibit, photo gallery… etc).

The point of this exercise is:

  1. To learn how to make an exhibit in Omeka, which is an industry standard in cultural heritage circles.
  2. To see how the assumptions built into the platform constrain or enable various kinds of storytelling. ALL digital resources have assumptions about how the world should work built into them, from Google to JSTOR to the Digital Public Library of America. Working inside Omeka.net gives you a glimpse of how these things work from the creator, rather than consumer, side.
  3. To learn how to analyze digital sources as we would any other source

WHAT YOU WILL SUBMIT:

1. A 500 – 1000 word reflection that analyzes your exhibit under PAPER headings, with the URL to your exhibit, with a final section discussing your process in building the exhibit.

We will be grading this document, not the exhibit itself.

So: have a title page with your name on it, your exhibit title, and the direct URL to that exhibit.

Then, for the reflection/analysis, discuss your exhibit AS IF you were considering it as a primary resource, explicitly using the PAPER headings.

You will tell us about

  • your purpose (obviously, you want to tell us about the evolution of your learning, but you might have other goals, too, that are expressed through careful use of colour, or … ),
  • your argument (the way you arrange things, force particular paths through the material, or…),
  • presuppositions (your worldview as it pertains to the role/value of digital work, perhaps; you might feel that this is a waste of time, or you might love playing and learning with digital tools; or you might be ok with digital but see them as mere tools whereas someone else might think of them more like paint & clay, as things to create with: how does that effect what you’ve done or reflect within it?),
  • epistemology (what has been chosen? what has been left out? why? to what end?)
  • and of course, related…

(The ‘R’ part might be the hardest: read, cite, and consider your exhibition in the light of this article http://dare.uva.nl/document/215092 Jose van Dijck, Search Engines and the production of academic knowledge. International Journal of Cultural Studies,13(6):574–592.)

  • INCLUDE a final section that tells us about the problems/potentials you experienced in building this assignment. In what ways does Omeka lean towards particular kinds of stories or paths through material? Does this matter?

A rubric will be provided. The balance of points will be towards your reflection/analysis, rather than the aesthetics of your exhibit.

-> You could have a bare-bones, ugly, exhibit: that would be perfectly ok. We’re not grading on aesthetics. But aesthetics do make a difference for the visitor to your site- an analysis of a bare-bones, ugly exhibit would need to reflect on what that design choice does, for the visitor, in terms of your purpose, argument…

I certainly want you to be thinking especially carefully about the ways ‘argument’, ‘epistemology’, and ‘related’ are reflected in your exhibit.

 

p3d.in for hosting your 3d scans

I’m playing with p3d.in to host some three dimensional models I’ve been making with 123D Catch. These are models that I have been using in conjunction with Junaio to create augmented reality pop-up books (and other things; more on that anon). Putting these 3d objects onto a webpage (or heaven forbid, a pdf) has been strangely much more complicated and time-consuming. P3d.in then serves a very useful purpose then!

Below are two models that I made using 123D catch. The first is the end of a log recovered from anaerobic conditions at the bottom of the Ottawa River (which is very, very deep in places). The Ottawa was used as a conduit for floating timber from its enormous watershed to markets in the US and the UK for nearly two hundred years. Millions of logs floated down annually…. so there’s a lot of money sitting down there. A local company, Log’s End, has been recovering these old growth logs and turning them into high-end wide plank flooring. They can’t use the ends of the logs as they are usually quite damaged, so my father picked some up and gave them to me, knowing my interest in all things stamped. This one carries an S within a V, which dates it to the time and timber limits of J.R. Booth I believe.

logend-edit2 (Click to view in 3D)

And here we have one of the models that my students made last year from the Mesoamerican materials conserved at the Canadian Museum of Civilization (soon-to-be-repurposed as the Museum of Canadian History; what will happen to these awkward materials that no longer fit the new mandate?)

mesoamerican (Click to view in 3D)

PS
Incidentally, I’ve now embedded these in a Neatline exhibition I am building:

3d manipulable objects in time and space

Simple Omeka to Wikitude Hack

I’m working on some projects at the moment, aiming to make augmented reality and cultural heritage discovery easier and gentler for the small scale historical society, student groups, etc: folks with a basic level of web literacy, but no real great level of programming skills.

To that end, here’s something one can do with Omeka, to push items from its database into the Wikitude augmented reality platform.

  1. In Omeka, have the Geolocation plugin installed and working.
  2. Navigate to http://[your omeka site.com]/geolocation/map.kml
  3. You should see the xml structure of your geolocated items.
  4. In a new tab, go to wikitude.me, and sign up for a developer account (it’s free).
  5. Click ‘add new world’.
  6. Click ‘upload KML file’.
  7. Fill in all required fields (you’ll have to create a 32 by 32 pixel icon to serve as a dot-on-the-map, and upload that too).
  8. Under ‘KML/KMZ’ file, click on ‘Enter KML URL’. This will give you a box into which you may paste the URL from #2.
  9. Hit save.

If you’re successful, the next screen will tell you how many points have been uploaded. If, at some later point you’ve added many more items to Omeka, you’ll have to go back to your World in Wikitude and hit save again, to upload the most recent stuff.

Now, with Wikitude on your phone, you might not be able to find your world right away. There’s a solution. If you log back into the Wikitude developer zone, and click on the world you just created, you’ll find a string of letters under ‘developer key’. On your Iphone, go to ‘settings’ , select ‘Wikitude’. Under ‘Developer Settings’, there’s a box for the developer key. Enter that developer key there. Start Wikitude up, refresh the display, and your items from Omeka will be under ‘Around Me’.

…And there you have it. Right now, this just does the basic text descriptions, and the location. By fiddling with the Geolocation plugin code, one might be able to add the other information that Wikitude can display, like images, video, audio, etc.

For a similar approach, but directly from Google Maps, see this video by drmonkeyjcg: