To access all our features please use the Goodpods app.
Open the app
MetaDAMA - Data Management in the Nordics
Winfried Etzel VP Activities DAMA Norway
All episodes
Best episodes
Top 10 MetaDAMA - Data Management in the Nordics Episodes
Best episodes ranked by Goodpods Users most listened
"The data lifecycles collides with the system lifecycles. It’s a classic."
Let’s talk about the paradoxes of Data: Data Lifecyle, Search and Data Catalog!
What a fantastic chat Ole and I had! Ole is writing his O’Reilly book Enterprise Data Catalog, has newsletter Symphony of Search. He brings in a new perspective from Library and Information Science and is a great advocate for transforming the way we think around data and search.
Ole has worked as a specialist, as a leader and as an architect, and has an academical background as PhD in Information Science from University of Copenhagen.
Here are my key takeaways:
- Data Lifecycle was first mentioned as the POSMAD lifecycle
- Plan - Plan for creation
- Obtain - Acquire data
- Store - store it in a system
- Share - expose it and make it accessible
- Maintain - curate data, keep it accurate
- Apply - Use the data
- Dispose - Archive or delete
- Store, share and apply is where the business value is derived
- The points where you get value from data are normally not the same, we use to manage data.
- The work e.g. national archives do, in cataloguing, and readying data for research is done at the very last stage of the lifecycle. But the value resides much earlier in the lifecycle.
- Data-driven innovation, data-drive culture... What these terms actually mean is that we need to get better at utilizing the value insight data.
- Intangible assets hold the highest value - data is the key to value creation.
- One of the potentials of a data catalog is to push the high-level DM activities to earlier stages of the lifecycle.
- Catalogs are pushing inventory activities from the dispose phase to the store and share phase of the lifecycle.
- There is a huge difference in the perspective of an IT system lifecycle and data lifecycle.
- Data always resides in a system, and that system has its own lifecycle. These lifecycles do not match.
- If you do not maintain data in your systems, any potential data migration becomes exponentially more difficult. What do we migrate, what do we keep, what do we delete?
- The solution can be a Data Catalog and/or metadata repository with retention policies for data.
- The distinction between searching in and searching for data has become really important due to the rise of data science.
- When you search for data, you are looking at data sources with potential value to search in.
- Metadata is key in searching for data - that means we have to manage the metadata lifecycle as well.
- A data Catalog is basically just a search engine.
- Data Catalogs rely more and more on the same technology components as search engines for the web, e.g. knowledge graphs.
- The key capability of data catalogs is a metadata overview over the data in your company.
- Data catalogs have an untouched potential to ensure data lifecycle management

#19 - Data Privacy (Eng)
MetaDAMA - Data Management in the Nordics
05/18/22 • 44 min

#18 - Data Governance (Eng)
MetaDAMA - Data Management in the Nordics
04/25/22 • 40 min
«If you do guidance correctly, people will follow it. People want to do the correct thing. Nobody wants to do things wrong.»
From fisherman on Island to Data MVP in Copenhagen! Asgeir has been through a fantastic journey and we had a great conversation around PowerBI Governance. Asgeir has his own blog about the topic.
Here are my key takeaways:
- Think of platforms at a translation: You are own a journey and platform is where you stand on, from where you push off, start your journey.
- A lot of organizations are only on maturity level 1 when it comes to Power BI, even though they think they range higher, or even if there are different levels of maturity in different parts of the organization.
- Buzzwords help shape opinions, and to have discussions. With good help, these opinions can be shaped into actions.
- If you have the possibility to do a green field approach to data mesh - consider it: It will not get easier than this.
- The parts of Data Governance, that can be solved with a focus on technology, and process are much more mature and easier to handle than the softer parts, that are concerned with people.
- It is easier to lock out intentional mistakes than unintentional.
- Governance is changing focus, from being compliance driven to providing a framework of how we can get more value from our data, it’s about making people productive.
- By making people more productive and efficient, you can pay off the cost of governance really fast.
- If you use data more proactively, you are moving the power from people to the machine. But there needs to be a balance, its not either or.
PoweBI
- In PowerBI implementations we should have talked Governance from the start.
- PowerBI enables people in your organization to use data on their own. There is always value ion that.
- To use self-service tools correctly, you need to either have people formally trained or/and have guidelines in place BEFORE they start doing things.
- Not everyone in your organization will become a PowerBI expert or is a data person. Don’t expect everyone to go there.
- Governance is about giving people a framework and a good chance to do things correctly from the beginning.
- Most low hanging fruit: Build a report inventory!
- Try to keep the usage of PowerBI to the M365 environment and meet people where they are.
- Know your requirements before you start using tools.
The 5 pillars cover all of what your governance strategy implementation should cover:
- The people pillar is about having the right roles in place and train people to perform in these roles.
- Because PowerBI is a self-service tool the administrator role is often allocated randomly.
- The processes and framework pillar is about what proper documents in place to make it work so users can use Power BI correctly and be compliant. This covers administrative documents as well as end user documents.
- The training and support pillar is about making sure everyone that uses Power BI has gotten the required training. This is also about deciding what kind of support mechanisms you need to have in place.
- The monitoring pillar is about setting up monitoring of Power BI. Usually, it involves extracting data from the Power BI activity log as well as the Power BI REST APIs for information about existing artifacts in your Power BI tenant.
- The settings and external tools pillar is about making sure Power BI settings are correctly sat as well as how to use other approved tools to support Power BI (extensions to Power BI).