Skip to main content

Opinion: Improving data portal feedback

Some of our sponsors own Data Portals where they publish (and sometimes encourage others to publish) data. Examples include Data Mill North, Calderdale Dataworks, Northern Powergrid's Open Data Portal. Yiu-Shing Pang recently shared some thoughts on their new Open Data Portal, which you can read the blog here

A common problem publishers of open data face is justifying the efforts they put into publishing datasets. The main methods they usually have to answer that question are download/visitor figures, surveys, and comment sections. As an organisation, we both publish datasets and use datasets published by others and we'd like a more holistic approach to feedback.

First let's look at the limitations of existing "feedback" methods:

  • Download/visitor numbers can tell you that one dataset has been downloaded or visited 3 times and another dataset 3000 times. But that doesn't actually mean that one is 1000 times more useful or used than the other. The dataset with 3 downloads may have been used to power some tool that is used by huge numbers of people. The dataset with 3000 downloads may just be because a single developer has inefficient code.
  • Surveys and online 'Contact' forms can give useful feedback about a Data Portal, in general, but often aren't great for specific feedback about a specific dataset. They also require people to know they exist and to be happy to volunteer their time for no clear benefit to themselves.
  • Comment sections are useful for individual datasets (as a user of the data you could report an issue with it) but can suffer from a lack of responses from the dataset publisher or can get filled up with irrelevant spam.

Ideally there would be a better feedback loop that has benefits to all parties: publisher, developers/users, and random members of the public.

Adding a showcase per dataset

Our very modest proposal is for every dataset page to have a "showcase" (or "existing uses" or "products") section that would be curated by the publisher of the dataset. This section would consist of a series of "blocks" that could have a title, a description, a thumbnail image, an author and a URL and would be for that dataset. It would resemble existing Showcase/Products pages.

A grid of products
A grid of "Products". Each consists of an image, a title (with a link), a description, and an author. This screenshot is of the "Products" page on Data Mill North.
Credit: Data Mill North

An immediate use of a showcase would be for publishers to separate their own visualisations from the data files. But, because it could promote the work of external developers/journalists/citizens (who have used the data) it gives those people an incentive to submit their uses back to the publisher, giving the publisher a better understanding of how people are using their data beyond simple download and visitor numbers. 

It also benefits random members of the public who stumble across the dataset page from a search engine. These people may not be clued up on the industry, haven't interacted with that specific dataset before but may be interested in using the data in original ways not anticipated by the publisher. We often see Data Portals that require the user to already know that the dataset they're interested in exists and how to use it. Giving an incentive for people to share their "use cases" by showcasing them on the data portal itself, i.e. publicity and/or recognition for innovative use of the data, benefits both parties as well as inspiring ideas for future, less experienced data users - everyone gains. 

A step further than this would even be to encourage data users to share their code and methodology. Publishers then have easy justification for their efforts, as they can see directly how their data is being used by the industry and general public and where improvements could be made to the dataset.

Summary

Many of our sponsors and network attempt to gather feedback on their data in similar ways. We're used to learning about user needs through comments, questionnaires and website statistics, however we think that the Data Portals themselves are a great resource to share example projects and promote an online community as a means to gather feedback - that benefits everyone. If you have anything to add, then continue the conversation with us over on Twitter @OpenInnovates
https://open-innovations.org/blog/2023-04-17-opinion-improving-data-portal-feedback
open-innovations.org
CC-MAIN-2023-23
17848
application/http; msgtype=response
sha1:PJLUUYWQSMSHSO6BFVFXCJ3SWJXGMHPN
<urn:uuid:4c9c18a4-cfb2-46e2-bf07-c5a072829d07>
2023-05-28T06:08:06Z
93.93.131.30
text/html
sha1:MJ6FVA3LG5ZLND3LJUOSRL7ZP5KSR4PN
<urn:uuid:bffebe9c-037a-4a6b-9aca-e82d96610839>
https://open-innovations.org/blog/2023-04-17-opinion-improving-data-portal-feedback
response
<urn:uuid:d174ce35-2624-46fd-81c7-ac59629d29b7>
isPartOf: CC-MAIN-2023-23
publisher: Common Crawl
description: Wide crawl of the web for May/June 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-37
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/