Search (9 results, page 1 of 1)

0.0014474503 = product of:
  0.033291355 = sum of:
    0.033291355 = weight(_text_:im in 4421) [ClassicSimilarity], result of:
      0.033291355 = score(doc=4421,freq=2.0), product of:
        0.066621356 = queryWeight, product of:
          2.8267863 = idf(docFreq=7115, maxDocs=44218)
          0.023567878 = queryNorm
        0.49970993 = fieldWeight in 4421, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.8267863 = idf(docFreq=7115, maxDocs=44218)
          0.125 = fieldNorm(doc=4421)
  0.04347826 = coord(1/23)

Theme

Klassifikationssysteme im Online-Retrieval

0.0010855875 = product of:
  0.024968514 = sum of:
    0.024968514 = weight(_text_:im in 3008) [ClassicSimilarity], result of:
      0.024968514 = score(doc=3008,freq=2.0), product of:
        0.066621356 = queryWeight, product of:
          2.8267863 = idf(docFreq=7115, maxDocs=44218)
          0.023567878 = queryNorm
        0.37478244 = fieldWeight in 3008, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.8267863 = idf(docFreq=7115, maxDocs=44218)
          0.09375 = fieldNorm(doc=3008)
  0.04347826 = coord(1/23)

Theme

Klassifikationssysteme im Online-Retrieval

8.7507087E-4 = product of:
  0.010063315 = sum of:
    0.0019641288 = product of:
      0.0039282576 = sum of:
        0.0039282576 = weight(_text_:1 in 1166) [ClassicSimilarity], result of:
          0.0039282576 = score(doc=1166,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.06785194 = fieldWeight in 1166, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.01953125 = fieldNorm(doc=1166)
      0.5 = coord(1/2)
    0.008099186 = product of:
      0.016198372 = sum of:
        0.016198372 = weight(_text_:international in 1166) [ClassicSimilarity], result of:
          0.016198372 = score(doc=1166,freq=10.0), product of:
            0.078619614 = queryWeight, product of:
              3.33588 = idf(docFreq=4276, maxDocs=44218)
              0.023567878 = queryNorm
            0.20603475 = fieldWeight in 1166, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.33588 = idf(docFreq=4276, maxDocs=44218)
              0.01953125 = fieldNorm(doc=1166)
      0.5 = coord(1/2)
  0.08695652 = coord(2/23)

Abstract

This article presents an overview of the LEAF project (Linking and Exploring Authority Files)1, which has set out to provide a framework for international, collaborative work in the sector of authority data with respect to authority control. Elaborating the virtues of authority control in today's Web environment is an almost futile exercise, since so much has been said and written about it in the last few years.2 The World Wide Web is generally understood to be poorly structured-both with regard to content and to locating required information. Highly structured databases might be viewed as small islands of precision within this chaotic environment. Though the Web in general or any particular structured database would greatly benefit from increased authority control, it should be noted that our following considerations only refer to authority control with regard to databases of "memory institutions" (i.e., libraries, archives, and museums). Moreover, when talking about authority records, we exclusively refer to personal name authority records that describe a specific person. Although different types of authority records could indeed be used in similar ways to the ones presented in this article, discussing those different types is outside the scope of both the LEAF project and this article. Personal name authority records-as are all other "authorities"-are maintained as separate records and linked to various kinds of descriptive records. Name authority records are usually either kept in independent databases or in separate tables in the database containing the descriptive records. This practice points at a crucial benefit: by linking any number of descriptive records to an authorized name record, the records related to this entity are collocated in the database. Variant forms of the authorized name are referenced in the authority records and thus ensure the consistency of the database while enabling search and retrieval operations that produce accurate results. On one hand, authority control may be viewed as a positive prerequisite of a consistent catalogue; on the other, the creation of new authority records is a very time consuming and expensive undertaking. As a consequence, various models of providing access to existing authority records have emerged: the Library of Congress and the French National Library (Bibliothèque nationale de France), for example, make their authority records available to all via a web-based search service.3 In Germany, the Personal Name Authority File (PND, Personennamendatei4) maintained by the German National Library (Die Deutsche Bibliothek, Frankfurt/Main) offers a different approach to shared access: within a closed network, participating institutions have online access to their pooled data. The number of recent projects and initiatives that have addressed the issue of authority control in one way or another is considerable.5 Two important current initiatives should be mentioned here: The Name Authority Cooperative (NACO) and Virtual International Authority File (VIAF).
NACO was established in 1976 and is hosted by the Library of Congress. At the beginning of 2003, nearly 400 institutions were involved in this undertaking, including 43 institutions from outside the United States.6 Despite the enormous success of NACO and the impressive annual growth of the initiative, there are requirements for participation that form an obstacle for many institutions: they have to follow the Anglo-American Cataloguing Rules (AACR2) and employ the MARC217 data format. Participating institutions also have to belong to either OCLC (Online Computer Library Center) or RLG (Research Libraries Group) in order to be able to contribute records, and they have to provide a specified minimum number of authority records per year. A recent proof of concept project of the Library of Congress, OCLC and the German National Library-Virtual International Authority File (VIAF)8-will, in its first phase, test automatic linking of the records of the Library of Congress Name Authority File (LCNAF) and the German Personal Name Authority File by using matching algorithms and software developed by OCLC. The results are expected to form the basis of a "Virtual International Authority File". The project will then test the maintenance of the virtual authority file by employing the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH)9 to harvest the metadata for new, updated, and deleted records. When using the "Virtual International Authority File" a cataloguer will be able to check the system to see whether the authority record he wants to establish already exists. The final phase of the project will test possibilities for displaying records in the preferred language and script of the end user. Currently, there are still some clear limitations associated with the ways in which authority records are used by memory institutions. One of the main problems has to do with limited access: generally only large institutions or those that are part of a library network have unlimited online access to permanently updated authority records. Smaller institutions outside these networks usually have to fall back on less efficient ways of obtaining authority data, or have no access at all. Cross-domain sharing of authority data between libraries, archives, museums and other memory institutions simply does not happen at present. Public users are, by and large, not even aware that such things as name authority records exist and are excluded from access to these information resources.

7.356988E-4 = product of:
  0.016921071 = sum of:
    0.016921071 = weight(_text_:und in 763) [ClassicSimilarity], result of:
      0.016921071 = score(doc=763,freq=14.0), product of:
        0.052235067 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.023567878 = queryNorm
        0.32394084 = fieldWeight in 763, product of:
          3.7416575 = tf(freq=14.0), with freq of:
            14.0 = termFreq=14.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.0390625 = fieldNorm(doc=763)
  0.04347826 = coord(1/23)

Content

Vgl. Kommentar Eversberg: Wer dranbleiben will am Puls der Zeit und speziell an der sich dynamisierenden Evolution eines neuen Datenformatkonzepts, der sollte sich langsam beeilen, sich mit BIBFRAME vertraut zu machen: http://bibframe.org Diese Startseite organisiert nun den Zugang zu allem, was schon vorliegt und präsentabel ist, und das ist allerhand. Wer erst mal nur schnuppern will und schauen, wie denn BIBFRAME-Daten wohl aussehen, gehe zur "demonstration area", wo man u.a. auch aufbereitete Daten der DNB findet. Es gibt ferner Online Tools, und darunter einen "Transformation service", dem man eigenes MARC-XML übergeben kann, damit er was draus mache. [Exporte mit unserem MARCXML.APR klappen nicht unmittelbar, man muß zumindest die in der Datei schon vorhandenen zwei Kopfzeilen aktivieren und ans Ende noch </collection> setzen. Und hierarchische Daten machen noch Probleme, die wir uns vornehmen müssen.] Wer jetzt denkt, "Was geht uns das alles an?", der lese die letzte Zeile, die da lautet: "BIBFRAME.ORG is a collaborative effort of US Library of Congress, Zepheira and you!"

5.427938E-4 = product of:
  0.012484257 = sum of:
    0.012484257 = weight(_text_:im in 3967) [ClassicSimilarity], result of:
      0.012484257 = score(doc=3967,freq=2.0), product of:
        0.066621356 = queryWeight, product of:
          2.8267863 = idf(docFreq=7115, maxDocs=44218)
          0.023567878 = queryNorm
        0.18739122 = fieldWeight in 3967, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.8267863 = idf(docFreq=7115, maxDocs=44218)
          0.046875 = fieldNorm(doc=3967)
  0.04347826 = coord(1/23)

Content

Vortrag im Rahmen der Session 93. Cataloguing der WORLD LIBRARY AND INFORMATION CONGRESS: 76TH IFLA GENERAL CONFERENCE AND ASSEMBLY, 10-15 August 2010, Gothenburg, Sweden - 149. Information Technology, Cataloguing, Classification and Indexing with Knowledge Management

2.3911135E-4 = product of:
  0.005499561 = sum of:
    0.005499561 = product of:
      0.010999122 = sum of:
        0.010999122 = weight(_text_:1 in 5896) [ClassicSimilarity], result of:
          0.010999122 = score(doc=5896,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.18998542 = fieldWeight in 5896, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5896)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Journal of digital information. 1(2001) no.8

2.0495258E-4 = product of:
  0.0047139092 = sum of:
    0.0047139092 = product of:
      0.0094278185 = sum of:
        0.0094278185 = weight(_text_:1 in 5933) [ClassicSimilarity], result of:
          0.0094278185 = score(doc=5933,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.16284466 = fieldWeight in 5933, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.046875 = fieldNorm(doc=5933)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Journal of digital information. 1(2001) no.8

2.0495258E-4 = product of:
  0.0047139092 = sum of:
    0.0047139092 = product of:
      0.0094278185 = sum of:
        0.0094278185 = weight(_text_:1 in 2884) [ClassicSimilarity], result of:
          0.0094278185 = score(doc=2884,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.16284466 = fieldWeight in 2884, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.046875 = fieldNorm(doc=2884)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Abstract

OpenRefine is described as a tool for working with 'messy' data - but what does this mean? It is probably easiest to describe the kinds of data OpenRefine is good at working with and the sorts of problems it can help you solve. OpenRefine is most useful where you have data in a simple tabular format but with internal inconsistencies either in data formats, or where data appears, or in terminology used. It can help you: Get an overview of a data set Resolve inconsistencies in a data set Help you split data up into more granular parts Match local data up to other data sets Enhance a data set with data from other sources Some common scenarios might be: 1. Where you want to know how many times a particular value appears in a column in your data. 2. Where you want to know how values are distributed across your whole data set. 3. Where you have a list of dates which are formatted in different ways, and want to change all the dates in the list to a single common date format.

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 133) [ClassicSimilarity], result of:
          0.007856515 = score(doc=133,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 133, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=133)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Semantic Web journal. 3(2012) no.1, S.3-21