October 20, 2024

My micromount collection database

I keep a record of my micromount collection in a database. This serves a variety of purposes. One is that it lets me look up things I have. I can do a variety of searches, including looking for all I have of some species, all the specimens I have from a given location and so on. I can find specimens that list a certain species as an association. I can keep "extra" information that doesn't go on the label such as when and where I got it, from who, how much I paid if I bought it. I can add any notes that seem pertinent. I can keep information about where the specimen is stored.

At least as important as any of that is that it lets me generate labels. I decided there was no possible way that I was going to do what some people do, namely use one system to track their collection and another to make labels.

Under the hood, my database is an sqlite3 database. My database application is a front end that handles entry of new records, searches, and label generation.

It is all open source and on Github for anyone who wants to use it.

Ruby on Rails (obsolete)

I used to use a ruby on rail application to handle my micromount database. Rails is such a disaster and train wreck, that I abandoned that and converted my application to a ruby application. That had issues that arose due to ruby versions and problems with gems and packages. Nothing like the chaos and misery I experienced with rails, but it was still so bad that I finally rewrote the whole thing in python.

Feedback? Questions? Drop me a line!

Tom's Mineralogy Info / [email protected]