SEASR for Digital Humanities
June 9th, 2011 by vikaThis week I’m at my second Digital Humanities Summer Institute at the University of Victoria. Last year, I took the large project management course, and it was tremendously useful in managing several projects, including ESTHR. This year I decided to try my hand at SEASR (pron. “Caesar”), or Software Environment for the Advancement of Scholarly Research.
The complex toolkit has great potential. The course has been frustrating, in part (though not wholly) because SEASR’s documentation is not at all geared toward your average digital humanist, or what I know of my diverse kind, anyway. I thought that the best thing I can do with my class time today was to write some documentation. Here it is. It’s in no way complete; just the beginning of an overview of SEASR for digital humanists. Please feel free to repost, augment, comment here with your augmentations and have me edit this post to reflect them, what have you.
At the end of this post, I propose the beginning of a list of categories into which all components and flows might be subdivided, each component/flow probably listed in more than one category. This would help humanities scholars with no prior experience with SEASR, or even some of the functionality it affords, get oriented in using it.
I also propose that we need a lot more detailed information for each component and flow. The SEASR team has already begun this process, but given the project’s maturity and the fact that it’s in its third year of being taught at DHSI, such (again, humanities-scholar-oriented) documentation is sorely lacking.
I should say that, unless ESTHR or another one of my projects decides to pursue use and development of SEASR, I am unlikely to add to its documentation after the end of this week. I ardently encourage SEASR’s developers and managers to devote significant resources to documenting this great project, such that it may be usable by the wide diversity of researchers who stand to benefit by it.
OK, here we go with the overview. Read the rest of this entry »