How the CIO Council Made Our Open Data Prioritization Tool Kit More Open

This post was created automatically via an RSS feed and was originally published at http://www.digitalgov.gov/2015/09/04/how-the-cio-council-made-our-open-data-prioritization-tool-kit-more-open/

Shown in Figure 1, the Open Data Prioritization Toolkit is categorized into phases of understanding, evaluating, and opening datasets. It also shows alignment to support tools designed to help your agency throughout each phase. The provided tools are sample templates to guide agencies as they examine datasets and customize them based on their unique requirements.

A few weeks ago the Council’s Innovation Committee released the Open Data Prioritization Toolkit. The response to the toolkit has been positive, but we also heard back from the community asking why the Open Data toolkit’s summary was locked up in a non-open format—PDF.

The Council Operations Team noted the irony of publishing a guide to opening data in a non-open format made a decision to eat our own dogfood.After some scouring we found a few open source tools to make the summary a markdown document we could share in HTML format.

Below is a rundown of the tools we used and how we did it. This is not an endorsement of specific tools, but it is an endorsement of making open the default for government publishing.

  1. We used Ben Balter’s word-to-markdown tool to convert our .docx copy of the summary to markdown.
  2. We pasted the markdown into StackEdit to convert it to HTML. In StackEdit, we did have to clean up the HTML a bit. We reinserted the figure images (hosted on CIO.gov), re-linked the table of contents, and recreated the footnotes.
  3. We exported the HTML and published on CIO.gov.

Some notes:

  • You can still use StackEdit to export to PDF, too.
  • An alternative to StackEdit is Dillinger.io.
  • We found this cheat sheet helpful with formatting in markdown.
  • We like using markdown because it allows you to focus on the content and not the formatting.

Questions? Tweet us @ciodotgov.

This post was originally published on the CIO Council blog by the CIO Council Operations Staff.

 

Tagged with: , ,