Search (5 results, page 1 of 1)

0.015323698 = product of:
  0.030647395 = sum of:
    0.030647395 = product of:
      0.06129479 = sum of:
        0.06129479 = weight(_text_:x in 1870) [ClassicSimilarity], result of:
          0.06129479 = score(doc=1870,freq=2.0), product of:
            0.21896711 = queryWeight, product of:
              4.2226825 = idf(docFreq=1761, maxDocs=44218)
              0.05185498 = queryNorm
            0.27992693 = fieldWeight in 1870, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.2226825 = idf(docFreq=1761, maxDocs=44218)
              0.046875 = fieldNorm(doc=1870)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Content

ORCID soll die elektronische Zuordnung von Publikation und Autoren ermöglichen. Dies ist notwendig, da verschiedene Autoren gleiche Namen haben können, Namen sich ändern (z. B. bei Heirat) und Namen in verschiedenen Publikationen unterschiedlich angegeben werden (z. B. einmal die ausgeschriebenen Vornamen, ein anderes Mal aber nur die Initialen). ORCID soll zum De-facto-Standard für die Autorenidentifikation wissenschaftlicher Publikationen werden. Die Etablierung wird von der Non-Profit-Organisation Open Researcher Contributor Identification Initiative organisiert. Zu den Gründungsmitgliedern der Initiative gehören zahlreiche wissenschaftliche Verlagsgruppen (z. B. Elsevier, Nature Publishing Group, Springer) und Forschungsorganisationen (z. B. EMBO, CERN). Die Planungen für ORCID wurden 2010 auf Umfragen gestützt. ORCID ging am 16. Oktober 2012 offiziell an den Start. Am Jahresende 2012 hatte ORCID 42.918 Registrierte, Jahresende 2013 waren es 460.000 Registrierte und im November 2014 hatte ORCID 1 Million Autorenidentifikationen ausgestellt. Vgl. auch den Zusammenhang mit der GND und den Erfassungsleitfaden der DNB unter: https://wiki.dnb.de/x/vYYGAw.

0.012769748 = product of:
  0.025539497 = sum of:
    0.025539497 = product of:
      0.051078994 = sum of:
        0.051078994 = weight(_text_:x in 82) [ClassicSimilarity], result of:
          0.051078994 = score(doc=82,freq=2.0), product of:
            0.21896711 = queryWeight, product of:
              4.2226825 = idf(docFreq=1761, maxDocs=44218)
              0.05185498 = queryNorm
            0.23327245 = fieldWeight in 82, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.2226825 = idf(docFreq=1761, maxDocs=44218)
              0.0390625 = fieldNorm(doc=82)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Footnote

Beitrag im Rahmen einer Special Section: Papers from the 10th ISKO Spanish Chapter Conference (X Congreso Capítulo Español de ISKO), Ferrol, Spain, 30 June-1 July, 2011.

0.01053845 = product of:
  0.0210769 = sum of:
    0.0210769 = product of:
      0.0421538 = sum of:
        0.0421538 = weight(_text_:22 in 3502) [ClassicSimilarity], result of:
          0.0421538 = score(doc=3502,freq=2.0), product of:
            0.18158731 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05185498 = queryNorm
            0.23214069 = fieldWeight in 3502, 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=3502)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Archivar. 70(2017) H.1, S.22-25

0.008782043 = product of:
  0.017564086 = sum of:
    0.017564086 = product of:
      0.035128172 = sum of:
        0.035128172 = weight(_text_:22 in 3780) [ClassicSimilarity], result of:
          0.035128172 = score(doc=3780,freq=2.0), product of:
            0.18158731 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05185498 = queryNorm
            0.19345059 = fieldWeight in 3780, 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=3780)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

19. 8.2017 9:24:22

0.007441822 = product of:
  0.014883644 = sum of:
    0.014883644 = product of:
      0.059534576 = sum of:
        0.059534576 = weight(_text_:authors in 2293) [ClassicSimilarity], result of:
          0.059534576 = score(doc=2293,freq=2.0), product of:
            0.2363972 = queryWeight, product of:
              4.558814 = idf(docFreq=1258, maxDocs=44218)
              0.05185498 = queryNorm
            0.25184128 = fieldWeight in 2293, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.558814 = idf(docFreq=1258, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2293)
      0.25 = coord(1/4)
  0.5 = coord(1/2)

Abstract

We illustrate the principle of unified treatment of all authority data for any kind of entities, subjects/topics, places, events, persons, organizations, etc. through the design and implementation of an enriched authority database for organizations, maintained as an integral part of an authority database that also includes subject authority control / classification data, using the same structures for data and common modules for processing and display of data. Organization-related data are stored in information systems of many companies. We specifically examine the case of the World Bank Group (WBG) according to organization role: suppliers, partners, customers, competitors, authors, publishers, or subjects of documents, loan recipients, suppliers for WBG-funded projects and subunits of the organization itself. A central organization authority where each organization is identified by a URI, represented by several names and linked to other organizations through hierarchical and other relationships serves to link data from these disparate information systems. Designing the conceptual structure of a unified authority database requires integrating SKOS, the W3C Organization Ontology and other schemes into one comprehensive ontology. To populate the authority database with organizations, we import data from external sources (e.g., DBpedia and Library of Congress authorities) and internal sources (e.g., the lists of organizations from multiple WBG information systems).