Distributed Interoperable Metadata Registry Abstract Interoperability between digital libraries depends on effective sharing of metadata. Successful sharing of metadata requires common standards for metadata exchange. Previous efforts have focused on either defining a single metadata standard, such as Dublin Core, or building digital library middleware, such as Z39.50 or Stanford's Digital Library Interoperability Protocol. In this article, we propose a distributed architecture for managing metadata and metadata schema. Instead of normalizing all metadata and schema to a single format, we have focused on building a middleware framework that tolerates heterogeneity. 1 Introduction Providing distributed, flexible search and retrieval of their collections was one of the promises of digital libraries. Metadata, at an abstract level, describes intrinsic and extrinsic data attributes according to an arbitrary, specific, and potentially unique conceptual space. 2 A State of Perpetual Metadata Heterogeneity 3.1 Metadata Schema Description
Descriptive metadata for copyright status The need to express the intellectual property rights of digital materials has focused on access and usage permissions which must be granted by the rights holder. A key set of permissions not acknowledged by these rights expressions is inherent in the legal copyright status of the item. Digital libraries can hold and provide access to many items for which copyright status is the sole governor of use. This article proposes a small set of descriptive data elements that should accompany digital materials to inform potential users of the copyright status of the item. One of the chief characteristics of digital works is the ease with which they can be re–used either in whole or in part. When users want to make use of an unprotected digital resource, they have to know the copyright status of the work in order to make a reasonable judgment. It is not uncommon to see statements associated with online resources offered by libraries that read something like:
Metadata Interoperability: A Study of Methodology Metadata Interoperability: A Study of Methodology Lois Mai Chan, Ph.DProfessor, School of Library and Information Science University of Kentucky U.S.A. loischan@uky.edu ABSTRACT: The rapid growth of Internet resources and digital collections and libraries is accompanied by a proliferation of metadata schemas. Introduction Recent decades have witnessed a proliferation of metadata schemas for description of digital resources. In recent literature, a great deal has been written about interoperability between and among different metadata schemas. Definition of Interoperability Many attempts have been to define the concept of interoperability. “The ability of multiple systems, using difference hardware and software platforms, data structures, and interfaces, to exchange and share data” (NISO 2004) “The ability of two or more systems or components to exchange information and use the exchanged information without special effort on either system” (ALCTS 2004) Uniform Standard Derivation Lingua Franca
Metadata Interoperability and Standardization - A Study of Methodology Part II: Achieving Interoperability at the Record and Repository Levels Abstract This is the second part of an analysis of the methods that have been used to achieve or improve interoperability among metadata schemas and their applications in order to facilitate the conversion and exchange of metadata and to enable cross-domain metadata harvesting and federated searches. From a methodological point of view, implementing interoperability may be considered at different levels of operation: schema level (discussed in Part I of the article), record level (discussed in Part II of the article), and repository level (also discussed in Part II). The results of efforts to improve interoperability may be observed from different perspectives as well, including element-based and value-based approaches. 1. As discussed in Part I of this study, the results of efforts to improve interoperability can be observed at different levels: Schema level – Efforts are focused on the elements of the schemas, being independent of any applications. 2. 2.1 Conversion of Metadata Records
Metadata Interoperability—What Is It, and Why Is It Important? | Marine Metadata Interoperability Introduction to interoperability - the exchange of metadata between computer systems Metadata interoperability is the ability of two or more information systems to exchange metadata with minimal loss of information. This does not address data compatibility – only interoperability of descriptive metadata. The OGC defines interoperability as the capability to communicate, execute programs, or transfer data among various functional units in a manner that requires the user to have little or no knowledge of the unique characteristics of those units ( ISO 2382-1). The OGC definition applies to metadata interoperability, when one replaces the word “data” in the definition with the word “metadata”. An important aspect is that interoperable metadata can be used by computer systems, in contrast to metadata that is designed to be read and understood by a person. Benefits of Interoperability Having interoperable metadata allows multiple systems to work with the same set of data and metadata.
Introduction to Metadata Elements: Library of Congress NOTE: This is an historical document from a 1998 pilot project and not a current Library of Congress metadata standard. Purpose: Identification of a core set of metadata elements to be used in the development, testing, and implementation of multiple repositories. Background: With a charter from the Digital Futures Group at the Library of Congress, representatives from Library Services, ITS and the National Digital Library Program drafted this list of elements drawing on previous work contained in Structural Metadata Dictionary for LC Digitized Material, version 1.03, and Metadata Table for the Coolidge-Consumerism Experiment, and on experience with the Thomson Editorial Asset Management System (TEAMS) repository proof-of-concept project, December 1998-April 1999. Types of Metadata: Metadata elements listed in the table are categorized according to three types: descriptive, administrative, and structural. The levels of metadata are Table of Core Metadata Elements | Example
Mapping between metadata formats MARC 21 to Dublin Core: MARC to Dublin Core Crosswalk - Library of Congress, Network Development and MARC Standards Office, February 2001.Available from: <URL: Dublin Core to USMARC: Dublin Core/MARC/GILS Crosswalk - Library of Congress, Network Development and MARC Standards Office, November 1999.Available from: <URL: See also: MARBI Discussion Paper No. 99: Metadata, Dublin Core, and USMARC: a review of current efforts, January 21, 1997.Available from: <URL: And: MARBI Discussion Paper No. 86: Mapping the Dublin Core Metadata Elements to USMARC, May 5, 1995.Available from: <URL: Dublin Core to danMARC2/GILS: Dublin Core/danMARC2/GILS Crosswalk - by Susanne Thorborg (Danish Library Center).Available from: <URL: Dublin Core to EAD. EAD to ISAD(G). ISAD(G) to EAD. USMARC to EAD.
Metadata.Net Home Page Semi-structured Data: Happy 10th Birthday! The first recorded mentions of “semi-structured data” occurred in two academic papers from Quass [1] and Tresch [2] in 1995. However, the real popularization of the term “semi-strucutred data” occurred through the seminal 1997 papers from Abiteboul, “Querying semi-structured data,” [3] and Buneman, “Semistructured data.” [4] Of course, semi-structured data had existed well before this time, only it had not been named as such. Peter Wood, a professor of computer science at Birkbeck College at the University of London, provides succinct definitions of the “structure” of various types of data: [5] — or classes. Entities in the same group have the same descriptions (or attributes), while descriptions for all entities in a group (or schema): a) have the same defined format; b) have a predefined length; c) are all present; and d) follow the same order. — the idea of semi-structured data predates XML but not HTML (with the actual genesis better associated with SGML, see below). [12] Y. </i>*}
Metadata Interoperability and Standardization - A Study of Methodology Part II: Achieving Interoperability at the Record and Repository Levels Abstract This is the second part of an analysis of the methods that have been used to achieve or improve interoperability among metadata schemas and their applications in order to facilitate the conversion and exchange of metadata and to enable cross-domain metadata harvesting and federated searches. From a methodological point of view, implementing interoperability may be considered at different levels of operation: schema level (discussed in Part I of the article), record level (discussed in Part II of the article), and repository level (also discussed in Part II). The results of efforts to improve interoperability may be observed from different perspectives as well, including element-based and value-based approaches. 1. As discussed in Part I of this study, the results of efforts to improve interoperability can be observed at different levels: Schema level – Efforts are focused on the elements of the schemas, being independent of any applications. 2. 2.1 Conversion of Metadata Records
Metadata When you select a license from the Creative Commons License Chooser, you're provided with HTML to place in your page. That HTML contains metadata which allows software to understand that you've applied a license to your work. Metadata is data about data. For example: title, creator, and licensing information. When you choose a license on our website, you get back some metadata (licensing information) encoded in RDF. What is RDF? RDF (Resource Description Framework) is a framework for metadata. the subject: a thing, identified by its URL the predicate: the type of metadata (like title or creator), also identified by a URL the object: the value of this type of metadata (like "The Story of My Life" or 'a person named "John Q. Together, these make RDF statements, which are expressed in a language called RDF/XML. What is the Semantic Web? The Semantic Web is the part of the Web available in RDF. RDF can also be used to create more powerful search engines.