Search results

An e‐mail survey was conducted by the Dublin Core Libraries Working Group to collect examples of Dublin Core use in libraries, and to provide input for the development of a Dublin Core application profile for libraries. A total of 29 responses were received from nine countries, describing 33 separate implementations of Dublin Core. The most commonly cited reasons for selecting Dublin Core were its international acceptance, flexibility and likelihood of future interoperability. Each of the 15 core elements was in use by between 59 percent and 97 percent of the projects in the survey. There was a high incidence (73 percent) of projects that use metadata elements in addition to the DC elements and approved qualifiers. The two most widely reported challenges involved in implementing Dublin Core were that there are too few elements and qualifiers, and the lack of usage guidelines.

The purpose of this paper is to employ a case study of the Omeka content management system to demonstrate how the adoption and implementation of a metadata standard (in this case, Dublin Core) can result in contrasting rhetorical arguments regarding metadata utility, quality, and reliability. In the Omeka example, the author illustrate a conceptual disconnect in how two metadata stakeholders – standards creators and standards users – operationalize metadata quality. For standards creators such as the Dublin Core community, metadata quality involves implementing a standard properly, according to established usage principles; in contrast, for standards users like Omeka, metadata quality involves mere adoption of the standard, with little consideration of proper usage and accompanying principles.

The paper uses an approach based on rhetorical criticism. The paper aims to establish whether Omeka’s given ends (the position that Omeka claims to take regarding Dublin Core) align with Omeka’s guiding ends (Omeka’s actual argument regarding Dublin Core). To make this assessment, the paper examines both textual evidence (what Omeka says) and material-discursive evidence (what Omeka does).

The evidence shows that, while Omeka appears to argue that adopting the Dublin Core is an integral part of Omeka’s mission, the platform’s lack of support for Dublin Core implementation makes an opposing argument. Ultimately, Omeka argues that the appearance of adopting a standard is more important than its careful implementation.

This study contributes to our understanding of how metadata standards are understood and used in practice. The misalignment between Omeka’s position and the goals of the Dublin Core community suggests that Omeka, and some portion of its users, do not value metadata interoperability and aggregation in the same way that the Dublin Core community does. This indicates that, although certain values regarding standards adoption may be pervasive in the metadata community, these values are not equally shared amongst all stakeholders in a digital library ecosystem. The way that standards creators (Dublin Core) understand what it means to “adopt a standard” is different from the way that standards users (Omeka) understand what it means to “adopt a standard.”

Among the newly developing metadata standards for the World Wide Web, Dublin Core Metadata Element Set (Dublin Core) is the pioneer in simple content description. There are various methods to deploy Dublin Core metadata, such as embedding it within a resource, linking it to a resource, or storing it in a database. This paper presents case studies of the deployment of Dublin Core at two significantly different institutions in Queensland, Australia. It aims to share experiences and ideas with those who are interested in deploying Dublin Core metadata. The two institutions are: State Library of Queensland, which demonstrates simple embedded metadata with minimum IT support; and Education Queensland, which utilizes a more complex metadata implementation within an Oracle database. Education Queensland also supplies its metadata to Education Network of Australia (EdNA), which collects metadata from all major Australian educational agencies and acts as an educational gateway.

Access to educational material has become an important issue for many stakeholders and the focus of much research worldwide. Resource discovery in educational gateways is usually based on metadata and this is an area of important developments. Resource metadata has a central role in the management of educational material and as a result there are several important metadata standards in use in the educational domain. One of the most widely used general metadata standards for learning material is the Dublin Core Metadata Element Set. The application of this general purpose, metadata standard for complex and heterogeneous educational material is not straightforward. This paper will give an overview of some practical issues and necessary steps in deploying Dublin Core based on the LITC experience in the EASEL (Educators Access to Services in the Electronic Landscape) project.

Library‐world “languages of description” are increasingly being expressed using the resource description framework (RDF) for compatibility with linked data approaches. This article aims to look at how issues around the Dublin Core, a small “metadata element set,” exemplify issues that must be resolved in order to ensure that library data meet traditional standards for quality and consistency while remaining broadly interoperable with other data sources in the linked data environment.

The article focuses on how the Dublin Core – originally seen, in traditional terms, as a simple record format – came increasingly to be seen as an RDF vocabulary for use in metadata based on a “statement” model, and how new approaches to metadata evolved to bridge the gap between these models.

The translation of library standards into RDF involves the separation of languages of description, per se, from the specific data formats into which they have for so long been embedded. When defined with “minimal ontological commitment,” languages of description lend themselves to the sort of adaptation that is inevitably a part of any human linguistic activity. With description set profiles, the quality and consistency of data traditionally required for sharing records among libraries can be ensured by placing precise constraints on the content of data records – without compromising the interoperability of the underlying vocabularies in the wider linked data context.

In today's environment, library data must continue to meet high standards of consistency and quality, yet it must be possible to link or merge the data with sources that follow other standards. Placing constraints on the data created, more than on the underlying vocabularies, allows both requirements to be met.

This paper examines how issues around the Dublin Core exemplify issues that must be resolved to ensure library data meet quality and consistency standards while remaining interoperable with other data sources.

To explore the impact of using metadata in finding and ranking web pages through search engines.

The study has been divided into two phases. In phase one, the use of metadata schemes and the impact of overlapped documents have been examined by employing the usability technique. Phase two examined the impact of adding metadata elements to web pages in their original rank order, using the experimental method. This study focuses on indexing web pages using metadata and its impact on search engine's rankings.

Meta tags are more widely used than Dublin Core. The overlapped pages tend to include metadata. The second phase shows that by adding metadata elements to web pages, it raises its rank order. However, this depends on the quality of the description and the metadata schemes. The study shows no great difference in page ranking between adding meta tags and Dublin Core.

To maximize the impact of metadata, more attention should be given to keyword and descriptive fields.

The hypothetical relationship between overlapped pages and the inclusion of metadata and indexing by search engines had not been previously examined.

The Dublin Core Metadata Standard was conceived illegitimately, had a troubled life, and has finally met its demise. Developed as a tool for online resource discovery, the standard waned after the arrival of Google. Because its fields were designed with a lack of specificity, Dublin Core suffered from nonstandard data elements and poor interoperability. Also, the poor organization behind the initiative contributed to its failure. Dublin Core will likely soon be replaced by an emerging standard, the Metadata Object Description Schema.

The International Conference on Dublin Core and Metadata Applications (DC‐2008) is being held this year in Berlin. The purpose of this paper is to describe the evolution of the Dublin Core effort from an initial focus on “core” elements for resource description towards a more comprehensive framework for developing application profiles that use multiple vocabularies on basis of the W3C resource description framework (RDF) model.

A Dublin Core application profile describes a metadata application, from functional requirements, via a domain model of entities to be described, to the formal specification of constraints on the basis of the DCMI Abstract Model.

Dublin Core application profiles are designed to be interoperable on the basis of W3C's RDF model and principles of Web architecture, such as consistent use of URIs, in order to facilitate the integration of metadata from multiple sources – a common requirement in today's Web.

The paper offers insights into the evolution of the Dublin Core.

This paper seeks to describe efforts in the area of converting bibliographic records into Dublin Core from the Common Communication Format.

The paper provides examples of two mappings, one for unqualified Dublin Core metadata elements, and the other for qualified Dublin Core metadata elements.

Some difficulties may occur during the conversion of bibliographic records, and these difficulties are stated along with possible solutions.

The paper provides a methodology which would enable an algorithm to be developed for converting CCF‐based bibliographic records into Dublin Core metadata elements.

The UK Office for Library and Information Networking are engaged in a wide range of work in the area of metadata, in cooperation with various partners. Projects on metadata for Internet resource discovery, interoperability and digital preservation all point to the continuing need for something like traditional library services to organise, access and preserve networked information.