Merge pull request project-open-data#496 from project-open-data/updating-links

Rebecca Williams · Rebecca Williams · commit 0e081085bc12 · 2015-07-07T11:29:06.000-04:00
Updating links to address project-open-data#399
diff --git a/examples/catalog-sample-extended.json b/examples/catalog-sample-extended.json
@@ -31,11 +31,11 @@
         "accessLevelComment": null,
         "distribution": [
             {
-                "accessURL": "https://explore.data.gov/views/ykv5-fn9t/rows.csv?accessType=DOWNLOAD", 
+                "accessURL": "https://data.example_agency.gov/views/ykv5-fn9t/rows.csv?accessType=DOWNLOAD", 
                 "format": "text/csv"
             }
         ],
-        "webService": "http://explore.data.gov/api/views/ykv5-fn9t/rows.json", 
+        "webService": "http://data.example_agency.gov/api/views/ykv5-fn9t/rows.json", 
         "license": "Public Domain", 
         "spatial": "United States", 
         "temporal": "2009-09-01T12:00:00Z/2010-05-31T12:00:00Z", 
@@ -65,19 +65,19 @@
         "accessLevelComment": null,
         "distribution": [
             {
-                "accessURL": "https://explore.data.gov/views/ykv5-fn9s/rows.csv?accessType=DOWNLOAD", 
+                "accessURL": "https://data.example_agency.gov/views/ykv5-fn9s/rows.csv?accessType=DOWNLOAD", 
                 "format": "text/csv"
             }, 
             {
-                "accessURL": "https://explore.data.gov/views/ykv5-fn9s/rows.json?accessType=DOWNLOAD", 
+                "accessURL": "https://data.example_agency.gov/views/ykv5-fn9s/rows.json?accessType=DOWNLOAD", 
                 "format": "application/json"
             }, 
             {
-                "accessURL": "https://explore.data.gov/views/ykv5-fn9s/rows.xml?accessType=DOWNLOAD", 
+                "accessURL": "https://data.example_agency.gov/views/ykv5-fn9s/rows.xml?accessType=DOWNLOAD", 
                 "format": "application/xml"
             }
         ],
-        "webService": "http://explore.data.gov/api/views/ykv5-fn9s/rows.json", 
+        "webService": "http://data.example_agency.gov/api/views/ykv5-fn9s/rows.json", 
         "license": "Public Domain", 
         "spatial": "United States", 
         "temporal": "2008-09-01T12:00:00Z/2009-05-31T12:00:00Z", 
diff --git a/examples/catalog-sample.json b/examples/catalog-sample.json
@@ -28,9 +28,9 @@
         "bureauCode": "018:10",
         "programCode": "018:001",
         "accessLevelComment": "",
-	"accessURL": "https://explore.data.gov/views/ykv5-fn9t/rows.csv?accessType=DOWNLOAD", 
+	"accessURL": "https://data.example_agency.gov/views/ykv5-fn9t/rows.csv?accessType=DOWNLOAD", 
 	"format": "text/csv",
-        "webService": "http://explore.data.gov/api/views/ykv5-fn9t/rows.json", 
+        "webService": "http://data.example_agency.gov/api/views/ykv5-fn9t/rows.json", 
         "license": "Public Domain", 
         "spatial": "United States", 
         "temporal": "2009-09-01T12:00:00Z/2010-05-31T12:00:00Z"   
@@ -50,19 +50,19 @@
         "accessLevelComment": "",
         "distribution": [
             {
-                "accessURL": "https://explore.data.gov/views/ykv5-fn9s/rows.csv?accessType=DOWNLOAD", 
+                "accessURL": "https://data.example_agency.gov/views/ykv5-fn9s/rows.csv?accessType=DOWNLOAD", 
                 "format": "text/csv"
             }, 
             {
-                "accessURL": "https://explore.data.gov/views/ykv5-fn9s/rows.json?accessType=DOWNLOAD", 
+                "accessURL": "https://data.example_agency.gov/views/ykv5-fn9s/rows.json?accessType=DOWNLOAD", 
                 "format": "application/json"
             }, 
             {
-                "accessURL": "https://explore.data.gov/views/ykv5-fn9s/rows.xml?accessType=DOWNLOAD", 
+                "accessURL": "https://data.example_agency.gov/views/ykv5-fn9s/rows.xml?accessType=DOWNLOAD", 
                 "format": "application/xml"
             }
         ],
-        "webService": "http://explore.data.gov/api/views/ykv5-fn9s/rows.json", 
+        "webService": "http://data.example_agency.gov/api/views/ykv5-fn9s/rows.json", 
         "license": "Public Domain", 
         "spatial": "United States", 
         "temporal": "2008-09-01T12:00:00Z/2009-05-31T12:00:00Z" 
diff --git a/schema.md b/schema.md
@@ -38,7 +38,7 @@ What to Document -- Datasets and Web APIs
 
 A dataset is an identifiable collection of structured data objects unified by some criteria (authorship, subject, scope, spatial, or temporal extent...). A catalog is a collection of descriptions of datasets; each description is a metadata record. The intention of a data catalog is to facilitate data access by users who are first interested in a particular kind of data, and upon finding a fit-for-purpose dataset, will next want to know how to get the data.
 
-A Web API (**A**pplication **P**rogramming **I**nterface) allows computer programs to dynamically query a dataset using the World Wide Web. For example, a dataset [of farmers markets](https://explore.data.gov/Agriculture/Farmers-Markets-Geographic-Data/wfna-38ey) may be made available for download as a single file (e.g. a CSV), or may be made available to developers through a Web API, such that a computer program could use a ZIP Code to retrieve a list of farmers markets in the ZIP Code area.
+A Web API (**A**pplication **P**rogramming **I**nterface) allows computer programs to dynamically query a dataset using the World Wide Web. For example, a dataset [of farmers markets](http://catalog.data.gov/dataset/farmers-markets-geographic-data) may be made available for download as a single file (e.g. a CSV), or may be made available to developers through a Web API, such that a computer program could use a ZIP Code to retrieve a list of farmers markets in the ZIP Code area.
 
 The catalog file for each agency should list all of the agency's datasets that can be made public, regardless of whether they are distributed by a file download or through a Web API.  The **Endpoint** data element is used to indicate which datasets offer Web APIs (see below for more information on Common Core and Extended metadata elements).
 
@@ -215,15 +215,15 @@ Further Metadata Field Guidance (alphabetical by field)
 
     "distribution": [
             {
-                "accessURL":"https://explore.data.gov/views/ykv5-fn9t/rows.csv?accessType=DOWNLOAD",
+                "accessURL":"https://data.example_agency.gov/views/ykv5-fn9t/rows.csv?accessType=DOWNLOAD",
                 "format":"text/csv"
             },
             {
-                "accessURL":"https://explore.data.gov/views/ykv5-fn9t/rows.json?accessType=DOWNLOAD",
+                "accessURL":"https:/data.example_agency.gov/views/ykv5-fn9t/rows.json?accessType=DOWNLOAD",
                 "format":"application/json"
             },
             {
-                "accessURL":"https://explore.data.gov/views/ykv5-fn9t/rows.xml?accessType=DOWNLOAD",
+                "accessURL":"https://data.example_agency.gov/views/ykv5-fn9t/rows.xml?accessType=DOWNLOAD",
                 "format":"text/xml"
             }
         ]
diff --git a/transportation-case-study.md b/transportation-case-study.md
@@ -52,7 +52,7 @@ Content releasability is determined with value, quality, security, privacy, and
 
 ## Results
 
-The DOT has released [765 datasets or tools](https://explore.data.gov/browse?Dataset-Summary_Agency=Department+of+Transportation) to Data.gov. The processes and policies that have been established under DOT’s approach to Open Government helped DOT build a comprehensive [plan](http://www.dot.gov/sites/dot.dev/files/docs/DOT%20Draft%20Enforcement%20and%20Compliance%20Data%20Report%20-%2005-18-2011%20-%20OCR.pdf) responding to the President’s [memorandum](http://www.gpo.gov/fdsys/pkg/DCPD-201100032/pdf/DCPD-201100032.pdf) on regulatory compliance that was [recognized](http://sunlightfoundation.com/blog/2011/08/31/two-suggestions-for-the-us-national-action-plan/) as a model for other agencies to follow. In May of 2012, DOT, in partnership with the Department of Justice, Department of Labor, and the Consumer Product Safety Commission, launched [Safety.Data.gov](http://safety.data.gov/) with 713 datasets, four (4) mobile apps, 14 resources and public domain software tools, and three (3) challenges or competitions. In September 2012, we held the first safety datapalooza, and the community now has 869 datasets, 10 mobile apps, and six (6) challenges or competitions encouraging public use of safety data from around the government.
+The DOT has released [765 datasets or tools](http://catalog.data.gov/dataset?organization=dot-gov&_organization_limit=0) to Data.gov. The processes and policies that have been established under DOT’s approach to Open Government helped DOT build a comprehensive [plan](http://www.dot.gov/sites/dot.dev/files/docs/DOT%20Draft%20Enforcement%20and%20Compliance%20Data%20Report%20-%2005-18-2011%20-%20OCR.pdf) responding to the President’s [memorandum](http://www.gpo.gov/fdsys/pkg/DCPD-201100032/pdf/DCPD-201100032.pdf) on regulatory compliance that was [recognized](http://sunlightfoundation.com/blog/2011/08/31/two-suggestions-for-the-us-national-action-plan/) as a model for other agencies to follow. In May of 2012, DOT, in partnership with the Department of Justice, Department of Labor, and the Consumer Product Safety Commission, launched [Safety.Data.gov](http://safety.data.gov/) with 713 datasets, four (4) mobile apps, 14 resources and public domain software tools, and three (3) challenges or competitions. In September 2012, we held the first safety datapalooza, and the community now has 869 datasets, 10 mobile apps, and six (6) challenges or competitions encouraging public use of safety data from around the government.
 
 DOT has already recognized benefits as a result of regulatory transparency efforts. For example, for the first time, FMCSA has begun releasing the information behind its Safety Measurement System (SMS) to the public in bulk, downloadable formats. Business and private citizens are mining this data for potential opportunities. For instance, a windshield repair company looking to grow its business is mining FMCSA information about safety violations to identify new customers. DOT and the public realize a benefit because the commercial vehicle operator customer is using a safer vehicle and operating in compliance with Federal Motor Carrier Safety Regulations. In addition, DOT has pursued innovation in its data release practices:
 * FMCSA released an [API](https://mobile.fmcsa.dot.gov/developer/home.page) and [mobile application](https://www.fmcsa.dot.gov/safety-security/saferbus/saferbus.aspx) to help people easily access a bus
@@ -72,7 +72,7 @@ foundation for further innovation. DOT took the vision for the [safety community
 * [DOT Open Government](http://www.dot.gov/open)
 * [DOT Data Inventory](http://www.dot.gov/open/data)
 * [DOT Regulatory Compliance Plan](http://www.dot.gov/sites/dot.dev/files/docs/DOT%20Draft%20Enforcement%20and%20Compliance%20Data%20Report%20-%2005-18-2011%20-%20OCR.pdf)
-* [DOT on Data.gov](https://explore.data.gov/browse?Dataset-Summary_Agency=Department+of+Transportation)
+* [DOT on Data.gov](http://catalog.data.gov/dataset?organization=dot-gov&_organization_limit=0)
 * [Safety community on Data.gov](http://safety.data.gov)
 
 

Original file line number	Diff line number	Diff line change
`@@ -38,7 +38,7 @@ What to Document -- Datasets and Web APIs`
`38`	`38`
`39`	`39`	`A dataset is an identifiable collection of structured data objects unified by some criteria (authorship, subject, scope, spatial, or temporal extent...). A catalog is a collection of descriptions of datasets; each description is a metadata record. The intention of a data catalog is to facilitate data access by users who are first interested in a particular kind of data, and upon finding a fit-for-purpose dataset, will next want to know how to get the data.`
`40`	`40`
`41`		`-A Web API (Application Programming Interface) allows computer programs to dynamically query a dataset using the World Wide Web. For example, a dataset [of farmers markets](https://explore.data.gov/Agriculture/Farmers-Markets-Geographic-Data/wfna-38ey) may be made available for download as a single file (e.g. a CSV), or may be made available to developers through a Web API, such that a computer program could use a ZIP Code to retrieve a list of farmers markets in the ZIP Code area.`
	`41`	`+A Web API (Application Programming Interface) allows computer programs to dynamically query a dataset using the World Wide Web. For example, a dataset [of farmers markets](http://catalog.data.gov/dataset/farmers-markets-geographic-data) may be made available for download as a single file (e.g. a CSV), or may be made available to developers through a Web API, such that a computer program could use a ZIP Code to retrieve a list of farmers markets in the ZIP Code area.`
`42`	`42`
`43`	`43`	`The catalog file for each agency should list all of the agency's datasets that can be made public, regardless of whether they are distributed by a file download or through a Web API. The Endpoint data element is used to indicate which datasets offer Web APIs (see below for more information on Common Core and Extended metadata elements).`
`44`	`44`
`@@ -215,15 +215,15 @@ Further Metadata Field Guidance (alphabetical by field)`
`215`	`215`
`216`	`216`	`"distribution": [`
`217`	`217`	`{`
`218`		`- "accessURL":"https://explore.data.gov/views/ykv5-fn9t/rows.csv?accessType=DOWNLOAD",`
	`218`	`+ "accessURL":"https://data.example_agency.gov/views/ykv5-fn9t/rows.csv?accessType=DOWNLOAD",`
`219`	`219`	`"format":"text/csv"`
`220`	`220`	`},`
`221`	`221`	`{`
`222`		`- "accessURL":"https://explore.data.gov/views/ykv5-fn9t/rows.json?accessType=DOWNLOAD",`
	`222`	`+ "accessURL":"https:/data.example_agency.gov/views/ykv5-fn9t/rows.json?accessType=DOWNLOAD",`
`223`	`223`	`"format":"application/json"`
`224`	`224`	`},`
`225`	`225`	`{`
`226`		`- "accessURL":"https://explore.data.gov/views/ykv5-fn9t/rows.xml?accessType=DOWNLOAD",`
	`226`	`+ "accessURL":"https://data.example_agency.gov/views/ykv5-fn9t/rows.xml?accessType=DOWNLOAD",`
`227`	`227`	`"format":"text/xml"`
`228`	`228`	`}`
`229`	`229`	`]`