Hey Jack,
Even when we enable MDC counts in a Dataverse repository, the regular, out-of-box download counter is always running, since it's associated with the guestbooks. The API call
https://researchdata.cuhk.edu.hk/api/info/metrics/downloads returns a count that roughly all regular download counts of datasets in the CUHK Research Data Repository. The count there is 81,027 at the time of this writing, and I think it's different from the 83,027 we see on the homepage at
https://researchdata.cuhk.edu.hk/dataverse/root because of the caching that Dataverse is doing so that these /metrics API endpoints return metrics faster.
So I'm even more certain that the downloads count at the top of the homepage is only the regular, out-of-box download counts, even for Dataverse repositories that have enabled MDC counts. The QDR repository also has MDC enabled, and its home page shows download counts that I believe are only the regular counts. The download count on the homepage at
https://data.qdr.syr.edu roughly matches what's returned by the API call
https://data.qdr.syr.edu/api/info/metrics/downloads.
You can also query the repository's database if you have access to it. The Dataverse community maintains a Google Doc with example database queries, and
its "File downloads, subsets and explorations" section includes examples that mostly use the database's "guestbookresponse" table to get regular download counts in different ways.
Let me know if you have any questions about this!
And thanks for encouraging discussion with this thread! I plan to continue helping test the design of how Dataverse records and communicates these MDC counts and regular download counts, as we plan to enable MDC counts on Harvard Dataverse and later on as we consider how to include them on the Modern UI version of Dataverse, and this discussion has been helpful, especially about what the homepage shows.