Search (3 results, page 1 of 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.
O'Neill, E.T.: ¬The FRBRization of Humphry Clinker : a case study in the application of IFLA's Functional Requirements for Bibliographic Records (FRBR) (2002) 0.04
```
0.04194205 = product of:
  0.1677682 = sum of:
    0.1677682 = weight(_text_:objects in 2433) [ClassicSimilarity], result of:
      0.1677682 = score(doc=2433,freq=4.0), product of:
        0.33668926 = queryWeight, product of:
          5.315071 = idf(docFreq=590, maxDocs=44218)
          0.06334615 = queryNorm
        0.49828792 = fieldWeight in 2433, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          5.315071 = idf(docFreq=590, maxDocs=44218)
          0.046875 = fieldNorm(doc=2433)
  0.25 = coord(1/4)
```
Abstract

The goal of OCLC's FRBR projects is to examine issues associated with the conversion of a set of bibliographic records to conform to FRBR requirements (a process referred to as "FRBRization"). The goals of this FRBR project were to: - examine issues associated with creating an entity-relationship model for (i.e., "FRBRizing") a non-trivial work - better understand the relationship between the bibliographic records and the bibliographic objects they represent - determine if the information available in the bibliographic record is sufficient to reliably identify the FRBR entities - to develop a data set that could be used to evaluate FRBRization algorithms. Using an exemplary work as a case study, lead scientist Ed O'Neill sought to: - better understand the relationship between bibliographic records and the bibliographic objects they represent - determine if the information available in the bibliographic records is sufficient to reliably identify FRBR entities.

Delsey, T.: ¬The Making of RDA (2016) 0.01

0.012873792 = product of:
  0.05149517 = sum of:
    0.05149517 = weight(_text_:22 in 2946) [ClassicSimilarity], result of:
      0.05149517 = score(doc=2946,freq=2.0), product of:
        0.22182742 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.06334615 = queryNorm
        0.23214069 = fieldWeight in 2946, 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=2946)
  0.25 = coord(1/4)

Date: 17. 5.2016 19:22:40

Search (3 results, page 1 of 1)

Authors

Years