Department of State
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 | August 17, 2016, 4:10 pm EDT by Bryant Renaud |
Assessment Summary
EDI is Red: Fails to document non-public, and restricted public datasets. Fails to document any outstanding APIs see https://www.google.com/#q=API+site:state.gov For instructions on how to properly document APIs see OMB guidance https://project-open-data.cio.gov/v1.1/api/. Fails to document any outstanding Licensing information.
PDL is Yellow: Agency fails to provides datasets in human-readable form on agency /data page.
Public Engagement is Red: The Department of State does not have a transparent, two-way feedback mechanism for potential users to ask questions or provide feedback on datasets.
Inventory Composition
Public Dataset Status
Dataset Link Quality
Status | Indicator | Automated Metrics | ||
---|---|---|---|---|
Overall Progress this Milestone | ||||
Inventory Updated this Quarter | ||||
108 | Number of Datasets | |||
Number of APIs | ||||
1 | Bureaus represented | |||
25.0% | Percentage of bureaus represented | |||
4 | Programs represented | |||
17.4% | Percentage of programs represented | |||
108 | Number of public datasets | |||
Number of restricted public datasets | ||||
Number of non-public datasets | ||||
0.0% | Percentage growth in records since last quarter | |||
To some extent (25-50%) | 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 Department is developing an Enterprise Data Catalog which serves as a tool for internal customers to register their datasets. This will also serve as a tool for search and discovery within the Department. There are two initiatives within the Department that provide a platform for communicating and collaborating with bureaus and offices. Enterprise Data Quality Initiative Knowledge Management Working Group | ||||
Agency provides a public Enterprise Data Inventory on Data.gov | ||||
Agency provided updated Enterprise Data Inventory to OMB | ||||
0.0% | License specified | Crawl details | ||
Number of datasets with redactions | ||||
Percent of datasets with redactions |
Status | Indicator | Automated Metrics |
---|---|---|
Overall Progress this Milestone | ||
108 | Number of Datasets | Crawl details |
Number of Collections | Crawl details | |
108 | Number of datasets not contained in a collection | Crawl details |
108 | 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 | |
214 | Total number of access and download links | Crawl details |
Quality Check: Links are sufficiently working | Crawl details | |
108 | Quality Check: Accessible links | Crawl details |
21 | Quality Check: Redirected links | Crawl details |
Quality Check: Error links | Crawl details | |
77 | Quality Check: Broken links | Crawl details |
100 | Quality Check: Percentage of download links in correct format as specified in metadata | Crawl details |
10.2 | Quality Check: Percentage of download links in HTML | Crawl details |
58.3 | Quality Check: Percentage of download links in PDF | Crawl details |
36.7 | 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 | ||
108 | Number of public datasets | Crawl details |
Number of restricted public datasets | Crawl details | |
Number of non-public datasets | Crawl details | |
36.7 | 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 | ||
100 | 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 | |||
While the Department does not have a standard twoway feedback mechanism for all data related questions or feedback, bureaus and program offices provide their own communication mechanism. The bureaus and program offices work with their user base to setup the appropriate mechanisms (such as email contact form page). | ||||
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 | |||
The System Owner (new or existing system) will identify all key data sets that can be created and published. The System Owner captures the core metadata information about the data set in iMatrix. The extended metadata, like record layout or permissible values, are entered into the Enterprise Metadata Registry. When entering the metadata the System Owner consults with Data Steward about the correct categorization of the data: public, restricted public, or non-public. Legal will have the responsibility to make the final determination if the data can be open. The iMatrix system owner will designate a user that will perform the metadata extraction process on the EDI, and subsequently process the data into a JSON file. The JSON file will be published on the www.state.gov/data page. This process will be done periodically, and not less than quarterly at the start. Every quarter the Department will target specific bureaus/offices and IT systems within its portfolio to reach out and communicate the Open Data Policy and obtain the datasets that they are currently producing. The list of the datasets will be made available through the Enterprise Data Inventory. Once it is initially entered – the dataset owner will be responsible for the update and maintenance of the dataset and the associated metadata. |
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
Expected Data.json URL | http://www.state.gov/data.json (From USA.gov Directory) |
---|---|
Resolved Data.json URL | http://www.state.gov/data.json |
Number of 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%(108 of 108) - The JSON file is invalid and can't be parsed without special processing |
Valid Schema | Valid |
Datasets | 108 |
Number of Collections | 0 |
Number of datasets not in a collection | 108 |
Datasets with Distribution URLs | 100% (108 of 108) |
Datasets with Download URLs | 98.1% (106 of 108) |
Total Distribution URLs | 214 |
Total Download URLs | 106 |
Total APIs | 0 |
Public APIs | 0 |
Restricted Public APIs | 0 |
Non-public APIs | 0 |
Public Datasets | 108 |
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 | 1 |
Programs Represented | 4 |
License Specified | 0.0% (0 of 108) |
Datasets with Redactions | 0.0% (0 of 108) |
Redactions without explanation (rights field) | 0.0% (0 of 108) |
File Size | 204.65KB |
Last modified | Monday, 30-May-2016 16:30:03 EDT |
Last crawl | Tuesday, 31-May-2016 00:03:17 EDT |
Analyze archive copies | Analyze archive from 2016-05-31 |
Nearby Daily Crawls |
Expected /data URL | http://www.state.gov/data (From USA.gov Directory) |
---|---|
Resolved /data URL | http://www.state.gov/data/ |
Redirects | 1 redirects |
HTTP Status | 200 |
Content Type | text/html |
Last modified | Monday, 30-May-2016 03:10:21 EDT |
Last crawl | Tuesday, 31-May-2016 00:03:16 EDT |
Expected /digitalstrategy.json URL | http://www.state.gov/digitalstrategy.json (From USA.gov Directory) |
---|---|
Resolved /digitalstrategy.json URL | http://www.state.gov/digitalstrategy.json |
Redirects | |
HTTP Status | 200 |
Content Type | application/json |
Valid JSON | Valid |
Last modified | Monday, 30-May-2016 16:30:02 EDT |
Last crawl | Tuesday, 31-May-2016 00:03:16 EDT |
Date specified: Tuesday, 12-Nov-2013 14:16:11 EST
Date of digitalstrategy.json file: Monday, 30-May-2016 16:30:02 EDT1.2.4 Develop Data Inventory Schedule - Summary
Summarize the Inventory Schedule
Milestone 1 / Initial Delivery / November 30, 2013 Number of datasets: 113 Open Datasets: 99 Milestone 1 / 1st Quarterly Update / February 28, 2014 Datasets Expanded: 36 (149 total datasets) Datasets Enriched: 18 Datasets Open: 9 (108 total open datasets) Milestone 3 / 2nd Quarterly Update / May 31, 2014 Datasets Expanded: 72 (221 total datasets) Datasets Enriched: 18 Datasets Open: 9 (117 total open datasets) Milestone 4 / 3rd Quarterly Update / August 30, 2014 Datasets Expanded: 72 (293 total datasets) Datasets Enriched: 36 Datasets Open: 18 (126 total open datasets) Milestone 5 / 4th Quarterly Update / November 30, 2014 Datasets Expanded: 72 (365 total datasets) Datasets Enriched: 36 Datasets Open: 18 (144 total open datasets)
1.2.5 Develop Data Inventory Schedule - Milestones
Title | Initial Delivery |
---|---|
Description | The initial delivery of the Open Data Plan, the Schedule, the Enterprise Data Inventory and the Public Data Listing |
Milestone Date | November 30, 2013 |
Description of how this milestone expands the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Number of datasets: 113 |
Description of how this milestone enriches the Inventory | N/A |
Description of how this milestone opens the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Open Datasets: 99 |
Title | 1st Quarterly Update |
---|---|
Description | Update Open Data Plan, Schedule, Enterprise Data Inventory and Public Data Listing |
Milestone Date | February 28, 2014 |
Description of how this milestone expands the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Datasets Expanded: 36 (149 total datasets) |
Description of how this milestone enriches the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Datasets Enriched: 18 |
Description of how this milestone opens the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Datasets Open: 9 (108 total open datasets) |
Title | 2nd Quarterly Update |
---|---|
Description | Update Open Data Plan, Schedule, Enterprise Data Inventory and Public Data Listing |
Milestone Date | May 31, 2014 |
Description of how this milestone expands the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Number of datasets: 72 (221 total datasets) |
Description of how this milestone enriches the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Datasets Enriched: 18 |
Description of how this milestone opens the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Open Datasets: 9 (117 total open datasets) |
Title | 3rd Quarterly Update |
---|---|
Description | Update Open Data Plan, Schedule, Enterprise Data Inventory and Public Data Listing |
Milestone Date | August 30, 2014 |
Description of how this milestone expands the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Number of datasets: 72 (293 total datasets) |
Description of how this milestone enriches the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Datasets Enriched: 36 |
Description of how this milestone opens the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Open Datasets: 18 (126 total open datasets) |
Title | 4th Quarterly Update |
---|---|
Description | Update Open Data Plan, Schedule, Enterprise Data Inventory and Public Data Listing |
Milestone Date | November 30, 2014 |
Description of how this milestone expands the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Number of datasets: 72 (365 total datasets) |
Description of how this milestone enriches the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Datasets Enriched: 36 |
Description of how this milestone opens the Inventory | See paragraph 1.2.7 Develop Data Publication Process, Open Datasets: 18 (144 total open datasets) |
1.2.6 Develop Customer Feedback Process
Describe the agency's process to engage with customers
Identifying and engaging with key data customers to help determine the value of federal data assets can help agencies prioritize those of highest value for quickest release. Customers will be engaged through blog entries, email, forms on the www.State.gov/open web page, and other means as appropriate. Customers include public as well as government stakeholders. Internal customers will use blogs, email and Corridor (the Department social media site) to interact with data owners directly. The Department will evaluate public and private input and reflect on how to incorporate it into their data management practices. The Department will regularly review its evolving customer feedback and public engagement strategy and develop criteria for prioritizing the opening of data assets, accounting for factors such as the quantity and quality of user demand, internal management priorities, and agency mission relevance.
1.2.7 Develop Data Publication Process
Describe the agency's data publication process
The System Owner (new or existing system) will identify all key data sets that can be created and published. The System Owner captures the core metadata information about the data set in iMatrix. The extended metadata, like record layout or permissible values, are entered into the Enterprise Metadata Registry. When entering the metadata the System Owner consults with Data Steward about the correct categorization of the data: public, restricted public, or non-public. Legal will have the responsibility to make the final determination if the data can be open. The iMatrix system owner will designate a user that will perform the metadata extraction process on the EDI, and subsequently process the data into a JSON file. The JSON file will be published on the www.state.gov/data page. This process will be done periodically, and not less than quarterly at the start. Every quarter the Department will target specific bureaus/offices and IT systems within its portfolio to reach out and communicate the Open Data Policy and obtain the datasets that they are currently producing. The list of the datasets will be made available through the Enterprise Data Inventory. Once it is initially entered – the dataset owner will be responsible for the update and maintenance of the dataset and the associated metadata.