Search (208 results, page 11 of 11)

2.1016564E-4 = product of:
  0.0035728158 = sum of:
    0.0035728158 = weight(_text_:in in 5796) [ClassicSimilarity], result of:
      0.0035728158 = score(doc=5796,freq=2.0), product of:
        0.033961542 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.024967048 = queryNorm
        0.10520181 = fieldWeight in 5796, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5796)
  0.05882353 = coord(1/17)

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.

2.1016564E-4 = product of:
  0.0035728158 = sum of:
    0.0035728158 = weight(_text_:in in 698) [ClassicSimilarity], result of:
      0.0035728158 = score(doc=698,freq=2.0), product of:
        0.033961542 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.024967048 = queryNorm
        0.10520181 = fieldWeight in 698, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.0546875 = fieldNorm(doc=698)
  0.05882353 = coord(1/17)

Abstract

The concept of authorship is central to how libraries organize their collections. But libraries do not only collect resources created by individuals, they also collect documents issued by organizations. Library catalogers use the concept of a "corporate body" to treat organizations as authors for the purpose of making their documents discoverable to users. This essay looks at the key features of establishing authorized access points (AAPs) and applying authority control for corporate bodies. It examines how practices with regard to corporate bodies have changed over time and considers the changes catalogers might expect to see in the future.

2.0801005E-4 = product of:
  0.0035361708 = sum of:
    0.0035361708 = weight(_text_:in in 1160) [ClassicSimilarity], result of:
      0.0035361708 = score(doc=1160,freq=6.0), product of:
        0.033961542 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.024967048 = queryNorm
        0.1041228 = fieldWeight in 1160, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.03125 = fieldNorm(doc=1160)
  0.05882353 = coord(1/17)

Abstract

This paper is the second in a series in D-Lib Magazine and describes a workflow management system being developed by the Digital Knowledge Center (DKC) at the Milton S. Eisenhower Library (MSEL) of The Johns Hopkins University. Based on experience from digitizing the Lester S. Levy Collection of Sheet Music, it was apparent that large-scale digitization efforts require a significant amount of human labor that is both time-consuming and costly. Consequently, this workflow management system aims to reduce the amount of human labor and time for large-scale digitization projects. The mission of this second phase of the project ("Levy II") can be summarized as follows: * Reduce costs for large collection ingestion by creating a suite of open-source processes, tools, and interfaces for workflow management * Increase access capabilities by providing a suite of research tools * Demonstrate utility of tools and processes with a subset of the online Levy Collection The cornerstones of the workflow management system include optical music recognition (OMR) software and an automated name authority control system (ANAC). The OMR software generates a logical representation of the score for sound generation, music searching, and musicological research. The ANAC disambiguates names, associating each name with an individual (e.g., the composer Septimus Winner also published under the pseudonyms Alice Hawthorne and Apsley Street, among others). Complementing the workflow tools, a suite of research tools focuses upon enhanced searching capabilities through the development and application of a fast, disk-based search engine for lyrics and music and the incorporation of an XML structure for metadata. The first paper (Choudhury et al. 2001) described the OMR software and musical components of Levy II. This paper focuses on the metadata and intellectual access components that include automated name authority control and the aforementioned search engine.

2.0801005E-4 = product of:
  0.0035361708 = sum of:
    0.0035361708 = weight(_text_:in in 1240) [ClassicSimilarity], result of:
      0.0035361708 = score(doc=1240,freq=6.0), product of:
        0.033961542 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.024967048 = queryNorm
        0.1041228 = fieldWeight in 1240, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.03125 = fieldNorm(doc=1240)
  0.05882353 = coord(1/17)

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.

1.8014197E-4 = product of:
  0.0030624135 = sum of:
    0.0030624135 = weight(_text_:in in 6103) [ClassicSimilarity], result of:
      0.0030624135 = score(doc=6103,freq=2.0), product of:
        0.033961542 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.024967048 = queryNorm
        0.09017298 = fieldWeight in 6103, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.046875 = fieldNorm(doc=6103)
  0.05882353 = coord(1/17)

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.

1.8014197E-4 = product of:
  0.0030624135 = sum of:
    0.0030624135 = weight(_text_:in in 402) [ClassicSimilarity], result of:
      0.0030624135 = score(doc=402,freq=2.0), product of:
        0.033961542 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.024967048 = queryNorm
        0.09017298 = fieldWeight in 402, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.046875 = fieldNorm(doc=402)
  0.05882353 = coord(1/17)

Abstract

The implementation of our online integrated catalog ACORN at Vanderbilt University Library has been a complex and time-consuming task. The authority control component represents an important portion of the effort. The authority file consists of approximately one-half million name, subject, series, and uniform title headings, the majority of which were supplied to us by a vendor, Blackwell North America (BNA). Authority work has been integrated into our cataloging routine successfully, new headings are being added to our database daily, and extant headings are being validated online. This paper will cover a description of how Vanderbilt selected the Northwestern Online Total Integrated System (NOTIS); the ongoing editing of the authority file following the BNA processing; the interrelationship of Vanderbilt University Library's three processing units, General Technical Services (GTS), Medical Library, and Law Library apropos of the authority function; and some of the policies and procedures drawn up by the Authority Control Coordinator with the assistance of the other librarians in Monograph and Serial Services.

1.8014197E-4 = product of:
  0.0030624135 = sum of:
    0.0030624135 = weight(_text_:in in 2195) [ClassicSimilarity], result of:
      0.0030624135 = score(doc=2195,freq=2.0), product of:
        0.033961542 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.024967048 = queryNorm
        0.09017298 = fieldWeight in 2195, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.046875 = fieldNorm(doc=2195)
  0.05882353 = coord(1/17)

Source

New pespectives on subject indexing and classification: essays in honour of Magda Heiner-Freiling. Red.: K. Knull-Schlomann, u.a

1.5011833E-4 = product of:
  0.0025520115 = sum of:
    0.0025520115 = weight(_text_:in in 2293) [ClassicSimilarity], result of:
      0.0025520115 = score(doc=2293,freq=2.0), product of:
        0.033961542 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.024967048 = queryNorm
        0.07514416 = fieldWeight in 2293, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2293)
  0.05882353 = coord(1/17)

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