Database Type: Open Data, SQL
Connector Supports: READ only
Introduction
Socrata, a scalable, cloud-based integrated solution offers a simple and intuitive method via its open data platform to deliver universal access to government data thereby allowing users the privilege to query, analyze and share information.
Socrata a web-based data repository has rendered the concept of transparent government a reality. It is a cloud-based service known for its built-in capability to create a classic visual representation of government domain-specific data through a web interface in the public interest. Besides extending open data solutions alongside easy access to open data apps to its users, it also allows non-profit organizations to be more transparent by importing data into Socrata so as to share it with users who can explore and filter datasets for viewing, analysis and so forth.
The VOGO Voice Socrata connector instances provide easy access to execute any singular SoQL query to impart the READ only function to public or private data.
Prerequisites
- Socrata dataset
- Username and password authentication to access private datasets.
- Understanding of how to write a SoQL query
Anatomy of Settings
Defining Settings values for Add New Socrata Account
Name: It refers to the name assigned to the instance of the connector created.
App Token: In order to be permitted to read datasets an application token needs to be included in the request. By doing so you get the privilege of higher throttling limits. Only the Read-only requests require the application token. An App token is obtained by registering your application in your Socrata profile. To know how to obtain an application token visit https://dev.socrata.com/docs/app-tokens.html
Username: Username authentication is only necessary when accessing private datasets.
Password: Password-based authentication is required only for accessing private datasets.
đź–Ť Note: Another instance of providing a username and password authentication would be when making requests to private datasets.
Datasite: Input the Base URL of the open data portal to which access is intended. For instance, towards the bottom of https://www.opendatanetwork.com/ you will find many different data providers. An example of valid input is: data.seattle.gov to the respective dataset is provided.
Disclaimer: All password/private information is encrypted when saved within the VOGO Voice platform for your security.
Connector Usage
Now that a connector is established it can now be used within any interaction flow. Each usage of the connector will allow different configurations to retrieve different results. Those settings can be either static or dynamic based on the needs.
Anatomy of Configuration
Defining Configuration Values for Socrata Connector
Name: The name assigned to identify the connector and the results data. The assigned name is used every time the connector is called to action through the components in the interaction builder platform.
Query Datasets: This is a quick search engine that will use the open data portal defined in the connector instance to search all of the “datasets” within that portal. Any selected result will auto-create the “Dataset” value with the appropriate 4×4.
Dataset: In this field provide the 4×4 Dataset Identifier for the dataset from the open data catalogs to which access is intended. It can be found in the description column of the chosen dataset and the respective identifier will also show up in the last part of the URL as highlighted below.
Query: “Socrata Query Language” (SoQL) is the query language used to filter the datasets. The SoQL statements are in fact a simplified version of the SQL query language specifically designed to interact with data on the web. To learn how to write SoQL queries visit https://dev.socrata.com/docs/queries/query.html
Caching: To know about caching, click here.