Skip to content
This repository was archived by the owner on Jun 18, 2024. It is now read-only.

Added available Socrata resources #53

Closed
wants to merge 1 commit into from

Conversation

willpugh
Copy link
Contributor

This pull request has been automatically generated by Prose.io.

@gbinal
Copy link
Contributor

gbinal commented May 21, 2013

Hi Will,

Thanks a bunch for all of the activity you're contributing to Project Open Data. In Socrata's current form, how would an agency go from Step 1 (maintaining an enterprise data inventory) to Step 2 (maintaining a public data inventory)? That is, would they export the catalog, translate it, and/or provide a feed that would support the data.json schema?

Gray

@willpugh
Copy link
Contributor Author

Currently, we support a DCAT api
[domain]/api/dcat.rdf
that allows you to get the catalog of datasets.

Pretty soon we'll have /data.json working as well.

@willpugh
Copy link
Contributor Author

Thought I would update this bug to mention that we have our initial support in for data.json, so any customer on Socrata now has a data.json file that provides a listing of all their publicly available datasets.

We now allow our customers to create a set of metadata fields in Socrata that we will map to the metadata in data.json. We handle most of the required fields natively. Customers can simply add the metadata fields they want to expose for extended properties.

I've created an example site. You can take a look at https://projectOpenData.demo.socrata.com that has all the metadata fields set-up for all the Project Open Data fields, and you can look at the /data.json to see how it maps. It also contains an instance of:

  1. An interactive dataset (where all the data is in Socrata)
  2. An external dataset (where Socrata points to a different URL for the actual data)
  3. A file dataset, where Socrata just points to a file to download

So you can we how each of the Socrata data set types are handled, and so anyone building tools can use it to test against.

Customers with existing metadata can talk to our Client Services team to get custom mappings to the data.json format as well.

So, you can now go to any public Socrata site and get a data.json file for it.

@waldoj
Copy link

waldoj commented May 30, 2013

👍 Bravo, Will!

@willpugh
Copy link
Contributor Author

This change has been obsoleted by #80 which includes language to show that Socrata has data.json implemented

@waldoj
Copy link

waldoj commented Jun 30, 2013

OK, then I'm closing this pull request so that #80 can be considered instead. Thanks for noting this pull request's obviation, @willpugh.

@waldoj waldoj closed this Jun 30, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants