Search (138 results, page 1 of 7)

0.012034168 = product of:
  0.056159448 = sum of:
    0.028625458 = weight(_text_:web in 5423) [ClassicSimilarity], result of:
      0.028625458 = score(doc=5423,freq=4.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.35694647 = fieldWeight in 5423, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5423)
    0.010144223 = weight(_text_:information in 5423) [ClassicSimilarity], result of:
      0.010144223 = score(doc=5423,freq=6.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.23515764 = fieldWeight in 5423, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5423)
    0.017389767 = weight(_text_:retrieval in 5423) [ClassicSimilarity], result of:
      0.017389767 = score(doc=5423,freq=2.0), product of:
        0.07433229 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.024573348 = queryNorm
        0.23394634 = fieldWeight in 5423, 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=5423)
  0.21428572 = coord(3/14)

Abstract

This article explores recent discussions about appropriate mark-up conventions for library information intended for use on the World Wide Web. In particular, the question of whether the MARC 21 format will continue to be useful and whether the time is right for a full-fledged conversion effort to XML is explored. The author concludes that the MARC format will be relevant well into the future, and its use will not hamper access to bibliographic information via the web. Early XML exploratory efforts carried out at the Stanford University's Lane Medical Library are reported on. Although these efforts are a promising start, much more consultation and investigation is needed to arrive at broadly acceptable standards for XML library information encoding and retrieval.

0.010290484 = product of:
  0.03601669 = sum of:
    0.01445804 = weight(_text_:web in 1166) [ClassicSimilarity], result of:
      0.01445804 = score(doc=1166,freq=8.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = 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.003622937 = weight(_text_:information in 1166) [ClassicSimilarity], result of:
      0.003622937 = score(doc=1166,freq=6.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = 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.006210631 = weight(_text_:retrieval in 1166) [ClassicSimilarity], result of:
      0.006210631 = score(doc=1166,freq=2.0), product of:
        0.07433229 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.024573348 = 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.011725084 = weight(_text_:frankfurt in 1166) [ClassicSimilarity], result of:
      0.011725084 = score(doc=1166,freq=2.0), product of:
        0.10213336 = queryWeight, product of:
          4.1562657 = idf(docFreq=1882, maxDocs=44218)
          0.024573348 = queryNorm
        0.114801705 = fieldWeight in 1166, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.1562657 = idf(docFreq=1882, maxDocs=44218)
          0.01953125 = fieldNorm(doc=1166)
  0.2857143 = coord(4/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.0102489805 = product of:
  0.07174286 = sum of:
    0.024842525 = weight(_text_:retrieval in 4578) [ClassicSimilarity], result of:
      0.024842525 = score(doc=4578,freq=2.0), product of:
        0.07433229 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.024573348 = queryNorm
        0.33420905 = fieldWeight in 4578, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.078125 = fieldNorm(doc=4578)
    0.046900336 = weight(_text_:frankfurt in 4578) [ClassicSimilarity], result of:
      0.046900336 = score(doc=4578,freq=2.0), product of:
        0.10213336 = queryWeight, product of:
          4.1562657 = idf(docFreq=1882, maxDocs=44218)
          0.024573348 = queryNorm
        0.45920682 = fieldWeight in 4578, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.1562657 = idf(docFreq=1882, maxDocs=44218)
          0.078125 = fieldNorm(doc=4578)
  0.14285715 = coord(2/14)

Imprint

Frankfurt : INDEKS

Theme

Klassifikationssysteme im Online-Retrieval

0.01007836 = product of:
  0.04703235 = sum of:
    0.017349645 = weight(_text_:web in 3967) [ClassicSimilarity], result of:
      0.017349645 = score(doc=3967,freq=2.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.21634221 = fieldWeight in 3967, 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=3967)
    0.010040177 = weight(_text_:information in 3967) [ClassicSimilarity], result of:
      0.010040177 = score(doc=3967,freq=8.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.23274569 = fieldWeight in 3967, 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=3967)
    0.019642524 = product of:
      0.058927573 = sum of:
        0.058927573 = weight(_text_:2010 in 3967) [ClassicSimilarity], result of:
          0.058927573 = score(doc=3967,freq=5.0), product of:
            0.117538005 = queryWeight, product of:
              4.7831497 = idf(docFreq=1005, maxDocs=44218)
              0.024573348 = queryNorm
            0.5013491 = fieldWeight in 3967, product of:
              2.236068 = tf(freq=5.0), with freq of:
                5.0 = termFreq=5.0
              4.7831497 = idf(docFreq=1005, maxDocs=44218)
              0.046875 = fieldNorm(doc=3967)
      0.33333334 = coord(1/3)
  0.21428572 = coord(3/14)

Abstract

The Europeana Data Model (EDM) is a new approach towards structuring and representing data delivered to Europeana by the various contributing cultural heritage institutions. The model aims at greater expressivity and flexibility in comparison to the current Europeana Semantic Elements (ESE), which it is destined to replace. The design principles underlying the EDM are based on the core principles and best practices of the Semantic Web and Linked Data efforts to which Europeana wants to contribute. The model itself builds upon established standards like RDF(S), OAI-ORE, SKOS, and Dublin Core. It acts as a common top-level ontology which retains original data models and information perspectives while at the same time enabling interoperability. The paper elaborates on the aforementioned aspects and the design principles which drove the development of the EDM.

Content

Vortrag im Rahmen der Session 93. Cataloguing der WORLD LIBRARY AND INFORMATION CONGRESS: 76TH IFLA GENERAL CONFERENCE AND ASSEMBLY, 10-15 August 2010, Gothenburg, Sweden - 149. Information Technology, Cataloguing, Classification and Indexing with Knowledge Management

Theme

Information Gateway

Year

2010

0.006391353 = product of:
  0.04473947 = sum of:
    0.03469929 = weight(_text_:web in 3918) [ClassicSimilarity], result of:
      0.03469929 = score(doc=3918,freq=2.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.43268442 = fieldWeight in 3918, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.09375 = fieldNorm(doc=3918)
    0.010040177 = weight(_text_:information in 3918) [ClassicSimilarity], result of:
      0.010040177 = score(doc=3918,freq=2.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.23274569 = fieldWeight in 3918, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.09375 = fieldNorm(doc=3918)
  0.14285715 = coord(2/14)

0.006220379 = product of:
  0.029028434 = sum of:
    0.017349645 = weight(_text_:web in 3841) [ClassicSimilarity], result of:
      0.017349645 = score(doc=3841,freq=2.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.21634221 = fieldWeight in 3841, 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=3841)
    0.0050200885 = weight(_text_:information in 3841) [ClassicSimilarity], result of:
      0.0050200885 = score(doc=3841,freq=2.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.116372846 = fieldWeight in 3841, 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=3841)
    0.006658699 = product of:
      0.019976096 = sum of:
        0.019976096 = weight(_text_:22 in 3841) [ClassicSimilarity], result of:
          0.019976096 = score(doc=3841,freq=2.0), product of:
            0.08605168 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.024573348 = queryNorm
            0.23214069 = fieldWeight in 3841, 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=3841)
      0.33333334 = coord(1/3)
  0.21428572 = coord(3/14)

Abstract

This entry describes the development of the MARC Communications format. After a brief overview of the initial 10 years it describes the succeeding phases of development up to the present. This takes the reader through the expansion of the format for all types of bibliographic data and for a multiple character scripts. At the same time a large business community was developing that offered products based on the format to the library community. The introduction of the Internet in the 1990s and the Web technology brought new opportunities and challenges and the format was adapted to this new environment. There has been a great deal of international adoption of the format that has continued into the 2000s. More recently new syntaxes for MARC 21 and models are being explored.

Date

27. 8.2011 14:22:38

Source

Encyclopedia of library and information sciences. 3rd ed. Ed.: M.J. Bates

0.0060943845 = product of:
  0.04266069 = sum of:
    0.03541482 = weight(_text_:web in 1467) [ClassicSimilarity], result of:
      0.03541482 = score(doc=1467,freq=12.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.4416067 = fieldWeight in 1467, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1467)
    0.007245874 = weight(_text_:information in 1467) [ClassicSimilarity], result of:
      0.007245874 = score(doc=1467,freq=6.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.16796975 = fieldWeight in 1467, 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=1467)
  0.14285715 = coord(2/14)

Abstract

XML (eXtensible Markup Language) is fast gaining favor as the universal format for data and document exchange -- in effect becoming the lingua franca of the Information Age. Currently, "library information" is at a particular disadvantage on the rapidly evolving World Wide Web. Why? Despite libraries'explorations of web catalogs, scanning projects, digital data repositories, and creation of web pages galore, there remains a digital divide. The core of libraries' data troves are stored in proprietary formats of integrated library systems (ILS) and in the complex and arcane MARC formats -- both restricted chiefly to the province of technical services and systems librarians. Even they are hard-pressed to extract and integrate this wealth of data with resources from outside this rarefied environment. Segregation of library information underlies many difficulties: producing standard bibliographic citations from MARC data, automatically creating new materials lists (including new web resources) on a particular topic, exchanging data with our vendors, and even migrating from one ILS to another. Why do we continue to hobble our potential by embracing these self-imposed limitations? Most ILSs began in libraries, which soon recognized the pitfalls of do-it-yourself solutions. Thus, we wisely anticipated the necessity for standards. However, with the advent of the web, we soon found "our" collections and a flood of new resources appearing in digital format on opposite sides of the divide. If we do not act quickly to integrate library resources with mainstream web resources, we are in grave danger of becoming marginalized

0.0057269144 = product of:
  0.0400884 = sum of:
    0.015495556 = weight(_text_:information in 7679) [ClassicSimilarity], result of:
      0.015495556 = score(doc=7679,freq=14.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.3592092 = fieldWeight in 7679, product of:
          3.7416575 = tf(freq=14.0), with freq of:
            14.0 = termFreq=14.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=7679)
    0.024592843 = weight(_text_:retrieval in 7679) [ClassicSimilarity], result of:
      0.024592843 = score(doc=7679,freq=4.0), product of:
        0.07433229 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.024573348 = queryNorm
        0.33085006 = fieldWeight in 7679, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.0546875 = fieldNorm(doc=7679)
  0.14285715 = coord(2/14)

Abstract

Discusses the issues involved in the development of data formats for computerized information retrieval systems. Integrated databases capable of holding both bibliographic and factual information, in a single database structure, are more convenient for searching and retrieval by end users. Several bibliographic formats have been developed and are used for these bibliographic control puposes. Reviews features of 6 major bibliographic formats: USMARC, UKMARC, UNIMARC, CCF, MIBIS and ABNCD are reviewed. Only 2 formats: CCF and ABNCD are capable of holding both bibliographic and factual information and supporting the design of integrated databases. The comparison suggests that, while CCF makes more detailed provision for bibliographic information, ABNCD makes better provision for factual information such as profiles of institutions, information systems, projects and human experts

Source

Information development. 12(1996) no.4, S.218-223

0.005693029 = product of:
  0.039851204 = sum of:
    0.010040177 = weight(_text_:information in 3008) [ClassicSimilarity], result of:
      0.010040177 = score(doc=3008,freq=2.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.23274569 = fieldWeight in 3008, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.09375 = fieldNorm(doc=3008)
    0.029811028 = weight(_text_:retrieval in 3008) [ClassicSimilarity], result of:
      0.029811028 = score(doc=3008,freq=2.0), product of:
        0.07433229 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.024573348 = queryNorm
        0.40105087 = fieldWeight in 3008, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.09375 = fieldNorm(doc=3008)
  0.14285715 = coord(2/14)

Theme

Klassifikationssysteme im Online-Retrieval

0.005538526 = product of:
  0.03876968 = sum of:
    0.028625458 = weight(_text_:web in 5896) [ClassicSimilarity], result of:
      0.028625458 = score(doc=5896,freq=4.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.35694647 = fieldWeight in 5896, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5896)
    0.010144223 = weight(_text_:information in 5896) [ClassicSimilarity], result of:
      0.010144223 = score(doc=5896,freq=6.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.23515764 = fieldWeight in 5896, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5896)
  0.14285715 = coord(2/14)

Abstract

This paper proposes the use of the Unified Modeling Language (UML) as a language for modelling ontologies for Web resources and the knowledge contained within them. To provide a mechanism for serialising and processing object diagrams representing knowledge, a pair of XSI-T stylesheets have been developed to map from XML Metadata Interchange (XMI) encodings of class diagrams to corresponding RDF schemas and to Java classes representing the concepts in the ontologies. The Java code includes methods for marshalling and unmarshalling object-oriented information between in-memory data structures and RDF serialisations of that information. This provides a convenient mechanism for Java applications to share knowledge on the Web

Source

Journal of digital information. 1(2001) no.8

0.005098375 = product of:
  0.035688624 = sum of:
    0.023132863 = weight(_text_:web in 2845) [ClassicSimilarity], result of:
      0.023132863 = score(doc=2845,freq=2.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.2884563 = fieldWeight in 2845, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0625 = fieldNorm(doc=2845)
    0.012555763 = product of:
      0.03766729 = sum of:
        0.03766729 = weight(_text_:22 in 2845) [ClassicSimilarity], result of:
          0.03766729 = score(doc=2845,freq=4.0), product of:
            0.08605168 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.024573348 = queryNorm
            0.4377287 = fieldWeight in 2845, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=2845)
      0.33333334 = coord(1/3)
  0.14285715 = coord(2/14)

Abstract

The current library bibliographic infrastructure was constructed in the early days of computers - before the Web, XML, and a variety of other technological advances that now offer new opportunities. General requirements of a modern metadata infrastructure for libraries are identified, including such qualities as versatility, extensibility, granularity, and openness. A new kind of metadata infrastructure is then proposed that exhibits at least some of those qualities. Some key challenges that must be overcome to implement a change of this magnitude are identified.

Date

9.12.2005 19:22:38

Source

Library hi tech. 22(2004) no.2, S.175-181

0.0047441917 = product of:
  0.03320934 = sum of:
    0.008366814 = weight(_text_:information in 4439) [ClassicSimilarity], result of:
      0.008366814 = score(doc=4439,freq=2.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.19395474 = fieldWeight in 4439, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.078125 = fieldNorm(doc=4439)
    0.024842525 = weight(_text_:retrieval in 4439) [ClassicSimilarity], result of:
      0.024842525 = score(doc=4439,freq=2.0), product of:
        0.07433229 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.024573348 = queryNorm
        0.33420905 = fieldWeight in 4439, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.078125 = fieldNorm(doc=4439)
  0.14285715 = coord(2/14)

0.0046954756 = product of:
  0.021912219 = sum of:
    0.00722902 = weight(_text_:web in 2405) [ClassicSimilarity], result of:
      0.00722902 = score(doc=2405,freq=2.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.09014259 = fieldWeight in 2405, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.01953125 = fieldNorm(doc=2405)
    0.0029581154 = weight(_text_:information in 2405) [ClassicSimilarity], result of:
      0.0029581154 = score(doc=2405,freq=4.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.068573356 = fieldWeight in 2405, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.01953125 = fieldNorm(doc=2405)
    0.011725084 = weight(_text_:frankfurt in 2405) [ClassicSimilarity], result of:
      0.011725084 = score(doc=2405,freq=2.0), product of:
        0.10213336 = queryWeight, product of:
          4.1562657 = idf(docFreq=1882, maxDocs=44218)
          0.024573348 = queryNorm
        0.114801705 = fieldWeight in 2405, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.1562657 = idf(docFreq=1882, maxDocs=44218)
          0.01953125 = fieldNorm(doc=2405)
  0.21428572 = coord(3/14)

Content

"Standardisierung - Auch 2007 ist die Arbeitsstelle für Standardisierung (AfS) auf dem Weg zur Internationalisierung der deutschen Regelwerke, Formate und Normdateien entscheidende Schritte vorangekommen. Im Mittelpunkt der Vorbereitungen für den Format-umstieg standen eine Konkordanz von MAB2 nach MARC 21 und die Festlegung neuer Felder, die für den Umstieg auf nationaler Ebene notwendig sind. Neben einer Vielzahl anderer Aktivitäten hat die DNB zwei Veranstaltungen zum Format-umstieg durchgeführt. In Zusammenarbeit mit den Expertengruppen des Standardisierungsausschusses wurden drei Stellungnahmen zu Entwürfen des Regelwerkes »Resource Description and Access (RDA)« erarbeitet; es fand eine Beteiligung an der internationalen Diskussion zu wichtigen Grundlagen statt. Der Erfüllung des Wunsches nach Einführung der Onlinekommunikation mit Normdateien ist die DNB im vergangenen Jahr deutlich nähergekommen: Änderungen an Normdaten sollen gleichzeitig in die zentral bei der DNB gehaltenen Dateien und in der Verbunddatenbank vollzogen werden. Seit Anfang September ist die erste Stufe der Onlinekommunikation im produktiven Einsatz: Die PND-Redaktionen in den Aleph-Verbünden arbeiten online zusammen. Das neue Verfahren wird sich auf alle bei der DNB geführten Normdaten erstrecken und in einem gestuften Verfahren eingeführt werden. Die DNB war in zahlreichen Standardisierungsgremien zur Weiterentwicklung von Metadatenstandards wie z.B. Dublin Core und ONIX (Online Information eXchange) sowie bei den Entwicklungsarbeiten für The European Library beteiligt. Die Projektarbeiten im Projekt KIM - Kompetenzzentrum Interoperable Metadaten wurden maßgeblich unterstützt. Im Rahmen der Arbeiten zum Gesetz über die Deutsche Nationalbibliothek wurde ein Metadatenkernset für die Übermittlung von Metadaten an die DNB entwickelt und in einer ersten Stufe mit einem ONIX-Mapping versehen. Innerhalb des Projektes »Virtual International Authority File - VIAF« entwickelten die Library of Congress (LoC), die DNB und OCLC - zunächst für Personennamen - gemeinsam eine virtuelle, internationale Normdatei, in der die Normdatensätze der nationalen Normdateien im Web frei zugänglich miteinander verbunden werden sollen. Die bisherigen Projektergebnisse haben die Machbarkeit einer internationalen Normdatei eindrucksvoll unter Beweis gestellt. Darum haben die Projektpartner in einem neuen Abkommen, das auch die Bibliothèque Nationale de France einschließt, im Oktober 2007 ihr Engagement für den VIAF nochmals bekräftigt und damit eine Konsolidierungs- und Erweiterungsphase eingeleitet."
"DDC-vascoda - Das Projekt DDC-vascoda wurde 2007 abgeschlossen. Für den Sucheinstieg bei vascoda wurde bislang nur eine Freitextsuche über alle Felder oder eine Expertensuche, bei der die Freitextsuche mit den formalen Kriterien Autor, Titel und (Erscheinungs-)Jahr kombiniert werden kann, angeboten. Die Suche konnte zwar auf einzelne Fächer oder Fachzugänge beschränkt werden, ein sachlicher Zugang zu der Information fehlt jedoch. Vascoda verwendete die Dewey Decimal Classification (DDC) als einheitliches Klassifikationsinstrument. Ziel des Projektes DDC-vascoda war es, über diese Klassifikation einen komfortablen und einheitlichen sachlichen Zugang als Einstieg in das Gesamtangebot einzurichten. Weiterhin wurde ein HTML-Dienst entwickelt, der es Fachportalen und anderen Datenanbietern ermöglicht, ohne großen Programmieraufwand ein DDC-Browsing über die eigenen Daten bereitzustellen."

Location

Frankfurt

0.004656976 = product of:
  0.03259883 = sum of:
    0.023132863 = weight(_text_:web in 2894) [ClassicSimilarity], result of:
      0.023132863 = score(doc=2894,freq=2.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.2884563 = fieldWeight in 2894, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0625 = fieldNorm(doc=2894)
    0.009465969 = weight(_text_:information in 2894) [ClassicSimilarity], result of:
      0.009465969 = score(doc=2894,freq=4.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.21943474 = fieldWeight in 2894, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0625 = fieldNorm(doc=2894)
  0.14285715 = coord(2/14)

Abstract

To solve the problem of information loss caused by format changes requires 1 more conversion to be made, i.e. to SGML or XML. Describes the 2 formats and discusses the conversion issues involved. The sooner conversion to SGML or XML is commenced the better for the organization and if necessary, outside facilities can be called upon to provide the expertise

Source

Information today. 15(1998) no.5, S.54

0.00460788 = product of:
  0.032255158 = sum of:
    0.017349645 = weight(_text_:web in 5070) [ClassicSimilarity], result of:
      0.017349645 = score(doc=5070,freq=2.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.21634221 = fieldWeight in 5070, 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=5070)
    0.014905514 = weight(_text_:retrieval in 5070) [ClassicSimilarity], result of:
      0.014905514 = score(doc=5070,freq=2.0), product of:
        0.07433229 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.024573348 = queryNorm
        0.20052543 = fieldWeight in 5070, 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=5070)
  0.14285715 = coord(2/14)

Abstract

Much research has focused on the problem of knowledge accessibility, sharing and reuse. Specific languages (e.g. KIF, CG, RDF) and ontologies have been proposed. Common characteristics, conventions or ontological distinctions are beginning to emerge. Since knowledge providers (humans and software agents) must follow common conventions for the knowledge to be widely accessed and re-used, we propose lexical, structural, semantic and ontological conventions based on various knowledge representation projects and our own research. These are minimal conventions that can be followed by most and cover the most common knowledge representation cases. However, agreement and refinements are still required. We also show that a notation can be both readable and expressive by quickly presenting two new notations -- Formalized English (FE) and Frame-CG (FCG) - derived from the CG linear form [9] and Frame-Logics [4]. These notations support the above conventions, and are implemented in our Web-based knowledge representation and document indexation tool, WebKB¹ [7]

0.0045840573 = product of:
  0.0320884 = sum of:
    0.007245874 = weight(_text_:information in 3033) [ClassicSimilarity], result of:
      0.007245874 = score(doc=3033,freq=6.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.16796975 = fieldWeight in 3033, 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=3033)
    0.024842525 = weight(_text_:retrieval in 3033) [ClassicSimilarity], result of:
      0.024842525 = score(doc=3033,freq=8.0), product of:
        0.07433229 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.024573348 = queryNorm
        0.33420905 = fieldWeight in 3033, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.0390625 = fieldNorm(doc=3033)
  0.14285715 = coord(2/14)

Abstract

In this paper I describe a conceptual design of a bibliographic retrieval system that enables more thourough control of bibliographic entities. A bibliographic entity has 2 components: the intellectual work and the physical item. Users searching bibliographic retrieval systems generally do not search for a specific item, but are willing to retrieve one of several alternative manifestations of a work. However, contemporary bibliographic retrieval systems are based solely on the descriptions of items. Works are described only implcitly by collocating descriptions of items. This method has resulted in a tool that does not include important descriptive attributes of the work, e.g. information regarding its history, its genre, or its bibliographic relationships. A bibliographic relationship is an association between 2 bibliographic entities. A system evaluation methodology wasused to create a conceptual schema for a bibliographic retrieval system. The model is based upon an analysis of data elements in the USMARC Formats for Bibliographic Data. The conceptual schema describes a database comprising 2 separate files of bibliographic descriptions, one of works and the other of items. Each file consists of individual descriptive surrogates of their respective entities. the specific data content of each file is defined by a data dictionary. Data elements used in the description of bibliographic works reflect the nature of works as intellectual and linguistic objects. The descriptive elements of bibliographic items describe the physical properties of bibliographic entities. Bibliographic relationships constitute the logical strucutre of the database

Imprint

Oxford : Learned Information

Source

Navigating the networks: Proceedings of the 1994 Mid-year Meeting of the American Society for Information Science, Portland, Oregon, May 21-25, 1994. Ed.: D.L. Andersen et al

0.004349945 = product of:
  0.030449614 = sum of:
    0.00585677 = weight(_text_:information in 5565) [ClassicSimilarity], result of:
      0.00585677 = score(doc=5565,freq=2.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.13576832 = fieldWeight in 5565, 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=5565)
    0.024592843 = weight(_text_:retrieval in 5565) [ClassicSimilarity], result of:
      0.024592843 = score(doc=5565,freq=4.0), product of:
        0.07433229 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.024573348 = queryNorm
        0.33085006 = fieldWeight in 5565, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5565)
  0.14285715 = coord(2/14)

Abstract

Surveys how the USMARC integrated bibliographic format (UBIF) could be mapped onto an hypermedia document USMARC format (HDUF) to meet the requirements of a hypermedia document control/retrieval/delivery (HDRD) system for the Internet. Explores the characteristics of such a system using an example of the WWW's directory and searching engine Yahoo!. Discusses additional standard specifications for the UBIF's structure, content designation, and data content to map this format into the HDUF that can serve as a proxy for the Net HDRD system

Imprint

Medford, NJ : Information Today

0.0043407828 = product of:
  0.03038548 = sum of:
    0.020241255 = weight(_text_:web in 8470) [ClassicSimilarity], result of:
      0.020241255 = score(doc=8470,freq=2.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.25239927 = fieldWeight in 8470, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0546875 = fieldNorm(doc=8470)
    0.010144223 = weight(_text_:information in 8470) [ClassicSimilarity], result of:
      0.010144223 = score(doc=8470,freq=6.0), product of:
        0.04313797 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.024573348 = queryNorm
        0.23515764 = fieldWeight in 8470, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=8470)
  0.14285715 = coord(2/14)

Abstract

Explains the technology used by the Oregon State Archives to relaize the goal of data interchangeability given the prescribed nature of the MARC format. Describes an emergent model of learning and information delivery focusing on the example of World Wide Web, accessed most often by the software client Mosaic, which is the fastest growing segment of the Internet information highway. Also describes The Data Magician, a flexible program which allows for many combinations of input and output formats, and will read unconventional formats such as MARC communications format. Oregon State Archives, using Mosaic and The Data Magician, are consequently able to present valuable electronic information to a variety of users

0.0041074697 = product of:
  0.028752286 = sum of:
    0.01987402 = weight(_text_:retrieval in 2861) [ClassicSimilarity], result of:
      0.01987402 = score(doc=2861,freq=2.0), product of:
        0.07433229 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.024573348 = queryNorm
        0.26736724 = fieldWeight in 2861, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.0625 = fieldNorm(doc=2861)
    0.0088782655 = product of:
      0.026634796 = sum of:
        0.026634796 = weight(_text_:22 in 2861) [ClassicSimilarity], result of:
          0.026634796 = score(doc=2861,freq=2.0), product of:
            0.08605168 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.024573348 = queryNorm
            0.30952093 = fieldWeight in 2861, 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=2861)
      0.33333334 = coord(1/3)
  0.14285715 = coord(2/14)

Abstract

Paper presented at a symposium on 'Implementing the Art and Architecture Thesaurus (AAT): Controlled Vocabulary in the Extended MARC format', held at the 1989 Annual Conference of the Art Libraries Society of North America. Describes how changes are effected in MARC and the role of the various groups in the library community that are involved in the implementing these changes. Discusses the expansion of the formats to accomodate cataloguing and retrieval for visual materials. Expanded capabilities for coding visual materials offer greater opportunity for user access.

Date

4.12.1995 22:40:20

0.004001391 = product of:
  0.028009737 = sum of:
    0.020241255 = weight(_text_:web in 2837) [ClassicSimilarity], result of:
      0.020241255 = score(doc=2837,freq=2.0), product of:
        0.08019538 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.024573348 = queryNorm
        0.25239927 = fieldWeight in 2837, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2837)
    0.007768482 = product of:
      0.023305446 = sum of:
        0.023305446 = weight(_text_:22 in 2837) [ClassicSimilarity], result of:
          0.023305446 = score(doc=2837,freq=2.0), product of:
            0.08605168 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.024573348 = queryNorm
            0.2708308 = fieldWeight in 2837, 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=2837)
      0.33333334 = coord(1/3)
  0.14285715 = coord(2/14)

Abstract

This paper describes the Metadata Object Description Schema (MODS), its accompanying documentation and some of its applications. It reviews the MODS user guidelines provided by the Library of Congress and how they enable a user of the schema to consistently apply MODS as a metadata scheme. Because the schema itself could not fully document appropriate usage, the guidelines provide element definitions, history, relationships with other elements, usage conventions, and examples. Short descriptions of some MODS applications are given and a more detailed discussion of its use in the Library of Congress's Minerva project for Web archiving is given.

Source

Library hi tech. 22(2004) no.1, S.89-98