Search (36 results, page 2 of 2)

0.01321952 = product of:
  0.0660976 = sum of:
    0.0660976 = weight(_text_:books in 5840) [ClassicSimilarity], result of:
      0.0660976 = score(doc=5840,freq=2.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.2669927 = fieldWeight in 5840, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5840)
  0.2 = coord(1/5)

Abstract

Purpose This paper scrutinizes the scholarship on community archives' information work. Community archives and archiving projects represent unprecedentedly democratic venues for information work centering on essential documentary concepts such as custody, collection development and appraisal, processing, arrangement and description, organization, representation and naming, collaboration, resource generation and allocation, activism and social justice, preservation, reuse, and sustainability. Design/methodology/approach Unearthed through databases searches, citation chaining, and browsing, sources examined include peer-reviewed journal articles, books, and book chapters published in the English language between 1985 and 2018. Findings The literature on community archives' information work shows considerable geographical (six continents), topical, and (inter)disciplinary variety. This paper first explores scholars' efforts to define both community and community archives. Second, it unpacks the ways in which community archives include new stakeholders and new record types and formats even as they leverage alternative archival principles and practices. Third, it discusses community archives as political venues for empowerment, activism, and social justice work. Fourth, this paper delves into the benefits and challenges of partnerships and collaborations with mainstream institutions. Fifth, it documents the obstacles community archives face: not only tensions within and among communities, but also sustainability concerns. Finally, it sets forth six directions for future research. Originality/value This paper is the first systematic review of the community archives literature.

0.01144844 = product of:
  0.0572422 = sum of:
    0.0572422 = weight(_text_:books in 2467) [ClassicSimilarity], result of:
      0.0572422 = score(doc=2467,freq=6.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.23122245 = fieldWeight in 2467, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.01953125 = fieldNorm(doc=2467)
  0.2 = coord(1/5)

Abstract

Consider movie listings in newspapers. Most Canadian newspapers list movie showtimes in two large blocks, for the two major theatre chains. The listings are ordered by region (in large cities), then theatre, then movie, and finally by showtime. Anyone wondering where and when a particular movie is playing must scan the complete listings. Determining what movies are playing in the next half hour is very difficult. When movie listings went onto the web, most sites used a simple faceted organization, always with movie name and theatre, and perhaps with region or neighbourhood (thankfully, theatre chains were left out). They make it easy to pick a theatre and see what movies are playing there, or to pick a movie and see what theatres are showing it. To complete the system, the sites should allow users to browse by neighbourhood and showtime, and to order the results in any way they desired. Thus could people easily find answers to such questions as, "Where is the new James Bond movie playing?" "What's showing at the Roxy tonight?" "I'm going to be out in in Little Finland this afternoon with three hours to kill starting at 2 ... is anything interesting playing?" A hypertext, faceted classification system makes more useful information more easily available to the user. Reading the books and articles below in chronological order will show a certain progression: suggestions that faceting and hypertext might work well, confidence that facets would work well if only someone would make such a system, and finally the beginning of serious work on actually designing, building, and testing faceted web sites. There is a solid basis of how to make faceted classifications (see Vickery in Recommended), but their application online is just starting. Work on XFML (see Van Dijck's work in Recommended) the Exchangeable Faceted Metadata Language, will make this easier. If it follows previous patterns, parts of the Internet community will embrace the idea and make open source software available for others to reuse. It will be particularly beneficial if professionals in both information studies and computer science can work together to build working systems, standards, and code. Each can benefit from the other's expertise in what can be a very complicated and technical area. One particularly nice thing about this area of research is that people interested in combining facets and the web often have web sites where they post their writings.
This bibliography is not meant to be exhaustive, but unfortunately it is not as complete as I wanted. Some books and articles are not be included, but they may be used in my future work. (These include two books and one article by B.C. Vickery: Faceted Classification Schemes (New Brunswick, NJ: Rutgers, 1966), Classification and Indexing in Science, 3rd ed. (London: Butterworths, 1975), and "Knowledge Representation: A Brief Review" (Journal of Documentation 42 no. 3 (September 1986): 145-159; and A.C. Foskett's "The Future of Faceted Classification" in The Future of Classification, edited by Rita Marcella and Arthur Maltby (Aldershot, England: Gower, 2000): 69-80). Nevertheless, I hope this bibliography will be useful for those both new to or familiar with faceted hypertext systems. Some very basic resources are listed, as well as some very advanced ones. Some example web sites are mentioned, but there is no detailed technical discussion of any software. The user interface to any web site is extremely important, and this is briefly mentioned in two or three places (for example the discussion of lawforwa.org (see Example Web Sites)). The larger question of how to display information graphically and with hypertext is outside the scope of this bibliography. There are five sections: Recommended, Background, Not Relevant, Example Web Sites, and Mailing Lists. Background material is either introductory, advanced, or of peripheral interest, and can be read after the Recommended resources if the reader wants to know more. The Not Relevant category contains articles that may appear in bibliographies but are not relevant for my purposes.

0.011103938 = product of:
  0.055519693 = sum of:
    0.055519693 = weight(_text_:22 in 8460) [ClassicSimilarity], result of:
      0.055519693 = score(doc=8460,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.30952093 = fieldWeight in 8460, 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=8460)
  0.2 = coord(1/5)

Source

Reference services review. 22(1994) no.2, S.31-40

0.011103938 = product of:
  0.055519693 = sum of:
    0.055519693 = weight(_text_:22 in 4226) [ClassicSimilarity], result of:
      0.055519693 = score(doc=4226,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.30952093 = fieldWeight in 4226, 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=4226)
  0.2 = coord(1/5)

Date

13. 6.1996 19:22:20

0.011103938 = product of:
  0.055519693 = sum of:
    0.055519693 = weight(_text_:22 in 7415) [ClassicSimilarity], result of:
      0.055519693 = score(doc=7415,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.30952093 = fieldWeight in 7415, 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=7415)
  0.2 = coord(1/5)

Abstract

State of the art review of natural language processing updating an earlier review published in ARIST 22(1987). Discusses important developments that have allowed for significant advances in the field of natural language processing: materials and resources; knowledge based systems and statistical approaches; and a strong emphasis on evaluation. Reviews some natural language processing applications and common problems still awaiting solution. Considers closely related applications such as language generation and th egeneration phase of machine translation which face the same problems as natural language processing. Covers natural language methodologies for information retrieval only briefly

0.011103938 = product of:
  0.055519693 = sum of:
    0.055519693 = weight(_text_:22 in 152) [ClassicSimilarity], result of:
      0.055519693 = score(doc=152,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.30952093 = fieldWeight in 152, 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=152)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22

0.011103938 = product of:
  0.055519693 = sum of:
    0.055519693 = weight(_text_:22 in 249) [ClassicSimilarity], result of:
      0.055519693 = score(doc=249,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.30952093 = fieldWeight in 249, 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=249)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22

0.011103938 = product of:
  0.055519693 = sum of:
    0.055519693 = weight(_text_:22 in 266) [ClassicSimilarity], result of:
      0.055519693 = score(doc=266,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.30952093 = fieldWeight in 266, 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=266)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22

0.010575616 = product of:
  0.052878078 = sum of:
    0.052878078 = weight(_text_:books in 4283) [ClassicSimilarity], result of:
      0.052878078 = score(doc=4283,freq=2.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.21359414 = fieldWeight in 4283, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.03125 = fieldNorm(doc=4283)
  0.2 = coord(1/5)

Abstract

Information retrieval - the retrieval, primarily, of documents or textual material - is fundamentally a linguistic process. At the very least we must describe what we want and match that description with descriptions of the information that is available to us. Furthermore, when we describe what we want, we must mean something by that description. This is a deceptively simple act, but such linguistic events have been the grist for philosophical analysis since Aristotle. Although there are complexities involved in referring to authors, document types, or other categories of information retrieval context, here I wish to focus an one of the most problematic activities in information retrieval: the description of the intellectual content of information items. And even though I take information retrieval to involve the description and retrieval of written text, what I say here is applicable to any information item whose intellectual content can be described for retrieval-books, documents, images, audio clips, video clips, scientific specimens, engineering schematics, and so forth. For convenience, though, I will refer only to the description and retrieval of documents. The description of intellectual content can go wrong in many obvious ways. We may describe what we want incorrectly; we may describe it correctly but in such general terms that its description is useless for retrieval; or we may describe what we want correctly, but misinterpret the descriptions of available information, and thereby match our description of what we want incorrectly. From a linguistic point of view, we can be misunderstood in the process of retrieval in many ways. Because the philosophy of language deals specifically with how we are understood and mis-understood, it should have some use for understanding the process of description in information retrieval. First, however, let us examine more closely the kinds of misunderstandings that can occur in information retrieval. We use language in searching for information in two principal ways. We use it to describe what we want and to discriminate what we want from other information that is available to us but that we do not want. Description and discrimination together articulate the goals of the information search process; they also delineate the two principal ways in which language can fail us in this process. Van Rijsbergen (1979) was the first to make this distinction, calling them "representation" and "discrimination.""

0.009715946 = product of:
  0.04857973 = sum of:
    0.04857973 = weight(_text_:22 in 5006) [ClassicSimilarity], result of:
      0.04857973 = score(doc=5006,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.2708308 = fieldWeight in 5006, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5006)
  0.2 = coord(1/5)

Date

18. 5.2006 20:06:22

0.009715946 = product of:
  0.04857973 = sum of:
    0.04857973 = weight(_text_:22 in 6084) [ClassicSimilarity], result of:
      0.04857973 = score(doc=6084,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.2708308 = fieldWeight in 6084, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0546875 = fieldNorm(doc=6084)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22

0.009715946 = product of:
  0.04857973 = sum of:
    0.04857973 = weight(_text_:22 in 4309) [ClassicSimilarity], result of:
      0.04857973 = score(doc=4309,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.2708308 = fieldWeight in 4309, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4309)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22

0.009715946 = product of:
  0.04857973 = sum of:
    0.04857973 = weight(_text_:22 in 2092) [ClassicSimilarity], result of:
      0.04857973 = score(doc=2092,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.2708308 = fieldWeight in 2092, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2092)
  0.2 = coord(1/5)

Date

22. 6.2015 16:13:38

0.0083279535 = product of:
  0.041639768 = sum of:
    0.041639768 = weight(_text_:22 in 2548) [ClassicSimilarity], result of:
      0.041639768 = score(doc=2548,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.23214069 = fieldWeight in 2548, 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=2548)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22

0.0083279535 = product of:
  0.041639768 = sum of:
    0.041639768 = weight(_text_:22 in 2608) [ClassicSimilarity], result of:
      0.041639768 = score(doc=2608,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.23214069 = fieldWeight in 2608, 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=2608)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22

0.006939962 = product of:
  0.03469981 = sum of:
    0.03469981 = weight(_text_:22 in 1088) [ClassicSimilarity], result of:
      0.03469981 = score(doc=1088,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.19345059 = fieldWeight in 1088, 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=1088)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22