Search (63 results, page 1 of 4)

0.04298305 = product of:
  0.064474575 = sum of:
    0.04744636 = weight(_text_:search in 2422) [ClassicSimilarity], result of:
      0.04744636 = score(doc=2422,freq=4.0), product of:
        0.1747324 = queryWeight, product of:
          3.475677 = idf(docFreq=3718, maxDocs=44218)
          0.05027291 = queryNorm
        0.27153727 = fieldWeight in 2422, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.475677 = idf(docFreq=3718, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2422)
    0.017028214 = product of:
      0.03405643 = sum of:
        0.03405643 = weight(_text_:22 in 2422) [ClassicSimilarity], result of:
          0.03405643 = score(doc=2422,freq=2.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.19345059 = fieldWeight in 2422, 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=2422)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

Abstract

Catalogs have for centuries been the main tool that enabled users to search for items in a library by author, title, or subject. A catalog can be interpreted as a set of bibliographic records, where each record acts as a surrogate for a publication. Every record describes a specific publication and contains the data that is used to create the indexes of search systems and the information that is presented to the user. Bibliographic records are often captured and exchanged by the use of the MARC format. Although there are numerous rdquodialectsrdquo of the MARC format in use, they are usually crafted on the same basis and are interoperable with each other -to a certain extent. The data model of a MARC-based catalog, however, is rdquo[...] extremely non-normalized with excessive replication of datardquo [1]. For instance, a literary work that exists in numerous editions and translations is likely to yield a large result set because each edition or translation is represented by an individual record, that is unrelated to other records that describe the same work.

Source

Research and advanced technology for digital libraries : 7th European Conference, proceedings / ECDL 2003, Trondheim, Norway, August 17-22, 2003

0.037582483 = product of:
  0.056373723 = sum of:
    0.03486581 = weight(_text_:search in 1169) [ClassicSimilarity], result of:
      0.03486581 = score(doc=1169,freq=6.0), product of:
        0.1747324 = queryWeight, product of:
          3.475677 = idf(docFreq=3718, maxDocs=44218)
          0.05027291 = queryNorm
        0.19953834 = fieldWeight in 1169, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          3.475677 = idf(docFreq=3718, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1169)
    0.021507913 = product of:
      0.043015826 = sum of:
        0.043015826 = weight(_text_:engines in 1169) [ClassicSimilarity], result of:
          0.043015826 = score(doc=1169,freq=2.0), product of:
            0.25542772 = queryWeight, product of:
              5.080822 = idf(docFreq=746, maxDocs=44218)
              0.05027291 = queryNorm
            0.16840704 = fieldWeight in 1169, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.080822 = idf(docFreq=746, maxDocs=44218)
              0.0234375 = fieldNorm(doc=1169)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

Abstract

T.1: Today's thesauri are mostly electronic tools, having moved on from the paper-based era when thesaurus standards were first developed. They are built and maintained with the support of software and need to integrate with other software, such as search engines and content management systems. Whereas in the past thesauri were designed for information professionals trained in indexing and searching, today there is a demand for vocabularies that untrained users will find to be intuitive. ISO 25964 makes the transition needed for the world of electronic information management. However, part 1 retains the assumption that human intellect is usually involved in the selection of indexing terms and in the selection of search terms. If both the indexer and the searcher are guided to choose the same term for the same concept, then relevant documents will be retrieved. This is the main principle underlying thesaurus design, even though a thesaurus built for human users may also be applied in situations where computers make the choices. Efficient exchange of data is a vital component of thesaurus management and exploitation. Hence the inclusion in this standard of recommendations for exchange formats and protocols. Adoption of these will facilitate interoperability between thesaurus management systems and the other computer applications, such as indexing and retrieval systems, that will utilize the data. Thesauri are typically used in post-coordinate retrieval systems, but may also be applied to hierarchical directories, pre-coordinate indexes and classification systems. Increasingly, thesaurus applications need to mesh with others, such as automatic categorization schemes, free-text search systems, etc. Part 2 of ISO 25964 describes additional types of structured vocabulary and gives recommendations to enable interoperation of the vocabularies at all stages of the information storage and retrieval process.

0.019265227 = product of:
  0.057795677 = sum of:
    0.057795677 = product of:
      0.115591355 = sum of:
        0.115591355 = weight(_text_:22 in 5743) [ClassicSimilarity], result of:
          0.115591355 = score(doc=5743,freq=4.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.6565931 = fieldWeight in 5743, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=5743)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

30. 3.2002 19:45:22

Source

Revista Española de Documentaçion Cientifica. 22(1999) no.2, S.198-219

0.01816343 = product of:
  0.054490287 = sum of:
    0.054490287 = product of:
      0.10898057 = sum of:
        0.10898057 = weight(_text_:22 in 2840) [ClassicSimilarity], result of:
          0.10898057 = score(doc=2840,freq=2.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.61904186 = fieldWeight in 2840, 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=2840)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Source

Library hi tech. 22(2004) no.1

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

Abstract

Discusses standards related to the USMARC holdings format. Considers issues of concern surrounding the following standards: Z39.71, the proposed standard for holdings statements for bibliographic items; Z39.50, the standard for intersystem search and retrieval; and X12, the national standard for the transmission of business data. Aslo discusses the relationship between EDI and the USMARC holdings format. Work is currently in progress to update the holdings format

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

Abstract

Contribution to an issue devoted to serials and reference services. Familiarity with the basic elements of the MARC format and their effect on the display and retrieval of bibliographic data is an essential element of public service in those libraries with MARC-based on-line catalogues. Describes the components of a MARC record. To successfully retrieve the information sought from an on-line catalogue, the catalogue user must know whether it is in an indexed field and, if so, must be familiar with the search strategies required by the system.

0.015893001 = product of:
  0.047679 = sum of:
    0.047679 = product of:
      0.095358 = sum of:
        0.095358 = weight(_text_:22 in 7196) [ClassicSimilarity], result of:
          0.095358 = score(doc=7196,freq=2.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.5416616 = fieldWeight in 7196, 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=7196)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Source

Library hi tech. 22(2004) no.1

0.015893001 = product of:
  0.047679 = sum of:
    0.047679 = product of:
      0.095358 = sum of:
        0.095358 = weight(_text_:22 in 4973) [ClassicSimilarity], result of:
          0.095358 = score(doc=4973,freq=2.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.5416616 = fieldWeight in 4973, 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=4973)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

26. 8.2000 19:22:35

0.015893001 = product of:
  0.047679 = sum of:
    0.047679 = product of:
      0.095358 = sum of:
        0.095358 = weight(_text_:22 in 6838) [ClassicSimilarity], result of:
          0.095358 = score(doc=6838,freq=2.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.5416616 = fieldWeight in 6838, 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=6838)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Source

Dialog mit Bibliotheken. 13(2001) H.3, S.20-22

0.015893001 = product of:
  0.047679 = sum of:
    0.047679 = product of:
      0.095358 = sum of:
        0.095358 = weight(_text_:22 in 2841) [ClassicSimilarity], result of:
          0.095358 = score(doc=2841,freq=2.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.5416616 = fieldWeight in 2841, 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=2841)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Source

Library hi tech. 22(2004) no.2

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

Abstract

Electronic documents are creating new services and generating new demands, with consequent impacts on the means of transmitting knowledge, international standards and democratisation of access. Universal bibliographic control depends on common rules for bibliographic description and format to ensure compatibility and exchange. In addition to ISBN and UNIMARC for cataloguing, Z39.50 allows searching of heterogeneous databases and SGML makes cataloguing in publication a reality. Such developments must be based on knowledge of what users want and their real search and consultation practices, not what the system devisers have the technology to create

0.013622571 = product of:
  0.040867712 = sum of:
    0.040867712 = product of:
      0.081735425 = sum of:
        0.081735425 = weight(_text_:22 in 6077) [ClassicSimilarity], result of:
          0.081735425 = score(doc=6077,freq=2.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.46428138 = fieldWeight in 6077, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=6077)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

2. 8.2001 16:22:33

0.012843484 = product of:
  0.03853045 = sum of:
    0.03853045 = product of:
      0.0770609 = sum of:
        0.0770609 = weight(_text_:22 in 2408) [ClassicSimilarity], result of:
          0.0770609 = score(doc=2408,freq=4.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.4377287 = fieldWeight in 2408, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=2408)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

13. 1.2007 18:31:22

Source

Cataloging and classification quarterly. 22(1996) nos.3/4, S.43-58

0.012843484 = product of:
  0.03853045 = sum of:
    0.03853045 = product of:
      0.0770609 = sum of:
        0.0770609 = weight(_text_:22 in 2845) [ClassicSimilarity], result of:
          0.0770609 = score(doc=2845,freq=4.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.4377287 = fieldWeight in 2845, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=2845)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

9.12.2005 19:22:38

Source

Library hi tech. 22(2004) no.2, S.175-181

0.011352143 = product of:
  0.03405643 = sum of:
    0.03405643 = product of:
      0.06811286 = sum of:
        0.06811286 = weight(_text_:22 in 5228) [ClassicSimilarity], result of:
          0.06811286 = score(doc=5228,freq=2.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.38690117 = fieldWeight in 5228, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=5228)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

29. 9.1996 18:58:22

0.011352143 = product of:
  0.03405643 = sum of:
    0.03405643 = product of:
      0.06811286 = sum of:
        0.06811286 = weight(_text_:22 in 1544) [ClassicSimilarity], result of:
          0.06811286 = score(doc=1544,freq=2.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.38690117 = fieldWeight in 1544, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=1544)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

22. 3.2016 12:15:46

0.011238049 = product of:
  0.033714145 = sum of:
    0.033714145 = product of:
      0.06742829 = sum of:
        0.06742829 = weight(_text_:22 in 5100) [ClassicSimilarity], result of:
          0.06742829 = score(doc=5100,freq=4.0), product of:
            0.17604718 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05027291 = queryNorm
            0.38301262 = fieldWeight in 5100, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5100)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

11. 9.1996 19:22:20

Source

Literacy: traditional, cultural, technological. Proceedings of the 23rd Annual Conference of the International Association of School Librarianship (selected papers), Pittsburgh, Pennsylvania, Pittsburgh University, School of Library and Information Science, 17-22 Jul 94

0.011183213 = product of:
  0.03354964 = sum of:
    0.03354964 = weight(_text_:search in 3033) [ClassicSimilarity], result of:
      0.03354964 = score(doc=3033,freq=2.0), product of:
        0.1747324 = queryWeight, product of:
          3.475677 = idf(docFreq=3718, maxDocs=44218)
          0.05027291 = queryNorm
        0.19200584 = fieldWeight in 3033, 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=3033)
  0.33333334 = coord(1/3)

Abstract

In this paper I describe a conceptual design of a bibliographic retrieval system that enables more thourough control of bibliographic entities. A bibliographic entity has 2 components: the intellectual work and the physical item. Users searching bibliographic retrieval systems generally do not search for a specific item, but are willing to retrieve one of several alternative manifestations of a work. However, contemporary bibliographic retrieval systems are based solely on the descriptions of items. Works are described only implcitly by collocating descriptions of items. This method has resulted in a tool that does not include important descriptive attributes of the work, e.g. information regarding its history, its genre, or its bibliographic relationships. A bibliographic relationship is an association between 2 bibliographic entities. A system evaluation methodology wasused to create a conceptual schema for a bibliographic retrieval system. The model is based upon an analysis of data elements in the USMARC Formats for Bibliographic Data. The conceptual schema describes a database comprising 2 separate files of bibliographic descriptions, one of works and the other of items. Each file consists of individual descriptive surrogates of their respective entities. the specific data content of each file is defined by a data dictionary. Data elements used in the description of bibliographic works reflect the nature of works as intellectual and linguistic objects. The descriptive elements of bibliographic items describe the physical properties of bibliographic entities. Bibliographic relationships constitute the logical strucutre of the database

0.011183213 = product of:
  0.03354964 = sum of:
    0.03354964 = weight(_text_:search in 133) [ClassicSimilarity], result of:
      0.03354964 = score(doc=133,freq=2.0), product of:
        0.1747324 = queryWeight, product of:
          3.475677 = idf(docFreq=3718, maxDocs=44218)
          0.05027291 = queryNorm
        0.19200584 = fieldWeight in 133, 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=133)
  0.33333334 = coord(1/3)

Abstract

This paper describes an experiment exploring the hypothesis that innovative application of the Functional Require-ments for Bibliographic Records (FRBR) principles can complement traditional bibliographic resource discovery systems in order to improve the user experience. A specialized service was implemented that, when given a plain list of results from a regular online catalogue, was able to process, enrich and present that list in a more relevant way for the user. This service pre-processes the records of a traditional online catalogue in order to build a semantic structure following the FRBR model. The service also explores web search features that have been revolutionizing the way users conceptualize resource discovery, such as relevance ranking and metasearching. This work was developed in the context of the TELPlus project. We processed nearly one hundred thousand bibliographic and authority records, in multiple languages, and originating from twelve European na-tional libraries. This paper describes the architecture of the service and the main challenges faced, especially concerning the extraction and linking of the relevant FRBR entities from the bibliographic metadata produced by the libraries. The service was evaluated by end users, who filled out a questionnaire after using a traditional online catalogue and the new service, both with the same bibliographic collection. The analysis of the results supports the hypothesis that FRBR can be implemented for re-source discovery in a non-intrusive way, reusing the data of any existing traditional bibliographic system.

0.011183213 = product of:
  0.03354964 = sum of:
    0.03354964 = weight(_text_:search in 5172) [ClassicSimilarity], result of:
      0.03354964 = score(doc=5172,freq=2.0), product of:
        0.1747324 = queryWeight, product of:
          3.475677 = idf(docFreq=3718, maxDocs=44218)
          0.05027291 = queryNorm
        0.19200584 = fieldWeight in 5172, 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=5172)
  0.33333334 = coord(1/3)

Abstract

One of the big challenges facing academic libraries today is to increase the relevance of the libraries to their user communities. If the libraries can increase the visibility of their resources on the open web, it will increase the chances of the libraries to reach to their user communities via the user's first search experience. BIBFRAME and library Linked Data will enable libraries to publish their resources in a way that the Web understands, consume Linked Data to enrich their resources relevant to the libraries' user communities, and visualize networks across collections. However, one of the important steps for transitioning to BIBFRAME and library Linked Data involves crosswalks, mapping MARC fields and subfields across data models and performing necessary data reformatting to be in compliance with the specifications of the new model, which is currently BIBFRAME 2.0. This article looks into how the Library of Congress has mapped library bibliographic data from the MARC format to the BIBFRAME 2.0 model and vocabulary published and updated since April 2016, available from http://www.loc.gov/bibframe/docs/index.html based on the recently released conversion specifications and converter, developed by the Library of Congress with input from many community members. The BIBFRAME 2.0 standard and conversion tools will enable libraries to transform bibliographic data from MARC into BIBFRAME 2.0, which introduces a Linked Data model as the improved method of bibliographic control for the future, and make bibliographic information more useful within and beyond library communities.