1
Data Governance at the Diputación of A Coruña with
OpenMetadata – Two Years of Transformation.
MAY - 2025
2
1.- Introduction: Brief presentation
I“m NicolÔs Gutiérrez García, project
manager for Data Governance at Ednon,
company specialized in advanced
technology solutions that supports public
and private organizations in their digital
transformation processes.
From Ednon, we contribute with expertise in
data governance, data management, artificial
intelligence, and cybersecurity, helping our
clients make more informed and secure
decisions.
In this OpenMetadata Meetup organized by Collate, I will share our two-year
experience implementing data governance initiatives at the Diputación A Coruña, a
project in which we have used OpenMetadata as a key platform to structure, catalog,
and govern information assets effectively and sustainably.
3
2.- The Diputación de A Coruña and its
Commitment to Citizens
Diputación of A Coruña is a SupraCouncil public administration that provides
technical, economic, and administrative support to the municipalities in the
province, especially the smaller ones.
Its functions include:
ā–ŗ Management of local infrastructures
ā–ŗ Social services
ā–ŗ Economic development
ā–ŗ Culture and sports
ā–ŗ Innovation and e-goverment
4
2.1- SUBTEL and the Provincial Electronic Registry
To enhance citizen interaction and improve administrative efficiency, the
Diputación has implemented tools such as:
SUBTEL: An electronic processing platform that
allows municipalities/councils and citizens to manage
grants, plans, and aid digitally.
Registry: An electronic platfomr of the General
Registry that enables the submission of documents,
requests, and communications regarding provincial
procedures, available 24/7.
5
2.2- Initial Data situation
Before implementing data governance, we faced several common challenges in
public administrations:
ā–ŗ Información silos
ā–ŗ Lack of traceability
ā–ŗ No Glossaries
ā–ŗ Lack of trust in data
ā–ŗ Technical dependency
6
2.3- Objectives y Decision
The Diputación set out to professionalize its data management, with a clear
focus on:
ā–ŗ Building a common metadata infrastructure
ā–ŗ Improving quality, traceability, and understanding of public information
ā–ŗ Creating a shared language for data across functional areas
ā–ŗ Laying the foundations for sustainable data governance aligned with regulatory
compliance and public efficiency improvement
ĀæWhy OpenMetadata?
ā–ŗ Flexible
ā–ŗ Adaptable to the changing reality of the organization
ā–ŗ Extensible
ā–ŗ In order to connect with current and future data sources
ā–ŗ Easy Integration
ā–ŗ Oracle, Postgres, QlikSense, Superset
ā–ŗ Supports technical and bussines metadata
ā–ŗ Python Framework /APIs
7
3.- Key Milestones: 2023
1.- Deployment on Client“s infrastructure
2.- Integration with priority sources: Oracle and
Postgres databases.
3.- Initial definition and organization of
the business glossary
4.- Definition and approval of
technical data quality, and
data modeling, policies and
procedures
8
3.- Key Milestones: 2024
ā–ŗ Implementation of curation flows ā–ŗ Integration with BI tools: QlikSense.
ā–ŗ Data source documentation.
Workflows
defined to
generate and
approve tasks by
the
datastewards
team about
documentation,
classification,
quality, etc.
Full report
cataloging with
lineage and
democratization
mechanisms via
the Data Office
Automation with Python and
advanced use of the API for
metadata dumps (e.g.,
documentation of data
sources: Oracle and Postgres
tables and fields)
9
3.- Key Milestones: 2025
ā–ŗ Translation of
OpenMetadata to
Galician
ā–ŗ AI Integration for discovery and
documentation processes
ā–ŗ KPIs Governance.
IA will be used for:
ā–ŗ Pre-documentation of data models
ā–ŗ Glossary analysis and proposal of
missing/new terms
ā–ŗ Quality rule automation
ā–ŗ Lineage construction for non
supported models
Tasks:
ā–ŗ Define KPIs as business terms
ā–ŗ Catalog and Gobern KPIs data sources
ā–ŗ Build complete lineage
ā–ŗ KPI democratization through O.M.
1
0
4.- Use Case: I (Show me the Numbers)
ā–ŗ Cataloged assets: 1412
ā–ŗ Descriptions: ā–ŗ Owners:
ā–ŗ Glossaries: 18 ā–ŗ Bussines Terms: 457 ā–ŗ Approved: 238 ā–ŗ Sensitive: 48 ā–ŗ Public: 68
1
1
4.- Use Case: II
1. Database scanning and
cataloging.
2. Approval flow defined by the
Data Office, where data stewards
review and validate the data
asset documentation.
3. Once approved, Python framework
is used with OpenMetadata APIs to
collect this documentation from
OpenMetadata.
ā–ŗ Automatic documentation of cataloged data sources:
4. This documentation collected is used to update de
database models.
This approach ensures that documentation is always aligned,
centralized, and accessible from both the data catalog and the
storage platforms themselves, thus facilitating its use,
maintenance, and auditing.
1
2
4.- Use Case: III
This process ensures that BI Data Products meet the quality standards defined by the Data
Office.
ā–ŗ The seal covers key aspects such as:
ā–ŗ Quality and consistency of the data.
ā–ŗ Standardization and traceability of sources.
ā–ŗ Transparency.
ā–ŗ Security and interoperability.
ā–ŗ Relevance of content and documentation.
ā–ŗ OFDA Seal of Approval for BI:
Once the data product is
approved, it is assigned a
classification tag in the Open
Metadata business glossary,
enabling its democratization
and use at the organizational
level with guarantees of
reliability and compliance.
1
3
4.- Casos de Uso. 4 COMPLETAR
Completar
ā–ŗ La revisión abarca aspectos clave como:
ā–ŗ Calidad y consistencia de los datos mostrados.
ā–ŗ Estandarización y trazabilidad de las fuentes.
ā–ŗ Transparencia en el modelo de datos utilizado.
ā–ŗ Revisión de la seguridad e interoperabilidad.
ā–ŗ Relevancia del contenido y nivel de documentación.
ā–ŗ Autodocumentacion Postgres BBDD multitenant:
Phatplus
Freepik
Three musketeers
Flat Icons
Referenciar fuentes:
1
4 Data, & Analytics
CONTACTO
RĆŗa Monte dos Postes, 6.
15703 Santiago de
Compostela
+34 981 55 27 00
@ednon
EDNON
www.ednon.com
comercial@ednon.co
m

OpenMetadata Spotlight - OpenMetadata @ EDNON

  • 1.
    1 Data Governance atthe Diputación of A CoruƱa with OpenMetadata – Two Years of Transformation. MAY - 2025
  • 2.
    2 1.- Introduction: Briefpresentation IĀ“m NicolĆ”s GutiĆ©rrez GarcĆ­a, project manager for Data Governance at Ednon, company specialized in advanced technology solutions that supports public and private organizations in their digital transformation processes. From Ednon, we contribute with expertise in data governance, data management, artificial intelligence, and cybersecurity, helping our clients make more informed and secure decisions. In this OpenMetadata Meetup organized by Collate, I will share our two-year experience implementing data governance initiatives at the Diputación A CoruƱa, a project in which we have used OpenMetadata as a key platform to structure, catalog, and govern information assets effectively and sustainably.
  • 3.
    3 2.- The Diputaciónde A CoruƱa and its Commitment to Citizens Diputación of A CoruƱa is a SupraCouncil public administration that provides technical, economic, and administrative support to the municipalities in the province, especially the smaller ones. Its functions include: ā–ŗ Management of local infrastructures ā–ŗ Social services ā–ŗ Economic development ā–ŗ Culture and sports ā–ŗ Innovation and e-goverment
  • 4.
    4 2.1- SUBTEL andthe Provincial Electronic Registry To enhance citizen interaction and improve administrative efficiency, the Diputación has implemented tools such as: SUBTEL: An electronic processing platform that allows municipalities/councils and citizens to manage grants, plans, and aid digitally. Registry: An electronic platfomr of the General Registry that enables the submission of documents, requests, and communications regarding provincial procedures, available 24/7.
  • 5.
    5 2.2- Initial Datasituation Before implementing data governance, we faced several common challenges in public administrations: ā–ŗ Información silos ā–ŗ Lack of traceability ā–ŗ No Glossaries ā–ŗ Lack of trust in data ā–ŗ Technical dependency
  • 6.
    6 2.3- Objectives yDecision The Diputación set out to professionalize its data management, with a clear focus on: ā–ŗ Building a common metadata infrastructure ā–ŗ Improving quality, traceability, and understanding of public information ā–ŗ Creating a shared language for data across functional areas ā–ŗ Laying the foundations for sustainable data governance aligned with regulatory compliance and public efficiency improvement ĀæWhy OpenMetadata? ā–ŗ Flexible ā–ŗ Adaptable to the changing reality of the organization ā–ŗ Extensible ā–ŗ In order to connect with current and future data sources ā–ŗ Easy Integration ā–ŗ Oracle, Postgres, QlikSense, Superset ā–ŗ Supports technical and bussines metadata ā–ŗ Python Framework /APIs
  • 7.
    7 3.- Key Milestones:2023 1.- Deployment on Client“s infrastructure 2.- Integration with priority sources: Oracle and Postgres databases. 3.- Initial definition and organization of the business glossary 4.- Definition and approval of technical data quality, and data modeling, policies and procedures
  • 8.
    8 3.- Key Milestones:2024 ā–ŗ Implementation of curation flows ā–ŗ Integration with BI tools: QlikSense. ā–ŗ Data source documentation. Workflows defined to generate and approve tasks by the datastewards team about documentation, classification, quality, etc. Full report cataloging with lineage and democratization mechanisms via the Data Office Automation with Python and advanced use of the API for metadata dumps (e.g., documentation of data sources: Oracle and Postgres tables and fields)
  • 9.
    9 3.- Key Milestones:2025 ā–ŗ Translation of OpenMetadata to Galician ā–ŗ AI Integration for discovery and documentation processes ā–ŗ KPIs Governance. IA will be used for: ā–ŗ Pre-documentation of data models ā–ŗ Glossary analysis and proposal of missing/new terms ā–ŗ Quality rule automation ā–ŗ Lineage construction for non supported models Tasks: ā–ŗ Define KPIs as business terms ā–ŗ Catalog and Gobern KPIs data sources ā–ŗ Build complete lineage ā–ŗ KPI democratization through O.M.
  • 10.
    1 0 4.- Use Case:I (Show me the Numbers) ā–ŗ Cataloged assets: 1412 ā–ŗ Descriptions: ā–ŗ Owners: ā–ŗ Glossaries: 18 ā–ŗ Bussines Terms: 457 ā–ŗ Approved: 238 ā–ŗ Sensitive: 48 ā–ŗ Public: 68
  • 11.
    1 1 4.- Use Case:II 1. Database scanning and cataloging. 2. Approval flow defined by the Data Office, where data stewards review and validate the data asset documentation. 3. Once approved, Python framework is used with OpenMetadata APIs to collect this documentation from OpenMetadata. ā–ŗ Automatic documentation of cataloged data sources: 4. This documentation collected is used to update de database models. This approach ensures that documentation is always aligned, centralized, and accessible from both the data catalog and the storage platforms themselves, thus facilitating its use, maintenance, and auditing.
  • 12.
    1 2 4.- Use Case:III This process ensures that BI Data Products meet the quality standards defined by the Data Office. ā–ŗ The seal covers key aspects such as: ā–ŗ Quality and consistency of the data. ā–ŗ Standardization and traceability of sources. ā–ŗ Transparency. ā–ŗ Security and interoperability. ā–ŗ Relevance of content and documentation. ā–ŗ OFDA Seal of Approval for BI: Once the data product is approved, it is assigned a classification tag in the Open Metadata business glossary, enabling its democratization and use at the organizational level with guarantees of reliability and compliance.
  • 13.
    1 3 4.- Casos deUso. 4 COMPLETAR Completar ā–ŗ La revisión abarca aspectos clave como: ā–ŗ Calidad y consistencia de los datos mostrados. ā–ŗ Estandarización y trazabilidad de las fuentes. ā–ŗ Transparencia en el modelo de datos utilizado. ā–ŗ Revisión de la seguridad e interoperabilidad. ā–ŗ Relevancia del contenido y nivel de documentación. ā–ŗ Autodocumentacion Postgres BBDD multitenant: Phatplus Freepik Three musketeers Flat Icons Referenciar fuentes:
  • 14.
    1 4 Data, &Analytics CONTACTO RĆŗa Monte dos Postes, 6. 15703 Santiago de Compostela +34 981 55 27 00 @ednon EDNON www.ednon.com [email protected] m