Metadata and a data catalog

CoreData EngineeringData Platform EngineeringData Catalog & Metadata ManagementWeb Application DevelopmentBusiness Process Improvement & Automation

Organisation: MIIDAS CO., LTD.
Period: Jul 2025 – Present
How it started: Self-initiated
My part: Proposal through build and operation, alone
For whom: My own team
What changed: Definitions and ER diagrams scattered, investigated each time → One generated catalog to look everything up in
Scale: 2,656 table definitions (as of July 2026), across multiple databases and schemas

What I did

Proposed and built the data catalog platform, cutting the investigation that used to precede every extraction.
Keep the automatic collection and publication of table and column definitions running.
Contribute back to the OSS it runs on (tbls) through bug reports and improvement proposals.

Adding business meaning on top of the generated definitions, starting with the data people ask about most.
Bringing table dependencies and lineage into the catalog.
Deciding what belongs in the catalog and what does not.

Combined tbls and Docusaurus so the definitions collected straight from the databases become the published catalog.
Scripted the work that recurs in operation: multiple databases and schemas, masking information, sidebar generation.

Writing

Extraction that goes inside the implementation, visualisation that serves the business goal.
I work alongside the business from the definition of the metric itself, and stay with it through to the insight it was asked for. From IoT systems to web and mobile, I have broad experience of building software, so I extract data with a deep understanding of the implementation behind it. Visualisation and analysis are the same — I put generative AI to work and deliver quickly, in the form the person will actually use. Underneath that, I can shape the data, the context around it and the ETL that feeds it for the age of generative AI, so that people and AI alike can work with what is there.

I do not stop at what the tool allows
When Grafana or WebPerformer could not do what was needed, I wrote the plugin or the surrounding tooling myself. When the open-source catalog we depend on, tbls, fell short, I filed the issue and the pull request. I read the documentation and the source, and I keep digging until I find the route that actually serves the goal — and where the result is worth sharing, I share it.