Search (226 results, page 12 of 12)

1.9733087E-4 = product of:
  0.002959963 = sum of:
    0.002959963 = product of:
      0.005919926 = sum of:
        0.005919926 = weight(_text_:information in 5383) [ClassicSimilarity], result of:
          0.005919926 = score(doc=5383,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.116372846 = fieldWeight in 5383, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.046875 = fieldNorm(doc=5383)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

State of the art review of hypertext systems in use in UK libraries. Systems include public access point of information (POI) systems that provide guidance to users of local resources, and networked document retrieval systems, such as WWW, that enable users to access texts stored on machines linked by the Internet. Particular emphasis is placed on those systems that are produced inhouse by the libraries in which they are used. The review is based on a series of telephone or face to face interviews conducted with representatives of those organizations that a literature review and mailed questionnaire survey identified as current users of hypertext. Considers issues relating to system development and usability, and presents a set of appropriate guidelines for the designers of future systems. Concludes that: the principle application of hypertext systems in UK libraries is in the implementation of POI systems; that such development is most advanced in the academic sector; and that such development is set to increase in tandem with use of the WWW

1.8604532E-4 = product of:
  0.0027906797 = sum of:
    0.0027906797 = product of:
      0.0055813594 = sum of:
        0.0055813594 = weight(_text_:information in 2429) [ClassicSimilarity], result of:
          0.0055813594 = score(doc=2429,freq=4.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.10971737 = fieldWeight in 2429, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.03125 = fieldNorm(doc=2429)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

Our catalog should not be called a FRBR catalog perhaps, but instead a "FRBR Inspired catalog." As such our main goal has been "practical findability," we are seeking to support the four identified user tasks of the FRBR model, or to "Search, Identify, Select, and Obtain," rather than to create a FRBR catalog, per se. By encoding as much information as possible in the MODS and MADS records we have created, we believe that useful searching will be supported, that by using unique identifiers for works and authors users will be able to identify that the entity they have located is the desired one, that by encoding expression level information (such as the language of the work, the translator, etc) users will be able to select which expression of a work they are interested in, and that by supplying links to different online manifestations that users will be able to obtain access to a digital copy of a work. This white paper will discuss previous and current efforts by the Perseus Project in creating a FRBRized catalog, including the cataloging workflow, lessons learned during the process and will also seek to place this work in the larger context of research regarding FRBR, cataloging, Library 2.0 and the Semantic Web, and the growing importance of the FRBR model in the face of growing million book digital libraries.

1.6444239E-4 = product of:
  0.0024666358 = sum of:
    0.0024666358 = product of:
      0.0049332716 = sum of:
        0.0049332716 = weight(_text_:information in 2436) [ClassicSimilarity], result of:
          0.0049332716 = score(doc=2436,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.09697737 = fieldWeight in 2436, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2436)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

RDA provides a set of guidelines and instructions on formulating data to support resource discovery. The data created using RDA to describe a resource are designed to assist users performing the following tasks: find-i.e., to find resources that correspond to the user's stated search criteria: identify-i.e., to confirm that the resource described corresponds to the resource sought, or to distinguish between two or more resources with similar characteristics select-i.e., to select a resource that is appropriate to the user's needs obtain-i.e., to acquire or access the resource described. The data created using RDA to describe an entity associated with a resource (a person, family, corporate body, concept, etc.) are designed to assist users performing the following tasks: find-i.e., to find information on that entity and on resources associated with the entity identify-i.e., to confirm that the entity described corresponds to the entity sought, or to distinguish between two or more entities with similar names, etc. clarify-i.e., to clarify the relationship between two or more such entities, or to clarify the relationship between the entity described and a name by which that entity is known understand-i.e., to understand why a particular name or title, or form of name or title, has been chosen as the preferred name or title for the entity.

1.6444239E-4 = product of:
  0.0024666358 = sum of:
    0.0024666358 = product of:
      0.0049332716 = sum of:
        0.0049332716 = weight(_text_:information in 906) [ClassicSimilarity], result of:
          0.0049332716 = score(doc=906,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.09697737 = fieldWeight in 906, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0390625 = fieldNorm(doc=906)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

The need for improved semantic in teroperability between and among vocabularies and knowledge organization schemes is undeniable and growing in importance. There is an ever-increasing need to create an environment by which even multiple portals could be accessed via subject metadata using software that is neutral and available ubiquitously or directly to the user, that could be copied by libraries for use in their own environment. In order to develop or improve a knowledge organization system including emerging options in semantic interoperability, scholars and practitioners need to be able to evaluate a wide variety of projects and stay current with the professional literature. Based on its findings, the Subcommittee concludes that the development of a successful subject semantic interoperability project is a long and difficult process. It requires a substantial investment of financial, human and computer resources. The Subcommittee recommends using the information and tools in this report and its appendices to assist in developing a successful project incorporating subject semantic interoperability. Finally the Subcommittee concludes that since this field of endeavor is still relatively young and immature, it is too early to generate a set of Best Practices that could be used in developing a successful project. We are past the theoretical and basic research phase and into the development phase. Even though there are some successful projects in full production, more projects need to reach maturity and much more research needs to be done.

1.6444239E-4 = product of:
  0.0024666358 = sum of:
    0.0024666358 = product of:
      0.0049332716 = sum of:
        0.0049332716 = weight(_text_:information in 2398) [ClassicSimilarity], result of:
          0.0049332716 = score(doc=2398,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.09697737 = fieldWeight in 2398, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2398)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

It may be jumping the gun a bit to review this publication before it is actually published, but we are nothing if not current here at Current Cites, so we will do it anyway (so sue us!). This publication-in-process is a joint effort of the Visual Resources Association and the Digital Library Federation. It aims to "provide guidelines for selecting, ordering, and formatting data used to populate catalog records" relating to cultural works. Although this work is far from finished (Chapters 1, 2, 7, and 9 are available, as well as front and back matter), the authors are making it available so pratictioners can use it and respond with information about how it can be improved to better aid their work. A stated goal is to publish it in print at some point in the future. Besides garnering support from the organizations named above as well as the Getty, the Mellon Foundation and others, the effort is being guided by experienced professionals at the top of their field. Get the point? If you're involved with creating metadata relating to any type of cultural object and/or images of such, this will need to be either on your bookshelf, or bookmarked in your browser, or both

1.1510967E-4 = product of:
  0.001726645 = sum of:
    0.001726645 = product of:
      0.00345329 = sum of:
        0.00345329 = weight(_text_:information in 6067) [ClassicSimilarity], result of:
          0.00345329 = score(doc=6067,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.06788416 = fieldWeight in 6067, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.02734375 = fieldNorm(doc=6067)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Footnote

Vgl. auch: http://www.bl.uk/information/finrap3.html