Initial sketch

[alecandido]

• insert in collection
  • start testing with single collection (e.g. platform.QPU)
  • always insert many
• insert in database bundle
  • this will be the "runcard" mode, so with a single runcard, that will multiple collections with potentially multiple documents
  • the layout will be at the level of the DB enum (e.g. Platform)
• read a record (given an ID)
  • in CLI (dump to stdout or file)
  • in Python (returning suitable object)
• read a bundle

[stavros11]

Are we planning to have these objects here or in qibolab? Because at the end these are the pieces we need to put together a Platform, so I am not sure if it makes sense to have them both here and also in qibolab.

[alecandido]

Here I need them, because I have to specify the collections (tables), but I don't want to have a Qibolab dependency.

In the end, Qibolab will make use of this DB, so it will receive objects from here (same Qibocal).

However, to which level these objects are enough for Qibolab and Qibocal I'm not sure. They will not provide any API, just the data. Thus, all the methods and domain logic will be specific to the other packages (in principle you might consider to have wrappers, and use these in Qibolab as well to hold data).

[stavros11]

For example, this could be exactly the object I was trying to describe in qiboteam/qibolab_platforms_qrc#5 (comment)

[alecandido]

I know, I had already written it when I was reading your comment :P
(it's there since yesterday)