Include a blurb for using Socrata.

Author: willpugh

Diff for: metadata-resources.md

@@ -1,8 +1,9 @@
 ---
+published: true
 layout: default
 title: Metadata Resources
-permalink: /metadata-resources/
-filename: metadata-resources.md
+permalink: "/metadata-resources/"
+filename: "metadata-resources.md"
 ---
 
 This section provides further background and resources to assist agencies in implementing the [common core metadata schema](/schema/).
@@ -52,11 +53,15 @@ C) Utilizing CKAN
 
 [CKAN](http://www.CKAN.org) is a popular, open-source data catalog.  Even if an agency hasn't begun a data catalog, adopting CKAN can provide a robust and feature-rich solution with which to begin maintaining an internal or external catalog.  In addition to providing an effective means of organizing the agency's data catalog, CKAN provides several opportunities for generating the needed data.json file.  CKAN provides a convenient CSV export that can then be imported into the [Catalog Generator](http://project-open-data.github.com/catalog-generator/) for conversion into an appropriately formatted JSON file.  Alternatively, CKAN provides a JSON API of the data catalog which can then be altered to provide an automatic update for the appropriately formatted JSON file.  
 
-D) Manual translating a data file from another system
+D) Using Socrata
+
+[Socrata](http://www.socrata.com/open-data-portal/) is a popular, open data catalog that is run as a service.  Agencies that have not adapted a data catalog yet, can use Socrata without having to install or setup any servers or software.  In addition to providing rich visualizations and data management features, Socrata **natively supports data.json** so any datasets managed through Socrata will be automatically exposed correctly.  Socrata also supports all the extended metadata fields through it's extensible metadata features.
+
+E) Manual translating a data file from another system
 
 Agencies may also manage their data catalogs through various database solutions such as Access, an asset management system, document management system, geoportal, or assorted proprietary systems.  Regardless of which system an agency employs, it should include a fundamental export option which allows the catalog to be exported as a CSV file, which can then be imported into the [Catalog Generator](http://project-open-data.github.com/catalog-generator/) for conversation to an appropriately formatted JSON file.  Depending on the solutions' varied further functionality, some of them may also provide APIs which can then be configured to maintain the data.json file.  If not, they may instead support XML and JSON exports, which can then be converted to the proper format.
 
-E) Convert from CSV or JSON to XML or RDFa lite.  
+F) Convert from CSV or JSON to XML or RDFa lite.  
 
 In order to generate appropriately formatted XML or RDFa Lite files, simply import an appropriately formatted CSV or JSON file into the [Catalog Generator](http://project-open-data.github.com/catalog-generator/), ensure that the metadata fields line up, and re-export the file.