Hey everyone, just wanted to share some thoughts on what’s going under the hood here at ArtClerk. We’ve been spending way too much time staring at documentation lately and honestly our brains are a bit fried but it is important stuff if you actually care about your museum’s data surviving the next decade.

People always ask why we bother with all these crazy acronyms like Spectrum or CIDOC CRM and LIDO. It feels like alphabet soup half the time. But the reality is that without them, your collection is basically just a giant pile of digital junk that nobody else can undersatnd.

Take Spectrum for example. It’s basically the gold standard for how we actually do museum work. Not just what we write down, but the process. How do we handle a loan? How do we move an object across the gallery without losing it? If we didn’t build ArtClerk to follow Spectrum, we’d basically be making up our own rules, and thats how things get lost or miscatloged. Trust us, you dont want to be the person explaining to a board why a 17th century vase is “missing” because the software didn’t track the location change properly.

Then there is CIDOC CRM. This one is a beast. It’s not a set of rules so much as a way of thinking about how everything in history is connected. It’s an ontology (fancy word, we know). It lets us link a painter to a specific school of thought, which is linked to a specific geographic region, which is linked to a specific time period. It makes your data “smart” so it can talk to other systems. If you want your collection to be part of the global digital heritage conversation, you need this. It’s hard to implement, but we’re doing the heavy lifting so you don’t have to.

And LIDO (Lightweight Information Describing Objects) is what we use when you actually want to show your stuff to the world. It’s the “harvesting” standard. When you want to push your records to an aggregator like Europeana or some local arts portal, LIDO is the language they speak. It strips away the internal museum “noise” and provides a clean, searchable record for the public.

We know it’s boring to talk about data standards when we could be talking about cool UI features or mobile apps, but this is the foundation. If the foundation is shaky, the whole thing falls apart eventually. We’re commited to making sure ArtClerk isn’t just a pretty interface, but a serious tool that respects the complexity of museum science.

Anyway, back to the code. If you have questions about how we handle your specific data migration or why we chose these over others, just reach out. We’re always down to geek out over metadata.