Search (7 results, page 1 of 1)

  • × author_ss:"Panzer, M."
  1. Green, R.; Panzer, M.: ¬The ontological character of classes in the Dewey Decimal Classification 0.02 
    0.020736888 = product of:
  0.08294755 = sum of:
    0.08294755 = weight(_text_:headings in 3530) [ClassicSimilarity], result of:
      0.08294755 = score(doc=3530,freq=2.0), product of:
        0.22113821 = queryWeight, product of:
          4.849944 = idf(docFreq=940, maxDocs=44218)
          0.045596033 = queryNorm
        0.37509373 = fieldWeight in 3530, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.849944 = idf(docFreq=940, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3530)
  0.25 = coord(1/4)
    Abstract
    Classes in the Dewey Decimal Classification (DDC) system function as neighborhoods around focal topics in captions and notes. Topical neighborhoods are generated through specialization and instantiation, complex topic synthesis, index terms and mapped headings, hierarchical force, rules for choosing between numbers, development of the DDC over time, and use of the system in classifying resources. Implications of representation using a formal knowledge representation language are explored.
  2. Panzer, M.: Increasing patient findability of medical research : annotating clinical trials using standard vocabularies (2017) 0.01 
    0.014869518 = product of:
  0.05947807 = sum of:
    0.05947807 = product of:
      0.11895614 = sum of:
        0.11895614 = weight(_text_:terminology in 2783) [ClassicSimilarity], result of:
          0.11895614 = score(doc=2783,freq=4.0), product of:
            0.24053115 = queryWeight, product of:
              5.2752647 = idf(docFreq=614, maxDocs=44218)
              0.045596033 = queryNorm
            0.49455607 = fieldWeight in 2783, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              5.2752647 = idf(docFreq=614, maxDocs=44218)
              0.046875 = fieldNorm(doc=2783)
      0.5 = coord(1/2)
  0.25 = coord(1/4)
    Abstract
    Multiple groups at Mayo Clinic organize knowledge with the aid of metadata for a variety of purposes. The ontology group focuses on consumer-oriented health information using several controlled vocabularies to support and coordinate care providers, consumers, clinical knowledge and, as part of its research management, information on clinical trials. Poor findability, inconsistent indexing and specialized language undermined the goal of increasing trial participation. The ontology group designed a metadata framework addressing disorders and procedures, investigational drugs and clinical departments, adopted and translated the clinical terminology of SNOMED CT and RxNorm vocabularies to consumer language and coordinated terminology with Mayo's Consumer Health Vocabulary. The result enables retrieval of clinical trial information from multiple access points including conditions, procedures, drug names, organizations involved and trial phase. The jump in inquiries since the search site was revised and vocabularies were modified show evidence of success.
  3. Panzer, M.: Towards the "webification" of controlled subject vocabulary : a case study involving the Dewey Decimal Classification (2007) 0.01 
    0.012266726 = product of:
  0.049066905 = sum of:
    0.049066905 = product of:
      0.09813381 = sum of:
        0.09813381 = weight(_text_:terminology in 538) [ClassicSimilarity], result of:
          0.09813381 = score(doc=538,freq=2.0), product of:
            0.24053115 = queryWeight, product of:
              5.2752647 = idf(docFreq=614, maxDocs=44218)
              0.045596033 = queryNorm
            0.40798795 = fieldWeight in 538, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.2752647 = idf(docFreq=614, maxDocs=44218)
              0.0546875 = fieldNorm(doc=538)
      0.5 = coord(1/2)
  0.25 = coord(1/4)
    Abstract
    The presentation will briefly introduce a series of major principles for bringing subject terminology to the network level. A closer look at one KOS in particular, the Dewey Decimal Classification, should help to gain more insight into the perceived difficulties and potential benefits of building taxonomy services out and on top of classic large-scale vocabularies or taxonomies.
  4. Panzer, M.: Cool URIs for the DDC : towards Web-scale accessibility of a large classification system (2008) 0.01 
    0.0061776326 = product of:
  0.02471053 = sum of:
    0.02471053 = product of:
      0.04942106 = sum of:
        0.04942106 = weight(_text_:22 in 2629) [ClassicSimilarity], result of:
          0.04942106 = score(doc=2629,freq=2.0), product of:
            0.15966953 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045596033 = queryNorm
            0.30952093 = fieldWeight in 2629, 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=2629)
      0.5 = coord(1/2)
  0.25 = coord(1/4)
    Source
    Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas
  5. Panzer, M.: Relationships, spaces, and the two faces of Dewey (2008) 0.01 
    0.0052571683 = product of:
  0.021028673 = sum of:
    0.021028673 = product of:
      0.042057347 = sum of:
        0.042057347 = weight(_text_:terminology in 2127) [ClassicSimilarity], result of:
          0.042057347 = score(doc=2127,freq=2.0), product of:
            0.24053115 = queryWeight, product of:
              5.2752647 = idf(docFreq=614, maxDocs=44218)
              0.045596033 = queryNorm
            0.17485198 = fieldWeight in 2127, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.2752647 = idf(docFreq=614, maxDocs=44218)
              0.0234375 = fieldNorm(doc=2127)
      0.5 = coord(1/2)
  0.25 = coord(1/4)
    Content
    What are those "other" relationships that Dewey possesses and that seem so important to surface? Firstly, there is the relationship of concepts to resources. Dewey has been used for a long time, and over 200,000 numbers are assigned to information resources each year and added to WorldCat by the Library of Congress and the German National Library alone. Secondly, we have relationships between concepts in the scheme itself. Dewey provides a rich set of non-hierarchical relations, indicating other relevant and related subjects across disciplinary boundaries. Thirdly, perhaps most importantly, there is the relationship between the same concepts across different languages. Dewey has been translated extensively, and current versions are available in French, German, Hebrew, Italian, Spanish, and Vietnamese. Briefer representations of the top-three levels (the DDC Summaries) are available in several languages in the DeweyBrowser. This multilingual nature of the scheme allows searchers to access a broader range of resources or to switch the language of--and thus localize--subject metadata seamlessly. MelvilClass, a Dewey front-end developed by the German National Library for the German translation, could be used as a common interface to the DDC in any language, as it is built upon the standard DDC data format. It is not hard to give an example of the basic terminology of a class pulled together in a multilingual way: <class/794.8> a skos:Concept ; skos:notation "794.8"^^ddc:notation ; skos:prefLabel "Computer games"@en ; skos:prefLabel "Computerspiele"@de ; skos:prefLabel "Jeux sur ordinateur"@fr ; skos:prefLabel "Juegos por computador"@es .
  6. Panzer, M.: Designing identifiers for the DDC (2007) 0.01 
    0.0051801032 = product of:
  0.020720413 = sum of:
    0.020720413 = product of:
      0.041440826 = sum of:
        0.041440826 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
          0.041440826 = score(doc=1752,freq=10.0), product of:
            0.15966953 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045596033 = queryNorm
            0.2595412 = fieldWeight in 1752, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0234375 = fieldNorm(doc=1752)
      0.5 = coord(1/2)
  0.25 = coord(1/4)
    Content
    Some examples of identifiers for concepts follow: <http://dewey.info/concept/338.4/en/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the English-language version of Edition 22. <http://dewey.info/concept/338.4/de/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the German-language version of Edition 22. <http://dewey.info/concept/333.7-333.9/> This identifier is used to retrieve or identify the 333.7-333.9 concept across all editions and language versions. <http://dewey.info/concept/333.7-333.9/about.skos> This identifier is used to retrieve a SKOS representation of the 333.7-333.9 concept (using the "resource" element). There are several open issues at this preliminary stage of development: Use cases: URIs need to represent the range of statements or questions that could be submitted to a Dewey web service. Therefore, it seems that some general questions have to be answered first: What information does an agent have when coming to a Dewey web service? What kind of questions will such an agent ask? Placement of the {locale} component: It is still an open question if the {locale} component should be placed after the {version} component instead (<http://dewey.info/concept/338.4/edn/22/en>) to emphasize that the most important instantiation of a Dewey class is its edition, not its language version. From a services point of view, however, it could make more sense to keep the current arrangement, because users are more likely to come to the service with a present understanding of the language version they are seeking without knowing the specifics of a certain edition in which they are trying to find topics. Identification of other Dewey entities: The goal is to create a locator that does not answer all, but a lot of questions that could be asked about the DDC. Which entities are missing but should be surfaced for services or user agents? How will those services or agents interact with them? Should some entities be rendered in a different way as presented? For example, (how) should the DDC Summaries be retrievable? Would it be necessary to make the DDC Manual accessible through this identifier structure?"
  7. Panzer, M.: Dewey: how to make it work for you (2013) 0.00 
    0.0038610206 = product of:
  0.015444082 = sum of:
    0.015444082 = product of:
      0.030888164 = sum of:
        0.030888164 = weight(_text_:22 in 5797) [ClassicSimilarity], result of:
          0.030888164 = score(doc=5797,freq=2.0), product of:
            0.15966953 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045596033 = queryNorm
            0.19345059 = fieldWeight in 5797, 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=5797)
      0.5 = coord(1/2)
  0.25 = coord(1/4)
    Source
    Knowledge quest. 42(2013) no.2, S.22-29

Years

Types

Themes