Search (9 results, page 1 of 1)

0.0050892793 = product of:
  0.035624955 = sum of:
    0.035624955 = weight(_text_:management in 701) [ClassicSimilarity], result of:
      0.035624955 = score(doc=701,freq=2.0), product of:
        0.13666032 = queryWeight, product of:
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.04054466 = queryNorm
        0.2606825 = fieldWeight in 701, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.0546875 = fieldNorm(doc=701)
  0.14285715 = coord(1/7)

Abstract

Library catalogs remain challenging for children to use, especially because children have difficulty with multi-step processes, have less semantic and technical knowledge, and often search differently from adults. Child-friendly catalogs should have clear, simple protocols and visual guides that are standardized yet include flexible options for differentiated manipulation. Materials should be described accurately and in ways that connect meaningfully to children. More fundamentally, cataloging children's materials needs to be done in light of children as potential users and limitations of the integrated library management system itself. Getting children's feedback in the process can optimize the results.

0.0050892793 = product of:
  0.035624955 = sum of:
    0.035624955 = weight(_text_:management in 707) [ClassicSimilarity], result of:
      0.035624955 = score(doc=707,freq=2.0), product of:
        0.13666032 = queryWeight, product of:
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.04054466 = queryNorm
        0.2606825 = fieldWeight in 707, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.0546875 = fieldNorm(doc=707)
  0.14285715 = coord(1/7)

Abstract

This paper discusses the basics of creating name authority records for Arabic personal names in accordance with Resource Description and Access instructions and Program for Cooperative Cataloging guidelines. A background into the use of romanization for non-Latin scripts in bibliographic and authority records is provided to establish the context. Issues with romanization that are particular to Arabic are addressed. Separate sections on modern and classical names provide an overview of the major challenges, and strategies to enhance discovery are outlined. The paper concludes with an examination of the possible benefits of identity management and other changes in the authority control landscape for names in non-Latin script.

0.004851134 = product of:
  0.033957936 = sum of:
    0.033957936 = product of:
      0.06791587 = sum of:
        0.06791587 = weight(_text_:states in 1131) [ClassicSimilarity], result of:
          0.06791587 = score(doc=1131,freq=2.0), product of:
            0.22326207 = queryWeight, product of:
              5.506572 = idf(docFreq=487, maxDocs=44218)
              0.04054466 = queryNorm
            0.304198 = fieldWeight in 1131, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.506572 = idf(docFreq=487, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1131)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Abstract

Section 1 of this article discusses the concept of bibliographical control and makes a distinction between this term, "bibliographical description," and related terms, which are often confused in the literature. It further discusses the function of bibliographical control and criticizes Patrick Wilson's distinction between "exploitative control" and "descriptive control." Section 2 presents projects for establishing bibliographic control from the Library of Alexandria to the Internet and Google, and it is found that these projects have often been dominated by a positivist dream to make all information in the world available to everybody. Section 3 discusses the theoretical problems of providing comprehensive coverage and retrieving documents represented in databases and argues that 100% coverage and retrievability is an unobtainable ideal. It is shown that bibliographical control has been taken very seriously in the field of medicine, where knowledge of the most important findings is of utmost importance. In principle, it is equally important in all other domains. The conclusion states that the alternative to a positivist dream of complete bibliographic control is a pragmatic philosophy aiming at optimizing bibliographic control supporting specific activities, perspectives, and interests.

0.0036351997 = product of:
  0.025446396 = sum of:
    0.025446396 = weight(_text_:management in 5718) [ClassicSimilarity], result of:
      0.025446396 = score(doc=5718,freq=2.0), product of:
        0.13666032 = queryWeight, product of:
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.04054466 = queryNorm
        0.18620178 = fieldWeight in 5718, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5718)
  0.14285715 = coord(1/7)

Abstract

Persistent identifiers (PID's) are essential for getting access and referring to library, archive and museum (LAM) collection objects in a sustainable and unambiguous way, both internally and externally. Heritage institutions need a universal policy for the use of PID's in order to have an efficient digital infrastructure at their disposal and to achieve optimal interoperability, leading to open data, open collections and efficient resource management. Here the discussion is limited to PID's that institutions can assign to objects they own or administer themselves. PID's for people, subjects etc. can be used by heritage institutions, but are generally managed by other parties. The first part of this article consists of a general theoretical description of persistent identifiers. First of all, I discuss the questions of what persistent identifiers are and what they are not, and what is needed to administer and use them. The most commonly used existing PID systems are briefly characterized. Then I discuss the types of objects PID's can be assigned to. This section concludes with an overview of the requirements that apply if PIDs should also be used for linked data. The second part examines current infrastructural practices, and existing PID systems and their advantages and shortcomings. Based on these practical issues and the pros and cons of existing PID systems a list of requirements for PID systems is presented which is used to address a number of practical considerations. This section concludes with a number of recommendations.

0.0031389953 = product of:
  0.021972965 = sum of:
    0.021972965 = product of:
      0.04394593 = sum of:
        0.04394593 = weight(_text_:22 in 5749) [ClassicSimilarity], result of:
          0.04394593 = score(doc=5749,freq=2.0), product of:
            0.14198048 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04054466 = queryNorm
            0.30952093 = fieldWeight in 5749, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=5749)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Date

2. 3.2020 19:04:22

0.0025446396 = product of:
  0.017812477 = sum of:
    0.017812477 = weight(_text_:management in 717) [ClassicSimilarity], result of:
      0.017812477 = score(doc=717,freq=2.0), product of:
        0.13666032 = queryWeight, product of:
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.04054466 = queryNorm
        0.13034125 = fieldWeight in 717, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.02734375 = fieldNorm(doc=717)
  0.14285715 = coord(1/7)

Abstract

The circ stats say it all: graphic novels' popularity among library users keeps growing, with more being published (and acquired by libraries) each year. The unique challenges of developing and managing a graphics novels collection have led the Association of Library Collections and Technical Services (ALCTS) to craft this guide, presented under the expert supervision of editor Ballestro, who has worked with comics for more than 35 years. Examining the ever-changing ways that graphic novels are created, packaged, marketed, and released, this resource gathers a range of voices from the field to explore such topics as: a cultural history of comics and graphic novels from their World War II origins to today, providing a solid grounding for newbies and fresh insights for all; catching up on the Big Two's reboots: Marvel's 10 and DC's 4; five questions to ask when evaluating nonfiction graphic novels and 30 picks for a core collection; key publishers and cartoonists to consider when adding international titles; developing a collection that supports curriculum and faculty outreach to ensure wide usage, with catalogers' tips for organizing your collection and improving discovery; real-world examples of how libraries treat graphic novels, such as an in-depth profile of the development of Penn Library's Manga collection; how to integrate the emerging field of graphic medicine into the collection; and specialized resources like The Cartoonists of Color and Queer Cartoonists databases, the open access scholarly journal Comic Grid, and the No Flying, No Tights website. Packed with expert guidance and useful information, this guide will assist technical services staff, catalogers, and acquisition and collection management librarians.

0.0023542463 = product of:
  0.016479723 = sum of:
    0.016479723 = product of:
      0.032959446 = sum of:
        0.032959446 = weight(_text_:22 in 941) [ClassicSimilarity], result of:
          0.032959446 = score(doc=941,freq=2.0), product of:
            0.14198048 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04054466 = queryNorm
            0.23214069 = fieldWeight in 941, 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=941)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Date

22. 3.2023 12:00:14

0.001961872 = product of:
  0.013733104 = sum of:
    0.013733104 = product of:
      0.027466208 = sum of:
        0.027466208 = weight(_text_:22 in 5930) [ClassicSimilarity], result of:
          0.027466208 = score(doc=5930,freq=2.0), product of:
            0.14198048 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04054466 = queryNorm
            0.19345059 = fieldWeight in 5930, 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=5930)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Date

11. 7.2020 13:22:58

0.001961872 = product of:
  0.013733104 = sum of:
    0.013733104 = product of:
      0.027466208 = sum of:
        0.027466208 = weight(_text_:22 in 883) [ClassicSimilarity], result of:
          0.027466208 = score(doc=883,freq=2.0), product of:
            0.14198048 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04054466 = queryNorm
            0.19345059 = fieldWeight in 883, 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=883)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Date

22. 1.2023 18:40:36