COUNTER metric PR_P1 or DR_D1 Searches platform to calculate Total Usage in Analytics databases cost per use reports
We request that the Total Usage field used in constructing the databases cost per use report utilize the COUNTER PRP1 Searches platform or DRD1 Searches platform metric.
Within the group of university libraries that are part of REBIUN (https://www.rebiun.org/), we have agreed to use the PRP1 metric, or alternatively DRD1 Searches platform, to calculate the cost per use of databases.
However, when configuring the report in Analytics, we encountered the problem that Alma uses the DR – Unique Title Requests metric. https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/080Analytics/Alma_Analytics_Subject_Areas/E-Inventory#Cost_Usage
Therefore, even if we build a cost per use report, it would not be valid for these libraries for databases.
-
Hello,
In order to better understand the need can you please give some examples – how the data is currently presented in analytics, what is the original report data, and why this is not correct.
Also, please note that DRD1 Searches platform does not exist in Counter DRD1.
Best regards,
Hadas Granot
Analytics product team -
Juana GOMEZ GARCIA commented
Totalmente de acuerdo