Change Details

We would like to have an estimate / accurate number of origins per source code providers (forge, package manager, ...) displayed in the archive coverage widget that can be found in the main archive web page. This needs some investigation on what is the best option to implement it: - run directly a database query then cache its result for subsequent calls ? - run a scheduler task each day that will count the number of origins per provider, then store its result in a metric table somewhere ?

We would like to have an estimate / accurate number of origins per source code providers (forge, package manager, ...) displayed in the archive coverage widget that can be found in the main archive web page. This needs some investigation on what is the best option to implement it: - run directly a database query then cache its result for subsequent calls ? - run a scheduler task each day that will count the number of origins per provider, then store its result in a metric table somewhere ? I think the work started in D561 might be useful for that task.

We would like to have an estimate / accurate number of origins per source code providers (forge, package manager, ...) displayed in the archive coverage widget that can be found in the main archive web page. This needs some investigation on what is the best option to implement it: - run directly a database query then cache its result for subsequent calls ? - run a scheduler task each day that will count the number of origins per provider, then store its result in a metric table somewhere ? I think the work started in D561 might be useful for that task.