Search (32 results, page 1 of 2)

0.03831512 = product of:
  0.1915756 = sum of:
    0.1915756 = weight(_text_:link in 21) [ClassicSimilarity], result of:
      0.1915756 = score(doc=21,freq=2.0), product of:
        0.2711644 = queryWeight, product of:
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.05088753 = queryNorm
        0.7064925 = fieldWeight in 21, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.09375 = fieldNorm(doc=21)
  0.2 = coord(1/5)

Abstract

Link national authority records - Build on their authority work - Move towards universal bibliographic control

0.022577403 = product of:
  0.11288701 = sum of:
    0.11288701 = weight(_text_:link in 5687) [ClassicSimilarity], result of:
      0.11288701 = score(doc=5687,freq=4.0), product of:
        0.2711644 = queryWeight, product of:
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.05088753 = queryNorm
        0.4163047 = fieldWeight in 5687, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5687)
  0.2 = coord(1/5)

Abstract

InterParty is a project that aims to develop a mechanism that will enable the interoperation of identifiers for "parties" or persons (authors, publishers, etc. - persons and corporate bodies in library authority files) across multiple domains. Partners represent the book industry, rights management, libraries, and identifier and technology communities, united by their perception of a common benefit from interoperation in terms of access to "common metadata" held by other members to improve the quality of their own data. The InterParty solution proposes a distributed network of members who provide access to "common metadata," defined as information in the public domain, sufficient to identify and distinguish the "public identity" of a person. At a minimum the InterParty network would provide access to multiple domains of data about persons, including multiple library authority files, author licensing data files, etc. It will also add value by providing a facility for linking records between different data files by means of a "link record." Link records will assert that an identity recorded in one database is the same as another identity recorded in another database. Linked data will be mutually enriching and therefore more reliable and supportive of accurate disambiguation of persons within and between databases. InterParty has potential to develop a common system that supports both the emerging needs of e-commerce and the traditional requirements of library authority control.

0.022350488 = product of:
  0.111752436 = sum of:
    0.111752436 = weight(_text_:link in 5001) [ClassicSimilarity], result of:
      0.111752436 = score(doc=5001,freq=2.0), product of:
        0.2711644 = queryWeight, product of:
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.05088753 = queryNorm
        0.4121206 = fieldWeight in 5001, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5001)
  0.2 = coord(1/5)

Footnote

Vgl. auch: lautet: http://eprints.rclis.org/archive/00008308/. Link auf die Grafiken: http://www.obvsg.at/fileadmin/files/obvsg/publ/BIT_4_06_FB_Oberhauser.pdf.

0.022350488 = product of:
  0.111752436 = sum of:
    0.111752436 = weight(_text_:link in 5796) [ClassicSimilarity], result of:
      0.111752436 = score(doc=5796,freq=2.0), product of:
        0.2711644 = queryWeight, product of:
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.05088753 = queryNorm
        0.4121206 = fieldWeight in 5796, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5796)
  0.2 = coord(1/5)

Abstract

Local and regional authority files exist to cover gaps in national and international authority files. These types of authority files should not exist alone if they are going to be fully utilized by other institutions that may have resources about the same individuals or topics. This article discusses how the Western Name Authority File, a regional controlled vocabulary of personal names and corporate bodies, can link to larger authority files such as the Library of Congress Name Authority File and Wikidata. Workflows and issues encountered with linking this local authority file to larger authority files are discussed.

0.019304762 = product of:
  0.09652381 = sum of:
    0.09652381 = weight(_text_:22 in 5819) [ClassicSimilarity], result of:
      0.09652381 = score(doc=5819,freq=2.0), product of:
        0.17819946 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.05088753 = queryNorm
        0.5416616 = fieldWeight in 5819, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.109375 = fieldNorm(doc=5819)
  0.2 = coord(1/5)

Date

24. 5.2001 19:22:37

0.016546939 = product of:
  0.08273469 = sum of:
    0.08273469 = weight(_text_:22 in 6888) [ClassicSimilarity], result of:
      0.08273469 = score(doc=6888,freq=2.0), product of:
        0.17819946 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.05088753 = 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.2 = coord(1/5)

Date

26.12.2011 12:30:22

0.016546939 = product of:
  0.08273469 = sum of:
    0.08273469 = weight(_text_:22 in 131) [ClassicSimilarity], result of:
      0.08273469 = score(doc=131,freq=2.0), product of:
        0.17819946 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.05088753 = 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.2 = coord(1/5)

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.016546939 = product of:
  0.08273469 = sum of:
    0.08273469 = weight(_text_:22 in 1266) [ClassicSimilarity], result of:
      0.08273469 = score(doc=1266,freq=2.0), product of:
        0.17819946 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.05088753 = 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.2 = coord(1/5)

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.016546939 = product of:
  0.08273469 = sum of:
    0.08273469 = weight(_text_:22 in 1290) [ClassicSimilarity], result of:
      0.08273469 = score(doc=1290,freq=2.0), product of:
        0.17819946 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.05088753 = 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.2 = coord(1/5)

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.015964633 = product of:
  0.079823166 = sum of:
    0.079823166 = weight(_text_:link in 2293) [ClassicSimilarity], result of:
      0.079823166 = score(doc=2293,freq=2.0), product of:
        0.2711644 = queryWeight, product of:
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.05088753 = queryNorm
        0.29437187 = fieldWeight in 2293, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2293)
  0.2 = coord(1/5)

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).

0.015964633 = product of:
  0.079823166 = sum of:
    0.079823166 = weight(_text_:link in 2295) [ClassicSimilarity], result of:
      0.079823166 = score(doc=2295,freq=2.0), product of:
        0.2711644 = queryWeight, product of:
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.05088753 = queryNorm
        0.29437187 = fieldWeight in 2295, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2295)
  0.2 = coord(1/5)

Abstract

The paper provides an illustration of the benefits of subject authority control improving multilingual subject access in NEBIS - Netzwerk von Bibliotheken und Informationsstellen in der Schweiz. This example of good practice focuses on some important aspects of classification and indexing. NEBIS subject authorities comprise a classification scheme and multilingual subject descriptor system. A bibliographic system supported by subject authority control empowers libraries as it enables them to expand and adjust vocabulary and link subjects to suit their specific audience. Most importantly it allows the management of different subject vocabularies in numerous languages. In addition, such an enriched subject index creates re-usable and shareable source of subject statements that has value in the wider context of information exchange. The illustrations and supporting arguments are based on indexing practice, subject authority control and use of classification in ETH-Bibliothek, which is the largest library within the NEBIS network.

0.015964633 = product of:
  0.079823166 = sum of:
    0.079823166 = weight(_text_:link in 2297) [ClassicSimilarity], result of:
      0.079823166 = score(doc=2297,freq=2.0), product of:
        0.2711644 = queryWeight, product of:
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.05088753 = queryNorm
        0.29437187 = fieldWeight in 2297, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2297)
  0.2 = coord(1/5)

Abstract

The paper introduces TinREAD (The Information Navigator for Readers), an integrated library system produced by IME Romania. The main feature of interest is the way TinREAD can handle a classification-based thesaurus in which verbal index terms are mapped to classification notations. It supports subject authority control interlinking the authority files (subject headings and UDC system). Authority files are used for indexing consistency. Although it is said that intellectual indexing is, unlike automated indexing, both subjective and inconsistent, TinREAD is using intellectual indexing as input (the UDC notations assigned to documents) for the automated indexing resulting from the implementation of a thesaurus structure based on UDC. Each UDC notation is represented by a UNIMARC subject heading record as authority data. One classification notation can be used to search simultaneously into more than one corresponding thesaurus. This way natural language terms are used in indexing and, at the same time, the link with the corresponding classification notation is kept. Additionally, the system can also manage multilingual data for the authority files. This, together with other characteristics of TinREAD are largely discussed and illustrated in the paper. Problems encountered and possible solutions to tackle them are shown.

0.012771706 = product of:
  0.06385853 = sum of:
    0.06385853 = weight(_text_:link in 2188) [ClassicSimilarity], result of:
      0.06385853 = score(doc=2188,freq=2.0), product of:
        0.2711644 = queryWeight, product of:
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.05088753 = queryNorm
        0.23549749 = fieldWeight in 2188, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.03125 = fieldNorm(doc=2188)
  0.2 = coord(1/5)

Abstract

This article focuses on the use of the German language subject headings authority file SWD (Schlagwortnormdatei) in Austria and outlines how Austrian academic libraries' employment of the SWD developed in active cooperation with their SWD partners. The Austrian subject indexing practice turned to the SWD terminology based on the newly published German subject indexing rules RSWK (Regeln für den Schlagwortkatalog) in the late 1980s. An electronic workflow was developed. Soon it became necessary to provide a data pool for new terms originally created by Austrian member libraries and to connect these data with the SWD source data (ÖSWD, 1991). Internal cooperation structures developed when local SWD editorial departments began to exist. As of 1994 a central editor was nominated to serve as direct link between active Austrian SWD users and SWD partners and the German National Library (DNB). Unfortunately the first active SWD period was followed by a long term vacancy due to the first central editor's early retirement. Nearly all functional and information structures stopped functioning while local data increased on a daily basis... In 2004 a new central ÖSWD editor was nominated, whose first task it was to rebuild structures, to motivate local editors as well as terminology experts in Austria, to create a communication network for exchanging information and to cooperate efficiently with the DNB and Austria's SWD partners. The great number of old data and term duplicates and the special role of personal names as subject authority data in the Austrian library system meant that newly created and older or reused terms had to be marked in a special way to allow for better segmentation and revision. Now, in 2008, the future of Austrian SWD use looks bright. Problems will continue to be overcome as the forthcoming new online editing process for authority files provides new challenges.

0.012771706 = product of:
  0.06385853 = sum of:
    0.06385853 = weight(_text_:link in 2303) [ClassicSimilarity], result of:
      0.06385853 = score(doc=2303,freq=2.0), product of:
        0.2711644 = queryWeight, product of:
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.05088753 = queryNorm
        0.23549749 = fieldWeight in 2303, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.03125 = fieldNorm(doc=2303)
  0.2 = coord(1/5)

Abstract

Authority control is a standard practice in the library community that provides consistent, unique, and unambiguous reference to entities such as persons, places, concepts, etc. The ideal way of referring to authority records through unique identifiers is in line with the current linked data principle. When presenting a bibliographic record, the linked authority records are expanded with the authoritative information. This way, any update in the authority records will not affect the indexing of the bibliographic records. The structural information in the authority files can also be leveraged to expand the user's query to retrieve bibliographic records associated with all the variations, narrower terms or related terms. However, in many digital libraries, especially largescale aggregations such as WorldCat and Europeana, name strings are often used instead of authority record identifiers. This is also partly due to the lack of global authority records that are valid across countries and cultural heritage domains. But even when there are global authority systems, they are not applied at scale. For example, in WorldCat, only 15% of the records have DDC and 3% have UDC codes; less than 40% of the records have one or more topical terms catalogued in the 650 MARC field, many of which are too general (such as "sports" or "literature") to be useful for retrieving bibliographic records. Therefore, when a user query is based on a Dewey code, the results usually have high precision but the recall is much lower than it should be; and, a search on a general topical term returns millions of hits without being even complete. All these practices make it difficult to leverage the key benefits of authority files. This is also true for authority files that have been transformed into linked data and enriched with mapping information. There are practical reasons for using name strings instead of identifiers. One is the indexing and query response. The future infrastructure design should take the performance into account while embracing the benefit of linking instead of copying, without introducing extra complexity to users. Notwithstanding all the restrictions, we argue that largescale aggregations also bring new opportunities for better exploiting the benefits of authority records. It is possible to use machine learning techniques to automatically link bibliographic records to authority records based on the manual input of cataloguers. Text mining and visualization techniques can offer a contextual view of authority records, which in return can be used to retrieve missing or mis-catalogued records. In this talk, we will describe such opportunities in more detail.

0.011175244 = product of:
  0.055876218 = sum of:
    0.055876218 = weight(_text_:link in 4529) [ClassicSimilarity], result of:
      0.055876218 = score(doc=4529,freq=2.0), product of:
        0.2711644 = queryWeight, product of:
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.05088753 = queryNorm
        0.2060603 = fieldWeight in 4529, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3287 = idf(docFreq=582, maxDocs=44218)
          0.02734375 = fieldNorm(doc=4529)
  0.2 = coord(1/5)

Content

Nur die Verbundbibliotheken des OBV können überdies ihre zu den Nachschlagewerken passenden Bestände in Aleph hinzufügen, ggf. selbst via Web-Frontend im Tool einen Link zum eigenen Verbundkatalog neu anlegen, und insbesondere ihre lokal verfügbaren elektronischen Volltexte anbinden3. Im Backend werden neue Datensätze angelegt, vorhandene Einträge korrigiert, redaktionelle Kommentare platziert und Korrekturanträge abgeschöpft sowie Neuauflagen für die richtige Anzeige und Verknüpfung, etwa mit der Rangfolgeliste, zu ihrem "Anker-Datensatz" umgelenkt. Außerdem werden hier HTML-Seiten wie Hilfetext, Rangfolgeliste u. ä. gepflegt. - Zum Administrationsinterface haben nur der Webmaster der UB Wien, die SWD-Zentralredaktion des OBV sowie die Fachabteilung SE der DNB Zugang. (Nicht nur) Sacherschließerinnen können das Tool mit all seinen Vorteilen nutzen und dennoch in gewohnter Weise vorgehen, wenn sie nach Quellen für ihre Neuansetzungen suchen wollen und darin recherchieren müssen, denn die Struktur des Tools folgt dem Aufbau der Druckfassung. Es empfiehlt sich, im jeweiligen Bibliothekssystem für SWD und PND zum Feld Quelle einen Hypertextlink im Erfassungsmodul anzubringen. Die Normdateiarbeit ist komplex und anspruchsvoll. Die Einhaltung der für alle Neuansetzungen verbindlichen Rangfolge wird mit dem Tool und seiner praxisorientierten Aufbereitung ganz entscheidend erleichtert, was von Beginn an zu einer hohen Qualität jedes Normdatensatzes verhilft. Den größten Zeitgewinn in der täglichen Praxis bringt der sofortige Zugriff auf verlinkte Volltexte. - Angesichts des zunehmenden multilateralen Datentausches bei gleichzeitiger dramatischer Verknappung personeller Ressourcen trotz eines erheblichen Anstiegs des inhaltlich zu erschließenden Literaturaufkommens wird dies im Workflow des vor kurzem eingeführten Online-Redaktionsverfahrens (ONR) für Normdateien der wohl nachhaltigste Effekt von "NSW online" sein."

0.011031292 = product of:
  0.055156462 = sum of:
    0.055156462 = weight(_text_:22 in 249) [ClassicSimilarity], result of:
      0.055156462 = score(doc=249,freq=2.0), product of:
        0.17819946 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.05088753 = queryNorm
        0.30952093 = fieldWeight in 249, 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=249)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22

0.011031292 = product of:
  0.055156462 = sum of:
    0.055156462 = weight(_text_:22 in 4594) [ClassicSimilarity], result of:
      0.055156462 = score(doc=4594,freq=2.0), product of:
        0.17819946 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.05088753 = queryNorm
        0.30952093 = fieldWeight in 4594, 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=4594)
  0.2 = coord(1/5)

Date

16. 7.2011 11:54:22

0.009652381 = product of:
  0.048261903 = sum of:
    0.048261903 = weight(_text_:22 in 5760) [ClassicSimilarity], result of:
      0.048261903 = score(doc=5760,freq=2.0), product of:
        0.17819946 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.05088753 = queryNorm
        0.2708308 = fieldWeight in 5760, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5760)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22

0.009652381 = product of:
  0.048261903 = sum of:
    0.048261903 = weight(_text_:22 in 120) [ClassicSimilarity], result of:
      0.048261903 = score(doc=120,freq=2.0), product of:
        0.17819946 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.05088753 = queryNorm
        0.2708308 = fieldWeight in 120, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0546875 = fieldNorm(doc=120)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22

0.009652381 = product of:
  0.048261903 = sum of:
    0.048261903 = weight(_text_:22 in 156) [ClassicSimilarity], result of:
      0.048261903 = score(doc=156,freq=2.0), product of:
        0.17819946 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.05088753 = queryNorm
        0.2708308 = fieldWeight in 156, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0546875 = fieldNorm(doc=156)
  0.2 = coord(1/5)

Date

10. 9.2000 17:38:22