PX-API and development of new console Norwegian experiences Jan Bruusgaard Pc-Axis Reference Group Meeting 2015

Background 1995: : Statbank database (not px-files) 2013: New web (CMS) 2013: Beta API –200 readymade datasets JSON-stat and CSV 2016: New Statbank based on PX-Web and new API

PX-web in three steps We implement PX-Web in three steps: 1.PX-API (feb 2016) 2.PX-Web (summer 2016?) 3.Data model 2.4 (autumn 2016??)

Why API first? Get an API towards all 6000 tables –and not only 200 predefined datasets Possible to implement parts of PX-Web as an addition to existing Statbank application –Reduce risk –Get experiences –Establish routines for deployment

Overview We use PX-API –json query –http POST Developed separate console –to assist user to query the API –Necessary as we do not have PX-web Todays’ API with readymade datasets will still exist side by side with PX-API

Challenges PX-API not as separate as we thought Hard to configure API without PX-Web PX-API metadata is missing –Grouping –Aggregations Makes datasets larger than wanted Strange behavior –Filter: top

Live demo of console See screenshots in the end of presentation

Demo - screenshots

Metadata

Edit query

Format

Filter: all vs top

New example – foreign trade

Error message - 404

Error message - 403