Issue 12341

Build a DatasetMetrics service for all registered datasets

Reporter: mdoering
Type: NewFeature
Summary: Build a DatasetMetrics service for all registered datasets
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2012-11-21 11:59:03.979
Updated: 2017-10-06 14:40:10.912
Resolved: 2017-10-06 14:40:10.867
Description: Expose a populated DatasetMetrics class for occurrence and checklist datasets. Currently DatasetMetrics is exposed as a temporary solution only for checklists via the clb webservices. But with the new cube services we can populate such an object also for occurrences. Decide where to best place this webservice (metrics-ws?) so that the dependencies are best catered for (it needs clb metrics & dependency)

Also work on the client, removing the current clb service and refactor its current usage with the new service]]>

Comment: To whoever takes this task: This discussion requires Markus and Tim input 
Created: 2012-11-21 12:38:17.943
Updated: 2012-11-21 12:38:17.943

Created: 2012-12-03 17:11:38.415
Updated: 2012-12-03 17:11:38.415
Further update:
I believe this implementation to be too limiting for occurrence datasets.  It only supports single dimensions which is not enough for occurrence datasets - e.g. it can't do basic kingdom/basisOfRecord/georeferenced for a dataset (a 4 dimension metric).  Please see the following which illustrates an alternative approach for occurrence datasets:

Author: hoefft
Comment: It has since been decided that we use SOLR facets for counts to avoid drift 
Created: 2017-10-06 14:40:10.91
Updated: 2017-10-06 14:40:10.91