March 20, 2018

Agenda

Challenge

Dashboard-oriented approach

Data portal approach

CKAN framework

Our vision

Path forward

Challenge

How do we make our data
more accessible?

Key concerns

  • Encouraging more use cases and public engagement
  • Sustainability/ease of maintanence
  • User-friendly interface

Dashboard-oriented approach

Pros and cons

Pros

  • Visually appealing
  • Interactivity
  • Possibility to control the message

Cons

  • High cost of production/maintanence
  • Difficult to manage
  • Product-centric approach
  • Limited utility

Data portal approach

A data portal does not preclude
creation of dashboards!

What is data portal?

A data portal is a site for storing a list of datasets with added features to facilitate accessing, viewing, and searching for any particular datasets.

Why data portal?

  • Proven utility
    • Many use cases (e.g. Data.gov, Chicago Data Portal)
  • Great for storing/sharing multiple datasets
    • Suitable for the R&A unit's "data clearinghouse" mission
    • Can have various formats of datasets (even dashboards)
  • Ease of use and management
    • User interface
    • Access control

CKAN framework

What is CKAN?

  • The Comprehensive Knowledge Archive Network:

"CKAN is an open-source DMS (data management system) for powering data hubs and data portals. CKAN makes it easy to publish, share and use data."

Use cases

Data.gov main page

opendata.swiss main page

Why use CKAN?

  • An actively managed/maintained open-source project
    • Free, flexible, and up-to-date
  • Comes with a rich set of features for a fully-functionl data portal

Useful features

  • Flexibility and customizability in portal structure and look
  • Elaborate access control
    • Organizations and groups
    • Capable of supporting a sustainable workflow
  • Built-in visualizations
    • A simple "dashboard" view for each entry is available via an extension
  • API for programmatic access to data
    • Great for research and application building
    • An entirely separate front-end interface is possible!

Our vision

Portal structure

  • Main page
    • Highlights, search bar, categories, some stats, etc.
  • Data
    • Raw datasets (with metadata and simple visualizations)
    • Dashboards (with metadata)
  • Articles
  • Applications
    • Featuring user-made applications
  • About
    • FQA, API documentation, Application guidelines, etc.

Access control

  • Users with permission
    • upload/edit an item for internal view only
  • Mangers
    • upload/edit/delete an item for internal and public views
  • Administrators
    • manage organizations and groups
    • grant permissions as needed

Contents

  • Data entries
    • Raw datasets, dashboards, publications
    • Metadata: brief descriptions, data dictionary, etc.
    • Tags for grouping/classifying entires
    • Data explorer and visualization views
    • API for programmatic access/use of data
  • Articles

Data entry; image from CKAN Documentation

"View" options; image from CKAN Documentation

"Data Explorer" view; image from CKAN Documentation

Built-in graph; image from CKAN Documentation

Embedding a webpage; image from CKAN Documentation

Article page example

User engagement

  • Application programming interface (API)
    • Facilitating data access for research projects or building applications
  • User-made applications
    • Applications meeting our standard -> featured on the Applications page
    • Providing an incentive to use our data -> more use cases
  • Outreach effort

Applications page example

Path forward

Timeline

Time Task
2018 1Q Proof of concept (demo); 2018 SJS grant application
2018 2Q Developing the access control model, portal structure and front-end UI design
2018 3Q Migrating datasets and articles; additional content creation (dashboards, etc)
2018 4Q Building the application; testing with select internal users and receiving feedback
2019 1Q Lauching the application; training internal users
2019 2Q Outreach for user engagement (e.g. Chi Hack Night, Universities); drafting final report to BJS
2019 3Q Ongoing user engagement; submitting final report to BJS

Questions?