Machine Learning is one of those hot topics at the moment. It’s even starting to become a really hot topic in the Humanities and, of course, also in the DH. But Humanities and Machine Learning are not the most obvious combination for many reasons. Tutorials on how to run machine learning algorithms on your data are starting to pop up in large quantities, even for the DH. But I find it problematic that they often just use those methods, just show you those few lines of code to type in and that’s it. Frameworks have made sure that ML algorithms are easy to use. They actually have a super-low entry level programming-wise thanks to all those libraries. But the actual thing about ML is that you need to understand it or it’s good for nothing. (Ok, I admit there are some uses which are pretty straightforward and don’t need to be fully understood by users, such as Deep Learning powered
You might have seen that I have written a little bit about #100DaysofX projects and challenges (such as the #100DaysofDH
Do people think that you, as a DH person, are also responsible for your project’s outreach activities yet nobody considers
Do you need to make a vector logo for your project but have no idea how? Do you want to
Your digital project is great, I’m sure of that – but does it even exist if nobody knows about it? Science communication is the answer to avoid this philosophical dilemma. In this short post, I wanted to share a list of quick-and-easy-to-implement ideas to add some science communication to your projects. This is just a short post to give you some ideas, not tutorials on how to do it. However, I am open to any tutorial requests you might have on the topics involved. As for the Twitter bot, there is a short post available already. So let’s get to it! Quick and easy strategies to #scicomm your DH project Create a better / thematic / facetted search interface. Maybe people aren’t using your data because the interface is not intuitive and they can’t find things or don’t know what to look for and where to look. This is the basic building block to build all the following things on.
As you probably know, I started the #100DaysofDH challenge on this blog during the first few weeks of Covid lockdown.
This post wants to convince you to try out creating a Twitter bot using Python Tweepy and AmazonAWS Lambda because it’s easy and fun. Of course, you can use any other utilities but Tweepy and AWS Lambda are the ones I tried. This is not a full tutorial but I can make one if anyone is interested. Inspired by the #100DaysofDH challenge In this post, I will just give you some basic Twitter knowledge, links for what you need to know to get it done and a link to the github of my #100DaysofDH challenge for which I implemented such a bot. If you want more guidance, please let me know. Also, read the post on the challenge because I noted down some restrictions I realized the Twitter automation guidelines impose on bots as I went along. In my example, I think I’m in fact doing one or two things which you actually shouldn’t do (I think bots shouldn’t like
Dear friends, today I want to illustrate some trans-disciplinary crossovers (into the DH) gone wrong. In earlier posts, I have already explained some of the dos (Looking at data with the eyes of a Humanist: How to apply digital skills to your Humanities research questions and Formulating Research Questions For Using DH Methods and What are ‘real’ Digital Humanities and how to get started?), so I assume I have you covered in that area. This is all very happy and positive – but I think I also owe it to you guys to give you an honest opinion of where you probably fucked up. It always hurts to learn these things and it’s more butterflies and rainbow-sprinkles to list all the empowering things you can do. But there are some traps as well and we don’t want you to fall into them. And if you already have, at least now you’ll have the closure to understand why you maybe have gotten rejected
I have been following the #100DaysofCode community for a while now and thought that it was sad that there didn’t seem to be a connection with the DH community. 100 Days of Code is such a great project which is motivational for those willing to learn but also a great way to foster a community. So I thought, why not start #100DaysofDH and I did. Looking forward to your contributions! The main activity around this will be happening on Twitter (account is @100DaysofDH, hashtag #100DaysofDH) but there is also a minimalist github.io page: https://100daysofdh.github.io/ On the github, you can also find the current state of the Tweepy and AWS-powered bot. The story behind the creation of this challenge Before getting into the details of how the challenge works, let me share some thoughts that I had in mind for the adaption of the 100 days challenge to the DH (skip this part if you just want the rules which can
A few weeks ago, I posted The Computational Humanities and Toxic Masculinity? A (long) reflection and didn’t know what reaction to expect. It would either be a shitstorm or get ignored, I assumed. It turns out, however, that the timing might have been just right, since I was contacted by the (informal) Turing Institute reading group – they wanted to discuss my blog post. I was honoured that they did and that I could participate. Here I wanted to share some new insights and reflection prompts this discussion has sparked for me. First things first: Thanks for everyone who participated! First of all, I was happy this discussion happened at all. That’s exactly the type of thing I had aimed for with the post, yet I was pretty surprised it actually happened. After all, you normally don’t always get you want. Maybe it’s that help will always be given at Hogwarts to those who ask for it. 😉 So anyway,
In my recent post on how to get started doing DH, I basically said that the essence of being DH is looking at data with the eyes of a Humanist and gave some tips on how to get started in just 10 days. However, it’s not that easy. Learning digital skills and the problem of skill transfer A problem I see a lot is that H people fail to transfer their newly won practical DH skills to their own research questions. They don’t know how to look at their own material as data. They don’t know how to leverage digital methods to help answer their own research questions. But if it isn’t compatible with their own research, they’ll never deepen their knowledge enough to actually profit from their DH skills. If you don’t use them, they are forgotten quickly. So how do you make this transfer which I think is, so far, being neglected as a skill which has to
Today, I want to talk about the Computational Humanities discussion from last year and finally say something with regard to the gender issues in it. I called this post ‘Toxic Masculinity?’ and maybe that’s provocative to you. But maybe it also correctly describes a situation which could come to pass in the DH – a discipline which considers itself so forward-thinking – if we don’t take lurking issues seriously. So this is my reaction. Some disclaimers and considerations I wanted to respond to this discussion when it originally came up. Then I didn’t dare to post it because I was kind of afraid there would be a bad reaction, especially as the slightly-shitstorm-like situation was still fresh and I didn’t want to offend anyone. So I didn’t and now it’s all kind of too late and not up-to-date anymore. But since the general subject is still relevant to me, I decided to use this Corona situation to write up this
In the feedback forms I did on the DH classes I have taught over the last years, I got one feedback I didn’t expect: People were extremely grateful I had practiced with them how to formulate valid research questions which, apparently, no one had ever (really) done with them before. I found that quite astonishing because the DH are all about methods and methods are like specizalized tools. You need to know what you can use them for. So here’s the crashcourse. The Hammer and the Nail I want to start off with an analogy. A hammer is a specialized but not an extremely specialized tool. You can use it for a range of tasks, however, not all tasks are going to work equally well. Some might work but would actually require a more specialized tool if you had one. You can really use the hammer on about anything and almost always, something is going to happen. For example, you
It’s not Sunday but since no one really cares anymore what day it is lately with this Corona lockdown situation,
Dear people, today I wanted to point you to a new github repository where I started to share some of
As per request, I wanted to address the subject of JATS-XML to LaTeX transformations today. The post might be interesting for you still even if you’re not particularly interested in said transformation since it will address more general requirements for transformations as well. What is JATS-XML and why would we transform from and into it? First things first: What is JATS-XML? It is an XML standard called the Journal Article Tag Suite (JATS). Journal Article Tag Suite … is an application of NISO Z39.96-2019, which defines a set of XML elements and attributes for tagging journal articles and describes three article models. The content on this site is the supporting documentation for the standard. JATS is a continuation of the NLM Archiving and Interchange DTD work begun in 2002 by NCBI. (source & JATS documentation) It has the <article> element, and in that, you get <front>, <body>, and <back>. Learn more about it and see examples in the links.
I don’t usually do self-promotional posts, but today I’ll make an exception: The LaTeX Ninja blog’s DH category was nominated for the DH Awards 2019. So I warmly encourage you to vote for the Ninja and share this – because, as the site’s 2019 FAQ state quite clearly – in the end, the DH awards are a popularity contest. So this is the reason for some shameless self-promotion today. I’ll be back with useful content soon. But this also serves me well in terms of my own blog time management since I’m currently too busy with conference organization to able to provide an insightful thoughtful blog entry. Generally, anyone can vote – you don’t even need to be in the DH yourself! So please do vote and get your grandma to vote too 😉 Am I allowed to vote? Everyone is allowed to vote, voting is entirely open to the public. You do not even have to view yourself as
In this post, I will explain how you can use the filecontents package to create an ‘inline’ .bib file inside your main document.tex . This can, for example, be useful if your LaTeX gets compiled on a server and your method only allows you to pass one single document. If you wanted to pass a .bib file with it, this wouldn’t work out. Also, for LaTeX releases past fall 2019, the package is no longer required for this functionality, you can use it directly as an environment. I’ll still keep this the way I wrote it. See the documentation here. Premlinaries: How I ended up writing this That’s what I initially wrote this little method for: Our publication system archives data following the single source principle: This means that all representations you want, such as a web site or an output PDF, will be generated from one single document. In our content management system, my data are encoded in TEI
The title suggests a political discussion, however, this is not what I want to discuss here. (However, I had a ‘more political’ discussion planned for a while.) At a recent conference, I realized many people from the Humanities find it difficult to grasp what the DH even really are – because they are so diverse. I was told a colleague had gone to a short DH summer school but still feels like she doesn’t get what the DH really are. Or that she hasn’t learned any ‘real DH’. How does this happen? How can we make it better? Maybe, as a first step, by trying to answer what the DH are in a way which is easy to grasp for someone who isn’t already part of the DH: It is really an umbrella term for a wide range of topics ranging from digital edition to long-term archiving, digitizing facsimile scans of books or running analyses. I don’t promise to unveil