Search (17 results, page 1 of 1)

0.018950384 = product of:
  0.07580154 = sum of:
    0.07580154 = weight(_text_:library in 5801) [ClassicSimilarity], result of:
      0.07580154 = score(doc=5801,freq=16.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.57517654 = fieldWeight in 5801, product of:
          4.0 = tf(freq=16.0), with freq of:
            16.0 = termFreq=16.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5801)
  0.25 = coord(1/4)

Abstract

Some international libraries are still using the Anglo-American Cataloging Rules, 2nd edition revised, for cataloging even though the Library of Congress and other large libraries have retired it in favor of Resource Description and Access. One of these libraries is the National Library of Greece, which consults the Library of Congress database before establishing authorities. There are cultural differences in names and subjects between the Library of Congress and the National Library, but some National Library terms may be more appropriate for users than the Library of Congress-established forms.

0.013399946 = product of:
  0.053599782 = sum of:
    0.053599782 = weight(_text_:library in 121) [ClassicSimilarity], result of:
      0.053599782 = score(doc=121,freq=8.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.40671125 = fieldWeight in 121, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0546875 = fieldNorm(doc=121)
  0.25 = coord(1/4)

Abstract

This article examines the motivations for the collaboration between the British Library and Library of Congress to develop a joint (Anglo-American) authority file. It describes the obstacles that had to be overcome for the British Library to become a Name Authority Cooperative (NACO) "copy holder", or node. It considers the contribution the British Library made to NACO, the benefits it has derived from participation in Program for Cooperative Cataloging (PCC), and concludes by looking ahead to the next 25 years.

0.011604695 = product of:
  0.04641878 = sum of:
    0.04641878 = weight(_text_:library in 696) [ClassicSimilarity], result of:
      0.04641878 = score(doc=696,freq=6.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.3522223 = fieldWeight in 696, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0546875 = fieldNorm(doc=696)
  0.25 = coord(1/4)

Abstract

Authority control enhances the accessibility of library resources by controlling the choice and form of access points, improving users' ability to efficiently find the works most relevant to their information search. While authority control and the technologies that support its implementation continue to evolve, the underlying principles and purposes remain the same. Written primarily for a new generation of librarians, this paper illuminates the importance of authority control in cataloging and library database management, discusses its history, describes current practices, and introduces readers to trends and issues in the field, including future applications beyond the library catalog.

0.009946881 = product of:
  0.039787523 = sum of:
    0.039787523 = weight(_text_:library in 5803) [ClassicSimilarity], result of:
      0.039787523 = score(doc=5803,freq=6.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.30190483 = fieldWeight in 5803, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.046875 = fieldNorm(doc=5803)
  0.25 = coord(1/4)

Abstract

In 2018, the national, bilingual authority file maintained by Library and Archives Canada (LAC), called Canadiana Authorities, underwent major changes when the internally-developed Integrated Library System (ILS) AMICUS was decommissioned and OCLC's WorldShare Management Services (WMS) was adopted as a replacement. As a part of the transition, LAC split its single, bilingual authority file Canadiana Authorities into separate English and French language files and joined Name Authority Cooperative Program (NACO) in order to manage its English-language authority records. This has been a significant change that has challenged the organization to rethink everyday practices while maintaining its commitments to the Canadian and global library community. This paper discusses this national library's history of bilingual cataloging, the reason for the changes, and the attempt to ensure that the two files "talk" to each other.

0.009475192 = product of:
  0.03790077 = sum of:
    0.03790077 = weight(_text_:library in 704) [ClassicSimilarity], result of:
      0.03790077 = score(doc=704,freq=4.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.28758827 = fieldWeight in 704, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0546875 = fieldNorm(doc=704)
  0.25 = coord(1/4)

Abstract

Controlled vocabularies are a foundational concept in library science and provide a framework for consistency in cataloging practices. Subject headings provide valuable access points to library resources during search and discovery for patrons. Many librarians will be familiar with the more widely used controlled vocabularies, like those maintained by national libraries or major professional organizations. More recently, there has been an increasing shift toward specialized vocabularies maintained by independent entities intended for much narrower use. While there is valid criticism of the nature or content of controlled vocabularies, they will likely continue to be an important feature in information organization.

0.009475192 = product of:
  0.03790077 = sum of:
    0.03790077 = weight(_text_:library in 1141) [ClassicSimilarity], result of:
      0.03790077 = score(doc=1141,freq=4.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.28758827 = fieldWeight in 1141, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1141)
  0.25 = coord(1/4)

Abstract

Bibliographic records can include information from controlled vocabularies to capture identities about individuals, especially about authors or intended audiences; personal name authority records can also contain information about identity. Employing a systematic analysis of the overlap of the Homosaurus, Library of Congress Subject Headings (LCSH), and Library of Congress Demographic Group Terms (LCDGT), this article explores the extent to which LGBTQ+ identities are represented in the three vocabularies. Despite LCSH's long, iterative history of development and the faceted, post-coordinate nature of LCDGT, neither vocabulary was found to be adequate in covering the complex, LGBTQ+ identities represented in the Homosaurus.

0.009475192 = product of:
  0.03790077 = sum of:
    0.03790077 = weight(_text_:library in 1154) [ClassicSimilarity], result of:
      0.03790077 = score(doc=1154,freq=4.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.28758827 = fieldWeight in 1154, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1154)
  0.25 = coord(1/4)

Abstract

We examined how data provenance and additional information of element values including nomens, and administrative information on the metadata should be modeled and represented in the Resource Description Framework (RDF) for linked data of library catalogs. First, we classified such information types into categories and organized the combination with recording-units, i.e., a description statement or description set. Next, we listed the appropriate RDF representation patterns for each recording-unit. Then, we reviewed the methods to examine such information in Resource Description and Access (RDA) in RDF, BIBFRAME, and Wikidata, and pointed out the issues involved in them.

0.008633038 = product of:
  0.034532152 = sum of:
    0.034532152 = product of:
      0.069064304 = sum of:
        0.069064304 = weight(_text_:project in 975) [ClassicSimilarity], result of:
          0.069064304 = score(doc=975,freq=2.0), product of:
            0.21156175 = queryWeight, product of:
              4.220981 = idf(docFreq=1764, maxDocs=44218)
              0.050121464 = queryNorm
            0.32644984 = fieldWeight in 975, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.220981 = idf(docFreq=1764, maxDocs=44218)
              0.0546875 = fieldNorm(doc=975)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

Entity management in a Linked Open Data (LOD) environment is a process of associating a unique, persistent, and dereferenceable Uniform Resource Identifier (URI) with a single entity. It allows data from various sources to be reused and connected to the Web. It can help improve data quality and enable more efficient workflows. This article describes a semi-automated entity management project conducted by the "Wikidata: WikiProject Chinese Culture and Heritage Group," explores the challenges and opportunities in describing Chinese women poets and historical places in Wikidata, the largest crowdsourcing LOD platform in the world, and discusses lessons learned and future opportunities.

0.008633038 = product of:
  0.034532152 = sum of:
    0.034532152 = product of:
      0.069064304 = sum of:
        0.069064304 = weight(_text_:project in 1142) [ClassicSimilarity], result of:
          0.069064304 = score(doc=1142,freq=2.0), product of:
            0.21156175 = queryWeight, product of:
              4.220981 = idf(docFreq=1764, maxDocs=44218)
              0.050121464 = queryNorm
            0.32644984 = fieldWeight in 1142, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.220981 = idf(docFreq=1764, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1142)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

This article outlines the early process and reflects on the experiences of the authors as members of a team creating a Hawaiian knowledge organization system. The authors put forward shared understanding as a process, not a goal, and a way to reimagine and elucidate the process of knowledge organization work. As the project has progressed, team members have embraced their work as not solely knowledge creation and organization, but also communication. The group has identified a metaphorical frame, community agreements, knowledge graphs, and authority record templates as communication tools that are critical to creating a shared space to discuss meaning.

0.006699973 = product of:
  0.026799891 = sum of:
    0.026799891 = weight(_text_:library in 5680) [ClassicSimilarity], result of:
      0.026799891 = score(doc=5680,freq=2.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.20335563 = fieldWeight in 5680, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5680)
  0.25 = coord(1/4)

Abstract

Authority control is an important part of cataloging since it helps provide consistent access to names, titles, subjects, and genre/forms. There are a variety of methods for providing authority control, ranging from manual, time-consuming processes to automated processes. However, the automated processes often seem out of reach for small libraries when it comes to using a pricey vendor or expert cataloger. This paper introduces ideas on how to handle authority control using a variety of tools, both paid and free. The author describes how their library handles authority control; compares vendors and programs that can be used to provide varying levels of authority control; and demonstrates authority control using MarcEdit.

0.006699973 = product of:
  0.026799891 = sum of:
    0.026799891 = weight(_text_:library in 5796) [ClassicSimilarity], result of:
      0.026799891 = score(doc=5796,freq=2.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.20335563 = fieldWeight in 5796, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5796)
  0.25 = coord(1/4)

Abstract

Local and regional authority files exist to cover gaps in national and international authority files. These types of authority files should not exist alone if they are going to be fully utilized by other institutions that may have resources about the same individuals or topics. This article discusses how the Western Name Authority File, a regional controlled vocabulary of personal names and corporate bodies, can link to larger authority files such as the Library of Congress Name Authority File and Wikidata. Workflows and issues encountered with linking this local authority file to larger authority files are discussed.

0.006699973 = product of:
  0.026799891 = sum of:
    0.026799891 = weight(_text_:library in 698) [ClassicSimilarity], result of:
      0.026799891 = score(doc=698,freq=2.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.20335563 = fieldWeight in 698, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0546875 = fieldNorm(doc=698)
  0.25 = coord(1/4)

Abstract

The concept of authorship is central to how libraries organize their collections. But libraries do not only collect resources created by individuals, they also collect documents issued by organizations. Library catalogers use the concept of a "corporate body" to treat organizations as authors for the purpose of making their documents discoverable to users. This essay looks at the key features of establishing authorized access points (AAPs) and applying authority control for corporate bodies. It examines how practices with regard to corporate bodies have changed over time and considers the changes catalogers might expect to see in the future.

0.006699973 = product of:
  0.026799891 = sum of:
    0.026799891 = weight(_text_:library in 1076) [ClassicSimilarity], result of:
      0.026799891 = score(doc=1076,freq=2.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.20335563 = fieldWeight in 1076, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1076)
  0.25 = coord(1/4)

Abstract

Authority data has always been at the core of library catalogues. Today, authority data is reference data on a wider scale. The former authorities of the "Sudoc" union catalogue mutated into "IdRef", a read/write platform of open data and services which seeks to become a national supplier of reliable identifiers for French universities. To support their dissemination and comply with high quality standards, Paprika and Qualinka have been added to our toolbox, to expedite the massive and secure linking of scientific publications to IdRef authorities.

0.0057428335 = product of:
  0.022971334 = sum of:
    0.022971334 = weight(_text_:library in 676) [ClassicSimilarity], result of:
      0.022971334 = score(doc=676,freq=2.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.17430481 = fieldWeight in 676, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.046875 = fieldNorm(doc=676)
  0.25 = coord(1/4)

Footnote

Beitrag in enem Themenheft 'Critical Library Perspectives'.

0.005093075 = product of:
  0.0203723 = sum of:
    0.0203723 = product of:
      0.0407446 = sum of:
        0.0407446 = weight(_text_:22 in 314) [ClassicSimilarity], result of:
          0.0407446 = score(doc=314,freq=2.0), product of:
            0.17551683 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050121464 = queryNorm
            0.23214069 = fieldWeight in 314, 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=314)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

23. 9.2021 19:12:22

0.004785695 = product of:
  0.01914278 = sum of:
    0.01914278 = weight(_text_:library in 367) [ClassicSimilarity], result of:
      0.01914278 = score(doc=367,freq=2.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.14525402 = fieldWeight in 367, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0390625 = fieldNorm(doc=367)
  0.25 = coord(1/4)

Abstract

Normdaten spielen speziell im Hinblick auf die Qualität der Inhaltserschließung bibliografischer und archivalischer Ressourcen eine wichtige Rolle. Ein konkretes Ziel der Inhaltserschließung ist z. B., dass alle Werke über Hermann Hesse einheitlich zu finden sind. Hier bieten Normdaten eine Lösung, indem z. B. bei der Erschließung einheitlich die GND-Nummer 11855042X für Hermann Hesse verwendet wird. Das Ergebnis ist eine höhere Qualität der Inhaltserschließung vor allem im Sinne von Einheitlichkeit und Eindeutigkeit und, daraus resultierend, eine bessere Auffindbarkeit. Werden solche Entitäten miteinander verknüpft, z. B. Hermann Hesse mit einem seiner Werke, entsteht ein Knowledge Graph, wie ihn etwa Google bei der Inhaltserschließung des Web verwendet (Singhal 2012). Die Entwicklung des Google Knowledge Graph und das hier vorgestellte Protokoll sind historisch miteinander verbunden: OpenRefine wurde ursprünglich als Google Refine entwickelt, und die Funktionalität zum Abgleich mit externen Datenquellen (Reconciliation) wurde ursprünglich zur Einbindung von Freebase entwickelt, einer der Datenquellen des Google Knowledge Graph. Freebase wurde später in Wikidata integriert. Schon Google Refine wurde zum Abgleich mit Normdaten verwendet, etwa den Library of Congress Subject Headings (Hooland et al. 2013).

0.0042442293 = product of:
  0.016976917 = sum of:
    0.016976917 = product of:
      0.033953834 = sum of:
        0.033953834 = weight(_text_:22 in 374) [ClassicSimilarity], result of:
          0.033953834 = score(doc=374,freq=2.0), product of:
            0.17551683 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050121464 = 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.25 = coord(1/4)

Date

24. 9.2021 12:22:02