Mobile Apps for Historians – Don’t re-invent the wheel

On #twitterhistorians this morning there is a question from Adam Crymble -” What should a mobile ap for historians be able to do?” which is important and interesting. It is provoked by the fact that there is grant money to spent, in Canada, on such an app for Environmental Historians, and they invited ideas and suggestions. They appear to be going down the road of a portal app, and I’m not sure that is the best thing to do.

Sean Kheraj asks: “What kind of features would you use in a mobile application for environmental historians? Are there important blogs, podcasts, and news sources that we should include in this app?” which looks to me like a portal app, and I don’t like those – too many apps out there are no more than collections of bookmarks or feeds, and no matter how well you do that, it is still just a niche portal (wicked pun there – read Sean’s blog and you’ll see why!). If I was doing that, I wouldn’t spend grant money on it; I’d set it as an assignment for a class of MA students and combine the best elements. To remain useful, any portal app for any discipline needs to be something you can tear down and rebuild every three years as technology, user behaviour and disciplinary perspectives change. The history of grant funding application building in all humanities disciplines is littered with the corpses of  tools which became outdated almost before they were complete.

There are a great many tools which all historians use, but trying to develope a better mobile version of X just for historians wouldn’t work in most cases.  No one with a modest grant is going to develope a better twitter for historians – money, contrary to official expectations, does not spawn great ideas.

It seems to me that the best starting point for any discussion of what historians need in a mobile app is what is distinctive about our disciplinary ways of knowing, of explaining events? And how, in practical terms do we do that on a daily basis?

What we do is causation, in complex events with multiple causes and incomplete evidence. We mostly work with documents, but really now we can use any bit of data that can be digitised and marked up. Tagging is good, but tagging with proper XML based standards is what we need. Old school research manuals still talk about taking notes on index cards, but I never actually met anyone who did that.

There are tools out there that do the notecards idea (Evernote, Catch notes) and allow external tagging of the ‘note’, but not internal markup with an XML based ontology. There are very expensive (overpriced?) tools which allow you to tag parts of visual, audio or video data. There are tools which allow visual representation of relationships – mindmapping tools like Thinking Space are good for that, and The Brain is awesomely cool but, also, alas, closed source, proprietary software so it is never getting my data.  There has even been an effort to create a markup for historical events.

None of these are quite right for historians, yet. They don’t all come together in one package, and they certainly won’t all come together easily in the first version of a  2mb app on a 7″ screen.  But it must be possible to develope a cloud based toolkit with a mobile client that will start to move towards that.  Something that will allow you to tag parts of your note with an XML based ontology that embodies your causal interpretation, and allows you to visualise the relationships that translate ‘facts and dates’ into knowledge. We are some way short of being able to have the sort of gadget that Asimov envisaged for data manipulation in “Second Foundation”, but since mobile devices will in a reasonable time allow us to project on any flat surface, at a quality that real people can work with, we might not be too far away from it. If you have read Second Foundation, you will remember their little data toy; if not, it is your assigned reading for this week!

Happily, there will be an official announcement in a week or two of a Phd programme in Digital Humanities here in Ireland, which will allow me to recruit someone to have a go at something like this. Watch this space.


Posted

in

by

Tags:

Comments

One response to “Mobile Apps for Historians – Don’t re-invent the wheel”

  1. Sean Kheraj Avatar

    Thanks for the feedback on the mobile app project, Mike. We don’t often get much online feedback from other historians so it is always helpful when someone actually writes back.

    For the most part, I agree with all of your comments. A portal app (which is basically what we have proposed) is a very common type of mobile application and we will certainly need to make it something we can “tear down and rebuild every three years”. A great mobile XML markup tool would be fantastic. I would eventually like to build something like that into a photo app (like Jot Not) with instant cloud storage for archive research and digitization of historical primary source documents. But perhaps your PhD programme in Digital Humanities will produce such an application in the near future (I’d be a willing beta tester).

    In defence of our project, I’ll explain a few of the reasons why we are headed in the direction of a portal app:

    1.) This is a small grant, two-person project. As such, we’re fairly limited in what we can do. A portal app is feasible within our funding and timeframe.

    2.) We are absolute programming novices. Part of the intent of this project is for two environmental historians to learn the basics of programming so that they can apply their disciplinary expertise to a digital history project. We’ll be charting this process through our respective blogs and the project website. One of the problems with digital humanities projects is that those with programming skills do not necessarily have the disciplinary skills and knowledge (environmental history in this case) to apply to those projects. Our intent is to, hopefully, be able to teach these basic programming skills in our classes (and not just digital history courses). Too often digital humanities projects only speak to the needs and interests of other digital humanists and by doing so the sub-discipline remains parochial. By learning mobile application development as complete “noobs” we hope to be able to teach these kind of skills to a wider base of history students in the future and better integrate digital history into the broader discipline. In order to do this, we need to start with a manageable project, like a portal app.

    3.) A portal app is accessible to a wide audience of users and can facilitate networking and communication. Part of the mandate of NiCHE (great pun by the way) is to facilitate networking and communication between scholars, public policymakers, and the broader Canadian public. Our project is intended to further this core purpose of NiCHE as an organization.

    These points are not intended to be excuses for the limited scope of this project. I just want to provide a little more background as explanation. I agree that a history-specific mobile tool, like XML markup, could have great impact on the discipline. Given the very limited number of digital history projects of this nature in Canadian history at the moment, this humble environmental history mobile application project is hopefully just the beginning.

    For readers interested in learning more about our project and providing feedback, please visit: http://www.seankheraj.com/?p=1007

Leave a Reply

Your email address will not be published. Required fields are marked *

css.php