Author Archives: Hugh Paterson III

Review of Garmin eTrex Venture HC for Language Documentation

Posted on by
Reply

In a recent (2010-2011) Language Documentation Project we decided to also collect GIS data (GPS Coordinates), about our consultants (place of origin and place of current dwelling), about our recording locations and for Geo-tagging Photos. We used a Garmin eTrex Venture HC to collect the data and then we compared this data with GIS information from Google maps and the National GIS information service. This write up and evaluation of the Garmin eTrex Venture HC is based on this experience.
Continue reading →

Open Change

Posted on by
Reply

I was recently looking at licenses for databases and discovered the ODbL license. This license was pioneered by the OpenStreetMap Project. I was reading their introduction to why the change was needed. This introduction outlined what the change was, what the change would allow them to do, who agreed, who disagreed, what the cost of the change would be, among other things. I thought it was a very open, engaging and confidence building way to move a group of volunteers through change. It allows for more kinds (also different kinds) of product use. It is well worth the look at not only if you are interested in the open licensing of data in databases and why CC-BY-SA and CC0 licenses do not work for data [also as PDF], but also how they are answering the questions of the community as they are moving the community through change.

Social Meta-data collection

Posted on by
3

As part of my job I work with materials created by the company I work for, that is the archived materials. We have several collections of photos by people from around the world. In fact we might have as many as 40,000 photos, slides, and Negatives. Unfortunately most of these images have no Meta-data associated with them. It just happens to be the case that many of the retirees from our company still live around or volunteer in the offices. Much of the meta-data for these images lives in the minds of these retirees. Each image tells a story. As an archivist I want to be able to tell that story to many people. I do not know what that story is. I need to be able to sit down and listen to that story and make the notes on each photo. This is time consuming. More time consuming than I have.

Here is the Data I need to minimally collect:

Photo ID Number: ______________________________
Who (photographer): ____________________________
Who (subject): ________________________________
People group:_________________________________
When (was the photo taken): _______________________
Where (Country): _______________________________
Where (City): _________________________________
Where (Place): ________________________________
What is in the Photo: ____________________________
Why was the photo taken (At what event):_________________________
Photo Description:__short story or caption___
Who (provided the Meta-data): _________________________

Here is my idea: Have 2 volunteers with iPads sit down with the retirees and show these pictures on the iPads to the retirees and then start collecting the data. The iPad app needs to be able to display the photos and then be able to allow the user to answer the above questions quickly and easily.

One app which has a really nice UI for editing photos is PhotoForge. [Review].

The iPad is only the first step though. The iPad works in one-on-one sessions working with one person at a time. Part of the overall strategy needs to be a cloud sourcing effort of meta-data collection. To implement this there needs to be central point of access where interested parties can have a many to one relationship with the content. This community added meta-data may have to be kept in a separate taxonomy until it can be verified by a curator, but there should be no reason that this community added meta-data can not be expected to be valid.

Meta-data Collection Model

However, what the app needs to do is more inline with MetaEditor 3.0. MetaEditor actually edits the IPTC tags in the photos – Allowing the meta-data to travel with the images.In one sense adding meta-data to an image is annotating an image. But this is something completely different than what Photo Annotate does to images.

Photo Annotate

Photosmith seems to be a move in the right direction, but it is focused on working with Lightroom. Not with a social media platform like Gallery2 & Gallery3, Flickr or CopperMine.While looking at open source photo CMS’s one of the things we have to be aware of is that meta-data needs to come back to the archive in a doublin core “markup”. That is it needs to be mapped and integrated with our current DC aware meta-data scehma. So I looked into modules that make Gallery and Drupal “DC aware”. One of the challenges is that there are many photo management modules for drupal. None of them will do all we want and some of them will do what we want more elegantly (in a Code is Poetry sense). In drupal it is possible that several modules might do what we want. But what is still needed is a theme which elegantly, and intuitively pulls together the users, the content, the questions and the answers. No theme will do what we want out of the box. This is where Form, Function, Design and Development all come together – and each case, especially ours is unique.

  1. Adding Dublin Core Metadata to Drupal
  2. Dublin Core to Gallery2 Image Mapping
  3. Galleries in Drupal
  4. A Potential Gallery module for drupal – Node Gallery
  5. Embedding Gallery 3 into Drupal
  6. Embedding Gallery 2 into Drupal

This, cloud sourcing of meta-data model has been implemented by the Library of Congress in the Chronicling America project. Where the Library of Congress is putting images out on Flickr and the public is annotating (or “enriching” or “tagging” ) them. Flickr has something called Machine Tags, which are also used to enrich the content.

There are two challenges though which still remain:

  1. How do we sync offline iPad enriched photos with online hosted images?
  2. How do we sync the public face of the hosted images to the authoritative source for the images in the archive’s files?

Software I would load on my Windows machine, because I can’t on my Mac…

Posted on by
Reply

While I was in Mexico I realized that for the way I work, virtualization was not the best solution… so here is a list of applications I would use:

Scan Taylor http://sourceforge.net/projects/scantailor/
Qiqqa http://www.qiqqa.com/About/Features#Compare
StatPlanet http://www.sacmeq.org/statplanet
FLeX http://fieldworks.sil.org/flex/
SayMore http://saymore.palaso.org/about
Chrome http://www.google.com/chrome/intl/en/make/features.html
GSpot www.headbands.com/gspot/

OS X Error -36

Posted on by
1

I had an OS failure while I was in Mexico. I managed to reinstall the combo update and things started working again. However, some of my big files (movies) will not copy, Time Machine fails, Some PDFs are now failing to copy. It always comes back to a -36 Error. I cannot find the error report for this online. It seems to be some sort of I/O error. I left a comment over on this blog.

prompt%> mv /Users/phil/Desktop/movie.avi .

I tried the command line mv command and the command line told me Input/Output error.

Failed mv

Failed mv

But I can play the file on my harddrive. – I have the same error if I try to copy the file to somewhere else on my internal harddrive.
Using OS X 10.6.5 on MBP 15″ moving the file to a WD My Passport via USB. The file in question is a .mts movie file. I can move other .mts movie files which were made with the same camera, at the same time, and are in the same folder to the external hardrive.

Error -36

Error -36

I can’t figure out why I have this error or how to solve it.

Network Language Documentation File Management

Posted on by
Reply

This post is a open draft! It might be updated at any time… But was last updated on at .

Meta-data is not just for Archives

Bringing the usefulness of meta-data to the language project workflow
It has recently come to my attention that there is a challenge when considering the need for a network accessible file management solution during a language documentation project. This comes with my first introduction to linguistic field experience and my first field setting for a language documentation project.The project I was involved with was documenting 4 Languages in the same language family. The Location was in Mexico. We had high-speed Internet, and a Local Area Network. Stable electric (more than not). The heart of the language communities were a 2-3 hour drive from where we were staying, so we could make trips to different villages in the language community, and there were language consultants coming to us from various villages. Those consultants who came to us were computer literate and were capable of writing in their language. The methods of the documentation project was motivated along the lines of: “we want to know ‘xyz’ so we can write a paper about ‘xyz’ so lets elicit things about ‘xyz'”. In a sense, the project was product oriented rather than (anthropological) framework oriented. We had a recording booth. Our consultants could log into a Google-doc and fill out a paradigm, we could run the list of words given to us through the Google-doc to a word processor and create a list to be recorded. Give that list to the recording technician and then produce a recorded list. Our consultants could also create a story, and often did and then we would help them to revise it and record it. We had Geo-Social data from the Mexican government census. We had Geo-spacial data from our own GPS units. During the corse of the project massive amounts of data were created in a wide variety of formats. Additionally, in the case of this project language description is happening concurrently with language documentation. The result is that additional data is desired and generated. That is, language documentation and language description feed each other in a symbiotic relationship. Description helps us understand why this language is so important to document and which data to get, documenting it gives us the data for doing analysis to describe the language. The challenge has been how do we organize the data in meaningful and useful ways for current work and future work (archiving)?People are evidently doing it, all over the world… maybe I just need to know how they are doing it. In our project there were two opposing needs for the data:

  • Data organization for archiving.
  • Data organization for current use in analysis and evaluation of what else to document.It could be argued that a well planned corpus would eliminate, or reduce the need for flexibility to decide what else there is to document. This line of thought does have its merits. But flexibility is needed by those people who do not try to implement detailed plans.

Continue reading →

EGIDS, SIL, and Language Documentation

Posted on by
Reply

About two or three weeks ago Gary Simons and Paul Lewis co-presented on an Extension to Fishman’s Graded Intergenerational Disruption Scale (Lewis & Simons 2010) [1] Paul M. Lewis & Gary F. Simons. 2010. Assessing endangerment: Expanding Fishman’s GIDS. Revue Roumaine de Linguistique 55.2: 103–20. . Fishman’s scale for measuring Language Vitality and Language Endangerment has been around for about 2 decades (almost longer than me ;-)). The Ethnologue in its most recent version has started to list the position of the language on the EGIDS scale. This is something that the editors are looking to expand to all languages in the Ethnologue. This has some bearing on Language Documentation globally (as grant writers and funders look at EGIDS as a pivot point for language vitality) and because Language Documentation efforts usually (and typically) focus on languages on a 7 or higher on the scale (Shifting, Moribund, Nearly Extinct, etc). Continue reading →

References

References
↑1 Paul M. Lewis & Gary F. Simons. 2010. Assessing endangerment: Expanding Fishman’s GIDS. Revue Roumaine de Linguistique 55.2: 103–20.

Finding that Apple command symbol

Posted on by
1

I have always wanted to be able to type the ⌘ symbol for various reasons, including writing tutorials, but I have not know how to access it through my keyboard. A few, general, related notes:

  1. There is a nice wright up including some history on the Command Key, ⌘ on wikipedia.
  2. How Apple Keyboards Lost a Logo and Windows PCs Gained One
  3. PopChar is an application which helps users find obscure characters.
    PopChar

    PopChar is a utility for helping users find the Characters they are looking for

    This functionality is built in to OS X with Character Viewer, though it is likely that PopChar extends the user experience in some way.
    CharacterViewer-with-highlight

    OS X Character Viewer

    Shiftkey-in-characterViewer

    Shift Key in Character Viewer

  4. This discussion on the Apple Forums talks about a way to put these symbols in Pages’ auto correction so that Pages will auto correct a set of characters typed to the symbol desired. I have seen this used in MS Word too.
  5. A table of Unicode characters corresponding to Macintosh keyboard symbols, as they commonly appear in menus.

    6. The Next two Links are more detailed but like the above.

  6. Special Key Symbols
  7. Apple Keyboard Symbols

    8. Marginally relevant:

  8. Multi-stroke Key Bindings
  9. Keystroke mapping explained by SIL’s NRSI.

It is unicode point 2318 (the html hex code is ⌘ ) and so you can find it in the character palette under:

  • Code Tables>Unicode>2300>2318

    • or you can go into

  • All Characters>Symbols>Technical Symbols

.

Apple ⌘ symbol

Apple ⌘ symbol

There are a few other ways to get at it, but that should do it for you.

On OS X, if you switch your keyboard to Unicode Hex Input, then holding down opt allows you to type the four digits for a unicode symbol and get the ⌘ (2318).

The Alt/Option Symbol has also been elusive. It can be fount at Unicode point 2325. U+2325.

Alt Key U+2325

Alt Key U+2325

Unicode and Hex Keyboard symbols
⌘ – ⌘ – ⌘ – the Command Key symbol
⌥ – ⌥ – ⌥ – the Option Key symbol
⇧ – ⇧ – ⇧ – the Shift Key (really just an outline up-arrow, not Mac-specific)

⇥ – ⇥ – ⇥ – the Tab Key symbol
⏎ – ⏎ – ⏎ – the Return Key symbol
⌫ – ⌫ – ⌫ – the Delete Key symbol