Search (7 results, page 1 of 1)

  • × theme_ss:"Formalerschließung"
  • × year_i:[2020 TO 2030}
  1. Koster, L.: Persistent identifiers for heritage objects (2020) 0.05
    0.04942918 = product of:
      0.19771671 = sum of:
        0.19771671 = weight(_text_:objects in 5718) [ClassicSimilarity], result of:
          0.19771671 = score(doc=5718,freq=8.0), product of:
            0.33668926 = queryWeight, product of:
              5.315071 = idf(docFreq=590, maxDocs=44218)
              0.06334615 = queryNorm
            0.58723795 = fieldWeight in 5718, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              5.315071 = idf(docFreq=590, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5718)
      0.25 = coord(1/4)
    
    Abstract
    Persistent identifiers (PID's) are essential for getting access and referring to library, archive and museum (LAM) collection objects in a sustainable and unambiguous way, both internally and externally. Heritage institutions need a universal policy for the use of PID's in order to have an efficient digital infrastructure at their disposal and to achieve optimal interoperability, leading to open data, open collections and efficient resource management. Here the discussion is limited to PID's that institutions can assign to objects they own or administer themselves. PID's for people, subjects etc. can be used by heritage institutions, but are generally managed by other parties. The first part of this article consists of a general theoretical description of persistent identifiers. First of all, I discuss the questions of what persistent identifiers are and what they are not, and what is needed to administer and use them. The most commonly used existing PID systems are briefly characterized. Then I discuss the types of objects PID's can be assigned to. This section concludes with an overview of the requirements that apply if PIDs should also be used for linked data. The second part examines current infrastructural practices, and existing PID systems and their advantages and shortcomings. Based on these practical issues and the pros and cons of existing PID systems a list of requirements for PID systems is presented which is used to address a number of practical considerations. This section concludes with a number of recommendations.
  2. Serra, L.G.; Schneider, J.A.; Santarém Segundo, J.E.: Person identifiers in MARC 21 records in a semantic environment (2020) 0.03
    0.03460042 = product of:
      0.13840169 = sum of:
        0.13840169 = weight(_text_:objects in 127) [ClassicSimilarity], result of:
          0.13840169 = score(doc=127,freq=2.0), product of:
            0.33668926 = queryWeight, product of:
              5.315071 = idf(docFreq=590, maxDocs=44218)
              0.06334615 = queryNorm
            0.41106653 = fieldWeight in 127, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.315071 = idf(docFreq=590, maxDocs=44218)
              0.0546875 = fieldNorm(doc=127)
      0.25 = coord(1/4)
    
    Abstract
    This article discusses how libraries can include person identifiers in the MARC format. It suggests using URIs in fields and subfields to help transition the data to an RDF model, and to help prepare the catalog for a Linked Data. It analyzes the selection of URIs and Real-World Objects, and the use of tag 024 to describe person identifiers in authority records. When a creator or collaborator is identified in a work, the identifiers are transferred from authority to the bibliographic record. The article concludes that URI-based descriptions can provide a better experience for users, offering other methods of discovery.
  3. Soos, C.; Leazer, H.H.: Presentations of authorship in knowledge organization (2020) 0.02
    0.02471459 = product of:
      0.09885836 = sum of:
        0.09885836 = weight(_text_:objects in 21) [ClassicSimilarity], result of:
          0.09885836 = score(doc=21,freq=2.0), product of:
            0.33668926 = queryWeight, product of:
              5.315071 = idf(docFreq=590, maxDocs=44218)
              0.06334615 = queryNorm
            0.29361898 = fieldWeight in 21, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.315071 = idf(docFreq=590, maxDocs=44218)
              0.0390625 = fieldNorm(doc=21)
      0.25 = coord(1/4)
    
    Abstract
    The "author" is a concept central to many publication and documentation practices, often carrying legal, professional, social, and personal importance. Typically viewed as the solitary owner of their creations, a person is held responsible for their work and positioned to receive the praise and criticism that may emerge in its wake. Although the role of the individual within creative production is undeniable, literary (Foucault 1977; Bloom 1997) and knowledge organization (Moulaison et. al. 2014) theorists have challenged the view that the work of one person can-or should-be fully detached from their professional and personal networks. As these relationships often provide important context and reveal the role of community in the creation of new things, their absence from catalog records presents a falsely simplified view of the creative process. Here, we address the consequences of what we call the "author-asowner" concept and suggest that an "author-as-node" approach, which situates an author within their networks of influence, may allow for more relational representation within knowledge organization systems, a framing that emphasizes rather than erases the messy complexities that affect the production of new objects and ideas.
  4. Morris, V.: Automated language identification of bibliographic resources (2020) 0.02
    0.017165057 = product of:
      0.06866023 = sum of:
        0.06866023 = weight(_text_:22 in 5749) [ClassicSimilarity], result of:
          0.06866023 = score(doc=5749,freq=2.0), product of:
            0.22182742 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.06334615 = queryNorm
            0.30952093 = fieldWeight in 5749, 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=5749)
      0.25 = coord(1/4)
    
    Date
    2. 3.2020 19:04:22
  5. Das, S.; Paik, J.H.: Gender tagging of named entities using retrieval-assisted multi-context aggregation : an unsupervised approach (2023) 0.01
    0.012873792 = product of:
      0.05149517 = sum of:
        0.05149517 = weight(_text_:22 in 941) [ClassicSimilarity], result of:
          0.05149517 = score(doc=941,freq=2.0), product of:
            0.22182742 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.06334615 = queryNorm
            0.23214069 = fieldWeight in 941, 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=941)
      0.25 = coord(1/4)
    
    Date
    22. 3.2023 12:00:14
  6. Kim, J.(im); Kim, J.(enna): Effect of forename string on author name disambiguation (2020) 0.01
    0.010728161 = product of:
      0.042912643 = sum of:
        0.042912643 = weight(_text_:22 in 5930) [ClassicSimilarity], result of:
          0.042912643 = score(doc=5930,freq=2.0), product of:
            0.22182742 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.06334615 = queryNorm
            0.19345059 = fieldWeight in 5930, 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=5930)
      0.25 = coord(1/4)
    
    Date
    11. 7.2020 13:22:58
  7. Zhang, L.; Lu, W.; Yang, J.: LAGOS-AND : a large gold standard dataset for scholarly author name disambiguation (2023) 0.01
    0.010728161 = product of:
      0.042912643 = sum of:
        0.042912643 = weight(_text_:22 in 883) [ClassicSimilarity], result of:
          0.042912643 = score(doc=883,freq=2.0), product of:
            0.22182742 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.06334615 = queryNorm
            0.19345059 = fieldWeight in 883, 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=883)
      0.25 = coord(1/4)
    
    Date
    22. 1.2023 18:40:36