As a Data Architect at the museum (ELIO), I am responsible for laying the technical foundation for active, scalable, and sustainable digitization.
I manage the digital infrastructure: development environments, servers, storage locations, interfaces, deployment processes, and DevOps structures (HPC). In doing so, I ensure that digitization projects are not developed as isolated solutions, but as stable, reusable data flows.
At the same time, I design data workflows: from data capture and quality control to transformation, enrichment, storage, and provisioning. This includes metadata, images, OCR texts, XML/PageXML, JSON, JSONL, SQL, and NoSQL structures. I ensure that collection data, digitized materials, and research data are clearly described, versioned, discoverable, and machine-readable.
As a data architect, I bridge the gap between subject departments, digitization, IT, and research. I translate curatorial and scientific requirements into technical data models and robust pipelines. My work not only makes digital objects visible but also usable: for portals, APIs, long-term archiving, analysis, AI applications, and future research questions.
In addition, I work on technical workflows for digital object production. This includes 3D modeling processes, batch scripting, Helicon workflows, and Windows-based automation. I support these tasks “on the side” by standardizing recurring steps and making them more efficient.
In short: I build the data architecture and technical processes that enable the digital museum to operate reliably, grow, and share knowledge. Clear structure and concise sentences help document complex work in an understandable way.
