Data dictionary
Field definitions supplied by the publishing agency in CKAN.
| Column | Type | Label | Description |
|---|---|---|---|
| Report Month | text | Report Month | — |
| Org Code | text | Org Code | — |
| Department | text | Department | — |
| All reported employees | numeric | All reported employees | — |
| Telework eligible employees | numeric | Telework eligible employees | — |
| telework_eligible___all_reported | text | Telework eligible / All reported | — |
| Remote centered employees | numeric | Remote centered employees | — |
| remote_centered___all_reported | text | Remote centered / All reported | — |
| remote_centered___telework_eligible | text | Remote centered / Telework eligible | — |
| Office centered employees | numeric | Office centered employees | — |
| office_centered___all_reported | text | Office centered / All reported | — |
| office_centered___telework_eligible | text | Office centered / Telework eligible | — |
| teleworker__remote___office_ | numeric | Teleworker (remote + office) | — |
| teleworker___all_reported | text | Teleworker / All reported | — |
| teleworker___telework_eligible | text | Teleworker / Telework eligible | — |
| Not teleworking employees from eligible | numeric | Not teleworking employees from eligible | — |
| not_teleworking___all_reported | text | Not teleworking / All reported | — |
| not_teleworking___telework_eligible | text | Not teleworking / Telework eligible | — |
| not_teleworking___not_eligible | numeric | Not teleworking + Not eligible | — |
| not_teleworking___not_eligible___all_reported | text | Not teleworking + Not eligible / All reported | — |
| telework_days___from_eligible | text | Telework days % from eligible | — |
Resource details
| Format | CSV |
|---|---|
| Size | 452 KB |
| Rows | 3,148 |
| Last updated | Sep 30, 2026 |
| Part of | Statewide Hybrid Workforce |
Other resources in this dataset
CKAN Data API
Access resource data through the CKAN DataStore API. The examples below use this resource's ID.
Endpoints
The Data API provides these actions. Creating or updating records requires appropriate permissions; the query actions read public DataStore records.
| Create | https://ckan.cdt.dev.datopian.com/api/3/action/datastore_create |
|---|---|
| Update / insert | https://ckan.cdt.dev.datopian.com/api/3/action/datastore_upsert |
| Query | https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search |
| Query via SQL | https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql |
Query examples
First five results
"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=39310013-da4f-499c-90bb-9fa7880ccbed&limit=5"Results containing "jones"
"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=39310013-da4f-499c-90bb-9fa7880ccbed&q=jones"SQL query
"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql?sql=SELECT%20%2A%20FROM%20%2239310013-da4f-499c-90bb-9fa7880ccbed%22%20LIMIT%205"SQL queries depend on whether SQL search is enabled by the portal.
OData query
Use the resource's OData URL and its field names for paging, selecting columns, or filtering rows.
ODATA_RESOURCE_URL?$top=5
ODATA_RESOURCE_URL?$skip=5&$top=5
ODATA_RESOURCE_URL?$select=FIELD_NAME&$filter=FIELD_NAME eq 'VALUE'Replace ODATA_RESOURCE_URL, FIELD_NAME, and VALUE with the details for the selected resource. See the OData query options guide (opens in a new tab) for more examples.
Use the API in code
JavaScript (JSONP)
var data = { resource_id: '39310013-da4f-499c-90bb-9fa7880ccbed', limit: 5, q: 'jones' };
$.ajax({
url: 'https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search',
data: data,
dataType: 'jsonp',
success: function (response) {
console.log(response.result.total, response.result.records);
}
});Python
import json
from urllib.request import urlopen
url = 'https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=39310013-da4f-499c-90bb-9fa7880ccbed&limit=5'
with urlopen(url) as response:
result = json.load(response)['result']
print(result['total'], result['records'])For parameters and response fields, see the CKAN DataStore documentation (opens in a new tab).