You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Socrata has rolled-out a new read/write metadata API that allows users to read metadata (e.g., name of data set, description, categories, tags, column descriptions, etc.)
Reading Metadata
You can read metadata on all the data sets (e.g., list name, description, categories, etc.) on a Socrata domain (e.g., data.cityofchicago.org) or you can list metadata for a single data set. Here is the metadata available to read on a data set.
Writing and Updating Metdata
Users with an API key that allows writing to Socrata can publish and update metadata over the API. Users can author new metadata or overwrite/update existing metadata.
Including in RSocrata
If we adopt this, I'm not sure the best way to approach it. Namely, I think there are two potential options. First, we can have reading/writing metadata to be standalone functions, such as read.socrataMetadata and write.socrataMetadata, respectively.
Otherwise, we could potentially include these as an optional switch within the existing read.socrata and write.socrata functions. For instance, listing all available metadata for a domain would be read.socrata(url = data.domain.gov, metadata = T) while as writing metadata would take the form of write.socrata( ... , metadata = T).
The text was updated successfully, but these errors were encountered:
Socrata has rolled-out a new read/write metadata API that allows users to read metadata (e.g., name of data set, description, categories, tags, column descriptions, etc.)
Reading Metadata
You can read metadata on all the data sets (e.g., list name, description, categories, etc.) on a Socrata domain (e.g., data.cityofchicago.org) or you can list metadata for a single data set. Here is the metadata available to read on a data set.
Writing and Updating Metdata
Users with an API key that allows writing to Socrata can publish and update metadata over the API. Users can author new metadata or overwrite/update existing metadata.
Including in RSocrata
If we adopt this, I'm not sure the best way to approach it. Namely, I think there are two potential options. First, we can have reading/writing metadata to be standalone functions, such as
read.socrataMetadata
andwrite.socrataMetadata
, respectively.Otherwise, we could potentially include these as an optional switch within the existing
read.socrata
andwrite.socrata
functions. For instance, listing all available metadata for a domain would beread.socrata(url = data.domain.gov, metadata = T)
while as writing metadata would take the form ofwrite.socrata( ... , metadata = T)
.The text was updated successfully, but these errors were encountered: