Accessing parser data through Metabase

Now that you are done with creating your parser, which is actively tracking your data, parsing it, and saving it to a Postgres database, let’s move to the question of how to access the data?

For data access, we provide add-ons to our users. One of these add-ons is Metabase.

Metabase is an open-source tool to help you extract information from your data. You can use Metabase to build out beautiful internal and public dashboards, save and share queries, etc.

Before getting started with Metabase, let’s revisit the structure of your indexed data.

Understanding the structure of your data

In the previous section Setting up an Indexer Using Ordium Parser , we deployed a parser for the ORDIUM ERC20 contract, we will continue to use it as an example.

• When you create your parser you are asked to enter the schema name in which your data is to be indexed. The schema name corresponds to a schema in Postgres.

• Don’t remember the name you gave? The name of the schema where your parser is writing data can be found upon clicking on a respective parser.

• As initially mentioned, all of your data tables are saved under this schema.

• The data of each of the contract events/functions selected for indexing(at the time of parser creation) is saved into corresponding tables.

Table nomenclature

• All the table names are in snake case and are postfixed with _events and _methods for event and function tables respectively.

For example, if we selected the following events and functions for indexing

1. Events: Approval, Transfer

2. Functions: transferFrom

We could expect to find the following tables in our schema

1. Event tables: approval_events, transfer_events

2. Function tables: transfer_from_methods