Department of the Treasury
Enterprise Data Inventory - Volume and composition over time
M-13-13 Milestone 11 - May 31st 2016
OMB Review Complete: OMB has completed the agency review for this milestone. Agencies should contact their OMB desk officer if anything looks incorrect.
Leading Indicators
These indicators are reviewed by the Office of Management and Budget
| Review Status | complete |
|---|---|
| Reviewer | Bryant Renaud |
| Last Updated | December 5, 2017, 11:22 am EST by Rebecca Williams |
Assessment Summary
PDL is Red: Fails to provide human-readable list of datasets on https://www.treasury.gov/resource-center/data-chart-center/digitalstrategy/Pages/data.aspx
Public Engagement is Red: IDC responses do not specify 2-way mechanism for feedback.
Other: PDL (https://www.treasury.gov/jsonfiles/data.json) is distinct from EDI (https://www.treasury.gov/jsonfiles/enterprise_data_inventory.json).
Inventory Composition
Public Dataset Status
Dataset Link Quality
| Status | Indicator | Automated Metrics | ||
|---|---|---|---|---|
| Overall Progress this Milestone | ||||
| Inventory Updated this Quarter | ||||
| 435 | Number of Datasets | |||
| 5 | Number of APIs | |||
| 10 | Bureaus represented | |||
| 100% | Percentage of bureaus represented | |||
| 17 | Programs represented | |||
| 17.9% | Percentage of programs represented | |||
| 237 | Number of public datasets | |||
| 3 | Number of restricted public datasets | |||
| 195 | Number of non-public datasets | |||
| 83.5% | Percentage growth in records since last quarter | |||
| To a great extent (50-75%) | To what extent is your agency’s Enterprise Data Inventory (EDI) complete? | |||
| See below | What steps have you taken to ensure your Enterprise Data Inventory is complete | |||
| The Fiscal Service continuously monitors and updates the current Enterprise Data Inventory with an emphasis on nonpublic data sets. Fiscal Service is evaluating existing policies and procedures for collection and update of the data inventory. FinCEN continuously monitors and updates the Enterprise Data Inventory as needed. OCC Continuously monitors and updates the Enterprise Data Inventory as needed. TTB reviews the electronic dataset inventory on a quarterly basis to ensure EDI is complete. TTB's Office of the Chief Information Officer, the Regulations and Rulings Division, and the Records Management organizations also work closely together to ensure systems are properly identified, documented, and added to the inventory when obtained or new public datasets of existing information are created. US Mint: Consulted with division chiefs of each division of the US Mint to ensure that all data set produced or used by the division are included in the Enterprise Data Inventory. | ||||
| Agency provides a public Enterprise Data Inventory on Data.gov | ||||
| Agency provided updated Enterprise Data Inventory to OMB | ||||
| 61.2% | License specified | Crawl details | ||
| Number of datasets with redactions | ||||
| Percent of datasets with redactions | ||||
| Status | Indicator | Automated Metrics |
|---|---|---|
| Overall Progress this Milestone | ||
| 237 | Number of Datasets | Crawl details |
| Number of Collections | Crawl details | |
| 237 | Number of datasets not contained in a collection | Crawl details |
| 237 | Number of Public Datasets with File Downloads | Crawl details |
| 5 | Number of APIs | Crawl details |
| 5 | Number of public APIs | Crawl details |
| Number of restricted public APIs | Crawl details | |
| Number of non-public APIs | Crawl details | |
| 526 | Total number of access and download links | Crawl details |
| Quality Check: Links are sufficiently working | Crawl details | |
| 379 | Quality Check: Accessible links | Crawl details |
| 90 | Quality Check: Redirected links | Crawl details |
| 47 | Quality Check: Error links | Crawl details |
| 10 | Quality Check: Broken links | Crawl details |
| 46.2 | Quality Check: Percentage of download links in correct format as specified in metadata | Crawl details |
| 82.3 | Quality Check: Percentage of download links in HTML | Crawl details |
| 10.3 | Quality Check: Percentage of download links in PDF | Crawl details |
| Percentage growth in records since last quarter | ||
| 100% | Valid Metadata | Crawl details |
| /data exists | Crawl details | |
| Provides datasets in human-readable form on /data | ||
| /data.json | Crawl details | |
| Harvested by data.gov | ||
| 237 | Number of public datasets | Crawl details |
| Number of restricted public datasets | Crawl details | |
| Number of non-public datasets | Crawl details | |
| Percent growth of public datasets | ||
| Percent growth of restricted public datasets | ||
| Percent growth of non-public datasets | ||
| Percent datasets licensed as U.S. Public Domain | ||
| 61.2 | Percent datasets licensed as Creative Commons Zero | |
| Percent datasets with other licenses | ||
| 38.8 | Percent datasets with no license |
| Status | Indicator | Automated Metrics | ||
|---|---|---|---|---|
| Overall Progress this Milestone | ||||
| Description of feedback mechanism delivered | Crawl details | |||
| Data release is prioritized through public engagement | ||||
| Provided narrative evidence of data improvements based on public feedback this quarter | ||||
| Feedback loop is closed, 2 way communication | ||||
| See below | Link to or description of Feedback Mechanism | |||
| https://www.treasury.gov/resource-center/data-chart-center/digitalstrategy/pages/default.aspx | ||||
| Provides valid contact point information for all datasets | ||||
| Status | Indicator | Automated Metrics | ||
|---|---|---|---|---|
| Overall Progress this Milestone | ||||
| Data Publication Process Delivered | Crawl details | |||
| Information that should not to be made public is documented with agency's OGC | ||||
| See below | 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. | ||||
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 | Valid |
| Detected Data.json Schema | federal-v1.1 |
| Datasets with Valid Metadata | 100%(237 of 237) |
| Valid Schema | Valid |
| Datasets | 237 |
| Number of Collections | 0 |
| Number of datasets not in a collection | 237 |
| Datasets with Distribution URLs | 100% (237 of 237) |
| Datasets with Download URLs | 100% (237 of 237) |
| Total Distribution URLs | 526 |
| Total Download URLs | 274 |
| Total APIs | 5 |
| Public APIs | 5 |
| Restricted Public APIs | 0 |
| Non-public APIs | 0 |
| Public Datasets | 237 |
| Restricted Public Datasets | 0 |
| Non-public Datasets | 0 |
| Normally there would be a set of quality assurance fields here to verify that the download links included within the metadata are functioning properly, but the results of those tests are not currently available. | |
| Bureaus Represented | 10 |
| Programs Represented | 17 |
| License Specified | 61.2% (145 of 237) |
| Datasets with Redactions | 0.0% (0 of 237) |
| Redactions without explanation (rights field) | 0.0% (0 of 237) |
| File Size | 461.35KB |
| Last modified | Friday, 27-May-2016 13:16:24 EDT |
| Last crawl | Tuesday, 31-May-2016 00:03:20 EDT |
| Analyze archive copies | Analyze archive from 2016-05-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 | Tuesday, 31-May-2016 00:03:17 EDT |
| Last crawl | Tuesday, 31-May-2016 00:03:18 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 | Tuesday, 31-May-2016 00:03:18 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.