Search (5 results, page 1 of 1)

0.038397796 = product of:
  0.13439228 = sum of:
    0.04815084 = weight(_text_:libraries in 1177) [ClassicSimilarity], result of:
      0.04815084 = score(doc=1177,freq=4.0), product of:
        0.13401186 = queryWeight, product of:
          3.2850544 = idf(docFreq=4499, maxDocs=44218)
          0.04079441 = queryNorm
        0.35930282 = fieldWeight in 1177, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.2850544 = idf(docFreq=4499, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1177)
    0.08624143 = weight(_text_:case in 1177) [ClassicSimilarity], result of:
      0.08624143 = score(doc=1177,freq=4.0), product of:
        0.17934912 = queryWeight, product of:
          4.3964143 = idf(docFreq=1480, maxDocs=44218)
          0.04079441 = queryNorm
        0.48085782 = fieldWeight in 1177, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          4.3964143 = idf(docFreq=1480, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1177)
  0.2857143 = coord(2/7)

Abstract

The Michigan State University Libraries (MSUL) digital repository contains numerous collections of openly available material. Since 2016, the digital repository has been using Faceted Application of Subject Terminology (FAST) subject headings as its primary subject vocabulary in order to streamline faceting, display, and search. The MSUL FAST use case presents some challenges that are not addressed by existing MARC-focused FAST tools. This paper will outline the MSUL digital repository team's justification for including FAST headings in the digital repository as well as workflows for adding FAST headings to Metadata Object Description Schema (MODS) metadata, their maintenance, and utilization for discovery.

0.005896022 = product of:
  0.041272152 = sum of:
    0.041272152 = weight(_text_:libraries in 1165) [ClassicSimilarity], result of:
      0.041272152 = score(doc=1165,freq=4.0), product of:
        0.13401186 = queryWeight, product of:
          3.2850544 = idf(docFreq=4499, maxDocs=44218)
          0.04079441 = queryNorm
        0.30797386 = fieldWeight in 1165, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.2850544 = idf(docFreq=4499, maxDocs=44218)
          0.046875 = fieldNorm(doc=1165)
  0.14285715 = coord(1/7)

Abstract

University of Victoria Libraries has implemented faceted vocabularies, particularly FAST, in its digital collections platform (Vault). The process involved migrating a variety of standardized (pre-coordinated Library of Congress subject headings) and non-standardized metadata to conform to a URI-centric metadata application profile. The authors argue that faceted vocabularies and FAST have helped to create a robust and intuitive user navigation in the platform and allowed for an efficient and straightforward metadata creation process. Maintaining FAST as linked data within Vault has required putting in place some technical processes to keep URIs and textual labels up to date and solutions (FAST Updater) have been locally developed.

0.00486397 = product of:
  0.03404779 = sum of:
    0.03404779 = weight(_text_:libraries in 1163) [ClassicSimilarity], result of:
      0.03404779 = score(doc=1163,freq=2.0), product of:
        0.13401186 = queryWeight, product of:
          3.2850544 = idf(docFreq=4499, maxDocs=44218)
          0.04079441 = queryNorm
        0.25406548 = fieldWeight in 1163, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2850544 = idf(docFreq=4499, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1163)
  0.14285715 = coord(1/7)

Abstract

This paper is the result of a request from Library of Congress leadership to assess pre-coordinated versus post-coordinated subject cataloging. It argues that the disadvantages of pre-coordinated subject strings are perennial and continue to hinder progress, while the advantages of post-coordinated subject cataloging have expanded, resulting in new opportunities to serve the needs of catalogers and end users alike. The consequences of retaining pre-coordinated headings will have long-term impacts that heavily out-weigh the short-term challenges of transitioning to new cataloging practices. By implementing post-coordinated, faceted vocabularies, the Library of Congress will be investing in the future of libraries.

0.00486397 = product of:
  0.03404779 = sum of:
    0.03404779 = weight(_text_:libraries in 1176) [ClassicSimilarity], result of:
      0.03404779 = score(doc=1176,freq=2.0), product of:
        0.13401186 = queryWeight, product of:
          3.2850544 = idf(docFreq=4499, maxDocs=44218)
          0.04079441 = queryNorm
        0.25406548 = fieldWeight in 1176, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2850544 = idf(docFreq=4499, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1176)
  0.14285715 = coord(1/7)

Abstract

Digital repository migrations present a periodic opportunity to assess metadata quality and to perform strategic enhancements. Lafayette College Libraries implemented OCLC FAST (Faceted Application of Subject Terminology) for its digital image collections as part of a migration from multiple repositories to a single one built on the Samvera Hyrax open-source framework. Application of FAST has normalized subject headings across dissimilar collections in a way that tremendously improves descriptive consistency for staff and discoverability for end users. However, the process of applying FAST headings was complicated by several features of in-scope metadata as well as gaps in available controlled subject authorities.

0.0019739573 = product of:
  0.0138177 = sum of:
    0.0138177 = product of:
      0.0276354 = sum of:
        0.0276354 = weight(_text_:22 in 374) [ClassicSimilarity], result of:
          0.0276354 = score(doc=374,freq=2.0), product of:
            0.14285508 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04079441 = queryNorm
            0.19345059 = fieldWeight in 374, 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=374)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Date

24. 9.2021 12:22:02