Skip to content
  • EA Voices
  • About
  • Contributors
  • Glossary

EA Voices

Aggregated enterprise architecture wisdom

  • EA Voices
  • About
  • Contributors
  • Glossary

Metadata as a Process

September 4, 2021 by Richard Veryard

Link: http://feedproxy.google.com/~r/Soapbox/~3/o8GGJ7mka18/metadata-as-process.html

From Architecture, Data and Intelligence

Data sharing and collaboration between different specialist areas requires agreement and transparency about the structure and meaning of the data. This is one of the functions of metadata.

I’ve been reading a paper (by Professor Paul Edwards and others) about the challenges this poses in interdisciplinary scientific research. They identify four characteristic features of scientific metadata, noting that these features can be found within a single specialist discipline as well as cross-discipline.

  • Fragmentation – many people contributing, no overall control
  • Divergent – multiple conflicting versions (often in Excel spreadsheets)
  • Iterative – rarely right first time, lots of effort to repair misunderstandings and mistakes
  • Localized – each participant is primarily focused on their own requirements rather than the global picture

They make two important distinctions, which will be relevant to enterprise data management as well.

Firstly between product and process. Instead of trying to create a static, definitive set of data definitions and properties, which will completely eliminate the need for any human interaction between the data creator and data consumer, assume that an ongoing channel of communication will be required to resolve emerging issues dynamically. (Some of the more advanced data management tools can support this.)

Secondly between precision and lubrication. Tight coupling between two systems requires exact metadata, but interoperability might also be achievable with inexact metadata plus something else to reduce any friction. (Metadata as the new oil, perhaps?)

Finally, they observe that metadata typically falls into the category of almost standards.

Everyone agrees they are a good idea, most have some such standards, yet few deploy them completely or effectively.

Does that sound familiar? 


J Bates, The politics of data friction (Journal of Documentation, 2017)

Paul Edwards, A Vast Machine (MIT Press 2010). I haven’t read this book yet, but I found a review by Danny Yee (2011)

Paul Edwards, Matthew Mayernik, Archer Batcheller, Geoffrey Bowker and Christine Borgman, Science Friction: Data, Metadata and Collaboration (Social Studies of Science 41/5, October 2011), pp. 667-690. 

Martin Thomas Horsch, Silvia Chiacchiera, Welchy Leite Cavalcanti and Björn Schembera, Research Data Infrastructures and Engineering Metadata. In Data Technology in Materials Modelling (Springer 2021) pp 13-30

Jillian Wallis, Data Producers Courting Data Reusers: Two Cases from Modeling Communities (International Journal of Digital Curation, 2014, 9/1, 2014) pp 98–109

0
0
Categories #eavoices, interoperability, metadata, semantics, standardization Tags #eavoices, coupling
Right, Left, and the Singularity
Yes, 2-speed IT is real, but not like you think

Open Data

Get the EA Voices XML feed or use the EA Voices API.

Popular Themes

#eavoices Agile Applications & Technology Archimate Architecture Articles Artificial Intelligence big data business Business Architecture business transformation Cloud Computing complexity Complexity / Structure data Decision making digital transformation EA EA, SOA and other technologies effectiveness Elevating Architecture Elevating EA entarch enterprise Enterprise Architecture Enterprise Architecture (EA) Enterprise Transformation Futures Governance Innovation IT IT Governance knowledge Leadership machine learning Security Sense Making SOA Society Standards Strategy Strategy Planning The Open Group togaf Uncategorized

Tags

#eavoices adm analysis Architect Architecture automation behavior blog Blogs business business it alignment career change Cloud community Culture Customer EA emergence enterprise Enterprise Architecture Enterprise Architecture Management Financial Services glue google hardware marketing Microsoft Model Open Group Conference organisation PaaS paradigm platform podcast Power reference architecture research Service Software story tool trust Value vision

Categories

Recent Posts

  • Building the Foundation — The Open Footprint® Standard, Edition 1.0, Part 1: Data Model General Requirements
  • Designing an Enterprise-ready Framework for Retail Loss Monitoring
  • Joule In SAP For Me: Conversation Support For Enterprise Architecture
  • Business Models Should Drive Every Context View and Decision
  • Democratize Enterprise Architecture Reporting Through AI
  • Serendipity for Serendipity
  • Key Considerations When Allowing a Vendor to Train Its AI Models on Customer Data
  • AI Enterprise Architecture Assistant: now included in SAP LeanIX
  • A Small Enterprise Architecture Function Health Check Before the Holidays
  • Ardoq est désormais disponible en français!
  • What Corporate Leaders Misunderstand About Cybersecurity Frameworks
  • Creating Enterprise And Architecture Principles
  • The Adaptive Extension Framework: Modernizing Core ERP Foundations
  • The AI Decision Matrix
  • The Alignment Gap: Why It Exists, and How Enterprise Architecture Closes It
  • Design the Future of Your Enterprise – On Your Terms
  • Enterprise Architect, Is Your Jargon Scaring People Away?
  • Designing Decision Rights for AI
  • Designing Decision Rights for AI
  • Why Senior Engineers Are Looking Hard at Architecture Right Now
EA Fellows