Search (7 results, page 1 of 1)

  • × theme_ss:"Formalerschließung"
  • × type_ss:"el"
  • × year_i:[2020 TO 2030}
  1. Vierkant, P.: Entwurf des DataCite-Metadatenschemas 4.5 offen für Kommentierung (2022) 0.00 
    0.0031205663 = product of:
  0.0062411325 = sum of:
    0.0062411325 = product of:
      0.018723397 = sum of:
        0.018723397 = weight(_text_:h in 672) [ClassicSimilarity], result of:
          0.018723397 = score(doc=672,freq=2.0), product of:
            0.113683715 = queryWeight, product of:
              2.4844491 = idf(docFreq=10020, maxDocs=44218)
              0.045758117 = queryNorm
            0.16469726 = fieldWeight in 672, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4844491 = idf(docFreq=10020, maxDocs=44218)
              0.046875 = fieldNorm(doc=672)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)
    Abstract
    "In den letzten anderthalb Jahren hat die DataCite Metadata Working Group an Änderungen für die neue Version des DataCite Metadatenschemas gearbeitet, um die sich entwickelnden neuen Anwendungsfälle für DataCite DOIs zu unterstützen. Diese vorgeschlagenen Aktualisierungen sind eine Reaktion auf Anfragen von Mitgliedern der DataCite-Community. Wir möchten sicherstellen, dass diese Änderungen funktionieren, d. h. dass sie die Probleme lösen, die sie lösen sollen. Zum ersten Mal überhaupt stellen wir deshalb einen RFC-Entwurf zur Kommentierung bereit, bevor wir die nächste Version (4.5) des Metadatenschemas veröffentlichen. Dieser Entwurf beinhaltet: * Unterstützung für Instrumente * Unterstützung von pre-registrations und registration reports * Unterstützung für Verlagsidentifikatoren * Neues Distribution property * Erläuterungen zum RelatedItem property * Aktualisierte PhysicalObject-Definition Details zur Rückmeldung sind in dem Request for Comments enthalten: https://docs.google.com/document/d/1UyQQwtjnu-4_4zXE4TFZ74-mjLZI3NkEf8RrF0WeOdI/edit Eine Kopie des Vorschlags im PDF-Format ist ebenfalls verfügbar: https://datacite.org/documents/DataCite_Metadata_Schema_4.5_RFC.pdf Weitere Informationen finden Sie im DataCite Blog: https://doi.org/10.5438/q34f-c696."
  2. Koster, L.: Persistent identifiers for heritage objects (2020) 0.00 
    0.0014819547 = product of:
  0.0029639094 = sum of:
    0.0029639094 = product of:
      0.008891728 = sum of:
        0.008891728 = weight(_text_:a in 5718) [ClassicSimilarity], result of:
          0.008891728 = score(doc=5718,freq=14.0), product of:
            0.052761257 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.045758117 = queryNorm
            0.1685276 = fieldWeight in 5718, product of:
              3.7416575 = tf(freq=14.0), with freq of:
                14.0 = termFreq=14.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5718)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)
    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.
    Type
    a
  3. Uhlemann, S.; Hammer, A.: Retrokonversion von 1,2 Millionen Zettelkarten in 1,5 Jahren (2021) 0.00 
    0.0011089934 = product of:
  0.0022179869 = sum of:
    0.0022179869 = product of:
      0.0066539603 = sum of:
        0.0066539603 = weight(_text_:a in 302) [ClassicSimilarity], result of:
          0.0066539603 = score(doc=302,freq=4.0), product of:
            0.052761257 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.045758117 = queryNorm
            0.12611452 = fieldWeight in 302, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=302)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)
    Type
    a
  4. Schwarz, S.: Kompetenzvermittlung digital : how to ... RDA? : Konzeption eines digitalen Lernangebots an der Universitäts- und Stadtbibliothek Köln (2021) 0.00 
    7.8417675E-4 = product of:
  0.0015683535 = sum of:
    0.0015683535 = product of:
      0.0047050603 = sum of:
        0.0047050603 = weight(_text_:a in 380) [ClassicSimilarity], result of:
          0.0047050603 = score(doc=380,freq=2.0), product of:
            0.052761257 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.045758117 = queryNorm
            0.089176424 = fieldWeight in 380, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=380)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)
    Type
    a
  5. Aitchison, C.R.: Cataloging virtual reality artworks: challenges and future prospects (2021) 0.00 
    7.8417675E-4 = product of:
  0.0015683535 = sum of:
    0.0015683535 = product of:
      0.0047050603 = sum of:
        0.0047050603 = weight(_text_:a in 711) [ClassicSimilarity], result of:
          0.0047050603 = score(doc=711,freq=2.0), product of:
            0.052761257 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.045758117 = queryNorm
            0.089176424 = fieldWeight in 711, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=711)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)
    Type
    a
  6. Schrader, A.: ORCID DE 2 erfolgreich beendet (2022) 0.00 
    7.8417675E-4 = product of:
  0.0015683535 = sum of:
    0.0015683535 = product of:
      0.0047050603 = sum of:
        0.0047050603 = weight(_text_:a in 824) [ClassicSimilarity], result of:
          0.0047050603 = score(doc=824,freq=2.0), product of:
            0.052761257 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.045758117 = queryNorm
            0.089176424 = fieldWeight in 824, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=824)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)
  7. Schrader, A.: ORCID DE 2 erfolgreich beendet (2022) 0.00 
    6.721515E-4 = product of:
  0.001344303 = sum of:
    0.001344303 = product of:
      0.004032909 = sum of:
        0.004032909 = weight(_text_:a in 828) [ClassicSimilarity], result of:
          0.004032909 = score(doc=828,freq=2.0), product of:
            0.052761257 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.045758117 = queryNorm
            0.07643694 = fieldWeight in 828, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=828)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)

Authors

Languages