reglab/housing_qa huggingface dataset:
OR Rev Stat § 276A.323 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.323 - State agency coordination.

(1) As used in this section: (a) "Executive department" has the meaning given that term in ORS 174.112, except that "executive department" does not include: (A) The Secretary of State. (B) The State Treasurer. (C) The Attorney General. (D) The Oregon State Lottery. (E) Public universities listed in ORS 352.002. (b) "State agency" means an agency, as defined in ORS 183.310, in the executive department. (2) All state agencies shall: (a) Cooperate with the office of Enterprise Information Services in the implementation of a continuing statewide agency-by-agency risk-based information technology security assessment and remediation program. (b) Cooperate in the development of, and follow, the plans, rules, policies and standards adopted by the State Chief Information Officer with regard to the unification of agency information technology security functions in this state. (c) Conduct and document the completion of annual information technology security awareness training for all agency employees. (d) Report security metrics using methodologies developed by the office of Enterprise Information Services. (e) Participate in activities coordinated by the office of Enterprise Information Services in order to better understand and address security incidents and critical cybersecurity threats to the state. (3) The State Chief Information Officer shall determine and allocate the costs to state agencies associated with providing information technology services, third-party security evaluations, vulnerability assessments and remediation measures. State agencies shall pay the costs to the State Chief Information Officer in the same manner as the state agency pays other claims. The State Chief Information Officer shall deposit into the State Information Technology Operating Fund established under ORS 276A.209 all moneys that the State Chief Information Officer receives from state agencies for purposes of providing information technology services and administering and enforcing the duties, functions and powers under this section. [2017 c.513 §2; 2021 c.17 §3]
OR Rev Stat § 276A.332 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.332 - Authority of State Chief Information Officer to enter into agreements.

Notwithstanding any other provision of law, the State Chief Information Officer may: (1) Enter into any agreement, or any configuration of agreements, relating to state cybersecurity with any private entity or unit of government, or with any configuration of private entities and units of government. The subject of agreements entered into under this section may include, but need not be limited to, cybersecurity training and awareness, information technology security assessments and vulnerability testing, cyber disruption and incident response, risk-based remediation measures and application life cycle maintenance. (2) Include in any agreement entered into under this section any financing mechanisms, including but not limited to the imposition and collection of franchise fees or user fees and the development or use of other revenue sources. [2017 c.513 §5]
OR Rev Stat § 276A.335 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.335 - Moneys from federal government and other sources.

(1) The State Chief Information Officer may accept from the United States Government or any of its agencies any funds that are made available to the state for carrying out the purposes of ORS 276A.323 to 276A.335, regardless of whether the funds are made available by grant, loan or other financing arrangement. Under the authority granted by ORS chapter 190, the State Chief Information Officer may enter into agreements and other arrangements with the United States Government or any of its agencies as may be necessary, proper and convenient for carrying out the purposes of ORS 276A.323 to 276A.335. (2) The office of Enterprise Information Services may accept from any source any grant, donation, gift or other form of conveyance of land, money, real or personal property or other valuable thing made to the state or the office of Enterprise Information Services for carrying out the purposes of ORS 276A.323 to 276A.335. (3) Any cybersecurity initiative, consistent with the purposes of ORS 276A.323 to 276A.335, may be financed in whole or in part by contributions of any funds or property made by any private entity or unit of government that is a party to any agreement entered into under the authority of the office of Enterprise Information Services. (4) The State Chief Information Officer shall deposit into the State Information Technology Operating Fund established under ORS 276A.209 all moneys received under this section. [2017 c.513 §6; 2021 c.17 §5]
OR Rev Stat § 276A.350 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.350 - Definitions.

As used in ORS 276A.350 to 276A.371: (1)(a) "Data" means final versions of statistical or factual information, including statistical or factual data about image files, that: (A) Is in alphanumeric form reflected in a list, table, graph, chart or other nonnarrative form that can be digitally transmitted or processed; (B) Is controlled by and regularly created or maintained by, or on behalf of, a state agency; and (C) Records a measurement, transaction or determination related to the mission of the agency. (b) "Data" does not include image files, including but not limited to designs, drawings, photos and scanned copies of original documents. (2) "Dataset" means a named collection of related records, maintained on a storage device, that contains data organized, formatted or structured in a specific or prescribed way. (3) "Mosaic effect" means a situation in which information in an individual dataset, in isolation, may not pose a risk of identifying an individual, but when combined with other available information could pose such a risk. (4)(a) "Publishable data" means all data and datasets collected by a state agency. (b) "Publishable data" does not include: (A) Data to which a state agency may deny access pursuant to any provision of a federal, state or local law, rule or regulation, or another applicable policy or restriction. (B) Data that contain a significant amount of information to which a state agency may deny access pursuant to any provision of a federal, state or local law, rule or regulation. (C) Data that reflect the internal deliberative process of a state agency, including but not limited to negotiating positions, future procurements or pending or reasonably anticipated legal or administrative proceedings. (D) Data stored on a personal computing device owned by a state agency, or data stored on a portion of a network that has been exclusively assigned to a single agency employee or to a single computing device owned or controlled by a state agency. (E) Materials subject to copyright, patent, trademark, confidentiality agreements or trade secret protection. (F) Materials that have commercial value or the disclosure of which could reduce a state agency’s competitive advantage. (G) Proprietary applications, computer code, software, operating systems and similar materials. (H) Employment records, internal employee directories or lists, facilities data, information technology and other data related to internal state agency administration. (I) Any other data the publication of which is prohibited by law. (5) "State agency" means the executive department, as defined in ORS 174.112, except that "state agency" does not include the Secretary of State or the State Treasurer. [2017 c.720 §1]
OR Rev Stat § 276A.353 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.353 - Chief Data Officer; duties; rules.

(1) The State Chief Information Officer shall appoint a Chief Data Officer. (2) The Chief Data Officer shall: (a) Maintain a central web portal for the publication of publishable data under ORS 276A.362. (b) Establish the open data standard as provided in ORS 276A.356. (c) Prepare and publish the technical standards manual as provided in ORS 276A.359. (d) Create an enterprise data inventory that accounts for all datasets used within agency information systems and that indicates whether each dataset may be made publicly available and if the dataset is currently available to the public. The enterprise data inventory is a public record. (e) Provide information protection and privacy guidance for state agencies. (f) Establish an enterprise data and information strategy. (g) Identify ways to use and share existing data for business intelligence and predictive analytic opportunities. (h) Identify strategies to combine internal and external data sources. (i) Establish statewide data governance and policy area data governance and provide guidance for agencies about data governance efforts. (j) Oversee the delivery of education and standards to state agencies regarding data quality, master data management and data life cycle management. (k) Form an advisory group to assist the Chief Data Officer in carrying out the duties described in this section and in establishing an enterprise memorandum of understanding for interagency data sharing. (L) Submit a biennial report to a committee or interim committee of the Legislative Assembly related to information management and technology on: (A) The status of agency posting of publishable data; and (B) The status of data sharing within and between agencies, enabling cross-agency analysis to provide information for public purposes, including but not limited to program design and budgeting decisions. (3) The Chief Data Officer may establish and maintain an online forum to solicit feedback from the public and to encourage discussion on the open data standard and publishable data available on the web portal. (4) The State Chief Information Officer may adopt rules necessary to implement ORS 276A.350 to 276A.371. [2017 c.720 §2]
OR Rev Stat § 276A.356 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.356 - Open data standard.

(1) The Chief Data Officer appointed under ORS 276A.353 shall establish an open data standard for state agencies publishing publishable data on the web portal maintained under ORS 276A.353. A local or tribal government may adopt the standard. The standard must include: (a) A format that permits public notification of updates whenever possible. (b) Requirements to update publishable data as often as is necessary to preserve the integrity and usefulness of publishable data. (c) The availability of publishable data without registration or license requirements or restrictions on the use of publishable data. As used in this paragraph, "registration or license requirements or restrictions on the use of publishable data" does not include measures designed or required to ensure access to publishable data, to protect the web portal from abuse or attempts to damage or impair the use of the web portal, or to analyze the types of publishable data being accessed to improve service delivery. (d) The ability to electronically search publishable data using external information technology. (2) In establishing the open data standard, the Chief Data Officer shall consult with subject matter experts from state agencies, organizations specializing in technology and innovation, the academic community and other interested groups designated by the Chief Data Officer. Whenever feasible, the Chief Data Officer shall consult with these entities in the development of technical and open standards. (3) The Chief Data Officer may adopt rules to implement the open data standard. [2017 c.720 §3]
OR Rev Stat § 276A.359 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.359 - Technical standards manual.

(1) The Chief Data Officer appointed under ORS 276A.353 shall prepare and publish a technical standards manual for publishing data through the web portal maintained under ORS 276A.353. The manual must: (a) Enable state agencies to make publishable data available to the greatest number of users and for the greatest number of applications and emphasize that state agencies must, whenever practicable, use open data standards for web publishing in a machine-readable format. (b) Identify the policy for each technical standard and specify which types of data the standard applies to, and may recommend or require that publishable data be published in more than one technical standard. (c) Include a plan to adopt or utilize a web application programming interface that permits application programs to request and receive publishable data directly from the web portal. (2) The Chief Data Officer shall update the manual as necessary. [2017 c.720 §4]
OR Rev Stat § 276A.362 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.362 - Release of publishable data on web portal; exemptions; rules.

(1) A state agency that releases publishable data shall release the data on the web portal maintained under ORS 276A.353 in accordance with the open data standard and technical standards manual established by the Chief Data Officer under ORS 276A.356 and 276A.359. If a state agency cannot make all publishable data available on the web portal, the state agency shall report to the Chief Data Officer all publishable data that the agency is unable to make available and state the reasons why the agency is unable to make the data available and the date by which the agency expects the publishable data to be made available on the portal. (2) The State Chief Information Officer shall adopt rules allowing a state agency to request an exemption from the requirements of subsection (1) of this section when: (a) The release of publishable data would subject the agency’s information systems to a substantial risk of cyberattack; or (b) The state agency is purchasing software or vendor services and industry practices do not support downstream processing and dissemination activities. [2017 c.720 §5]
OR Rev Stat § 276A.365 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.365 - Information management by state agencies.

(1) A state agency shall manage information as a strategic asset throughout the information’s life cycle. To improve the management of information resources and reinforce the state’s presumption of openness, an agency shall: (a) Collect or create information in a way that supports downstream processing and dissemination activities, including: (A) Using machine-readable and open formats; (B) Using data standards approved by the Chief Data Officer in the collection and creation of information in order to promote data interoperability and openness; (C) Ensuring information stewardship through the use of open licenses; and (D) Using common core and extensible metadata. (b) Build information systems to support interoperability and information accessibility. (c) Strengthen data management and release practices to ensure agency data assets are managed and maintained throughout the assets’ life cycle by: (A) Adopting effective data asset portfolio management approaches. (B) Creating and maintaining an inventory of agency information resources to be included in the enterprise data inventory. (C) Creating and maintaining a public data listing, including datasets that can be made publicly available but that have not yet been released. (D) Establishing a process to engage with customers and the public to help facilitate and prioritize data release. (E) Clarifying roles and responsibilities for promoting efficient and effective data release practices. (d) Strengthen measures to ensure that privacy and confidentiality are fully protected and that data are properly secured. (e) Account for the mosaic effect of data aggregation. (f) Incorporate new interoperability and openness requirements into core agency processes. (2) A state agency shall integrate the following minimum requirements into the project planning documentation and technical design for all new information systems and systems preparing for modernization, as appropriate: (a) System designs must be scalable and flexible and must facilitate the extraction of data in multiple formats, using standards and specifications in the system design that promote industry best practices for data sharing, and separation of data from the application layer to maximize data reuse opportunities; (b) All data outputs of the associated system must meet the requirements described in paragraph (a) of this subsection; and (c) Data schemata and dictionaries must be documented and shared with internal partners and the State Chief Information Officer. (3)(a) A state agency’s use of proprietary software may not diminish the ability of the public to inspect and copy a public record. (b) A state agency may not enter into a contract for the creation of a public records database that impairs the ability of the public to inspect or copy the public records of the state agency, including but not limited to the documentation described in subsection (2)(c) of this section. [2017 c.720 §6]
OR Rev Stat § 276A.368 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.368 - Purpose of data; limitation of liability; publishable data in public domain.

(1) Publishable data available on the web portal maintained under ORS 276A.353 is provided for informational purposes only. The state does not warrant the completeness, accuracy, content or fitness for any particular purpose or use of publishable data made available on the web portal. No warranties may be implied or inferred with respect to the publishable data made available on the web portal. (2) The state is not liable for any deficiencies in the completeness, accuracy, content or fitness for any particular purpose or use of publishable data made available on the web portal or by any third-party application utilizing publishable data. (3) All publishable data is in the public domain for purposes of applicable copyright laws. (4) The Chief Data Officer shall post the text of subsections (1) to (3) of this section on the web portal home page. [2017 c.720 §7]
OR Rev Stat § 276A.371 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.371 - Obligations of state agency under public records law.

ORS 276A.350 to 276A.371 do not supersede any obligation imposed on a state agency by ORS 192.311 to 192.478. [2017 c.720 §8]
OR Rev Stat § 276A.374 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.374 - Application to Secretary of State and State Treasurer; rules.

The Secretary of State and the State Treasurer shall by rule adopt for each respective office requirements related to data that are the same as, or are similar to, the requirements established by ORS 276A.350 to 276A.371 and by rules adopted by the State Chief Information Officer or the Chief Data Officer under ORS 276A.350 to 276A.371. [2017 c.720 §9]
OR Rev Stat § 276A.400 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.400 - Policy.

The Legislative Assembly declares it to be the policy of the State of Oregon: (1) To use information technology in education, health care, economic development and government services to improve economic opportunities and quality of life for all Oregonians regardless of location or income. (2) To stimulate demand to encourage and enable long-term infrastructure innovation and improvement. (3) That telecommunications planning process shall: (a) Organize users in new ways to aggregate demand, reduce costs and create support networks; (b) Encourage collaboration between communities of interest by geographic area and economic sector; and (c) Encourage competition among technology and service providers. [Formerly 283.500]
OR Rev Stat § 276A.403 (2021)
2021 Oregon Revised Statutes|Volume : 07 - Public Facilities and Finance|Chapter 276A - Information Technology|Section 276A.403 - Coordination of telecommunications systems.

 (1) The State Chief Information Officer shall coordinate, in a manner that is consistent with plans, standards, policies, goals, directives and rules that the State Chief Information Officer sets, specifies or adopts, the consolidation and operation of all telecommunications systems, including emergency telecommunications systems, that the state and state agencies use. Notwithstanding any other provision of law, an agent or agency of the state may not construct, purchase or otherwise gain access to a telecommunications system without the prior approval of the State Chief Information Officer. (2) The provisions of this section do not require emergency service providers, as defined by the State Chief Information Officer, to consolidate telecommunications systems that emergency service providers use into nonemergency networks. [Formerly 283.505]