Search (26 results, page 2 of 2)

0.0018875621 = product of:
  0.009437811 = sum of:
    0.009437811 = weight(_text_:a in 2987) [ClassicSimilarity], result of:
      0.009437811 = score(doc=2987,freq=6.0), product of:
        0.053464882 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046368346 = queryNorm
        0.17652355 = fieldWeight in 2987, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0625 = fieldNorm(doc=2987)
  0.2 = coord(1/5)

Abstract

Since around 2005 several striking attempts have been made to rethink the design of library catalogs in production systems; the North Carolina State University's (NCSU) Endeca catalog being a notable example. These developments are taking place just as the continued relevance of traditional cataloging is being questioned. This article examines the relationship of these new designs to evolving cataloging practice and the changing discovery environment.

Type

a

0.0018276243 = product of:
  0.009138121 = sum of:
    0.009138121 = weight(_text_:a in 3102) [ClassicSimilarity], result of:
      0.009138121 = score(doc=3102,freq=10.0), product of:
        0.053464882 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046368346 = queryNorm
        0.1709182 = fieldWeight in 3102, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046875 = fieldNorm(doc=3102)
  0.2 = coord(1/5)

Abstract

Dewey Decimal Classification has been used to organize materials owned by the three scientific libraries at the University of Pavia, and to allow integrated browsing in their union catalogue through SciGator, a home built web-based user interface. Classification acts as a bridge between collections located in different places and shelved according to different local schemes. Furthermore, cross-discipline relationships recorded in the system allow for expanded queries that increase recall. Advantages and possible improvements of such a system are discussed.

Type

a

0.0016683849 = product of:
  0.008341924 = sum of:
    0.008341924 = weight(_text_:a in 4307) [ClassicSimilarity], result of:
      0.008341924 = score(doc=4307,freq=12.0), product of:
        0.053464882 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046368346 = queryNorm
        0.15602624 = fieldWeight in 4307, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0390625 = fieldNorm(doc=4307)
  0.2 = coord(1/5)

Abstract

The construction and updating of indexing languages depend on the organization of their hierarchical structures in order to determine the classification of related terms and, above all, to allow a constant updating of vocabulary, a condition for knowledge evolution. The elaboration of an indexing language for online catalogs of libraries' networks is important considering the diversity and specificity of knowledge areas. From this perspective, the present paper reports on the work of a team of catalogers and researchers engaged in the construction of a hierarchical structure of an indexing language for an online catalog of a university library's network. The work on hierarchical structures began by defining the categories and subcategories that form the indexing language macrostructure by using the parameters of the Library of Congress Subject Headings , the National Library Terminology and the Vocabulary of the University of São Paulo Library's system. Throughout the stages of the elaboration process of the macrostructure, difficulties and improvements were observed and discussed. The results enabled the assessment of the hierarchical structures of the languages used in the organization of the superordinate and subordinate terms, which has contributed to the systematization of operational procedures contained in an indexing language manual for online catalogs of libraries.

Type

a

0.0016346768 = product of:
  0.008173384 = sum of:
    0.008173384 = weight(_text_:a in 309) [ClassicSimilarity], result of:
      0.008173384 = score(doc=309,freq=8.0), product of:
        0.053464882 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046368346 = queryNorm
        0.15287387 = fieldWeight in 309, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046875 = fieldNorm(doc=309)
  0.2 = coord(1/5)

Abstract

This paper describes a survey on how system vendors and libraries handled tagging in OPACs and discovery layers. Tags are user added subject metadata, also called folksonomies. This survey also investigated user behavior when they face the possibility to tag. The findings indicate that legacy/classic systems have no tagging capability. About 47% of the discovery tools provide tagging function. About 49% of the libraries that have a system with tagging capability have turned the tagging function on in their OPACs and discovery tools. Only 40% of the libraries that turned tagging on actually utilized user added subject metadata as access point to collections. Academic library users are less active in tagging than public library users.

Type

a

0.0016346768 = product of:
  0.008173384 = sum of:
    0.008173384 = weight(_text_:a in 2554) [ClassicSimilarity], result of:
      0.008173384 = score(doc=2554,freq=2.0), product of:
        0.053464882 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046368346 = queryNorm
        0.15287387 = fieldWeight in 2554, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.09375 = fieldNorm(doc=2554)
  0.2 = coord(1/5)

Type

a

0.0010897844 = product of:
  0.005448922 = sum of:
    0.005448922 = weight(_text_:a in 195) [ClassicSimilarity], result of:
      0.005448922 = score(doc=195,freq=2.0), product of:
        0.053464882 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046368346 = queryNorm
        0.10191591 = fieldWeight in 195, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0625 = fieldNorm(doc=195)
  0.2 = coord(1/5)

Type

a