Date specified: Friday, 31-May-2019 09:16:54 EDT
Date of digitalstrategy.json file: Wednesday, 18-Dec-2013 09:47:54 EST
1.2.4 Develop Data Inventory Schedule - Summary
Summarize the Inventory Schedule
In 2005 the EPA developed a metadata catalog for Agency datasets known as the Environmental Dataset Gateway (EDG). In response to Project Open Data requirements the EPA CIO issued an Agency-wide data call in Fall of 2013 asking all EPA organizations to register their datasets in EDG. Since that time the Agency has been committed to increasing the percentage of EPA data cataloged within the EDG. The Office of Environmental Information works with the Agency's Information Management Officers on an ongoing basis to encourage them to ensure that data within their program offices are registered in the EDG and has increased its network of stakeholders to ensure that any datasets not identified during the 2013 data call are registered in EDG.
1.2.5 Develop Data Inventory Schedule - Milestones
|Title||Provide reports to programs to identify metadata holes.|
|Description||EPA uses its registry of IT Systems, READ, to identify datasets that may not be cataloged in the EDG. The EDG team works with the data stewardship network to identify and catalog the missing datasets.|
|Description of how this milestone expands the Inventory||This milestone allows EPA to identify and catalog new datasets that were not identified in the original 2013 data call within the Agency's Environmental Dataset Gateway, the metadata catalog which is used to create the Enterprise Data Inventory.|
|Description of how this milestone enriches the Inventory||This milestone brings new and important datasets into EPA's Enterprise Data Inventory.|
|Description of how this milestone opens the Inventory||This milestones provides additional datasets that are publicly available through both the EDG and data.gov.|
1.2.6 Develop Customer Feedback Process
Describe the agency's process to engage with customers
EPA interacts with the public on its data in numerous ways including public meetings/forums, feedback buttons on websites, webinars, mailboxes, FOIA Online and help desks. Recently the Agency launched an online public data forum to communicate with the public about its data in a fully transparent manner: http://developer.epa.gov/forums/forum/dataset-qa/. This forum enables two-way, transparent feedback between the Agency and the public. It can be accessed through three different webpages: the Environmental Dataset Gateway (EDG) webpage, the Developer Central webpage, and EPA's Digital Strategy webpage. The forum shows both the public user's question and the Agency's answer and categorizes questions to increase discoverability about specific topics. Development work is underway to embed the forum into the Agency's metadata stylesheet. This would allow people to ask questions about a specific dataset directly from a metadata record and have that question routed to the metadata owner for response.
In addition to the Forum, EPA has developed an error correction tool which allows the public to report errors that they find relating to data, especially in relation to the geographic locations of data points. The errors are routed through a system that returns feedback to the person who has reported the error.
1.2.7 Develop Data Publication Process
Describe the agency's data publication process
EPA has a number of policies and procedures concerning the publication of Agency data. The Enterprise Information Management Policy requires all EPA Organization officials, employees, and individuals or non-EPA organizations, if applicable, to ensure information is cataloged and or labeled with metadata. This includes geographic references, as appropriate, in EPA and Federal-wide registries, repositories or other information systems. The EPA GeoPlatform Publishing Workflow Standard Operating Procedure and the EPA Environmental Dataset Gateway (EDG) Governance Structure and Standard Operating Procedure outline the details of EPA data publishing.
EPA provides a range of tools and registry content (e.g. Reusable Component Services, Environmental Dataset Gateway, and Data Element Registry) through its System of Registries located at: www.epa.gov/sor. EPA is continuing efforts to document APIs through the development of an Agency-wide API Strategy. The proposed strategy is based on 18F's API standards. The proposal encourages the use of api.data.gov's API management platform. In addition, APIs produced by the EPA should be described using one of the common API definition formats (such as Swagger, API Blueprint and RAML). The strategy is being finalized and an Agency-wide communication plan is being developed. This communication plan will include Standard Operating Procedures (SOPs) that require API developers to register dataset APIs in the EPA's Environmental Dataset Gateway, which will allow these APIs to become part of the EPA's EDI/PDL. All other APIs will be registered in EPA's Reusable Components Services (RCS).