Search (1598 results, page 1 of 80)

0.15031722 = product of:
  0.30063444 = sum of:
    0.30063444 = sum of:
      0.25911155 = weight(_text_:core in 1087) [ClassicSimilarity], result of:
        0.25911155 = score(doc=1087,freq=18.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          1.0044112 = fieldWeight in 1087, product of:
            4.2426405 = tf(freq=18.0), with freq of:
              18.0 = termFreq=18.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.046875 = fieldNorm(doc=1087)
      0.04152288 = weight(_text_:22 in 1087) [ClassicSimilarity], result of:
        0.04152288 = score(doc=1087,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.23214069 = fieldWeight in 1087, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046875 = fieldNorm(doc=1087)
  0.5 = coord(1/2)

Abstract

The Core Standard for Rare Books, known as the DCRB Core standard, was approved by the Program for Cooperative Cataloging for use beginning in January 1999. Comparable to the core standards for other types of materials, the DCRB Core standard provides requirements for an intermediate level of bibliographic description for the cataloging of rare books. While the Core Standard for Books seems to have found a place in general cataloging practice, the DCRB Core standard appears to have met with resistance among rare book cataloging practitioners. This study investigates the extent to which such resistance exists by examining all of the DCRB Core records in the OCLC (Online Computer Library Center) Online Union Catalog (WorldCat) and the Research Libraries Croup Union Catalog (RLIN) databases that were created during the standard's first five years. The study analyzes the content of the records for adherence to the standard and investigates the ways in which the flexibility of the standard and cataloger's judgment augmented many records with more than the mandatory elements of description and access.

Date

10. 9.2000 17:38:22

Object

DCRB Core standard

0.12526436 = product of:
  0.25052872 = sum of:
    0.25052872 = sum of:
      0.21592632 = weight(_text_:core in 153) [ClassicSimilarity], result of:
        0.21592632 = score(doc=153,freq=18.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.83700943 = fieldWeight in 153, product of:
            4.2426405 = tf(freq=18.0), with freq of:
              18.0 = termFreq=18.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.0390625 = fieldNorm(doc=153)
      0.0346024 = weight(_text_:22 in 153) [ClassicSimilarity], result of:
        0.0346024 = score(doc=153,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.19345059 = fieldWeight in 153, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0390625 = fieldNorm(doc=153)
  0.5 = coord(1/2)

Abstract

In January 1999, the Program for Cooperative Cataloging approved the core bibliographic standard for rare books, called the DCRB Core standard. Like the other core standards, the DCRB Core provides the framework within which catalogers can create bibliographic records that are less than full, but are as reliable as full-level records in description and authorized headings. In the three years since its approval, there is little evidence that the standard has been widely used. This study reports the results of a survey sent to forty-three participants who indicated in a preliminary query that they do use the DCRB Core or that they have made the decision not to use it. In the thirty-seven surveys that were returned, only about 16% of the respondents said they have used the standard to create bibliographic records for their rare books. The libraries that do not use the core standard find it inferior or lacking in a number of ways. Several of those libraries, however, are planning to use the standard in the future or are seriously planning to investigate using it. Such intent may indicate that the time is approaching when more libraries will find reasons to implement the standard. One impetus may come from the findings of a recent survey of the special collections departments of member libraries of the Association of Research Libraries that emphasize the size of the backlogs in those departments. If faster accessibility to specific portions of the backlogs would benefit users more than having fulllevel cataloging, application of the DCRB Core standard could facilitate reducing those backlogs.

Date

10. 9.2000 17:38:22

Object

DCRB Core standard

0.11148728 = product of:
  0.22297455 = sum of:
    0.22297455 = sum of:
      0.17453119 = weight(_text_:core in 637) [ClassicSimilarity], result of:
        0.17453119 = score(doc=637,freq=6.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.67654675 = fieldWeight in 637, product of:
            2.4494898 = tf(freq=6.0), with freq of:
              6.0 = termFreq=6.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.0546875 = fieldNorm(doc=637)
      0.04844336 = weight(_text_:22 in 637) [ClassicSimilarity], result of:
        0.04844336 = score(doc=637,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.2708308 = fieldWeight in 637, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0546875 = fieldNorm(doc=637)
  0.5 = coord(1/2)

Abstract

In an interview, Diane I. Hillmann, an expert in metadata for digital libraries and currently co-principal investigator for the National Science Digital Library Registry based at Cornell University, discusses her education and career, and provides overviews and insights on metadata initiatives, including standards and models such as the widely adopted Dublin Core schema. She shares her professional interests from the early part of her career with communications, cataloging, and database production services; highlights key issues; and provides ideas and resources for managing changes in metadata standards and digital projects.

Date

2.12.2007 19:35:22

Object

Dublic Core

0.10713197 = product of:
  0.21426395 = sum of:
    0.21426395 = sum of:
      0.17274107 = weight(_text_:core in 2634) [ClassicSimilarity], result of:
        0.17274107 = score(doc=2634,freq=8.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.6696076 = fieldWeight in 2634, product of:
            2.828427 = tf(freq=8.0), with freq of:
              8.0 = termFreq=8.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.046875 = fieldNorm(doc=2634)
      0.04152288 = weight(_text_:22 in 2634) [ClassicSimilarity], result of:
        0.04152288 = score(doc=2634,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.23214069 = fieldWeight in 2634, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046875 = fieldNorm(doc=2634)
  0.5 = coord(1/2)

Abstract

This report introduces the Dublin Core Microformats (DCMF) project, a new way to use the DC element set within X/HTML. The DC microformats encode explicit semantic expressions in an X/HTML webpage, by using a specific list of terms for values of the attributes "rev" and "rel" for <a> and <link> elements, and "class" and "id" of other elements. Microformats can be easily processed by user agents and software, enabling a high level of interoperability. These characteristics are crucial for the growing number of social applications allowing users to participate in the Web 2.0 environment as information creators and consumers. This report reviews the origins of microformats; illustrates the coding of DC microformats using the Dublin Core Metadata Gen tool, and a Firefox extension for extraction and visualization; and discusses the benefits of creating Web services utilizing DC microformats.

Object

Dublin Core Microformats

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.10545276 = product of:
  0.21090552 = sum of:
    0.21090552 = sum of:
      0.17630312 = weight(_text_:core in 2651) [ClassicSimilarity], result of:
        0.17630312 = score(doc=2651,freq=12.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.6834154 = fieldWeight in 2651, product of:
            3.4641016 = tf(freq=12.0), with freq of:
              12.0 = termFreq=12.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.0390625 = fieldNorm(doc=2651)
      0.0346024 = weight(_text_:22 in 2651) [ClassicSimilarity], result of:
        0.0346024 = score(doc=2651,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.19345059 = fieldWeight in 2651, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0390625 = fieldNorm(doc=2651)
  0.5 = coord(1/2)

Abstract

The digitized version of the only extant copy of Archimedes' key mathematical and scientific works contains over 6,500 images and 130 pages of transcriptions. Metadata is essential for managing, integrating and accessing these digital resources in the Web 2.0 environment. The Dublin Core Metadata Element Set meets many of our needs. It offers the needed flexibility and applicability to a variety of data sets containing different texts and images in a dynamic technical environment. The program team has continued to refine its data dictionary and elements based on the Dublin Core standard and feedback from the Dublin Core community since the 2006 Dublin Core Conference. This presentation cites the application and utility of the DCMI Standards during the final phase of this decade-long program. Since the 2006 conference, the amount of data has grown tenfold with new imaging techniques. Use of the DCMI Standards for integration across digital images and transcriptions will allow the hosting and integration of this data set and other cultural works across service providers, libraries and cultural institutions.

Object

Dublin Core

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.1018882 = sum of:
  0.081126764 = product of:
    0.2433803 = sum of:
      0.2433803 = weight(_text_:3a in 562) [ClassicSimilarity], result of:
        0.2433803 = score(doc=562,freq=2.0), product of:
          0.43304712 = queryWeight, product of:
            8.478011 = idf(docFreq=24, maxDocs=44218)
            0.051078856 = queryNorm
          0.56201804 = fieldWeight in 562, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            8.478011 = idf(docFreq=24, maxDocs=44218)
            0.046875 = fieldNorm(doc=562)
    0.33333334 = coord(1/3)
  0.02076144 = product of:
    0.04152288 = sum of:
      0.04152288 = weight(_text_:22 in 562) [ClassicSimilarity], result of:
        0.04152288 = score(doc=562,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.23214069 = fieldWeight in 562, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046875 = fieldNorm(doc=562)
    0.5 = coord(1/2)

Content

Vgl.: http://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CEAQFjAA&url=http%3A%2F%2Fciteseerx.ist.psu.edu%2Fviewdoc%2Fdownload%3Fdoi%3D10.1.1.91.4940%26rep%3Drep1%26type%3Dpdf&ei=dOXrUMeIDYHDtQahsIGACg&usg=AFQjCNHFWVh6gNPvnOrOS9R3rkrXCNVD-A&sig2=5I2F5evRfMnsttSgFF9g7Q&bvm=bv.1357316858,d.Yms.

Date

8. 1.2013 10:22:32

0.097772196 = product of:
  0.19554439 = sum of:
    0.19554439 = sum of:
      0.16094199 = weight(_text_:core in 2649) [ClassicSimilarity], result of:
        0.16094199 = score(doc=2649,freq=10.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.62387 = fieldWeight in 2649, product of:
            3.1622777 = tf(freq=10.0), with freq of:
              10.0 = termFreq=10.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.0390625 = fieldNorm(doc=2649)
      0.0346024 = weight(_text_:22 in 2649) [ClassicSimilarity], result of:
        0.0346024 = score(doc=2649,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.19345059 = fieldWeight in 2649, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0390625 = fieldNorm(doc=2649)
  0.5 = coord(1/2)

Abstract

OCLC's Crosswalk Web Service (Godby, Smith and Childress, 2008) formalizes the notion of crosswalk, as defined in Gill,et al. (n.d.), by hiding technical details and permitting the semantic equivalences to emerge as the centerpiece. One outcome is that metadata experts, who are typically not programmers, can enter the translation logic into a spreadsheet that can be automatically converted into executable code. In this paper, we describe the implementation of the Dublin Core Terms application profile in the management of crosswalks involving MARC. A crosswalk that encodes an application profile extends the typical format with two columns: one that annotates the namespace to which an element belongs, and one that annotates a 'broader-narrower' relation between a pair of elements, such as Dublin Core coverage and Dublin Core Terms spatial. This information is sufficient to produce scripts written in OCLC's Semantic Equivalence Expression Language (or Seel), which are called from the Crosswalk Web Service to generate production-grade translations. With its focus on elements that can be mixed, matched, added, and redefined, the application profile (Heery and Patel, 2000) is a natural fit with the translation model of the Crosswalk Web Service, which attempts to achieve interoperability by mapping one pair of elements at a time.

Object

Dublin Core

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.09547374 = product of:
  0.19094747 = sum of:
    0.19094747 = sum of:
      0.14250411 = weight(_text_:core in 2631) [ClassicSimilarity], result of:
        0.14250411 = score(doc=2631,freq=4.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.5523981 = fieldWeight in 2631, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.0546875 = fieldNorm(doc=2631)
      0.04844336 = weight(_text_:22 in 2631) [ClassicSimilarity], result of:
        0.04844336 = score(doc=2631,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.2708308 = fieldWeight in 2631, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0546875 = fieldNorm(doc=2631)
  0.5 = coord(1/2)

Abstract

A technique for converting Library of Congress Subject Headings MARCXML to Simple Knowledge Organization System (SKOS) RDF is described. Strengths of the SKOS vocabulary are highlighted, as well as possible points for extension, and the integration of other semantic web vocabularies such as Dublin Core. An application for making the vocabulary available as linked data on the Web is also described.

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.09527188 = product of:
  0.19054376 = sum of:
    0.19054376 = sum of:
      0.16286184 = weight(_text_:core in 3271) [ClassicSimilarity], result of:
        0.16286184 = score(doc=3271,freq=16.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.6313121 = fieldWeight in 3271, product of:
            4.0 = tf(freq=16.0), with freq of:
              16.0 = termFreq=16.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.03125 = fieldNorm(doc=3271)
      0.02768192 = weight(_text_:22 in 3271) [ClassicSimilarity], result of:
        0.02768192 = score(doc=3271,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.15476047 = fieldWeight in 3271, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.03125 = fieldNorm(doc=3271)
  0.5 = coord(1/2)

Abstract

In this paper we investigate the scattering of journals and literature obsolescence reflected in more than 137,000 document delivery requests submitted to a national document delivery service. We first summarize the major findings of the study with regards to the performance of the service. We then identify the "core" journals from which article requests were satisfied and address the following research questions: (a) Does the distribution of (core) journals conform to the Bradford's Law of Scattering? (b) Is there a relationship between usage of journals and impact factors, journals with high impact factors being used more often than the rest? (c) Is there a relationship between usage of journals and total citation counts, journals with high total citation counts being used more often than the rest? (d) What is the median age of use (half-life) of requested articles in general? (e) Do requested articles that appear in core journals get obsolete more slowly? (f) Is there a relationship between obsolescence and journal impact factors, journals with high impact factors being obsolete more slowly? (g) Is there a relationship between obsolescence and total citation counts, journals with high total citation counts being obsolete more slowly? Based an the analysis of findings, we found that the distribution of highly and moderately used journal titles conform to Bradford's Law. The median age of use was 8 years for all requested articles. Ninety percent of the articles requested were 21 years of age or younger. Articles that appeared in 168 core journal titles seem to get obsolete slightly more slowly than those of all titles. We observed no statistically significant correlations between the frequency of journal use and ISI journal impact factors, and between the frequency of journal use and ISI- (Institute for Scientific Information, Philadelphia, PA) cited half-lives for the most heavily used 168 core journal titles. There was a weak correlation between usage of journals and ISI-reported total citation counts. No statistically significant relationship was found between median age of use and journal impact factors and between median age of use and total citation counts. There was a weak negative correlation between ISI journal impact factors and cited half-lives of 168 core journals, and a weak correlation between ISI citation halflives and use half-lives of core journals. No correlation was found between cited half-lives of 168 core journals and their corresponding total citation counts as reported by ISI. Findings of the current study are discussed along with those of other studies.

Date

20. 3.2005 10:54:22

0.09001261 = product of:
  0.18002522 = sum of:
    0.18002522 = sum of:
      0.1523433 = weight(_text_:core in 1236) [ClassicSimilarity], result of:
        0.1523433 = score(doc=1236,freq=14.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.5905384 = fieldWeight in 1236, product of:
            3.7416575 = tf(freq=14.0), with freq of:
              14.0 = termFreq=14.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.03125 = fieldNorm(doc=1236)
      0.02768192 = weight(_text_:22 in 1236) [ClassicSimilarity], result of:
        0.02768192 = score(doc=1236,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.15476047 = fieldWeight in 1236, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.03125 = fieldNorm(doc=1236)
  0.5 = coord(1/2)

Abstract

Dublin Core is often presented as a modern form of catalog card -- a set of elements (and now qualifiers) that describe resources in a complete package. Sometimes it is proposed as an exchange format for sharing records among multiple collections. The founding principle that "every element is optional and repeatable" reinforces the notion that a Dublin Core description is to be taken as a whole. This paper, in contrast, is based on a much different premise: Dublin Core is a language. More precisely, it is a small language for making a particular class of statements about resources. Like natural languages, it has a vocabulary of word-like terms, the two classes of which -- elements and qualifiers -- function within statements like nouns and adjectives; and it has a syntax for arranging elements and qualifiers into statements according to a simple pattern. Whenever tourists order a meal or ask directions in an unfamiliar language, considerate native speakers will spontaneously limit themselves to basic words and simple sentence patterns along the lines of "I am so-and-so" or "This is such-and-such". Linguists call this pidginization. In such situations, a small phrase book or translated menu can be most helpful. By analogy, today's Web has been called an Internet Commons where users and information providers from a wide range of scientific, commercial, and social domains present their information in a variety of incompatible data models and description languages. In this context, Dublin Core presents itself as a metadata pidgin for digital tourists who must find their way in this linguistically diverse landscape. Its vocabulary is small enough to learn quickly, and its basic pattern is easily grasped. It is well-suited to serve as an auxiliary language for digital libraries. This grammar starts by defining terms. It then follows a 200-year-old tradition of English grammar teaching by focusing on the structure of single statements. It concludes by looking at the growing dictionary of Dublin Core vocabulary terms -- its registry, and at how statements can be used to build the metadata equivalent of paragraphs and compositions -- the application profile.

Date

26.12.2011 14:01:22

Object

Dublin Core

0.08927664 = product of:
  0.17855328 = sum of:
    0.17855328 = sum of:
      0.14395088 = weight(_text_:core in 2624) [ClassicSimilarity], result of:
        0.14395088 = score(doc=2624,freq=8.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.5580063 = fieldWeight in 2624, product of:
            2.828427 = tf(freq=8.0), with freq of:
              8.0 = termFreq=8.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.0390625 = fieldNorm(doc=2624)
      0.0346024 = weight(_text_:22 in 2624) [ClassicSimilarity], result of:
        0.0346024 = score(doc=2624,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.19345059 = fieldWeight in 2624, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0390625 = fieldNorm(doc=2624)
  0.5 = coord(1/2)

Abstract

This paper describes the information properties of museum specimen labels and machine learning tools to automatically extract Darwin Core (DwC) and other metadata from these labels processed through Optical Character Recognition (OCR). The DwC is a metadata profile describing the core set of access points for search and retrieval of natural history collections and observation databases. Using the HERBIS Learning System (HLS) we extract 74 independent elements from these labels. The automated text extraction tools are provided as a web service so that users can reference digital images of specimens and receive back an extended Darwin Core XML representation of the content of the label. This automated extraction task is made more difficult by the high variability of museum label formats, OCR errors and the open class nature of some elements. In this paper we introduce our overall system architecture, and variability robust solutions including, the application of Hidden Markov and Naïve Bayes machine learning models, data cleaning, use of field element identifiers, and specialist learning models. The techniques developed here could be adapted to any metadata extraction situation with noisy text and weakly ordered elements.

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.087265596 = product of:
  0.17453119 = sum of:
    0.17453119 = product of:
      0.34906238 = sum of:
        0.34906238 = weight(_text_:core in 4879) [ClassicSimilarity], result of:
          0.34906238 = score(doc=4879,freq=6.0), product of:
            0.25797358 = queryWeight, product of:
              5.0504966 = idf(docFreq=769, maxDocs=44218)
              0.051078856 = queryNorm
            1.3530935 = fieldWeight in 4879, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              5.0504966 = idf(docFreq=769, maxDocs=44218)
              0.109375 = fieldNorm(doc=4879)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Konferenzbericht des 7. Dublin core Workshop 1999 in Frankfurt an Main

Object

Dublin Core

0.087265596 = product of:
  0.17453119 = sum of:
    0.17453119 = product of:
      0.34906238 = sum of:
        0.34906238 = weight(_text_:core in 188) [ClassicSimilarity], result of:
          0.34906238 = score(doc=188,freq=6.0), product of:
            0.25797358 = queryWeight, product of:
              5.0504966 = idf(docFreq=769, maxDocs=44218)
              0.051078856 = queryNorm
            1.3530935 = fieldWeight in 188, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              5.0504966 = idf(docFreq=769, maxDocs=44218)
              0.109375 = fieldNorm(doc=188)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Footnote

Übers. des Titels: Internet - Metadata - Dublin Core

Object

Dublin Core

0.08680016 = product of:
  0.17360032 = sum of:
    0.17360032 = sum of:
      0.12466513 = weight(_text_:core in 2652) [ClassicSimilarity], result of:
        0.12466513 = score(doc=2652,freq=6.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.48324767 = fieldWeight in 2652, product of:
            2.4494898 = tf(freq=6.0), with freq of:
              6.0 = termFreq=6.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.0390625 = fieldNorm(doc=2652)
      0.048935182 = weight(_text_:22 in 2652) [ClassicSimilarity], result of:
        0.048935182 = score(doc=2652,freq=4.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.27358043 = fieldWeight in 2652, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0390625 = fieldNorm(doc=2652)
  0.5 = coord(1/2)

Object

Dublin Core

Pages

S.14-22

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.085262276 = product of:
  0.17052455 = sum of:
    0.17052455 = sum of:
      0.11516071 = weight(_text_:core in 7411) [ClassicSimilarity], result of:
        0.11516071 = score(doc=7411,freq=2.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.44640505 = fieldWeight in 7411, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.0625 = fieldNorm(doc=7411)
      0.05536384 = weight(_text_:22 in 7411) [ClassicSimilarity], result of:
        0.05536384 = score(doc=7411,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.30952093 = fieldWeight in 7411, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0625 = fieldNorm(doc=7411)
  0.5 = coord(1/2)

Abstract

- Formal characterization given to the thesaurus mapping problem - Interopearbility workflow - - Thesauri SKOS Core transformation - - Thesaurus Mapping algorithms implementation - The "gold standard" data set and the THALEN application - Thesaurus interoperability assessment measures - Experimental results

Date

7.11.2008 10:40:22

0.085262276 = product of:
  0.17052455 = sum of:
    0.17052455 = sum of:
      0.11516071 = weight(_text_:core in 2629) [ClassicSimilarity], result of:
        0.11516071 = score(doc=2629,freq=2.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.44640505 = fieldWeight in 2629, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.0625 = fieldNorm(doc=2629)
      0.05536384 = weight(_text_:22 in 2629) [ClassicSimilarity], result of:
        0.05536384 = score(doc=2629,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.30952093 = fieldWeight in 2629, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0625 = fieldNorm(doc=2629)
  0.5 = coord(1/2)

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.08183463 = product of:
  0.16366926 = sum of:
    0.16366926 = sum of:
      0.122146375 = weight(_text_:core in 4458) [ClassicSimilarity], result of:
        0.122146375 = score(doc=4458,freq=4.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.47348404 = fieldWeight in 4458, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.046875 = fieldNorm(doc=4458)
      0.04152288 = weight(_text_:22 in 4458) [ClassicSimilarity], result of:
        0.04152288 = score(doc=4458,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.23214069 = fieldWeight in 4458, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046875 = fieldNorm(doc=4458)
  0.5 = coord(1/2)

Date

12. 3.2000 19:25:22

Object

Dublin core

0.08183463 = product of:
  0.16366926 = sum of:
    0.16366926 = sum of:
      0.122146375 = weight(_text_:core in 2556) [ClassicSimilarity], result of:
        0.122146375 = score(doc=2556,freq=4.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.47348404 = fieldWeight in 2556, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.046875 = fieldNorm(doc=2556)
      0.04152288 = weight(_text_:22 in 2556) [ClassicSimilarity], result of:
        0.04152288 = score(doc=2556,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.23214069 = fieldWeight in 2556, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046875 = fieldNorm(doc=2556)
  0.5 = coord(1/2)

Abstract

First generation scholarly research on the Web lacked a firm system of authority control. Second generation Web research is beginning to model subject access with library science principles of bibliographic control and cataloguing. Harnessing the Web and organising the intellectual content with standards and controlled vocabulary provides precise search and retrieval capability, increasing relevance and efficient use of technology. Dublin Core metadata standards permit a full evaluation and cataloguing of Web resources appropriate to highly specific research needs and discovery. Current research points to a type of structure based on a system of faceted classification. This system allows the semantic and syntactic relationships to be defined. Controlled vocabulary, such as the Library of Congress Subject Headings, can be assigned, not in a hierarchical structure, but rather as descriptive facets of relating concepts. Web design features such as this are adding value to discovery and filtering out data that lack authority. The system design allows for scalability and extensibility, two technical features that are integral to future development of the digital library and resource discovery.

Date

30.12.2008 18:22:46

Object

Dublin Core

0.08183463 = product of:
  0.16366926 = sum of:
    0.16366926 = sum of:
      0.122146375 = weight(_text_:core in 2623) [ClassicSimilarity], result of:
        0.122146375 = score(doc=2623,freq=4.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.47348404 = fieldWeight in 2623, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.046875 = fieldNorm(doc=2623)
      0.04152288 = weight(_text_:22 in 2623) [ClassicSimilarity], result of:
        0.04152288 = score(doc=2623,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.23214069 = fieldWeight in 2623, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046875 = fieldNorm(doc=2623)
  0.5 = coord(1/2)

Object

Dublin Core

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.07821775 = product of:
  0.1564355 = sum of:
    0.1564355 = sum of:
      0.12875359 = weight(_text_:core in 2664) [ClassicSimilarity], result of:
        0.12875359 = score(doc=2664,freq=10.0), product of:
          0.25797358 = queryWeight, product of:
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.051078856 = queryNorm
          0.49909604 = fieldWeight in 2664, product of:
            3.1622777 = tf(freq=10.0), with freq of:
              10.0 = termFreq=10.0
            5.0504966 = idf(docFreq=769, maxDocs=44218)
            0.03125 = fieldNorm(doc=2664)
      0.02768192 = weight(_text_:22 in 2664) [ClassicSimilarity], result of:
        0.02768192 = score(doc=2664,freq=2.0), product of:
          0.17886946 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051078856 = queryNorm
          0.15476047 = fieldWeight in 2664, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.03125 = fieldNorm(doc=2664)
  0.5 = coord(1/2)

Abstract

DISC-UK DataShare (2007-2009), a project led by the University of Edinburgh and funded by JISC (Joint Information Systems Committee, UK), arises from an existing consortium of academic data support professionals working in the domain of social science datasets (Data Information Specialists Committee-UK). We are working together across four universities with colleagues engaged in managing open access repositories for e-prints. Our project supports 'early adopter' academics who wish to openly share datasets and presents a model for depositing 'orphaned datasets' that are not being deposited in subject-domain data archives/centres. Outputs from the project are intended to help to demystify data as complex objects in repositories, and assist other institutional repository managers in overcoming barriers to incorporating research data. By building on lessons learned from recent JISC-funded data repository projects such as SToRe and GRADE the project will help realize the vision of the Digital Repositories Roadmap, e.g. the milestone under Data, "Institutions need to invest in research data repositories" (Heery and Powell, 2006). Application of appropriate metadata is an important area of development for the project. Datasets are not different from other digital materials in that they need to be described, not just for discovery but also for preservation and re-use. The GRADE project found that for geo-spatial datasets, Dublin Core metadata (with geo-spatial enhancements such as a bounding box for the 'coverage' property) was sufficient for discovery within a DSpace repository, though more indepth metadata or documentation was required for re-use after downloading. The project partners are examining other metadata schemas such as the Data Documentation Initiative (DDI) versions 2 and 3, used primarily by social science data archives (Martinez, 2008). Crosswalks from the DDI to qualified Dublin Core are important for describing research datasets at the study level (as opposed to the variable level which is largely out of scope for this project). DataShare is benefiting from work of of the DRIADE project (application profile development for evolutionary biology) (Carrier, et al, 2007), eBank UK (developed an application profile for crystallography data) and GAP (Geospatial Application Profile, in progress) in defining interoperable Dublin Core qualified metadata elements and their application to datasets for each partner repository. The solution devised at Edinburgh for DSpace will be covered in the poster.

Object

Dublin Core

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas