Dev sprint 4: Explorer & Context

Hypothesis

The MVP will provide access to UCR data in a variety of ways. There are 3 main experiences - the explorer view that provides access to high-level trends and incident data at the national and state levels, downloads which will allow users to download and explore the data with granularity, and an API which allows advanced users to query the entire dataset (to the extent it’s made available to the CDE)

Sprint 4 goals

• Adding a homepage that allows users to learn about the CDE and navigate to data by location and crime type.
• Making refinements to the visual design and organization of the explorer view based on earlier user feedback. * Specifically, the team sought to simplify how time ranges are used in navigation and clarify how SRS & NIBRS data is used to power charts within the view.
• Continued integration of the design and its supporting API to enable the dynamic display of data based on a user’s query.
• Developing new content that may be programmatically displayed based on the parameters of a query.
• Some refactoring of the code base to improve performance and its maintainability, as well as the addition of automated testing for improved cross-browser support.

What we learned

“I see this as the highlights — you’re showing me the big picture.” CRIMINAL JUSTICE ADVOCATE

“This is what people have been waiting for.” STATE UCR PROGRAM MANAGER

“You’re showing us things we would like to do in our work, but isn’t possible today.” CJIS SA

“You’re showing us things we would like to do in our work, but isn’t possible today.” CJIS SA

Next steps

• Complete major integration work
• Enable users to view and download selected aspects of UCR data
• Add a mechanism to allow for the collection of user feedback
• Incorporate design and usability testing feedback
• Provide documentation for use of the API