Featured Articles
Metadata Repositories vs. Metadata Registries
- By Dan McCreary
- Published 06/1/2009
- Business , Implementation & Strategy , Introductory
-
Rating:




For several years people have been using the terms metadata Registry and Repository inconstantly, imprecisely and almost interchangeably and I would like to weigh in as to how these terms could be used more precisely to allow organizations to effectively to manage metadata processes.
First lets take the definition of a Repository. Webster defines a repository as …a place, room, or container where something is deposited or stored.. Note that here is nothing in this definition about the quality of the things being stored or the process to check to see if new incoming items are duplicates of things already in the repository. If I have 100 users they could each define "Customer" as the see fit and put their own definition into the metadata repository as their own definition. No problems.
Managing Meta Data Risks
- By Lou Agosta
- Published 07/3/2008
- Introductory , Implementation & Strategy , Business , Compliance
- Unrated
Collecting, administering and leveraging meta data presents challenges and risks that must be surfaced and managed to avoid unpleasant surprises in the areas of data warehousing, data administration and the system development life cycle at large. Absent careful planning, the surprises can overwhelm the benefits of any meta data initiative. Without accurate, current, high-quality meta data, development teams in both data warehousing and transactional systems are on a slope of diminishing returns, working harder and harder to maintain many-to-many interfaces. Meta data affects system analysis, version and change control, system interoperability, intersystem visibility and transparency, and related factors at an enterprise level.
The number one risk to meta data projects is that the team will end up with documentation, not actionable insight into diverse IT systems interoperations. Of course, system documentation is generally a useful and, at times, an essential IT artifact. However, it is subject to a number of well-known shortcomings. When produced in the form of electronic documents, it is an idle wheel. Documentation does not automate or move any part of the development or maintenance process. Documents are often obsolete the very day they are published. A document does not know whether it is obsolete or not; and a labor-intensive, manual effort is required to keep documents current. Inaccurate (outdated) information is often worse than no information at all because it is misleading. In contrast, a data modeling tool from which database data definition language (DDL) can be produced or which can be imported into an ETL (extract, transform and load) or query-and-reporting tool is a mechanism that enables meta data-driven design or maintenance. Because the meta data interchange between tools is incomplete, some manual labor will be required to manage the risk of a meta data idle wheel. Teamwork and discipline remain essential to managing this situation.
Who Needs Metadata?
- By Ronald Forino
- Published 07/3/2008
- Introductory
- Unrated
A few weeks ago, I was asked to help oversee a client's business intelligence project that was running behind schedule. By the time I joined the project, the requirements and design had been completed, and the delivery team had finished most of its development work. The ETL process was working properly, and several reports had been developed. However, the project had been stalled for several weeks, having made little or no progress. The reason for the delay was that each of the reports that had been developed needed to be "certified."
Approximately 15 reports had been requested for the first release of the system. The requirements team had been told that most of these would replace reports that users were currently receiving. The team was provided with a set of the existing reports, which were mainly Microsoft Excel spreadsheets. The reports looked simple enough. Each column had a heading that identified the data it contained, and the team was told where the data was located. An estimate was made for how long the reports would take to develop. So what was the problem? In a word, metadata.
Model Driven Information Architecture
- By Brian J. Noggle, Michael Lang
- Published 07/3/2008
- Business , Implementation & Strategy
- Unrated
Over the past twenty years, enterprises have created many diverse systems to manage their information and data. Individual systems combine a myriad of hardware configurations, operating systems, databases, and applications. Often, individual enterprises have found themselves with several disparate information systems among their divisions and departments, especially after mergers or acquisitions have broadened the scope and depth of the enterprise.
As the world, not to mention the enterprise, networks more completely, the enterprise needs to integrate its diverse systems to operate and analyze its resources more effectively. Numerous external sources, from partner information resources to real-time data feeds, have become available. The enterprise needs to marshal and integrate these disparate systems. At the heart of the systems integration challenge lies an information integration challenge.
Model-driven integration differs from the programmed integration. Programmed integration relies upon hard-coding a finite, and inextensible, solution to a particular challenge. Model-driven integration focuses on abstracting the information content into a model that describes the enterprise’s information resources. This model captures the nature of the information the enterprise has within its systems and the way the enterprise uses data in its daily operations.
Meta Data Architecture Fundamentals
- By David Marco
- Published 07/3/2008
- Introductory , Implementation & Strategy
- Unrated
Over the next few years many companies will have the unenviable task of completely rebuilding their decision support systems. This is occurring because many of these systems were built with flawed architectures. The architecture used to build the meta data repository is every bit as critical to its long-term viability as the architecture for the decision support system is. By taking the time to build a sound architecture your repository effort will be able to grow and mature over time to support all of your company’s meta data needs.
Recent Articles
Metadata: Use It or Lose It
- By Conrad Jacoby
- Published 06/12/2007
- Introductory , Compliance
- Unrated
You've probably heard the word "metadata," but what exactly is this mysterious information? Equally important how should it be handled? Failure to adequately capture and preserve metadata associated with electronic discovery materials has been considered spoliation of evidence and grounds for significant discovery sanctions. Conversely, a failure to erase metadata from outgoing law firm correspondence can inadvertently communicate a wealth of inappropriate information to recipients. This article reveals how metadata is created, its purpose, and situations where metadata can assume significant importance.
What is metadata?
People normally define an electronic document, spreadsheet, e-mail message or other digital data as the content they can see, the information intentionally added by the document's author. However, almost all computer programs automatically add additional information to a document, usually storing it at the beginning or end of the electronic file where the program can easily find it. This information is generically known as "metadata."
When a file is attached to an e-mail message or copied from one location to another, much of its associated metadata is also transferred with the file. Some metadata, however, is automatically updated to reflect the new location or other actions involving the file. As a result, computer files that appear identical when viewed or printed may have different metadata.
Understandig Meta-Data
- By Conrad Jacoby
- Published 06/12/2007
- Introductory , Compliance
- Unrated
Any practicing attorney who uses a computer has probably heard the dreaded word "metadata" -- but what exactly is this mysterious information? Equally important, how should it be handled? Failure to adequately capture and preserve metadata associated with electronic discovery materials has been considered spoliation of evidence and grounds for significant discovery sanctions. Conversely, a failure to erase metadata from outgoing law firm correspondence can inadvertently communicate a wealth of inappropriate information to recipients. This article reviews how metadata is created, its purpose, and situations where metadata can assume significant importance."
What is metadata?
When most people think about an electronic document or an e-mail message, they define the file by the content that has been intentionally created by the document's author—e.g., our typing. However, to function more efficiently, virtually all computer programs automatically track additional information that relates to a document, usually storing it at the beginning or end of the file, where it can easily be found by the program. This information is generically known as "metadata."
When a file is attached to an e-mail message or copied from one location to another, much of its associated metadata is also transferred with the file. Some metadata, however, will automatically update to reflect the new location of the file. As a result, computer files that appear identical when printed out may have different metadata.
Many different forms of metadata exist, and each program tracks metadata that is appropriate for the particular data files it creates. Most word processing programs available today, for example, identify and record at least the following information:
· Name of the user logged into the computer
· The number of characters and words in the document
· How often and for how long the document has been edited
· Revisions that have been made to the document.
E-mail programs like Microsoft Outlook can associate e-mail messages with literally hundreds of pieces of metadata information, such as folders where messages are stored, whether messages were forwarded, and whether recipients opened a mail message that they were sent. Many of these metadata fields, however, remain empty unless certain actions take place; in most cases, the majority of possible metadata fields are actually empty.
In addition to metadata information that is written into a data file by word processing (or spreadsheet or e-mail) software, a computer's operating system also tracks information about the files stored where they can be accessed. This data includes:
- Document size;
- Date and time the document was last saved and last accessed;
- Location where the document has been stored; and
- Which users have rights to access the document.
The Power of Meta-Data
- By James Koopmann
- Published 02/17/2007
- Meta-data Management , Introductory
- Unrated
Data within your database is just that, data. It becomes information only when you can effectively extract and distribute in an understandable form. Using meta-data has come a long way; it allows for free-flowing information and is putting the ability to extract information into the hands of end-users.
When I first started my career in data processing, I began as a COBOL programmer. Back then, meta-data was strictly “data about data” and, in those days, we had to rely on s FDs, copy books, and a scarce set of documentation that comprised our meta-data. Such resources told us where data was located and what particular objects (tables) and columns meant.
Today, meta-data has grown into a complete subject area encompassing such terms as Knowledge Management, Corporate Data Dictionaries, and Enterprise Meta-Data Repositories. All of these classifications have the single goal to categorize the underlying information buried within databases so that end users can get to information faster. They do this by employing tools that allow end users to unlock the mysteries of what information is available and where it is located.
Imagine that you are cornered in the break room by the CEO or called into a sales meeting and asked to produce a report that describes demographic information for current customers. This task seems to be quick and easy, at least at face value. But, you quickly remember that you have distributed databases that control different product lines, and the way objects have been defined within those databases are quite different. To compound the issue, your CEO is starting to describe “customers” as anyone who has purchased products or services from you including potential customers that are not stored in a database yet but are in multiple spreadsheets maintained by your sales reps. No doubt, it is becoming obvious that these requirements will be changing and you begin to feel like you will be trying to hit a moving target.
Meta Tags- What Are They and Which Search Engines Use Them?
- By Richard Zwicky
- Published 08/14/2005
- Introductory , Meta-data Management , Web
- Unrated
Defining Meta Tags is much easier than explaining how they are used, and by which engines. The reason is very few engines clearly lay out what they do and do not look at, and how much emphasis they put on any one factor. So, we’ll start with the easy part
Meta Tags are lines of HTML code embedded into web pages that are used by search engines to store information about your site. These "tags" contain keywords, descriptions, copyright information, site titles and more. They are among the numerous things that the search engines look for, when trying to evaluate a web site.
Meta Data Repository Redux, Part 1 ? Meta Data Use Case Detail and Diversity
- By John Singer
- Published 03/17/2005
- Meta-data Management , Implementation & Strategy
- Unrated
They say what goes around comes around and this certainly applies to the meta data information repository. Over the last 25 years, each great evolution of information systems technology and best practices has bred the same set of issues and the invariable vendor response - the meta data repository (or some derivation). What is this problem that keeps recurring? Simply put, as newer technologies are used to develop systems, the increase in complexity breaks the system management status quo. The answer always involves storing information about the system components in a central place for analysis - i.e., the meta data repository. It hasn't always been called this, but nonetheless, the basic approach to solving IT management complexity is the same. We are now witnessing this event playing out once more, but I'm getting ahead of the story.
Schemalogic
- By MDX Admin
- Published 03/17/2003
- Tools & Vendors
- Unrated
Global enterprises spend over $60 billion per year on integration and maintenance of enterprise applications and content management systems. At the same time, the volume of data and content these systems must distribute and manage is increasing at an exponential rate. The result is a brittle network of corporate systems and fractured content silos that stifle the ability of the organization to assimilate new processes and access and distribute key information assets.
These systems must have agreement on the meaning of enterprise terminologies and their interrelationships to exchange and distribute information. In the past, there was no way to centrally manage and maintain these terms and relationships on an enterprise-wide basis. Businesses are now realizing the importance of deploying new solutions to manage enterprise terminologies and interrelationships in a systematic fashion and ensure robust integration of complex business and content management systems.
At SchemaLogic, we refer to these terms and interrelationships as the “business semantics” of the enterprise. SchemaLogic Enterprise Suite provides a framework that enables companies to model the structures and relationships of the business semantics that define corporate knowledge and content. We facilitate dynamic changes to the business semantics model through a Web-based governance and collaboration process that enables participation across organizational, corporate and industry boundaries and facilitates the development of business semantics in a dynamic, constantly changing environment.
SchemaLogic Enterprise Suite allows organizations to deploy new business models by accelerating information access and delivery. SchemaLogic customers reduce operational costs through better information management, increased data quality and more agile, intelligent business decisions.
Data Advantage Group
- By MDX Admin
- Published 03/17/2003
- Tools & Vendors
- Unrated
Data Advantage Group is a leading provider of best-in-class information asset management solutions designed specifically for the distributed real-time enterprise. Data Advantage Group’s MetaCenter Platform is the first practical solution to provide a clear and unambiguous definition and history of the data and standards organizations rely upon when running their businesses.
For over five years, Data Advantage Group has been consistently delivering value to its customers through the MetaCenter Platform. MetaCenter’s design is driven by the specific needs of Data Advantage Group’s customers for a real-time distributed meta data management solution. The goal from the onset was to create the first third generation solution to provide “End-to-End Meta data Management and Analytics” for the distributed enterprise.
MetaCenter
MetaCenter provides a single window into complex information systems, unlocking the contextual and relational information stored in business intelligence, database, data integration, data quality and data modeling applications. The MetaCenter Platform seamlessly integrates these components based on a suite of best practices for managing and creating knowledge bases. Business processes and corporate standards can be documented and seamlessly linked to the technical data underlying their execution. This empowers technical and business users to efficiently collaborate while analyzing and managing the knowledge represented in their corporate information systems. Organizations benefit through dramatic improvements in employee productivity, elimination of duplicative work, institutionalization of knowledge and standards, and a substantial reduction in operational risk.
Infolibrarian
- By MDX Admin
- Published 03/17/2003
- Tools & Vendors
- Unrated
InfoLibrarian is a leading metadata management repository and portal product for capturing, managing and disseminating metadata across the enterprise. InfoLibrarian helps to reduce integration and management costs by providing a "Card Catalog" style system to manage information assets, mappings and semantics relating to hardware, software, processes and data.