Search (14 results, page 1 of 1)

0.0028568096 = product of:
  0.028568096 = sum of:
    0.028568096 = weight(_text_:web in 2953) [ClassicSimilarity], result of:
      0.028568096 = score(doc=2953,freq=4.0), product of:
        0.0933738 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.028611459 = queryNorm
        0.3059541 = fieldWeight in 2953, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.046875 = fieldNorm(doc=2953)
  0.1 = coord(1/10)

Abstract

This article presents the process adopted by the France to bring library catalogs to the Web of data and the RDA role in this general strategy. After analising RDA limits and inconsistencies, inherited from the tradition of AACR and MARC21 catalogues, the authors present the French approach to RDA and its positioning in correlation to international standards like ISBD and FRBR. The method adopted in France for FRBRising the catalogues go through a technical work of creating alignment beteween existing data, exploiting the technologies applied to the creation of data.bnf.fr and through a revision of the French cataloguing rules, allowing FRBRised metadata creation. This revision is based on RDA and it is setting up a French RDA application profile, keeping the analysis on the greater differences. RDA adoption, actually, is not a crucial issue in France and not a self standing purpose; it is just a tool for the transition of bibliographic data towards the Web of data.

0.0023567479 = product of:
  0.023567477 = sum of:
    0.023567477 = weight(_text_:web in 5441) [ClassicSimilarity], result of:
      0.023567477 = score(doc=5441,freq=2.0), product of:
        0.0933738 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.028611459 = queryNorm
        0.25239927 = fieldWeight in 5441, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5441)
  0.1 = coord(1/10)

Abstract

Ability to collect time-specific lists of faculty publications has become increasingly important for academic departments. At OHSU publication lists had been retrieved manually by a librarian who conducted literature searches in bibliographic databases. These searches were complicated and time consuming, and the results were large and difficult to assess for accuracy. The OHSU library has built an open web page that allows novices to make very sophisticated institution-specific queries. The tool frees up library staff, provides users with an easy way of retrieving reliable local publication information from PubMed, and gives an opportunity for more sophisticated users to modify the algorithm or dive into the data to better understand nuances from a strong jumping off point.

0.0020200694 = product of:
  0.020200694 = sum of:
    0.020200694 = weight(_text_:web in 2947) [ClassicSimilarity], result of:
      0.020200694 = score(doc=2947,freq=2.0), product of:
        0.0933738 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.028611459 = queryNorm
        0.21634221 = fieldWeight in 2947, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.046875 = fieldNorm(doc=2947)
  0.1 = coord(1/10)

Abstract

The Toolkit designed by the RDA Steering Committee makes Resource Description and Access available on the web, together with other useful documents (workflows, The process of implementation of RDA by Library of Congress, National Agricultural Library, and National Library of Medicine is presented. Each phase of development, test, decision, preparation for implementation of RDA and training about RDA is fully and accurately described and discussed. Benefits from implementation of RDA for the Library of Congress are identified and highlighted: more flexibility in cataloguing decisions, easier international sharing of cataloguing data, clearer linking among related works; closer cooperation with other libraries in the North American community, production of an online learning platform in order to deliver RDA training on a large scale in real time to catalogers.

0.0020200694 = product of:
  0.020200694 = sum of:
    0.020200694 = weight(_text_:web in 2948) [ClassicSimilarity], result of:
      0.020200694 = score(doc=2948,freq=2.0), product of:
        0.0933738 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.028611459 = queryNorm
        0.21634221 = fieldWeight in 2948, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.046875 = fieldNorm(doc=2948)
  0.1 = coord(1/10)

Abstract

RDA Resource Description and Access are guidelines for description and access to resources designed for digital environment and released, in its first version, in 2010. RDA is based on FRBR and its derived models, that focus on users' needs and on resources of any kind of content, medium and carrier. The paper discusses relevance of main features of RDA for the future role of libraries in the context of semantic web and metadata creation and exchange. The paper aims to highlight many consequences deriving from RDA being a content standard, and in particular the change from record management to data management, differences among the two functions realized by RDA (to identify and to relate entities) and functions realized by other standard such as MARC21 (to archive data) and ISB (to visualize data) and show how, as all these functions are necessary for the catalog, RDA needs to be integrated by other rules and standard and that these tools allow the fulfilment of the variation principle defined by S.R. Ranganathan.

0.0020200694 = product of:
  0.020200694 = sum of:
    0.020200694 = weight(_text_:web in 2951) [ClassicSimilarity], result of:
      0.020200694 = score(doc=2951,freq=2.0), product of:
        0.0933738 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.028611459 = queryNorm
        0.21634221 = fieldWeight in 2951, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.046875 = fieldNorm(doc=2951)
  0.1 = coord(1/10)

Abstract

This article attempts to clarify the nature of the relationship between the RDA and ISBD standards in order to be able to understand their differences and vinculations, as well as to remove some misinterpretations about this relationship. With this objective, some aspects that can affect their differences, such as types of standards, points of view, scope, origin, policies of the creation and development group or organization in charge that logically justify these differences, are analyzed. These have not presented any obstacles for a correct relationship with the help of the Linked Data technology. In this article, account is also given of the work done of mappings and alignments between the standards in order to contribute properly to the Semantic Web. This knowledge is the one fundamental required for current catalogers to use standards judiciously, knowledgeably and responsibly.

0.0020200694 = product of:
  0.020200694 = sum of:
    0.020200694 = weight(_text_:web in 2959) [ClassicSimilarity], result of:
      0.020200694 = score(doc=2959,freq=2.0), product of:
        0.0933738 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.028611459 = queryNorm
        0.21634221 = fieldWeight in 2959, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.046875 = fieldNorm(doc=2959)
  0.1 = coord(1/10)

Abstract

RIMMF software is grew out of the need to visualize and realize records according to the RDA guidelines. The article describes the software structure and features in the creation of a r­ball, that is a small database populated by recordings of bibliographic and authority resources enriched by relationships between and among entities involved. At first it's introduced the need that led to RIMMF outcome, then starts the software functional analysis. With a description of the main steps of the r-ball building, emphasizing the issues raised. The results highlights some critical aspects, but above all the wide scope of possible developments that open the Cultural Heritage Institutions horizon to the web prospective. Conclusions display the RDF-linked­data development of the RIMMF incoming future.

0.0020200694 = product of:
  0.020200694 = sum of:
    0.020200694 = weight(_text_:web in 3523) [ClassicSimilarity], result of:
      0.020200694 = score(doc=3523,freq=2.0), product of:
        0.0933738 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.028611459 = queryNorm
        0.21634221 = fieldWeight in 3523, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.046875 = fieldNorm(doc=3523)
  0.1 = coord(1/10)

Abstract

On December 12, 2016, Carl Stahmer and MacKenzie Smith presented at the CNI Members Fall Meeting about the BIBFLOW project, self-described on Twitter as "a two-year project of the UC Davis University Library and Zepheira investigating the future of library technical services." In her opening remarks, Ms. Smith, University Librarian at UC Davis, stated that one of the goals of the project was to devise a roadmap "to get from where we are today, which is kind of the 1970s with a little lipstick on it, to 2020, which is where we're going to be very soon." The notion that where libraries are today is somehow behind the times is one of the commonly heard rationales behind a move to linked data. Stated more precisely: - Libraries devote considerable time and resources to producing high-quality bibliographic metadata - This metadata is stored in unconnected silos - This metadata is in a format (MARC) that is incompatible with technologies of the emerging Semantic Web - The visibility of library metadata is diminished as a result of the two points above Are these assertions true? If yes, is linked data the solution?

0.0016833913 = product of:
  0.016833913 = sum of:
    0.016833913 = weight(_text_:web in 2277) [ClassicSimilarity], result of:
      0.016833913 = score(doc=2277,freq=2.0), product of:
        0.0933738 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.028611459 = queryNorm
        0.18028519 = fieldWeight in 2277, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2277)
  0.1 = coord(1/10)

Theme

Semantic Web

0.0016833913 = product of:
  0.016833913 = sum of:
    0.016833913 = weight(_text_:web in 2952) [ClassicSimilarity], result of:
      0.016833913 = score(doc=2952,freq=2.0), product of:
        0.0933738 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.028611459 = queryNorm
        0.18028519 = fieldWeight in 2952, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2952)
  0.1 = coord(1/10)

Abstract

The Toolkit designed by the RDA Steering Committee makes Resource Description and Access available on the web, together with other useful documents (workflows, mappings, etc.). Reading, learning and memorizing are interconnected, and a working tool should make these activities faster and easier to perform. Some issues arise while verifying the real easiness of use and learning of the tool. The practical and formal requirements for a cataloguing code include plain language, ease of memorisation, clarity of instructions, familiarity for users, predictability and reproducibility of solutions, and general usability. From a formal point of view, the RDA text does not appear to be conceived for an uninterrupted reading, but just for reading of few paragraphs for temporary catalographic needs. From a content point of view, having a syndetic view of the description of a resource is rather difficult: catalographic details are scattered and their re-organization is not easy. The visualisation and logical organisation in the Toolkit could be improved: the table of contents occupies a sizable portion of the screen and resizing or hiding it is not easy; the indentation leaves little space to the words; inhomogeneous font styles (italic and bold) and poor contrast between background and text colours make reading not easy; simultaneous visualization of two or more parts of the text is not allowed; and Toolkit's icons are less intuitive than expected. In the conclusion, some suggestions on how to improve the Toolkit's aspects and usability are provided.

9.1271737E-4 = product of:
  0.009127174 = sum of:
    0.009127174 = product of:
      0.027381519 = sum of:
        0.027381519 = weight(_text_:29 in 5348) [ClassicSimilarity], result of:
          0.027381519 = score(doc=5348,freq=2.0), product of:
            0.10064617 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.028611459 = queryNorm
            0.27205724 = fieldWeight in 5348, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5348)
      0.33333334 = coord(1/3)
  0.1 = coord(1/10)

Date

10.11.2018 16:29:37

7.823291E-4 = product of:
  0.007823291 = sum of:
    0.007823291 = product of:
      0.023469873 = sum of:
        0.023469873 = weight(_text_:29 in 1152) [ClassicSimilarity], result of:
          0.023469873 = score(doc=1152,freq=2.0), product of:
            0.10064617 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.028611459 = queryNorm
            0.23319192 = fieldWeight in 1152, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.046875 = fieldNorm(doc=1152)
      0.33333334 = coord(1/3)
  0.1 = coord(1/10)

Date

26.12.2011 16:29:28

7.752915E-4 = product of:
  0.0077529154 = sum of:
    0.0077529154 = product of:
      0.023258746 = sum of:
        0.023258746 = weight(_text_:22 in 2946) [ClassicSimilarity], result of:
          0.023258746 = score(doc=2946,freq=2.0), product of:
            0.10019246 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.028611459 = queryNorm
            0.23214069 = fieldWeight in 2946, 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=2946)
      0.33333334 = coord(1/3)
  0.1 = coord(1/10)

Date

17. 5.2016 19:22:40

6.51941E-4 = product of:
  0.00651941 = sum of:
    0.00651941 = product of:
      0.019558229 = sum of:
        0.019558229 = weight(_text_:29 in 3373) [ClassicSimilarity], result of:
          0.019558229 = score(doc=3373,freq=2.0), product of:
            0.10064617 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.028611459 = queryNorm
            0.19432661 = fieldWeight in 3373, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3373)
      0.33333334 = coord(1/3)
  0.1 = coord(1/10)

Date

31. 1.2017 13:29:56

5.2155275E-4 = product of:
  0.0052155275 = sum of:
    0.0052155275 = product of:
      0.015646582 = sum of:
        0.015646582 = weight(_text_:29 in 1183) [ClassicSimilarity], result of:
          0.015646582 = score(doc=1183,freq=2.0), product of:
            0.10064617 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.028611459 = queryNorm
            0.15546128 = fieldWeight in 1183, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03125 = fieldNorm(doc=1183)
      0.33333334 = coord(1/3)
  0.1 = coord(1/10)

Date

26.12.2011 14:08:29