Molecule Event Sourcing

Besides just storing structures and their IDs, Molevent stores events. These events can be used:

  1. By people who’re looking the info about who/what/when worked on that molecule

  2. By software that wishes to do lookups. E.g. if you start an ELN page and draw a compound, you’d probably be interested if someone else already worked on it? Well, your ELN can access Molevent for this information.

Event information

Every time you draw something, synthesize, purify, assay - Molevent stores:

  1. A timestamped record of that event

  2. Metadata with the most important properties

  3. A so-called "context" - a grouping of molecules when more than one compound participated in the action. E.g. if chemists ran a parallel experiment. This allows to connect the event to other related events.

  4. Link to the target system endpoint where the rest of the information about the event can be found (if target system has API)

  5. Link to the target system page, so that the scientist could open and view the information in browser (if target system has web interface)

Filling the database

In order for Molevent to know about the event, we need to record it. For this reason we write so-called ETL processes that extract the information from one system and load it into ETL.

Molevent already has some systems supported, like Revvity Signals for instance. We can add support for other off-the-shelf products or instruct/help with your in-house systems.