Department of Commerce

http://www.commerce.gov/

Milestone 7 - May 31st 2015

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 Rebecca Williams
Last Updated September 29, 2015, 5:54 pm EDT by Justin Grimes

Assessment Summary

Enterprise Data Inventory: The EDI grew by 11% since last quarter, however this was after a -89% drop last quarter. To be compliant substantial growth is needed. The EDI includes 487 data assets, but a the Google search for .xls, .csv, .xml, and .json across Commerce component websites produces 10,100,000 dataset results.

Public Data Listing: To be compliant substantial growth and metadata improvements are needed. Only 12 APIs are included in the Public Data Listing. Add featured datasets: https://www.whitehouse.gov/sites/default/files/microsites/ostp/us_open_data_action_plan.pdf, https://www.commerce.gov/economicindicators, http://fedstats.sites.usa.gov/data-releases/ Ensure all APIs are included in the PDL with rich documentation: https://raw.githubusercontent.com/18F/API-All-the-X/gh-pages/_data/individual_apis.yml; https://18f.github.io/API-All-the-X/pages/apis_in_data_catalogs

Public Engagement: To be featured as a best practice going forward, integration with Data.gov, web analytics, and a prioritized schedule based on public feedback is needed. To integrate more seamlessly with Data.gov, work to incorporate their Help Desk API into your feedback mechanism. A first step would be to to include this data request link on your /data page: https://www.data.gov/data-request/?agency_name=52668 When hosting events be sure to add them to Data.gov/events. It is unclear how many views commerce.gov/data obtained, to remedy this work with the DAP team: http://www.digitalgov.gov/services/dap/ Lastly, develop a public schedule to improve the open maturity of your data based on public feedback. Two U.S. local examples include: https://cityofphiladelphia.github.io/slash-data/census/; http://montgomerycountymd.gov/open/Resources/Files/OpenDataImplementationPlan_FY14.pdf; See also: https://cio.gov/wp-content/uploads/filebase/cio_document_library/Open Data Prioritization Toolkit Summary.html

Privacy and Security: To be featured as a best practice, work with your OGC to ensure all "restricted public" and "non-public" datasets are included in the EDI with accessLevel explanations included in the rights field. If any metadata requires redaction, ensure that is redacted precisely, with a presumption for openness: https://project-open-data.cio.gov/redactions/

Human Capital: To be featured as a best practice growth in Open Data dedicated staff time and detailed data governance is needed.

Use & Impact: To be featured as a best practice more detailed examples are needed featuring how Commerce's open data is used to achieve: cost savings, efficiency, fuel for business, improved civic services, informed policy, performance planning, research and scientific discoveries, transparency and accountability, and increased public participation, etc.

Inventory Composition

Public Dataset Status

Dataset Link Quality

Status Indicator Automated Metrics
Overall Progress this Milestone
Inventory Updated this Quarter
492 Number of Datasets
12 Number of APIs
Schedule Delivered Crawl details
10 Bureaus represented
24 Programs represented
472 Number of public datasets
19 Number of restricted public datasets
1 Number of non-public datasets
Inventory > Public listing
+11% Percentage growth in records since last quarter
10,100,000 Spot Check - datasets listed by search engine
Agency provides a public Enterprise Data Inventory on Data.gov
100% License specified Crawl details
Status Indicator Automated Metrics
Overall Progress this Milestone
487 Number of Datasets Crawl details
Number of Collections Crawl details
385 Number of Public Datasets with File Downloads Crawl details
12 Number of APIs Crawl details
409 Total number of access and download links Crawl details
Quality Check: Links are sufficiently working Crawl details
331 Quality Check: Accessible links Crawl details
35 Quality Check: Redirected links Crawl details
Quality Check: Error links Crawl details
18 Quality Check: Broken links Crawl details
+9% Percentage growth in records since last quarter
100% Valid Metadata Crawl details
/data exists Crawl details
/data.json Crawl details
Harvested by data.gov
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://opencommerce.ideascale.com/a/index
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
IKalin@doc.gov Open Data Primary Point of Contact
POCs identified for required responsibilities
Status Indicator Automated Metrics
Overall Progress this Milestone
Identified 5 data improvements for this quarter
See below Primary Uses
Commerce Department data is used in a very wide range of uses from weather forecasting and environmental research, economic analysis and development of trade opportunities to demographic analysis and planning by state and local governments as well as private industry.
Value or impact of data
See below Primary data discovery channels
Commerce has engaged with organizations such as GovLab (Open Data Rountable) and commercial groups such as the ESRI Users Conference to increase awareness of the data Commerce has to offer and to gather feedback from data users on what they need and how they would like to be able to access it.
See below User suggestions on improving data usability
• Create a centralized data catalogue: Organize catalogue of datasets and make them accessible in an easily findable way. Datasets should be catalogued in a common, machine-readable format. • Continue to develop APIs, and provide an interface at each bureau to help add context for APIs. • Establish common, open standards across Commerce for taxonomy, vocabulary, and APIs. • Develop communication channels for direct collaboration with subject matter experts at Commerce, and feedback channels for the private sector to have effective input. • Develop methods to track users: Establish ways to track who is using which datasets. • Improve metadata for datasets throughout DOC. (One suggestion: Hold a “metadata-thon.”) • Meet the needs of diverse data users – ranging from those who just want access to raw data, to those who want more developed information products and answers.
See below User suggestions on additional data releases
Centralization of datasets: each bureau should have one place to identify all datasets o Catalogued in machine-readable formats o PTO: needs to develop better search functions, including for data in image form o Include context and documentation for each dataset  BEA: improve technical documentation to better differentiate between raw and modeled data  PTO: make more information available about the scope of patent rights, including expiration dates, or decisions by the agency and/or courts about patent claims  PTO: Put out data with more context to make it usable by non-experts – eg, trademark transaction data and trademark assignment. o Create a standardized registry that has standard metadata and can be queried with APIs. o Create a site map of bureaus/locations of datasets in lieu of a single site holding all datasets; easier to implement and update; and points of contact for each dataset
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.commerce.gov/data.json (From USA.gov Directory)
Resolved Data.json URL http://www.commerce.gov/data.json
Number of Redirects
HTTP Status 200
Content Type text/plain
Valid JSON Valid
Detected Data.json Schema federal-v1.1
Datasets with Valid Metadata 100%(487 of 487)
Valid Schema Valid
Datasets 487
Datasets with Distribution URLs 81.7% (398 of 487)
Datasets with Download URLs 79.1% (385 of 487)
Total Distribution URLs 431
Total Download URLs 409
Total APIs 12
Public Datasets 467
Restricted Public Datasets 19
Non-public Datasets 1
Bureaus Represented 10
Programs Represented 24
License Specified 100% (487 of 487)
Datasets with Redactions 0.0% (0 of 487)
Redactions without explanation (rights field) 0.0% (0 of 487)
File Size 1.27MB
Last modified Friday, 29-May-2015 14:14:43 EDT
Last crawl Sunday, 31-May-2015 00:28:04 EDT
Analyze archive copies Analyze archive from 2015-05-31
Nearby Daily Crawls
/data page
Expected /data URL http://www.commerce.gov/data (From USA.gov Directory)
Resolved /data URL http://www.commerce.gov/data
Redirects
HTTP Status 0
Content Type
Last crawl Sunday, 31-May-2015 00:27:48 EDT
/digitalstrategy.json
Expected /digitalstrategy.json URL http://www.commerce.gov/digitalstrategy.json (From USA.gov Directory)
Resolved /digitalstrategy.json URL http://www.commerce.gov/digitalstrategy.json
Redirects
HTTP Status 200
Content Type text/plain
Valid JSON Valid
Last crawl Sunday, 31-May-2015 00:27:56 EDT
Digital Strategy

Date specified: Thursday, 28-May-2015 10:50:02 EDT


1.2.4 Develop Data Inventory Schedule - Summary

Summarize the Inventory Schedule


Given the volume and complexity of Commerce's data, we have worked with OMB and GSA to build an EDI that complies with OMB policy. However, we are still working to fully integrate our millions of data sets into a single data-management system.

1.2.5 Develop Data Inventory Schedule - Milestones

TitleMilestone 1 - Expand and Open EDI
DescriptionThe Department of Commerce will initially focus on expanding and opening its Enterprise Data Inventory. To this end, the Open Government Senior Leaders, in collaboration with Agency CIOs, Data Stewards, and the Data.gov Points of Contact, will continue to work with Commerce Office of Open Government and Privacy to identify, prioritize and submit additional public, non-public, and restricted-public datasets to the Department. In addition, the Open Government Senior Leaders and Data.gov Points of Contact will continue the development of an Open Data process and guidance that expedite the publication of its datasets in the future. At the end of Q1, Commerce will submit an updated EDI to OMB. Over the second quarter, from February 28 to May 31, Commerce and its component bureaus will continue to input into its EDI additional datasets. The Department will also continue to collaborate with its Data Stewards to update its customer feedback and outreach efforts. At the end of Q2, Commerce will submit an updated EDI to OMB.
Milestone DateFebruary 28, 2014
Description of how this milestone expands the InventoryThe Department’s Enterprise Data Inventory (EDI), as defined by OMB guidance, is the same as the Public Data Listing (PDL) in that none of the public data assets in the Department’s data catalog have been redacted.
Description of how this milestone enriches the InventoryAs part of an ongoing effort, the Department is making every effort to conduct and publish a comprehensive inventory of our total data assets. However, due to the size, history and complexity of the Department of Commerce’s Bureaus, the current inventory available on commerce.gov/data.json represents less than 1 percent of the actual enterprise.
Description of how this milestone opens the Inventory
TitleMilestone 2 - Enrich EDI and Public Datasets
DescriptionCommerce's data sets are now integrated into one .json file that is harvested by Data.gov
Milestone DateMay 31, 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


Since the last milestone report, the following actions were taken in order to improve the Department’s mechanisms for public feedback:
•	Added functions to our data.commerce.gov web page that include a “suggest a dataset” web form and also an “Engage” set of tools to connect via social media.
•	Went live with a public, Department-level Github account that is publishing public repos and responding to issue posts.
•	Started hosting “office hours” with the Office of the Chief Data Officer where the public will be able to present questions and comments
•	Launched the Commerce Data Advisory Council that is, among other things, seeking to channel industry feedback for the entire Department.

1.2.7 Develop Data Publication Process

Describe the agency's data publication process