Enterprise Data Inventory: To be featured as a best practice growth and license improvements are needed. The EDI includes 654 data assets, but a the Google search for .xls, .csv, .xml, and .json produces 224,000 dataset results. While 99.4% of datasets include a labeled license, many are not Public Domain. Licensing information should be reviewed and updated, see: https://project-open-data.cio.gov/open-licenses/ Any dataset that is not available in the Public Domain should include an explanation as to why in the rights
field.
Public Data Listing: To be featured as a best practice growth and metadata improvements are needed. There has been only 2% growth and 4 APIs added to the Public Data Listing since last quarter. Add featured datasets: https://www.whitehouse.gov/sites/default/files/microsites/ostp/us_open_data_action_plan.pdf 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. USDA provides several transparent methods for 2-way customer feedback and communication, as described at http://www.usda.gov/wps/portal/usda/usdahome?navid=DIGITALSTRATEGY, including a GitHub site. 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=49015 When hosting events be sure to add them to Data.gov/events. While the related Topic www.data.gov/food received 18,213 views last quarter, it is unclear how many views usda.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 USDA'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.
Enterprise Data Inventory: To be featured as a best practice growth and license improvements are needed. The EDI includes 654 data assets, but a the Google search for .xls, .csv, .xml, and .json produces 224,000 dataset results. While 99.4% of datasets include a labeled license, many are not Public Domain. Licensing information should be reviewed and updated, see: https://project-open-data.cio.gov/open-licenses/ Any dataset that is not available in the Public Domain should include an explanation as to why in the `rights` field.
Public Data Listing: To be featured as a best practice growth and metadata improvements are needed. There has been only 2% growth and 4 APIs added to the Public Data Listing since last quarter. Add featured datasets: https://www.whitehouse.gov/sites/default/files/microsites/ostp/us_open_data_action_plan.pdf 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. USDA provides several transparent methods for 2-way customer feedback and communication, as described at http://www.usda.gov/wps/portal/usda/usdahome?navid=DIGITALSTRATEGY, including a GitHub site. 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=49015 When hosting events be sure to add them to Data.gov/events. While the related Topic www.data.gov/food received 18,213 views last quarter, it is unclear how many views usda.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 USDA'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.
Lasted edited on August 31, 2015, 8:41 am EDT by Rebecca Williams