Search (17 results, page 1 of 1)

0.021732338 = product of:
  0.060850542 = sum of:
    0.016528286 = weight(_text_:wide in 1166) [ClassicSimilarity], result of:
      0.016528286 = score(doc=1166,freq=2.0), product of:
        0.13505316 = queryWeight, product of:
          4.4307585 = idf(docFreq=1430, maxDocs=44218)
          0.030480823 = queryNorm
        0.122383565 = fieldWeight in 1166, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.4307585 = idf(docFreq=1430, maxDocs=44218)
          0.01953125 = fieldNorm(doc=1166)
    0.017933775 = weight(_text_:web in 1166) [ClassicSimilarity], result of:
      0.017933775 = score(doc=1166,freq=8.0), product of:
        0.09947448 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.030480823 = queryNorm
        0.18028519 = fieldWeight in 1166, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.01953125 = fieldNorm(doc=1166)
    0.014190909 = weight(_text_:bibliothek in 1166) [ClassicSimilarity], result of:
      0.014190909 = score(doc=1166,freq=2.0), product of:
        0.12513994 = queryWeight, product of:
          4.1055303 = idf(docFreq=1980, maxDocs=44218)
          0.030480823 = queryNorm
        0.113400325 = fieldWeight in 1166, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.1055303 = idf(docFreq=1980, maxDocs=44218)
          0.01953125 = fieldNorm(doc=1166)
    0.0044938973 = weight(_text_:information in 1166) [ClassicSimilarity], result of:
      0.0044938973 = score(doc=1166,freq=6.0), product of:
        0.053508412 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.030480823 = queryNorm
        0.083984874 = fieldWeight in 1166, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.01953125 = fieldNorm(doc=1166)
    0.0077036773 = weight(_text_:retrieval in 1166) [ClassicSimilarity], result of:
      0.0077036773 = score(doc=1166,freq=2.0), product of:
        0.092201896 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.030480823 = queryNorm
        0.08355226 = fieldWeight in 1166, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.01953125 = fieldNorm(doc=1166)
  0.35714287 = coord(5/14)

Abstract

This article presents an overview of the LEAF project (Linking and Exploring Authority Files)1, which has set out to provide a framework for international, collaborative work in the sector of authority data with respect to authority control. Elaborating the virtues of authority control in today's Web environment is an almost futile exercise, since so much has been said and written about it in the last few years.2 The World Wide Web is generally understood to be poorly structured-both with regard to content and to locating required information. Highly structured databases might be viewed as small islands of precision within this chaotic environment. Though the Web in general or any particular structured database would greatly benefit from increased authority control, it should be noted that our following considerations only refer to authority control with regard to databases of "memory institutions" (i.e., libraries, archives, and museums). Moreover, when talking about authority records, we exclusively refer to personal name authority records that describe a specific person. Although different types of authority records could indeed be used in similar ways to the ones presented in this article, discussing those different types is outside the scope of both the LEAF project and this article. Personal name authority records-as are all other "authorities"-are maintained as separate records and linked to various kinds of descriptive records. Name authority records are usually either kept in independent databases or in separate tables in the database containing the descriptive records. This practice points at a crucial benefit: by linking any number of descriptive records to an authorized name record, the records related to this entity are collocated in the database. Variant forms of the authorized name are referenced in the authority records and thus ensure the consistency of the database while enabling search and retrieval operations that produce accurate results. On one hand, authority control may be viewed as a positive prerequisite of a consistent catalogue; on the other, the creation of new authority records is a very time consuming and expensive undertaking. As a consequence, various models of providing access to existing authority records have emerged: the Library of Congress and the French National Library (Bibliothèque nationale de France), for example, make their authority records available to all via a web-based search service.3 In Germany, the Personal Name Authority File (PND, Personennamendatei4) maintained by the German National Library (Die Deutsche Bibliothek, Frankfurt/Main) offers a different approach to shared access: within a closed network, participating institutions have online access to their pooled data. The number of recent projects and initiatives that have addressed the issue of authority control in one way or another is considerable.5 Two important current initiatives should be mentioned here: The Name Authority Cooperative (NACO) and Virtual International Authority File (VIAF).
NACO was established in 1976 and is hosted by the Library of Congress. At the beginning of 2003, nearly 400 institutions were involved in this undertaking, including 43 institutions from outside the United States.6 Despite the enormous success of NACO and the impressive annual growth of the initiative, there are requirements for participation that form an obstacle for many institutions: they have to follow the Anglo-American Cataloguing Rules (AACR2) and employ the MARC217 data format. Participating institutions also have to belong to either OCLC (Online Computer Library Center) or RLG (Research Libraries Group) in order to be able to contribute records, and they have to provide a specified minimum number of authority records per year. A recent proof of concept project of the Library of Congress, OCLC and the German National Library-Virtual International Authority File (VIAF)8-will, in its first phase, test automatic linking of the records of the Library of Congress Name Authority File (LCNAF) and the German Personal Name Authority File by using matching algorithms and software developed by OCLC. The results are expected to form the basis of a "Virtual International Authority File". The project will then test the maintenance of the virtual authority file by employing the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH)9 to harvest the metadata for new, updated, and deleted records. When using the "Virtual International Authority File" a cataloguer will be able to check the system to see whether the authority record he wants to establish already exists. The final phase of the project will test possibilities for displaying records in the preferred language and script of the end user. Currently, there are still some clear limitations associated with the ways in which authority records are used by memory institutions. One of the main problems has to do with limited access: generally only large institutions or those that are part of a library network have unlimited online access to permanently updated authority records. Smaller institutions outside these networks usually have to fall back on less efficient ways of obtaining authority data, or have no access at all. Cross-domain sharing of authority data between libraries, archives, museums and other memory institutions simply does not happen at present. Public users are, by and large, not even aware that such things as name authority records exist and are excluded from access to these information resources.

0.015488921 = product of:
  0.07228163 = sum of:
    0.017933775 = weight(_text_:web in 6105) [ClassicSimilarity], result of:
      0.017933775 = score(doc=6105,freq=2.0), product of:
        0.09947448 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.030480823 = queryNorm
        0.18028519 = fieldWeight in 6105, 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=6105)
    0.049158752 = weight(_text_:bibliothek in 6105) [ClassicSimilarity], result of:
      0.049158752 = score(doc=6105,freq=6.0), product of:
        0.12513994 = queryWeight, product of:
          4.1055303 = idf(docFreq=1980, maxDocs=44218)
          0.030480823 = queryNorm
        0.39283025 = fieldWeight in 6105, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          4.1055303 = idf(docFreq=1980, maxDocs=44218)
          0.0390625 = fieldNorm(doc=6105)
    0.005189105 = weight(_text_:information in 6105) [ClassicSimilarity], result of:
      0.005189105 = score(doc=6105,freq=2.0), product of:
        0.053508412 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.030480823 = queryNorm
        0.09697737 = fieldWeight in 6105, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0390625 = fieldNorm(doc=6105)
  0.21428572 = coord(3/14)

Abstract

Die Deutsche Bibliothek, the Library of Congress, and OCLC Online Computer Library Center are jointly developing a virtual international authority file (VIAF) for personal names which links authority records from the world's national bibliographic agencies and will be made freely available on the Web. The goals of the project are to prove the viability of automatically linking authority records from different national authority files and to demonstrate its benefits. The authority and bibliographic files from the Library of Congress and Die Deutsche Bibliothek were used to create the initial VIAF which contains over six million names with over a half million links. A key aspect of the project was the development of automated name matching algorithms which use information from both authority records and the corresponding bibliographic records. The practicality of algorithmically linking the personal names between national authority files was demonstrated; seventy percent of the authority records for personal names common to both files were automatically linked with an error rate of less than one percent. The long-term goal of the VIAF project is to combine the authoritative names from many national libraries and other significant sources into a shared global authority service.

0.012808081 = product of:
  0.059771042 = sum of:
    0.021520529 = weight(_text_:web in 310) [ClassicSimilarity], result of:
      0.021520529 = score(doc=310,freq=2.0), product of:
        0.09947448 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.030480823 = queryNorm
        0.21634221 = fieldWeight in 310, 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=310)
    0.006226926 = weight(_text_:information in 310) [ClassicSimilarity], result of:
      0.006226926 = score(doc=310,freq=2.0), product of:
        0.053508412 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.030480823 = queryNorm
        0.116372846 = fieldWeight in 310, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.046875 = fieldNorm(doc=310)
    0.032023586 = weight(_text_:retrieval in 310) [ClassicSimilarity], result of:
      0.032023586 = score(doc=310,freq=6.0), product of:
        0.092201896 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.030480823 = queryNorm
        0.34732026 = fieldWeight in 310, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.046875 = fieldNorm(doc=310)
  0.21428572 = coord(3/14)

Abstract

Authority files have played an important role in improving the quality of indexing and subject cataloging. Although authorities can significantly improve search by increasing the number of access points, they are rarely an integral part of the information retrieval process, particularly end-users searches. A retrieval prototype, searchFAST, was developed to test the feasibility of using an authority file as an index to bibliographic records. searchFAST uses FAST (Faceted Application of Subject Terminology) as an index to OCLC's WorldCat.org bibliographic database. The searchFAST methodology complements, rather than replaces, existing WorldCat.org access. The bibliographic file is searched indirectly; first the authority file is searched to identify appropriate subject headings, then the headings are used to retrieve the matching bibliographic records. The prototype demonstrates the effectiveness and practicality of using an authority file as an index. Searching the authority file leverages authority control work by increasing the number of access points while supporting a simple interface designed for end-users.

Source

Beyond libraries - subject metadata in the digital environment and semantic web. IFLA Satellite Post-Conference, 17-18 August 2012, Tallinn

Theme

Verbale Doksprachen im Online-Retrieval

0.012462383 = product of:
  0.058157787 = sum of:
    0.03586755 = weight(_text_:web in 1291) [ClassicSimilarity], result of:
      0.03586755 = score(doc=1291,freq=8.0), product of:
        0.09947448 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.030480823 = queryNorm
        0.36057037 = fieldWeight in 1291, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1291)
    0.015407355 = weight(_text_:retrieval in 1291) [ClassicSimilarity], result of:
      0.015407355 = score(doc=1291,freq=2.0), product of:
        0.092201896 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.030480823 = queryNorm
        0.16710453 = fieldWeight in 1291, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1291)
    0.006882885 = product of:
      0.020648655 = sum of:
        0.020648655 = weight(_text_:22 in 1291) [ClassicSimilarity], result of:
          0.020648655 = score(doc=1291,freq=2.0), product of:
            0.10673865 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.030480823 = queryNorm
            0.19345059 = fieldWeight in 1291, 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=1291)
      0.33333334 = coord(1/3)
  0.21428572 = coord(3/14)

Abstract

More and more users index everything on their own in the web 2.0. There are services for links, videos, pictures, books, encyclopaedic articles and scientific articles. All these services are library independent. But must that really be? Can't libraries help with their experience and tools to make user indexing better? On the experience of a project from German language Wikipedia together with the German person authority files (Personen Namen Datei - PND) located at German National Library (Deutsche Nationalbibliothek) I would like to show what is possible. How users can and will use the authority files, if we let them. We will take a look how the project worked and what we can learn for future projects. Conclusions - Authority files can have a role in the web 2.0 - there must be an open interface/ service for retrieval - everything that is indexed on the net with authority files can be easy integrated in a federated search - O'Reilly: You have to found ways that your data get more important that more it will be used

Content

Vortrag anlässlich des Workshops: "Extending the multilingual capacity of The European Library in the EDL project Stockholm, Swedish National Library, 22-23 November 2007".

Object

Web 2.0

0.005824221 = product of:
  0.040769543 = sum of:
    0.02536219 = weight(_text_:web in 4599) [ClassicSimilarity], result of:
      0.02536219 = score(doc=4599,freq=4.0), product of:
        0.09947448 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.030480823 = queryNorm
        0.25496176 = fieldWeight in 4599, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0390625 = fieldNorm(doc=4599)
    0.015407355 = weight(_text_:retrieval in 4599) [ClassicSimilarity], result of:
      0.015407355 = score(doc=4599,freq=2.0), product of:
        0.092201896 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.030480823 = queryNorm
        0.16710453 = fieldWeight in 4599, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.0390625 = fieldNorm(doc=4599)
  0.14285715 = coord(2/14)

Abstract

Aufgrund der fortgesetzten Publikationsflut stellt sich immer dringender die Frage, wie die Schwellen für die Titel- und Normdatenpflege gesenkt werden können - sowohl für die intellektuelle als auch die automatisierte Sacherschließung. Zu einer Verbesserung der Daten- und Arbeitsqualität in der Sacherschließung kann beigetragen werden a) durch eine flexible Visualisierung der Gemeinsamen Normdatei (GND) und anderer Wissensorganisationssysteme, so dass deren Graphstruktur intuitiv erfassbar wird, und b) durch eine investigative Analyse ihrer aktuellen Struktur und die Entwicklung angepasster automatisierter Methoden zur Ermittlung und Korrektur fehlerhafter Muster. Die Deutsche Nationalbibliothek (DNB) prüft im Rahmen des GND-Entwicklungsprogramms 2017-2021, welche Bedingungen für eine fruchtbare community-getriebene Open-Source-Entwicklung entsprechender Werkzeuge gegeben sein müssen. Weiteres Potential steckt in einem langfristigen Übergang zu einer Darstellung von Titel- und Normdaten in Beschreibungssprachen im Sinne des Semantic Web (RDF; OWL, SKOS). So profitiert die GND von der Interoperabilität mit anderen kontrollierten Vokabularen und von einer erleichterten Interaktion mit anderen Fach-Communities und kann umgekehrt auch außerhalb des Bibliothekswesens zu einem noch attraktiveren Wissensorganisationssystem werden. Darüber hinaus bieten die Ansätze aus dem Semantic Web die Möglichkeit, stärker formalisierte, strukturierende Satellitenvokabulare rund um die GND zu entwickeln. Daraus ergeben sich nicht zuletzt auch neue Perspektiven für die automatisierte Sacherschließung. Es wäre lohnend, näher auszuloten, wie und inwieweit semantisch-logische Verfahren den bestehenden Methodenmix bereichern können.

Theme

Semantisches Umfeld in Indexierung u. Retrieval

0.0032436366 = product of:
  0.04541091 = sum of:
    0.04541091 = weight(_text_:bibliothek in 4184) [ClassicSimilarity], result of:
      0.04541091 = score(doc=4184,freq=2.0), product of:
        0.12513994 = queryWeight, product of:
          4.1055303 = idf(docFreq=1980, maxDocs=44218)
          0.030480823 = queryNorm
        0.36288103 = fieldWeight in 4184, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.1055303 = idf(docFreq=1980, maxDocs=44218)
          0.0625 = fieldNorm(doc=4184)
  0.071428575 = coord(1/14)

Abstract

Die Aufgabe der Erabeitung, Verwaltung und Pflege mehrsprachiger Schlagwortnormdateien erfordert erheblich Mittel und sollte daher am besten in Kooperation erfolgen. 4 europäische Nationalbibliotheken (die Schweizerische Landesbibliothek, die Bibliothèque de France, Die Deutsche Bibliothek und die British Library) haben gemeinsam eine Machbarkeitsstudie über die Verknüpfung bestehender Schlagwortverzeichnisse in verschiedenen Sprachen erarbeitet, um einen mehrsprachigen Schlagwort-Zugang zu ihren Daten zu ermöglichen

0.0032276732 = product of:
  0.045187425 = sum of:
    0.045187425 = weight(_text_:elektronische in 1870) [ClassicSimilarity], result of:
      0.045187425 = score(doc=1870,freq=2.0), product of:
        0.14414315 = queryWeight, product of:
          4.728978 = idf(docFreq=1061, maxDocs=44218)
          0.030480823 = queryNorm
        0.3134899 = fieldWeight in 1870, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.728978 = idf(docFreq=1061, maxDocs=44218)
          0.046875 = fieldNorm(doc=1870)
  0.071428575 = coord(1/14)

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.002835579 = product of:
  0.039698105 = sum of:
    0.039698105 = weight(_text_:web in 318) [ClassicSimilarity], result of:
      0.039698105 = score(doc=318,freq=20.0), product of:
        0.09947448 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.030480823 = queryNorm
        0.39907828 = fieldWeight in 318, product of:
          4.472136 = tf(freq=20.0), with freq of:
            20.0 = termFreq=20.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.02734375 = fieldNorm(doc=318)
  0.071428575 = coord(1/14)

Abstract

Seit Bestehen der Menschheit sammelt der Mensch Informationen, seit Bestehen des Internets stellt der Mensch Informationen ins Web, seit Bestehen des Semantic Webs sollen auch Maschinen in die Lage versetzt werden mit diesen Informationen umzugehen. Das Bibliothekswesen ist einer der Sammler. Seit Jahrhunderten werden Kataloge und Bibliografien sowie Inventarnachweise geführt. Mit der Aufgabe des Zettelkatalogs hin zum Onlinekatalog wurde es Benutzern plötzlich möglich in Beständen komfortabel zu suchen. Durch die Bereitstellung von Daten aus dem Bibliothekswesen im Semantic Web sollen nicht nur die eigenen Katalogsysteme Zugriff auf diese Informationen erhalten, sondern jede beliebige Anwendung, die auf das Web zugreifen kann. Darüber hinaus ist die Vorstellung, dass sich die im Web befindenden Daten - in sofern möglich - miteinander verlinken und zu einem gigantischen semantischen Netz werden, das als ein großer Datenpool verwendet werden kann. Die Voraussetzung hierfür ist wie beim Übergang zum Onlinekatalog die Aufbereitung der Daten in einem passenden Format. Normdaten dienen im Bibliothekswesen bereits dazu eine Vernetzung der unterschiedlichen Bestände zu erlauben. Bei der Erschließung eines Buches wird nicht bloß gesagt, dass jemand, der Thomas Mann heißt, der Autor ist - es wird eine Verknüpfung vom Katalogisat zu dem Thomas Mann erzeugt, der am 6. Juni 1875 in Lübeck geboren und am 12. August 1955 in Zürich verstorben ist. Der Vorteil von Normdateneintragungen ist, dass sie zum eindeutigen Nachweis der Verfasserschaft oder Mitwirkung an einem Werk beitragen. Auch stehen Normdateneintragungen bereits allen Bibliotheken für die Nachnutzung bereit - der Schritt ins Semantic Web wäre somit die Öffnung der Normdaten für alle denkbaren Nutzergruppen.
Die Gemeinsame Normdatei (GND) ist seit April 2012 die Datei, die die im deutschsprachigen Bibliothekswesen verwendeten Normdaten enthält. Folglich muss auf Basis dieser Daten eine Repräsentation für die Darstellung als Linked Data im Semantic Web etabliert werden. Neben der eigentlichen Bereitstellung von GND-Daten im Semantic Web sollen die Daten mit bereits als Linked Data vorhandenen Datenbeständen (DBpedia, VIAF etc.) verknüpft und nach Möglichkeit kompatibel sein, wodurch die GND einem internationalen und spartenübergreifenden Publikum zugänglich gemacht wird. Dieses Dokument dient vor allem zur Beschreibung, wie die GND-Linked-Data-Repräsentation entstand und dem Weg zur Spezifikation einer eignen Ontologie. Hierfür werden nach einer kurzen Einführung in die GND die Grundprinzipien und wichtigsten Standards für die Veröffentlichung von Linked Data im Semantic Web vorgestellt, um darauf aufbauend existierende Vokabulare und Ontologien des Bibliothekswesens betrachten zu können. Anschließend folgt ein Exkurs in das generelle Vorgehen für die Bereitstellung von Linked Data, wobei die so oft zitierte Open World Assumption kritisch hinterfragt und damit verbundene Probleme insbesondere in Hinsicht Interoperabilität und Nachnutzbarkeit aufgedeckt werden. Um Probleme der Interoperabilität zu vermeiden, wird den Empfehlungen der Library Linked Data Incubator Group [LLD11] gefolgt.
Im Kapitel Anwendungsprofile als Basis für die Ontologieentwicklung wird die Spezifikation von Dublin Core Anwendungsprofilen kritisch betrachtet, um auszumachen wann und in welcher Form sich ihre Verwendung bei dem Vorhaben Bereitstellung von Linked Data anbietet. In den nachfolgenden Abschnitten wird die GND-Ontologie, welche als Standard für die Serialisierung von GND-Daten im Semantic Web dient, samt Modellierungsentscheidungen näher vorgestellt. Dabei wird insbesondere der Technik des Vocabulary Alignment eine prominente Position eingeräumt, da darin ein entscheidender Mechanismus zur Steigerung der Interoperabilität und Nachnutzbarkeit gesehen wird. Auch wird sich mit der Verlinkung zu externen Datensets intensiv beschäftigt. Hierfür wurden ausgewählte Datenbestände hinsichtlich ihrer Qualität und Aktualität untersucht und Empfehlungen für die Implementierung innerhalb des GND-Datenbestandes gegeben. Abschließend werden eine Zusammenfassung und ein Ausblick auf weitere Schritte gegeben.

0.0024327273 = product of:
  0.03405818 = sum of:
    0.03405818 = weight(_text_:bibliothek in 6103) [ClassicSimilarity], result of:
      0.03405818 = score(doc=6103,freq=2.0), product of:
        0.12513994 = queryWeight, product of:
          4.1055303 = idf(docFreq=1980, maxDocs=44218)
          0.030480823 = queryNorm
        0.27216077 = fieldWeight in 6103, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.1055303 = idf(docFreq=1980, maxDocs=44218)
          0.046875 = fieldNorm(doc=6103)
  0.071428575 = coord(1/14)

Abstract

A draft of Functional Requirements for Authority Records (FRAR) was made available for worldwide review on IFLANET from July through October 2005. The FRANAR Working Group received comments from 12 individuals and 13 institutions (including 6 national libraries and 3 national-level cataloguing committees). The working group expresses its appreciation to all who took the time to prepare comments. The comments received were compiled into a comments log which totaled 145 pages. Seven members of the Working Group met at the Koninklijke Bibliothek, The Hague, Netherlands, on December 9, 2005, to consider these comments and to start revising the draft to reflect decisions made in response to the comments. The group was able to deal with about two-thirds of the comments during the meeting and, since the December meeting has had a series of four conference calls to complete discussions of the remaining comments, with additional calls anticipated before the Seoul meetings.

0.0024327273 = product of:
  0.03405818 = sum of:
    0.03405818 = weight(_text_:bibliothek in 2393) [ClassicSimilarity], result of:
      0.03405818 = score(doc=2393,freq=2.0), product of:
        0.12513994 = queryWeight, product of:
          4.1055303 = idf(docFreq=1980, maxDocs=44218)
          0.030480823 = queryNorm
        0.27216077 = fieldWeight in 2393, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.1055303 = idf(docFreq=1980, maxDocs=44218)
          0.046875 = fieldNorm(doc=2393)
  0.071428575 = coord(1/14)

Abstract

Normdateien lösen das Problem von unterschiedlichen Namensschreibweisen, Übersetzungen und Namensdoppelungen. Nationale oder an Sprachräume gebundene Normdaten sind mittlerweile im "Virtual International Authority File" Projekt (VIAF) über Konkordanzen miteinander verlinkt. Neben diesen von Bibliotheken erstellten Normdaten entstehen aber auch in anderen Kontexten Identifizierungssysteme, die die Uneindeutigkeit von Personennamen in sehr großen Datenmengen beseitigen sollen. Ein arbeitsaufwändiges Problem ist dabei aber immer noch nicht gelöst: nach wie vor müssen Bibliothekare die Identität der Autoren mühsam recherchieren. Wie einfach wäre es, wenn die GND oder LoC Nummer beim Namen des Autors abgedruckt wäre! An einem Pilotprojekt der UB Tübingen wird demonstriert, wie durch die Zusammenarbeit von Herausgeber, Verlag und Bibliothek die GND-Nummern der Autoren in der Publikation abgedruckt werden können.

0.0011799231 = product of:
  0.016518923 = sum of:
    0.016518923 = product of:
      0.049556766 = sum of:
        0.049556766 = weight(_text_:22 in 6888) [ClassicSimilarity], result of:
          0.049556766 = score(doc=6888,freq=2.0), product of:
            0.10673865 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.030480823 = queryNorm
            0.46428138 = fieldWeight in 6888, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=6888)
      0.33333334 = coord(1/3)
  0.071428575 = coord(1/14)

Date

26.12.2011 12:30:22

0.0011799231 = product of:
  0.016518923 = sum of:
    0.016518923 = product of:
      0.049556766 = sum of:
        0.049556766 = weight(_text_:22 in 131) [ClassicSimilarity], result of:
          0.049556766 = score(doc=131,freq=2.0), product of:
            0.10673865 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.030480823 = queryNorm
            0.46428138 = fieldWeight in 131, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=131)
      0.33333334 = coord(1/3)
  0.071428575 = coord(1/14)

Content

Vortrag anlässlich des Workshops: "Extending the multilingual capacity of The European Library in the EDL project Stockholm, Swedish National Library, 22-23 November 2007".

0.0011799231 = product of:
  0.016518923 = sum of:
    0.016518923 = product of:
      0.049556766 = sum of:
        0.049556766 = weight(_text_:22 in 1266) [ClassicSimilarity], result of:
          0.049556766 = score(doc=1266,freq=2.0), product of:
            0.10673865 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.030480823 = queryNorm
            0.46428138 = fieldWeight in 1266, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=1266)
      0.33333334 = coord(1/3)
  0.071428575 = coord(1/14)

Content

Vortrag anlässlich des Workshops: "Extending the multilingual capacity of The European Library in the EDL project Stockholm, Swedish National Library, 22-23 November 2007".

0.0011799231 = product of:
  0.016518923 = sum of:
    0.016518923 = product of:
      0.049556766 = sum of:
        0.049556766 = weight(_text_:22 in 1290) [ClassicSimilarity], result of:
          0.049556766 = score(doc=1290,freq=2.0), product of:
            0.10673865 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.030480823 = queryNorm
            0.46428138 = fieldWeight in 1290, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=1290)
      0.33333334 = coord(1/3)
  0.071428575 = coord(1/14)

Content

Vortrag anlässlich des Workshops: "Extending the multilingual capacity of The European Library in the EDL project Stockholm, Swedish National Library, 22-23 November 2007".

5.930406E-4 = product of:
  0.008302568 = sum of:
    0.008302568 = weight(_text_:information in 4191) [ClassicSimilarity], result of:
      0.008302568 = score(doc=4191,freq=2.0), product of:
        0.053508412 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.030480823 = queryNorm
        0.1551638 = fieldWeight in 4191, 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=4191)
  0.071428575 = coord(1/14)

Abstract

The report deals with the necessity for developing a National Subject Authority File in russia. Basic approaches creating such a file creation are introduced. The history and main features of the National Library of Russia Subject authority File are described. The report includes information on number of projects being undertaken both in NLR and in Russia

5.930406E-4 = product of:
  0.008302568 = sum of:
    0.008302568 = weight(_text_:information in 1240) [ClassicSimilarity], result of:
      0.008302568 = score(doc=1240,freq=8.0), product of:
        0.053508412 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.030480823 = queryNorm
        0.1551638 = fieldWeight in 1240, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.03125 = fieldNorm(doc=1240)
  0.071428575 = coord(1/14)

Abstract

The Alexandria Digital Library (ADL) Project has developed a content standard for gazetteer objects and a hierarchical type scheme for geographic features. Both of these developments are based on ADL experience with an earlier gazetteer component for the Library, based on two gazetteers maintained by the U.S. federal government. We define the minimum components of a gazetteer entry as (1) a geographic name, (2) a geographic location represented by coordinates, and (3) a type designation. With these attributes, a gazetteer can function as a tool for indirect spatial location identification through names and types. The ADL Gazetteer Content Standard supports contribution and sharing of gazetteer entries with rich descriptions beyond the minimum requirements. This paper describes the content standard, the feature type thesaurus, and the implementation and research issues. A gazetteer is list of geographic names, together with their geographic locations and other descriptive information. A geographic name is a proper name for a geographic place and feature, such as Santa Barbara County, Mount Washington, St. Francis Hospital, and Southern California. There are many types of printed gazetteers. For example, the New York Times Atlas has a gazetteer section that can be used to look up a geographic name and find the page(s) and grid reference(s) where the corresponding feature is shown. Some gazetteers provide information about places and features; for example, a history of the locale, population data, physical data such as elevation, or the pronunciation of the name. Some lists of geographic names are available as hierarchical term sets (thesauri) designed for information retreival; these are used to describe bibliographic or museum materials. Examples include the authority files of the U.S. Library of Congress and the GeoRef Thesaurus produced by the American Geological Institute. The Getty Museum has recently made their Thesaurus of Geographic Names available online. This is a major project to develop a controlled vocabulary of current and historical names to describe (i.e., catalog) art and architecture literature. U.S. federal government mapping agencies maintain gazetteers containing the official names of places and/or the names that appear on map series. Examples include the U.S. Geological Survey's Geographic Names Information System (GNIS) and the National Imagery and Mapping Agency's Geographic Names Processing System (GNPS). Both of these are maintained in cooperation with the U.S. Board of Geographic Names (BGN). Many other examples could be cited -- for local areas, for other countries, and for special purposes. There is remarkable diversity in approaches to the description of geographic places and no standardization beyond authoritative sources for the geographic names themselves.

4.9163465E-4 = product of:
  0.006882885 = sum of:
    0.006882885 = product of:
      0.020648655 = sum of:
        0.020648655 = weight(_text_:22 in 3780) [ClassicSimilarity], result of:
          0.020648655 = score(doc=3780,freq=2.0), product of:
            0.10673865 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.030480823 = 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.33333334 = coord(1/3)
  0.071428575 = coord(1/14)

Date

19. 8.2017 9:24:22