There are a couple of indicators in the initial message that may rule out the Group By option. For example, @Gene_Howell says “many databases”. Before approaching any implementation strategy one might want to know more about the underlying data model. Are these separate bases? Separate tables? Separate views?
@Gene_Howell also mentions the need for a separate database showing the analytics of the day’s activity. Indeed, something like this is straightforward until you factor in the deeper requirements which may include the [potential] confidential nature of a leader board for the collection agents.
Analytics are typically data assets that need to be harvested and aggregated with clear separation from the people who generate the raw data. As such, many of the seemingly obvious and simple ways to collect and roll up metrics in Airtable may actually expose information making it possible for users to “game” the system.
Like the blood-brain barrier in humans, performance analytics must also have a degree of separation to avoid potential issues while creating sound data for decision-making. Just sayin’ …
In my view, analytics of this nature should require no additional effort by the people and activities being monitored. It should just happen quietly behind the scenes. Certainly, some data should be gathered through process touch-points, but these tend to measure process compliance, not productivity or outcomes of process compliance.
To do analytics well, it’s important to be able to assess data changes over time to extract user behaviour even when they don’t follow process.
