4.7 years ago by
Yes that doc you were reading is out of date. I have actually been updating reactome.db for a while now (with occasional input from Willem). There has been an updated version every release and they are numbered to match the version of reactome that they contain. But after the most recent update (merely a few weeks ago) the reactome folks pulled the denormalized db dumps from their site. And now I can see why since it looks like the most recent denormalized dumps were not actually ever updated to reactome version 50. That's a bummer since it basically means that the most recent package has some stale information in it (which I am working on getting updated). This is the ultimate cause of both of the different problems that Guangchuang has mentioned. These fields are all ones that originate in the denormalized database.
Anyhow, I am currently discussing a solution to this problem with them but the conversation has been proceeding at a pace of about one reply per day and so it still hasn't wrapped up (yet). It all looks hopeful though (the reactome guys are helping me to know more about what their long term future plans are for this data resource). And we are currently discussing the best alternative routes for me to get the information that previously came from their denormalized database. When the conversation has concluded I will make a new updated reactome.db package I will push it online and post about it here.