Open Data Catalog is an open data catalog based on Django, Python and PostgreSQL. It was originally developed for OpenDataPhilly.org, a portal that provides access to open data sets, applications, and APIs related to the Philadelphia region. The Open Data Catalog is a generalized version of the original source code with a simple skin. It is intended to display information and links to publicly available data in an easily searchable format. The code also includes options for data owners to submit data for consideration and for registered public users to nominate a type of data they would like to see openly available to the public.
I see the endpoint just returns an array of datasets as oppose following the structure specified here https://project-open-data.cio.gov/v1.1/schema/ . That breaks implementation on our side cos we're getting a json array instead of the expected json object. Can we make changes to follow the standard structure :
Base on the code changes made here https://github.com/azavea/Open-Data-Catalog/commit/1ab582544b8e987d192ad1a2068622894d9f152b
I see the endpoint just returns an array of datasets as oppose following the structure specified here https://project-open-data.cio.gov/v1.1/schema/ . That breaks implementation on our side cos we're getting a json array instead of the expected json object. Can we make changes to follow the standard structure :
Or if changing will break impl for existing clients, We can add a new endpoint that follows the above format.