{"database": "openregs", "table": "crs_reports", "rows": [["R48954", "Data.gov: Implementation and Perspectives on Its Functions", "2026-05-21T04:00:00Z", "2026-05-22T17:08:41Z", "Active", "Reports", "Meghan M. Stuessy, Clinton T. Brass", null, "Over many decades, Congress has legislated policies to provide federal data to different types of users for a variety of purposes or \u201cuse cases.\u201d From constituents seeking to learn more about the functions of their representative government to researchers seeking authoritative data for ongoing work, Data.gov is the latest effort in a series of initiatives addressing ongoing debates about how the public may access government data.\nThrough administrative initiatives beginning in 2009 and implementation of the Open, Public, Electronic, and Necessary Government Data Act (OPEN Government Data Act; P.L. 115-435, Title II) from 2019 to the present, Data.gov has operated primarily as a directory to certain kinds of government-held information. The General Services Administration administers Data.gov\u2019s day-to-day operations, while the Office of Management and Budget (OMB) effectively exercises control over the website\u2019s implementation and develops related guidance for agencies. Data.gov hosts the federal data catalog, which lists information about many agency data assets and provides means to access some of them. However, Data.gov does not typically serve as a repository for the underlying data assets themselves; rather, it is characterized in law as \u201ca single public interface online as a point of entry\u201d that directs users to data assets hosted elsewhere, such as on individual agency websites.\nThe OPEN Government Data Act defines data as \u201crecorded information\u201d and data asset as \u201ca collection of data elements or data sets that may be grouped together.\u201d However, OMB\u2019s definition from implementation guidance in Memorandum M-25-05 interpreted the act\u2019s definition of the term data asset more narrowly to mean data that are both structured (e.g., organized into columns and rows and a database of digital images) and logically grouped (e.g., with a shared function or purpose). These definitions and others contained in the statute may permit agencies a level of discretion in determining which data assets are included and which are excluded from Data.gov\u2019s federal data catalog. The OPEN Government Data Act differs markedly from previous administrative and legislative efforts to make federal data available to the public in that it requires agencies to use the statutory framework for data access built by the Freedom of Information Act (FOIA) to determine which data should be included and made available on Data.gov.\nIn many ways, Data.gov is situated at a nexus of different perspectives and competing priorities seeking to influence policy on how to make federal data available. Policymakers and stakeholders have variously emphasized different aspects of information policy, and Congress may continue to weigh in on what aspects the federal government should value. These considerations include how long data should be kept, what types of data should be stored (and in what formats), whether and how data should be made more available or secure, who should gain access to data and when, and what type and quality of data should be applied for particular purposes.\nThis report provides an overview of the operations of Data.gov, including how they continue to be influenced by past administrative decisions. It also discusses six perspectives toward information availability that continue to influence Data.gov\u2019s operations and poses questions raised by each viewpoint that policymakers might consider regarding the website\u2019s present and future development. The report then examines several related issues that Congress may wish to consider. These include the ability of Data.gov to serve varied audiences, transparency of data asset inclusion and reporting procedures, and the persistence of data access over time. Lastly, the report discusses debates regarding whether Data.gov, as home of the federal data catalog, should function as either a registry for locating data or a repository for hosting federal data.", "https://www.congress.gov/crs_external_products/R/PDF/R48954/R48954.1.pdf", "https://www.congress.gov/crs_external_products/R/HTML/R48954.html"]], "columns": ["id", "title", "publish_date", "update_date", "status", "content_type", "authors", "topics", "summary", "pdf_url", "html_url"], "primary_keys": ["id"], "primary_key_values": ["R48954"], "units": {}, "query_ms": 0.5087560275569558, "source": "Federal Register API & Regulations.gov API", "source_url": "https://www.federalregister.gov/developers/api/v1", "license": "Public Domain (U.S. Government data)", "license_url": "https://www.regulations.gov/faq"}