pwalsh

This table is taken from this public document.

Column	Field name	What is required	Reason for inclusion	Additional information	Inclusion status
1	Department family	Name of department or parent department.	To identify spend to each deaprtment area.	Consistent naming conventions must be used. Departments need to issue naming conventions.	Mandatory inclusion
2	Entity	Name of individual entity	To identify spend of individual bodies within the departmental family	Where a core department is completing the return, the entry in the department “family field” should be repeated here. Consistent naming conventions must be used.	Mandatory inclusion
3	Date	The payment date as recorded in department's purchase or general ledger.	To identify the date that the

pwalsh

pwalsh

OpenSpending and OpenBudgets.eu Roadmaps

Some links to work in progress:

• https://github.com/openspending/fiscal-data-package
• https://github.com/openspending/fiscal-data-packager
• https://github.com/openspending/fiscal-data-js
• https://github.com/openspending/fiscal-data-package-viewer
• https://github.com/openspending/os-cli
• https://github.com/openspending/os-conductor

pwalsh

CKAN Data Quality

Background

We are working on a set of "data quality" tools, to check the quality of open data publications.

These tools are currently very much WIP, here:

• Dashboard: https://github.com/okfn/data-quality-dashboard/tree/feature/refactor
• Example: http://uk-25k.datadashboards.io

pwalsh

# using brew installed Python

brew install portaudio portmidi libsndfile liblo jack

brew link portaudio portmidi libsndfile liblo

cd ~/Sites/tmp

svn checkout http://pyo.googlecode.com/svn/trunk/ pyo-read-only

pwalsh

Keybase proof

I hereby claim:

• I am pwalsh on github.
• I am pwalsh (https://keybase.io/pwalsh) on keybase.
• I have a public key ASCzOJE9TdT0SeKkhN1zw4Jj0vGEOfOPzQGYdF8I02HrYgo

To claim this, I am signing this object:

pwalsh

Developer

Overview

We are looking for Developers to join our growing team. Viderum implements a range of data management solutions for government and the enterprise using open source technologies, including many that our team creates and maintains in house.

Developers at Viderum work as part of a delivery team under technical supervision of a Senior Developer. They communicate about their work with technical and non-technical stakeholders on their team, and therefore need to be proficient in spoken and written English. Our Developers scope and define work with our Senior Developers - depending on level of experience - and are responsible for implementation of a range of data management solutions.

Most of the work we do at Viderum is in Python, and some experience implementing web applications in Python or Node.js is required. As we do a lot of work with data, experience with data wrangling, data engineering, and/or data science is desirable, as is some familiarity with SQL or other database technolog

pwalsh

Senior Developer

Overview

We are looking for Senior Developers to join our growing team. Viderum implements a range of data management solutions for government and the enterprise using open source technologies, including many that our team creates and maintains in house.

Senior Developers at Viderum have experience working with teams of developers in a leading role. They communicate regularly with technical and non-technical stakeholders about the team’s work, and therefore need excellent spoken and written English. Our Senior Developers scope and define work for other developers on their delivery teams, as well as lead on technical implementation.

Most of the work we do at Viderum is in Python, and experience designing and implementing web applications in Python is a must. As we do a lot of work with data, experience with data wrangling, data engineering, and/or data science is highly desirable, as is a strong working knowledge of SQL and other database technologies. We also do frontend development

pwalsh

Mac OS X development environment

Homebrew [ http://brew.sh/ ]

It all begins with Homebrew. This setup uses Homebrew for almost everything, including things your Mac ships with, like Python.

Managing everything in Homebrew lets us use the most up-to-date packages available, and means we are not subject to any customizations, however small, Apple makes to their packaged software.

pwalsh

incorrect validation

A resource descriptor with fields with format set to None validates with validate, but fails with dump_to_sql.

{'name': 'srm_services', 'path': 'res_1.csv', 'profile': 'tabular-data-resource', 'schema': {'fields': [{'name': 'id', 'type': 'string', 'format': None, 'constraints': {}}, {'name': 'source', 'type': 'string', 'format': None, 'constraints': {}}, {'name': 'name', 'type': 'string', 'format': None, 'constraints': {}}, {'name': 'payment_required', 'type': 'string', 'format': None, 'constraints': {}}, {'name': 'urls', 'type': 'string', 'format': None, 'constraints': {}}, {'name': 'description', 'type': 'string', 'format': None, 'constraints': {}}, {'name': 'details', 'type': 'string', 'format': None, 'constraints': {}}, {'name': 'status', 'type': 'string', 'format': None, 'constraints': {}}, {'name': 'payment_details', 'type': 'string', 'format': None, 'constraints': {}}], 'missingValues': ['']}}

Solution: set format to "default"