If you're interested in scholarly publishing, open access data-as-publication, the taylorization of the academy, and more, you need to go read everything written by Eric Kansa. If you find you can't get the document at the link above, try this: http:/
2 min read
[I've also put the confirmed #DIGH5800 speakers on this schedule]
Oct 6: How we got here, 'code': Jenna
Oct 13: The Crowd: Marissa
[Oct 20: 5800: Gail Carmichael]
[Oct 23: 5800: Damien Huffer]
Nov 3: Viz & Other ways of seeing: Elise
[Nov 10: 5800: Alban Denoyel]
Nov 17: **Attention** You are invited to my book launch on this day, at our usual time, in the Paterson Hall History Department Lounge (4th floor). There will be a digital workshop with my co-author Ian Milligan. This will count towards DIGH5000. Which means Jessie's seminar will be moved to a new date (tba).
Nov 24: Maps & Digitized Space: Jessie (11.35 - 1, Discovery Centre rm 481)
[The 5800: DH Maker Bus Crew - Kim Martin et al session is postponed until further notice]
Dec 1: Images & Audio: Richard
Jan 12: Text analysis: Susan
Jan 26: Algorithmic writing: Alex
Feb 9: Sustainability: Beth & Richard
Feb 23: Scholarly Publishing: Sharon
March 8: Archives & Databases: Justin
March 22: Future DH!: Allie
April 5: DH Primers presentation: Tout la gang.
If you haven't selected a session yet, I think I am going to limit your choices to January 26th, or February 23rd, as there is much there we could cover and two seminar presentations on those days could work nicely. Please consult with the person who has already claimed that spot to ensure that you don't duplicate. Leave a comment on this post to claim your spot!
2 min read
There might be times when having an open online notebook for a digital humanities project makes a lot of sense. Tonight, I came across another static site generator that turns your folder of markdown files into a searchable wiki-style site, with rss feeds (rss is a way of piping all of your content out of your site so that it can be resused in different ways. For instance, you could create a twitter robot - yes, you can! - that tweets every time your site is updated with new content, tweeting links to the specific pieces. Originally, RSS was a way of reading in one place all of your favourite content by 'subscribing' to various websites' feeds).
But I digress.
I've written it all up over on my research blog http:/
The site generator is called 'Pykwiki': http:/
Your totally functional website will be generated in the 'docroot' folder. To put the site online, you'd just move those files into a github repository (or put it on your own server, if you have one) on a gh-pages branch.
(You'll have to look up how to make a gh-pages branch :)
2 min read
Now you've learned how github works, here's a neat way of getting a personal website/journal/open notebook up and running.
1. Fork this repository https:/
2. Rename your copy of the repository in the settings, by hitting the cogwheel icon, and changing the repo name from 'jeckyll-noww' to
3. Click 'rename'. Scroll down - see the green bar that says 'your site is published at shawngraham.github.io!' (yours'll be different, of course). Click on that link - your site is live!
4. If it isn't, we'll just give Github a nudge. On the main page for your repo, click on the file called _config.yml
5. Click the pencil icon, so you can edit it. Change line 6, to put in your name. Go to the bottom of the page and hit the green commit changes button. Open a new browser window, put the URL in:
A more detailed set of instructions is at http:/
You can add new posts to your new blog by cloning the repo on your desktop, and then saving .md files into the _posts folder. Note that the naming convention has to be the same as the example post. Then sync with your repo, and your changes are published to the web!
There are lots of reasons why you might do this, but two very good ones is a) free b) you keep control because your materials are on your own machine c) it's fast - the site is static and so no time is wasted computing what the page ought to look like d) it's secure. Well, more secure than many options (ask me about the Heritage Crowd project sometime).