The other day I wrote about the response that we had from the UK’s Department of Health and Social Care. In that reply the DHSC said that it had a problem with some of the evidence we had put forward because “it should also be noted that most of these studies are pre-prints (therefore have not been scrutinised through peer review)”. A few further notes on this.

This week has been one in which my personal and professional lives have aligned in interesting ways. As you may know, one strand of my work focuses on the study of academic publishing, including peer review. This has featured discussions of the idea of “excellence” but also how preprints are viewed in the world.

There’s a lot of focus in the scholarly communications space on transformative agreements for the mega-publishers. Indeed, most of the discourse, most of the time, is about the big publishers in this space. They play Big Bad Wolf with their exorbitant profit margins and make for an easy target.

I was lucky enough, recently, to get a slightly-ahead-of-general-release opportunity to openly peer review Kathleen Fitzpatrick’s most recent book manuscript, Leading Generously . It’s over on HCommons for those who want to take a look and feed in. While there’s much, content-wise, in the book on which I might remark, I wanted, instead, to take a few minutes to reflect on the process of “open peer review” here and how it led me to act.

The title of this post refers not to the classic 1987 single by Run-DMC but, instead, to the trickiness of rheumatoid arthritis and vasculitis as multisystem inflammatory disorders with a range of diverse outcomes.

The next few months mark a series of “10”s for me. On the 10th September, it will be 10 years since my Ph.D. viva. In November, it will be 10 years since I got my first lecturing position (TT Assistant Prof) at the University of Lincoln. It’s 10 years since I met Dr Caroline Edwards and we began publishing Alluvium together. And it’s 10 years since we began planning the Open Library of Humanities.

Affect Theory To be blunt, the past two and a half years have been terrible for me. Certainly, they have been worse for others. But I have spent the last two years feeling that basic activities in public pose an existential threat. The isolation of shielding is bad – but I do have my lovely wife and our little dog, so I am fortunate in that respect.

If you can’t login using the Lastpass CLI tool and it just says “unknown” when you enter your password, there’s a simple fix. Go to My Vault -> Account Settings. In there, press “Show Advanced Settings”. Then set “Password Iterations” to 100100 and follow the procedure. After that, the CLI tool will work again! Lastpass CLI can't login using master password was originally published by Martin Paul Eve at Martin Paul Eve on July 28, 2022.

What is “the scholarly record”? There is some work on this already.

My backup application, django-caretaker, has to reload the SQLite database after it has run the import procedure. Basically, we’re using an external tool to recreate (delete and replace) the original SQL file on disk. But Django won’t always reload this. There are three “gotchas” for how to handle this. The first is that you need a reload function.

There are several tutorials out there on how to get Django apps dockerized and deployed onto AWS Fargate. None of them worked for me. So I have put together a project demonstrating how to do this. It’s available on Github.