scRNA-tools low-maintenance mode

scRNA-tools
database
Announcement of the scRNA-tools database entering low-maintenance mode, some more detail and various thoughts
Author

Luke Zappia

Published

March 4, 2024

You are probably here because you have seen or heard that the scRNA-tools database will be entering low-maintenance mode. This post explains a bit more about what that means and some of the motivation behind the decision.

Hang on, what’s scRNA-tools?

scRNA-tools is a database that catalogues software tools for analysing scRNA-seq data which I created during my PhD and have curated and maintained ever since. You can read more about it on the project page, in the original paper and in our analysis of the first 1000 tools in the database.

So, what’s happening?

In May 2024 I will be putting scRNA-tools into what I am calling “low-maintenance mode”. Basically, this means I will stop actively seeking out new tools to add to the database and updates for existing tools. I will still make changes based on user submissions and the existing automated checks but the rate of updates will significantly decrease. Upgrades to the database, website and other code are unlikely to happen unless things break.

That’s sad 😿, why now?

I’m moving onto the next step in my career and can no longer justify the 2-3 hours per week it takes review new papers, curate them and add tools to the database. Transiting to low-maintenance mode means less frequent updates and should reduce the commitment to something I can keep up with, similar to the software packages I maintain. I would love to keep scRNA-tools running as it has but the continuous, ongoing nature of the curation makes it difficult when you can no-longer justify it as “work”, and this will only increase as the field continuous to grow.

I also have to acknowledge that I haven’t developed scRNA-tools as I would have liked over the last few years. There are several new categories and features I wanted to add but, as the typical academic says, I never found the time.

Maybe someone else could take over?

I always wanted scRNA-tools to be a community project so I am definitely open to this but I would need to be convinced that whoever takes over would be able to commit to actively maintaining the project. In the past I have had people reach out to contribute, and even recruited a team to help with curation and expanding the database, but that always petered out after a few weeks or months. I totally don’t blame anyone for that, there is very little for a PhD student to gain from contributing to a project like this, but it does make me cautious about handing over the project to someone who may not end up putting more time into it than I can.

Last thoughts

scRNA-tools has helped record the first years of the single-cell genomics revolution and has been a big part of my work life for the last eight or so years. While I think it is a valuable resource it is also limited, especially as the field expands into other modalities. It will be sad it see it not updated as frequently but it’s time for us both to move on.