Department of Defense

http://www.defense.gov/

Milestone 5 - November 30th 2014

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 Jamie Berryhill (
Last Updated January 12, 2015, 11:59 am EST by paulOMB

Assessment Summary

EDI: Did not the update the EDI for November 2014. /digitalstrategy page has not been updated since February 2014.

PDL: DOD has not added a new dataset on data.gov since August 2014, when it added 5. Prior to that, DOD added 367 in June 2014. These are the only two months in the last year that DOD has added datasets.

Public Engagement: Feedback via email. No proof of two-way communication or prioritization based on feedback. OMB gave DOD Yellow on this measure for every milestone so far, but DOD has not improved their feedback mechanism, so will now be red until a transparent 2-way communication channel exists.

Privacy & Security: Process lacks details of roles, responsibilities, and workflows.

Use & Impact: Did not submit.

Public Dataset Status

Status Indicator Automated Metrics
Overall Progress this Milestone
Inventory Updated this Quarter
Number of Datasets
Number of APIs
Schedule Delivered Crawl details
Bureaus represented
Programs represented
Number of public datasets
Number of restricted public datasets
Number of non-public datasets
Inventory > Public listing
Percentage growth in records since last quarter
Schedule Risk for Nov 30, 2014
Spot Check - datasets listed by search engine
Agency provides a public Enterprise Data Inventory on Data.gov
License specified Crawl details
Status Indicator Automated Metrics
Overall Progress this Milestone
373 Number of Datasets Crawl details
Number of Collections Crawl details
371 Number of Public Datasets with File Downloads Crawl details
Number of 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
0.0 Percentage growth in records since last quarter
99.7 Valid Metadata Crawl details
/data exists Crawl details
/data.json Crawl details
Harvested by data.gov
10552 Views on data.gov for the quarter
Status Indicator Automated Metrics
Overall Progress this Milestone
Description of feedback mechanism delivered Crawl details
Data release is prioritized through public engagement
Feedback loop is closed, 2 way communication
See below Link to or description of Feedback Mechanism
http://data.defense.gov/ContactUs.aspx
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
Status Indicator Automated Metrics
Overall Progress this Milestone
See below Open Data Primary Point of Contact
william.erwin@osd.mil
POCs identified for required responsibilities
Status Indicator Automated Metrics
Overall Progress this Milestone
Identified 5 data improvements for this quarter
Not Provided Primary Uses
Not Provided Value or impact of data
Not Provided Primary data discovery channels
Not Provided User suggestions on improving data usability
Not Provided User suggestions on additional data releases
Digital Analytics Program on /data

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 http://www.defense.gov/data.json
Number of Redirects
HTTP Status 200
Content Type application/json
Valid JSON Valid
Datasets with Valid Metadata 99.7%(372 of 373)
Valid Schema Invalid
For more complete and readable validation results, see the full schema validator results
Schema Errors There are validation errors on 1 records

Errors on record 96:
modified
  • does not match the regex pattern ^([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?$
  • does not match the regex pattern ^P(?=\w*\d)(?:\d+Y|Y)?(?:\d+M|M)?(?:\d+W|W)?(?:\d+D|D)?(?:T(?:\d+H|H)?(?:\d+M|M)?(?:\d+(?:\­.\d{1,2})?S|S)?)?$
  • does not match the regex pattern ^([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?(\/)([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?$
  • does not match the regex pattern ^([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?(\/)P(?=\w*\d)(?:\d+Y|Y)?(?:\d+M|M)?(?:\d+W|W)?(?:\d+D|D)?(?:T(?:\d+H|H)?(?:\d+M|M)?(?:\d+(?:\­.\d{1,2})?S|S)?)?$
  • does not match the regex pattern ^P(?=\w*\d)(?:\d+Y|Y)?(?:\d+M|M)?(?:\d+W|W)?(?:\d+D|D)?(?:T(?:\d+H|H)?(?:\d+M|M)?(?:\d+(?:\­.\d{1,2})?S|S)?)?\/([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?$
  • does not match the regex pattern ^R\d*\/([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?\/P(?=\w*\d)(?:\d+Y|Y)?(?:\d+M|M)?(?:\d+W|W)?(?:\d+D|D)?(?:T(?:\d+H|H)?(?:\d+M|M)?(?:\d+(?:\­.\d{1,2})?S|S)?)?$
  • failed to match at least one schema
Datasets 373
Datasets with Distribution URLs 0.0% (0 of 373)
Total Distribution URLs 0
Public Datasets 373
Restricted Public Datasets 0
Non-public Datasets 0
Bureaus Represented 9
Programs Represented 10
File Size 397.78KB
Last modified Friday, 22-Aug-2014 11:32:57 EDT
Last crawl Saturday, 29-Nov-2014 23:05:33 EST
Analyze archive copies Analyze archive from 2014-11-30
/data page
Expected /data URL http://www.defense.gov/data (From USA.gov Directory)
Resolved /data URL http://www.defense.gov/data/
Redirects 1 redirects
HTTP Status 200
Content Type text/html; charset=utf-8
Last crawl Saturday, 29-Nov-2014 23:05:33 EST
/digitalstrategy.json
Expected /digitalstrategy.json URL http://www.defense.gov/digitalstrategy.json (From USA.gov Directory)
Resolved /digitalstrategy.json URL http://www.defense.gov/digitalstrategy.json
Redirects
HTTP Status 200
Content Type application/json
Valid JSON Valid
Last modified Friday, 28-Feb-2014 10:28:00 EST
Last crawl Saturday, 29-Nov-2014 23:05:33 EST
Digital Strategy

Date specified: Thursday, 27-Feb-2014 06:14:07 EST

Date of digitalstrategy.json file: Friday, 28-Feb-2014 10:28:00 EST

1.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

TitleDesignate Agency Data Inventory
DescriptionSelect DoD repository to be used as the “enterprise data inventory”
Milestone Date30 November 2013
Description of how this milestone expands the InventoryContains over 4000 IT systems which have datasets
Description of how this milestone enriches the InventoryContains multiple categorizations of the contents of datasets
Description of how this milestone opens the InventoryRepository is at Controlled Unclassified Information level and is not releasable to public
TitleEnhance Enterprise Data Inventory to track dataset releasability
DescriptionImplement 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 Dateo/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
TitlePromulgate guidance
DescriptionIssue 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 Dateo/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.