This link has been bookmarked by 34 people . It was first bookmarked on 31 Jul 2006, by Kevin Wen.
-
21 Oct 15
-
03 Apr 15
-
A metadata schema provides a formal structure designed to identify the knowledge structure of a given discipline and to link that structure to the information of the discipline through the creation of an information system that will assist the identification, discovery, and use of information within that discipline
-
For each element defined, a metadata standard usually provides content rules for how content should be included (for example, how to identify the main title), representation rules for content (for example, capitalization rules or standards for representing time), and allowable content values (for example, whether values must be taken from a specified controlled vocabulary or can be author-supplied, derived from text, or added by metadata creators working without a controlled term list
-
-
11 Oct 13
-
08 Oct 13
-
09 Jan 13
-
11 Sep 12
violet ladyragnellChan, L.M. & Zeng, M.L. (2006). Metadata Interoperability and Standardization – A Study of Methodology Part I: Achieving Interoperability at the Schema Level. D-Lib Magazine, 12 (6). Retrieved May 15, 2012,
-
10 Nov 11
-
13 Jun 11
-
From a methodological point of view, implementing interoperability may be considered at different levels of operation: schema level, record level, and repository level.
-
"Interoperability is the ability of multiple systems with different hardware and software platforms, data structures, and interfaces to exchange data with minimal loss of content and functionality" [NISO, 2004].
"Interoperability is the ability of two or more systems or components to exchange information and use the exchanged information without special effort on either system" [CC:DA, 2000].
"Interoperability: The compatibility of two or more systems such that they can exchange information and data and can use the exchanged information and data without any special manipulation" [Taylor 2004, p. 369].
-
- A schema was created and applied to records for one or more particular projects.
- Elements from several schemas were considered. An application profile was established based on a number of schemas; then, the element set specified by the application profile was applied to records of particular project(s).
- Two or more existing databases containing metadata records were exchanged or integrated based on the matching elements of the schemas involved.
- Records from existing metadata collections were harvested or merged by a unified repository. These collections had applied different schemas or established their own application profiles before the harvesting.
-
- Schema level – Efforts are focused on the elements of the schemas, being independent of any applications. The results usually appear as derived element sets or encoded schemas, crosswalks, application profiles, and element registries.
- Record level – Efforts are intended to integrate the metadata records through the mapping of the elements according to the semantic meanings of these elements. Common results include converted records and new records resulting from combining values of existing records.
- Repository level – With harvested or integrated records from varying sources, efforts at this level focus on mapping value strings associated with particular elements (e.g., terms associated with subject or format elements). The results enable cross-collection searching.
It should be noted that the models to be discussed in this article are not always mutually exclusive. Sometimes, within a particular project, more than one method may be used.
-
- a semantic definition of each metadata element;
- whether or not a metadata element is mandatory, optional, or mandatory based on certain conditions;
- whether or not a metadata element may occur multiple times in the same record;
- constraints due to the organization of metadata elements relative to each other, e.g., hierarchical parent-child relationships;
- constraints imposed on the value of an element (e.g., free text, numeric range, date, or a controlled vocabulary); and
- optional support for locally defined metadata elements.
The predominant method used in crosswalking is direct mapping or establishing equivalency among elements in different schemas. Metadata "mapping" refers to a formal identification of equivalent or nearly equivalent metadata elements or groups of metadata elements from different metadata schemas, carried out in order to facilitate semantic interoperability [Baca et al., 2000]. Quite a few metadata properties need to be brought into consideration in the mapping. According to the NISO document Issues in Crosswalking Content Metadata Standards [St. Pierre and LaPlant, 1998], common properties may include:
-
The relative crosswalking approach appears to work better when mapping from complex to simpler schema (e.g., from MARC to DC, but not vice versa).
-
In the open, networked environment that encompasses multiple user communities using a multitude of standards for description of digital resources, the need for interoperability among metadata schemas is paramount. To enable federated searches and to facilitate metadata management, much effort has been devoted to achieving or improving interoperability among metadata records. As discussed in this article, efforts to improve interoperability can take place at different levels – schema, record, and repository levels.
-
-
10 Jun 11
-
08 Sep 10
-
08 May 10
-
04 Nov 09
-
16 Jul 09
-
23 Jun 09
-
21 Jun 09
-
26 Sep 08
-
23 Aug 08
-
05 Feb 08
-
From a methodological point of view, implementing interoperability may be considered at different levels of operation: schema level, record level, and repository level.
-
- Semantics – definitions of the meanings of the elements and their refinements.
- Content – declarations or instructions of what and how values should be assigned to the elements.
A metadata element set has two basic components:
-
"Interoperability is the ability of multiple systems with different hardware and software platforms, data structures, and interfaces to exchange data with minimal loss of content and functionality"
-
It is becoming generally accepted in the information community that interoperability is one of the most important principles in metadata implementation. Other basic metadata principles include simplicity, modularity, reusability, and extensibility [Duval et al., 2002; Zeng et al., 2003]. These principles inform metadata database design as well as other system-dependent developments. From the very beginning of a metadata project, the principles that enable user-centered and interoperable services should be foremost in design and implementation.
-
-
30 Nov 06
-
03 Sep 06
-
27 Aug 06
-
The rapid growth of Internet resources and digital collections has been accompanied by a proliferation of metadata schemas, each of which has been designed based on the requirements of particular user communities, intended users, types of materials, subject domains, project needs, etc. Problems arise when building large digital libraries or repositories with metadata records that were prepared according to diverse schemas. This article (published in two parts) contains an analysis of the methods that have been used to achieve or improve interoperability among metadata schemas and applications, for the purposes of facilitating conversion and exchange of metadata and enabling 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, record level, and repository level. Part I of the article intends to explain possible situations in which metadata schemas may be created or implemented, whether in individual projects or in integrated repositories. It also discusses approaches used at the schema level. Part II of the article will discuss metadata interoperability efforts at the record and repository levels.
-
-
15 Aug 06
-
31 Jul 06
-
19 Jul 06
-
23 Jun 06
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.