Status update

I’d like to share a status update on the Open Journal Matcher. As I’ve mentioned before, I have a grant to refactor and make the OJM more sustainable. I’m considering two different approaches to the rewritten OJM. The first relies entirely on PythonAnywhere, while the second still involves Google Cloud Platform. This post describes where… Continue reading Status update

The latest abstracts

Right now, as I type, I’m downloading the latest English-language abstracts from the Directory of Open Access Journals API. This is something I do periodically, to refresh the data used by the Open Journal Matcher. I do this regularly in part because new journal articles are published all the time, and it’s obviously valuable to… Continue reading The latest abstracts

Costs of development

Developing a project, even a small one, can be expensive. From when I started working on the Open Journal Matcher in earnest (in January) to when it was more or less complete in its current form (in the beginning of October), I probably spent about $1000 of my grant money. To me, this is a… Continue reading Costs of development

Building incrementally

As soon as I finished the Open Journal Matcher and released it to the world, I wanted to rewrite it from the ground up. When I looked at the code, it was clear that so much could be improved: from better variable names, to clearer flow, and more concise functionality. I had to resist the… Continue reading Building incrementally

Slow down, be thorough

Since (for now) the Open Journal Matcher is built without using a proper task queue, I’ve been spending a lot of effort handling the various errors thrown by my Google Cloud Function. This is both satisfying and annoying: it is nice to catch and handle each error properly, but it takes some digging to figure… Continue reading Slow down, be thorough

On variable costs

Now that the Open Journal Matcher is live and receiving traffic, I’m wondering how much it is going to cost to keep running. There isn’t an obvious answer. Mostly this is because Google Cloud Functions scale with your project. This is definitely good for scalability and availability, but it makes it much more difficult to… Continue reading On variable costs