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
{{ message }}
This repository was archived by the owner on Jun 18, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: implementation-guide.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,6 @@ layout: default
4
4
title: Implementation Guide
5
5
permalink: "/implementation-guide/"
6
6
filename: "implementation-guide.md"
7
-
8
7
---
9
8
10
9
## 1) Create and maintain an enterprise data inventory
@@ -16,7 +15,7 @@ Maintain a complete listing of all datasets owned, managed, collected, and/or cr
16
15
17
16
Produce a single catalog or list of data managed in a single table, workspace, or other relevant location. Describe each dataset according to the [common core metadata](/schema/).
18
17
19
-
This listing can be maintained in a Data Management System (DMS) such as the open-source [CKAN](http://www.ckan.org) platform; a single spreadsheet, with each metadata field as its own column; or a DMS of your choosing.
18
+
This listing can be maintained in Data Management Systems (DMS) such as the open-source [CKAN](http://www.ckan.org) platform or Software as a Service offerings like [Socrata](http://www.socrata.com/open-data-portal); a single spreadsheet, with each metadata field as its own column; or a DMS of your choosing.
20
19
21
20
### B) Best Practices and Examples
22
21
@@ -47,6 +46,7 @@ While you could manually create this file in a text editor, it is recommended th
47
46
48
47
***Don’t have a DMS?** Use the hosted Catalog Generator to create your data.json file via basic data entry.
49
48
***Is your data inventory stored in a CSV (Excel file)?** Use the [CSV-to-API generator](http://labs.data.gov/csv-to-api/) to automatically convert it into a compliant data.json file.
49
+
***Is your data inventory stored in Socrata?** Socrata has native support for data.json, so any datasets stored are automatically exposed appropriately. In addition, any of the extended properties specified in the [common core metadata](http://project-open-data.github.io/schema/) can be set on a per-dataset basis using the built-in metadata facilities.
50
50
***Is your data inventory stored in CKAN?** Use the Data.gov extension (coming soon).
51
51
***Not sure if your data.json file meets the requirements?** Paste your file into the [JSON Validator](https://github.com/project-open-data/json-validator) to receive real-time feedback.
0 commit comments