Search (1270 results, page 3 of 64)

0.06999727 = product of:
  0.2799891 = sum of:
    0.2799891 = weight(_text_:java in 6851) [ClassicSimilarity], result of:
      0.2799891 = score(doc=6851,freq=2.0), product of:
        0.4494802 = queryWeight, product of:
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.06377861 = queryNorm
        0.62291753 = fieldWeight in 6851, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.0625 = fieldNorm(doc=6851)
  0.25 = coord(1/4)

Abstract

This book provides a quick, concise guide to the issues surrounding the preparation of a well-designed, professional web site using HTML. Topics covered include: how to plan your web site effectively, effective use of hypertext, images, audio and video; layout techniques using tables and and list; how to use style sheets, font sizes and plans for mathematical equation make up. Integration of CGI scripts, Java and ActiveX into your web site is also discussed

0.06999727 = product of:
  0.2799891 = sum of:
    0.2799891 = weight(_text_:java in 171) [ClassicSimilarity], result of:
      0.2799891 = score(doc=171,freq=2.0), product of:
        0.4494802 = queryWeight, product of:
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.06377861 = queryNorm
        0.62291753 = fieldWeight in 171, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.0625 = fieldNorm(doc=171)
  0.25 = coord(1/4)

Abstract

Explains how the Intranet (in effect an Internet limited to the computer systems of a single organization) developed out of the Internet, and what its uses and advantages are. Focuses on the Intranet developed in the Glaxo Wellcome organization. Briefly discusses a number of technologies in development, e.g. Java, Real audio, 3D and VRML, and summarizes the issues involved in the successful development of the Intranet, that is, bandwidth, searching tools, security, and legal issues

0.06999727 = product of:
  0.2799891 = sum of:
    0.2799891 = weight(_text_:java in 604) [ClassicSimilarity], result of:
      0.2799891 = score(doc=604,freq=2.0), product of:
        0.4494802 = queryWeight, product of:
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.06377861 = queryNorm
        0.62291753 = fieldWeight in 604, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.0625 = fieldNorm(doc=604)
  0.25 = coord(1/4)

Abstract

Gives an overview of Web information system development. Discusses some basic concepts and technologies such as HTML, HTML FORM, CGI and Java, which are associated with developing WWW information systems. Further discusses the design and implementation of Virtual Travel Mart, a Web based end user oriented travel information system. Finally, addresses some issues in developing WWW information systems

0.06999727 = product of:
  0.2799891 = sum of:
    0.2799891 = weight(_text_:java in 2782) [ClassicSimilarity], result of:
      0.2799891 = score(doc=2782,freq=2.0), product of:
        0.4494802 = queryWeight, product of:
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.06377861 = queryNorm
        0.62291753 = fieldWeight in 2782, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.0625 = fieldNorm(doc=2782)
  0.25 = coord(1/4)

Abstract

Ameritech Library Services has released Dynix WebPac on NT, which provides access to a Dynix catalogue from any Java compatible Web browser. Users can place holds, cancel and postpone holds, view and renew items on loan and sort and limit search results from the Web. Describes some of the other features of Dynix WebPac

0.06999727 = product of:
  0.2799891 = sum of:
    0.2799891 = weight(_text_:java in 3078) [ClassicSimilarity], result of:
      0.2799891 = score(doc=3078,freq=2.0), product of:
        0.4494802 = queryWeight, product of:
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.06377861 = queryNorm
        0.62291753 = fieldWeight in 3078, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.0625 = fieldNorm(doc=3078)
  0.25 = coord(1/4)

Abstract

OCLC has announced that 6 library systems have completed field tests of the OCLC SiteSearch 4.0 suite of software, paving its way for release. Traces the beta site testing programme from its beginning in November 1997 and notes that OCLC SiteServer components have been written in Java programming language which will increase libraries' ability to extend the functionality of the SiteSearch software to create new features specific to local needs

0.06999727 = product of:
  0.2799891 = sum of:
    0.2799891 = weight(_text_:java in 4618) [ClassicSimilarity], result of:
      0.2799891 = score(doc=4618,freq=2.0), product of:
        0.4494802 = queryWeight, product of:
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.06377861 = queryNorm
        0.62291753 = fieldWeight in 4618, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.0625 = fieldNorm(doc=4618)
  0.25 = coord(1/4)

Abstract

Demonstrates a new method of providing networked computer assisted learning to avoid the pitfalls of traditional methods. This was achieved using Web pages enhanced with Java applets, MPEG video clips and Dynamic HTML

0.06999727 = product of:
  0.2799891 = sum of:
    0.2799891 = weight(_text_:java in 130) [ClassicSimilarity], result of:
      0.2799891 = score(doc=130,freq=2.0), product of:
        0.4494802 = queryWeight, product of:
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.06377861 = queryNorm
        0.62291753 = fieldWeight in 130, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.0625 = fieldNorm(doc=130)
  0.25 = coord(1/4)

Object

Java

0.069742486 = product of:
  0.13948497 = sum of:
    0.104995914 = weight(_text_:java in 55) [ClassicSimilarity], result of:
      0.104995914 = score(doc=55,freq=2.0), product of:
        0.4494802 = queryWeight, product of:
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.06377861 = queryNorm
        0.23359407 = fieldWeight in 55, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.0475073 = idf(docFreq=104, maxDocs=44421)
          0.0234375 = fieldNorm(doc=55)
    0.03448905 = weight(_text_:und in 55) [ClassicSimilarity], result of:
      0.03448905 = score(doc=55,freq=22.0), product of:
        0.14145452 = queryWeight, product of:
          2.217899 = idf(docFreq=13141, maxDocs=44421)
          0.06377861 = queryNorm
        0.24381724 = fieldWeight in 55, product of:
          4.690416 = tf(freq=22.0), with freq of:
            22.0 = termFreq=22.0
          2.217899 = idf(docFreq=13141, maxDocs=44421)
          0.0234375 = fieldNorm(doc=55)
  0.5 = coord(2/4)

Content

"Fünf Jahre nach seiner Gründung ist Google zum Herz des weltweiten Computernetzes geworden. Mit seiner Konzentration aufs Wesentliche hat die Suchmaschine alle anderen Anbieter weit zurück gelassen. Aber Google kann viel mehr, als im Web nach Texten und Bildern zu suchen. Gesammelt und aufbereitet werden auch Beiträge in Diskussionsforen (Newsgroups), aktuelle Nachrichten und andere im Netz verfügbare Informationen. Wer sich beim "Googeln" darauf beschränkt, ein einziges Wort in das Suchformular einzutippen und dann die ersten von oft mehreren hunderttausend Treffern anzuschauen, nutzt nur einen winzigen Bruchteil der Möglichkeiten. Wie man Google bis zum letzten ausreizt, haben Tara Calishain und Rael Dornfest in einem bislang nur auf Englisch veröffentlichten Buch dargestellt (Tara Calishain/Rael Dornfest: Google Hacks", www.oreilly.de, 28 Euro. Die wichtigsten Praxistipps kosten als Google Pocket Guide 12 Euro). - Suchen mit bis zu zehn Wörtern - Ihre "100 Google Hacks" beginnen mit Google-Strategien wie der Kombination mehrerer Suchbegriffe und enden mit der Aufforderung zur eigenen Nutzung der Google API ("Application Programming Interface"). Diese Schnittstelle kann zur Entwicklung von eigenen Programmen eingesetzt werden,,die auf die Google-Datenbank mit ihren mehr als drei Milliarden Einträgen zugreifen. Ein bewussteres Suchen im Internet beginnt mit der Kombination mehrerer Suchbegriffe - bis zu zehn Wörter können in das Formularfeld eingetippt werden, welche Google mit dem lo-gischen Ausdruck "und" verknüpft. Diese Standardvorgabe kann mit einem dazwischen eingefügten "or" zu einer Oder-Verknüpfung geändert werden. Soll ein bestimmter Begriff nicht auftauchen, wird ein Minuszeichen davor gesetzt. Auf diese Weise können bei einer Suche etwa alle Treffer ausgefiltert werden, die vom Online-Buchhändler Amazon kommen. Weiter gehende Syntax-Anweisungen helfen ebenfalls dabei, die Suche gezielt einzugrenzen: Die vorangestellte Anweisung "intitle:" etwa (ohne Anführungszeichen einzugeben) beschränkt die Suche auf all diejenigen Web-Seiten, die den direkt danach folgenden Begriff in ihrem Titel aufführen. Die Computer von Google bewältigen täglich mehr als 200 Millionen Anfragen. Die Antworten kommen aus einer Datenbank, die mehr als drei Milliarden Einträge enthält und regelmäßig aktualisiert wird. Dazu Werden SoftwareRoboter eingesetzt, so genannte "Search-Bots", die sich die Hyperlinks auf Web-Seiten entlang hangeln und für jedes Web-Dokument einen Index zur Volltextsuche anlegen. Die Einnahmen des 1998 von Larry Page und Sergey Brin gegründeten Unternehmens stammen zumeist von Internet-Portalen, welche die GoogleSuchtechnik für ihre eigenen Dienste übernehmen. Eine zwei Einnahmequelle ist die Werbung von Unternehmen, die für eine optisch hervorgehobene Platzierung in den GoogleTrefferlisten zahlen. Das Unternehmen mit Sitz im kalifornischen Mountain View beschäftigt rund 800 Mitarbeiter. Der Name Google leitet sich ab von dem Kunstwort "Googol", mit dem der amerikanische Mathematiker Edward Kasner die unvorstellbar große Zahl 10 hoch 100 (eine 1 mit hundert Nullen) bezeichnet hat. Kommerzielle Internet-Anbieter sind sehr, daran interessiert, auf den vordersten Plätzen einer Google-Trefferliste zu erscheinen.
Da Google im Unterschied zu Yahoo oder Lycos nie ein auf möglichst viele Besuche angelegtes Internet-Portal werden wollte, ist die Suche in der Datenbank auch außerhalb der Google-Web-Site möglich. Dafür gibt es zunächst die "Google Toolbar" für den Internet Explorer, mit der dieser Browser eine eigene Leiste, für die Google-Suche erhält. Freie Entwickler bieten im Internet eine eigene Umsetzung: dieses Werkzeugs auch für den Netscape/ Mozilla-Browser an. Daneben kann ein GoogleSucheingabefeld aber auch auf die eigene WebSeite platziert werden - dazu sind nur vier Zei-len HTML-Code nötig. Eine Google-Suche zu starten, ist übrigens auch ganz ohne Browser möglich. Dazu hat das Unternehmen im Aprilvergangenen Jahres die API ("Application Programming Interface") frei gegeben, die in eigene Programme' eingebaut wird. So kann man etwa eine Google-Suche mit einer E-Mail starten: Die Suchbegriffe werden in die Betreff Zeile einer ansonsten leeren EMail eingetragen, die an die Adresse google@capeclear.com geschickt wird. Kurz danach trifft eine automatische Antwort-Mail mit den ersten zehn Treffern ein. Die entsprechenden Kenntnisse vorausgesetzt, können Google-Abfragen auch in Web-Services eingebaut werden - das sind Programme, die Daten aus dem Internet verarbeiten. Als Programmiertechniken kommen dafür Perl, PHP, Python oder Java in Frage. Calishain und Dornfest stellen sogar eine Reihe von abgedrehten Sites vor, die solche Programme für abstrakte Gedichte oder andere Kunstwerke einsetzen."

0.06767474 = product of:
  0.27069896 = sum of:
    0.27069896 = weight(_text_:head in 676) [ClassicSimilarity], result of:
      0.27069896 = score(doc=676,freq=4.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.5758386 = fieldWeight in 676, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0390625 = fieldNorm(doc=676)
  0.25 = coord(1/4)

Abstract

Authorship attribution is an important problem in text classification, with many applications and a substantial body of research activity. Among the research findings are that many different methods will work, including a number of methods that are superficially language-independent (such as an analysis of the most common "words" or "character n-grams" in a document). Since all languages have words (and all written languages have characters), this method could (in theory) work on any language. However, it is not clear that the methods that work best on, for example English, would also work best on other languages. It is not even clear that the same level of performance is achievable in different languages, even under identical conditions. Unfortunately, it is very difficult to achieve "identical conditions" in practice. A new corpus, developed by George Mikros, provides very tight controls not only for author but also for topic, thus enabling a direct comparison of performance levels between the two languages Greek and English. We compare a number of different methods head-to-head on this corpus, and show that, overall, performance on English is higher than performance on Greek, often highly significantly so.

0.06699457 = product of:
  0.26797828 = sum of:
    0.26797828 = weight(_text_:head in 1661) [ClassicSimilarity], result of:
      0.26797828 = score(doc=1661,freq=2.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.57005113 = fieldWeight in 1661, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0546875 = fieldNorm(doc=1661)
  0.25 = coord(1/4)

Abstract

The author, former head of information and documentation at the German patent office, recalls more than 30 years of international cooperation in the classifying and indexing of patent documents. Reviews the work of the former ICEREPAT (International Cooperation in Information Retrieval among Examining Patent Offices) which produced coordinate indexing term lists. Describes the development of the IPC which produced a purely hierarchical classification with function oriented and application oriented entries. Completion of the IPC as a basic search tool was greeted with satisfaction by the patent world. Revised versions of IPC are issued every 5 years in English and in French. Outlines the problems still associated with the searching of patent documents

0.06699457 = product of:
  0.26797828 = sum of:
    0.26797828 = weight(_text_:head in 3875) [ClassicSimilarity], result of:
      0.26797828 = score(doc=3875,freq=2.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.57005113 = fieldWeight in 3875, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0546875 = fieldNorm(doc=3875)
  0.25 = coord(1/4)

0.06699457 = product of:
  0.26797828 = sum of:
    0.26797828 = weight(_text_:head in 5928) [ClassicSimilarity], result of:
      0.26797828 = score(doc=5928,freq=2.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.57005113 = fieldWeight in 5928, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0546875 = fieldNorm(doc=5928)
  0.25 = coord(1/4)

0.06699457 = product of:
  0.26797828 = sum of:
    0.26797828 = weight(_text_:head in 507) [ClassicSimilarity], result of:
      0.26797828 = score(doc=507,freq=2.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.57005113 = fieldWeight in 507, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0546875 = fieldNorm(doc=507)
  0.25 = coord(1/4)

0.06699457 = product of:
  0.26797828 = sum of:
    0.26797828 = weight(_text_:head in 506) [ClassicSimilarity], result of:
      0.26797828 = score(doc=506,freq=2.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.57005113 = fieldWeight in 506, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0546875 = fieldNorm(doc=506)
  0.25 = coord(1/4)

Abstract

As librarians at Ball State University Libraries prepared to implement the authority control module of its automated system, little information about the dependability of the module or its effectiveness as compared to the active system of providing authority control was available. The head of cataloguing decided that it would be advisable to compare the effectiveness of the pre cataloguing authority control procedure in place with the post cataloguing authority control procedures that could be provided through the NOTIS reports, with the 2 systems running concurrently during the test period. The test, as expected, revealed that in most respects the post cataloguing authority control procedures provide as much or more in the way of authority control than the front end procedures, and that their uses reduce redundancy and increase efficiency

0.06699457 = product of:
  0.26797828 = sum of:
    0.26797828 = weight(_text_:head in 3446) [ClassicSimilarity], result of:
      0.26797828 = score(doc=3446,freq=2.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.57005113 = fieldWeight in 3446, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0546875 = fieldNorm(doc=3446)
  0.25 = coord(1/4)

Abstract

In addition to having a ethical obligation to treat colleagues with courtesy and respect, refernce librarians must be able to interact effectively with one another in order to provide an optimal level of service to their users. A well functioning reference unit builds on the individual strengths of each reference librarian and promotes an environment conductive to consultation and sharing. The tone for setting such an atmosphere is largely dependent upon the actions of the head of the unit who must set an example of fairness, cooperation, and striving for excellence while providing encouragement to update skills

0.06699457 = product of:
  0.26797828 = sum of:
    0.26797828 = weight(_text_:head in 4372) [ClassicSimilarity], result of:
      0.26797828 = score(doc=4372,freq=2.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.57005113 = fieldWeight in 4372, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0546875 = fieldNorm(doc=4372)
  0.25 = coord(1/4)

Content

Interview mit Martina Reich, head of the Library and Information Specialist at Roland Berger & Partner GmbH, International Management Consultant, München and Madrid

0.06699457 = product of:
  0.26797828 = sum of:
    0.26797828 = weight(_text_:head in 1963) [ClassicSimilarity], result of:
      0.26797828 = score(doc=1963,freq=2.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.57005113 = fieldWeight in 1963, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0546875 = fieldNorm(doc=1963)
  0.25 = coord(1/4)

Abstract

Ki-Tat is the Head of Systems, Hong Kong University of Science & Technology Library, Hong Kong. In his article, Ki-Tat discusses why MARC21 is ideal for Anglo-American names, but not suitable for non-Latin names. He provides three suggestions: making 1XX field repeatable, improving linking capability between related forms of a name by avoiding the subfield 6 in tag 880, and adding a subfield to store language script used in each tag field. Ki-Tat also stresses that encoding MARC in XML provides possibility to expand "authority control" to "access control". Lastly, he illustrates a method of using SOAP (Simple Object Access Protocol) technology to provide name access control globally.

0.06699457 = product of:
  0.26797828 = sum of:
    0.26797828 = weight(_text_:head in 915) [ClassicSimilarity], result of:
      0.26797828 = score(doc=915,freq=2.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.57005113 = fieldWeight in 915, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0546875 = fieldNorm(doc=915)
  0.25 = coord(1/4)

Abstract

This paper explores the potential for creating online environments for bilingual communities in which minority-language use is supported and actively encouraged. It discusses the language behaviour and attitudes of Welsh-English bilingual users in Pen i Ben, a pilot online community of practice for Head Teachers in Wales. The patterns of language use and the functional roles served by the languages are described. Despite the creation of a bilingual environment and the implementation of specific strategies to encourage Welsh use, the trend indicates increasing use of English. However, it is suggested that a wider set of supporting strategies might be successful in maintaining a truly bilingual online community.

0.06699457 = product of:
  0.26797828 = sum of:
    0.26797828 = weight(_text_:head in 15) [ClassicSimilarity], result of:
      0.26797828 = score(doc=15,freq=2.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.57005113 = fieldWeight in 15, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0546875 = fieldNorm(doc=15)
  0.25 = coord(1/4)

Abstract

This paper describes a system to semi-automatically extend and refine ontologies by mining textual data from the Web sites of international online media. Expanding a seed ontology creates a semantic network through co-occurrence analysis, trigger phrase analysis, and disambiguation based on the WordNet lexical dictionary. Spreading activation then processes this semantic network to find the most probable candidates for inclusion in an extended ontology. Approaches to identifying hierarchical relationships such as subsumption, head noun analysis and WordNet consultation are used to confirm and classify the found relationships. Using a seed ontology on "climate change" as an example, this paper demonstrates how spreading activation improves the result by naturally integrating the mentioned methods.

0.06699457 = product of:
  0.26797828 = sum of:
    0.26797828 = weight(_text_:head in 58) [ClassicSimilarity], result of:
      0.26797828 = score(doc=58,freq=2.0), product of:
        0.4700952 = queryWeight, product of:
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.06377861 = queryNorm
        0.57005113 = fieldWeight in 58, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          7.370734 = idf(docFreq=75, maxDocs=44421)
          0.0546875 = fieldNorm(doc=58)
  0.25 = coord(1/4)

Abstract

For several decades we, among others, have criticized the use of citations for evaluative purposes. Although these criticisms have been noted, they have been largely brushed aside or ignored, not addressed head on. This may be for a number of reasons, but we believe the main one is that these criticisms undermine the desire to have an easy "scientific"-that is, quantitative-method of evaluation. Consequently, we continue and update our criticism of the use of citations for evaluation.