(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]