Search (196 results, page 1 of 10)

  • × theme_ss:"Formalerschließung"
  • × type_ss:"a"
  1. Shafer, K.E.: Mantis Project : A Toolkit for Cataloging (2001) 0.09
    0.094363734 = product of:
      0.18872747 = sum of:
        0.18872747 = product of:
          0.37745494 = sum of:
            0.37745494 = weight(_text_:toolkit in 1028) [ClassicSimilarity], result of:
              0.37745494 = score(doc=1028,freq=2.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                1.0101926 = fieldWeight in 1028, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.09375 = fieldNorm(doc=1028)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  2. Galeffi, A.; Sardo, A.L.: Cataloguing, a necessary evil : critical aspects of RDA (2016) 0.07
    0.06810116 = product of:
      0.13620232 = sum of:
        0.13620232 = product of:
          0.27240464 = sum of:
            0.27240464 = weight(_text_:toolkit in 2952) [ClassicSimilarity], result of:
              0.27240464 = score(doc=2952,freq=6.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.7290438 = fieldWeight in 2952, product of:
                  2.4494898 = tf(freq=6.0), with freq of:
                    6.0 = termFreq=6.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=2952)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    The Toolkit designed by the RDA Steering Committee makes Resource Description and Access available on the web, together with other useful documents (workflows, mappings, etc.). Reading, learning and memorizing are interconnected, and a working tool should make these activities faster and easier to perform. Some issues arise while verifying the real easiness of use and learning of the tool. The practical and formal requirements for a cataloguing code include plain language, ease of memorisation, clarity of instructions, familiarity for users, predictability and reproducibility of solutions, and general usability. From a formal point of view, the RDA text does not appear to be conceived for an uninterrupted reading, but just for reading of few paragraphs for temporary catalographic needs. From a content point of view, having a syndetic view of the description of a resource is rather difficult: catalographic details are scattered and their re-organization is not easy. The visualisation and logical organisation in the Toolkit could be improved: the table of contents occupies a sizable portion of the screen and resizing or hiding it is not easy; the indentation leaves little space to the words; inhomogeneous font styles (italic and bold) and poor contrast between background and text colours make reading not easy; simultaneous visualization of two or more parts of the text is not allowed; and Toolkit's icons are less intuitive than expected. In the conclusion, some suggestions on how to improve the Toolkit's aspects and usability are provided.
    Object
    RDA Toolkit
  3. Kuhagen, J.: RDA content in multiple languages : a new standard not only for libraries (2016) 0.06
    0.062909156 = product of:
      0.12581831 = sum of:
        0.12581831 = product of:
          0.25163662 = sum of:
            0.25163662 = weight(_text_:toolkit in 2955) [ClassicSimilarity], result of:
              0.25163662 = score(doc=2955,freq=2.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.67346174 = fieldWeight in 2955, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.0625 = fieldNorm(doc=2955)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    A summary of the presence of RDA content in languages other than English in RDA Toolkit, in the RDA Registry, in the RIMMF data editor, and as separate translations is given. Translation policy is explained and the benefits of translation on the content of RDA are noted.
  4. Acedera, A.P.: Are Philippine librarians ready for resource description and access (RDA)? : the Mindanao experience (2014) 0.06
    0.055045508 = product of:
      0.110091016 = sum of:
        0.110091016 = product of:
          0.22018203 = sum of:
            0.22018203 = weight(_text_:toolkit in 1983) [ClassicSimilarity], result of:
              0.22018203 = score(doc=1983,freq=2.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.589279 = fieldWeight in 1983, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=1983)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    This study aimed to find out the level of readiness of Mindanao librarians to use Resource Description and Access (RDA), which has been prescribed and adopted by the Philippine Professional Regulatory Board for Librarians (PRBFL). The majority of librarians are aware of the PRBFL prescription and adoption. Librarians who received more RDA training and felt that their RDA training was adequate and were more comfortable with the use of RDA as compared with those who received little or no RDA training. An important finding of the study is that most Mindanao libraries do not have access to the RDA Toolkit.
  5. Lisius, P.H.: AACR2 to RDA : is knowledge of both needed during the transition period? (2015) 0.06
    0.055045508 = product of:
      0.110091016 = sum of:
        0.110091016 = product of:
          0.22018203 = sum of:
            0.22018203 = weight(_text_:toolkit in 2008) [ClassicSimilarity], result of:
              0.22018203 = score(doc=2008,freq=2.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.589279 = fieldWeight in 2008, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=2008)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    The cataloging community is at a crossroads. Will catalogers need to continue learning both Anglo-American Cataloguing Rules , Second Edition (AACR2) and Resource Description and Access (RDA), or will learning RDA alone be enough? Through a selective literature review and examining the RDA Toolkit, it seems that there is currently a collective need to have access to both codes. However, when considering both Library of Congress-Program for Cooperative Cataloging (LC-PCC) and OCLC initiatives and an example from this author's institution relating to authority control in RDA and bibliographic record hybridization, it may only be necessary to learn RDA in the future. Additional research into practitioner experience could be done in the future to further examine this.
  6. Unkhoff-Giske, B.: Umfrage zur RDA-Einführung in der Universitätsbibliothek Trier (2018) 0.06
    0.055045508 = product of:
      0.110091016 = sum of:
        0.110091016 = product of:
          0.22018203 = sum of:
            0.22018203 = weight(_text_:toolkit in 4343) [ClassicSimilarity], result of:
              0.22018203 = score(doc=4343,freq=2.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.589279 = fieldWeight in 4343, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=4343)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Nach fast einem Jahr praktischer Erfahrung mit dem neuen Regelwerk wurde in der Universitätsbibliothek Trier eine Umfrage zur Einführung von "Resource Description and Access (RDA)" durchgeführt. Dabei ging es um den Katalogisierungsalltag: die Sicherheit im Umgang mit RDA und dem Toolkit, die Informationsversorgung, Änderungen beim Arbeitsaufwand, die Bewertung der RDA-Regelungen, insbesondere des neuen Prinzips "Cataloguer's judgement" und die persönliche Einstellung gegenüber dem Regelwerksumstieg. Die Ergebnisse der 20 Fragen werden im folgenden Beitrag vorgestellt und analysiert. Die Umfrage führte zu überraschend positiven Erkenntnissen, deckte aber auch Problemfelder auf, die der Nachbearbeitung bedürfen.
  7. Dunsire, G.; Fritz, D.; Fritz, R.: Instructions, interfaces, and interoperable data : the RIMMF experience with RDA revisited (2020) 0.06
    0.055045508 = product of:
      0.110091016 = sum of:
        0.110091016 = product of:
          0.22018203 = sum of:
            0.22018203 = weight(_text_:toolkit in 5751) [ClassicSimilarity], result of:
              0.22018203 = score(doc=5751,freq=2.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.589279 = fieldWeight in 5751, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=5751)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    This article presents a case study of RIMMF, a software tool developed to improve the orientation and training of catalogers who use Resource Description and Access (RDA) to maintain bibliographic data. The cataloging guidance and instructions of RDA are based on the Functional Requirements conceptual models that are now consolidated in the IFLA Library Reference Model, but many catalogers are applying RDA in systems that have evolved from inventory and text-processing applications developed from older metadata paradigms. The article describes how RIMMF interacts with the RDA Toolkit and RDA Registry to offer cataloger-friendly multilingual data input and editing interfaces.
  8. Wiesenmüller, H.: Gewogen und für zu leicht befunden : die Ergebnisse des RDA Tests in den USA (2011) 0.05
    0.047181867 = product of:
      0.094363734 = sum of:
        0.094363734 = product of:
          0.18872747 = sum of:
            0.18872747 = weight(_text_:toolkit in 5660) [ClassicSimilarity], result of:
              0.18872747 = score(doc=5660,freq=2.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.5050963 = fieldWeight in 5660, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.046875 = fieldNorm(doc=5660)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Seit Juli 2010 lief in den USA ein groß angelegter Test des neuen Regelwerks "Resource Description and Access" (RDA) und des Online-Werkzeugs "RDA Toolkit": Nach einer dreimonatigen Lernphase wurden im Laufe von weiteren drei Monaten über 10.000 Titeldaten- und 12.000 Normdatensätze von den drei US-amerikanischen Nationalbibliotheken (Library of Congress, National Agricultural Library, National Library of Medicine), den 23 offiziellen Testpartnern sowie weiteren informellen Testern angelegt. Im Laufe des ersten Quartals 2011 wertete das "U.S. RDA Test Coordinating Committee" die Ergebnisse aus und erstellte einen Bericht für die Direktoren der drei Nationalbibliotheken. Mit Spannung war nun die Entscheidung "on whether or not to implement RDA"' - so die Formulierung, mit der die drei Nationalbibliotheken im Mai 2008 ihr Testvorhaben angekündigt hatten - erwartet worden. Am 14. Juni wurde das "executive summary" zusammen mit einer Verlautbarung der Direktoren veröffentlicht; seit dem 17. Juni liegt der vollständige Bericht inklusive der Empfehlungen vor.
  9. Morris, S.R.; Wiggins, B.: Implementing RDA at the Library of Congress (2016) 0.05
    0.047181867 = product of:
      0.094363734 = sum of:
        0.094363734 = product of:
          0.18872747 = sum of:
            0.18872747 = weight(_text_:toolkit in 2947) [ClassicSimilarity], result of:
              0.18872747 = score(doc=2947,freq=2.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.5050963 = fieldWeight in 2947, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.046875 = fieldNorm(doc=2947)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    The Toolkit designed by the RDA Steering Committee makes Resource Description and Access available on the web, together with other useful documents (workflows, The process of implementation of RDA by Library of Congress, National Agricultural Library, and National Library of Medicine is presented. Each phase of development, test, decision, preparation for implementation of RDA and training about RDA is fully and accurately described and discussed. Benefits from implementation of RDA for the Library of Congress are identified and highlighted: more flexibility in cataloguing decisions, easier international sharing of cataloguing data, clearer linking among related works; closer cooperation with other libraries in the North American community, production of an online learning platform in order to deliver RDA training on a large scale in real time to catalogers.
  10. Moore, D.; Mealey, N.: Consortial-based customizations for new Primo UI (2016) 0.05
    0.047181867 = product of:
      0.094363734 = sum of:
        0.094363734 = product of:
          0.18872747 = sum of:
            0.18872747 = weight(_text_:toolkit in 3199) [ClassicSimilarity], result of:
              0.18872747 = score(doc=3199,freq=2.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.5050963 = fieldWeight in 3199, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.046875 = fieldNorm(doc=3199)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Users interested in customizing their Primo installation are required to configure specific settings, files, and code during the View setup process. A consequence of this is that unique customizations are not easily sharable between institutions. With the release of the new Primo User Interface, Ex Libris has enabled institutions to manage interface customizations via the Package Customization Manager. In the summer of 2016, an Orbis Cascade Alliance working group investigated the efficacy of the Package Manager as a means of centrally sharing and deploying Orbis Cascade Alliance Primo Toolkit customizations. By virtue of passively loading customizations to the central package, each institution could pass custom parameters with local JS in order to adapt central customizations to the specific needs of that institution's users. This article will address both the potential and the limitations of the Primo Package Customization Manager. It will also provide best practices for consortia seeking to centrally manage and share Primo enhancements and it will identify areas of future development for centrally shared customizations.
  11. Poulter, A.: Filling in the blanks in RDA or remaining blank? : the strange case of FRSAD (2013) 0.04
    0.04448349 = product of:
      0.08896698 = sum of:
        0.08896698 = product of:
          0.17793396 = sum of:
            0.17793396 = weight(_text_:toolkit in 980) [ClassicSimilarity], result of:
              0.17793396 = score(doc=980,freq=4.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.47620937 = fieldWeight in 980, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.03125 = fieldNorm(doc=980)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    RDA (Resource Description and Access) was released in July 2010, and made available for use, either in an online form, the RDA Toolkit (http://beta.rdatoolkit.gvpi.net/) or in printed form, in a large loose-leaf binder. In July 2011, the Library of Congress, the National Library of Medicine, and the National Agricultural Library announced the decision to adopt RDA after conducting trials. The decision to adopt RDA though carried riders on certain perceived issues to be resolved, related to rules readability, online delivery issues of the RDA Toolkit and a business case outlining costs and benefits of adoption. It appears though that, allowing for these issues to be dealt with, RDA will begin adoption in 2013 and will gradually replace the aged AACR2 (Anglo-American Cataloguing Rules, Second Edition). Unlike AACR2, RDA was intended to also provide subject access. As RDA currently stands, Chapters 12-16, 23, 33-37 are intended to establish guidelines for providing subject access, but only Chapter 16, 'Identifying Places' is complete.. This paper will outline possible strategies for moving forward in completing the remaining blank chapters, based on the model given in the recent Functional Requirements for Subject Authority Data (IFLA Working Group, 2010), here-after referred to as FRSAD. This paper begins by outlining significant developments prior to the appearance of FRSAD which was formerly known as FRSAR. This involves coverage of the two preceding reports, the Functional Requirements of Bibliographic Records (FRBR, IFLA 2008) and the Functional Requirements for Authority Data (FRAD, IFLA 2009), which was formerly known as FRANAR. The final version of FRSAD, released in 2009, will be contrasted to earlier efforts to extend the FRBR/FRAD models to fully cover subject access. Finally, a prospective proposal to take FRSAD forward to implementation using PRECIS (Preserved Context Indexing System) will be examined, as well as the general reception of FRSAD.
  12. Mejía, J.A.; García, C.; Ramos, A.; Hernández, O.: Implementation of RDA to bibliographic and authority records from the LIBRUNAM catalog at the Universidad Nacional Autónoma de México (2014) 0.04
    0.039318223 = product of:
      0.078636445 = sum of:
        0.078636445 = product of:
          0.15727289 = sum of:
            0.15727289 = weight(_text_:toolkit in 1992) [ClassicSimilarity], result of:
              0.15727289 = score(doc=1992,freq=2.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.42091358 = fieldWeight in 1992, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=1992)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    This article discusses the implementation of the new cataloging code, Resource Description and Access (RDA), to the bibliographic and authority records of the LIBRUNAM catalog. In 2010, the Dirección General de Bibliotecas started analyzing this new cataloging code through the use of the RDA Toolkit and other documentation related to RDA. During this process, the core elements for bibliographic and authority records were identified and retrospective changes were automatically carried out using the Aleph Library Management System. For those records that needed modifications, manual updates were made, while RDA instructions were applied to new records. The updating of each element is described, including carrier and content types, preferred titles in the original language, and conventional and collective titles for religious works. Elements defined in Chapter 9 and Chapter 11, and relationship designators defined in Appendix K were added to authority records for personal names. These retrospective updates were made to 1,500,000 bibliographic records and 73,000 authority records. The adoption of the RDA code in LIBRUNAM accomplishes support for the main user tasks: Find, identify, select, and obtain.
  13. Wiesenmüller, H.: Baustelle RDA : die Dynamik des Regelwerks als Herausforderung (2017) 0.04
    0.039318223 = product of:
      0.078636445 = sum of:
        0.078636445 = product of:
          0.15727289 = sum of:
            0.15727289 = weight(_text_:toolkit in 4000) [ClassicSimilarity], result of:
              0.15727289 = score(doc=4000,freq=2.0), product of:
                0.3736465 = queryWeight, product of:
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.049039155 = queryNorm
                0.42091358 = fieldWeight in 4000, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  7.61935 = idf(docFreq=58, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=4000)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Der Beitrag beschreibt die dynamische Entwicklung des Katalogisierungsregelwerks "Resource Description and Access" (RDA) und die weitreichenden Konsequenzen, die sich daraus für den deutschsprachigen Raum ergeben. Seit seinem ersten Erscheinen im Jahr 2010 hat sich RDA erheblich verändert. Größere Regeländerungen wurden bisher einmal jährlich in den Standard eingearbeitet, kleinere sogar viermal jährlich. Im Rahmen des 3R-Projekts (RDA Toolkit Restructure and Redesign Project) erfolgt derzeit eine umfassende Umstrukturierung und Neugestaltung des Regelwerkstextes. Auch danach ist nicht mit einem merklichen Nachlassen der Dynamik zu rechnen. Jede Änderung am Standard muss verarbeitet und für die D-A-CH-Länder aufbereitet werden. Der Aufwand dafür ist hoch: Vielfach müssen Anwendungsregeln angepasst werden, und neben der deutschen Übersetzung sind zahlreiche weitere Dokumente zu aktualisieren. Teilweise wirken sich Änderungen auch auf die Implementierung aus. Schließlich müssen alle Neuerungen umfassend kommuniziert werden. Zur Unterstützung der komplexen Prozesse werden professionelle und mächtige Werkzeuge benötigt. Noch wichtiger ist es jedoch, ein Bewusstsein dafür zu schaffen, dass für die Arbeiten dauerhaft ausreichende Personalressourcen bereitgestellt werden müssen. Denn nur der Umstieg auf RDA ist abgeschlossen - die kontinuierliche Arbeit am Regelwerk geht weiter.
  14. RAK-NBM : Interpretationshilfe zu NBM 3b,3 (2000) 0.04
    0.037584867 = product of:
      0.075169735 = sum of:
        0.075169735 = product of:
          0.15033947 = sum of:
            0.15033947 = weight(_text_:22 in 4362) [ClassicSimilarity], result of:
              0.15033947 = score(doc=4362,freq=4.0), product of:
                0.17172676 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.049039155 = queryNorm
                0.8754574 = fieldWeight in 4362, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.125 = fieldNorm(doc=4362)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Date
    22. 1.2000 19:22:27
  15. Carter, J.A.: PASSPORT/PRISM: authors and titles and MARC : oh my! (1993) 0.03
    0.026576513 = product of:
      0.053153027 = sum of:
        0.053153027 = product of:
          0.10630605 = sum of:
            0.10630605 = weight(_text_:22 in 527) [ClassicSimilarity], result of:
              0.10630605 = score(doc=527,freq=2.0), product of:
                0.17172676 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.049039155 = queryNorm
                0.61904186 = fieldWeight in 527, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.125 = fieldNorm(doc=527)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Source
    OCLC systems and services. 9(1993) no.3, S.20-22
  16. Madison, O.M:A.: ¬The role of the name main-entry heading in the online environment (1992) 0.03
    0.026576513 = product of:
      0.053153027 = sum of:
        0.053153027 = product of:
          0.10630605 = sum of:
            0.10630605 = weight(_text_:22 in 4397) [ClassicSimilarity], result of:
              0.10630605 = score(doc=4397,freq=2.0), product of:
                0.17172676 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.049039155 = queryNorm
                0.61904186 = fieldWeight in 4397, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.125 = fieldNorm(doc=4397)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Source
    Serials librarian. 22(1992), S.371-391
  17. Bärhausen, A.; Euskirchen, A.: Nachbearbeitung der Katalog-Konversion oder : Es bleibt viel zu tun, packen wir's an! (1999) 0.02
    0.02349054 = product of:
      0.04698108 = sum of:
        0.04698108 = product of:
          0.09396216 = sum of:
            0.09396216 = weight(_text_:22 in 4367) [ClassicSimilarity], result of:
              0.09396216 = score(doc=4367,freq=4.0), product of:
                0.17172676 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.049039155 = queryNorm
                0.54716086 = fieldWeight in 4367, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.078125 = fieldNorm(doc=4367)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Date
    22. 1.2000 19:36:10
    22. 1.2000 19:40:40
  18. Houissa, A.: Arabic personal names : their components and rendering in catalog entries (1991) 0.02
    0.023254449 = product of:
      0.046508897 = sum of:
        0.046508897 = product of:
          0.093017794 = sum of:
            0.093017794 = weight(_text_:22 in 2857) [ClassicSimilarity], result of:
              0.093017794 = score(doc=2857,freq=2.0), product of:
                0.17172676 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.049039155 = queryNorm
                0.5416616 = fieldWeight in 2857, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.109375 = fieldNorm(doc=2857)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Source
    Cataloging and classification quarterly. 13(1991) no.2, S.3-22
  19. Jones, E.: ¬The FRBR model as applied to continuing resources (2005) 0.02
    0.023254449 = product of:
      0.046508897 = sum of:
        0.046508897 = product of:
          0.093017794 = sum of:
            0.093017794 = weight(_text_:22 in 2900) [ClassicSimilarity], result of:
              0.093017794 = score(doc=2900,freq=2.0), product of:
                0.17172676 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.049039155 = queryNorm
                0.5416616 = fieldWeight in 2900, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.109375 = fieldNorm(doc=2900)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Date
    10. 9.2000 17:38:22
  20. Münnich, M.: RAK2: Sachstandsbericht : vom Bibliothekartag '95 zum Bibliothekartag '96 (1996) 0.02
    0.023254449 = product of:
      0.046508897 = sum of:
        0.046508897 = product of:
          0.093017794 = sum of:
            0.093017794 = weight(_text_:22 in 4594) [ClassicSimilarity], result of:
              0.093017794 = score(doc=4594,freq=2.0), product of:
                0.17172676 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.049039155 = queryNorm
                0.5416616 = fieldWeight in 4594, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.109375 = fieldNorm(doc=4594)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Date
    21. 9.1996 16:03:22

Years

Languages

  • e 154
  • d 37
  • i 3
  • f 1
  • s 1
  • More… Less…

Types