You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
View and download statistics are currently "all time" due to limitations of the DSpace Statistics API. We should explore the possibility of enabling a "reporting period". The current version of the API supports date ranges so we can now limit statistics to a date range by POSTing community, collection, or item IDs and date parameters.
The problem is that this is only feasible for hundreds or thousands of items, but not the entire repository. We could enable it as an option when generating a report perhaps, rather than for the entire AReS Explorer UI. See the Swagger API docs.
The text was updated successfully, but these errors were encountered:
alanorth
changed the title
Enable date-based statistics for DSpace Statistics API
Enable date-based usage statistics for DSpace Statistics API
Nov 18, 2020
alanorth
changed the title
Enable date-based usage statistics for DSpace Statistics API
Enable date-based usage statistics from the DSpace Statistics API
Nov 18, 2020
A better way to think about this would be as a "reporting period" actually, for example to see how many views/downloads took place during a certain date range.
See the DSpace Statistics API documentation for the new endpoints that allow POSTing a date range with a list of IDs:
View and download statistics are currently "all time" due to limitations of the DSpace Statistics API. We should explore the possibility of enabling a "reporting period". The current version of the API supports date ranges so we can now limit statistics to a date range by POSTing community, collection, or item IDs and date parameters.
For example, if you send this request:
The API will respond:
The problem is that this is only feasible for hundreds or thousands of items, but not the entire repository. We could enable it as an option when generating a report perhaps, rather than for the entire AReS Explorer UI. See the Swagger API docs.
The text was updated successfully, but these errors were encountered: