Metadata is "data [information] that provides information about other data".[1] Three distinct types of metadata exist: descriptive metadata, structural metadata, and administrative metadata.[2]

  • Descriptive metadata describes a resource for purposes such as discovery and identification. It can include elements such as title, abstract, author, and keywords.
  • Structural metadata is metadata about containers of data and indicates how compound objects are put together, for example, how pages are ordered to form chapters. It describes the types, versions, relationships and other characteristics of digital materials. [3]
  • Administrative metadata provides information to help manage a resource, such as when and how it was created, file type and other technical information, and who can access it.[4]


Metadata was traditionally used in the card catalogs of libraries until the 1980s, when libraries converted their catalog data to digital databases. In the 2000s, as digital formats were becoming the prevalent way of storing data and information, metadata was also used to describe digital data using metadata standards.

The first description of "meta data" for computer systems is purportedly noted by MIT's Center for International Studies experts David Griffel and Stuart McIntosh in 1967: "In summary then, we have statements in an object language about subject descriptions of data and token codes for the data. We also have statements in a meta language describing the data relationships and transformations, and ought/is relations between norm and data." [5]

There are different metadata standards for each different discipline (e.g., museum collections, digital audio files, websites, etc.). Describing the contents and context of data or data files increases its usefulness. For example, a web page may include metadata specifying what software language the page is written in (e.g., HTML), what tools were used to create it, what subjects the page is about, and where to find more information about the subject. This metadata can automatically improve the reader's experience and make it easier for users to find the web page online.[6] A CD may include metadata providing information about the musicians, singers and songwriters whose work appears on the disc.

A principal purpose of metadata is to help users find relevant information and discover resources. Metadata also helps to organize electronic resources, provide digital identification, and support the archiving and preservation of resources. Metadata assists users in resource discovery by "allowing resources to be found by relevant criteria, identifying resources, bringing similar resources together, distinguishing dissimilar resources, and giving location information."[7] Metadata of telecommunication activities including Internet traffic is very widely collected by various national governmental organizations. This data is used for the purposes of traffic analysis and can be used for mass surveillance.[8]

In many countries, the metadata relating to emails, telephone calls, web pages, video traffic, IP connections and cell phone locations are routinely stored by government organizations.[9]


  1. Metadata means "data about data". Although the "meta" prefix (from the Greek preposition and prefix μετά-) means "after" or "beyond", it is used to mean "about" in epistemology. Metadata is defined as the data providing information about one or more aspects of the data; it is used to summarize basic information about data which can make tracking and working with specific data easier.[10] Some examples include:
  • Means of creation of the data
  • Purpose of the data
  • Time and date of creation
  • Creator or author of the data
  • Location on a computer network where the data was created
  • Standards used
  • File size

For example, a digital image may include metadata that describes how large the picture is, the color depth, the image resolution, when the image was created, the shutter speed, and other data.[11] A text document's metadata may contain information about how long the document is, who the author is, when the document was written, and a short summary of the document. Metadata within web pages can also contain descriptions of page content, as well as key words linked to the content.[12] These links are often called "Metatags", which were used as the primary factor in determining order for a web search until the late 1990s.[12] The reliance of metatags in web searches was decreased in the late 1990s because of "keyword stuffing".[12] Metatags were being largely misused to trick search engines into thinking some websites had more relevance in the search than they really did.[12]

Metadata can be stored and managed in a database, often called a metadata registry or metadata repository.[13] However, without context and a point of reference, it might be impossible to identify metadata just by looking at it.[14] For example: by itself, a database containing several numbers, all 13 digits long could be the results of calculations or a list of numbers to plug into an equation - without any other context, the numbers themselves can be perceived as the data. But if given the context that this database is a log of a book collection, those 13-digit numbers may now be identified as ISBNs - information that refers to the book, but is not itself the information within the book. The term "metadata" was coined in 1968 by Philip Bagley, in his book "Extension of Programming Language Concepts" where it is clear that he uses the term in the ISO 11179 "traditional" sense, which is "structural metadata" i.e. "data about the containers of data"; rather than the alternative sense "content about individual instances of data content" or metacontent, the type of data usually found in library catalogues.[15][16] Since then the fields of information management, information science, information technology, librarianship, and GIS have widely adopted the term. In these fields the word metadata is defined as "data about data".[17][page needed] While this is the generally accepted definition, various disciplines have adopted their own more specific explanation and uses of the term.


While the metadata application is manifold, covering a large variety of fields, there are specialized and well-accepted models to specify types of metadata. Bretherton & Singley (1994) distinguish between two distinct classes: structural/control metadata and guide metadata.[18] Structural metadata describes the structure of database objects such as tables, columns, keys and indexes. Guide metadata helps humans find specific items and are usually expressed as a set of keywords in a natural language. According to Ralph Kimball metadata can be divided into 2 similar categories: technical metadata and business metadata. Technical metadata corresponds to internal metadata, and business metadata corresponds to external metadata. Kimball adds a third category, process metadata. On the other hand, NISO distinguishes among three types of metadata: descriptive, structural, and administrative.[17]

Descriptive metadata is typically used for discovery and identification, as information to search and locate an object, such as title, author, subjects, keywords, publisher. Structural metadata describes how the components of an object are organized. An example of structural metadata would be how pages are ordered to form chapters of a book. Finally, administrative metadata gives information to help manage the source. Administrative metadata refers to the technical information, including file type, or when and how the file was created. Two sub-types of administrative metadata are rights management metadata and preservation metadata. Rights management metadata explains intellectual property rights, while preservation metadata contains information to preserve and save a resource.[7][page needed]

An additional type of metadata beginning to be more developed is accessibility metadata. Accessibility metadata is not a new concept to libraries; however, advances in universal design have raised its profile.[19]:213-214 Projects like Cloud4All and GPII identified the lack of common terminologies and models to describe the needs and preferences of users and information that fits those needs as a major gap in providing universal access solutions.[19]:210-211. Those types of information are accessibility metadata.[19]:214 Schema.org has incorporated several accessibility properties based on IMS Global Access for All Information Model Data Element Specification.[19]:214 The Wiki page WebSchemas/Accessibility lists several properties and their values.

While the efforts to describe and standardize the varied accessibility needs of information seekers are beginning to become more robust their adoption into established metadata schemas has not been as developed. For example, while Dublin Core (DC)'s “audience” and MARC 21's “reading level” could be used to identify resources suitable for users with dyslexia and DC's “Format” could be used to identify resources available in braille, audio, or large print formats, there is more work to be done.[19]:214


Metadata (metacontent) or, more correctly, the vocabularies used to assemble metadata (metacontent) statements, is typically structured according to a standardized concept using a well-defined metadata scheme, including: metadata standards and metadata models. Tools such as controlled vocabularies, taxonomies, thesauri, data dictionaries, and metadata registries can be used to apply further standardization to the metadata. Structural metadata commonality is also of paramount importance in data model development and in database design.


Metadata (metacontent) syntax refers to the rules created to structure the fields or elements of metadata (metacontent).[20] A single metadata scheme may be expressed in a number of different markup or programming languages, each of which requires a different syntax. For example, Dublin Core may be expressed in plain text, HTML, XML, and RDF.[21]

A common example of (guide) metacontent is the bibliographic classification, the subject, the Dewey Decimal class number. There is always an implied statement in any "classification" of some object. To classify an object as, for example, Dewey class number 514 (Topology) (i.e. books having the number 514 on their spine) the implied statement is: "<book><subject heading><514>. This is a subject-predicate-object triple, or more importantly, a class-attribute-value triple. The first two elements of the triple (class, attribute) are pieces of some structural metadata having a defined semantic. The third element is a value, preferably from some controlled vocabulary, some reference (master) data. The combination of the metadata and master data elements results in a statement which is a metacontent statement i.e. "metacontent = metadata + master data". All of these elements can be thought of as "vocabulary". Both metadata and master data are vocabularies which can be assembled into metacontent statements. There are many sources of these vocabularies, both meta and master data: UML, EDIFACT, XSD, Dewey/UDC/LoC, SKOS, ISO-25964, Pantone, Linnaean Binomial Nomenclature, etc. Using controlled vocabularies for the components of metacontent statements, whether for indexing or finding, is endorsed by ISO 25964: "If both the indexer and the searcher are guided to choose the same term for the same concept, then relevant documents will be retrieved."[22] This is particularly relevant when considering search engines of the internet, such as Google. The process indexes pages then matches text strings using its complex algorithm; there is no intelligence or "inferencing" occurring, just the illusion thereof.

Hierarchical, linear and planar schemata

Metadata schemata can be hierarchical in nature where relationships exist between metadata elements and elements are nested so that parent-child relationships exist between the elements. An example of a hierarchical metadata schema is the IEEE LOM schema, in which metadata elements may belong to a parent metadata element. Metadata schemata can also be one-dimensional, or linear, where each element is completely discrete from other elements and classified according to one dimension only. An example of a linear metadata schema is the Dublin Core schema, which is one dimensional. Metadata schemata are often two dimensional, or planar, where each element is completely discrete from other elements but classified according to two orthogonal dimensions.[23]


In all cases where the metadata schemata exceed the planar depiction, some type of hypermapping is required to enable display and view of metadata according to chosen aspect and to serve special views. Hypermapping frequently applies to layering of geographical and geological information overlays.[24]


The degree to which the data or metadata is structured is referred to as its "granularity". "Granularity" refers to how much detail is provided. Metadata with a high granularity allows for deeper, more detailed, and more structured information and enables greater level of technical manipulation. A lower level of granularity means that metadata can be created for considerably lower costs but will not provide as detailed information. The major impact of granularity is not only on creation and capture, but moreover on maintenance costs. As soon as the metadata structures become outdated, so too is the access to the referred data. Hence granularity must take into account the effort to create the metadata as well as the effort to maintain it.


International standards apply to metadata. Much work is being accomplished in the national and international standards communities, especially ANSI (American National Standards Institute) and ISO (International Organization for Standardization) to reach consensus on standardizing metadata and registries. The core metadata registry standard is ISO/IEC 11179 Metadata Registries (MDR), the framework for the standard is described in ISO/IEC 11179-1:2004.[25] A new edition of Part 1 is in its final stage for publication in 2015 or early 2016. It has been revised to align with the current edition of Part 3, ISO/IEC 11179-3:2013[26] which extends the MDR to support registration of Concept Systems. (see ISO/IEC 11179). This standard specifies a schema for recording both the meaning and technical structure of the data for unambiguous usage by humans and computers. ISO/IEC 11179 standard refers to metadata as information objects about data, or "data about data". In ISO/IEC 11179 Part-3, the information objects are data about Data Elements, Value Domains, and other reusable semantic and representational information objects that describe the meaning and technical details of a data item. This standard also prescribes the details for a metadata registry, and for registering and administering the information objects within a Metadata Registry. ISO/IEC 11179 Part 3 also has provisions for describing compound structures that are derivations of other data elements, for example through calculations, collections of one or more data elements, or other forms of derived data. While this standard describes itself originally as a "data element" registry, its purpose is to support describing and registering metadata content independently of any particular application, lending the descriptions to being discovered and reused by humans or computers in developing new applications, databases, or for analysis of data collected in accordance with the registered metadata content. This standard has become the general basis for other kinds of metadata registries, reusing and extending the registration and administration portion of the standard.

The Geospatial community has a tradition of specialized geospatial metadata standards, particularly building on traditions of map- and image-libraries and catalogues. Formal metadata is usually essential for geospatial data, as common text-processing approaches are not applicable.

The Dublin Core metadata terms are a set of vocabulary terms which can be used to describe resources for the purposes of discovery. The original set of 15 classic[27] metadata terms, known as the Dublin Core Metadata Element Set[28] are endorsed in the following standards documents:

Although not a standard, Microformat (also mentioned in the section metadata on the internet below) is a web-based approach to semantic markup which seeks to re-use existing HTML/XHTML tags to convey metadata. Microformat follows XHTML and HTML standards but is not a standard in itself. One advocate of microformats, Tantek Çelik, characterized a problem with alternative approaches:



Metadata may be written into a digital photo file that will identify who owns it, copyright and contact information, what brand or model of camera created the file, along with exposure information (shutter speed, f-stop, etc.) and descriptive information, such as keywords about the photo, making the file or image searchable on a computer and/or the Internet. Some metadata is created by the camera and some is input by the photographer and/or software after downloading to a computer. Most digital cameras write metadata about model number, shutter speed, etc., and some enable you to edit it;[33] this functionality has been available on most Nikon DSLRs since the Nikon D3, on most new Canon cameras since the Canon EOS 7D, and on most Pentax DSLRs since the Pentax K-3. Metadata can be used to make organizing in post-production easier with the use of key-wording. Filters can be used to analyze a specific set of photographs and create selections on criteria like rating or capture time.

Photographic Metadata Standards are governed by organizations that develop the following standards. They include, but are not limited to:

  • IPTC Information Interchange Model IIM (International Press Telecommunications Council),
  • IPTC Core Schema for XMP
  • XMP – Extensible Metadata Platform (an ISO standard)
  • Exif – Exchangeable image file format, Maintained by CIPA (Camera & Imaging Products Association) and published by JEITA (Japan Electronics and Information Technology Industries Association)
  • Dublin Core (Dublin Core Metadata Initiative – DCMI)
  • PLUS (Picture Licensing Universal System).
  • VRA Core (Visual Resource Association)[34]


Information on the times, origins and destinations of phone calls, electronic messages, instant messages and other modes of telecommunication, as opposed to message content, is another form of metadata. Bulk collection of this call detail record metadata by intelligence agencies has proven controversial after disclosures by Edward Snowden Intelligence agencies such as the NSA are keeping online metadata of millions of internet user for up to a year, regardless of whether or not they are persons of interest to the agency.


Metadata is particularly useful in video, where information about its contents (such as transcripts of conversations and text descriptions of its scenes) is not directly understandable by a computer, but where efficient search of the content is desirable. This is particularly useful in video applications such as Automatic Number Plate Recognition software, wherein license plate data is saved and used to create reports and alerts.[35] There are two sources in which video metadata is derived: (1) operational gathered metadata, that is information about the content produced, such as the type of equipment, software, date, and location; (2) human-authored metadata, to improve search engine visibility, discoverability, audience engagement, and providing advertising opportunities to video publishers.[36] In today's society most professional video editing software has access to metadata. Avid's MetaSync and Adobe's Bridge are two prime examples of this.[37]


Metadata can be created either by automated information processing or by manual work. Elementary metadata captured by computers can include information about when an object was created, who created it, when it was last updated, file size, and file extension. In this context an object refers to any of the following:

  • A physical item such as a book, CD, DVD, a paper map, chair, table, flower pot, etc.
  • An electronic file such as a digital image, digital photo, electronic document, program file, database table, etc.

Data virtualization

Data virtualization has emerged in the 2000s as the new software technology to complete the virtualization "stack" in the enterprise. Metadata is used in data virtualization servers which are enterprise infrastructure components, alongside database and application servers. Metadata in these servers is saved as persistent repository and describe business objects in various enterprise systems and applications. Structural metadata commonality is also important to support data virtualization.

Statistics and census services

Standardization work has had a large impact on efforts to build metadata systems in the statistical community[citation needed]. Several metadata standards[which?] are described, and their importance to statistical agencies is discussed. Applications of the standards[which?] at the Census Bureau, Environmental Protection Agency, Bureau of Labor Statistics, Statistics Canada, and many others are described[citation needed]. Emphasis is on the impact a metadata registry can have in a statistical agency.

Library and information science

Metadata has been used in various ways as a means of cataloging items in libraries in both digital and analog format. Such data helps classify, aggregate, identify, and locate a particular book, DVD, magazine or any object a library might hold in its collection. Until the 1980s, many library catalogues used 3x5 inch cards in file drawers to display a book's title, author, subject matter, and an abbreviated alpha-numeric string (call number) which indicated the physical location of the book within the library's shelves. The Dewey Decimal System employed by libraries for the classification of library materials by subject is an early example of metadata usage. Beginning in the 1980s and 1990s, many libraries replaced these paper file cards with computer databases. These computer databases make it much easier and faster for users to do keyword searches. Another form of older metadata collection is the use by US Census Bureau of what is known as the "Long Form." The Long Form asks questions that are used to create demographic data to find patterns of distribution.[38] Libraries employ metadata in library catalogues, most commonly as part of an Integrated Library Management System. Metadata is obtained by cataloguing resources such as books, periodicals, DVDs, web pages or digital images. This data is stored in the integrated library management system, ILMS, using the MARC metadata standard. The purpose is to direct patrons to the physical or electronic location of items or areas they seek as well as to provide a description of the item/s in question.

More recent and specialized instances of library metadata include the establishment of digital libraries including e-print repositories and digital image libraries. While often based on library principles, the focus on non-librarian use, especially in providing metadata, means they do not follow traditional or common cataloging approaches. Given the custom nature of included materials, metadata fields are often specially created e.g. taxonomic classification fields, location fields, keywords or copyright statement. Standard file information such as file size and format are usually automatically included.[39] Library operation has for decades been a key topic in efforts toward international standardization. Standards for metadata in digital libraries include Dublin Core, METS, MODS, DDI, DOI, URN, PREMIS schema, EML, and OAI-PMH. Leading libraries in the world give hints on their metadata standards strategies.[40][41]

In museums

Metadata in a museum context is the information that trained cultural documentation specialists, such as archivists, librarians, museum registrars and curators, create to index, structure, describe, identify, or otherwise specify works of art, architecture, cultural objects and their images.[42][43][page needed][44][page needed] Descriptive metadata is most commonly used in museum contexts for object identification and resource recovery purposes.[43]


Metadata is developed and applied within collecting institutions and museums in order to:

  • Facilitate resource discovery and execute search queries.[44]
  • Create digital archives that store information relating to various aspects of museum collections and cultural objects, and serves for archival and managerial purposes.[44]
  • Provide public audiences access to cultural objects through publishing digital content online.[43][44]


Many museums and cultural heritage centers recognize that given the diversity of art works and cultural objects, no single model or standard suffices to describe and catalogue cultural works.[42][43][44] For example, a sculpted Indigenous artifact could be classified as an artwork, an archaeological artifact, or an Indigenous heritage item. The early stages of standardization in archiving, description and cataloging within the museum community began in the late 1990s with the development of standards such as Categories for the Description of Works of Art (CDWA), Spectrum, CIDOC Conceptual Reference Model (CRM), Cataloging Cultural Objects (CCO) and the CDWA Lite XML schema.[43] These standards use HTML and XML markup languages for machine processing, publication and implementation.[43] The Anglo-American Cataloguing Rules (AACR), originally developed for characterizing books, have also been applied to cultural objects, works of art and architecture.[44] Standards, such as the CCO, are integrated within a Museum's Collections Management System (CMS), a database through which museums are able to manage their collections, acquisitions, loans and conservation.[44] Scholars and professionals in the field note that the "quickly evolving landscape of standards and technologies" create challenges for cultural documentarians, specifically non-technically trained professionals.[45][page needed] Most collecting institutions and museums use a relational database to categorize cultural works and their images.[44] Relational databases and metadata work to document and describe the complex relationships amongst cultural objects and multi-faceted works of art, as well as between objects and places, people and artistic movements.[43][44] Relational database structures are also beneficial within collecting institutions and museums because they allow for archivists to make a clear distinction between cultural objects and their images; an unclear distinction could lead to confusing and inaccurate searches.[44]

Cultural objects and art works

An object's materiality, function and purpose, as well as the size (e.g., measurements, such as height, width, weight), storage requirements (e.g., climate-controlled environment) and focus of the museum and collection, influence the descriptive depth of the data attributed to the object by cultural documentarians.[44] The established institutional cataloging practices, goals and expertise of cultural documentarians and database structure also influence the information ascribed to cultural objects, and the ways in which cultural objects are categorized.[42][44] Additionally, museums often employ standardized commercial collection management software that prescribes and limits the ways in which archivists can describe artworks and cultural objects.[45] As well, collecting institutions and museums use Controlled Vocabularies to describe cultural objects and artworks in their collections.[43][44] Getty Vocabularies and the Library of Congress Controlled Vocabularies are reputable within the museum community and are recommended by CCO standards.[44] Museums are encouraged to use controlled vocabularies that are contextual and relevant to their collections and enhance the functionality of their digital information systems.[43][44] Controlled Vocabularies are beneficial within databases because they provide a high level of consistency, improving resource retrieval.[43][44] Metadata structures, including controlled vocabularies, reflect the ontologies of the systems from which they were created. Often the processes through which cultural objects are described and categorized through metadata in museums do not reflect the perspectives of the maker communities.[42][46]

Museums and the Internet

Metadata has been instrumental in the creation of digital information systems and archives within museums, and has made it easier for museums to publish digital content online. This has enabled audiences who might not have had access to cultural objects due to geographic or economic barriers to have access to them.[43] In the 2000s, as more museums have adopted archival standards and created intricate databases, discussions about Linked Data between museum databases have come up in the museum, archival and library science communities.[45] Collection Management Systems (CMS) and Digital Asset Management tools can be local or shared systems.[44] Digital Humanities scholars note many benefits of interoperability between museum databases and collections, while also acknowledging the difficulties achieving such interoperability.[45]



Problems involving metadata in litigation in the United States are becoming widespread.[when?] Courts have looked at various questions involving metadata, including the discoverability of metadata by parties. Although the Federal Rules of Civil Procedure have only specified rules about electronic documents, subsequent case law has elaborated on the requirement of parties to reveal metadata.[47] In October 2009, the Arizona Supreme Court has ruled that metadata records are public record.[48] Document metadata have proven particularly important in legal environments in which litigation has requested metadata, which can include sensitive information detrimental to a certain party in court. Using metadata removal tools to "clean" or redact documents can mitigate the risks of unwittingly sending sensitive data. This process partially (see data remanence) protects law firms from potentially damaging leaking of sensitive data through electronic discovery.


Problems involving metadata in litigation in the United States are becoming widespread.[when?] Courts have looked at various questions involving metadata, including the discoverability of metadata by parties. Although the Federal Rules of Civil Procedure have only specified rules about electronic documents, subsequent case law has elaborated on the requirement of parties to reveal metadata.[49] In October 2009, the Arizona Supreme Court has ruled that metadata records are public record.[50] Document metadata have proven particularly important in legal environments in which litigation has requested metadata, which can include sensitive information detrimental to a certain party in court. Using metadata removal tools to "clean" or redact documents can mitigate the risks of unwittingly sending sensitive data. This process partially (see data remanence) protects law firms from potentially damaging leaking of sensitive data through electronic discovery.


In Australia, the need to strengthen national security has resulted in the introduction of a new metadata storage law.[51] This new law means that both security and policing agencies will be allowed to access up to two years of an individual's metadata, with the aim of making it easier to stop any terrorist attacks and serious crimes from happening.

In healthcare

Australian medical research pioneered the definition of metadata for applications in health care. That approach offers the first recognized attempt to adhere to international standards in medical sciences instead of defining a proprietary standard under the World Health Organization (WHO) umbrella. The medical community yet did not approve the need to follow metadata standards despite research that supported these standards.[52]

Data warehousing

A data warehouse (DW) is a repository of an organization's electronically stored data. Data warehouses are designed to manage and store the data. Data warehouses differ from business intelligence (BI) systems, because BI systems are designed to use data to create reports and analyze the information, to provide strategic guidance to management.[53] Metadata is an important tool in how data is stored in data warehouses. The purpose of a data warehouse is to house standardized, structured, consistent, integrated, correct, "cleaned" and timely data, extracted from various operational systems in an organization. The extracted data are integrated in the data warehouse environment to provide an enterprise-wide perspective. Data are structured in a way to serve the reporting and analytic requirements. The design of structural metadata commonality using a data modeling method such as entity relationship model diagramming is important in any data warehouse development effort. They detail metadata on each piece of data in the data warehouse. An essential component of a data warehouse/business intelligence system is the metadata and tools to manage and retrieve the metadata. Ralph Kimball[54][page needed] describes metadata as the DNA of the data warehouse as metadata defines the elements of the data warehouse and how they work together.

Kimball et al.[55] refers to three main categories of metadata: Technical metadata, business metadata and process metadata. Technical metadata is primarily definitional, while business metadata and process metadata is primarily descriptive. The categories sometimes overlap.

  • Technical metadata defines the objects and processes in a DW/BI system, as seen from a technical point of view. The technical metadata includes the system metadata, which defines the data structures such as tables, fields, data types, indexes and partitions in the relational engine, as well as databases, dimensions, measures, and data mining models. Technical metadata defines the data model and the way it is displayed for the users, with the reports, schedules, distribution lists, and user security rights.
  • Business metadata is content from the data warehouse described in more user-friendly terms. The business metadata tells you what data you have, where they come from, what they mean and what their relationship is to other data in the data warehouse. Business metadata may also serve as a documentation for the DW/BI system. Users who browse the data warehouse are primarily viewing the business metadata.
  • Process metadata is used to describe the results of various operations in the data warehouse. Within the ETL process, all key data from tasks is logged on execution. This includes start time, end time, CPU seconds used, disk reads, disk writes, and rows processed. When troubleshooting the ETL or query process, this sort of data becomes valuable. Process metadata is the fact measurement when building and using a DW/BI system. Some organizations make a living out of collecting and selling this sort of data to companies - in that case the process metadata becomes the business metadata for the fact and dimension tables. Collecting process metadata is in the interest of business people who can use the data to identify the users of their products, which products they are using, and what level of service they are receiving.

On the Internet

The HTML format used to define web pages allows for the inclusion of a variety of types of metadata, from basic descriptive text, dates and keywords to further advanced metadata schemes such as the Dublin Core, e-GMS, and AGLS[56] standards. Pages can also be geotagged with coordinates. Metadata may be included in the page's header or in a separate file. Microformats allow metadata to be added to on-page data in a way that regular web users do not see, but computers, web crawlers and search engines can readily access. Many search engines are cautious about using metadata in their ranking algorithms due to exploitation of metadata and the practice of search engine optimization, SEO, to improve rankings. See Meta element article for further discussion. This cautious attitude may be justified as people, according to Doctorow,[57] are not executing care and diligence when creating their own metadata and that metadata is part of a competitive environment where the metadata is used to promote the metadata creators own purposes. Studies show that search engines respond to web pages with metadata implementations,[58] and Google has an announcement on its site showing the meta tags that its search engine understands.[59] Enterprise search startup Swiftype recognizes metadata as a relevance signal that webmasters can implement for their website-specific search engine, even releasing their own extension, known as Meta Tags 2.[60]

In broadcast industry

In broadcast industry, metadata is linked to audio and video broadcast media to:

  • identify the media: clip or playlist names, duration, timecode, etc.
  • describe the content: notes regarding the quality of video content, rating, description (for example, during a sport event, keywords like goal, red card will be associated to some clips)
  • classify media: metadata allows producers to sort the media or to easily and quickly find a video content (a TV news could urgently need some archive content for a subject). For example, the BBC have a large subject classification system, Lonclass, a customized version of the more general-purpose Universal Decimal Classification.

This metadata can be linked to the video media thanks to the video servers. Most major broadcast sport events like FIFA World Cup or the Olympic Games use this metadata to distribute their video content to TV stations through keywords. It is often the host broadcaster[61] who is in charge of organizing metadata through its International Broadcast Centre and its video servers. This metadata is recorded with the images and are entered by metadata operators (loggers) who associate in live metadata available in metadata grids through software (such as Multicam(LSM) or IPDirector used during the FIFA World Cup or Olympic Games).[62][63]


Metadata that describes geographic objects in electronic storage or format (such as datasets, maps, features, or documents with a geospatial component) has a history dating back to at least 1994 (refer MIT Library page on FGDC Metadata). This class of metadata is described more fully on the geospatial metadata article.

Ecological and environmental

Ecological and environmental metadata is intended to document the "who, what, when, where, why, and how" of data collection for a particular study. This typically means which organization or institution collected the data, what type of data, which date(s) the data was collected, the rationale for the data collection, and the methodology used for the data collection. Metadata should be generated in a format commonly used by the most relevant science community, such as Darwin Core, Ecological Metadata Language,[64] or Dublin Core. Metadata editing tools exist to facilitate metadata generation (e.g. Metavist,[65] Mercury: Metadata Search System, Morpho[66]). Metadata should describe provenance of the data (where they originated, as well as any transformations the data underwent) and how to give credit for (cite) the data products.

Digital music

When first released in 1982, Compact Discs only contained a Table Of Contents (TOC) with the number of tracks on the disc and their length in samples.[2][dead link][3] Fourteen years later in 1996, a revision of the CD Red Book standard added CD-Text to carry additional metadata.[4] But CD-Text was not widely adopted. Shortly thereafter, it became common for personal computers to retrieve metadata from external sources (e.g. CDDB, Gracenote) based on the TOC.

Digital audio formats such as digital audio files superseded music formats such as cassette tapes and CDs in the 2000s. Digital audio files could be labelled with more information than could be contained in just the file name. That descriptive information is called the audio tag or audio metadata in general. Computer programs specializing in adding or modifying this information are called tag editors. Metadata can be used to name, describe, catalogue and indicate ownership or copyright for a digital audio file, and its presence makes it much easier to locate a specific audio file within a group, typically through use of a search engine that accesses the metadata. As different digital audio formats were developed, attempts were made to standardize a specific location within the digital files where this information could be stored.

As a result, almost all digital audio formats, including mp3, broadcast wav and AIFF files, have similar standardized locations that can be populated with metadata. The metadata for compressed and uncompressed digital music is often encoded in the ID3 tag. Common editors such as TagLib support MP3, Ogg Vorbis, FLAC, MPC, Speex, WavPack TrueAudio, WAV, AIFF, MP4, and ASF file formats.

Cloud applications

With the availability of cloud applications, which include those to add metadata to content, metadata is increasingly available over the Internet.

Administration and management


Metadata can be stored either internally,[67] in the same file or structure as the data (this is also called embedded metadata), or externally, in a separate file or field from the described data. A data repository typically stores the metadata detached from the data, but can be designed to support embedded metadata approaches. Each option has advantages and disadvantages:

  • Internal storage means metadata always travels as part of the data they describe; thus, metadata is always available with the data, and can be manipulated locally. This method creates redundancy (precluding normalization), and does not allow managing all of a system's metadata in one place. It arguably increases consistency, since the metadata is readily changed whenever the data is changed.
  • External storage allows collocating metadata for all the contents, for example in a database, for more efficient searching and management. Redundancy can be avoided by normalizing the metadata's organization. In this approach, metadata can be united with the content when information is transferred, for example in Streaming media; or can be referenced (for example, as a web link) from the transferred content. On the down side, the division of the metadata from the data content, especially in standalone files that refer to their source metadata elsewhere, increases the opportunities for misalignments between the two, as changes to either may not be reflected in the other.

Metadata can be stored in either human-readable or binary form. Storing metadata in a human-readable format such as XML can be useful because users can understand and edit it without specialized tools.[68] However, text-based formats are rarely optimized for storage capacity, communication time, or processing speed. A binary metadata format enables efficiency in all these respects, but requires special software to convert the binary information into human-readable content.

Database management

Each relational database system has its own mechanisms for storing metadata. Examples of relational-database metadata include:

  • Tables of all tables in a database, their names, sizes, and number of rows in each table.
  • Tables of columns in each database, what tables they are used in, and the type of data stored in each column.

In database terminology, this set of metadata is referred to as the catalog. The SQL standard specifies a uniform means to access the catalog, called the information schema, but not all databases implement it, even if they implement other aspects of the SQL standard. For an example of database-specific metadata access methods, see Oracle metadata. Programmatic access to metadata is possible using APIs such as JDBC, or SchemaCrawler.[69]

In popular culture

One of the first satirical examinations of the concept of Metadata as we understand it today is American Science Fiction author Hal Draper's short story, MS_Fnd_in_a_Lbry (1961). Here, the knowledge of all Mankind is condensed into an object the size of a desk drawer, however the magnitude of the metadata (e.g. catalog of catalogs of... , as well as indexes and histories) eventually leads to dire yet humorous consequence for the human race. The story prefigures the modern consequences of allowing metadata to become more important than the real data it is concerned with, and the risks inherent in that eventuality as a cautionary tale.

See also


  1. ^ "Archived copy". Archived from the original on 27 February 2015. Retrieved 27 February 2015. 
  2. ^ Zeng, Marcia (2004). "Metadata Types and Functions". NISO. Archived from the original on 7 October 2016. Retrieved 5 October 2016. 
  3. ^ "Archived copy". Archived from the original on 27 March 2017. Retrieved 10 May 2017. 
  4. ^ National Information Standards Organization (NISO) (2001). Understanding Metadata (PDF). NISO Press. p. 1. ISBN 1-880124-62-9. Archived (PDF) from the original on 7 November 2014. 
  5. ^ Steiner, Tobias (2017-11-23). "Metadaten und OER: Geschichte einer Beziehung (Metadata and OER: [hi]story of a relationship)". Synergie. Fachmagazin für Digitalisierung in der Lehre (in German). 04: 54. doi:10.17613/m6p81g. ISSN 2509-3096. 
  6. ^ "Best Practices for Structural Metadata". University of Illinois. 15 December 2010. Archived from the original on 24 June 2016. Retrieved 17 June 2016. 
  7. ^ a b National Information Standards Organization; Rebecca Guenther; Jaqueline Radebaugh (2004). Understanding Metadata (PDF). Bethesda, MD: NISO Press. ISBN 1-880124-62-9. Archived (PDF) from the original on 7 November 2014. Retrieved 2 April 2014. 
  8. ^ "Archived copy". Archived from the original on 21 June 2016. Retrieved 6 June 2016. 
  9. ^ "Archived copy". Archived from the original on 22 December 2016. Retrieved 21 December 2016. 
  10. ^ "A Guardian Guide to your Metadata". theguardian.com. Guardian News and Media Limited. 12 June 2013. Archived from the original on 6 March 2016. 
  11. ^ "ADEO Imaging: TIFF Metadata". Archived from the original on 17 May 2013. Retrieved 20 May 2013. 
  12. ^ a b c d Rouse, Margaret (July 2014). "Metadata". WhatIs. TechTarget. Archived from the original on 29 October 2015. 
  13. ^ Hüner, K.; Otto, B.; Österle, H.: Collaborative management of business metadata, in: International Journal of Information Management, 2011
  14. ^ "Metadata Standards And Metadata Registries: An Overview" (PDF). Archived (PDF) from the original on 29 June 2011. Retrieved 23 December 2011. 
  15. ^ Philip Bagley (November 1968). "Extension of programming language concepts" (PDF). Philadelphia: University City Science Center. Archived (PDF) from the original on 30 November 2012. 
  16. ^ "The notion of "metadata" introduced by Bagley". Solntseff, N+1; Yezerski, A (1974). "A survey of extensible programming languages". Annual Review in Automatic Programming. 7. Elsevier Science Ltd: 267–307. doi:10.1016/0066-4138(74)90001-9. 
  17. ^ a b NISO. Understanding Metadata (PDF). NISO Press. ISBN 1-880124-62-9. Archived (PDF) from the original on 7 November 2014. Retrieved 5 January 2010. 
  18. ^ Bretherton, F. P.; Singley, P.T. (1994). Metadata: A User's View, Proceedings of the International Conference on Very Large Data Bases (VLDB). pp. 1091–1094. 
  19. ^ a b c d e Beyene, Wondwossen Mulualem (2017). "Metadata and universal access in digital library environments". Library Hi Tech. 35 (2). doi:10.1108/LHT-06-2016-0074. 
  20. ^ Cathro, Warwick (1997). "Metadata: an overview". Archived from the original on 22 December 2009. Retrieved 6 January 2010. 
  21. ^ DCMI (5 October 2009). "Semantic Recommendations". Archived from the original on 31 December 2009. Retrieved 6 January 2010. 
  22. ^ https://www.iso.org/obp/ui/#iso:std:iso:25964:-1:ed-1:v1:en Archived 17 June 2016 at the Wayback Machine.
  23. ^ "Types of Metadata". University of Melbourne. 15 August 2006. Archived from the original on 2009-10-24. Retrieved 6 January 2010. 
  24. ^ Kübler, Stefanie; Skala, Wolfdietrich; Voisard, Agnès. "THE DESIGN AND DEVELOPMENT OF A GEOLOGIC HYPERMAP PROTOTYPE" (PDF). Archived (PDF) from the original on 3 October 2013. 
  25. ^ "ISO/IEC 11179-1:2004 Information technology - Metadata registries (MDR) - Part 1: Framework". Iso.org. 18 March 2009. Archived from the original on 17 January 2012. Retrieved 23 December 2011. 
  26. ^ "ISO/IEC 11179-3:2013 Information technology-Metadata registries - Part 3: Registry metamodel and basic attributes". iso.org. 2014. 
  27. ^ "DCMI Specifications". Dublincore.org. 14 December 2009. Archived from the original on 17 August 2013. Retrieved 17 August 2013. 
  28. ^ "Dublin Core Metadata Element Set, Version 1.1". Dublincore.org. Archived from the original on 16 August 2013. Retrieved 17 August 2013. 
  29. ^ J. Kunze, T. Baker (2007). "The Dublin Core Metadata Element Set". ietf.org. Archived from the original on 4 August 2013. Retrieved 17 August 2013. 
  30. ^ "ISO 15836:2009 - Information and documentation - The Dublin Core metadata element set". Iso.org. 18 February 2009. Archived from the original on 27 March 2014. Retrieved 17 August 2013. 
  31. ^ "NISO Standards - National Information Standards Organization". Niso.org. 22 May 2007. Archived from the original on 16 November 2011. Retrieved 17 August 2013. 
  32. ^ "What's the Next Big Thing on the Web? It May Be a Small, Simple Thing -- Microformats". Knowledge@Wharton. Wharton School of the University of Pennsylvania. 2005-07-27. 
  33. ^ "How To Copyright Your Photos With Metadata". Guru Camera. gurucamera.com. Archived from the original on 30 June 2016. 
  34. ^ "VRA Core Support Pages". Visual Resource Association Foundation. Visual Resource Association Foundation. Archived from the original on 9 April 2016. Retrieved 27 February 2016. 
  35. ^ Homeland Security (October 2012). "System Assessment and Validation for Emergency Responders (SAVER)" (PDF). 
  36. ^ Webcase, Weblog (2011). "Examining video file metadata". Archived from the original on 26 November 2015. Retrieved 25 November 2015. 
  37. ^ Oak Tree Press (2011). "Metadata for Video". Archived from the original on 26 November 2015. Retrieved 25 November 2015. 
  38. ^ National Archives of Australia (2002). "AGLS Metadata Element Set - Part 2: Usage Guide - A non-technical guide to using AGLS metadata for describing resources". Archived from the original on 30 March 2010. Retrieved 17 March 2010. 
  39. ^ Solodovnik, Iryna (2011). "Metadata issues in Digital Libraries: key concepts and perspectives". JLIS.it: Italian Journal of Library, Archives and Information Science. University of Florence. 2 (2). doi:10.4403/jlis.it-4663. Archived from the original on 16 June 2013. Retrieved 29 June 2013. 
  40. ^ Library of Congress Network Development and MARC Standards Office (8 September 2005). "Library of Congress Washington DC on metadata". Loc.gov. Archived from the original on 15 December 2011. Retrieved 23 December 2011. 
  41. ^ "Deutsche Nationalbibliothek Frankfurt on metadata". Archived from the original on 24 October 2012. 
  42. ^ a b c d Zange, Charles S. (31 January 2015). "Community makers, major museums, and the Keet S'aaxw: Learning about the role of museums in interpreting cultural objects". Museums and the Web. Archived from the original on 4 November 2016. 
  43. ^ a b c d e f g h i j k Baca, Murtha (2006). Cataloging cultural objects: a guide to describing cultural works and their images. Visual Resources Association. Visual Resources Association. 
  44. ^ a b c d e f g h i j k l m n o p q Baca, Murtha (2008). Introduction to Metadata: Second Edition. Los Angeles: Getty Information Institute. Los Angeles: Getty Information Institute. 
  45. ^ a b c d Hooland, Seth Van; Verborgh, Ruben (2014). Linked Data for Libraries, Archives and Museums: How to Clean, Link and Publish Your Metadata. London: Facet. 
  46. ^ Srinivasan, Ramesh (December 2006). "Indigenous, ethnic and cultural articulations of new media". International Journal of Cultural Studies. 9 (4). doi:10.1177/1367877906069899. Archived from the original on 18 October 2014. 
  47. ^ Gelzer, Reed D. (February 2008). "Metadata, Law, and the Real World: Slowly, the Three Are Merging". Journal of AHIMA. American Health Information Management Association. 79 (2): 56–57, 64. Archived from the original on 13 September 2010. Retrieved 8 January 2010. 
  48. ^ Walsh, Jim (30 October 2009). "Ariz. Supreme Court rules electronic data is public record". The Arizona Republic. Phoenix, Arizona. Retrieved 8 January 2010. 
  49. ^ Gelzer, Reed D. (February 2008). "Metadata, Law, and the Real World: Slowly, the Three Are Merging". Journal of AHIMA. American Health Information Management Association. 79 (2): 56–57, 64. Archived from the original on 13 September 2010. Retrieved 8 January 2010. 
  50. ^ Walsh, Jim (30 October 2009). "Ariz. Supreme Court rules electronic data is public record". The Arizona Republic. Phoenix, Arizona. Retrieved 8 January 2010. 
  51. ^ Senate passes controversial metadata laws
  52. ^ M. Löbe, M. Knuth, R. Mücke TIM: A Semantic Web Application for the Specification of Metadata Items in Clinical Research Archived 11 May 2012 at the Wayback Machine., CEUR-WS.org, urn:nbn:de:0074-559-9
  53. ^ Inmon, W.H. Tech Topic: What is a Data Warehouse? Prism Solutions. Volume 1. 1995.
  54. ^ Kimball, Ralph (2008). The Data Warehouse Lifecycle Toolkit (Second ed.). New York: Wiley. pp. 10, 115–117, 131–132, 140, 154–155. ISBN 978-0-470-14977-5. 
  55. ^ Kimball 2008, pp. 116–117
  56. ^ National Archives of Australia, AGLS Metadata Standard, accessed 7 January 2010, "Archived copy". Archived from the original on 10 January 2010. Retrieved 7 January 2010. 
  57. ^ Metacrap: Putting the torch to seven straw-men of the meta-utopia "Archived copy". Archived from the original on 8 May 2007. Retrieved 8 May 2007. 
  58. ^ The impact of webpage content characteristics on webpage visibility in search engine results "Archived copy" (PDF). Archived (PDF) from the original on 7 September 2012. Retrieved 3 April 2012. 
  59. ^ "Meta tags that Google understands". Google.com. Archived from the original on 22 May 2014. Retrieved 22 May 2014. 
  60. ^ "Swiftype-specific Meta Tags". Swiftype Documentation. Swiftype. 3 October 2014. Archived from the original on 6 October 2014. 
  61. ^ "HBS is the FIFA host broadcaster". Hbs.tv. 6 August 2011. Archived from the original on 17 January 2012. Retrieved 23 December 2011. 
  62. ^ "Host Broadcast Media Server and Related Applications" (PDF). Archived from the original (PDF) on 2 November 2011. Retrieved 2013-08-17. 
  63. ^ "logs during sport events". Broadcastengineering.com. Archived from the original on 16 November 2011. Retrieved 23 December 2011. 
  64. ^ [1] Archived 23 April 2011 at the Wayback Machine.
  65. ^ "Metavist 2". Metavist.djames.net. Archived from the original on 21 August 2011. Retrieved 23 December 2011. 
  66. ^ "KNB Data :: Morpho". Knb.ecoinformatics.org. 20 May 2009. Archived from the original on 13 January 2012. Retrieved 23 December 2011. 
  67. ^ O'Neill, Dan. "ID3.org". Archived from the original on 11 November 2011. 
  68. ^ De Sutter, Robbie; Notebaert, Stijn; Van de Walle, Rik (September 2006). "Evaluation of Metadata Standards in the Context of Digital Audio-Visual Libraries". In Gonzalo, Julio; Thanos, Constantino; Verdejo, M. Felisa; Carrasco, Rafael. Research and Advanced Technology for Digital Libraries: 10th European Conference, EDCL 2006. Springer. p. 226. ISBN 978-3540446361. Archived from the original on 27 April 2016. 
  69. ^ Sualeh Fatehi. "SchemaCrawler". SourceForge. Archived from the original on 3 September 2009. 

Further reading

  • Gartner, Richard. 2016. Metadata: Shaping Knowledge from Antiquity to the Semantic Web . Springer. ISBN 9783319408910.
  • Zeng, Marcia & Qin, Jian. 2016. Metadata . Facet. ISBN 9781783300525.

External links