Department of the Treasury
M-13-13 Milestone 24 - August 31st 2019
Automated Metrics
These metrics are generated by an automated analysis that runs every 24 hours until the end of the quarter at which point they become a historical snapshot
data.json
Expected Data.json URL | http://www.ustreas.gov/data.json (From USA.gov Directory) |
---|---|
Resolved Data.json URL | https://www.treasury.gov/jsonfiles/data.json |
Number of Redirects | 3 redirects |
HTTP Status | 200 |
Content Type | application/json |
Valid JSON | Invalid Check a JSON Validator |
Detected Data.json Schema | federal-v1.1 |
Datasets with Valid Metadata | 100%(278 of 278) - The JSON file is invalid and can't be parsed without special processing |
Valid Schema | Valid |
Datasets | 278 |
Number of Collections | 0 |
Number of datasets not in a collection | 278 |
Datasets with Distribution URLs | 100% (278 of 278) |
Datasets with Download URLs | 100% (278 of 278) |
Total Distribution URLs | 615 (but only 361 accessible) |
Total Download URLs | 322 |
Total APIs | 0 |
Public APIs | 0 |
Restricted Public APIs | 0 |
Non-public APIs | 0 |
Public Datasets | 278 |
Restricted Public Datasets | 0 |
Non-public Datasets | 0 |
The fields below serve as quality assurance to verify that the download links included within the metadata are functioning properly |
|
Server Not Found | 10.1% (62 of 615) |
Working links (HTTP 2xx) | 58.7% (361 of 615) |
Broken links (HTTP 4xx) | 3.7% (23 of 615) |
Error Links (HTTP 5xx) | 7.3% (45 of 615) |
Redirected Links (HTTP 3xx) | 20.2% (124 of 615) |
Correct format | 49.6% (179 of 361) |
PDF for raw data | 11.9% (43 of 361) |
HTML for raw data | 70.9% (256 of 361) |
Bureaus Represented | 10 |
Programs Represented | 18 |
License Specified | 67.3% (187 of 278) |
Datasets with Redactions | 0.0% (0 of 278) |
Redactions without explanation (rights field) | 0.0% (0 of 278) |
File Size | 528.23KB |
Last modified | Friday, 24-May-2019 09:36:23 EDT |
Last crawl | Sunday, 02-Jun-2019 00:35:58 EDT |
Analyze archive copies | Analyze archive from 2019-08-31 |
Nearby Daily Crawls |
Expected /data URL | http://www.ustreas.gov/data (From USA.gov Directory) |
---|---|
Resolved /data URL | https://www.treasury.gov/resource-center/data-chart-center/digitalstrategy/Pages/data.aspx |
Redirects | 3 redirects |
HTTP Status | 200 |
Content Type | text/html; charset=utf-8 |
Last modified | Saturday, 01-Jun-2019 21:56:59 EDT |
Last crawl | Sunday, 02-Jun-2019 00:30:08 EDT |
Expected /digitalstrategy.json URL | http://www.ustreas.gov/digitalstrategy.json (From USA.gov Directory) |
---|---|
Resolved /digitalstrategy.json URL | https://www.treasury.gov/jsonfiles/digitalstrategy.json |
Redirects | 4 redirects |
HTTP Status | 200 |
Content Type | application/json |
Valid JSON | Valid |
Last modified | Monday, 24-Aug-2015 13:36:23 EDT |
Last crawl | Sunday, 02-Jun-2019 00:30:08 EDT |
Date specified: Tuesday, 25-Nov-2014 16:36:11 EST
Date of digitalstrategy.json file: Monday, 24-Aug-2015 13:36:23 EDT1.2.4 Develop Data Inventory Schedule - Summary
Summarize the Inventory Schedule
Treasury Bureaus are working to complete the Enterprise Dataset Inventory.
1.2.5 Develop Data Inventory Schedule - Milestones
1.2.6 Develop Customer Feedback Process
Describe the agency's process to engage with customers
The customers can connect with Treasury by: Email to digital@treasury.gov for all feedback/inquires related to the Open Data Executive Order and Digital Government Strategy. Subscribing to the RSS Feeds of the blogs at http://www.treasury.gov/connect/blog/Pages/default.aspx. Choose to receive the updates via emails. Connect via social media. The details are at http://www.treasury.gov/connect/Pages/default.aspx Contact various offices and bureaus. The details are at Treasury http://www.treasury.gov/connect/Pages/contact-us.aspx
1.2.7 Develop Data Publication Process
Describe the agency's data publication process
Identify: The data set for public publication will be identified based on inputs from the data owner community and the data consumer community. Engaging with the data consumer (also referred to as the customer) using the process outlined in the “Customer Engagement Process” section helps to determine the data sets and the fields that comprise the data set. Review: The data set must be reviewed by relevant officials from:Business Data Owner and System Owner, Office of Privacy and General Counsel, Security Publish: Create metadata for the data set, provide data context description.