It is a good time to discuss that though as we are making some fundamental changes in KCIDB to improve performance and allow it to be more agile in how we deal with the various needs we are seeing from the community. In a nutshell, we are creating a new interface to publish the data to KCIDB and also allow easier local dev env for people to try it out. Thinking about your need here, maybe we could go as far as having an endpoint in the new KCIDB api that consumes the xml directly and do the translation internally. We should also look if the schema is enough for you or new additions may be needed. For context, for those not aware with the new KernelCI infra. KCIDB data is the backend of our https://dashboard.kernelci.org/ and https://kci.dev/ cmdline. Mind you that both project are quite new and will grow more and more functionality over the years. We'd be happy to collect your usecases and see how we can evolve our infra, dashboard, etc. Best, - Gus