Search (9 results, page 1 of 1)

  • × author_ss:"Panzer, M."
  1. Panzer, M.: Cool URIs for the DDC : towards Web-scale accessibility of a large classification system (2008) 0.02 
    0.019369476 = product of:
  0.03873895 = sum of:
    0.012957836 = weight(_text_:information in 2629) [ClassicSimilarity], result of:
      0.012957836 = score(doc=2629,freq=2.0), product of:
        0.08351069 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.047571484 = queryNorm
        0.1551638 = fieldWeight in 2629, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0625 = fieldNorm(doc=2629)
    0.025781117 = product of:
      0.051562235 = sum of:
        0.051562235 = weight(_text_:22 in 2629) [ClassicSimilarity], result of:
          0.051562235 = score(doc=2629,freq=2.0), product of:
            0.16658723 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.047571484 = 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.5 = coord(2/4)
    Abstract
    The report discusses metadata strategies employed and problems encountered during the first step of transforming the DDC into a Web information resource. It focuses on the process of URI design, with regard to W3C recommendations and Semantic Web paradigms. Special emphasis is placed on usefulness of the URIs for RESTful web services.
    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
  2. Panzer, M.: Increasing patient findability of medical research : annotating clinical trials using standard vocabularies (2017) 0.02 
    0.016932264 = product of:
  0.033864528 = sum of:
    0.019436752 = weight(_text_:information in 2783) [ClassicSimilarity], result of:
      0.019436752 = score(doc=2783,freq=8.0), product of:
        0.08351069 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.047571484 = queryNorm
        0.23274569 = fieldWeight in 2783, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.046875 = fieldNorm(doc=2783)
    0.014427775 = product of:
      0.02885555 = sum of:
        0.02885555 = weight(_text_:retrieval in 2783) [ClassicSimilarity], result of:
          0.02885555 = score(doc=2783,freq=2.0), product of:
            0.1438997 = queryWeight, product of:
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.047571484 = queryNorm
            0.20052543 = fieldWeight in 2783, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.046875 = fieldNorm(doc=2783)
      0.5 = coord(1/2)
  0.5 = coord(2/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.
    Source
    Bulletin of the Association for Information Science and Technology. 43(2017) no.2, S.40-43
  3. Panzer, M.: Dewey: how to make it work for you (2013) 0.02 
    0.015070234 = product of:
  0.030140469 = sum of:
    0.01402727 = weight(_text_:information in 5797) [ClassicSimilarity], result of:
      0.01402727 = score(doc=5797,freq=6.0), product of:
        0.08351069 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.047571484 = queryNorm
        0.16796975 = fieldWeight in 5797, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5797)
    0.0161132 = product of:
      0.0322264 = sum of:
        0.0322264 = weight(_text_:22 in 5797) [ClassicSimilarity], result of:
          0.0322264 = score(doc=5797,freq=2.0), product of:
            0.16658723 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.047571484 = 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.5 = coord(2/4)
    Content
    "As knowledge brokers, we are living in interesting times for libraries and librarians. We wonder sometimes if our traditional tools like the Dewey Decimal Classification (DDC) system can cope with the onslaught of information. The categories provided don't always seem adequate for the knowledge-discovery habits of today's patrons. They have grown accustomed to new ways for their information needs to be met, from the fire-and-forget style of a hard-to-control classic Google search to the pervasive, always-on style of Google Now, anticipating users' information needs without their having even asked a verbal question. Contrariwise, I believe that we, as librarians, could be making better use of our tools. Many (like the DDC) are a reflection of the same social and epistemological forces that brought about modernity at the turn of the last century. We as librarians are in the unique position of providing services that are as ground-breaking as these tools. As we see the need to provide unique and cutting-edge knowledge discovery to our users, I argue in this article that the DDC can play a key role in fulfilling this purpose."
    Source
    Knowledge quest. 42(2013) no.2, S.22-29
  4. Panzer, M.: Designing identifiers for the DDC (2007) 0.01 
    0.013238657 = product of:
  0.026477315 = sum of:
    0.004859188 = weight(_text_:information in 1752) [ClassicSimilarity], result of:
      0.004859188 = score(doc=1752,freq=2.0), product of:
        0.08351069 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.047571484 = queryNorm
        0.058186423 = fieldWeight in 1752, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1752)
    0.021618126 = product of:
      0.043236252 = sum of:
        0.043236252 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
          0.043236252 = score(doc=1752,freq=10.0), product of:
            0.16658723 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.047571484 = 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.5 = coord(2/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?"
  5. Panzer, M.: Semantische Integration heterogener und unterschiedlichsprachiger Wissensorganisationssysteme : CrissCross und jenseits (2008) 0.00 
    0.0042508235 = product of:
  0.017003294 = sum of:
    0.017003294 = product of:
      0.03400659 = sum of:
        0.03400659 = weight(_text_:retrieval in 4335) [ClassicSimilarity], result of:
          0.03400659 = score(doc=4335,freq=4.0), product of:
            0.1438997 = queryWeight, product of:
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.047571484 = queryNorm
            0.23632148 = fieldWeight in 4335, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.0390625 = fieldNorm(doc=4335)
      0.5 = coord(1/2)
  0.25 = coord(1/4)
    Abstract
    Klassische bibliothekarische Indexierungswerkzeuge werden bis heute nur selten fürs Retrieval nutzbar gemacht; die Wichtigkeit, verschiedene dieser Vokabularien zu harmonisieren und integriert zu verwenden, ist noch immer keine Selbstverständlichkeit. Im Rahmen des DFG-Projektes "CrissCross" wird, ausgehend von der deutschen Ausgabe der Dewey-Dezimalklassifikation, eine Verknüpfung zwischen der DDC und der Schlagwortnormdatei (SWD) aufgebaut, um eine verbale Suche über klassifikatorisch erschlossene Bestände zu ermöglichen. Als Verbreiterung der Basis des verbalen Zugriffs wird außerdem das Mapping der amerikanischen LCSH und des französischen RAMEAU angestrebt. Nach einer kurzen Vorstellung von CrissCross und der Abgrenzung gegenüber ähnlichen Unterfangen werden Rückwirkungen semantischer Integration auf die verknüpften Vokabulare diskutiert. Wie müssen und können sich z.B. Thesauri verändern, wenn sie mit anderen (strukturheterologen) Systemen verknüpft sind? Dabei liegt ein Schwerpunkt der Analyse auf dem semantischen Verhältnis üblicher Mappingrelationen zu den verknüpften Begriffen (besonders im Hinblick auf Polysemie). Außerdem wird der Mehrwert fürs Retrieval auf der Basis solcher Wissensorganisationssysteme, z.B. durch automatisierten Zugriff über Ontologien, diskutiert.
  6. Panzer, M.: Towards the "webification" of controlled subject vocabulary : a case study involving the Dewey Decimal Classification (2007) 0.00 
    0.004208101 = product of:
  0.016832404 = sum of:
    0.016832404 = product of:
      0.033664808 = sum of:
        0.033664808 = weight(_text_:retrieval in 538) [ClassicSimilarity], result of:
          0.033664808 = score(doc=538,freq=2.0), product of:
            0.1438997 = queryWeight, product of:
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.047571484 = queryNorm
            0.23394634 = fieldWeight in 538, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.0546875 = fieldNorm(doc=538)
      0.5 = coord(1/2)
  0.25 = coord(1/4)
    Theme
    Klassifikationssysteme im Online-Retrieval
  7. Panzer, M.: Taxonomies as resources identification, location and access of a »Webified« Dewey (2008) 0.00 
    0.0028345266 = product of:
  0.011338106 = sum of:
    0.011338106 = weight(_text_:information in 5471) [ClassicSimilarity], result of:
      0.011338106 = score(doc=5471,freq=2.0), product of:
        0.08351069 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.047571484 = queryNorm
        0.13576832 = fieldWeight in 5471, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5471)
  0.25 = coord(1/4)
    Abstract
    The paper outlines the first steps in an initiative to weave the Dewey Decimal Classification (DDC) as a resource into the fabric of the Web. In order for DDC web services to not only being »on« the Web, but rather a part of it, Dewey has to be available under the same rules as other information resources. The process of URI design for identified resources is described and a draft URI template is presented. In addition, basic semantic principles of RESTful web service architecture are discussed, and their appropriateness for making a large-scale knowledge organization system (KOS) like the DDC more congenial for Semantic Web applications is evaluated.
  8. Panzer, M.: Relationships, spaces, and the two faces of Dewey (2008) 0.00 
    0.002429594 = product of:
  0.009718376 = sum of:
    0.009718376 = weight(_text_:information in 2127) [ClassicSimilarity], result of:
      0.009718376 = score(doc=2127,freq=8.0), product of:
        0.08351069 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.047571484 = queryNorm
        0.116372846 = fieldWeight in 2127, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0234375 = fieldNorm(doc=2127)
  0.25 = coord(1/4)
    Content
    "When dealing with a large-scale and widely-used knowledge organization system like the Dewey Decimal Classification, we often tend to focus solely on the organization aspect, which is closely intertwined with editorial work. This is perfectly understandable, since developing and updating the DDC, keeping up with current scientific developments, spotting new trends in both scholarly communication and popular publishing, and figuring out how to fit those patterns into the structure of the scheme are as intriguing as they are challenging. From the organization perspective, the intended user of the scheme is mainly the classifier. Dewey acts very much as a number-building engine, providing richly documented concepts to help with classification decisions. Since the Middle Ages, quasi-religious battles have been fought over the "valid" arrangement of places according to specific views of the world, as parodied by Jorge Luis Borges and others. Organizing knowledge has always been primarily an ontological activity; it is about putting the world into the classification. However, there is another side to this coin--the discovery side. While the hierarchical organization of the DDC establishes a default set of places and neighborhoods that is also visible in the physical manifestation of library shelves, this is just one set of relationships in the DDC. A KOS (Knowledge Organization System) becomes powerful by expressing those other relationships in a manner that not only collocates items in a physical place but in a knowledge space, and exposes those other relationships in ways beneficial and congenial to the unique perspective of an information seeker.
    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 .
    Expressed in such manner, the Dewey number provides a language-independent representation of a Dewey concept, accompanied by language-dependent assertions about the concept. This information, identified by a URI, can be easily consumed by semantic web agents and used in various metadata scenarios. Fourthly, as we have seen, it is important to play well with others, i.e., establishing and maintaining relationships to other KOS and making the scheme available in different formats. As noted in the Dewey blog post "Tags and Dewey," since no single scheme is ever going to be the be-all, end-all solution for knowledge discovery, DDC concepts have been extensively mapped to other vocabularies and taxonomies, sometimes bridging them and acting as a backbone, sometimes using them as additional access vocabulary to be able to do more work "behind the scenes." To enable other applications and schemes to make use of those relationships, the full Dewey database is available in XML format; RDF-based formats and a web service are forthcoming. Pulling those relationships together under a common surface will be the next challenge going forward. In the semantic web community the concept of Linked Data (http://en.wikipedia.org/wiki/Linked_Data) currently receives some attention, with its emphasis on exposing and connecting data using technologies like URIs, HTTP and RDF to improve information discovery on the web. With its focus on relationships and discovery, it seems that Dewey will be well prepared to become part of this big linked data set. Now it is about putting the classification back into the world!"
  9. Baker, T.; Bermès, E.; Coyle, K.; Dunsire, G.; Isaac, A.; Murray, P.; Panzer, M.; Schneider, J.; Singer, R.; Summers, E.; Waites, W.; Young, J.; Zeng, M.: Library Linked Data Incubator Group Final Report (2011) 0.00 
    0.0016197294 = product of:
  0.006478918 = sum of:
    0.006478918 = weight(_text_:information in 4796) [ClassicSimilarity], result of:
      0.006478918 = score(doc=4796,freq=2.0), product of:
        0.08351069 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.047571484 = queryNorm
        0.0775819 = fieldWeight in 4796, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.03125 = fieldNorm(doc=4796)
  0.25 = coord(1/4)
    Abstract
    The mission of the W3C Library Linked Data Incubator Group, chartered from May 2010 through August 2011, has been "to help increase global interoperability of library data on the Web, by bringing together people involved in Semantic Web activities - focusing on Linked Data - in the library community and beyond, building on existing initiatives, and identifying collaboration tracks for the future." In Linked Data [LINKEDDATA], data is expressed using standards such as Resource Description Framework (RDF) [RDF], which specifies relationships between things, and Uniform Resource Identifiers (URIs, or "Web addresses") [URI]. This final report of the Incubator Group examines how Semantic Web standards and Linked Data principles can be used to make the valuable information assets that library create and curate - resources such as bibliographic data, authorities, and concept schemes - more visible and re-usable outside of their original library context on the wider Web. The Incubator Group began by eliciting reports on relevant activities from parties ranging from small, independent projects to national library initiatives (see the separate report, Library Linked Data Incubator Group: Use Cases) [USECASE]. These use cases provided the starting point for the work summarized in the report: an analysis of the benefits of library Linked Data, a discussion of current issues with regard to traditional library data, existing library Linked Data initiatives, and legal rights over library data; and recommendations for next steps. The report also summarizes the results of a survey of current Linked Data technologies and an inventory of library Linked Data resources available today (see also the more detailed report, Library Linked Data Incubator Group: Datasets, Value Vocabularies, and Metadata Element Sets) [VOCABDATASET].

Authors

Years

Languages

Types

Themes