1. Make Open Data, Content, and Web APIs the New Default
1.1 Issue government-wide open data, content, and web Application Program Interface (API) policy and identify standards and best practices for improved interoperability (OMB)
This can be found here: Project Open Data
18F also has API resources here: Developer Program
1.2 Ensure all new IT systems follow the open data, content, and web API policy and operationalize agency.gov/developer pages (OCC)
Describe Policy: The OCC is working diligently to institutionalize and operationalize the development of IT systems as applicable with openness by default. We are implementing activities to ensure information is managed as an asset across the enterprise. Through the use of Software Development Lifecycle processes, we ensure that are development activities are consistent and reusable throughout the enterprise as well as secure within the data architecture and lifecycle. Activities included in the current implementation are the collection of business requirements, use of open data architectures, user centered design, documented naming standards, data modeling, security architect meetings, dataset publishing support processes, and an enterprise repository of requirements and code. We will continue enhance our development processes through Continuous Improvement as part of our Agile Scrum Development.
Overall Status: In Progress
1.2.3 Governance Tools
The OCC is considering an agency-wide API Strategy building upon 18F's API standards and using api.data.gov's API management platform. In addition, APIs produced by the OCC should be described using one of the common API definition formats (such as Odata, OpenAPI, 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.
Status: In Progress
1.2.4 Develop Data Inventory Schedule
Summarize the Inventory Schedule: The OCC is working on completing an Enterprise Dataset Inventory.
1.2.5 Develop Data Inventory Schedule – Milestones
Title: Provide reports to programs to identify metadata holes.
Description: OCC uses its registry of IT Systems to identify datasets that may not be cataloged.
Milestone Date: Ongoing
Description of how this milestone expands the Inventory: This milestone allows OCC to identify and catalog new datasets that were not identified in the original 2013 Treasury data call.
Description of how this milestone enriches the Inventory: This milestone brings new and important datasets into the OCC's Data Inventory.
Description of how this milestones opens the Inventory: This milestones provides additional datasets that are publicly available through both occ.gov and data.gov.
1.2.6 Develop Customer Feedback Process
Describe the agency's process to engage with customers: OCC interacts with the public on its data in numerous ways including public meetings/forums, feedback links on websites, webinars, FOIA Online, mailboxes, and help desks.
1.2.7 Describe the agency's data publication process:
- Identify: The data set for public publication will be identified based on inputs from the data owner community and the data consumer community. Engaging with the data consumer (also referred to as the customer) using the process outlined in the "Customer Engagement Process" section helps to determine the data sets and the fields that compose the data set.
- Review: The data set must be reviewed by relevant officials from
- Business Data Owner and System Owner.
- Office of Privacy and General Counsel.
- Publish: Create metadata for the data set, provide data context description.
2. Make Existing High-Value Data and Content Available Through Web APIs
2.1 Engage with customers to identify at least two existing major customer-facing services that contain high-value data or content as first-move candidates to make compliant with new open data, content, and web API policy (OCC)
Overall status: Complete
2.1.1 Paragraph on customer engagement approach
The OCC discussed possible customer-facing high-value data sources with customers to identify two first-move candidate datasets.
2.1.2 Prioritized list of first-move candidate datasets
System Name: Enforcement Actions Search
System Description: Database of OCC enforcement actions
System Scope: OCC enforcement actions
Main Customer: Public and internal users
System Name: Community Reinvestment Act (CRA) Evaluation Search
System Description: Database of OCC CRA evaluations
System Scope: OCC CRA evaluations
Main Customer: Public and internal users
2.2 Make high-value data and content in at least two existing, major customer—facing systems available through web APIs, apply metadata tagging, and publish a plan to transition additional high-value systems (OCC)
Overall status: In Progress
2.2.1 Publish plan on future activity
Describe policy: Treasury will work with the OCC to identify additional candidates for APIs or datasets.
2.2.2 Make 2+ systems (datasets) available via web APIs with metadata tags
Name of system: TBD
Description of system: TBD
2.3 Expand Data.gov to include a web API catalog that centrally aggregates web APIs posted on agencies' /developer pages (GSA)
Completed May 23, 2013: https://www.data.gov/developers/apis