Hi Adam,
Yes, this should be achievable, although combining historical view counts with metadata from the currently published version is the part I'd validate first.
I'd start with the Knowledge Use (kb_use) table, filtering on Viewed = true and Created within the last six months. From there, aggregate views by article number across versions and sort descending.
The complication is that the Can Read criteria and KB Category need to come from the currently published article, rather than whichever version generated the views. A standard grouped report may not support that combination directly.
I'd first test the OOTB reporting options before considering a database view or scripted reporting solution. I'd also verify the kb_use retention settings to ensure the full six months of history is available.
One question: when you say Can Read, are you looking for the names of the article-level user criteria, or the effective access permissions, including the knowledge base criteria? That distinction could affect the approach and effort.
