Change Details

“Total partners” -> “Total active partners” Add breakdown of proxy/bundle/manual? Remove from public view days until decision and application status distribution graphs Remove from staff view “Most popular pages” list Standardize approach to CSV download - some adjust based on date of download, others don’t

The Library Card platform has a metrics dashboard. We stopped using much of the data on it in favour of more fine-grained data such as that from the EZProxy logs. Additionally, it stopped loading some time ago (T237721). It hasn't been displayed to users in the navigation bar for a while either. We want to review what steps would be required to remove the dashboard entirely from the tool, and understand the degree to which we could remove large parts of the codebase, such as the graphs app. We have the django-request module installed in the Library Card platform, but may no longer have any need for it. Per our review of our various logs (T256465), we don't want to be continuing to generate a large database of user page requests if we don't need it for anything. The module is used to generate pageview data on the dashboard but may not be useful anywhere else. **Questions** - What is the list of components we can remove if we no longer want the dashboard? - Is any code in the graphs app used on other pages? If so, could it be migrated somewhere else? - Is the django-request module used in any other area of the codebase, or could it be safely removed alongside the dashboard?

“Total partners” -> “Total active partners”The Library Card platform has a metrics dashboard. We stopped using much of the data on it in favour of more fine-grained data such as that from the EZProxy logs. Additionally, it stopped loading some time ago (T237721). It hasn't been displayed to users in the navigation bar for a while either. We want to review what steps would be required to remove the dashboard entirely from the tool, and understand the degree to which we could remove large parts of the codebase, such as the graphs app. We have the django-request module installed in the Library Card platform, but may no longer have any need for it. Per our review of our various logs (T256465), we don't want to be continuing to generate a large database of user page requests if we don't need it for anything. The module is used to generate pageview data on the dashboard but may not be useful anywhere else. **Questions** - What is the list of components we can remove if we no longer want the dashboard? Add breakdown of proxy/bundle/manual - Is any code in the graphs app used on other pages? If so, could it be migrated somewhere else? Remove from public view days until decision and application status distribution graphs Remove from staff view “Most popular pages” list Standardize approach to CSV download - some adjust based on date of download - Is the django-request module used in any other area of the codebase, others don’tor could it be safely removed alongside the dashboard?