Skip to content
This repository has been archived by the owner on Dec 23, 2020. It is now read-only.

Dev sprint 6: Finishing

Amber Reed edited this page May 21, 2017 · 8 revisions

What we did

  • Complete remaining integration work for the explorer view
  • Build an about page that explains the goals & limitations of the CDE
  • Finalize the datasets available for download
  • Address critical performance issues
  • Advance designs for county-level perspectives

Learning goals

  • How well do users understand the purpose, goals, and limitations of the CDE? For people with pre-existing knowledge of the CDE, what have they heard about it? What are their expectations? (About page & background )
  • How do user react to the general organization & presentation of the site?
  • For people familiar with the UCR program: how does the lack of estimates (or apparent differences between the data presented by the CDE and published CIUS reports) affect their interpretation of the results and the utility of the data overall?
  • How does knowledge of agency participation for a location affect the interpretation of results?
  • What do they think about the county-level designs? (County Design)
  • What background information is helpful when viewing county-level detail?
  • How would you expect to navigate to city-based data from here?

Participants

  • 18F team conducted 2, 1hr remote interviews with an open data expert and a UCR program manager to gather feedback on the design and development of the Crime Data Explorer.

What we learned

  • Overall, reactions were positive. Both participants saw the CDE as a significant improvement over the existing UCR website.
  • Users have varying perspectives as to what the CDE is meant to be - at times, we heard “portal for data entry” and “real-time.”
  • Not everyone understands why some states report SRS, or NIBRS.
  • Users expect to be able to drill-down into location-specific details.
  • Consumers prefer raw data when downloading it, but will need additional context in order to work with it.

Next steps

  • Planning
  • Functional enhancements
  • Add a Readme and data dictionary to provide context for downloads
  • Add a mechanism for providing feedback
  • Code refactoring & API optimization
  • Design polish

Prototype tested

Clone this wiki locally