Open Data, Content, and Web API Policy
The Departmental Data Release Policy sets the default state of DOT data to open by stating, DOT policy is to make data available at the most detailed level possible, subject only to the limits imposed by data quality and the need to protect national/homeland security, individual privacy, and confidentiality. Further, the policy states, DOT policy is to disseminate data as soon as possible following collection, subject only to the limits imposed by resources, technology, authority, regulation and data quality while protecting security, privacy, and confidentiality. DOT has existing processes for performing pre-dissemination reviews and public disclosure risk assessments. Regardless of the releasability of a dataset, that dataset much be registered in the DOT data inventory.
Over the last year, we have more than doubled the size of our inventory of available data sets. We now have over 2,000 data sets available on Data.gov and also listed in project open data JSON format. The Department of Transportation (DOT) approach to ensuring all data assets from each bureau and program in the agency will be identified and accounted for in its Enterprise Data Inventory is focused on linking various information management programs together. Specifically, the DOT Enterprise Data Inventory is considered complete when each of its Operating Administrations (OAs) has accounted for all datasets that are:
- collected under an OMB-approved Information Collection Request
- contained in Records Disposition Schedules (RDS) and Electronic Information Systems (EIS) list
- covered by a Privacy Act System of Records Notice (SORN)
- associated with an information technology (IT) investment reported on the Exhibit 53
Each OA will register all datasets in the DOT metadata registry.
The DOT Enterprise Data Inventory schedule takes a methodical approach to completing the task. Each DOT Operating Administration (OA) will review data from each of its information management programs to identify a complete list of information collections, record schedules, and IT investments that contain data. Once the list is complete, OAs will proceed with inventorying the datasets contained in those information systems. The milestones are:
January 17, 2014 - Develop OA implementation plan: Each DOT OA will formulate an implementation plan to conduct its data inventory activities, identifying team members and gathering data from its information management programs.
February 28, 2014 - Establish the Universe & analyze releasability: Each DOT OA will analyze the data from its information management programs to identify those that contain data and will gather any information regarding the releasability of those datasets.
April 28, 2014 - Inventory public dataset: Using the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry.
June 30, 2014 - Inventory mission-oriented datasets: Using the data gathered at Milestone 2, each DOT will register its mission-oriented datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
September 29, 2014 - Inventory administrative datasets: DOT will update and finalize its Interim Identification & Prioritization Process and Guidelines to prioritize activities around expanding, enriching, and opening Enterprise Data Inventory.