Old db, huge HITS table. Is it safe to truncate it?

Omeka Classic Troubleshooting
1

Hello.

I’m trying to recover an old Omeka Classic installation, and while backing up the db I’ve noticed a huge (more than 5 GB) HITS table.

What is exactly the purpose of that table, could its size create any issue (apart from hosting’s limitations on db sizes), and would it be safe to truncate it?

Thanks.

2

“hits” isn’t part of the standard Omeka install. I think it comes from one of the logging/tracking plugins.

3

Guessed so, thanks John.

Btw, is there any literature page where one can see the standard structure of the Omeka db?

4

I don’t think we have a page or anything listing them. You could look at the application/schema folder to see the definitions of the core’s tables though.

1 Like
5

It was created by the Stats plugin

6

The omeka s module Statistics is based on this plugin, but the point is the same: if you have a huge table, it means it is not protected from robots.
In any case, do a backup of the table for future statistics, remove hits from old years and keep only one or two years of data.
Other statistics tools usually create a table by year, but this plugin doesn’t have clearing process. It will be a new feature in the module for Omeka S, but i don’t maintain any more any omeka classic plugin.

1 Like