Show all events for a specific account. We already show all events in the current version of Polkascan, however this time we want to harvest the relationship between these events and accounts they operate on. For this, the back-end needs a new ETL process and harvester logic to collect this data and an extension of the GraphQL service to expose it. The event attribute data will also be provided int the GraphQL query result. For more detailed information on the event, the state at a given block doesn't need to be harvested on the back-end, but can be fetched on the client using the SubstrateRPCAdapter. On the front-end (and thus in the GrapQl service) there will be a filter for the runtime version, pallet, type of event, date range, and block range. Creating the ETL process involves some complexity in determining how the JSON data is best collected and interpreted. We are only interested in specific events with certain attributes. Event specifications can be different between runtime versions, so we need to break down metadata for each version.
Show all events for a specific account. We already show all events in the current version of Polkascan, however this time we want to harvest the relationship between these events and accounts they operate on. For this, the back-end needs a new ETL process and harvester logic to collect this data and an extension of the GraphQL service to expose it. The event attribute data will also be provided int the GraphQL query result. For more detailed information on the event, the state at a given block doesn't need to be harvested on the back-end, but can be fetched on the client using the SubstrateRPCAdapter. On the front-end (and thus in the GrapQl service) there will be a filter for the runtime version, pallet, type of event, date range, and block range. Creating the ETL process involves some complexity in determining how the JSON data is best collected and interpreted. We are only interested in specific events with certain attributes. Event specifications can be different between runtime versions, so we need to break down metadata for each version.