Search (8 results, page 1 of 1)

0.009683615 = product of:
  0.04841807 = sum of:
    0.04841807 = weight(_text_:context in 3759) [ClassicSimilarity], result of:
      0.04841807 = score(doc=3759,freq=2.0), product of:
        0.17622331 = queryWeight, product of:
          4.14465 = idf(docFreq=1904, maxDocs=44218)
          0.04251826 = queryNorm
        0.27475408 = fieldWeight in 3759, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.14465 = idf(docFreq=1904, maxDocs=44218)
          0.046875 = fieldNorm(doc=3759)
  0.2 = coord(1/5)

Abstract

The entry provides an overview of the data content standard, Cataloging Cultural Objects (CCO), developed by the Visual Resources Association (VRA), and published in 2006 by the American Library Association (ALA). CCO fills a gap in the array of descriptive standards by providing guidelines for visual resources curators, museum documentation specialists, archivists, librarians, or anyone engaged in the documentation of works of art and architecture, objects of material culture, and their images. The entry begins by placing CCO within the context of object and visual image cataloging and the broader framework of data content standards. Following the organization of the guide, which is divided into three parts, General Guidelines, Elements, and Authorities, it summarizes the main features of CCO. Finally, it evaluates CCO in terms of its suitability for use by the metadata communities that form its intended audience, and its sustainability.

0.0065765786 = product of:
  0.03288289 = sum of:
    0.03288289 = product of:
      0.098648675 = sum of:
        0.098648675 = weight(_text_:29 in 4173) [ClassicSimilarity], result of:
          0.098648675 = score(doc=4173,freq=4.0), product of:
            0.14956595 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.04251826 = queryNorm
            0.6595664 = fieldWeight in 4173, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.09375 = fieldNorm(doc=4173)
      0.33333334 = coord(1/3)
  0.2 = coord(1/5)

Date

28.11.1999 13:32:29
27. 9.2005 14:29:52

0.00538205 = product of:
  0.02691025 = sum of:
    0.02691025 = weight(_text_:index in 1464) [ClassicSimilarity], result of:
      0.02691025 = score(doc=1464,freq=2.0), product of:
        0.18579477 = queryWeight, product of:
          4.369764 = idf(docFreq=1520, maxDocs=44218)
          0.04251826 = queryNorm
        0.14483857 = fieldWeight in 1464, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.369764 = idf(docFreq=1520, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1464)
  0.2 = coord(1/5)

Footnote

Rez. in: KO 34(2007) no.4, S. 264-265 (L.C. Howarth): "At a time when cataloguing code revision is continuing apace with the consolidation of the International Standard Bibliographic Description (ISBD), the drafting of RDA: Resource Description and Access, and the development of common principles for an international cataloguing code (International Meeting of Experts on an International Cataloguing Code [IME ICC]), the publication of a guide for cataloguing cultural objects is timely and purposeful. Compiling this data content standard on behalf of the Visual Resources Association, the five editors - with oversight from an advisory board - have divided the guide into three parts. Following a brief introduction outlining the purpose, intended audience, and scope and methodology for the publication, Part One, General Guidelines, explains both what the Cataloging Cultural Objects (CCO) guide is "a broad document that includes rules for formatting data, suggestions for required information, controlled vocabulary requirements, and display issues" (p. I) and is not "not a metadata element set per se" (p. 1). Part Two, Elements, is further divided into nine chapters dealing with one or more metadata elements, and describing the relationships between and among each element. Part Three, Authorities, discusses what elements to include in building authority records. A Selected Bibliography, Glossary, and Index, respectively, round out the guide.

0.0046599186 = product of:
  0.023299592 = sum of:
    0.023299592 = weight(_text_:system in 4289) [ClassicSimilarity], result of:
      0.023299592 = score(doc=4289,freq=2.0), product of:
        0.13391352 = queryWeight, product of:
          3.1495528 = idf(docFreq=5152, maxDocs=44218)
          0.04251826 = queryNorm
        0.17398985 = fieldWeight in 4289, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.1495528 = idf(docFreq=5152, maxDocs=44218)
          0.0390625 = fieldNorm(doc=4289)
  0.2 = coord(1/5)

Abstract

This article begins by presenting and discussing the distinction between record-oriented and pattern-oriented search. Examples or recordoriented (or item-oriented) questions include: "What (or how many, etc.) glass items made prior to 100 A.D. do we have in our collection?" and "How many paintings featuring dogs do we have that were painted during the 19th century, and who painted them?" Standard database systems are well suited to answering such questions, based on the data in, for example, a collections management system. Examples of pattern-oriented questions include: "How does the (apparent) productoin of glass objects vary over time between 400 B.C. and 100 A.D.?" and "What other animals are present in paintings with dogs (painted during the 19th century and in our collection)?" Standard database systems are not well suited to answering these sorts of questions, even though the basic data is properly stored in them. To answer pattern-oriented questions it is the accepted solution to transform the underlying (relational) data to what is called the data cube or cross tabulation form. We discuss how this can be done for non-numeric data, such as are found in museum collections and archives

0.0046599186 = product of:
  0.023299592 = sum of:
    0.023299592 = weight(_text_:system in 1951) [ClassicSimilarity], result of:
      0.023299592 = score(doc=1951,freq=2.0), product of:
        0.13391352 = queryWeight, product of:
          3.1495528 = idf(docFreq=5152, maxDocs=44218)
          0.04251826 = queryNorm
        0.17398985 = fieldWeight in 1951, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.1495528 = idf(docFreq=5152, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1951)
  0.2 = coord(1/5)

Abstract

Der Bestand eines Fernseharchivs gleicht auf dem ersten Blick einem Irrgarten. Täglich werden große Mengen an audiovisuellen Informationen über den Äther geschickt und gleichzeitig für eine eventuelle Wiederverwendung digital gespeichert. Die Herausforderung für jeden Archivar besteht darin, aus Millionen von Sendeminuten auf Anfrage möglichst schnell das passende Material zusammenzustellen. Mit diesem Problem befasste sich das EU-Projekt Primavera (Personalized Retrieval und Indexing of Media Assets in Virtual Environments for Real-Time Access). Die darin entwickelte Software testet der Österreichische Rundfunk in Wien seit einem Jahr. Sie wurde vom Fraunhofer-Institut für Integrierte Publikations- und Informationssysteme (IPSI) in Darmstadt, der tecmath AG in Kaiserslautern und dem Instituto Trentino Di Cultura (ITC) in Trient gemeinsam entworfen. Neuer Suchansatz Suchte ein Redakteur bisher in archivierten Sendungen, bestellte er schließlich mehrere, vermutlich passende Mitschnitte. Viele davon erweisen sich jedoch schnell als nutzlos. Nun kann man bereits am Bildschirm anhand von Schlüsselbildern - den Keyframes genannten Standbildern markanter Szenen - eine Vorauswahl treffen. Einzelne Zugriffe auf das System erfolgen über einen Web-Browser, wobei Suchergebnisse grafisch aufberei tet werden. Damit eine Suche erfolgreich ist, müssen die Archivbestände exakt klassifiziert sein. Mit einem Werkzeug namens Piclasso beschleunigt das Programm die Verschlagwortung von bereits vorhandenen Filmen, indem es deren Klassifizierung sozusagen lernt und auf neu hinzukommendes Material automatisch anwendet. Der Archivar hat dabei aber jederzeit die Wahl, ob er einen Vorschlag übernimmt oder nicht. Zudem kann der Nutzer nicht nurtext-, sondern auch bildbezogen suchen.

0.0023251716 = product of:
  0.011625858 = sum of:
    0.011625858 = product of:
      0.034877572 = sum of:
        0.034877572 = weight(_text_:29 in 2827) [ClassicSimilarity], result of:
          0.034877572 = score(doc=2827,freq=2.0), product of:
            0.14956595 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.04251826 = queryNorm
            0.23319192 = fieldWeight in 2827, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.046875 = fieldNorm(doc=2827)
      0.33333334 = coord(1/3)
  0.2 = coord(1/5)

Date

10. 5.2009 17:29:18

0.001937643 = product of:
  0.009688215 = sum of:
    0.009688215 = product of:
      0.029064644 = sum of:
        0.029064644 = weight(_text_:29 in 2398) [ClassicSimilarity], result of:
          0.029064644 = score(doc=2398,freq=2.0), product of:
            0.14956595 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.04251826 = queryNorm
            0.19432661 = fieldWeight in 2398, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2398)
      0.33333334 = coord(1/3)
  0.2 = coord(1/5)

Date

2.12.2015 11:29:57

0.0015501144 = product of:
  0.0077505717 = sum of:
    0.0077505717 = product of:
      0.023251714 = sum of:
        0.023251714 = weight(_text_:29 in 2671) [ClassicSimilarity], result of:
          0.023251714 = score(doc=2671,freq=2.0), product of:
            0.14956595 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.04251826 = queryNorm
            0.15546128 = fieldWeight in 2671, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03125 = fieldNorm(doc=2671)
      0.33333334 = coord(1/3)
  0.2 = coord(1/5)

Date

29. 8.2004 19:05:56