Search (2 results, page 1 of 1)

0.011183213 = product of:
  0.03354964 = sum of:
    0.03354964 = weight(_text_:search in 2436) [ClassicSimilarity], result of:
      0.03354964 = score(doc=2436,freq=2.0), product of:
        0.1747324 = queryWeight, product of:
          3.475677 = idf(docFreq=3718, maxDocs=44218)
          0.05027291 = queryNorm
        0.19200584 = fieldWeight in 2436, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.475677 = idf(docFreq=3718, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2436)
  0.33333334 = coord(1/3)

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.

0.0089465715 = product of:
  0.026839713 = sum of:
    0.026839713 = weight(_text_:search in 2429) [ClassicSimilarity], result of:
      0.026839713 = score(doc=2429,freq=2.0), product of:
        0.1747324 = queryWeight, product of:
          3.475677 = idf(docFreq=3718, maxDocs=44218)
          0.05027291 = queryNorm
        0.15360467 = fieldWeight in 2429, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.475677 = idf(docFreq=3718, maxDocs=44218)
          0.03125 = fieldNorm(doc=2429)
  0.33333334 = coord(1/3)

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.