I have just updated my agent-based model on political participation to NetLogo 6.1.1 over at CoMSES. The model has not changed since 2005, but this way the model remains immediately accessible to anyone interested in an ABM implementation of Milbrath’s model of political participation.
Apart from my MSc thesis, I have used the model in two papers:
More recently, I have applied some of these insights in a survey — for which I got support by Rosita Fibbi — and a quantitative regression analysis:
If you aren’t, you should be using Zotero. It amazes me to see researchers ‘managing’ their references manually these days. It’s complicated, takes time, is prone to errors, and simply unnecessary. There are many options out there to manage your references, but you should look at the free and open Zotero. You can install it on all your devices, you’re not limited in the number of citations you can use, you can take it with you when you change workplace, and in fact you’re not even restricted to the feature of Zotero because you can use plugins. Seamless integration in word processors isn’t going to stand out from the competition, but getting stuff into Zotero takes no effort at all — it’s unparalleled easy with just one click in your web browser. You get free syncing, too. There really is no reason not to keep notes of what you are reading.
After grabbing Zotero, you probably want Zotfile, too. Zotfile manages your PDF versions of research articles. In my view, the most useful feature is the ability to extract highlighted text from the PDF. It’s so practical that I sometimes even don’t take proper notes (for the main points, you should store them in your brain anyway).
Image credit: Zotero, Zotfile
2018. Github ·
Ruedin, Didier. 2018. Housing Randomizer. LiveCode. Github. https://github.com/druedin/housing_randomizer.
Housing Randomizer for a field experiment on discrimination in the rental housing market. I have created the program in LiveCode, adopted to cater for three languages (German, French, Italian).
I have recently explored open-source approaches to computer-assisted qualitative data analysis (CAQDA). As is common with open-source software, there are several options available, but as is often also the case, not many of them can keep up with the commercial packages, or are abandoned.
Here I wanted to highlight just three options.
RQDA is built on top of R, which is perhaps not the most obvious choice — but can have advantages. The documentation is steadily improving, making it more apparent how RQDA has the main features we’ve come to expect from CAQDA software. I find it a bit fiddly with the many windows that tend to be opened, especially when working on a small screen.
Colloquium is Java-based, which makes it run almost everywhere. It offers a rather basic feature set, and tags can only be assigned to lines (which also implies that lines are the unit of analysis). Where it shines, though, is how it enables working in two languages in parallel.
CATMA is web-based, but runs without flash — so it should run pretty anywhere. It offers basic manual and automatic coding, but there’s one feature we really should care about: CATMA does TEI. This means that CATMA offers a standardized XML export that should be usable in the future, and facilitate sharing the documents as well as the accompanying coding. That’s quite exciting.
What I find difficult to judge at the moment, is whether TEI will be adopted by CAQDA software. Atlas.ti does some XML, but as far as I know it’s not TEI. And, would TEI be more useful to future researchers than a SQLite database like RQDA produces them?
Some time ago, I came across a blog post highlighting how open-source contributors can be alienated by maintainers. Tim Jurka describes his unpleasant experience of sending an updated version of an R package to CRAN. He highlights the short and impersonal messages from CRAN maintainers, an apparent contradiction, and generally felt alienated by the process. Interestingly, there are four lessons to be learnt offered:
– don’t alienate volunteers — everyone in the R community is a volunteer, and it doesn’t benefit the community when you’re unnecessarily rude.
– understand volunteers have other commitments — while the core R team is doing an excellent job building a statistical computing platform, not everyone can make the same commitment to an open-source project.
– open-source has limited resources — every contribution helps.
– be patient — not everyone can operate on the same level, and new members will need to be brought up to speed on best practices.
I guess everyone would sign up to this, but oddly enough my experience with the team running CRAN has always been of the nature Tim Jurka cites as a positive example: brief, but courteous. What is definitely missing from said blog post, though, is an appreciation that the team running R and CRAN are also volunteers!