Department of Defense
Enterprise Data Inventory - Volume and composition over time
Milestone 22 - February 28th 2019
Current Milestone: The milestone selected is still in progress. The Automated Metrics will update daily until the milestone date.
OMB Review Has Not Begun: OMB has not begun reviewing the agency for this milestone. The review will begin after the milestone date.
Leading Indicators
These indicators are reviewed by the Office of Management and Budget
| Review Status | |
|---|---|
| Reviewer | |
| Last Updated |
Assessment Summary
| Status | Indicator | Automated Metrics |
|---|---|---|
| Overall Progress this Milestone | ||
| Inventory Updated this Quarter | ||
| Number of Datasets | ||
| Number of APIs | ||
| Bureaus represented | ||
| Percentage of bureaus represented | ||
| Programs represented | ||
| Percentage of programs represented | ||
| Number of public datasets | ||
| Number of restricted public datasets | ||
| Number of non-public datasets | ||
| Percentage growth in records since last quarter | ||
| To what extent is your agency’s Enterprise Data Inventory (EDI) complete? | ||
| What steps have you taken to ensure your Enterprise Data Inventory is complete | ||
| Agency provides a public Enterprise Data Inventory on Data.gov | ||
| Agency provided updated Enterprise Data Inventory to OMB | ||
| License specified | Crawl details | |
| Number of datasets with redactions | ||
| Percent of datasets with redactions |
| Status | Indicator | Automated Metrics |
|---|---|---|
| Overall Progress this Milestone | ||
| Number of Datasets | Crawl details | |
| Number of Collections | Crawl details | |
| Number of datasets not contained in a collection | Crawl details | |
| Number of Public Datasets with File Downloads | Crawl details | |
| Number of APIs | Crawl details | |
| Number of public APIs | Crawl details | |
| Number of restricted public APIs | Crawl details | |
| Number of non-public APIs | Crawl details | |
| Total number of access and download links | Crawl details | |
| Quality Check: Links are sufficiently working | Crawl details | |
| Quality Check: Accessible links | Crawl details | |
| Quality Check: Redirected links | Crawl details | |
| Quality Check: Error links | Crawl details | |
| Quality Check: Broken links | Crawl details | |
| Quality Check: Percentage of download links in correct format as specified in metadata | Crawl details | |
| Quality Check: Percentage of download links in HTML | Crawl details | |
| Quality Check: Percentage of download links in PDF | Crawl details | |
| Percentage growth in records since last quarter | ||
| Valid Metadata | Crawl details | |
| /data exists | Crawl details | |
| Provides datasets in human-readable form on /data | ||
| /data.json | Crawl details | |
| Harvested by data.gov | ||
| 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 | ||
| Percent datasets licensed as Creative Commons Zero | ||
| Percent datasets with other licenses | ||
| 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 | ||
| Link to or description of Feedback Mechanism | ||
| 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 | ||
| Describe the agency's data publication process |
| Status | Indicator | Automated Metrics |
|---|---|---|
| Overall Progress this Milestone | ||
| Open Data Primary Point of Contact | ||
| POCs identified for required responsibilities | ||
| Chief Data Officer (if applicable) |
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.defense.gov/data.json (From USA.gov Directory) |
|---|---|
| Resolved Data.json URL | https://www.defense.gov/data.json |
| Number of Redirects | 1 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%(177 of 177) - The JSON file is invalid and can't be parsed without special processing |
| Valid Schema | Valid |
| Datasets | 177 |
| Number of Collections | 0 |
| Number of datasets not in a collection | 177 |
| Datasets with Distribution URLs | 100% (177 of 177) |
| Datasets with Download URLs | 97.2% (172 of 177) |
| Total Distribution URLs | 188 (but only 25 accessible) |
| Total Download URLs | 183 |
| Total APIs | 0 |
| Public APIs | 0 |
| Restricted Public APIs | 0 |
| Non-public APIs | 0 |
| Public Datasets | 177 |
| 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 To see a detailed breakdown of these issues, download the full error log as a CSV |
|
| Server Not Found | 2.1% (4 of 188) |
| Working links (HTTP 2xx) | 13.3% (25 of 188) |
| Broken links (HTTP 4xx) | 33.0% (62 of 188) |
| Error Links (HTTP 5xx) | 0.0% (0 of 188) |
| Redirected Links (HTTP 3xx) | 51.6% (97 of 188) |
| Correct format | 100% (25 of 25) |
| PDF for raw data | 8.0% (2 of 25) |
| HTML for raw data | 64.0% (16 of 25) |
| Bureaus Represented | 9 |
| Programs Represented | 6 |
| License Specified | 100% (177 of 177) |
| Datasets with Redactions | 0.0% (0 of 177) |
| Redactions without explanation (rights field) | 0.0% (0 of 177) |
| File Size | 214.33KB |
| Last modified | Wednesday, 26-Sep-2018 13:19:43 EDT |
| Last crawl | Friday, 14-Dec-2018 23:30:59 EST |
| Nearby Daily Crawls | |
| Expected /data URL | http://www.defense.gov/data (From USA.gov Directory) |
|---|---|
| Resolved /data URL | https://data.defense.gov/ |
| Redirects | 2 redirects |
| HTTP Status | 200 |
| Content Type | text/html; charset=utf-8 |
| Last crawl | Friday, 14-Dec-2018 23:30:34 EST |
| Expected /digitalstrategy.json URL | http://www.defense.gov/digitalstrategy.json (From USA.gov Directory) |
|---|---|
| Resolved /digitalstrategy.json URL | https://www.defense.gov/digitalstrategy.json |
| Redirects | 1 redirects |
| HTTP Status | 200 |
| Content Type | application/json |
| Valid JSON | Valid |
| Last modified | Wednesday, 26-Sep-2018 13:19:42 EDT |
| Last crawl | Friday, 14-Dec-2018 23:30:34 EST |
Date specified: Thursday, 27-Feb-2014 06:14:07 EST
Date of digitalstrategy.json file: Wednesday, 26-Sep-2018 13:19:42 EDT1.2.4 Develop Data Inventory Schedule - Summary
Summarize the Inventory Schedule
The DoD Information Technology Portfolio Repository (DITPR) houses information that keeps track of DoD IT systems. DITPR currently has information about 4,000 systems and the datasets contained in those systems. DoD will identify datasets that are publicly releasable, and DITPR will be modified to provide status of progress towards exposing releasable data to the public.
1.2.5 Develop Data Inventory Schedule - Milestones
| Title | Designate Agency Data Inventory |
|---|---|
| Description | Select DoD repository to be used as the “enterprise data inventory” |
| Milestone Date | 30 November 2013 |
| Description of how this milestone expands the Inventory | Contains over 4000 IT systems which have datasets |
| Description of how this milestone enriches the Inventory | Contains multiple categorizations of the contents of datasets |
| Description of how this milestone opens the Inventory | Repository is at Controlled Unclassified Information level and is not releasable to public |
| Title | Enhance Enterprise Data Inventory to track dataset releasability |
|---|---|
| Description | Implement changes to the DoD Data Repository to allow collection of information about datasets as public, public restricted, or non-public and the status of progress on making those determined to be public available on www.defense.gov/data or www.data.gov |
| Milestone Date | o/a 30 September 2014 |
| Description of how this milestone expands the Inventory | |
| Description of how this milestone enriches the Inventory | |
| Description of how this milestone opens the Inventory |
| Title | Promulgate guidance |
|---|---|
| Description | Issue guidance to DoD Components directing them to comply with Open Data and make datasets determined to be publicly releasable (all or partial) available with quarterly targets |
| Milestone Date | o/a 1 July 2014 |
| Description of how this milestone expands the Inventory | |
| Description of how this milestone enriches the Inventory | |
| Description of how this milestone opens the Inventory |
1.2.6 Develop Customer Feedback Process
Describe the agency's process to engage with customers
The Department of Defense (DoD) engages customers using a variety of methods. DoD interfaces with service providers and customers to help identify the services that are the most popular and possible high priority candidates for dataset release. Also, the DoD Knowledge Base tool (https://kb.defense.gov) provides insight on the information customers are currently requesting for release. DoD’s Open Data website has a "Contact Us" page inviting customers to enter a description of the data requested for release from the DoD. Customer feedback, resource availability and budget constraints will be considered when prioritizing dataset release candidates.
1.2.7 Develop Data Publication Process
Describe the agency's data publication process
DoD data is subject to the same mature policies, responsibilities, and procedures as DoD information. Bottom line up front: The heads of DoD Components are responsible for ensuring that security and policy reviews are performed on all official DoD information intended for public release. At minimum, the review of information intended for public release must consider the risks to operations security, information security, information assurance, and personally identifiable information. The public release of official DoD information is limited only as necessary to safeguard information requiring protection in the interest of national security or other legitimate governmental interest. The details of DoD’s information release policies, responsibilities and procedures are available in DoD Directive 5230.09, “CLEARANCE OF DOD INFORMATION FOR PUBLIC RELEASE,” August 22, 2008, DoD Instruction 5230.29, “SECURITY AND POLICY REVIEW OF DOD INFORMATION FOR PUBLIC RELEASE,” January 1, 2009, and the Appendix to Enclosure 3 of DoD Instruction 8550.01, “DOD INTERNET SERVICES AND INTERNET-BASED CAPABILITIES,” September 11, 2012.