Search (4 results, page 1 of 1)

  • × author_ss:"Coyle, K."
  • × theme_ss:"Formalerschließung"
  • × type_ss:"a"
  1. Coyle, K.: Future considerations : the functional library systems record (2004) 0.03
    0.031588875 = product of:
      0.06317775 = sum of:
        0.06317775 = sum of:
          0.013257373 = weight(_text_:a in 562) [ClassicSimilarity], result of:
            0.013257373 = score(doc=562,freq=12.0), product of:
              0.053105544 = queryWeight, product of:
                1.153047 = idf(docFreq=37942, maxDocs=44218)
                0.046056706 = queryNorm
              0.24964198 = fieldWeight in 562, product of:
                3.4641016 = tf(freq=12.0), with freq of:
                  12.0 = termFreq=12.0
                1.153047 = idf(docFreq=37942, maxDocs=44218)
                0.0625 = fieldNorm(doc=562)
          0.04992038 = weight(_text_:22 in 562) [ClassicSimilarity], result of:
            0.04992038 = score(doc=562,freq=2.0), product of:
              0.16128273 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.046056706 = queryNorm
              0.30952093 = fieldWeight in 562, 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=562)
      0.5 = coord(1/2)
    
    Abstract
    The paper performs a thought experiment on the concept of a record based on the Functional Requirements for Bibliographic Records and library system functions, and concludes that if we want to develop a functional bibliographic record we need to do it within the context of a flexible, functional library systems record structure. The article suggests a new way to look at the library systems record that would allow libraries to move forward in terms of technology but also in terms of serving library users.
    Source
    Library hi tech. 22(2004) no.2, S.166-174
    Type
    a
  2. Coyle, K.: Simplicity in data models (2015) 0.00
    0.002269176 = product of:
      0.004538352 = sum of:
        0.004538352 = product of:
          0.009076704 = sum of:
            0.009076704 = weight(_text_:a in 2025) [ClassicSimilarity], result of:
              0.009076704 = score(doc=2025,freq=10.0), product of:
                0.053105544 = queryWeight, product of:
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.046056706 = queryNorm
                0.1709182 = fieldWeight in 2025, product of:
                  3.1622777 = tf(freq=10.0), with freq of:
                    10.0 = termFreq=10.0
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.046875 = fieldNorm(doc=2025)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Evolving from database models using punch cards, strict linear relational databases and predefined object-oriented data structures, the triple statements underlying Semantic Web technologies bypass many design constraints to offer endless flexibility. Overcoming structure is challenging, especially the relatively recent structure formalized in the Functional Requirements for Bibliographic Records (FRBR). Though geared to easier access and interoperability and recognizing a multilevel bibliographic model, FRBR remains tied to translating entity-relation diagrams to data structures. Resource Description Framework (RDF) provides a more flexible way to express concepts, in which bibliographic models may be thought of as graphs of properties and relationships. But even RDF-based models can undermine that flexibility by mixing concept classes and data structures. The advantage of RDF classes is to provide semantics that enable a user to focus on similarities, not bound by contextual constraints.and success metrics.
    Footnote
    Contribution to a special section "Linked data and the charm of weak semantics".
    Type
    a
  3. Coyle, K.; Hillmann, D.: Resource Description and Access (RDA) : cataloging rules for the 20th century (2007) 0.00
    0.0020714647 = product of:
      0.0041429293 = sum of:
        0.0041429293 = product of:
          0.008285859 = sum of:
            0.008285859 = weight(_text_:a in 2525) [ClassicSimilarity], result of:
              0.008285859 = score(doc=2525,freq=12.0), product of:
                0.053105544 = queryWeight, product of:
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.046056706 = queryNorm
                0.15602624 = fieldWeight in 2525, product of:
                  3.4641016 = tf(freq=12.0), with freq of:
                    12.0 = termFreq=12.0
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=2525)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    There is evidence that many individuals and organizations in the library world do not support the work taking place to develop a next generation of the library cataloging rules. The authors describe the tensions existing between those advocating an incremental change to cataloging process and others who desire a bolder library entry into the digital era. Libraries have lost their place as primary information providers, surpassed by more agile (and in many cases wealthier) purveyors of digital information delivery services. Although libraries still manage materials that are not available elsewhere, the library's approach to user service and the user interface is not competing successfully against services like Amazon or Google. If libraries are to avoid further marginalization, they need to make a fundamental change in their approach to user services. The library's signature service, its catalog, uses rules for cataloging that are remnants of a long departed technology: the card catalog. Modifications to the rules, such as those proposed by the Resource Description and Access (RDA) development effort, can only keep us rooted firmly in the 20th, if not the 19th century. A more radical change is required that will contribute to the library of the future, re-imagined and integrated with the chosen workflow of its users.
    Type
    a
  4. Coyle, K.: FRBR, twenty years on (2015) 0.00
    0.0020506454 = product of:
      0.004101291 = sum of:
        0.004101291 = product of:
          0.008202582 = sum of:
            0.008202582 = weight(_text_:a in 2174) [ClassicSimilarity], result of:
              0.008202582 = score(doc=2174,freq=6.0), product of:
                0.053105544 = queryWeight, product of:
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.046056706 = queryNorm
                0.1544581 = fieldWeight in 2174, product of:
                  2.4494898 = tf(freq=6.0), with freq of:
                    6.0 = termFreq=6.0
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=2174)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    The article analyzes the conceptual model of the Functional Requirements for Bibliographic Records (FRBR) as a general model of bibliographic data and description that can be interpreted, as needed, to serve the needs of various communities. This is illustrated with descriptions of five different implementations based on the concepts in FRBR: FRBRER (entity-relation), FRBROO (object oriented), FRBRCore (FRBR entities as linked data), (FRBR entities within the commerce model), and FaBiO (FRBR indecs as a basis for academic document types). The author argues that variant models show the strength of the FRBR concepts, and should be encouraged.
    Type
    a