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
Currently, there is no way to get usage stats for Views using the TSC library. Getting usage stats would be helpful if you wanted to monitor how the site was being used. The stats could identify popular content and content that wasn't viewed that could be removed, etc.
You can retrieve the usage stats for views in the REST API by including a query in the URL in a GET request for views: '?includeUsageStatistics=true'
The TSC library is set up for storing this data, but it isn't implemented. The ViewItem class has the attribute total_views , but there is no way to add the usage data. To collect the data, you could add a new endpoint, similar to the populate_views() endpoint for workbooks, or you could modify the views.get() endpoint to return the data by default, or with a parameter. Whatever works best with your design model.
Currently, there is no way to get usage stats for Views using the TSC library. Getting usage stats would be helpful if you wanted to monitor how the site was being used. The stats could identify popular content and content that wasn't viewed that could be removed, etc.
You can retrieve the usage stats for views in the REST API by including a query in the URL in a GET request for views: '?includeUsageStatistics=true'
The TSC library is set up for storing this data, but it isn't implemented. The ViewItem class has the attribute
total_views
, but there is no way to add the usage data. To collect the data, you could add a new endpoint, similar to thepopulate_views()
endpoint for workbooks, or you could modify theviews.get()
endpoint to return the data by default, or with a parameter. Whatever works best with your design model.Here's one idea using a parameter:
From
class Views
:This implementation works, but it changes the signature of the get method. It is false by default to mirror the REST API behavior.
Cheers,
Dave
The text was updated successfully, but these errors were encountered: